soqrates.eurospi.net A practical View on...

http://soqrates.eurospi.net

[email protected]

A practical View on Traceability-

Definition and Implementation of a Model-based Approach


[email protected]

A Practical View on TraceabilitySoQrates AK Traces

Slide: 2

Workshop Agenda

From Topic

09:00 Welcome & Introduction

09:20Presentation “Automated Traceability Assessment through Augmented Lifecycle Space”

10:00 Questions & Expectations

10:10Presentation of the Meta Model, Engineering Model and Product Model

10:40 Coffee break

11:00 Explanation exercise 1 "Greenhouse" for group work

11:15 Group work exercise 1 "Greenhouse"

12:15 Presentation of example 1 "Greenhouse"

12:30 Lunch


[email protected]


Slide: 3

From Topic

14:00 Explanation exercise 2 "Greenhouse" for group work

14:15 Group work exercise 2 "Greenhouse"

15:15 Presentation of example 2 "Greenhouse"

15:30 Presentation of the Greenhouse example with a tool

16:00 Coffee break

16:30 Demonstration of "SoQrates Product Editor" (SPEd)

16:45 Discussion, Wrap up and Feedback

17:30 End

Workshop Agenda


[email protected]

Introduction & Motivation for Traceabilityby SoQrates AK Traces


[email protected]


Slide: 5

SoQrates Working Group “Traces”Goals

• Efficient implementation of traceability and consistency required by different standards

• Transparent activities between the engineering disciplines• Managed hierarchies in complex products• Platform development with reusable components • Efficient product variant management• Veritable increase of quality, safety and security• Proof of concept with best practice examples


[email protected]


Slide: 6

“Traceability” helps you to trace all relevant data to a specific (development) information.

Bilateral Traceability means that links between elements of the different development phases, e.g. system requirements vs. system architectural design, can be traced in both directions.

In ManagementProcesses

… will be part of release XY

In EngineeringVertical

… will be detailed in the software design

In EngineeringHorizontal

… will be verified by the

test case

e.g.: This Software requirement…

What is the meaning of “Traceability”?


[email protected]


Slide: 7

What is the difference between “Traceability” and “Consistency”?

Traceability (ISO/IEC/IEEE 24765, Automotive SPICE V3.0)

The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another.

Consistency (Automotive SPICE V3.0)

Consistency addresses content and semantics and ensures that work products are not in contradiction to each other. Consistency is supported by bidirectional traceability.


[email protected]


Slide: 8

Traceability in StandardsAutomotive SPICE® Version 2.5


[email protected]


Slide: 9

Traceability in Standards Automotive SPICE® Version 3.0

Source: Automotive SPICE® PAM v3.0, July 16th, 2015, © VDA QMC


[email protected]

SoQrates Traces Model


[email protected]


Slide: 11

• An established traceabilitygives sustainable benefits

• Traceability is required byseveral standards

• Traceability is not neededonly for its own sake

• Traceability causes lots of painin the realization

Traces ModelIntroduction

• Thousands of requirements• Hundreds of architecture

elements• Thousands of test cases• Thousands of links for

traceability• Several products or product

variants

Traces model for reducing the effort of creating and maintaining traceability


[email protected]


Slide: 12

Traces ModelContents

• Meta Model• Engineering Model• Product Model• Example “Greenhouse”


[email protected]


Slide: 13

Meta Model

class Meta Model

ItemGroup

- type: ItemType

A

SingleItem

- type: ItemType

A

WorkProduct

- type: ItemType

A

«enumeration»ItemType

Requirement Architecture Implementation Test Specification Test Execution

A

Same type

Bidirectional traceability to single items of different ItemTypes.

ItemGroup may be structured in different hierarchies for each ItemType.

Bidirectional traceability to single items of same ItemTypes.

0..*

1

1..*

1

1..*

1


[email protected]


Slide: 14

Engineering Model - Engineering Disciplines Requirements Engineering

class Requirements Model

Requirements Engin.

Requirement

Requirements Specification

Requirements Group

WorkProduct

- type: ItemType

ItemGroup

- type: ItemType

SingleItem

- type: ItemType

ENG.2.BP6ENG.4.BP6

1..*«indirect»

1

«instantiate»

«instantiate»

0..*

1

1..*

1..*

1..*

1

1..*

1

«instantiate» 0..*

1


[email protected]


