Video channel

Have you ever dealt with the European Space Agency (ESA)? If so, you must now know how well-written their tender documents are, and how clear and unambiguous the ESA standards are.

In this webinar we’ll present the rules and recommendations described both in the ECSS Drafting rules (ECSS-D-00-01) and in the ECSS-E-ST-10-06C. Furthermore, we’ll also show how the RAT – Authoring Tool implements all these rules so that meeting all these recommendations can be done effortlessly.

Since 1995 to the 2016 last version, NASA publishes the “NASA Systems Engineering Handbook” (https://www.nasa.gov/connect/ebooks/nasa-systems-engineering-handbook) to bring the fundamental concepts and techniques of NASA Systems Engineering as a discipline at NASA body of knowledge. This handbook offers guidance for current best Agency practices and maintains the alignment of the Handbook with the Agency’s systems engineering policy. The handbook is considered as top-level guidance for good systems engineering practices in the space industry.

We have developed a knowledge library, to be used on our SE Suite, that takes the benefits of the NASA handbook body of knowledge to enhance the quality of requirements. This NASA domain knowledge library includes glossary, acronyms, abbreviations, as well as specific taxonomies, hierarchies, and terms relationships. It also brings guidance for well-formed requirements through rules and patterns. The library incorporates a set of metrics, based on NASA handbook guidance. These metrics implemented in our SE Suite help to ensure the quality of requirements and to optimize the requirements authoring process.

Discover in this webinar how our SE Suite, along with this NASA knowledge library we have developed, can improve the quality of your organization requirement as well as your requirement authoring and checking process. Thanks to this approach, your organization could discover requirements errors in an early stage of the process, to prevent adding potentially huge extra costs and time to market delays to your organization projects.

INCOSE, the International Council on Systems Engineering has done an excellent job in the dissemination of best practices and guides towards the Systems Engineering Community. A wonderful example of this kind of guide is the INCOSE Guide for Writing Requirements (GfWR) that is helping engineers meet the challenging quality standards that every requirement shall have, especially in the Safety Critical disciplines.

While other standards just define a number of nice-to-have, but yet very abstract set of quality characteristics, the INCOSE GfWR also includes a number of comprehensible, and SMART (specific, measurable and easy to automatize), set of quality rules for requirements and for requirements documents.

No matter what tool you use to manage your requirements, RQA - QUALITY Studio and RAT - Authoring Tools from The REUSE Company offer an easy-to-use library including the quality rules described in the GfWR; allowing both quality control of your existing documents, and real-time help during the authoring stage of the requirements. Writing high-quality requirements has never been so easy.

Low requirements quality is one of the main reasons that lead to unsuccessful projects in any engineering domain. Unclear and ambiguous statements, contradictory requirements or inconsistent measures are just a few examples of the dozens of errors that are very common to happen in requirements specifications. This webinar introduces the tools to early detect these sources of problems and provides with a set of basic techniques to overcome them, so an error-free requirements specification leads to achieving successful projects. All these basic aspects of requirements quality will be covered using a default installation of the tools RQA - Quality Analyzer and RAT - Authoring Tools.

In the world of systems engineering, the importance of having high quality requirements is well known and that is why there are standards and guidelines that establish the characteristics that the requirements must have for considering them of good quality.

To obtain quality measurements of the requirements it is common to use quantitative quality metrics based on established standards. However, the risk is to build assessment methods and tools that are both arbitrary and rigid in the parameterization and combination of metrics. This webinar is focused on the presentation of a flexible method to assess and improve the quality of requirements that can be easily adapted to different contexts, projects, organizations and quality standards, with a high degree of automation.

In the method proposed, the domain experts contribute with an initial set of requirements that they have classified according to their quality, and their quality metrics are extracted. Then machine learning techniques are used to emulate the implicit expert’s quality function. A procedure to suggest least-effort improvements in bad requirements is also provided.

The method is easily tailorable to different contexts, different styles to write requirements, and different demands in quality. The whole process of inferring and applying the quality rules adapted to each organization is highly automated.

In this tutorial you will learn how to analyze the quality of your requirements with RQA - Quality Analyzer (SQA). By connecting our tool to a requirements repository like IBM DOORS, PTC, Excel etc. you can analyze the requirements quality following the criteria for Correctness, Consistency and Completeness in an automatic way.

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, requirements patterns and requirements quality rules).

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.

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 quality can be assessed against all those models.

In addition to that, the knowledge about a project is a living entity, that means that it will evolve (hopefully) along the project lifecycle. An Ontology Configuration Management process will be presented to keep track of the changes performed on the ontology.

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 quality of the different subsystems.

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 considering all different types of requirements (safety, security, regulation…)?
Are all the different types of actors mentioned in the high-level requirements?
Are we addressing the counterpart for some specific actions? That is, if a specific item can be created in a system, should it be also removed at any particular time? When a light can be switched on, shouldn’t we also expect a requirement to switch it off?
Are all the system elements described in a model well-covered in our specifications?
Are there interfaces between components where our requirements are not linking together these pair of components?
Are all the actions described at a specific level properly flowed down to the following levels?
Completeness also has to do with links and attributes. Missing links or empty attributes are also sources of incompleteness.
A tool like RQA will never replace the human labor to tackle this issue, but what technology can offer is a quick and exhaustive analysis of large requirements specifications; and, at the same time, having in mind that necessity and completeness are the two sides of the same coin.

