integrated requirements engineering and development of … · 2019-03-26 · requirements...

V1.0 | 2019-03-20

PREEvision User Day 2019

Integrated Requirements Engineering and Development of Specifications

RELEASED

u Integration Levels

Out of The Box Functionalities and Processes

Change Management with Internal Experts

Change Management with External Partners

Agenda

2

Evolution of Requirement Engineering Tools

Integration Levels

File based

Purely textual

No Traceability

Standalone Tool

Structured Requirements

Internal Linking & Tracing

Linking to other tools or databases not reliable and not possible on atomic basis

Tool Environment

Linking & Tracing to e.g. Test tools

Integration via OLSC possible but relations across database boundaries cannot be versioned and archived.

Fully Integrated

Common database allows links on atomic basis

No tool borders

Versionable and reliable

Consistent traceability

File based, only lightly

coupled

3

Level 1: Purely Textual

Integration Levels

Purely textual in PREEvision?

u Model based

Purely textual

4

Level 1: Purely Textual

Integration Levels

Purely textual in PREEvision?

u Model based

u Formulized language for describing data (Metamodel), information is clear, structured and consistent

u Different Requirement Types (Definition, Information, …)

u Consistency and Online Checks

u Lifecycles

u Version Management

u True Reuses

u Role and Right Management

u LibO Formatting & Reporting

u Use Case Diagrams

Purely textual

5

Level 2: Usage of Requirements Links

Integration Levels

Link requirements among each other

u Different Link Types (trace, refine,…)

u Better Traceability

u Better Understanding

Requirement Links

Purely textual

Natural border of standalone tools

6

Level 3: Usage of Mappings

Integration Levels

Purely textual

Requirement Links

Mappings

Linking the Model

u Type safe

u Basis for analysis, e.g. coverage analysis

u Consistent traceability through the model

u Simple navigation

u Simplification of understanding, e.g. by usage in diagrams

u Easy creation via drag&drop in Model View or in Table Editors

7

Level 4: Usage of Variants

Integration Levels

Purely textual

Requirement Links

Variants

Mappings

Make it context dependent

u Determine variants, e.g. relevant series for a requirement directly in the Requirement Text Editor

8


Integration Levels

9


Integration Levels

Purely textual

Requirement Links

Variants

Mappings

Make it context dependent

u Determine variants, e.g. relevant series for a requirement directly in the Requirement Text Editor

u No need to create an independent requirement for each variant as information is separated

u Activation of a variant highlights requirements associated to the variant in the specification editor

u Generation of variant sensitive reports and specifications

10

Level 5: Usage of Placeholders

Integration Levels

Purely textual

Requirement Links

Variants

Mappings

Placeholder

Reference the model

u Referencing any attribute of any artifact in the model via drag&drop into the rich text.

u DnD support from Model View, Tables and Diagrams

u Referencing of diagrams, charts and tables

u Placeholders are kept always up to date

u Relevant attributes can be defined for a perspective

u Copy and paste support with automatic mergeof already existing placeholders

11

Level 6: PREEvision

Integration Levels

Purely textual

Requirement Links

Variants

Mappings

Placeholder

Model is the specification

The model is the requirement specification

u Get along without requirement artifacts at all – use instead the model as single point of truth!

u Via the ReqIF Export any artifact with any attribute from any layer can be used for the specification document.

Goal might not be completely reachable due to standards, laws, company internal or non functional requirements used in the specification

12

Integration Levels

13

Data Management, Collaboration, Platform Management, Safety, Change Management

Summary

Integration Levels

Requirements Engineering and Management

Test Engineering and Management

FunctionalArchitectureDesign

SOADesign

SoftwareDesign

PhysicalArchitectureEvaluation

PhysicalArchitectureDesign

PhysicalSystemDesign

COMDesign

WH SeriesDesign

WHArchitectureDesign

REQ-X Mapping

Subject under TestSpecified Artifact under Test

14

Integration Levels

u Out of The Box Functionalities and Processes



Agenda

15

Data Management, Collaboration, Platform Management, Safety, Change Management

Processes


Requirements Engineering and Management

Test Engineering and Management

Specification of Tests

Design & Implementationof Tests

Execution & Documentationof Tests

Evaluation & Analysisof Test Results

Planningof Tests

Template Definition

Agreementwith Supplier

System Specification

Component Specification

16

Requirements Management: Involved Roles

Out of The Box Functionalities and ProcessesLegend:

Responsible Role

Supporting Role

Component Responsible

System Responsible

Test Engineer

Architect

17

Component specification

B


A

Integrated Requirements Process


Template

V1

System specification

Instantiation

Reuse & Copy