Slide: 15

Engineering Model - Engineering Disciplines Architecture Design

class Architecture Model

Architectural Design

Architecture Element

Architecture

Architecture Component

WorkProduct

- type: ItemType

ItemGroup

- type: ItemType

SingleItem

- type: ItemType

0..*

1

1..*

1

«instantiate»

0..*

1

«instantiate»

«instantiate»

1..*«indirect»

1

ENG.5.BP10

1..*

1..*

1..*

1


[email protected]


Slide: 16

Engineering Model - Engineering Disciplines Implementation

class Implementation Model

Implementation

Implementation System

Implementation Unit

Implementation Component

WorkProduct

- type: ItemType

ItemGroup

- type: ItemType

SingleItem

- type: ItemType

1..*

1..*

1..*

1

«instantiate»

1..*

1

1..*«indirect»

1

0..*

1 0..*

1

«instantiate»

«instantiate»


[email protected]


Slide: 17

Engineering Model - Engineering Disciplines Test Engineering

class Test Engineering Model

Test Engineering

Test Case

Test Case Group

Test Specification WorkProduct

- type: ItemType

ItemGroup

- type: ItemType

SingleItem

- type: ItemType

0..*

1

1

1..*

1..*

1..*

«instantiate»

1..*

1

«instantiate»

«instantiate» 0..*

1

1..*«indirect»

1


[email protected]


Slide: 18

Engineering Model - Engineering Disciplines Test Execution

class Test Execution Model

Test Execution

Test Report

Test Report Group

Test Case Result

WorkProduct

- type: ItemType

ItemGroup

- type: ItemType

SingleItem

- type: ItemType

«instantiate»

1..*

1

1..*«indirect»

1

0..*

10..*

1

«instantiate»

«instantiate»

1..*

1..*

1..*

1


[email protected]


Slide: 19

Engineering Model Engineering Disciplines

class Engineering Disciplines


+ Architecture+ Architecture Component+ Architecture Element

A

Implementation

+ Implementation System+ Implementation Component+ Implementation Unit

A

Requirements Engin.

+ Requirements Specification+ Requirements Group+ Requirement

A

Test Engineering

+ Test Specification+ Test Case Group+ Test Case

A

Test Execution

+ Test Report+ Test Report Group+ Test Case Result

A

The base practices for bilateral traceablity of Automotive SPICE version 2.5 are indicated.

ENG.5.BP10

ENG.7.BP7ENG.9.BP7

ENG.2.BP6ENG.4.BP6

ENG.6.BP8

ENG.3.BP6ENG.4.BP7ENG.5.BP9

ENG.6.BP10

ENG.6.BP9

ENG.8.BP5ENG.10.BP5


[email protected]


Slide: 20

Engineering Model - Engineering LayersProduct Layer

class Product Layer

Requirements Engin.

A


A

Implementation

A

Test Engineering

A

Test Execution

A


A

Architecture

A


A

Test Specification

A

Test Report

A

ENG.8.BP5ENG.10.BP5

ENG.6.BP9

ENG.7.BP7ENG.9.BP7

ENG.6.BP10


ENG.5.BP10ENG.6.BP8

ENG.2.BP6ENG.4.BP6


[email protected]


Slide: 21

Engineering Model - Engineering LayersReusability Layer

class Reusability Layer

Requirements Engin.

A


A

Implementation

A

Test Engineering

A

Test Execution

A


A

Requirements Group

A


A

Test Case Group

A

Test Report Group

A

0..*

1


ENG.5.BP10ENG.6.BP8

0..*

1

ENG.6.BP10

0..*

1

0..*

1

ENG.2.BP6ENG.4.BP6

ENG.8.BP5ENG.10.BP5

ENG.6.BP9

ENG.7.BP7ENG.9.BP7

0..*

1


[email protected]


Slide: 22

Engineering Model - Engineering LayersTraceability Layer

class Traceability Layer

Requirements Engin.

A


A

Implementation

A

Test Engineering

A

Test Execution

A

Requirement

A


A

Implementation Unit

A

Test Case

A

Test Case Result

A

ENG.8.BP5ENG.10.BP5

ENG.2.BP6ENG.4.BP6

1..*

1..*

1..*

1..*ENG.7.BP7ENG.9.BP7

1

1..*

1 1..*

1

1

ENG.5.BP10


