Requirements Management with PREEvision · Requirements Management AUTOSAR System and Software Design Communication Design (AUTOSAR and Legacy) Hardware Component Development Function

V2.0 | 2018-04-03

April 3, 2018

Requirements Management with PREEvision: An integrated solution

RELEASED

2

u PREEvision

Integrated Requirements Management with PREEvision

Requirements Management Use Cases

Create & Write Requirements

Manage Requirements

Manage & Visualize Dependencies

Check & Validate Requirements

Exchange Requirements

Agenda

3

Supported E/E Engineering Use Cases

PREEvision

E/E Backbone,Collaboration Platform,

File Management

Design of SafetyRelevant Systems

Product LineEngineering

ArchitectureDesign

Requirements Engineering and Requirements Management

AUTOSARSystem and Software

Design

Communication Design(AUTOSAR and Legacy)

Hardware ComponentDevelopment

Function Driven DesignSystem Design

Test Engineering andTest Management

E/E Backbone,Collaboration Platform,

File Management

Product LineEngineering and Variants

ArchitectureDesign

Requirements Engineering and Requirements Management

AUTOSARSystem, Service and Software

Design

Communication Design(AUTOSAR and Legacy Formats)

Hardware ComponentDevelopment

Function Driven DesignSystem Design

Test Engineering andTest Management

Wiring HarnessDesign

Change and Release Management

Design of SafetyRelevant Systems

4

PREEvision Modeling Layers and Process & Team Support

PREEvision

5

Product Strategy

Requirements Design Test

PREEvision

Model-based Electric/Electronic Development from Architecture Design to Series Production

ArchitectureDesign

Series Production

u Support of Series-Production Use Cases

u Process Support > Version Management

> Life Cycles

> Ticket-, Release- and Change Management

u Team Collaboration> Many Users, Multiple Sites

> Usability for Sporadic Users and Experts

> Lazy Loading, Partial Model Support

u Integration > Requested Import and Export Filters

> Synchronization with ALM and PLM systems

u Support of IT Requirements > Data Migration

> IT Security

> User Administration

> License Management

6

PREEvision

u Integrated Requirements Management with PREEvision



Manage Requirements




Agenda

7

u Good reasons for Requirements Management

u Definition of requirements: detailed common understanding about the product that is to be developed

u Systematic requirement management is an important prerequisite for the efficient development of complex and high-quality products

u The Goal is to achieve a common understanding between contractor and contracting party

Requirements Management


8

u Traditional Requirements Management with PREEvision includes all the typical features, e.g.:

u Formulating requirements in a comfortable editor

u Structure requirements in a hierarchical way

u Linking, tracking and validating of requirements

u Importing requirements via RIF, ReqIF and Excel

u Exporting requirements via ReqIF or Excel

u Easy generation of specifications

u Additionally

u Modeling instead of mere recording

u Early validations & consistency checks

u High quality of requirements

u Change marker and history

u Version management

u Life cycle management

u Reuse concept

Traditional Requirements Management with PREEvision


9

u Inventory of traditional Requirements Engineering

u Standalone tool

u Mapping only between the requirements

u Linking to other tools difficult, danger of outdated and broken links

u Deep traceability on atomic basis to E/E artifacts not possible

u Relations across multiple databases are not versionable and not archivable in a save way

u Challenges in the E/E development

u E/E architectures get more and more complex

u Plenty variants must be handled

u Additional Needs for Requirement Engineering

u Dependencies between Requirements and the affected E/E artifacts must be easily identifiable

u Changes of a requirement have to be regarded in a consistent way. Answers have to be given on questions like > Which components are affected by a change?

> Which test cases must be adopted?

Traditional Requirements Engineering


10

u Solution: Integrated Requirements Engineering

u All development artifacts in a central data basis. Engineering data and Requirements Management data is located in one model, problems like tool borders or broken links simply do not exist. Engineering and requirement data are always consistent.

u Organization has full overview over the E/E artifacts and their correlations

u Common repository,

u Common visualization,

u Computer supported evaluation

u Seamless traceability

u Benefit

u With a centralized data basis complexity can be managed in an efficient way

u Lesser expense for internal coordination

u No expense for maintenance of redundant and possibly inconsistent data

u Lesser development costs

u Faster time to market

Integrated Requirements Engineering


Central data basis

Smooth and conflict-free working by lock &

commit

Productline and Release management

Change management

Lifecycle management File management

Role and Right management

Version management

11

u Modeling instead of mere recording

u Possibility to map requirements with any artifact of the E/E model

u Support of bottom-up approach (creation of requirements starting from an E/E artifact)

u Easy handling and navigation of requirements through all related parts of the product line model

u Seamless traceability

u Placeholder concept: like field functions in a word processing program every attribute of an E/E artifact can be referenced inside the requirements description and is kept up-to-date.

u Possibility to use variant and reuse concepts

u Early validations & consistency checks -> high quality of requirements

u Change marker and history

u Version management

u Lifecycle management

