Reqtify in support of Embeded Systems Development at PSA

Transcription

1 Reqtify in support of Embeded Systems Development at PSA Mathieu DUTHOIT April 2011

2 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

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

4 Use of Reqtify for Requirements traceability & coverage analysis 4 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 : 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) Used for requirement coverage analysis but also for : Requirement change measurement Inconsistency check (rules) Requirement management necessary for ISO26262 : Identify safety related requirement with ASIL level tags (Att_SdF@4D) Trace which component supports/contributes to this requirement Verify that covering requirements have the same ASIL level. Management of Diversity using tags (Att_var@ ) and filters

5 Use of Reqtify for Requirements traceability & coverage analysis 5 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)

6 Use of Reqtify within COC project

7 7 Origins & goal of COC project Started in 2005 following an internal audit on EE development process To give the differents actors of the embeded functions & system design a design tool chain to support their development process including : Description of the design (functional & physical) Verification of the design (static & simulation) Automatic generation of documents based on design information Based on structured, shared and validated information by each relevant actors This phase requires an important work on the process This tool chain first connects existing tools and second adds new missing tools : Used for the design of 70 vehicule functions (500 systems due to diversity)

8 8 Use of Reqtify within COC project COC is a Design Tool Chain to support EE system design using modeling : Define the structural and behavior description of Embeded Functions from COTS tools like Simulink/Stateflow and Statemate Define an EE Physical Architecture (sensor, ECU, actuators, busses and wired links) including EE service functions Define Communication Matrices (CAN, LIN, ) Allocate the Embeded Functions and interfaces on the components and links of the Physical Architecture to build a system. Define requirements linked to the models Simulate the system model Verify the system model (results from simulation using test scenarios) Generate SdF model (SIMFIA) from System model Automatically generate documents (systems and components) from models & requirements Build and verify a vehicle project Automatically build and verify component model

9 9 COC design activities Design Activity Project Activity Allocatable Functions & environment Technical Requirements Test scenario Project Conf. Reference AEE Function 1 Communication Matrices System Design Simulation : Verification & Validation System Design 1a EE Service Functions Component Requirement Specification Links Components (ECU, sensor Actuator) EE Physical Architecture Various Reports Failure Analysis Model Test results System Design Document Function N System Design X Project doc. Generation : -System Design -Component Specification -Synthesis reports

10 10 COC in the V cycle Zone de Données Partagées Elaboration des lois de control / commande SIMULINK, STATEMATE... Elaboration des architectures physiques ACAM Organisation des données techniques (Stockage, versionnement, gestion de configuration) Validation sur table & véhicule Allocation du fonctionnel sur les architectures physiques (schémas opérationnels) ACAM SIMULATION Simulation / vérification des modèles de conception COC-S DC fonctions CdC CdC Organes Organes COC-P Organes Intégration progressive virtuel / réel Vérification des caractéristiques organes Développement organe et logiciel (AUTOSAR)

11 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 Thank you for your attention 12

13 Annexes 13

14 14 Requirements traceability & coverage analysis Rqtf Prj 1 VHL - Function VHL - 2 Req. Function (DOORS) 2 Req. VHL (DOORS) - Function 1 Req. (DOORS) VHL System VHL 3 Req. System (Word, 2 Req. Excel) (Word, VHL Excel) System 1 Req. (Word, Excel) VHL System 3 VHL Test System Proc. 2 VHL System Test (Excel) Proc. 1 Test Proc. (Excel) (Excel) Rqtf Prj 2 Rqtf Prj 3 Component C Component B Req. Component Req. (Word) A Req. (Word) (Word) Component C Component Test Proc. B Component Test (Excel) Proc. A Test Proc. (Excel) (Excel) Component BSI Component S/W Req. BSI Component S/W (Word) Req. BSI Fct 1 S/W (Word) Arch. Req.(Word) Component C Component S/W Test Proc. B Component S/W Test (Word) A Proc. S/W Test (Word) Proc. (Word)

15 15 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 = requirements managed at the system design level

16 16 Reqtify Project 2 User : EE design architect Object : Verify coverage of System Design requirements by the impacted Components Specification requirements :

17 17 Reqtify Project 3 User : Component Development Engineer Object : Verify coverage of Systems Design requirements by the Component Specification requirements :

18 COC tools architecture Import des modèles fonctionnels -Elaboration des Appareils, AEE et Schémas Opérationnels Rédaction et gestion des exigences techniques Typage et cohérence des flux Modélisation Fonctionnelle (allouable, service EE & environnement) Matlab/Simulink/Stateflow Statemate Conception d Architecture EE ACAM Exigences Techniques (GET) DICO Flux ZDP (stockage structuré des infos) Advitium COC-P (structuration des données, navigation, import/export des données partagées, support du workflow) Reqtify Import des messageries définies dans BDMUX (enveloppe ou appareils) Synthèse automatique des planches de conception en modèle simulable Réalisation des Fiches de test et exécution sur COC-S + remontée des résultats - Synthèse du modèle SdF d un SO, ajout des infos SdF et réalisation de l étude SdF associée Définition des messageries BDMUX SIMULATION COC-S Tests automatiques COC-T Etudes SdF SIMFIA -Génération de document (DC Fct), CdC Organe ou rapports de synthèse Génération documentaire GAD -Définition et gestion des conf. projets Gestion des Conf. Projet Projets/ACAM 18

19 Physical Architecture Design (example) 19

20 System Design (example) 20

21 Reqtify as COC-P : 21

22 22 Use of Reqtify in COC-P Automatic Generation of Document using Reqtify report generator :

23 23 Use of Reqtify in COC-P Through COC-P, coverage links between objects (more specifically documents) can be established :

24 24 Use of Reqtify in COC-P Reqtify coverage analysis projects are automatically generated thru Configurations de dépendances :