Reqtify@PSAReqtify in support of Embedded Systems

development at PSA

Mathieu DUTHOIT April 2011

2

Content

Use of Reqtify in its primary role : Requirements traceability & coverage analysis :

Use of Reqtify within COC project

What is COC ?

Choice of Reqtify for COC-P

Use of Reqtify in COC-P

Use of Reqtify in its primary role : Requirements traceability & coverage analysis

4

Use of Reqtify for Requirements traceability & coverage analysis

Used mainly in EE domain

About 120+ users between standard Reqtify use and COC-P

Areas covered :

Definition and management of common Analysis Types and Requirement formalism :

Used for requirement coverage analysis but also for :

Requirement change measurement

Inconsistency check (rules)

Requirement (current) Text Requirement (source)

GEN-VHL-DC-ANBC.0126 (1) Requirement text

Attributes :

Att_Sdf@4C

Att_var@ xn

…

GEN-VHL-ST-ANBC.0042 (2)

GEN-VHL-ST-ANBC.0103 (1)

GEN-VHL-ST-IHM.0037 (3)

Detail

5

Use of Reqtify for Requirements traceability & coverage analysis

The good :

Easy to set up and realize real requirement traceability

User really involved in the coverage result : He manages his own project

Flexibility

Dedicated to requirement analysis and coverage : Does not interfere with document management.

The “must be careful of”

Needs organization for common Requirement format (as much as possible)

Needs organization for sharing of analysis types, rules etc.

Needs organization to handle large projects

“Expressions regulières” very powerful but sometimes hard to master (support@reqtify.com)

Use of Reqtify within COC project

7

Use of Reqtify within COC project

COC is a Design Tool Chain to support EE system design using modelingUses the structural and behavior description of Embeded Functions from COTS tools like Simulink/Stateflow and Statemate

Allows users to define an EE Physical Architecture (sensor, ECU, actuators, busses and wired links) including EE service functions

Allows users to define Communication Matrices (CAN, LIN,…)

Allows users to allocate the Embeded Functions and interfaces on the components and links of the Physical Architecture and build a system.

Allows users to define requirements linked to the models

Allows users to simulate the system model

Allows users to verify the system model (results from simulation using test scenarios)

Allows users to generate SdF model (SIMFIA) from System model

Allows users to automatically generate documents (systems and components) from models & requirements

Allows users to build and verify a vehicle project

Allows users to automatically build and verify component model

8

COC design activities

Allocatable

Functions

& environment

EE Service

Functions

Components

(ECU, sensor

Actuator)

Links EE Physical

Architecture

Communication

MatricesSystem

Design

Simulation :

Verification

& Validation

Test

scenario

Test

results

System

Design

Document

Technical

Requirements

ReportsComponent

Requirement

Specification

Failure

Analysis

Project Conf.

Design Activity Project Activity

Reference

AEE

Function 1

System Design

1a

System Design

X

Project doc. Generation :

-System Design

-Component Specification

-Synthesis reports

Function N

9

COC in the V cycle

Elaboration des

lois de control /

commande

Allocation du fonctionnel

sur les architectures physiques

(schémas opérationnels)

Simulation / vérification

des modèles de

conception

SIMULATION

SIMULINK, STATEMATE...

Intégration

progressive

virtuel / réel

Organisation des

données techniques (Stockage, versionnement,

gestion de configuration)

Zone de Données

Partagées

Développement organe

et logiciel (AUTOSAR)

CdC

OrganesCdC

Organes

Vérification des

caractéristiques organesOrganes

Elaboration des

architectures physiques

ACAM

ACAM

COC-S

DC

fonctions

COC-P

Validation

sur table &

véhicule

10

COC tools architecture

ZDP(stockage

structuré des infos)

COC-P(structuration

des données,

navigation,

import/export des

données partagées,

support du workflow)

Advitium Reqtify

Modélisation Fonctionnelle(allouable, service EE & environnement)

Matlab/Simulink/Stateflow

Statemate

Import des modèles

fonctionnels

Définition des messageries

BDMUX

Import des messageries définies

dans BDMUX (enveloppe ou

appareils)

Etudes SdF- Synthèse du modèle SdF d’un

SO, ajout des infos SdF et

réalisation de l’étude SdF

associée SIMFIA

Tests automatiquesRéalisation des Fiches de test

et exécution sur COC-S +

remontée des résultats

COC-T

SIMULATIONSynthèse automatique des

planches de conception en

modèle simulable COC-S

Génération documentaire-Génération de document (DC

Fct), CdC Organe ou rapports

de synthèse GAD

Gestion des Conf. Projet-Définition et gestion des conf.

projets

Projets/ACAM

Conception d’Architecture EE-Elaboration des Appareils, AEE

et Schémas Opérationnels

ACAM

Exigences Techniques (GET)Rédaction et gestion des

exigences techniques

DICO FluxTypage et cohérence des flux

11

Choice of Reqtify as COC-P

In the COC architecture, COC-P/Reqtify is used as a connector between database and applications to

Manage Data :

• Data organization

• Users access right management

• Data versionning and configuration

Import (or reference) data :

• Any documents

• Structural/behavioral models (Simulink/Stateflow, Statemate)

• Communication Matrices

Generate documents :

• Use of Reqtify report generator to access information contained in database and generate

– Technical documents (system design documents, component requirement documents) according to PSA document template

– Any specific reports on request (function/component allocation matrix,..)

Link documents together

Generate requirements coverage & impact analysis

12

Annexes

13

Requirements traceability & coverage analysis

VHL System 3Test Proc.

(Excel)

Component CTest Proc.

(Excel)

VHL -Function 2 Req.

(DOORS)

VHL -Function 2 Req.

(DOORS)VHL -Function 1 Req.

(DOORS)

VHLSystem 3 Req.(Word, Excel)

VHLSystem 2 Req.(Word, Excel)VHL

System 1 Req.(Word, Excel)

Component CReq.

(Word)

Component BReq.

(Word)Component A

Req.(Word)

Component BSIS/W Req.(Word)

Component BSIS/W Req.(Word)

Component BSIFct 1 S/W Arch.

Req.(Word)

Component CS/W Test Proc.

(Word)

Component BS/W Test Proc.

(Word)Component A

S/W Test Proc.(Word)

Component BTest Proc.

(Excel)Component A

Test Proc.(Excel)

VHL System 2Test Proc.

(Excel)VHL System 1

Test Proc.(Excel)

Rqtf Prj 1

Rqtf Prj 2

Rqtf Prj 3

14

Reqtify Project 1

User : EE design architect

Object : Verify & trace coverage of a VHL Function requirements (DOORS module) by the system design documents :

Around 70 (nbr of functions) * 200 requirements = 14 000 requirements managed at the system design level

15

Reqtify Project 2

User : EE design architect

Object : Verify coverage of System Design requirements by the impacted Components Specification requirements :

16

Reqtify Project 3

User : Component Development Engineer

Object : Verify coverage of Systems Design requirements by the Component Specification requirements :

17

Reqtify as COC-P :

18

Use of Reqtify in COC-P

Automatic Generation of Document using Reqtify report generator :

19

Use of Reqtify in COC-P

Through COC-P, coverage links between objects (more specifically documents) can be established :

20

Use of Reqtify in COC-P

Reqtify coverage analysis projects are automatically generated thru “Configurations de dépendances”: