The Requirements Quality Analyzer tool (RQA) allows you to define, measure, manage and improve the quality of the requirements' specifications. RQA performs Correctness, Completeness and Consistency analysis and it's configured according to your own quality policies.

The Requirements Quality Analyzer(RQA) uses a wide set of metrics (based on Correctness, Consistency and Completeness) in order to assess the quality of requirement specifications. In this video you will see how RQA checks the Correctness of the requirements specifications.

The Requirements Quality Analyzer (RQA) uses a wide set of metrics based on Correctness, Consistency and Completeness in order to assess the quality of requirement specifications.

RQA for Reqtify (Requirements Quality Analyzer for Reqtify) is an analysis tool to customize, assess and improve the quality of your requirements specifications managed with Reqtify.

Requirements Quality Analyzer for Excel allows you to assess and improve the quality of your requirements specifications written in MS Excel. http://www.reusecompany.com

This completeness metric compares the number of terms that are covered in the requirements specification with a selection of terms from the terminology layer of the System Knowledge Base (SKB)

This completeness metric compares the number of relationships that are found in the requirements specification with a selection of relationships from the Breakdown structure of the System Conceptual Model (SCM) layer of the System Knowledge Base (SKB)

This completeness metric compares the number of different Relationship Types (NOT relationships instances) that are found in the relationships extracted from the requirements specification with a Relationship Type selection set from the Conceptual Model layer of the System Knowledge Base (SKB)

This completeness metric compares the number of Relationships that are extracted from the requirements specification (through requirements patterns formalizations) with the Relationships that are extracted from a set of models stored in the Conceptual Model layer of the System Knowledge Base (SKB)

This completeness metric compares the number of different Properties that are found in the formalization from the requirements specification with a Properties set from the Conceptual Model layer of the System Knowledge Base (SKB)

This completeness metric compares the number of Requirements Patterns that are extracted from the requirements specification with the number of Requirements Patterns that are selected from the Patterns layer of the System Knowledge Base (SKB)

This completeness metric analyzes the not existence of links between requirements expressing the same need at the different level of abstraction in different modules/blocks of the same project.

This consistency metric compares the values of properties extracted from the specification with the values assigned to the same property stored in the Conceptual Model layer (SCM) of the System Knowledge Base (SKB)

This completeness metric compares the values of properties from the parts of a breakdown structure with the value of the property from the composite. The selected breakdown is stored in the Conceptual Model layer (SCM) of the System Knowledge Base (SKB)

This consistency metric compares several requirements from same or different specifications, representing the inconsistency ratio for requirements expressing the same need at the same level of abstraction

This consistency metric checks if the requirements from the same specification use different measurement systems (i.e. International system, British Imperial system, etc.). Therefore, it detects measurement systems’ incompatibilities for the magnitudes selected by the user. I.e.: Distance/Length – IS [Kilometers] or BIS [Yards]?, Weight – IS [Kilograms] or BIS [Pounds]?, etc.

This consistency metric checks if requirements from the same specification use different measurement units (i.e. ‘Kilograms’, ‘Pounds’, etc.) for a specific element’s property. Similar to the Measurement Units Consistency Metric, this one detects measurement units’ inconsistencies for a property of a element selected by the user. I.e.: Fuel tank – Capacity – Liters or Cubic Meters?, Aircraft – Weight – Kilograms or Pounds?, etc.

This video shows the use of the Requirements Authoring Tools (RAT), the tool in the Requirements Quality Suite to help authors while they write requirements specifications. The especial focus is on the assessment of consistency rules on-the-fly in RAT and the writing assistance based on patterns and dictionaries.

The Requirements Authoring Tool (RAT) is an assistant tool helping authors during the demanding process of writing requirements. RAT performs Correctness and Consistency analysis on the fly and suggests terminology changes based on an ontology.

