With the growing maturity of information and communication technologies, systems have been interconnected within growing networks, yielding new services through a combination of the system functionalities. This leads to an increasing complexity that has to be managed in order to take advantage of these system integrations. This book provides key answers as to how such systems of systems can be engineered and how their complexity can be mastered. After reviewing some definitions on systems of systems engineering, the book focuses on concrete applications and offers a survey of the activities and techniques that allow engineering of complex systems and systems of systems. Case studies, ranging from emergency situations such as Hurricane Katrina and its crisis management or a generic scenario of a major traffic accident and its emergency response, to the establishment of a scientific basis in the Antarctic region illustrate key factors of success and traps to avoid in order to cope with such situations.

Dominique Luzeaux has been employed by the French Ministry of Defense for over 20 years. He was Director of the Complex System Engineering Department from 2002 to 2004, and Chief Information Officer from 2005 to 2007. He is currently Director for Land Systems acquisition. He has written over 60 articles in international conferences and journals, and teaches robotics, theoretical computer science and system engineering at graduate level. He has co-authored a book on nanotechnology and microsystems, as well as books on systems of systems.

Jean-René Ruault was hired in 2004 by the French Ministry of Defense as an expert in systems engineering, standardization and human factors. He has published several articles on systems engineering and human-computer interactions, and was co-chairman of the ERGO-IA'06 conference as well as co-authoring books on systems of systems.

Jean-Luc Wippler has worked as a systems architect for over 20 years in fields such as defense systems, spatial systems, intelligence, and air traffic management. He has also been teaching systems engineering at graduate level for many years.

