Connecting Textual Requirements with Capella Models

1
All rights reserved © The REUSE Company 2022
WEBINARS 2022
Let’s start!!

2
WEBINARS 2022 The Presenters
Current Position: Chief Sales Manager of The REUSE Company
Former Product Manager of RQA and the Systems Engineering Suite
INCOSE CSEP Certified
Graduated in the INCOSE Institute for Technical Leadership
Active contributor to the INCOSE Guide for Writing Requirements
Other certifications: ITIL
Other interests: Project Management, Business Analysis, Risk Management
José Fuentes

3
WEBINARS 2022 The Presenters
Current Position: Key Account Manager of The REUSE Company
Member of the Sales & Consulting Department withinThe REUSE Company
Responsible for the Temperature War Systems Engineering Use Case
Systems Engineering Methodology thesis development
Complete SE Use Case based on the INCOSE 15288 Standard
3 years of experience and supervised training under two members of the
INCOSE Group, ASEP & CSEP
Degree in Computer Science & Engineering
Jose Pereira

4
WEBINARS 2022
Introduction to the speakers
Brief introduction to The REUSE Company
Why textual requirements with Capella?
Demonstration of use cases
Q&A
Contents

5
WEBINARS 2022
The company was
established in 1999
As a spin-off of a
University in Madrid
01 System +
Software
Engineers
Smart combination
between Company
staff and R&D
from Academia
02 Headquarters:
Madrid (Spain)
International offices:
Stockholm (Sweden)
Tokyo (Japan) Delegation
2022 Q4:
USA
Boston
03 To promote a
reusable, scalable and
global solution to a
smart and
interoperable
Systems Engineering
environment, by
offering a semantic
knowledge centric
approach.
04
WHEN WHO WHERE WHY
Introduction to The REUSE Company

6
WEBINARS 2022 Introduction to The REUSE Company
What we do:
The REUSE Company is a tool vendor
specialized in the application of
semantic technologies and artificial
intelligence to improve the
digitalization of the Systems
Engineering life cycle.

7
WEBINARS 2022
QUALITY (ies)
- Quality Management
- Verification &Validation management
- Risks Management
- Smart Authoring
TRACEABILITY
Links and Interoperability –
Transformations –
Change management –
REUSABILITY
- Interoperability
- Retrieval & Archiving
- Adaptability to Existing Toolsets
Knowledge Centric
Systems Engineering (KCSE)
Global Repositories –
Archiving –
Configuration Management –
Introduction to The REUSE Company

Title of the
Section
WHY Textual
Requirements
in Capella
“The system shall…”

9
WEBINARS 2022 What is Capella?
Open-Source solution for Model-based Systems Engineering
Comprehensive, extensible and field-proven MBSE tool and method to successfully
design systems architecture
Main characteristics:
Understand the customer need
Define and share the solution
Ensure engineering-wide collaboration
Early evaluate and justify architectural choices
Prepare and masterV&V
+info: https://www.eclipse.org/capella/

10
WEBINARS 2022 WhyTextual Requirements?

11
WEBINARS 2022
TEXTUAL REQUIREMENTS
Are the HEART of the current
system engineering practices
SOLUTION MODEL
Helps validate FEASIBILITY,
elicit/justify NEW REQUIREMENTS
for the system/subsystems
NEED MODEL
Helps FORMALIZE and
consolidate customer and system
requirements
Textual Requirements and Model Requirements

12
WEBINARS 2022 Textual Requirements and Model Requirements
A model requirement can FORMALIZE a textual requirement
and EXPLICIT its effects and ramifications
Models add RIGOR to need expression / solution description
Models enable AUTOMATED processing

13
WEBINARS 2022 Textual Requirements and Model Requirements
HIGH-LEVEL NEEDS and other expectations (environmental, regulations,
etc.) are easier to express with textual descriptions
Some EXPECTATIONS on a given element at a given engineering level do
NOT require any FORMAL MODELING (which is left to subsystem design)
So, textual form of
needs and
requirements are
not only useful,
but..
FULLY
NECESSARY
Text is normally better for the FIRST INTERACTION with customers and
suppliers
LEGALLY binding DOCUMENTS are normally written in text
Text allows for a much earlier FOCUS on QUALITY (verification of textual
requirements).
Remember: “Quality is everyone’s responsibility” by E. Deming