Requirements Authoring Tool (RAT) is an assistant for writing requirements. RAT uses a set of agreed upon patterns and leads engineers, step by step, suggesting the most suitable content for the requirement, always ensuring the right grammar.

RAT, from requirements quality control to requirements authoring. RAT assists you in the activity of writing requirements, it performs Correctness and Consistency analysis on the fly and it suggests terminology changes based on an ontology

Help BA and SE team when they write system requirements by using a quality oriented text editor, helping them to write right the first time.

Knowledge Manager is a tool designed to manage all knowledge around your requirements intensive projects. It helps you to create the patterns used during authoring and control. A SMART way to manage the knowledge.

Knowledge Manager, as part of the Requirements Quality Suite, can customize the requirements patterns that are then used by other tools such as Requirements Authoring Tool or Requirements Quality Analyzer

The Knowledge Manager is a tool designed to manage all knowledge around your requirements intensive industrial projects. It stores this knowledge into a well-designed repository, a System Knowledge Repository (SKR).

knowledgeMANAGER - A tool to manage ontologies and thesauri. Connected to the Requirements Quality Suite, it allows to enhance the quality of the Requirements Engineering process.

In this era of Lean and Agile principles we tend to focus on collaboration, team cohesion and customer value, so where do requirements come in and how can focused requirements engineering contribute to increased customer satisfaction? It does not matter what type of engineering principles you stick to, if you do all the work in a single team, larger organisation or let someone else deliver the product or service, it all comes down to the same issues of understanding the need and delivering a solution to it. This webinar will show how requirements are the mean to the end of achieving increased customer satisfaction and the key is a changed view on the importance of requirements being the messenger between all stakeholders. Topics: Customer satisfaction is a phrase often used and perhap...

