| Description |
1 online resource |
| Series |
Implementation of model based system engineering set |
|
Implementation of model based system engineering set
|
| Contents |
Machine generated contents note: pt. 1 Foundations of the Method: General Approach and Major Prospects -- ch. 1 Motivations, Background and Introduction to Arcadia -- 1.1. Context and challenges -- 1.2. bit of history: the creation of a method -- 1.2.1. Evolution of engineering -- 1.2.2. 2001 -- 2006: First experiments using a model-based approach -- 1.2.3. 2006: From an engineering transformation plan toward a method -- 1.2.4. First deployments -- new setbacks -- 1.2.5. Transition to an agile definition process of the method -- 1.2.6. Global operational deployment and maturity -- 1.3. Scope of application of Arcadia -- 1.3.1. collaborative development of the architecture, not the exploration -- 1.3.2. Cooperation with experts, but not their core profession -- 1.3.3. Definition and design of the architecture, not its development -- 1.3.4. Some very broad application scopes and areas -- 1.4. Arcadia presentation -- ch. 2 Main Perspectives Structuring the Modeling Approach -- 2.1. From the need to the solution -- 2.1.1. Operational analysis (or OA) -- 2.1.2. System needs analysis (or SA) -- 2.1.3. Logical architecture (or LA) -- 2.1.4. Physical architecture (or PA) -- 2.1.5. Product building strategy (or BS) -- 2.2. Overview of the main concepts -- 2.3. illustrative example: traffic regulation in the vicinity of a level crossing -- ch. 3 Adaptation to Project Context and Life Cycle -- 3.1. Iterative or incremental approach -- 3.2. Scheduling activities -- 3.3. Top-down or bottom-up approach -- 3.4. Progressive and focused architecture construction -- 3.5. Activity adjustment and adaptation to a particular area -- ch. 4 General Approach to Functional Analysis -- 4.1. role of functional analysis in Arcadia -- 4.2. General principles of functional analysis in Arcadia -- 4.2.1. Functions and exchanges -- 4.2.2. Missions, capabilities, functional chains and scenarios -- 4.2.3. States and modes -- 4.2.4. Data model -- 4.2.5. Non-functional characterization and analysis viewpoints -- 4.2.6. Summary -- 4.3. Functional analysis construction approach -- 4.3.1. Top-down hierarchical approach -- 4.3.2. Functional grouping bottom-up approach -- 4.3.3. Functional construction/allocation approach -- 4.3.4. Service functions and traversal functional chains based approach -- 4.3.5. Use case scenario based approach -- 4.3.6. practical approach of functional analysis -- 4.3.7. Summary -- ch. 5 Operational Analysis -- 5.1. Principles -- 5.2. Define missions and required operational capabilities -- 5.3. Perform operational needs analysis -- 5.4. Summary -- 5.5. Exercise -- ch. 6 System Needs Analysis -- 6.1. Principles -- 6.2. Performing a capability compromise analysis -- 6.3. Performing a functional and non-functional needs analysis -- 6.4. Formalizing and consolidating the expression of system needs -- 6.5. Summary -- 6.6. Exercise -- ch. 7 Definition of the Principle Architecture or Logical Architecture -- 7.1. Principles -- 7.2. Definition of the factors impacting the architecture and analysis viewpoints -- 7.3. Definition of the behavior principles of the system -- 7.4. Construction of component-based system structuring alternatives -- 7.5. Selection of the architecture alternative offering the best trade-off -- 7.6. Summary -- 7.7. Exercise -- ch. 8 Definition of the Finalized Architecture or Physical Architecture -- 8.1. Principles -- 8.2. Definition of the structuring principles of the architecture and behavior -- 8.3. Detail and finalization of the expected system behavior -- 8.4. Construction and rationalization of one or more possible system architectures -- 8.5. Selection, completion and justification of the system architecture retained -- 8.6. Summary -- 8.7. Exercise -- ch. 9 Definition of Implementation, Development, Acquisition and Integration Contracts -- 9.1. Principles -- 9.2. Definition of the product breakdown structure -- 9.3. Finalization of development contracts of components to be implemented -- 9.4. Consolidation of the definition of components to be acquired -- 9.5. Definition of the IVV strategy -- 9.6. Summary -- pt. 2 Method in Action: Using Engineering Models -- ch. 10 Mixing Viewpoints: Analysis and Specialties -- 10.1. Justification -- 10.2. Principles behind the approach -- 10.3. illustration of some viewpoints -- 10.3.1. Operational analysis -- 10.3.2. System needs analysis -- 10.3.3. Logical architecture -- 10.3.4. Physical architecture -- 10.3.5. Contracts development -- 10.4. Summary -- ch. 11 Requirements Engineering and Modeling -- 11.1. Limits of engineering based only on informal requirements -- 11.2. Using models as a support for expressing requirements -- 11.3. Link between informal and model requirements -- 11.4. Structuring requirements and the model -- 11.5. Summary -- ch. 12 Integration, Verification and Validation Approach -- 12.1. Defining and implementing the test strategy -- 12.1.1. Principles -- 12.1.2. Defining the strategy for testing and integration -- 12.1.3. Optimizing multilevel IVV -- 12.1.4. Specifying test means -- 12.1.5. Optimizing progress of the integration -- 12.2. Verifying model requirements -- 12.2.1. Principles -- 12.2.2. Inspection -- 12.2.3. Model analysis -- 12.2.4. Demonstration and tests -- 12.3. Definition and use of scenarios and functional chains in IVV -- 12.4. Verifying informal requirements -- 12.5. Summary -- ch. 13 Articulation between Engineering Levels -- 13.1. Principles of the coengineering approach -- 13.2. Responsibility and limits of each engineering -- 13.3. Articulation by informal requirements only -- 13.4. Model-based articulation -- 13.4.1. Single component transition -- 13.4.2. Multicomponent transition -- 13.4.3. Reusable component-based construction -- 13.4.4. Transition to design and development engineering -- 13.5. Articulation with the customer -- 13.5.1. Articulation between final customer and lead system supplier -- 13.5.2. Articulation between the lead supplier and a subsystem supplier -- 13.6. Summary -- ch. 14 System Supervision, States and Modes -- 14.1. Introduction to supervision -- 14.2. Principles and concepts -- 14.3. Articulation between states and modes in Arcadia perspectives -- 14.3.1. States and modes in operational analysis -- 14.3.2. States and modes in system needs analysis -- 14.3.3. States and modes in logical architecture -- 14.3.4. States and modes in physical architecture -- 14.3.5. States and modes between engineering levels -- 14.4. Approach to defining states and modes and the system supervision -- 14.4.1. Definition of expected behaviors -- 14.4.2. Analysis of superpositions of modes and states -- 14.4.3. Adapting architecture to superpositions -- 14.5. Designing supervision associated with system and components states and modes -- 14.5.1. Supervision functions and behavior -- 14.5.2. Articulation between system and components supervision -- 14.5.3. Analysis and verification of the conditions for system reconfigurations -- 14.6. Using the model for startup and shutdown procedures -- 14.7. Summary -- ch |
|
15 Contribution to Product Line Engineering -- 15.1. Context and position of the problem -- 15.2. General approach to product line engineering -- 15.2.1. Principles of the approach -- 15.2.2. Drivers and key activities in the approach -- 15.2.3. Benefits of the approach -- 15.3. Joint construction of architecture and product variability -- 15.3.1. Market analysis in operational analysis -- 15.3.2. Defining customer options in system needs analysis -- 15.3.3. Designing a logical and physical architecture compatible with the product policy -- 15.3.4. Deriving a configuration for a given customer or product using a subtractive approach -- 15.4. Additive or compositional engineering by building blocks -- 15.4.1. Engineering using reusable components, building blocks -- 15.4.2. Building a base of reusable components -- 15.4.3. Defining a configuration by reusing components in an additive approach -- 15.5. Articulating system and subsystem product lines -- 15.6. Summary -- pt. 3 Encyclopedia of the Language and Glossary of the Concepts of Arcadia -- ch. 16 Introduction to Arcadia Modeling Language -- 16.1. perimeter addressed -- 16.2. logic behind presenting these concepts -- 16.3. Conventions for representation in figures and diagrams -- ch. 17 Concepts of Functional and Operational Description -- 17.1. Concepts and relationships of functional description -- 17.2. Function -- 17.3. Function port -- 17.4. Functional exchange and exchange category -- 17.5. Synthetic representation of functions and functional exchanges -- 17.6. Dataflow and flow control functions -- 17.7. System mission -- 17.8. System capability -- 17.9. Functional chain -- 17.10. Function scenario -- 17.11. Orchestration -- 17.12. Concepts and functional relationships in operational analysis -- 17.13. Operational activity -- 17.14. Operational interaction -- 17.15. Operational mission -- 17.16. Operational capability -- 17.17. Operational process -- 17.18. Operational activity scenario -- ch. 18 Concepts of States and Modes -- 18.1. Concepts and relationships involved in states and modes -- 18.2. Mode -- 18.3. State -- 18.4. Transition -- 18.5. Mode/state machine -- 18.6. Configuration -- 18.7. Situation -- ch. 19 Concepts of Structural Description -- 19.1. Concepts and relationships of structural description -- 19.2. System |
|
Note continued: 19.3. Actor -- 19.4. Component -- 19.5. Behavioral component -- 19.6. Behavioral port -- 19.7. Behavioral exchange -- 19.8. Logical component -- 19.9. Hosting physical component -- 19.10. Physical port -- 19.11. Physical link -- 19.12. Physical path -- 19.13. Behavioral component scenario -- 19.14. Structural concepts and relationships in operational analysis -- 19.15. Operational entity and actor -- 19.16. Communication means -- 19.17. Configuration item -- ch. 20 Links between Functional and Structural Descriptions -- 20.1. Concepts and relationships between functional and structural descriptions -- 20.2. Performing functions -- 20.3. Implementing functional ports -- 20.4. Implementing functional exchanges -- 20.5. Functional path -- 20.6. Functional component scenario -- 20.7. Links between dataflow, states and modes, and scenarios or functional chains -- 20.8. Links between functional and structural descriptions in operational analysis -- 20.9. Simplifications in representation -- ch. 21 Data Exchange Concepts and Links with Functional and Structural Concepts -- 21.1. Concepts and relationships involved in data exchanges and their use -- 21.2. Exchange item -- 21.3. Data model, class -- 21.4. Allocating exchange items to functional ports and exchanges -- 21.5. Allocating exchange items to behavioral exchanges -- 21.6. Types and instances of data -- 21.7. Interfaces -- 21.8. Allocating interfaces to behavioral component ports -- 21.9. Links between exchanges, exchange items and interfaces -- 21.10. Interaction roles and interface usage -- 21.11. Interaction protocol -- ch. 22 Additional Concepts -- 22.1. Concepts for product line engineering -- 22.1.1. Variant -- 22.1.2. Variation point -- 22.1.3. Variability model -- 22.1.4. Project configuration -- 22.2. Concepts for the integration, verification and validation approach -- 22.2.1. Integration version -- 22.2.2. Functional version -- 22.2.3. Component functional contents -- 22.2.4. Integration configuration -- 22.2.5. IVV strategy -- 22.2.6. Test case -- 22.2.7. Test campaign -- 22.3. Other concepts not detailed here -- ch. 23 Building the Global Model -- 23.1. structure of an Arcadia model -- 23.2. Model segmentation to support alternatives -- 23.3. Using language concepts in perspectives -- 23.3.1. Operational analysis -- 23.3.2. System needs analysis -- 23.3.3. Logical architecture -- 23.3.4. Physical architecture -- 23.3.5. Product breakdown structure -- 23.4. Scope of links in the model -- 23.5. Traceability between model elements -- 23.6. Replicable Element Collection and Replica |
| Summary |
Arcadia is a system engineering method based on the use of models, with a focus on the collaborative definition, evaluation and exploitation of its architecture. This book describes the fundamentals of the method and its contribution to engineering issues such as requirements management, product line, system supervision, and integration, verification and validation (IVV). It provides a reference for the modeling language defined by Arcadia. The author discusses the range of applications, from the assessment of different architectures and their suitability, to the collaboration between system engineering, specialties such as safety or security, subsystems engineering teams, software and hardware. This is illustrated by several examples of representative models which constitute a common thread |
| Bibliography |
Includes bibliographical references and index |
| Notes |
Vendor-supplied metadata |
| Subject |
Systems engineering.
|
|
System design.
|
|
Model-driven software architecture.
|
|
systems engineering.
|
|
TECHNOLOGY & ENGINEERING -- Engineering (General)
|
|
TECHNOLOGY & ENGINEERING -- Reference.
|
|
Model-driven software architecture
|
|
System design
|
|
Systems engineering
|
| Form |
Electronic book
|
| ISBN |
9780081017944 |
|
0081017944 |
|
178548169X |
|
9781785481697 |
|
