CAIRIS (Computer Aided Integration of Requirements and Information Security) is a Requirements Management tool for specifying secure and usable systems. CAIRIS was built from the ground-up to support the elements necessary for usability, requirements, and risk analysis. Its features include:
*
... [More] Support for KAOS goal and obstacle modelling, and traceability between goal, requirements, security, and usability model elements.
* Support for entering and managing usability data, such as personas, tasks, and use cases
* Support for entering and managing risk analysis data.
* Automatic visualisation of models, and quantitative/quantative scoring of security and usability data
* Automatic document generation of a VOLERE compliant requirements specification. [Less]
The Overture project is developing a set of open source Eclipse plug-ins to support the integration of various VDM modelling tools (Vienna Development Method). The aim is to provide support for all existing VDM tools and language dialects.
Klever is a software verification framework that aims at automated checking of programs developed in the GNU C programming language against a variety of requirements using software model checkers (automatic software verification tools) implementing such methods of thorough static analysis as Bounded
... [More] Model Checking and Counterexample-Guided Abstraction Refinement. Software model checking allows finding faults that can be hardly detected by other software quality assurance techniques like code review, testing and static analysis. In addition, it is capable to prove formal correctness of programs checked against particular requirements under certain assumptions. [Less]
IRCv3 is a project by IRC client and server software authors working to enhance, improve, maintain and standardize the current IRC protocol. Stakeholders in the IRC protocol, such as IRC networks and IRC network operators are invited to participate.
An attempt to create an updated document about how the IRC client protocol works these days.
This covers the client-server protocol only, and does not touch the S2S protocol. The reasons for this are discussed in the document. This document includes bits and pieces cherry-picked from the RFCs
... [More], IRCv3, Internet-Drafts, and commands/replies that have generally been accepted by the IRC community.
This document draws from RFC1459 and RFC2812, as well as other specifications and drafts listed. [Less]
This site uses cookies to give you the best possible experience.
By using the site, you consent to our use of cookies.
For more information, please see our
Privacy Policy