14
WEBINARS 2022 ConnectingTextual Requirements and Model Requirements
Completeness + Authoring:
Textual Req vs Models
Roundtrip:
Textual Req both sides
Consistency:
Generation:
Textual Req to Models
Transformation:
SysML to Capella
Quality check:
Model quality check
Traceability:

15

16
WEBINARS 2022 Completeness between Requirements and models
Use case #1: Completeness

17
WEBINARS 2022 Completeness between Requirements and models
Use case #1: Completeness between
Requirements and Models
Steps:
1. Use SES ENGINEERING Studio to check
completeness: textual reqs. vs Capella
models
2. This will show that 1 element is missing
3. Open requirements in IBM DOORS
4. Write a new requirement with the RAT –
AUTHORINGTools plug-in
5. Use patterns to follow consistent language
6. Consistency in the definition of the
architecture: textual reqs. vs Capella models
7. Use SES ENGINEERING Studio to check
completeness: now it’s complete

18
Req roundtrip:

19
WEBINARS 2022 Requirements Roundtrip Synchronization
Use case #2:
Round-Trip Synchronization Between Capella &
other RMS (DOORS).
Steps:
1. Right-click on the selected Requirements
Specification.
2. Select the "Synchronization" option within
the RAT section.
3. Define the Source and Target side.
4. Complete connection configuration.
5. Select the operation to be executed for
each requirement.
6. And commit those actions!
For more information, please refer to this Webinar session: https://www.reusecompany.com/webinars/requirements-
authoring-tool-rat-for-capella-the-perfect-way-for-working-with-both-models-and-textual-requirements
Check all the benefits at:
https://www.reusecompany.com/rat-authoring-tools

20
Req roundtrip:
Consistency:

21
WEBINARS 2022 Consistency between Requirements and Models
Use case #3:
Consistency Quality Assessment between
Textual Requirements & Models (inside Capella).

22
WEBINARS 2022 Consistency between Requirements and Models
Use case #3:
Consistency Quality Assessment between
Textual Requirements & Models (inside Capella).
Steps:
1. Right-click on the chosen Requirement(s).
2. Select the “Edit Selected Requirement" option
within the RAT section.
3. The RAT AuthoringWindow will be opened.
4. In the “Metrics Summary” section, the tool
will automatically detect inconsistencies
such as wrong transition, etc.
5. Click on the highlighted quality metric to
obtain more information.
6. Finally, modify accordingly!
For more information, please refer to this Webinar session: https://www.reusecompany.com/webinars/requirements-
authoring-tool-rat-for-capella-the-perfect-way-for-working-with-both-models-and-textual-requirements
Check all the benefits at:
https://www.reusecompany.com/rat-authoring-tools

23
Req roundtrip:
Consistency:
Generation:

24
WEBINARS 2022 Generate Models fromTextual Requirements
Models and texts complement each other :
“The SYSTEMS ENGINEERING SANDWICH” (J. Dick).
Blending both sides helps generate a CONSISTENT AND COMPLETE knowledge base.

25
WEBINARS 2022
Generate Models fromTexts... andTexts from Models!
Generate Models fromTextual Requirements

26
WEBINARS 2022 Generate Models fromTextual Requirements
Use case #4:
Generate Models fromTextual Requirements.
Steps:
1. Open SES ENGINEERING Studio
to connect to both the source
requirements and the target model (empty)
2. Configure the interoperability
task:Transformation fromText to SysML
3. Run the interoperability task
4. Save the newly created objects in both
the database and the target model
5. Generate the block definition diagram
in the model!

27
Req roundtrip:
Consistency:
Generation:
Textual Req to SysML
Transformation:
SysML to Capella

