Systems Engineering: Analysis, Modeling and Simulation of Systems

Cover
Title Page
Copyright Page
Contents
Foreword
Acknowledgments
Introduction
Part 1. Systems Theory
	Chapter 1. Systems Theory
		1.1. The definition of a system
		1.2. Definition of a complex system
		1.3. Definition of a system of systems
		1.4. The systems approach
			1.4.1. The reductionist approach
			1.4.2. The holistic approach
			1.4.3. The analytical and systemic approach
			1.4.4. The emergence
		1.5. The systemic method
			1.5.1. Systemic exploration
			1.5.2. Qualitative modeling
			1.5.3. Quantitative modeling
			1.5.4. The simulation
		1.6. How to understand the complexity of a system
			1.6.1. Theme 1: the system is in an environment
			1.6.2. Theme 2: the system is structured
			1.6.3. Theme 3: the system evolves over time and has a dynamic
			1.6.4. Theme 4: the system is controlled
		1.7. Conclusion on systems theory
Part 2. Systems and Requirements Engineering
	Chapter 2. Introduction to Systems Engineering
		2.1. The system meets needs
			2.1.1. Definition of a need
		2.2. Definition of a stakeholder requirement
		2.3. How to go from need to system
		2.4. Definition of systems engineering
		2.5. Iterative systems engineering process
			2.5.1. Prescription and system construction
			2.5.2. Needs analysis
			2.5.3. Requirements specification
			2.5.4. Functional and logical design
			2.5.5. Physical design
			2.5.6. Verification and validation
			2.5.7. Evaluation and comparison
			2.5.8. The requirements cycle
		2.6. System architecture
		2.7. V-cycle
		2.8. W-cycle
		2.9. Conclusion on systems engineering
	Chapter 3. Introduction to Requirements Engineering
		3.1. Definition of requirements engineering
		3.2. The importance and challenges of requirements engineering
		3.3. Problem domain and solution domain
		3.4. Formalizing stakeholder needs and system requirements
		3.5. Validate system requirements
		3.6. Allocate system requirements to subsystems
		3.7. Validate the allocated requirements of the subsystems
		3.8. Choose the solution: define the requirements of the subsystems
		3.9. Managing requirements
			3.9.1. Why manage requirements?
			3.9.2. What are the risks associated with poor requirements management?
			3.9.3. Managing requirement attributes
			3.9.4. Managing the configuration of requirements
			3.9.5. Managing changes
		3.10. Conclusion on requirements engineering
Part 3. Definition of Requirements
	Chapter 4. Unifying Thread Example
		4.1. Objective of the unifying thread example
		4.2. Presentation of the raw specifications
	Chapter 5. Needs Analysis
		5.1. Objectives of needs analysis
		5.2. Stakeholder identification
			5.2.1. Definition of stakeholder
			5.2.2. PESTEL analysis
			5.2.3. Analysis by type of environment
			5.2.4. Application to the unifying thread example: stakeholder identification
		5.3. Identification of external interactions
			5.3.1. Objectives of identifying external interactions
			5.3.2. Application to the unifying thread example: identification of external interactions
		5.4. Collection of needs
			5.4.1. Why capture needs?
			5.4.2. Methods for collecting needs
			5.4.3. Application to the unifying thread example: formalization of needs
		5.5. Identification of the life cycle
			5.5.1. Building the system life cycle
			5.5.2. Application to the unifying thread example: identifying the life cycle
		5.6. Identification of the system s missions
			5.6.1. Definition of the system s missions
			5.6.2. Application to the unifying thread example: mission definition
		5.7. Identification of operational scenarios
			5.7.1. Defining an operational scenario
			5.7.2. Application to the unifying thread example: definition of operational scenarios
		5.8. Identification of services and constraints
			5.8.1. From missions to services
			5.8.2. Application to the unifying thread example: identification of services and constraints
		5.9. Formalization of stakeholder needs
			5.9.1. The input specifications
			5.9.2. Application to the unifying thread example: formalization of needs
		5.10. Conclusion on needs analysis
	Chapter 6. Requirements Specification
		6.1. Objective of the requirements specification process
		6.2. Identification of the system s functional modes
			6.2.1. Definition and purpose of the functional modes
			6.2.2. What to do to identify functional modes.
			6.2.3. Application to the unifying thread example: identifying the functional modes
		6.4. Identification of system functions
			6.4.1. What is a system function?
			6.4.2. What to do to identify the system functions
			6.4.3. Application to the unifying thread example: identification of system functions
		6.5. Identification of external interactions
		6.6. Defining system behaviors
			6.6.1. Objective of defining the functional behavior of the system
			6.6.2. Application to the unifying thread example: definition of a functional scenario
		6.7. Defining the system requirements
			6.7.1. Why define the system requirements?
			6.7.2. What to do to define the system requirements
			6.7.3. How to define system requirements: application to the unifying thread example
		6.8. System specification
			6.8.1. The specification document
			6.8.2. Application to the unifying thread example: system specification
		6.9. Conclusion on requirements specification
	Chapter 7. Requirements Validation
		7.1. General process
		7.2. Selecting methods and defining validation procedures
		7.3. Establishing requirements traceability
			7.3.1. Establishing traceability from needs to requirements
			7.3.2. Establish traceability from requirements to needs
		7.4. Analysis of assumptions and induced requirements
			7.4.1. Analysis of assumptions
			7.4.2. Analysis of induced requirements
		7.5. Rolling out the validation
			7.5.1. Checking the requirements individually (correctness)
			7.5.2. Globally checking the requirements (consistency)
			7.5.3. Validating requirements against needs
		7.6. Identifying and resolving gaps between needs and requirements
			7.6.1. Identifying gaps and conflicts
			7.6.2. Assessing conflicts
			7.6.3. Study of trade-offs
			7.6.4. Identifying trade-offs and impacts
		7.7. Saving a database of validated requirements
		7.8. Conclusion on requirements validation
