This article addresses the problem of safety evaluation of complex systems. It proposes an original and rigorous approach that integrates safety analysis in system engineering processes. The approach is based on system engineering principles and uses the famous industrial system engineering standard American National Standards Institute/Electronic Industries Alliance 632:1999. The objective is to help designers and safety engineers in safety management of complex systems. For an efficient design, the model-driven design is adopted through the definition of an information model. The system language “System Modeling Language” is used to address requirements definition and their traceability toward the solution and the verification and validation elements. This common language allows sharing information between the different persons involved in the design project like the system engineer and safety engineer.
AkerlundO (2006) ISAAC, a framework for integrated safety analysis of functional, geometrical and human aspects. In: European congress on embedded real-time software, Toulouse, France, 25–27January.
2.
AlbinetABegocSBoulangerJ-L. (2008) The MeMVaTEx methodology: from requirements to models in automotive application design. In: International conference: ERTS, embedded real time software 2008. Toulouse, France, 29 January–1 February.
3.
AuyangSY (2004) Engineering – An Endless Frontier. Cambridge, MA: Harvard University Press.
4.
AvizienisALaprieJ-CRandellB. (2004) Basic concepts and taxonomy of dependable and secure computing. IEEE Transactions on Dependable and Secure Computing1: 11–33.
5.
Bar-YamY (2005) About engineering complex systems: multiscale analysis and evolutionary engineering. BruecknerS.. (Eds.) In: Engineering Self-Organizing Systems: Methodologies and Applications. Springer-Verlag Berlin Heidelberg2005, vol. 3464, pp.16–31.
6.
BozzanoMCavalloACifaldiM. (2003) Improving safety assessment of complex systems: an industrial case study. In: FM 2003, Pisa, Italy, 8–14September.
7.
BrooksFPJr (1987) No silver bullet: essence and accidents of software engineering. IEEE Computer20: 10–19.
8.
ConquetE (2008) The ASSERT project: a step towards reliable and scientific system and software engineering. In: ERTS 2008, Toulouse, France, January29, 30, 3, February1.
9.
CoulinCSahraouiA-E-KZowghiD (2005) Towards a collaborative and combinational approach to requirements elicitation within a systems engineering framework. In: (SelvarajHenryMuthukumarVenkatesan) 18th international conference on systems engineering (ICEng’05), Las Vegas, NV, 16–18 August, pp.456–461.
FriedenthalSKobrynC (2004) Extending UML to support a systems modeling language. In: INCOSE Symposium Proceedings, Toulouse, France, 20–24 June.
12.
FriedenthalSMooreASteinerR (2009) A Practical Guide to SysML: The Systems Modeling Language (The MK/OMG Press). Morgan Kaufmann.
13.
GoguenJLindeC (1993) Techniques for requirements elicitation. In: 1st IEEE international symposium on requirements engineering, San Diego, CA, 4–6 January, pp.152–164.
14.
GotelOCZFinkelsteinCW (1994) An analysis of the requirements traceability problem. In:International conference on requirements engineering, Colorado Springs, CO, pp.94–101.
15.
GuillermR (2011) Intégration de la Sûreté de Fonctionnement dans les Processus d’Ingénierie Système. PhD Thesis, University of Toulouse, Toulouse, France.
16.
GuillermRSadouNDemmouH (2010) Information model for model driven design of complex system based on system engineering approach. In: International conference on complex systems design and management (CSDM 2010), Paris, France, 27–29 October, pp.99–111.
17.
JuristoNMorenoAMSilvaA (2002) Is the European industry moving toward solving requirements engineering problems?IEEE Software19(6): 70–77.
18.
KotovskyKHayesJRSimonHA (1985) Why are some problems hard? Evidence from tower of Hanoi. Cognitive Psychology198517: 248–294.
19.
LevesonNHerringMSOwensBD. (2007) Safety-driven model-based system engineering methodology. Part I: methodology description. MIT Technical Report.
MageeCde WeckOL (2004) Complex system classification. In: Fourteenth annual international symposium of the international council on systems engineering (INCOSE), Toulouse, France, 20–24 June.
22.
ParviainenPTihinenMLormansM. (2004) Requirements engineering: dealing with the complexity of sociotechnical systems development. In: MateJLSilvaA (eds) Requirements Engineering for Sociotechnical Systems. Hershey, PA: IdeaGroup Inc., ch. 1, pp.1–20.
23.
RasmussenJ (1997) Risk management in a dynamic society: a modelling problem. Safety Science27(2–3): 183–213.
24.
Robertson (2010) Volere Requirements Specification Template. 15th ed.Atlantic Systems Guild.
25.
SAE Aerospace (2004) SAE AS550 (2006) 6: Architecture Analysis and Design Language (AADL). SAE International.
26.
SahraouiAEKBuedeDSageA (2004) Issues in systems engineering research. In: INCOSE congress, Toulouse, France, 20–24June.
27.
ValerdiRWheatonM (2005) ANSI/EIA 632 as a standardized WBS for COSYSMO. In: AIAA 5th aviation, technology, integration and operations conference (ATIO), Arlington, VA, 26–28 September.
28.
VerriesJPaludettoMSaharaouiA-E-K (2008) From design with SysML to VHDL-AMS simulation. In: Proceeding of ESM’ 08, Le Havre, France, October, pp.115–120, 27–29October.
29.
WuWKellyTP (2006) Deriving safety requirements as part of system architecture definition. In: Proceedings of 24th international system safety conference, published by the system safety society, Albuquerque, NM, 22–27 August (the conference was held in 2005 but the paper was published by the system safety society in 2006).
30.
ZeiglerBPPraehoferHKimTG (2000) Theory of Modelling and Simulation. San Diego, CA: Academic Press.
