CLOSE ENCOUNTERS BETWEEN REQUIREMENTS AND SYSML EclipseCon France - - PowerPoint PPT Presentation

▶
close encounters between requirements and sysml
SMART_READER_LITE
LIVE PREVIEW

CLOSE ENCOUNTERS BETWEEN REQUIREMENTS AND SYSML EclipseCon France - - PowerPoint PPT Presentation

Oct 09, 2022 191 likes •535 views

CLOSE ENCOUNTERS BETWEEN REQUIREMENTS AND SYSML EclipseCon 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

slide-1
SLIDE 1

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

CLOSE ENCOUNTERS BETWEEN REQUIREMENTS AND SYSML

slide-2
SLIDE 2

| 2 EclipseCon 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/)

slide-3
SLIDE 3

| 4 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSML DIAMGRAMS

SysML Structure Diagram Block Definition Diagram Internal Block Diagram Parametric Diagram SysML Behavior Diagram State Machine Diagram Activity Diagram Use Case Diagram Sequence Diagram SysML Cross-Cutting Diagram Requirement Diagram

slide-4
SLIDE 4

| 6 EclipseCon 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)
slide-5
SLIDE 5

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

slide-6
SLIDE 6

| 8 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

INSTALLING PAPYRUS FOR REQUIREMENTS

slide-7
SLIDE 7

| 10 EclipseCon 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

slide-8
SLIDE 8

| 11

Specification

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

Business Needs-Goals Modeling System Requirements Modeling Preferences Setting Requirements Types Definition

slide-9
SLIDE 9

| 12 EclipseCon 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)

slide-10
SLIDE 10

| 13 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SPECIFICATION: BUSINESS MODELING

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

slide-11
SLIDE 11

| 14 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SPECIFICATION: BUSINESS MODELING

Diagram-Based Form-Based Tree-Based

slide-12
SLIDE 12

| 15 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSTEM REQUIREMENTS

slide-13
SLIDE 13

| 16 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

SYSTEM REQUIREMENTS MODELLING: TABLES

slide-14
SLIDE 14

| 17 EclipseCon 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

slide-15
SLIDE 15

| 20 EclipseCon 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

slide-16
SLIDE 16

| 21 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

IMPORTING AND EXPORTING TO EXTERNAL SOURCES

CSV XLS ReqIf Papyrus for Requirements

slide-17
SLIDE 17

| 22 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

REQUIREMENTS MANAGEMENT (TRACEABILITY)

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

  • ther language) x Requirements
slide-18
SLIDE 18

| 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

slide-19
SLIDE 19

| 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

slide-20
SLIDE 20

| 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

slide-21
SLIDE 21

| 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

slide-22
SLIDE 22

| 27

SysML, generic and customer- defined tables for traceability.

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

slide-23
SLIDE 23

| 28

Traceability contextual tools Based on selected Requirements Related Elements Based on Requirements

REQUIREMENTS MANAGEMENT (TRACEABILITY)

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

slide-24
SLIDE 24

| 30 EclipseCon 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

slide-25
SLIDE 25

| 31 EclipseCon 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

slide-26
SLIDE 26

| 32 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

EVALUATE METRICS

It will be possible to show graphical views

These GUI will be integrated soon

slide-27
SLIDE 27

| 33

Ex., Validate if requirements are satisfied or verified

CHOOSING CONSTRAINTS TO VALIDATE

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

slide-28
SLIDE 28

| 34

VISUALIZATION OF THE RESULTS OF CONSTRAINTS VALIDATION

Warnings/Error signs are displayed on requirements

EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

slide-29
SLIDE 29

| 35 EclipseCon 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

slide-30
SLIDE 30

| 36 EclipseCon France 2016 | Mauricio Alferez and Patrick Tessier

DEMOSTRATION

slide-31
SLIDE 31

| 37 EclipseCon 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)

slide-32
SLIDE 32

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