ecss requirements management system

17
ECSS Requirements Management System MBSE 2021

Upload: others

Post on 14-Jan-2022

10 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: ECSS Requirements Management System

ECSS Requirements Management System

MBSE 2021

Page 2: ECSS Requirements Management System

2©2021 RHEA Group | Public | E-RMS September 15, 2021

About the presenter

Page 3: ECSS Requirements Management System

3©2021 RHEA Group | Public | E-RMS September 15, 2021

The Project

Page 4: ECSS Requirements Management System

4©2021 RHEA Group | Public | E-RMS September 15, 2021

OSMoSE and Space System Ontology(SSO)

• SSO addresses the System aspects of any Space System (i.e. space & ground segment & launcher)

• E-RMS SSO as a UoD

• SSO is agreed within OSMoSE

• Applies OSMoSE ORM Modelling guidelines

exchange

Derivation rules in notes

Concept Custom Properties

Page 5: ECSS Requirements Management System

5©2021 RHEA Group | Public | E-RMS September 15, 2021

Conceptual Data Modeling

• Captures the semantics, i.e. the “WHAT“

• Integrates each stakeholder’s semantics in a global conceptual model solution

• Supports the exchange between stakeholders by

• sub-setting the global conceptual model with the needs of each stakeholder, i.e. producing local views

• enabling exchanges of shared semantics by mapping the stakeholder-specific conceptual views

Page 6: ECSS Requirements Management System

6©2021 RHEA Group | Public | E-RMS September 15, 2021

Conceptual Data Modelling

• Sources → ECSS-D-00B, ECSS Repository, ECSS Steering Board, OSMOSE Models, ECSS Master DB

• Methodology → Fact-Based Modelling → Object Role Modelling (ORM) Technique → NORMA tool

• Working method• Define the UoD to be modelled

• Extract Data Concepts from processes

• Look for examples in ECSS repository

• Model in ORM the involved information and cross-check with existing models (if any)

• Raise questions to ECSS SB

• Update Model, if needed.

• Review model with ESA and Cross-check OSMOSE WG

• Enhance model with metadata (via custom properties) for automatic doc/code generation

Represents Benefits

• Data Relationships• Business Rules• Semantic Checks• Derivation Rules & some calculations

• Automatic Textual verbalization of the model (in natural but formal text)• Glossary management of the schema• Population of the model• Code generation (to logical and physical levels)• Diagrams export

Page 7: ECSS Requirements Management System

7©2021 RHEA Group | Public | E-RMS September 15, 2021

Conceptual Data Modelling

Resulting Models in 34 ORM files:

• ECSS Concepts → 36 root concepts• Some concepts are merged (e.g., DRR, RID, CR)

• Generic shareable entity and value types cross-UoD

• Refactor the M-ST-40 Foundation Model of OSMoSE WG

• All ECSS concepts are instances from Foundation model

• Provide a Version Control Model for OSMoSEaligned with OMG SysML v2. submission

• Conceptual model of the HMI concept

• Conceptual model of a business process workflow

Page 8: ECSS Requirements Management System

8©2021 RHEA Group | Public | E-RMS September 15, 2021

Conceptual Data Modelling

Page 9: ECSS Requirements Management System

9©2021 RHEA Group | Public | E-RMS September 15, 2021

Process Modelling

❑ Goal→ Formalization of processes performed for ECSS doc management

❑ Sources → ECSS-D-00B & Interviews with ECSS Steering Board

❑ Number of Processes → 24 High Level Processes

❑ Methodology:▪ Analysis of the D-00 Document▪ Cross-check the process diagram (sub-chapter 2) against description (sub-chapter 3)▪ Raise inconsistencies, missing information, ambiguities ▪ Model the understanding using BPMN✓ Identify conceptual data objects and relations → They will have to be modelled in ORM for the model integration✓ Model the process with different granularity levels → From black box approach to atomic ‘tasks’✓ Identify ‘repeatable’ tasks between processes and define ‘reusable’ parametric tasks

▪ Discuss the model with the ECSS SB▪ Update the model, if needed.

❑ Conceptualize the definition of processes → ORM Model of the applicable BPMN Element Subset

❑ Results❑ 60 Raised CR ❑ 77 BPMN Models for 24 processes ❑ Model Sample Population of the Drafting Process in ORM compliant with associated BPMN models

Page 10: ECSS Requirements Management System

10©2021 RHEA Group | Public | E-RMS September 15, 2021

Process Modelling

Page 11: ECSS Requirements Management System

11©2021 RHEA Group | Public | E-RMS September 15, 2021

Process Modeling

Page 12: ECSS Requirements Management System

12©2021 RHEA Group | Public | E-RMS September 15, 2021

Orthogonal Model Consistency

❑ BPMN Subset modelled

in NORMA• User Tasks can be performed through HMIs

❑ HMIs modelled as well in NORMA• Independent on the impl. Technology• Using custom code generation algorithms for

data types as in CDP4/COMET

❑ Objects involved in the process/HMI also in the ORM model

BPMN ORM

DBDoc

Specs

HMI

gen

erat

es

populates

sources sources

Req Spec

Ontology

Page 13: ECSS Requirements Management System

13©2021 RHEA Group | Public | E-RMS September 15, 2021

Orthogonal Model Consistency: Link points

*Not real mockup of the project

Page 14: ECSS Requirements Management System

14©2021 RHEA Group | Public | E-RMS September 15, 2021

Requirement Specification

Spec Format

Model Format

Textual Format

generates

docTemplates

populates

ECSS and data req.

Specification req.

System req.

Page 15: ECSS Requirements Management System

15©2021 RHEA Group | Public | E-RMS September 15, 2021

ConclusionsChange Requests

Models

SW Development

PHASE-1

PHASE-2

Specifications & TN

SW Deploy & Distribute

Population Samples

SW Testing

Page 16: ECSS Requirements Management System

16©2021 RHEA Group | Public | E-RMS September 15, 2021

Page 17: ECSS Requirements Management System

THANK YOU