Agenda:

Introduction
The completeness problem in systems engineering: how to know when the requirements are complete?
Completeness metrics in Requirements Quality Suite
Live demo:
Tailoring completeness metrics in RQA
Checking completeness for a DOORS specification with RQA
Q&A

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.

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 Authoring Tool)

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.

As requirements represent one of the major causes of failures in systems engineering projects, it is of the utmost importance to embrace tools & techniques that help identify defects introduced in the earliest stages of requirements engineering.

The RAT – Authoring Tool widget for IBM DOORS Next Generation offers a fully integrated interface enabling authors to write high-quality requirements based on tailored quality metrics and customized presets of requirement patterns.

The solution also features a connection to the quality management tool RQA – Quality Studio® in which the quality metrics can be edited and quality reports generated.

This webinar will present the main features of the RAT – Authoring Tool widget for IBM DOORS Next Generation and the connection to RQA – Quality Studio®.

Learn how textual and model requirements are working together towards success!
While Eclipse Capella is a model-based systems engineering environment, it’s also clear that it enables the creation of model requirements that complement textual requirements.

When dealing with both, textual and model requirements, ensuring consistency and completeness are key to the final success of our systems.

This webinar introduces a new add-on for Capella, the so-called RAT for Capella (by The REUSE Company).

Its main goals are:
- to ensure the correctness of the requirements that are managed within Capella;
- to help authors follow a pattern to end up with a well-formed requirement;
- to ensure naming consistency between the model elements and the textual requirements,
- to provide a complete round-trip in Capella between other Requirements Management System and RAT.

This webinar describse the RAT for Capella add-on, and provideq a live demo of the tool.

This webinar was driven byJosé Fuentes, Chief Operating Officer at the REUSE Company.
José Fuentes obtained his degree in Information Science at the Carlos III University of Madrid (Spain). He is the current COO of The REUSE Company.
José has been dealing with requirements engineering, software, and systems engineering for over 20 years. He’s INCOSE CSEP certified, and he’s an active contributor to INCOSE, mainly to the INCOSE Requirements Working Group, where he’s now considered as an active contributor to the INCOSE Guide for Writing Requirements.

Slides: https://fr.slideshare.net/Obeo_corp/capella-webinar-writing-perfect-textual-requirements

Creative commons BY-ND Licence: Attribution + NoDerivatives

RAT - Authoring Tools providing real-time CCC assessment and consistency with the underlying model.
The seamless integration of textual Requirements within MBSE is a challenge in today’s Systems Engineering state of the art. Requirements are usually elaborated using natural language text and hence provide high expressivity and easiness of production and management. MBSE offers well-structured methodologies (like ARCADIA, OOSE, Systematica (S*), etc.) and a rigorous path for developing high-quality designs, but they demand steep learning curves.

This webinar presents an add-on to Capella that follows all the principles and features of the RAT - Authoring Tools on top of Requirements Modeling Tools (RMS), but now on top of a Modeling tool like Capella; thus enhancing a seamless consistency between textual requirements and models (model requirements).

The webinar will include a demo of this new add-on, showing the following features:

- Assisted authoring of requirements through pattern-based auto-completion
- Real-time quality assessment
- Maintenance of relations between textual and model-based requirements, and capitalization of links for change tracking
- Synchronization of textual requirements: a round-trip approach between Capella and other external Requirements Management Systems

The use of patterns to write structured requirements is strongly recommended in Requirements Engineering in order to avoid defects in engineering systems development that are mainly traced back to unprecise, unclear, or incomplete requirements.

Since the 1990s, the members of the SOPHIST GmbH (usually called “The Sophists”) have been in the forefront of consulting and training services in the area of requirements engineering. The Sophist patterns comprise both functional and non-functional requirement patterns, as well as patterns to express conditions and properties of systems.

The objective of this webinar is to introduce you to the newly integrated Sophist patterns into our RAT - Authoring Tools, with examples of real-time writing assistance enabled by the tool in order to check the compliance with the structure of the selected pattern.

Integration of our RAT - Authoring Tools with the 3DX Platform from Dassault Systèmes to calculate the quality of requirements in real time.

In this tutorial you will learn how to analyze the quality of your requirements with RQA - Quality Analyzer (SQA). By connecting our tool to a requirements repository like IBM DOORS, PTC, Excel etc. you can analyze the requirements quality following the criteria for Correctness, Consistency and Completeness in an automatic way.

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).

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.