A multi-view approach for component based design

Transcription

1 CESAR - Cost-efficient methods and processes for safety relevant embedded systems A multi-view approach for component based design Odile Laurent () Eric Armengaud (VIF) ARTEMIS technology conference Budapest, June 2010

2 Presentation overview The key drivers for CESAR engineering development process The CESAR development life cycle The multi-views concept The CBD common data model Conclusion 2

3 The key drivers for CESAR development process Be generic enough to be instantiated by different industrial domains Support real-time critical constraints Reduce cost and time development relying on: Models allowing early V&V and automatic translations Components reinforcing reuse Ease concurent engineering based on: A multi-views approach supporting the different skills involved in the product development A common data model whose aim is to share common information between the different product artefacts 3

4 The CESAR development life cycle process (1/2) A V life cycle with well defined phases 4

5 The CESAR development life cycle process (2/2) The model-based approach for early validation and automatic translations 5

6 The CESAR development life cycle process (2/2) The model-based approach for early validation and automatic translations But, different kinds of models for different skills (dysfunctional models for safety, performance models for timing constraints, ) : The justification for multi-views concept 6

7 The multi-views approach: focusing on architecture design 7

8 The multi-views approach What for? sharing common architecture data between models stakeholders oriented The notion of view and viewpoint based on IEEE 1471 standard: A view is a representation of a whole system from the perspective of a related set of concerns. A viewpoint is a specification of the conventions for constructing and using a view; a pattern or template from which to develop individual views by establishing the purposes and audience for a view and the techniques for its creation and analysis. 8

9 The Multi-views approach: the double challenge The first challenge: Identify the relevant views The identified views : Operational: focus on the system missions Functional: focus on the functional aspects of the system Logical: define system architecture, define abstract components, allocation of functions on them, behaviour of components and interfaces between components Physical : define concrete hardware and software components, allocation of functions on hardware and software components Safety: define the dysfunctional aspects of the system Product line: define the variability points Performance: define the system performance Interface: define the interfaces of the system components The multi-views prism The second challenge: Propose the appropriate foundations to share common data between the different views 9

10 Component based design common data-model What for? Ensuring the views consistency Allowing the communication between the various tools all along the development process What characteristics? Reflect the industrial practices Support the develop process activities Flexible to be customized to each industrial domain Independant from the implementation The identification of these common data is done highlighting for each development life cycle activities the necessary information to share between these activities 10

11 The architecture design: which views for which phases? Operational Analysis operational view Product line view Interface view Functional/NF Analysis: Functional view Product line view Interface view Logical Architecture definition: Logical view Safety view Interface view Product line view Performance view Physical Architecture definition Physical view Safety view Interface view Product line view Performance view : A1 F1 F21 F1 F22 F6 C11 F21 F1 F6 A2 A2 F5 F2 F4 F3 C1 C2 F3 C12 F22 C2 C1 F7 C3 Processors Buses C3 C4 ViewPoints ViewPoints 11

12 The common data-model : an example for the physical analysis phase 12

13 The common data-model : the design principles 13

14 Conclusion The ambition of CESAR: To implement the IEEE 1471 standard (multi-views approach) taking into account the cross-domain dimension To decouple the implementation of the CBD data model from the conceptual aspects To integrate the CBD data model into the RTP CESAR meta-model Way forward: Extend the CDB data model to the different viewpoints Extend the CBD data model to the V&V concerns Ensure the ability to instantiate it with respect to application domains needs 14