ENG.6.BP9ENG.6.BP10

ENG.6.BP8

1

1..*


[email protected]

Product Model


[email protected]


Slide: 24

Product Model Meta Model ProductComponent

class Meta Model

ItemGroup

- type: ItemType

A

SingleItem

- type: ItemType

A

WorkProduct

- type: ItemType

A

«enumeration»ItemType

Requirement Architecture Implementation Test Specification Test Execution

A

ProductComponent

A

Each type

Same type

Bidirectional traceability to single items of different ItemTypes.

ItemGroup may be structured in different hierarchies for each ItemType.

Bidirectional traceability to single items of same ItemTypes.

0..*

1

1..*

1

N

Collection

1

1..*

1


[email protected]


Slide: 25

Product Model Product Component View

class Product Component

ProductComponent

A

Requirements Group

A

Requirement

A


A


A


A

Implementation Unit

A

Test Case Group

A

Test Case

A

Test Report Group

A

Test Case Result

A

A product component should not contain product components

0..1

1..*

1

1..*

0..*

1

0..1

1..*

1

1..*

1..*

1

1..* 1..*

0..1

1..*

1..*

1

1..*

1..*

1..*

1

0..1

1..*

0..*

1

1 1

1

1..*

0..*

1

1..*

1 0..*

10..1

1..*

1

1..*

0..*

1


[email protected]


Slide: 26

Product ModelProduct View

class Product Model

Product

A


A

Architecture

A


A

Test Specification

A

Test Report

A

Requirements Group

A

Requirement

A


A


A


A

Implementation Unit

A

Test Case Group

A

Test Case

A

Test Report Group

A

Test Case Result

A

1

1..*

1 1

1

1..*

1..*

1

1

1

1..*

1

0..*

11..*

«indirect»1

1

1..*

1

1

0..*

1

1

1

1..*

1

1..*

1

1

1

0..*

1

1

1

1..*«indirect»

1

1

1..*1..*

1..*

0..*

11..*

«indirect»1

1..* 1..*

0..*

11..*

«indirect»

1

1..*«indirect»

1


[email protected]


Slide: 27

Product ModelProduct Development with Product Components

class Multi Product Development

Product

A

ProductComponent

A

Portfolio

A

Product Component Collection

A


A

Architecture

A


A

Test Specification

A

Test Report

A

*

1

1

1

1

11..*

1

1

1 1

1

1

1

1..*

1


[email protected]


Slide: 28

Product ModelProduct Components (only Requirements)

class Multi Product Dev elopment Requirement

Product


Requirements Group

ProductComponent

Requirement

Portfolio Product Component Collection

0..1

1..*

*

1

1..*«indirect»

1

1..*

1

1..*

1

1..*

1

1

1

0..*

1


[email protected]


Slide: 29

Product ModelProduct Components

class Product Dev elopment (complete)

Portfolio

A

Product

A


A


A

Architecture

A


A

Test Specification

A

Test Report

A

Requirements Group

A


A


A

Test Case Group

A

Test Report Group

A

ProductComponent

A

Consistent subsetOverall collection

Requirement

A


A

Implementation Unit

A

Test Case

A

Test Case Result

A

1..*

«indirect»

1

1

1..*

1..*

1

1

1

1..*

«indirect»1

1 1

0..*

1

1..*

«indirect»

1

1

1 1

1

0..*1

0..1

1..*

1

1

0..*1

1..*

1..*

1..*

«indirect»

1

1..* 1..*

1..*

1

1..*

«indirect»

1

0..1

1..*0..1

1..*

1..*

1

0..1

1..*

0..*1

1..*

1

1

1..*

1

1

*

1

1 1..*

0..*1

1..*

1

0..1

1..*

1..*

1

1

1..*


[email protected]


Slide: 30

Traces Model Summary

• Partitioning of a product into product components• Each product component is composed of the items for all

engineering disciplines– Requirements– Architecture– Implementation– Test Specification– Test Execution

• Each product component contains the traceability between all items of the engineering disciplines


[email protected]

Exercise 1 “Greenhouse”


[email protected]


Slide: 32

Exercise 1 “Greenhouse“

object Example Greenhouse


[email protected]


Slide: 33

Exercise 1 “Greenhouse” Product Component View


ProductComponent

A

Requirements Group

A

Requirement

A


A


A


A

Implementation Unit

A

