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.

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.

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.

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.

Completeness is, by far, the most difficult quality characteristic to be checked in our requirements specifications.

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.

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.

Learn how Requirements Quality Suite and Requirements Authoring Tool is used with PTC Integrity Lifecycle Manager to ensure high quality, reusable requirements.

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.

Requirements Quality Analysis involves many different topics aside of the proper definition of the quality rules to follow. On the one hand, using a consistent style when writing the different types of requirements makes requirements more consistent, understandable and allows a more accurate quality check; that is addressed in RQS (Requirements Quality Suite) by means of requirements patterns.