Did you know? When it comes to requirements patterns, both good and bad requirements patterns are valuable for analyzing quality. Requirements Quality Analyzer RQA, in version 2014, includes a very interesting feature to define parameterized metrics. Those parameterized metrics are seamlessly integrated together with the rest of out-of-the-box metrics, and provides the end user an easy to use extensibility to describe your own metrics.
Did you know? RAT v2014 is now able to connect to different requirements repositories. Unlike RAT version 4.x that was only available for IBM DOORS, RAT v2014 is able to connect to IBM DOORS, Visure REQUIREMENTS, CATIA Reqtify and Microsoft Excel. Furthermore, RAT now comes in different flavours:
Did you know? The quality of your requirements can be assessed automatically while you are sleeping.
The Requirements Quality Suite (RQA) cannot only analyze your requirements quality on the fly; it can also assess your requirements off-line. The RQA Synchronizer is in charge of this functionality, by performing an off-line assessment. A scheduled task can be created to run RQA Synchronizer at any time and in a regular basis.
knowledgeMANAGER, our tool for ontology management, comes with some classical types of relationships; parent-child, related... are some classical types of relationships for thesauri and ontologies.
Aside of those types, it's very easy to add and manage new types of relationships, known as semantics in the current version of knowledgeMANAGER. Furthermore, it's very easy to import concepts, from an external source, that are related using this new type of relationships.
Did you know? Reducing inconsistencies between requirements is an easy way to reduce your project costs.
Thanks to the ontology-based semantic analysis that RQS (Requirements Quality Suite) is able to perform; now you can automatically find these inconsistencies in your project requirements.
According to many sources, including INCOSE in its Systems Engineering Handbook, the cost of fixing a defect introduced during the early stages of a project grows exponentially as time goes by along the different phases of the project. In other words, if the cost of fixing a defect that was introduced in the requirements engineering phase were US$1, fixing the same defect during the development could be up to 100 times more expensive and fixing it in production could be up to 1,000 times more expensive.
Did you know? Coupled and inconsistent requirements are two big issues when writing your requirements specifications.
Thanks to the semantic analysis of RQS, based on Natural Language Processing, a semantic graph can be generated out of every single requirement. This is the process we call formalization. Requirements with similar formalization can be considered as coupled requirements, while further analysis can be done to detect inconsistent content.
Did you know? The correct structure (grammar) of your requirements boosts the quality of your specifications. Try Requirements Authoring Tool, based on patterns, boilerplates and ontologies, while authoring your requirements.