Test Case Group

A

Test Case

A

Test Report Group

A

Test Case Result

A


0..1

1..*

1

1..*

0..*

1

0..1

1..*

1

1..*

1..*

1

1..* 1..*

0..1

1..*

1..*

1

1..*

1..*

1..*

1

0..1

1..*

0..*

1

1 1

1

1..*

0..*

1

1..*

1 0..*

10..1

1..*

1

1..*

0..*

1


[email protected]


Slide: 34

Exercise 1 “Greenhouse“Group Work

• Specify your product greenhouse

• Specify product components of the greenhouse

• Specify the requirements, architecture and test cases for one product component of the greenhouse

• Specify the bilateral traceability between the items



ProductComponent

A

Requirements Group

A

Requirement

A


A


A


A

Implementation Unit

A

Test Case Group

A

Test Case

A

Test Report Group

A

Test Case Result

A


0..1

1..*

1

1..*

0..*

1

0..1

1..*

1

1..*

1..*

1

1..* 1..*

0..1

1..*

1..*

1

1..*

1..*

1..*

1

0..1

1..*

0..*

1

1 1

1

1..*

0..*

1

1..*

1 0..*

10..1

1..*

1

1..*

0..*

1


[email protected]

Example 1 “Greenhouse”


[email protected]


Slide: 36

Example 1 “Greenhouse”Product Components for “Summerseason”

cmp Greenhouse Summerseason

LowcostTemperatureSensorLowcost

Temperature Sensor

LowcostTemperatureSensor

WindowControl

Window with Motor

WindowControl

Green House Frame

ECU Summerseason

TemperatureSensorControl

WindowControl


[email protected]


Slide: 37

Example 1 “Greenhouse”Electronic Control Unit “Summertime”

cmp ECU Summerseason

ECU Summerseason

WindowControl


Touch-Screen

Microcontroller Window Driv er


[email protected]


Slide: 38

Example 1 “Greenhouse” Product Component ECU Summertime

object Product Component ECU Summerseason

r_ECU Summerseason: Requirements Group

a_ECU Summerseason:


s_ECU Summerseason: Test

Case Group

x_ECU Summerseason: Test

Report Group

i_ECU Summerseason: Implementation

Component

ECU Summerseason: ProductComponent

Touch-Screen: Architecture Element

Temperature Sensor Interface: Requirement

Display Temperature: Requirement

Threshold Values: Requirement

Window Control Interface : Requirement

Window Driver: Architecture Element

Microcontroller: Architecture Element

Greenhouse Components: Product Component Collection

Microcontroller: Implementation Unit

Window Driv er: Implementation Unit

Display Messages: Requirement

Input Dev ive: Requirement

Microcontroller: Requirement

Temperature Interface: Architecture Element

Touch Screen: Implementation Unit

Start Up: Test Case

Print: Test Case

Read: Test Case

I2C Input: Test Case

Output Current: Test Case

Start Up: Test Case Result

Print: Test Case Result

Read: Test Case Result

I2C Input: Test Case Result

Output Current: Test Case Result


[email protected]

Exercise 2 “Greenhouse”


[email protected]


Slide: 40

Exercise 2 “Greenhouse“Group Work

• Identify a variant of your greenhouse

• Identify the product components of the greenhouse variant

• Associate all identified product components to the variants of the greenhouse respecting reusability

• Was the decomposition of your initial greenhouse adequate for reusability?

obj ect Example Greenhouse


[email protected]

Example 2 “Greenhouse”


[email protected]


Slide: 42

Example 2 “Greenhouse”Product Components for “Wintertime”

cmp Greenhouse Wintertime

WindowControl

Window with Motor

WindowControl

HeaterControl

Heater

HeaterControl

Green House Frame

PreciseTemperatureSensorPrecise

Temperature Sensor

PreciseTemperatureSensor

ECU Wintertime

HeaterControl


WindowControl


[email protected]


Slide: 43

Example 2 “Greenhouse” Portfolio


Greenhouse Portfolio: Portfolio

Greenhouse Summerseason: Product

(from Portfolio)

Greenhouse Wintertime: Product

(from Portfolio)


[email protected]


Slide: 44

Example 2 “Greenhouse” Product Components

object Greenhouse Portfolio

ReUseGreenhouse Summerseason:

Product



ECU Wintertime: ProductComponent