The Integrated Requirements Engineering approach in PREEvision


Integrated Requirements Management is the seamless integration of requirements in the entire E/E development process.

12

Realization of top-down, bottom-up and middle-out modelling approaches is possible. The specification can be based in a classic way on requirements which are then transformed into concrete E/E artifacts. Alternatively the specification can be directly derived from the E/E artifacts (bottom-up). A mixture of requirements and E/E artifacts is the most common way, allowing to extend your specification with details from the development artifacts like special attributes or diagrams.

u The system model is precise and up-to-date.

u The requirement content is in the development artifacts in the model

u The specification is generated based on the model data and in a customer specific layout.

u The document can be exported as ReqIF

Integrated Requirements Management: the model serves as specification


System Model

SysReqSpec

Transmission Co...

Indicator Stick / ...

Central Gateway...

Engine Control / -;- (E...

Climate Control ...

Seat Control / -;...

Lighting Control...

Instrument Clust...

Brake-by-wire / ...

Steer-by-wire / -...

Driver Assistance / -;- (E...

Camera / -;- (Sensor)

Radar / -;- (Sensor)

Telephone Interf... Head Unit / -;- (...

Lane Departure Detection Speed Sensor / -...

implicitly / -;- (E...

explicitly / -;- (El...

teminal15 / -;- (...

terminal30 / -;- (...

Powered (by)

Counteract Steering

Cancel Activation

Validate Lane Departure

Steering Wheel Position

S1_Chassis CAN

COM

- : PowerIn

Bottom-up approch

13

Integrated Requirements Management


Middle-out approach

14

Benefits of the Integrated Requirements Management in PREEvision


Classic Requirements Management

u Strong tool support for doing a complex, high sophisticated work

u Document based handling of requirements via tables

u Full formatting via Libre Office

u Extendible model via custom attributes

u Full traceability of requirements

u Extendable tool with customer specific functions, checks and reports

u Consistency checks and metrics increase requirements quality

u Import / export functionalities

u Report generation

Integrated Requirements Management

u Higher efficiency and better quality by the capability to have a comprehensive and consistent set of requirements (and derived solutions)

u All in one place – requirements, their technical implementation and related test artifacts in one model

u No expense for maintenance of redundant and possibly inconsistent data

u Enabler for know-how transfer within the organization

u Lesser expense for internal coordination

u Mappings between requirements and the related E/E development artifacts can be performed in one and the same system

u Easy navigation through all parts of the E/E architecture

u ReqIF export of system specifications

u Lesser development costs

u Faster time to market

15

PREEvision


u Requirements Management Use Cases


Manage Requirements




Agenda

16

Typical Use Cases of Requirements Management


Create & Write

Requirements

Manage

Requirements

Create & Manage

Dependencies

Check & Validate

Requirements

Requirements

Specifications

Exchange

Requirements

17

Requirements can be created via context menu or shortcut either

u In ModelView,

u Requirement Text Editor (Table) or

u starting from any model artifact.

Create Requirements


18

Editing Requirements


Description with rich text formatting

Hierarchical structuring

u The User can edit the requirements in different views:

u Directly in the table

u Stand alone editor

u Property view

u Integrated dedicated Libre Office editor

u Allows to extend the creation and writing of requirements with tables, graphics and advanced text formatting functions

19

u All text formatting functions of Libre Office available

u Template file with allowed formatscan be defined

u Styles and Formatting view for applyingformats quickly

u Formatting can be restricted

u Authority management

u Paste action

u Edit action: used styles are checked and not allowed formats are marked

Formatting of Requirements


Insertion of tables, graphics, diagrams

Libre Office menu

20

Requirement Types


u Requirement subtypes for a systematic specification are available

u Information (can)

u Intention (will)

u Requirement (shall)

u Safety and Security Requirements

u Refactoring: transformation of one type into another possible

u Selectable subtypes are definable

21

u Use case diagrams provide a user centric perspective on a system.

u They show the intended functionality and the benefits of the system from the perspective of the users.

u They visualize the relations and dependencies between users and use cases.

u Use case diagrams are behavior diagrams and follow the Unified Modeling Language 2.0 (UML 2.0) specification.

u Available elements are: > Use cases

> Use case systems

> Actors

> Include and extend relations

> Extension points

> Generalizations

u Features> All general PREEvision diagram features are supported.

> Use Case Diagrams can be created under any artifact in the Product Goals layer.

> Fulfillment association between Requirements / Customer Features and Use Cases are available.

Use case diagrams


22

PREEvision




u Manage Requirements




Agenda

23

Manage Requirements: Life Cycle Management

Manage Requirements

Life cycle management describes:

u the sequence of states of the requirement

u contains the information on its current development status or maturity level, e.g. new, completed, verified …

Life cycles allow to

u restrict access rights for roles (e.g. deny a check-in for the role developer in the state New)

u proof mandatory attributes

u Initiate actions, e.g. ask for responsible resource after a transition into a Feedback state

u Send mails, e.g. automatically inform a user if a feedback is needed from him

24

Extension of the Metamodel: custom attributes

Manage Requirements

User defined requirement attribute

Model queries

u Requirements can be

u extended with user-defined attributes that can be directly edited

u displayed as a separate column in the table

u defined as enumeration, boolean, integer, string, …

25

Multi Value Attribute Definition, allowing to select several literals of the enumeration.

u Definition of a default value is possible

u Special control available in Table Editors and in the Property Editor

u Entries in the control and in table cells are sorted by the given order (index)

u Selected entries are separated by an semicolon in table cells

u Filtering and sorting is available in Table Editors

Custom attributes: example

Manage Requirements

26

Manage Requirements: Reuse

Manage Requirements

1

Reuse can be created via short-cut menu or via drag & drop

12

u The benefits of reuse is to reduce lead time, costs and to improve quality

u Already existing artifacts can be used again and don’t needed to becreated new.

u Changes are automatically updated for all reused artifacts.

27

PREEvision




Manage Requirements

u Manage & Visualize Dependencies



Agenda

28

u Requirement links can be created via drag &drop

u Links or Mappings can be represented in a separate column with a symbolic representation, showing the count of incoming and outgoing links.

u On mouse over a tooltip shows details for the incoming/outgoing links

u Artifacts in the tooltipp are navigable

u The shown information can be customized

Create dependencies: link Requirements to other Requirements


29

u Requirements can be mapped to development data objects on all levels of the data model simply via drag & drop

u Mappings can be displayed as columns, can be shown in the model tree or can be used in diagrams

Create dependencies: map Requirements to any E/E artifact


Mappings can be displayed in the table

Mapped artifact

30

u Within a formatted text, placeholders can be created to reference any data of any model artifacts. Placeholders can be simply created via drag and drop of the referenced artifact into the formatted text.

u Clicking on a placeholder navigates to the referenced artifact.

u Placeholders are shown in curly brackets.

u In reports placeholders can be also used and are automatically updated when creating a report. In reports special placeholders for lists, diagrams, tables and charts are available.

Placeholders: use data from E/E artifacts in Requirements


Placeholders can reference any data of E/E artifacts

Drag&Drop

Referenced artifact

31

u Requirements can be linked to other requirements to maintain traceability

u Linked requirements are shown in tables, the model tree, property view and diagrams

u Possibility to map requirements to development data objects on all levels of the data model (via drag & drop or typing)

Manage & Visualize Dependencies: Traceability


33

All changes (attribute and relation changes) carried out for an artifact are logged and illustrated in the change history. Even if change markers have been removed, this has no impact on the traceability of changes in the change history.

The change history can either be opened for an artifact to display the history of all changes of the artifact, or it can be opened for a single attribute or relation. A detailed and a compact display mode is available for the change history.

u The information provided by the change history can be used in a change report.

Manage & Visualize Dependencies: Change History


The change history answers

Which data of an artifact has been changed.

Which data of an artifact has been changed since the last commit / life cycle state change.

What was the initial value of an artifact’s attribute and what are its subsequent values.

When the change was carried out.

Who has carried out the change.Who?

What?

Which?

When?

34

The compact view shows only changed attributes and relations and only changes to the former model version. All further previous values in the history of an attribute/relation can be displayed by selecting an individual model version from a drop-down list. The changes of an attribute/relation can be seen at a glance. Depending on the attribute type different compare tables are offered

u Richtext: Libre Office compare

u Other Attributes: Table

u Relations: +/- indicates an added/deleted relation

Change history: compact view


35

PREEvision




Manage Requirements


u Check & Validate Requirements


Agenda

36

Check & Validate: Requirements Analysis (1/2)


With PREEvision it is possible to validate requirement attributes

37

Check & Validate: Requirements Analysis (2/2)


u With help of automatic checks it is possible to prove the consistency of the requirements directly

38

PREEvision




Manage Requirements



u Exchange Requirements

Agenda

39

Generate Requirements Specifications


u Reports can be generated based on user defined templates

u High level of flexibility in the report format including the use of tables, diagrams and complex model queries

40

ReqIF Import and Export


41

u Customized ReqIF exports based on temporary reports available, allowing to export any data of the model, not only requirements.

u Full support of PREEvision report functionality including diagrams and tables for all PREEvision modeling layers.

u Support of vendor specific ReqIF Tool Extensions by customizing the PREEvision ReqIF Import and Export is possible.

ReqIF Export using Reports


42

RIF import


u Requirements can be imported in RIF file formats

u User-defined configuration of requirements attributes to be imported / exported

u Existing specifications can be updated via imports

u It is possible to import requirements as customer features or test artifacts via RIF files

43 © 2014. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V2.0 | 2018-04-03

Author:Robert RotterVector Germany

For more information about Vectorand our products please visit

www.vector.com

http://www.vector.com/

Documents

Requirements Management with PREEvision · Requirements Management AUTOSAR System and Software Design Communication Design (AUTOSAR and Legacy) Hardware Component Development Function