ECSS - European Cooperation for Space Standardization- represents a set of standards aiming to gain a common understanding across the space industry in Europe. ECSS released the ECSS-E-ST-10-06C (6 March 2009) to provide some guidelines for the development of technical requirements specifications. The REUSE Company has developed a Knowledge Library coping with the ECSS standard (among others within the ECSS) to guide requirements writers writing high-quality requirements and provide help during the long-lasting requirements inspections, those making easier the compliance with the ECSS standards. This Knowledge Library is part of the SES Suite (Systems Engineering Suite), managed by our tool Knowledge Library (including glossaries, taxonomies of terms, taxonomies of types of requirements, ...

Ambiguity is a factor that can jeopardize the optimal development of a project, as decisions over the requirements statement are made subjectively. And luckily this aspect can be under control if we apply Systems Engineering centred on Knowledge and Quality to develop better assets of information during the project lifecycle. There are four main aspects that aids KCSE (Knowledge Centric Systems Engineering) implementation within an organization: - Discovering Information in Requirements Documents - Controlled information to unify requirements interpretation - Identifying weaknesses and challenges in requirements documents - Building up the Knowledge Base or Ontology Verification analysis: Smarter and Quicker

Requirements are, with no doubts, the main source of re-work in both software and systems intensive projects. This webinar introduces these sources of problems and misunderstanding, and provides a set of basic tricks and techniques to overcome the problems and provide error-free requirements specifications to properly set the roots of successful projects. All these basic aspects of requirements quality will be covered using a default installation of the tools VERIFICATION Studio and the Rich Authoring Tool.

Competition in a fair and transparent manner is the heart of procurement, that is why you probably already have a process in place to ensure the legal aspects of Fairness, Integrity and Transparency through the competition. But what about the two other corner stones and key guiding principles of Economy and Effectiveness, and not least the principle of Best value for money? The Procurement Quality Suite (PQS) guarantees that the purchasing body is conducting the procurement process with maximum effectiveness in relation to the overall budget, and that the principle of Best value for money is indisputably and crystal clear from the initiation of the procurement project, through requirements definition, strategy selection and finally, bid evaluation and selection. PQS consists is an appli...

A recent blog post by our esteemed colleague Christer Fröling has sparked a tidal wave of interest and his paper “NLP beats DXL (DOORS scripting) every day of the week” has been distributed widely. But can his claim be substantiated? Dr. Simon Wright will investigate this claim during a webinar and examine the evidence. As someone who has been involved in improving requirements quality for over 20 years and as a DXL programmer for over 10 years he is ideally placed to referee this match, DXL verses NLP. During the webinar he will briefly review the development of Requirements Quality Tools and draw out the salient features that are needed to effectively and efficiently undertake NLP. He will explain the differences between textural analysis, syntax checking, semantic checking, corre...

In the world of Model-Based Systems Engineering, we usually find a huge ecosystem full of tools. The community of practitioners will be using a wide variety of different tools for Requirements Management, Logical and Physical Modelling, Traceability, Simulation, Quality Management etc. With regard to Quality Management, System Quality Analyzer (SQA) performs requirements quality assessment based on the Correctness, Completeness & Consistency (CCC) approach, that is, automatic verification of your requirements and support to requirements authoring. For this purpose, the SQA knowledge base (ontology) can be customized to automatically include -in real-time- the content of Rhapsody models or Simulink files or even external ontologies created with Protégé, among others, so that requirements...

Model-Based (MBSE) is the current trend in regard to Systems Engineering, leveraging testing and simulation activities. However, it’s also clear that textual requirements will remain in the scene since they are also key for testing, certification, and communication with other stakeholders. This Webinar describes a real scenario where, while working in a model-based project using Rhapsody, there is the need of writing high quality requirements concerning the UML/SysML elements of the project. In this scenario where UML/SysML models coexist with requirements, a crucial role is played by physical models simulations, indeed requirements feasibility is going to be tested against physical models simulation (FMUs files).

Model-Based (MBSE) is the current trend in regard to Systems Engineering, leveraging testing and simulation activities. However, it’s also clear that textual requirements will remain in the scene since they are also key for testing, certification, and communication with other stakeholders. This Webinar describes a SMART way to mix both models and textual requirements together, covering topics such as requirements transformation (from requirements to models and vice versa, from requirements to test cases…), traceability of different sorts of items, retrieval and reuse of work products… All these topics will be addressed having in mind the importance of quality standards, since are the key for systems certification, and fully required to always reuse, trace and transform high-quality ...

Nowadays, very few companies develop, distribute, and sell products end-to-end. On the contrary, it’s quite common to find the supply chain approach, where many suppliers might be involved in the whole product lifecycle. This may lead to specialization, cost reduction, and scalability. This Webinar focuses on the close communication between the OEMs (Original Equipment Manufacturers) and the Suppliers to perform quality assessment and keep track of the evolution of the quality of the supplier assets. In a nutshell, OEMs will define the quality metrics that must be fulfilled by the different Suppliers along the supply chain. Suppliers will develop their specifications, performing also quality assessment, and will send quality reports to the OEM. With this information, the OEM tracks the...

Completeness is, by far, the most difficult quality characteristic to be checked in our requirements specifications. Completeness is a twofold issue. On the one hand, a requirement statement is complete when it includes and conveys all the information it has to include: who is the subject of the action, when is this action performed, under what conditions, what should be the performance…. In other words, and citing the INCOSE Guide for Writing Requirements, a requirement statement is complete when it “… describes the necessary capability, characteristic, constraint, or quality factor … without needing other information to understand the requirement”. On the other hand, the entire specification should be analyzed in terms of completeness to answer questions such as: Are we consi...

Writing correct requirements is, sometimes, a challenging task. However, there are plenty of resources publicly available including tips on how to write correct requirements; we in The REUSE Company also provide our own guide (RQS tips summary), training and tools (RQA and RAT). Once the correctness topic is properly addressed, the real problem when analyzing the overall quality of a project (in terms of its requirements) comes with the consistency among the different requirements, that many times are written by different people, in different places… Not to mention the consistency between requirements and models in a MBSE environment. This webinar focuses on the analysis of requirements consistency, and the metrics provided in Requirements Quality Suite to deal with this topic.

When you are bidding in a public tender, every minute counts. Even for the more experienced analyst, the short time that is available makes it very difficult and risky to come up the right bid, the one that presents the best budget by maximizing existing asset reuse. You need to quickly identify those tender areas which can be matched to what you have developed or built before and, in addition, those areas that you haven't seen before. Wouldn't it be nice if you could shorten your public tender or RFP analysis with the help of The Reuse Company tools to: - Quickly parse the tender - Pre-allocate or cluster requirements according to specific criteria - Compare tender requirements with your existing assets to determine what has been previously developed or built and therefore make a more edu...

Learn how Requirements Quality Suite and Requirements Authoring Tool is used with PTC Integrity Lifecycle Manager to ensure high quality, reusable requirements. These requirements can then form a high quality foundation to drive successful UML / SysML activity. This allows multi-discipline teams to build complete reliable and agile traceability across your engineering assets.

Finding the proper set of quality rules to be checked in our requirements documents is key for the success of our projects. RQA (Requirements Quality Analyzer) allows you an easy translation between paper-based quality rules and checklists into an automatic tool to help quality teams and requirements authors. RQA includes, out-of-the-box, a wide variety of requirements quality metrics. However, in some cases, the metrics to follow have to be tailored for particular cases and the out-of-the-box metrics could be not sufficient. This Webinar shows how a set of parameterized metrics can help to create custom metrics easily. All this custom metrics are automatically and seamlessly integrated together with the rest of out-of-the-box metrics and are accessible in both RQA and RAT (Requirements Au...

In this webinar we will show how KM (Knowledge Manager) can be used to easily create and manage requirements patterns. RAT (Requirements Authoring Tool) will also be shown briefly to exemplify the writing of a new requirement based on one of the patterns created during the live demonstration, and how to apply requirements patterns for an automatic extraction of requirements from an unstructured source. Finally, we will also show how RQA (Requirements Quality Analyzer) can make use of those patterns to leverage the use of the quality metrics, and to extract content suitable for the knowledge base (domain concepts and relationships among concepts, properties…). RQA, RAT and KM are the tools included in the Requirements Quality Suite (RQS).

Checking and enhancing the quality of requirement specifications is a vital task for ensuring a successful outcome of a project. Out-of-the-Box the Requirements Quality Analyzer (RQA), and the Requirements Authoring Tool (RAT), help the user to avoid the most common and most annoying mistakes found in requirements. During this webinar we will explain and demonstrate the mechanisms offered by the RQS Tools to deal with the bulk discovery, capture and management of knowledge, and how sources of knowledge in current, or even previous projects can be used to ease this process.

IBM Rational DOORS is a popular tool for managing requirements. However, DOORS alone is not enough to ensure the quality of your requirements, and the use of best practice, whilst conforming to external regulations. This Webinar will show how the Requirements Quality Suite (RQS) allows the tailoring of the rules your requirements must follow (individual, as a set, across the whole project or within an organization); including the control of these rules with Requirements Quality Analyzer (RQA), or the on-line help for the authors, using the Requirements Authoring Tool (RAT). The webinar will highlight the new features of the latest version of the Requirements Quality Suite, giving those who still are unfamiliar with these tools, a clear overview of how you can improve the quality of your re...

The REUSE Company is specialized in the application of Semantic Analysis Technologies to a wide range of industries (Aerospace, Defense, Automotive, Naval, Health, Industrial machinery...). Our customers are usually (but not limited to) safety oriented organizations. Our main focus is on System/Software Reuse, Traceability and Quality.

The REUSE Company (TRC) as a IVS with some Requirements Engineering products in the market aimed to analyze and improve the quality of requirements specifications as a plugin of IBM DOORS, Visure Requirements, Reqtify or MS Office