Lowcost Temperature Sensor: ProductComponent

Greenhouse Frame: ProductComponent

Window with Motor: ProductComponent

Precise Temperature Sensor: ProductComponent

Heater: ProductComponent

Greenhouse Portfolio: Portfolio


[email protected]


Slide: 45

Example 2 “Greenhouse” Product Component Collection

object Product Component Collection Greenhouse



Window w ith Motor: ProductComponent




Lowcost Temperature Sensor:

ProductComponent

Precise Temperature Sensor:

ProductComponent

r_Greenhouse Frame: Requirements Group

r_Window with Motor: Requirements Group

r_Lowcost Temperature Sensor: Requirements Group


a_Greenhouse Frame: Architecture Component

i_Greenhouse Frame: Implementation

Component

s_Greenhouse Frame: Test Case Group

x_Greenhouse Frame: Test Report Group

a_Window with Motor: Architecture Component

a_ECU Summerseason:


a_Lowcost Temperature Sensor:


i_Window with Motor: Implementation

Component

s_Window with Motor: Test Case Group


Case Group

s_Lowcost Temperature Sensor:

Test Case Group

x_Lowcost Temperature Sensor:

Test Report Group


Report Group

x_Window with Motor: Test Report Group


Component

i_Lowcost Temperature Sensor:


r_Heater: Requirements Group

a_Heater: Architecture Component

i_Heater: Implementation

Component

s_Heater: Test Case Group

x_Heater: Test Report Group

r_ECU Wintertime: Requirements Group

a_ECU Wintertime: Architecture Component

s_ECU Wintertime: Test Case Group

x_ECU Wintertime: Test Report Group

i_ECU Wintertime: Implementation

Component

r_Precise Temperature Sensor: Requirements

Group

a_Precise Temperature Sensor: Architecture

Component

s_Precise Temperature Sensor: Test Case

Group

x_Precise Temperature Sensor: Test Report

Group

i_Precise Temperature Sensor:



[email protected]


Slide: 46

Example 2 “Greenhouse” Product Components for Product Summerseason

object Greenhouse Summerseason Product Component


(from Product Component Collection)



Window w ith Motor: ProductComponent




Lowcost Temperature Sensor:

ProductComponent


Greenhouse Summerseason:

Product

(from Portfolio)


[email protected]


Slide: 47

Example 2 “Greenhouse” Product “Summerseason”

object Greenhouse Summerseason

Greenhouse Summerseason:

Product

(from Portfol io)

r_Greenhouse Summerseason:

Requirements Specification(from Portfol io)



r_Window w ith Motor: Requirements Group


r_Low cost Temperature Sensor: Requirements Group




a_Greenhouse Summerseason:

Architecture

(from Portfol io)

i_Greenhouse Summerseason:


(from Portfol io)

s_Greenhouse Summerseason: Test

Specification

(from Portfol io)

x_Greenhouse Summerseason: Test

Report

(from Portfolio)




Component






a_Window w ith Motor: Architecture Component


a_ECU Summerseason:



a_Low cost Temperature Sensor:



i_Window w ith Motor: Implementation

Component





Case Group


s_Lowcost Temperature Sensor:

Test Case Group


x_Lowcost Temperature Sensor:

Test Report Group



Report Group


x_Window w ith Motor: Test Report Group



Component


i_Low cost Temperature Sensor:











Low cost Temperature Sensor:

ProductComponent


«indirect»

«indirect»

«indirect»«indirect» «indirect»

«indirect»«indirect»


[email protected]


Slide: 48

object Greenhouse Wintertime











Precise Temperature Sensor:

ProductComponent




r_Window w ith Motor: Requirements Group





Component






a_Window w ith Motor: Architecture Component


i_Window w ith Motor: Implementation

Component




x_Window w ith Motor: Test Report Group


r_Greenhouse Wintertime:

Requirements Specification(from Portfol io)

a_Greenhouse Wintertime: Architecture

(from Portfol io)

i_Greenhouse Wintertime:


(from Portfol io)

s_Greenhouse Wintertime: Test

Specification

(from Portfol io)

x_Greenhouse Wintertime: Test Report

(from Portfolio)


(from Portfol io)

r_Heater: Requirements Group


a_Heater: Architecture Component


i_Heater: Implementation

Component


s_Heater: Test Case Group


x_Heater: Test Report Group


