The System Design Life Cycle
This chapter focuses on a generic process for developing (safety-critical) systems. After a reminder concerning the current development process including the safety aspects, the “Cesar -proposed” development process, based on multi-views and a component-b
- PDF / 1,960,132 Bytes
- 53 Pages / 439.36 x 666.15 pts Page_size
- 26 Downloads / 193 Views
The System Design Life Cycle Nikolaos Priggouris, Adeline Silva, Markus Shawky, Magnus Persson, Vincent Ibanez, Joseph Machrouh, Nicola Meledo, Philippe Baufreton, and Jason Mansell Rementeria
This chapter focuses on a generic process for developing (safety-critical) systems. After a reminder concerning the current development process including the safety aspects, the “CESAR-proposed” development process, based on multi-views and a component-based approach, is highlighted. Despite the fact that the system design life-cycle in each CESAR domain (aerospace, automotive, rail and automation) is characterised by many commonalities, there are also inherent differences, prescribed by domain standards, which are usually reflected in the overall engineering activities. Convergence on a generic development process is crucial for CESAR because this process is the cornerstone of the RTP. More specifically, it will condition the RTP instantiation capabilities and the data which must be manipulated at all stages of system development. These data are the main drivers for sharing information between the development phases on which the interoperability principles rely.
N. Priggouris () Hellenic Aerospace Industry S.A., Tanagra, Greece e-mail: [email protected] A. Silva Fraunhofer Institute for Experimental Software Engineering IESE, Kaiserslautern, Germany M. Shawky Centre National de la Recherche Scientifique, Paris, France V. Ibanez J. Machrouh N. Meledo Thales Group, Neuilly-sur-Seine Cedex, France M. Persson KTH Royal Institute of Technology, Stockholm, Sweden P. Baufreton SAGEM Defense Securite, Paris, France J.M. Rementeria Fundaci´on European Software Insitute, Donostia – San Sebasti´an, Spain A. Rajan and T. Wahl (eds.), CESAR - Cost-efficient Methods and Processes for Safety-relevant Embedded Systems, DOI 10.1007/978-3-7091-1387-5 2, © Springer-Verlag Wien 2013
15
16
N. Priggouris et al.
The cross-domain generic process depicted in this chapter is the result of close cooperation between the domain applications. This proposed process is subject to evolution throughout the CESAR innovations cycles. Indeed, only the experiments led by the application domains will be able to demonstrate its adequacy and its adaptability to meet the industrial needs. The main breakthrough of the proposed process is that it tries to focus on, and impose the use of, models and components during all design phases so that the system description moves from a document-based approach to a more intuitive one where formal methods can be used and early validation techniques can be applied in a more rigorous way. The chapter also includes a short presentation of important modelling aspects that are regarded as a prerequisite for addressing the “CESAR-proposed” development process.
2.1 The “Existing” Development Process All industrial partners involved in CESAR deal with the development of embedded safety-critical real-time systems. This includes in the majority of cases the consideration, during the development and design life-c
Data Loading...