28
WEBINARS 2022 Generate Arcadia Models from SysML Models
Use case #5:
Transform SysML Models to Capella (Arcadia)
Models.
Steps:
1. Open SES ENGINEERING Studio
to connect to both the source SysML Model
and the target Capella Model (empty)
2. Configure the InteroperabilityTask:
"Transformation from SysML to Arcadia"
3. Run the InteroperabilityTask
4. Save the newly created objects in both
the database and the target Capella Model
5. Work inside SES or Capella with your new
model!

29
Req roundtrip:
Consistency:
Generation:
Transformation:
SysML to Capella
Quality check:
Model quality check

30
WEBINARS 2022 Quality checking of Capella Models
"The practical question is how
wrong do they have to be not to
be useful."
George E.P. Box
“Investing on the quality of models
(through early inspections) is key
for ensuring useful models, and
thus, the success of our systems.”
José M. Fuentes

31
WEBINARS 2022
Non-parameterized metrics:
Do not require any parameter (configuration) to be executed.
E.g.: Incorrect spelling in any component description
Parameterized metrics:
Require some kind of parameter (configuration) to be executed.
I.e., these metrics are algorithms that need some parameters to provide
the output.
E.g.: Regular expression pattern check on the component name
It’s mandatory to provide a regular expression to execute the metric
There are optional parameters in all MBSE metrics (parameterized or
non-parameterized):
This is the Filter
To restrict the analysis only on those components of a given type
E.g.:
Description is not empty of the components of type Use_Case
Regular expression pattern on the description of the components
of type Use_Case
Quality checking of Capella Models

32
Super/Sub element
Description:
Checks that model elements of a given type are always owned (contained) / or owns (contains)
elements of another given type
Example of rules based on
this metric:
A Logical System is contained in
at least one Diagram
An Actor should be contained in
at least one Diagram
A state machine without any
state
An empty diagram
An interface without operations

33
Relationship instances
Description:
Given an object (X), computes the number of the
relationship instances of a given type (Y) where X is
involved.
Optional configurations:
• It can be established if X shall play the role of source
(from) in the relationship, target (to), or any of them
• Additionally, the other element in the relationship (Z)
can be checked to have a type or stereotype included in
a list of valid ones.
Example of rules based on this metric:
• An Actor should be associated with, at least, one use
case
• An Actor cannot be associated with another Actor
• A Pin should not be connected directly to a function by
means of an ObjectFlow, it should be connected through
another Pin

34
Use case #6 Quality checking of Capella
Models
Steps:
1. Open SES ENGINEERING Studio and
connect to a Capella Model
2. Assign a set of rules for MBSE
3. Run Correctness checking
4. Show results

35
Req roundtrip:
Consistency:
Generation:
Transformation:
SysML to Capella
Quality check:
Model quality check
Traceability:

36
WEBINARS 2022
Pros
Cons
MUST in COMPLEX and SAFETY CRITICAL projects.
Requested by STANDARDS and GOOD PRACTICES: ISO 26262,
ARP4754…
ProvidesVISIBILITY in COMPLEX projects.
TEDIOUS and MANUAL task.
CONNECTIONS toTOOLS not easily connected to.
Aware of CHANGES and EVOLUTION of project.
Seamless and smart traceability

37
WEBINARS 2022 Seamless and smart traceability

38

39
StR019- The
driver shall be
able to
control the
temperature
of the car.
User01-
Driver: the
person who
drives the
car.
SyR211- The
car shall have
a thermostat.
SyR212- The
car shall
control the
temp…
SyR871- The
thermostat
shall regulate
the
temperature

40
Use case #7: Seamless & SMART
traceability
Steps:
1. Open the SES ENGINEERING
Studio
2. Connect to a requirements
document
3. Connect to a Capella Model
4. Add traces manually
5. Also, the tool automatically suggests
other traces

41
Req roundtrip:
Consistency:
Generation:
Transformation:
SysML to Capella
Quality check:
Model quality check
Traceability:

42
WEBINARS 2022

43
WEBINARS 2022

Connecting Textual Requirements with Capella Models

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Connecting Textual Requirements with Capella Models

Similar to Connecting Textual Requirements with Capella Models (20)

More from Obeo

More from Obeo (18)

Recently uploaded

Recently uploaded (20)

Connecting Textual Requirements with Capella Models