r_ECU Wintertime: Requirements Group


a_ECU Wintertime: Architecture Component


s_ECU Wintertime: Test Case Group


x_ECU Wintertime: Test Report Group


i_ECU Wintertime: Implementation

Component


r_Precise Temperature Sensor: Requirements

Group


a_Precise Temperature Sensor: Architecture

Component


s_Precise Temperature Sensor: Test Case

Group


x_Precise Temperature Sensor: Test Report

Group


i_Precise Temperature Sensor:



Example 2 “Greenhouse”Product “Wintertime"


[email protected]

Specification of the Greenhouse in an adapted Tool


[email protected]


Slide: 50

Requirements for a Traceability Tool

• The Tool shall be simple and easy to use– The problem is complicated enough

• The Tool shall support traceablity and consistency– A Global Unique ID is the base for traceability– Traceablity is the base for consistency– consistency needs rules for validation

• The Tool shall support all engineering disciplines– The maximal efficiency and consistency checks can only be reached if all

disciplines are taken into account• The Tool shall reuse product components and traces in products

– Traceability in real products is not possible without reuse• The Tool shall support coverage, metrics and reporting

– The traces and the objects shall be in one repository to obtain reliable results


[email protected]


Slide: 51

Traceability Layerclass Traceability Layer

Requirements Engin.

A


A

Implementation

A

Test Engineering

A

Test Execution

A

Requirement

A


A

Implementation Unit

A

Test Case

A

Test Case Result

A

ENG.8.BP5ENG.10.BP5

ENG.2.BP6ENG.4.BP6

1..*

1..*

1..*

1..*ENG.7.BP7ENG.9.BP7

1

1..*

1 1..*

1

1

ENG.5.BP10


ENG.6.BP9ENG.6.BP10

ENG.6.BP8

1

1..*

We start on Requirements Item Level


[email protected]


Slide: 52

SoQrates Product Editor –Requirements Data

An individual Global Unique ID is supported

A Database ID isoften not helpfulA requirement hierarchy

can be defined …

Now we are on Requirements Item Level A data sheet for

every item

… and Links will beautomatically generated

Start the Tool


[email protected]


Slide: 53

SoQrates Product Editor –Requirements Links

A link sheet forevery item

This Item …

… the parents …

… and the children


[email protected]


Slide: 54

SoQrates Product Editor –Architecture

Add ArchitectureItem Level …

… and add an architecture hierarchy


[email protected]


Slide: 55

SoQrates Product Editor –Architecture Requirements

Requirements will be linkedto Architecture Elements by

copy and paste


[email protected]


Slide: 56

SoQrates Product Editor –Link Requirements to Architecture Elements

Second Explorer is helpfulby copy and paste

Copy Requirements …


[email protected]


Slide: 57

SoQrates Product Editor –Link Requirements to Architecture Elements

… and paste them to therelated Architecture Element


[email protected]


Slide: 58

SoQrates Product Editor –Reuse Architecture Elements

For reuse copyArchitecture Elements …


[email protected]


Slide: 59

SoQrates Product Editor –Reuse Architecture Elements

… and paste them to anotherArchitecture Element


[email protected]


Slide: 60

SoQrates Product Editor –TestCases for Requirements

… define Test Cases …

For testing addTest Case Level …

… copy the relatedRequirements …


[email protected]


Slide: 61

SoQrates Product Editor –TestCases for Requirements

… and paste them tothe related Test Case


[email protected]


Slide: 62

SoQrates Product Editor – All Disciplines

Add Implementation Item Level …Add Test Result Level

… and add ArchitectureElements with theirRequirements in the

same way


[email protected]


Slide: 63

Product Component Developmentclass Product Component

ProductComponent

A

Requirements Group

A

Requirement

A


A


A


A

Implementation Unit

A

Test Case Group

A

Test Case

A

Test Report Group

A

Test Case Result

A


0..1

1..*

1

1..*

0..*

1

0..1

1..*

1

1..*

1..*

1

1..* 1..*

0..1

1..*

1..*

1

1..*

1..*

1..*

1

0..1

1..*

0..*

1

1 1

1

1..*

0..*

1

1..*

1 0..*

10..1

1..*

1

1..*

0..*

1

For a ProductComponent we need …

… our defined linked Items …

… and Groups of them


[email protected]


Slide: 64

SoQrates Product Editor –Requirement and Architecture Groups