Attributes

Structure

Syste

m a

nd C

om

ponent

Tem

pla

te

V1

V1 V1

PL PL PL PL

18



Template System specification


AV1 V1

V1


B

V1

Instantiation

System provides content

Reuse & CheckinLinking between Component and

System

Reuse & Copy

Attributes

Structure

PL PL PL PL

19





AV1 V1

V1


B

V1

V2

V2

Merge & Updatekeep links

Instantiation


Reuse & CheckinLinking between Component and

System

Reuse & Copy

Attributes

Structure

Changes

20





AV1 V1

V1


B

V1

V2

V2

Instantiation

Reuse & Copy

Attributes

Structure

Changes

Merge & Updatekeep links

? Change details

set Lifecycle State

21

u Recognition of an changed artifact either by

u revision number of an updated requirement or a

u lifecycle state or by

u change marker symbol (Model View, Table Editor or Property Editor)

u Change details for an artifact can be accessed on level of attribute changes in the Change History View

Change Management


V2

? Change details

22

Introduction of Change Logs

Support for recording, analysis and display of relevant changes

u Changes are documented via a ticket

u Relevant changes can be defined by profiles (Meta Classes and Meta Attributes)

u On commit of an relevant artifact a ticket can be selected, the changed artifacts are associated, change log is created

u Change History allows to view the recorded changes regarding

u change interval

u relevant attributes

u Change logs can be accessed and can be displayed in Table Editors for showing relevant changes (from viewpoint of change order and viewpoint of changed artifact)

Outlook Change Management


Deliver relevant change details tocollogues or suppliers

23

Lifetime of specifications


Specification versions

Released Specification

V1 V3 V4

Test Engineer Component Responsible

Suppliers

In t

est

V2

In w

ork

In a

gre

em

ent

24

Integration Levels


u Change Management with Internal Experts


Agenda

25

Internal Review


System specification


A

V1

V1


V2

V2


Changes

Linking between Component and

System

Component ResponsibleSystem Responsible

26

Changes

Internal Review Process


System Specifications

Component Specifications

System 1 Component 1

V1V1

Component 1

InternalReview and Vote

Agreements between OEM and Supplier

V1

Integration of Remarks

and

Update of Specifications

Component 1

V2

Assessment

Component 1

V1

27

Review and Vote


28

u Comfortable One-clickinitialization is provided

u Automatic generation of theagreement structure

Review specifications


Component Responsible

System Responsible

Task Overview Table

Agreement Task: System 1

Agreement Task: Component 4


Task Overview Table


Agreement Task System 1

Agreement Task System 129

Integration Levels



u Change Management with External Partners

Agenda

30

Agreements with Suppliers


Specification versions

Released Specification

V1 V3 V4

Test Engineer Component Responsible

Suppliers

In t

est

V2

In w

ork

In a

gre

em

ent

RequirementInterchangeFormat 31

System Specifications

Component Specifications

System 1 Component 2

Agreements between OEM and Suppliers


V1 V1

Supplier

InternalReview and Vote

Agreements between OEM and Supplier

Component 2

Export/Import via

SPEC

Assessment

by OEM

Component 2

V1

Changes

Integration of Remarks

and

Update of Specifications

Component 2

V2

32

Exchange of Agreements between OEM and Supplier via ReqIF


Only export supported

33

u Simple initiation of „Specification Review“ using context menu

Initiate Review: Create a Specification Review


Import ReqIF filewith review content

Export the Specificationprepared for review

Review Spec

SupplierOEM OEM

Initiate Review Spec

OEM

34

Initiate Review: Create a Specification Review for ReqIF export


Import ReqIF filewith review content


Review Spec

SupplierOEM OEM

Initiate Review Spec

OEM

35

Export ReqIF file with review content


ReqIF

Initiate ReviewImport ReqIF filewith review content

ReviewSpec Spec

SupplierOEM OEM

Agreement Export


OEM

36

u In 3rd Party Tool supplier can:

u set his status

u add his review comments

u export ReqIF with enriched agreement information

Review in 3rd Party Tool




Spec

OEMOEM OEM

Review Spec

Supplier

37

Import ReqIF file with review content




Spec

OEMOEM OEM

Agreement Import

Only ImportSupplier Statusand Comments

Review Spec

Supplier

ReqIF

38

Small Example




Spec

OEMOEM OEM

Review Spec

Supplier

39

© 2019. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 | 2019-03-20

Authors:Robert RotterDr. Nico AdlerVector Germany

For more information about Vectorand our products please visit

www.vector.com

http://www.vector.com/

integrated requirements engineering and development of … · 2019-03-26 · requirements...

Documents