Author Biographies	p. xi
Introduction	p. xv
Engineering Large-Scale Complex Systems and Emergency Situation Management	p. 1
Engineering Large-scale Complex Systems	p. 3
Introduction	p. 3
The notion of service in large complex systems	p. 7
Architecture: a key concept	p. 11
Towards resilient systems	p. 13
Resilience: definitions	p. 14
Resilience versus dependability	p. 17
Engineering resilience	p. 18
Development of relationships between participants	p. 28
Complexity: plurality of viewpoints for systems engineering	p. 35
The maintenance and logistics of systems of systems	p. 59
Perspectives and lines of enquiry	p. 61
Contextual elements	p. 61
Factors of influence	p. 64
Trends, issues and challenges in systems engineering	p. 66
Development of the engineering process	p. 71
Themes of research	p. 76
Conclusion	p. 79
Bibliography	p. 82
Management of Emergency Situations: Architecture and Engineering of Systems of Systems	p. 85
Introduction	p. 85
Main concepts of systems engineering	p. 86
Context of the emergency situation management scenario	p. 89
Global context: Tairétalet	p. 89
Synthesis of the Dubbus accident report	p. 90
Decision of the Tairétalet authorities	p. 92
Analysis of context and participants involved	p. 96
Results of studies on existing resources	p. 99
Emergency situation management scenario: perimeter and architecture	p. 102
Reference operational scenario	p. 102
Alternative operational scenarios	p. 108
Perimeter and component systems of the system of systems	p. 109
System dimensions: lines of development	p. 111
Architecture of component systems of the system of systems	p. 116
Detecting an accident: the accident detection system	p. 116
Evaluating the gravity of an accident, coordinating the emergency services and allocating casualties to hospitals: the regional call center	p. 135
Casualty evacuation: emergency service centers and hospitals	p. 175
Continuous improvement of emergency situation management	p. 176
Systems engineering for the regional call center, emergency service centers and hospitals	p. 176
Specificities of system of systems engineering	p. 195
Conclusion	p. 197
Acknowledgements	p. 197
Bibliography	p. 198
Case Study: Antarctica Life Support Facility	p. 205
Introduction to the Antarctica Life Support Facility Case Study	p. 207
Why Antarctica?	p. 208
Fictional context of the study	p. 209
The Antarctica mission	p. 209
The cast of characters	p. 211
Some data on the Antarctic and Adélie Land	p. 212
Geography	p. 212
Climate	p. 212
Biological patrimony	p. 213
Location of the life support facility	p. 213
Bibliography	p. 213
Finding the Right Problem	p. 215
What system are we dealing with?	p. 216
Purpose and missions	p. 217
The system perimeter	p. 219
System lifecycle	p. 221
Who does the system involve?	p. 226
Creating a working framework	p. 228
Gathering information	p. 229
Modeling the context	p. 235
Understanding and defining goals	p. 236
Modeling the domain	p. 241
Defining stakeholder requirements and constraints	p. 247
Things to remember: stakeholder-requirements engineering	p. 251
Bibliography	p. 252
Who Can Solve the Problem?	p. 255
Consultation and selection	p. 256
Establishment of an acquisition plan	p. 256
Creating an initial list of companies	p. 258
Organizing and launching a request for information	p. 259
Selecting companies for the call to tender	p. 260
Preparing and launching the call to tender	p. 261
Selecting a partner company	p. 261
Responding (and winning)	p. 262
Approaching the problem	p. 262
Advancing into the unknown	p. 263
Where should we start?	p. 265
Doing it all simultaneously	p. 269
Committing to a "right" definition of the system to be created	p. 272
From stakeholder requirements to technical requirements	p. 273
Covering the whole of the System's lifecycle	p. 274
Accounting for stakeholder expectations and constraints	p. 276
Remaining realistic	p. 277
Removing major risks	p. 278
Facing identified threats	p. 279
Use of precise terminology	p. 282
Creating the list of technical requirements	p. 284
Creating the necessary model	p. 284
Expressing the "right" technical requirements	p. 286
Compliance with the specification	p. 288
Things to remember: technical requirements engineering	p. 290
Bibliography	p. 291
Solving the Problem	p. 293
General approach	p. 294
Functional design	p. 297
A brief introduction to functional design	p. 297
Application	p. 300
Physical design	p. 313
Identifying physical components	p. 313
Allocation of functions to identified components	p. 315
Grouping components by sub-system	p. 318
Architecture of (some) sub-systems	p. 321
Sub-systems architecture of the life support facility	p. 324
Interfaces	p. 326
Waste management	p. 330
Centralized supervision	p. 331
Other types of interactions between components	p. 332
The "playing fields" of the systems architect	p. 333
EFFBDs	p. 336
An informal introduction to EFFBD diagrams	p. 336
Syntax and structure of EFFBDs	p. 338
Formalization of EFFBDs	p. 338
Verification and validation of EFFBDs	p. 340
Things to remember: architectural design	p. 342
Bibliography	p. 343
Solving the Problem Completely, in a Coherent and Optimal Manner	p. 345
Making the right technical decisions at the right level and the right time	p. 347
Formalizing possibilities	p. 348
Using a multi-criteria analytical approach	p. 350
Reinforcing and optimizing choices	p. 360
Things to remember	p. 363
Integrating disciplines	p. 366
Integrating dependability	p. 368
Integrating the human factor	p. 380
Things to remember	p. 389
Bibliography	p. 391
Anticipating Integration, Verification and Validation	p. 393
Positioning integration, verification and validation	p. 395
Integration, verification and validation in the system's lifecycle	p. 403
Analyzing input	p. 405
Establishing an integration, verification and validation strategy	p. 407
Identifying integration, verification and validation objectives	p. 408
Stages of integration, verification and validation	p. 415
Defining the infrastructure	p. 419
Platforms	p. 419
Tools	p. 420
Data	p. 422
Integration, verification and validation organization	p. 422
Choosing techniques	p. 423
Review	p. 424
Testing	p. 425
Traceability	p. 426
Things to remember: integration, verification and validation	p. 427
Activities linked to engineering	p. 427
Anticipation	p. 427
A multi-faceted approach	p. 428
Strategy: a key point	p. 428
The IW manager: a high-pressure role	p. 429
Bibliography	p. 429
Conclusion to the "Antarctica Life Support Facility" Case Study	p. 431
"Before we can manage a solution, we need to find one!"	p. 432
"Modeling isn't drawing!"	p. 434
Implementing systems engineering	p. 437
Acknowledgements	p. 439
Bibliography	p. 440
Conclusion	p. 441
List of Authors	p. 443
Index	p. 445
Table of Contents provided by Ingram. All Rights Reserved.

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.