Part 4. System Design
	Chapter 8. Functional and Logical Design
		8.1. Design and functional architecture
			8.1.1. Static functional architecture
			8.1.2. Dynamic functional architecture
			8.1.3. Behavioral functional architecture
		8.2. Identifying the sub-functions of the system and their interactions
			8.2.1. Purpose of identifying sub-functions
			8.2.2. Functional chain analysis approach
			8.2.3. Implementation of the unifying thread example: identification of sub-functions
			8.2.4. The outputs of the static architecture
			8.2.5. Rules on the quality of a functional decomposition
		8.3. Functional interface analysis
			8.3.1. The coupling matrices
			8.3.2. Characterizing functional interfaces
		8.4. Consolidation of functional modes
			8.4.1. Objective of consolidating functional modes
			8.4.2. What to do to identify the functional sub-modes
			8.4.3. Application to the unifying thread example: resumption of the functional modes
		8.5. Resuming system functioning
			8.5.1. Objective of the system recovery
			8.5.2. Implementation of the unifying thread example: resumption of the system functioning
		8.6. Propose groupings of sub-functions into logical components
			8.6.1. The use of logical components
			8.6.2. Proposing a schematic diagram of the solution
		8.7. Allocate functional requirements to sub-functions
			8.7.1. Objective of the allocation of system requirements to sub-functions
			8.7.2. Application to the unifying thread example: allocation of system requirements to sub-functions
		8.8. Conclusion on functional design
	Chapter 9. Verification and Validation of the Functional Architecture
		9.1. Verification of the functional architecture
		9.2. Validation of functional architecture
			9.2.1. Selecting methods and defining validation procedures
			9.2.2. Establishing traceability
			9.2.3. Analysis of assumptions
			9.2.4. Unrolling the validation
			9.2.5. Performing the revalidation
			9.2.6. Recording the results of the functional architecture s validation
		9.3. Conclusion on the verification and validation of functional design
	Chapter 10. Physical Design
		10.1. Purpose of physical design
		10.2. Identification of physical components
			10.2.1. Identifying components and allocating technical functions
			10.2.2. Completing the identification of the components with the missions of the system
			10.2.3. Completing the identification of components with non-functional requirements
			10.2.4. Identification of variants in the physical architecture
			10.2.5. Building physical architectures with a product line approach
			10.2.6. Building physical architectures from a logical architecture
			10.2.7. Application to the unifying thread example: identification of components
		10.3. Decomposition of the components
			10.3.1. Architecture principles
			10.3.2. Coupling matrix
			10.3.3. Global coupling quality of an architecture
			10.3.4. The physical tree structure
			10.3.5. The architecture of the components
			10.3.6. Application to the unifying thread example: components and interfaces
		10.4. Characterization of interfaces
		10.5. Identification of system configurations
			10.5.1. Definition of a technical configuration
			10.5.2. Activities to identify technical configurations
			10.5.3. Application to the unifying thread example: identification of configurations
		10.6. Identifying the physical functioning of the system
			10.6.1. Definition of the physical functioning of the system
			10.6.2. Application to the unifying thread example: constructional scenario
		10.7. Allocation and definition of subsystem requirements
			10.7.1. Emergence of properties
			10.7.2. Architecture sizing
			10.7.3. Allocating non-functional requirements
			10.7.4. Definition of subsystem requirements
		10.8. Conclusion on the physical design
	Chapter 11. Verification and Validation of the Physical Architecture
		11.1. Verification of the physical architecture
			11.1.1. Defining physical design verification procedures
			11.1.2. Performing physical design verification
			11.1.3. Rechecking the physical design
			11.1.4. Recording the results of the physical design verification
		11.2. Validation of the physical architecture
		11.3. Conclusion on the verification and validation of the physical architecture
	Chapter 12. Evaluation and Comparison of Solutions
		12.1. Evaluation of architectures
			12.1.1. Selection of common criteria
			12.1.2. Value criteria
			12.1.3. Risk and cost criteria
		12.2. Comparison of architectures
			12.2.1. Selecting stakeholders
			12.2.2. Characterizing the weight of each criterion
			12.2.3. Getting stakeholders to vote
			12.2.4. Comparing architectures
			12.2.5. Justifying architectural choices
		12.3. Conclusion on the evaluation and comparison of the architectures
