EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

CLOSE ENCOUNTERS BETWEEN REQUIREMENTS AND SYSML

| 2EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

WHAT WE DO

Papyrus REQ = Papyrus for Requirements

A set of Eclipse plugins for model-based requirements engineering integrated in the Papyrus platform (http://www.eclipse.org/papyrus/)

| 4EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSML DIAMGRAMS

SysML Structure Diagram

Block DefinitionDiagram

Internal Block Diagram

ParametricDiagram

SysML Behavior Diagram

State Machine Diagram

ActivityDiagram

Use Case Diagram

SequenceDiagram

SysML Cross-CuttingDiagram

RequirementDiagram

| 6EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

ANATOMY OF THE «REQUIREMENT» CONCEPT

Requirement concept

defined in a Profile

The Requirement concept

used by the Users

« Requirement » properties: An identifier

A text requirement description

A name (inherited from Class defined in UML)

| 7EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

• Papyrus UML

For developers:

http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/neon

For users:

Papyrus 2.0 Neon - Next release.

• SysML 1.1 (Included by Default) or

• SysML 1.4 (Need to be installed as an “Additional Papyrus

Component”)

INSTALLATION REQUIREMENTS

Figure 1. Installing SysML 1.4

| 8EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

INSTALLING PAPYRUS FOR REQUIREMENTS

| 10EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

MAIN PROCESSES IN EACH DEVELOPMENT AREA

Management / Traceability

Specification Analysis

Validation and Verification

Check Rules

Trace

Elements

Evaluate Metrics

Requirements

Types Definition

Preferences

Setting

Re/Import/Export

Requirements

Generate

Reports

Business Needs-

Goals Modeling

System

Requirements

Modeling

| 11

Specification

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

Business Needs-Goals

Modeling

System Requirements

Modeling

Preferences Setting

Requirements Types

Definition

| 12EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

BUSINESS NEEDS-GOALS MODELING

Papyrus BMM editor

A Business Motivation Model (BMM) v1.3

captures business requirements and

justifies why business want to do something,

what they aim to achieve, how they plan to

get there, and how they plan to assess the

results.

BMM Overview (Figure taken from: http://www.omg.org/spec/BMM/1.3)

| 13EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SPECIFICATION: BUSINESS MODELING

BMM Overview (Figure taken from: http://www.omg.org/spec/BMM/1.3)

| 14EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SPECIFICATION: BUSINESS MODELING

Diagram-Based

Form-Based

Tree-Based

| 15EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSTEM REQUIREMENTS

| 16EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSTEM REQUIREMENTS MODELLING: TABLES

| 17EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

CHANGE PREFERENCES SETTINGS

These

preferences

help you to

create these

IDs

These

preferences

help you to

create these

IDs

| 20EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

MAIN PROCESSES IN EACH DEVELOPMENT AREA

Management / Traceability

Specification Analysis

Validation and Verification

Check Rules

Trace

Elements

Evaluate Metrics

Requirements

Types Definition

Preferences

Setting

Re/Import/Export

Requirements

Generate

Reports

Business Needs-

Goals Modeling

System

Requirements

Modeling

| 21EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

IMPORTING AND EXPORTING TO EXTERNAL SOURCES

CSV

XLS

ReqIf

Papyrus for Requirements

| 22EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

REQUIREMENTS MANAGEMENT (TRACEABILITY)

TracedTo Matrix –Model Elements (EX. From BMM or Any

other language) x Requirements

| 23

DerivedFrom Matrix –Requirements x Requirements

The table is synchronized and allows creating and

deleting “derivedReqt” Links

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 24

RefinedBy – Requirements x Requirements

The table is synchronized and allows

creating and deleting “Refine” Links

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 25

Requirements Management (Traceability)

Satisfy Matrix – Model Elements x Requirements

The table is synchronized and allows

creating and deleting “Satisfy” Links

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 26

VerifiedBy Matrix – Model Elements (“Test Case”) x Requirements

The table is synchronized and allows

creating and deleting “Verify” Links

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 27

SysML, generic and customer-defined tables for traceability.

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 28

Traceability contextual tools

Based on selected Requirements Related Elements

Based on Requirements

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 30EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

MAIN PROCESSES IN EACH DEVELOPMENT AREA

Management / Traceability

Specification Analysis

Validation and Verification

Check Rules

Trace

Elements

Evaluate Metrics

Requirements

Types Definition

Preferences

Setting

Re/Import/Export

Requirements

Generate

Reports

Business Needs-

Goals Modeling

System

Requirements

Modeling

| 31EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

EVALUATE METRICS

Ex. Calculate the number of satisfied/Unsatisfied requirements using a model

conforming to the Structured Metrics Meta-model (SMM)

Possibility to compute your own metrics by using SMM Models

Default and embedded metrics

User-defined metrics

| 32EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

EVALUATE METRICS

It will be possible to show graphical viewsThese GUI will be

integrated soon

| 33

Ex., Validate if requirements are satisfied or verified

CHOOSING CONSTRAINTS TO VALIDATE

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 34

VISUALIZATION OF THE RESULTS OF CONSTRAINTS

VALIDATION

Warnings/Error signs are displayed on requirements

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

| 35EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

MAIN PROCESSES IN EACH DEVELOPMENT AREA

Management / Traceability

Specification Analysis

Validation and Verification

Check Rules

Trace

Elements

Evaluate Metrics

Requirements

Types Definition

Preferences

Setting

Re/Import/Export

Requirements

Generate

Reports

Business Needs-

Goals Modeling

System

Requirements

Modeling

| 36EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

DEMOSTRATION

| 37EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

• Change the strategy to create new requirements IDs by reusing

ReqCycle.

• Use ReqCycle for linking requirements to code (ex. In a Unit Test “this

test verifies this requirement”).

• Link OSLC (Open Services for Lifecycle Collaboration) to support

interoperability between tools

• Semi-formalize requirements using templates

• Integrate requirements types libraries according to different types of

domains

FUTURE WORK (LINKS WITH OTHER ECLIPSE TOOLS)

Commissariat à l’énergie atomique et aux énergies alternatives

Institut List | CEA SACLAY NANO-INNOV | BAT. 861 – PC142

91191 Gif-sur-Yvette Cedex - FRANCE

www-list.cea.fr

Établissement public à caractère industriel et commercial | RCS Paris B 775 685 019

Thank

you