Webinars

We are moving from delivering systems to delivering services, and thus, knowledge digitalization plays a key role in order to improve the way we do engineering for our development procedures. Therefore, we need to align the methods and techniques with the business needs to align all the legacy assets with the required development and manufacturing needs.

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.

Upon landing in Mexico, Conquistador Hernán Cortés famously ordered his men to “burn the boats”. For the same reasons, our journey towards Model Based System Engineering (MBSE) will require the burning of the specification “document boats” used to house and transport the most important artifacts; i.e. the declarations of Stakeholder Needs and System Requirements.

Traceability is a core activity within the System Development Lifecycle, although a tedious and time-consuming task, especially when the traces involve items coming from different disciplines and tools.

Guidelines for the development of technical requirements specifications in the space industry following the ECSS-E-ST-10-06C.

Ambiguity can jeopardize a project. Learn how to apply Systems Engineering centered on Knowledge and Quality to develop better information!

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

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?

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?

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

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.

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.

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.

Our partner Requirements Experts organizes a LIVE Webinar called "Case Study: Vasa Warhip Project"