Part 5. Virtual System Integration
	Chapter 13. Integration on a W-Cycle
		13.1. Virtual integration and real integration
		13.2. Simulation models
		13.3. Conclusion on integration on a W-cycle
	Chapter 14. Creating a Simulable Design Model
		14.1. Defining the simulation objectives
		14.2. Simulation and the systemic approach
		14.3. Analysis and modeling of system architecture
		14.4. Analysis and causal modeling
			14.4.1. Extracting simulation variables
			14.4.2. Relationships between variables
			14.4.3. Feedback loops
			14.4.4. Application to the unifying thread example: causal analysis
		14.5. Formalizing the simulation model
			14.5.1. Classification of variables
			14.5.2. Dynamic modeling
			14.5.3. Application to the unifying thread example: formalization of the causal model
		14.6. Running the simulation
			14.6.1. Identifying and configuring equations
			14.6.2. Configuring the simulation
			14.6.3. Application to the unifying thread example: simulation
		14.7. Analyzing the results
			14.7.1. Purpose of the analysis of the results
			14.7.2. Application to the unifying thread example: analysis of the results
		14.8. Conclusion on the realization of a simulable design model
	Chapter 15. Making a Simulable Specification Model
		15.1. The monitoring model
			15.1.1. Why make a monitoring model?
			15.1.2. How to build a monitoring model
		15.2. Writing structured requirements
			15.2.1. Reminder on the structure of a requirement.
			15.2.2. Application to the unifying thread example: selecting structured requirements
		15.3. Formalizing property requirements
			15.3.1. Properties
			15.3.2. How to formalize a property
			15.3.3. Application to the unifying thread example: formalization of properties
		15.4. Building a monitoring model
			15.4.1. Application to a property
			15.4.2. Creating the specification model
		15.5. Running the simulation
			15.5.1. Connecting the specification model
			15.5.2. Application to the unifying thread example: running the specification model
		15.6. Analyzing the results
			15.6.1. Result from the specification model
			15.6.2. Application to the unifying thread example
		15.7. Conclusion on the realization of a simulable specification model
Part 6. System Integration
	Chapter 16. Using Models
		16.1. Models in systems engineering
		16.2. Typology of models
		16.3. Analytical behavioral models
			16.3.1. Using the behavioral model in V&V
			16.3.2. Model-based design
		16.4. Business analytical models
			16.4.1. Using the business model in V&V
		16.5. Conclusion on the use of models
	Chapter 17. System Integration, Verification and Validation
		17.1. System integration
			17.1.1. Receiving subsystems
			17.1.2. Assembling subsystems
		17.2. Checking the system
			17.2.1. Defining the system verification strategy
			17.2.2. Defining the system verification procedures
			17.2.3. Performing the system check
			17.2.4. Establishing system compliance
		17.3. System validation
			17.3.1. Preparing for validation
			17.3.2. Performing validation
			17.3.3. Analyzing the results
			17.3.4. Saving validation results
		17.4. Conclusion on system integration, verification and validation
General Conclusion
References
Index
EULA