Add RequirementGroup Level …

… Architecture Group Level …


[email protected]


Slide: 65

SoQrates Product Editor –Implementation and TestCase Groups

… Implementation Group Level …

… and Test Case Group Level

Items will be added to theGroups by copy and paste


[email protected]


Slide: 66

SoQrates Product Editor –Define Product Components in a Collection

Add ProductComponent Level …

… create a ProductComponent Selection ...

… and a ProductComponent …

… and add Item Groups tothe Product Component

with copy and paste


[email protected]


Slide: 67

SoQrates Product Editor –Reuse Groups

Item Groups can be reused in several Product Components


[email protected]


Slide: 68

Engineering ModelProduct Development with Product Components

class Multi Product Development

Product

A

ProductComponent

A

Portfolio

A


A


A

Architecture

A


A

Test Specification

A

Test Report

A

*

1

1

1

1

11..*

1

1

1 1

1

1

1

1..*

1For a Product

we need …

… our defined ProductComponents …

… to create Productspecific Specifications


[email protected]


Slide: 69

SoQrates Product Editor –Define a Product with Product Components

Add Product Level …

… create a ProductPortfolio ...

… and a Product

Define the Product by addingProduct Components with

copy and pasteThe Product specificSpecifications will becreated automatically


[email protected]


Slide: 70

Engineering ModelProduct Development – Indirect link via Components

class Product Dev elopment (complete)

Portfolio

A

Product

A


A


A

Architecture

A


A

Test Specification

A

Test Report

A

Requirements Group

A


A


A

Test Case Group

A

Test Report Group

A

ProductComponent

A

Consistent subsetOverall collection

Requirement

A


A

Implementation Unit

A

Test Case

A

Test Case Result

A

1..*

«indirect»

1

1

1..*

1..*

1

1

1

1..*

«indirect»1

1 1

0..*

1

1..*

«indirect»

1

1

1 1

1

0..*1

0..1

1..*

1

1

0..*1

1..*

1..*

1..*

«indirect»

1

1..* 1..*

1..*

1

1..*

«indirect»

1

0..1

1..*0..1

1..*

1..*

1

0..1

1..*

0..*1

1..*

1

1

1..*

1

1

*

1

1 1..*

0..*1

1..*

1

0..1

1..*

1..*

1

1

1..*

Items are linkedto Groups

Groups are linked toProduct Components

Product Componentsare linked to Products

Specifications arelinked to Products …

… and so indirectlylinked to Groups

and Items


[email protected]


Slide: 71

SoQrates Product Editor –Collect Specifications by Indirection

The indirectly linked Groups and Items will be automaticaly linked direct tothe Specification of the same Issue

Type, when a Product Component was pasted into the Product


[email protected]


Slide: 72

SoQrates Product Editor –Product Consistency

Based on the traceability of a Product a coverage analysis

over all disciplines …

… or for separate disciplinesis possible

A rule based consistencyanalysis can be done during

the coverage analysis


[email protected]


Slide: 73

SoQrates Product Editor –Product Component consistency

Based on the traceability of a Product Component a coverage and

consistency analysis can be done

The coverage and consistencyanalysis of Groups or Items can be

done in the same way


[email protected]

Thank you for your attention!

Rainer Dreves, Conti Temic Microelectronic GmbH, Sieboldstrasse 19, 90411 [email protected]

Frank Hällmayer, Software Factory GmbH, Parkring 4, 85748 Garching near [email protected]

Lutz Haunert, Giesecke & Devrient GmbH Zamdorferstr. 88, 81677 [email protected]

Bernhard Sechser, Method Park Consulting GmbHWetterkreuz 19a, 91058 [email protected]

Armin Rieß, B. Braun Avitum AGAm Buschberg 1, 34212 [email protected]


[email protected]

• Biró M., Klespitz J., Gmeiner J., Illibauer C., Kovács K.: Towards Automated Traceability Assessment through Augmented Lifecycle Space

• Dreves R., Hällmeyer F., Haunert L., Sechser B.: Method to Realize Traceability in Development Processes (EuroSPI 2015), 30 September – 02 October, Ankara

References


[email protected]


Slide: 76

WorkshopParticipants

Last Name First Name Company Location

soqrates.eurospi.net A practical View on...

Documents

Transcript of soqrates.eurospi.net A practical View on...