Tags : Browse Projects

Select a tag to browse associated projects and drill deeper into the tag cloud.

jUCMNav

Compare

  Analyzed 7 months ago

jUCMNav is a graphical editor for modeling, analysis and transformations with the User Requirements Notation (URN), which includes the Use Case Map (UCM) notation and the Goal-oriented Requirement Language (GRL). It also supports Feature Models. jUCMNav is an Eclipse plug-in.

198K lines of code

4 current contributors

7 months since last commit

10 users on Open Hub

Activity Not Available
5.0
 
I Use This

Isotrol RequMNGT Redmine Plugin

Compare

  Analyzed over 2 years ago

RequMNGT is a Redmine plugin that allows you to manage in your software project: * system and software requirements. * traceability. * baseline and Request For Change. 1. you can identify business artifacts, software artifact and others like Business Actor, Business Use Case,... 2. you ... [More] can manage and check the (Horizontal and vertical) TOTAL TRACEABILITY between the different artifact of a software project: * Feature, Requirement, Use case, classes, test case, code ... 3. You can create, delete, modify one or several baseline and manage the requests for change. 4. You can generate different reports (requirement, usecase, testcase, Metrics ...) 5. If you install the risk management plugin RiskMNGT, you could classify the requirements or scenarios according to the exposure level [Less]

12.7K lines of code

0 current contributors

over 7 years since last commit

3 users on Open Hub

Activity Not Available
0.0
 
I Use This

Xuse Requirements & Use-Case management

Compare

  Analyzed about 2 months ago

The Xuse project defines an XML data model that allows for the capture and management of software requirements from a use-case centric perspective. The project provides XSLTs to create multiple views on this data model in a variety of formats such as HTML, PDF, SVG etc. As all the data is stored ... [More] in XML it is possible to provide different information to different consumers: for example you may wish to document technical issues of why a software requirement will be difficult to implement but not show this information to the customer who is signing off the requirements. Additionally different people such as QA engineers and developers may require different views on the data - something that XSLT facilitates. [Less]

23.8K lines of code

0 current contributors

about 4 years since last commit

3 users on Open Hub

Activity Not Available
4.0
   
I Use This

rmtoo

Compare

  Analyzed about 6 hours ago

rmtoo is an open source requirements management tool. It is intended for programmers as it comes with no GUI. The requirements are stored in plain text files. The tool allows e. g. to check dependencies (traceability) or create different LaTeX artifacts like project backlog or priorization list. ... [More] Also supported is effort estimation for the not yet implemented requirements. [Less]

40K lines of code

0 current contributors

over 4 years since last commit

2 users on Open Hub

Inactive
4.0
   
I Use This

oors

Compare

  Analyzed over 2 years ago

A tool for managing relationships between objects. It is primary being designed for use as a specification management tool for systems engineering but is being kept completely generalised so that it can be used for other purposes. Core ConceptsProvides the ability to define relationships between ... [More] paragraphs of text that are managed as individual objects. Completely general and definable. Uses a well defined data model that can be queried easily. Full scripting ability for extensions to the core product. Inspired from Rational (previously Telelogic) DOORS. DocumentsOverview Design Interface Design Design Releases [Less]

6.64K lines of code

0 current contributors

over 5 years since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This

Olympos

Compare

  Analyzed 7 months ago

Olympos is an holistic MDA/MDD approach to projects. It allows to create Web (PHP, J2EE), Desktop (c#) and Mobile applications (.NET, J2ME) from a UML model. Features a Web 2.0 IDE, a generator based on openArchitectureWare and several cartridges.

842K lines of code

3 current contributors

7 months since last commit

1 users on Open Hub

Activity Not Available
5.0
 
I Use This

CAIRIS

Compare

  Analyzed 3 months ago

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]

272K lines of code

9 current contributors

3 months since last commit

1 users on Open Hub

Activity Not Available
0.0
 
I Use This

ARREA

Compare

  Analyzed 3 months ago

ARREA (A Reasonable Requirements Engineering Application) is a simple yet powerful requirements management tool that uses XML files to store information and Subversion to allow team collaboration

289 lines of code

0 current contributors

almost 5 years since last commit

1 users on Open Hub

Activity Not Available
5.0
 
I Use This

Pyrede

Compare

  Analyzed 37 minutes ago

A web service to find packages in distributions from a requirements.txt file

9.76K lines of code

0 current contributors

over 3 years since last commit

1 users on Open Hub

Inactive
5.0
 
I Use This
Licenses: No declared licenses

x-rms

Compare

  Analyzed about 1 year ago

Most specifications (describing requirements, tests, constraints/hazards, and design approaches) for complex systems are hosted either in databases, in documents, or in wiki's. All approaches have their strengths and weaknesses. Database-based system tend to be expensive and proprietary, and ... [More] conversion systems are needed to generate document "views" onto the data that can be read by stakeholders and persisted in a document control system. Database approaches provide great flexibility and enable linking between requirements and related artifacts like tests, design details, constraints, parent requirements, and hazards. Document-based systems are inexpensive and easy to set up, but lack a mechanism to link requirements to related artifacts. It can also be hard to maintain consistency in document formatting and content with multiple spec authors at work. Wikis provide easy access to project stakeholders, but don't lend themselves to structured and consistent information formatting. Linking wiki pages and table records can be manually intensive, and creating print-quality documents can be difficult. LSpeX combines the power of a database-driven RMS system with the simplicity and low cost of document and wiki-driven systems. All requirements and related artifacts are persisted in XML, with one XML file created per requirement, test, hazard, or design specification. Each specification type has an associated schema to ensure compliance to organization-specific specification norms. XSL-FO is used to transform the XML-based specifications into a set of PDF documents. The key feature of the resulting PDF documents is a rich set of internal and external links. The links help management complexity by making it easy to navigate between related specifications. For example, links connect individual requirements to the test protocols that demonstrate their complete implementation, and to the constraints or hazards that motivate their existence. PDF redlines can be automatically generated for change management activities. The entire system is customizable through a set of XSLT files, and is powered by Xalan and FOP (both open source). Plugins can be created to connect the system to wiki's and document control systems to make specification reading and controlled editing easy. [Less]

0 lines of code

0 current contributors

over 8 years since last commit

0 users on Open Hub

Activity Not Available
0.0
 
I Use This
Mostly written in language not available
Licenses: Apache-2.0