Atnaujinkite slapukų nuostatas

Model-based System and Architecture Engineering with the Arcadia Method [Kietas viršelis]

3.50/5 (4 ratings by Goodreads)
(Thales Corporate Engineering, France)
  • Formatas: Hardback, 388 pages, aukštis x plotis: 229x152 mm, weight: 800 g
  • Išleidimo metai: 22-Nov-2017
  • Leidėjas: ISTE Press Ltd - Elsevier Inc
  • ISBN-10: 178548169X
  • ISBN-13: 9781785481697
Kitos knygos pagal šią temą:
Model-based System and Architecture Engineering with the Arcadia MethodDidesnis paveikslėlis
  • Formatas: Hardback, 388 pages, aukštis x plotis: 229x152 mm, weight: 800 g
  • Išleidimo metai: 22-Nov-2017
  • Leidėjas: ISTE Press Ltd - Elsevier Inc
  • ISBN-10: 178548169X
  • ISBN-13: 9781785481697
Kitos knygos pagal šią temą:
Pastovi nuoroda: https://www.kriso.lt/db/9781785481697.html
Raktažodžiai:

This book presents ARCADIA—a tooled method devoted to systems and architecture engineering, especially for those dealing with strong constraints to be reconciled (cost, performance, safety, security, reuse, consumption, weight). The book describes the detailed reasoning necessary to: understand the real customer need; define and share the product architecture among all engineering stakeholders; early validate its design and justify it; and ease and master integration, validation, verification and qualification (IVVQ).

  • Offers a comprehensive examination of systems engineering, including the use of models to support it
  • Not only yet another book on modeling, but rather a journey in systems engineering, enlightening the use of models to support it.
  • Focuses on solitary modeling tasks while also covering prime collaborations between engineering stakeholders
  • Examines modeling techniques to capture and share architecture and to early verify it against need and non-functional constraints
  • Addresses subjects not usually covered by model-based system engineering (MBSE) methods, such as co-engineering with specialties, system/sub-system co-engineering, integration verification and validation
  • Features a powerful, dedicated tool (Capella)
  • Covers a range of topics, including an introduction to system engineering issues, an introduction to MBSE, a presentation of the method for beginners and a handy reference manual for advanced users
Preface xv
Part 1 Foundations of the Method: General Approach and Major Prospects
1(148)
Chapter 1 Motivations, Background and Introduction to Arcadia
3(12)
1.1 Context and challenges
3(1)
1.2 A bit of history: the creation of a method
4(6)
1.2.1 Evolution of engineering
4(1)
1.2.2 2001--2006: First experiments using a model-based approach
5(1)
1.2.3 2006: From an engineering transformation plan toward a method
6(1)
1.2.4 First deployments - new setbacks
7(1)
1.2.5 Transition to an agile definition process of the method
8(1)
1.2.6 Global operational deployment and maturity
8(2)
1.3 Scope of application of Arcadia
10(2)
1.3.1 The collaborative development of the architecture, not the exploration
10(1)
1.3.2 Cooperation with experts, but not their core profession
11(1)
1.3.3 Definition and design of the architecture, not its development
11(1)
1.3.4 Some very broad application scopes and areas
11(1)
1.4 Arcadia presentation
12(3)
Chapter 2 Main Perspectives Structuring the Modeling Approach
15(4)
2.1 From the need to the solution
15(1)
2.1.1 Operational analysis (or OA)
15(1)
2.1.2 System needs analysis (or SA)
15(1)
2.1.3 Logical architecture (or LA)
16(1)
2.1.4 Physical architecture (or PA)
16(1)
2.1.5 Product building strategy (or BS)
16(1)
2.2 Overview of the main concepts
16(2)
2.3 An illustrative example: traffic regulation in the vicinity of a level crossing
18(1)
Chapter 3 Adaptation to Project Context and Life Cycle
19(6)
3.1 Iterative or incremental approach
20(1)
3.2 Scheduling activities
21(1)
3.3 Top-down or bottom-up approach
21(1)
3.4 Progressive and focused architecture construction
22(1)
3.5 Activity adjustment and adaptation to a particular area
23(2)
Chapter 4 General Approach to Functional Analysis
25(22)
4.1 The role of functional analysis in Arcadia
25(1)
4.2 General principles of functional analysis in Arcadia
26(6)
4.2.1 Functions and exchanges
26(2)
4.2.2 Missions, capabilities, functional chains and scenarios
28(2)
4.2.3 States and modes
30(1)
4.2.4 Data model
31(1)
4.2.5 Non-functional characterization and analysis viewpoints
32(1)
4.2.6 Summary
32(1)
4.3 Functional analysis construction approach
32(15)
4.3.1 Top-down hierarchical approach
32(5)
4.3.2 Functional grouping bottom-up approach
37(2)
4.3.3 Functional construction/allocation approach
39(2)
4.3.4 Service functions and traversal functional chains based approach
41(2)
4.3.5 Use case scenario based approach
43(2)
4.3.6 The practical approach of functional analysis
45(1)
4.3.7 Summary
46(1)
Chapter 5 Operational Analysis
47(16)
5.1 Principles
47(1)
5.2 Define missions and required operational capabilities
48(1)
5.3 Perform operational needs analysis
49(12)
5.4 Summary
61(1)
5.5 Exercise
61(2)
Chapter 6 System Needs Analysis
63(22)
6.1 Principles
63(1)
6.2 Performing a capability compromise analysis
64(3)
6.3 Performing a functional and non-functional needs analysis
67(15)
6.4 Formalizing and consolidating the expression of system needs
82(2)
6.5 Summary
84(1)
6.6 Exercise
84(1)
Chapter 7 Definition of the Principle Architecture or Logical Architecture
85(28)
7.1 Principles
85(1)
7.2 Definition of the factors impacting the architecture and analysis viewpoints
86(2)
7.3 Definition of the behavior principles of the system
88(11)
7.4 Construction of component-based system structuring alternatives
99(12)
7.5 Selection of the architecture alternative offering the best trade-off
111(1)
7.6 Summary
111(1)
7.7 Exercise
112(1)
Chapter 8 Definition of the Finalized Architecture or Physical Architecture
113(28)
8.1 Principles
113(1)
8.2 Definition of the structuring principles of the architecture and behavior
114(2)
8.3 Detail and finalization of the expected system behavior
116(6)
8.4 Construction and rationalization of one or more possible system architectures
122(16)
8.5 Selection, completion and justification of the system architecture retained
138(1)
8.6 Summary
139(1)
8.7 Exercise
140(1)
Chapter 9 Definition of Implementation, Development, Acquisition and Integration Contracts
141(8)
9.1 Principles
141(1)
9.2 Definition of the product breakdown structure
142(2)
9.3 Finalization of development contracts of components to be implemented
144(2)
9.4 Consolidation of the definition of components to be acquired
146(1)
9.5 Definition of the IVV strategy
147(1)
9.6 Summary
148(1)
Part 2 Method in Action: Using Engineering Models
149(134)
Chapter 10 Mixing Viewpoints: Analysis and Specialties
151(14)
10.1 Justification
151(2)
10.2 Principles behind the approach
153(3)
10.3 An illustration of some viewpoints
156(8)
10.3.1 Operational analysis
157(1)
10.3.2 System needs analysis
158(1)
10.3.3 Logical architecture
159(2)
10.3.4 Physical architecture
161(2)
10.3.5 Contracts development
163(1)
10.4 Summary
164(1)
Chapter 11 Requirements Engineering and Modeling
165(8)
11.1 Limits of engineering based only on informal requirements
165(2)
11.2 Using models as a support for expressing requirements
167(2)
11.3 Link between informal and model requirements
169(2)
11.4 Structuring requirements and the model
171(1)
11.5 Summary
171(2)
Chapter 12 Integration, Verification and Validation Approach
173(18)
12.1 Defining and implementing the test strategy
173(9)
12.1.1 Principles
173(2)
12.1.2 Defining the strategy for testing and integration
175(2)
12.1.3 Optimizing multilevel IVV
177(1)
12.1.4 Specifying test means
178(2)
12.1.5 Optimizing progress of the integration
180(2)
12.2 Verifying model requirements
182(3)
12.2.1 Principles
182(1)
12.2.2 Inspection
183(1)
12.2.3 Model analysis
183(1)
12.2.4 Demonstration and tests
184(1)
12.3 Definition and use of scenarios and functional chains in IVV
185(3)
12.4 Verifying informal requirements
188(1)
12.5 Summary
189(2)
Chapter 13 Articulation between Engineering Levels
191(20)
13.1 Principles of the coengineering approach
191(2)
13.2 Responsibility and limits of each engineering
193(1)
13.3 Articulation by informal requirements only
194(2)
13.4 Model-based articulation
196(10)
13.4.1 Single component transition
196(4)
13.4.2 Multicomponent transition
200(4)
13.4.3 Reusable component-based construction
204(1)
13.4.4 Transition to design and development engineering
204(2)
13.5 Articulation with the customer
206(2)
13.5.1 Articulation between final customer and lead system supplier
206(1)
13.5.2 Articulation between the lead supplier and a subsystem supplier
207(1)
13.6 Summary
208(3)
Chapter 14 System Supervision, States and Modes
211(22)
14.1 Introduction to supervision
211(1)
14.2 Principles and concepts
211(6)
14.3 Articulation between states and modes in Arcadia perspectives
217(3)
14.3.1 States and modes in operational analysis
217(1)
14.3.2 States and modes in system needs analysis
218(1)
14.3.3 States and modes in logical architecture
218(1)
14.3.4 States and modes in physical architecture
219(1)
14.3.5 States and modes between engineering levels
219(1)
14.4 Approach to defining states and modes and the system supervision
220(6)
14.4.1 Definition of expected behaviors
220(2)
14.4.2 Analysis of superpositions of modes and states
222(3)
14.4.3 Adapting architecture to superpositions
225(1)
14.5 Designing supervision associated with system and components states and modes
226(4)
14.5.1 Supervision functions and behavior
226(1)
14.5.2 Articulation between system and components supervision
227(2)
14.5.3 Analysis and verification of the conditions for system reconfigurations
229(1)
14.6 Using the model for startup and shutdown procedures
230(1)
14.7 Summary
231(2)
Chapter 15 Contribution to Product Line Engineering
233(50)
15.1 Context and position of the problem
233(2)
15.2 General approach to product line engineering
235(4)
15.2.1 Principles of the approach
235(1)
15.2.2 Drivers and key activities in the approach
236(1)
15.2.3 Benefits of the approach
237(2)
15.3 Joint construction of architecture and product variability
239(39)
15.3.1 Market analysis in operational analysis
239(7)
15.3.2 Defining customer options in system needs analysis
246(12)
15.3.3 Designing a logical and physical architecture compatible with the product policy
258(17)
15.3.4 Deriving a configuration for a given customer or product using a subtractive approach
275(3)
15.4 Additive or compositional engineering by building blocks
278(3)
15.4.1 Engineering using reusable components, building blocks
278(1)
15.4.2 Building a base of reusable components
279(1)
15.4.3 Defining a configuration by reusing components in an additive approach
280(1)
15.5 Articulating system and subsystem product lines
281(1)
15.6 Summary
282(1)
Part 3 Encyclopedia of the Language and Glossary of the Concepts of Arcadia
283(70)
Chapter 16 Introduction to Arcadia Modeling Language
285(4)
16.1 The perimeter addressed
285(1)
16.2 The logic behind presenting these concepts
286(1)
16.3 Conventions for representation in figures and diagrams
287(2)
Chapter 17 Concepts of Functional and Operational Description
289(16)
17.1 Concepts and relationships of functional description
289(1)
17.2 Function
290(1)
17.3 Function port
291(1)
17.4 Functional exchange and exchange category
291(1)
17.5 Synthetic representation of functions and functional exchanges
292(1)
17.6 Dataflow and flow control functions
293(3)
17.7 System mission
296(1)
17.8 System capability
296(1)
17.9 Functional chain
296(3)
17.10 Function scenario
299(1)
17.11 Orchestration
300(1)
17.12 Concepts and functional relationships in operational analysis
300(1)
17.13 Operational activity
301(1)
17.14 Operational interaction
302(1)
17.15 Operational mission
302(1)
17.16 Operational capability
302(1)
17.17 Operational process
302(1)
17.18 Operational activity scenario
303(2)
Chapter 18 Concepts of States and Modes
305(4)
18.1 Concepts and relationships involved in states and modes
305(1)
18.2 Mode
305(1)
18.3 State
306(1)
18.4 Transition
306(1)
18.5 Mode/state machine
307(1)
18.6 Configuration
307(1)
18.7 Situation
308(1)
Chapter 19 Concepts of Structural Description
309(10)
19.1 Concepts and relationships of structural description
309(1)
19.2 System
310(1)
19.3 Actor
310(1)
19.4 Component
310(1)
19.5 Behavioral component
310(1)
19.6 Behavioral port
310(1)
19.7 Behavioral exchange
311(1)
19.8 Logical component
312(1)
19.9 Hosting physical component
312(1)
19.10 Physical port
312(1)
19.11 Physical link
312(2)
19.12 Physical path
314(1)
19.13 Behavioral component scenario
314(1)
19.14 Structural concepts and relationships in operational analysis
315(1)
19.15 Operational entity and actor
316(1)
19.16 Communication means
316(1)
19.17 Configuration item
316(3)
Chapter 20 Links between Functional and Structural Descriptions
319(10)
20.1 Concepts and relationships between functional and structural descriptions
319(1)
20.2 Performing functions
319(2)
20.3 Implementing functional ports
321(1)
20.4 Implementing functional exchanges
321(1)
20.5 Functional path
322(1)
20.6 Functional component scenario
322(2)
20.7 Links between dataflow, states and modes, and scenarios or functional chains
324(1)
20.8 Links between functional and structural descriptions in operational analysis
325(1)
20.9 Simplifications in representation
326(3)
Chapter 21 Data Exchange Concepts and Links with Functional and Structural Concepts
329(8)
21.1 Concepts and relationships involved in data exchanges and their use
329(1)
21.2 Exchange item
330(1)
21.3 Data model, class
330(1)
21.4 Allocating exchange items to functional ports and exchanges
331(1)
21.5 Allocating exchange items to behavioral exchanges
332(1)
21.6 Types and instances of data
332(1)
21.7 Interfaces
332(1)
21.8 Allocating interfaces to behavioral component ports
332(1)
21.9 Links between exchanges, exchange items and interfaces
333(1)
21.10 Interaction roles and interface usage
334(1)
21.11 Interaction protocol
335(2)
Chapter 22 Additional Concepts
337(4)
22.1 Concepts for product line engineering
337(1)
22.1.1 Variant
337(1)
22.1.2 Variation point
337(1)
22.1.3 Variability model
338(1)
22.1.4 Project configuration
338(1)
22.2 Concepts for the integration, verification and validation approach
338(1)
22.2.1 Integration version
338(1)
22.2.2 Functional version
338(1)
22.2.3 Component functional contents
339(1)
22.2.4 Integration configuration
339(1)
22.2.5 IVV strategy
339(1)
22.2.6 Test case
339(1)
22.2.7 Test campaign
339(1)
22.3 Other concepts not detailed here
339(2)
Chapter 23 Building the Global Model
341(12)
23.1 The structure of an Arcadia model
341(2)
23.2 Model segmentation to support alternatives
343(2)
23.3 Using language concepts in perspectives
345(3)
23.3.1 Operational analysis
346(1)
23.3.2 System needs analysis
346(1)
23.3.3 Logical architecture
347(1)
23.3.4 Physical architecture
347(1)
23.3.5 Product breakdown structure
348(1)
23.4 Scope of links in the model
348(1)
23.5 Traceability between model elements
349(1)
23.6 Replicable Element Collection and Replica
350(3)
Conclusion and Perspectives 353(4)
Appendix 357(6)
Bibliography 363(4)
Index 367
Jean-Luc Voirin is Systems Technical Director at Thales. A software and system architect, he has worked for 15 years on modeling methods and tools. He is the author of the Arcadia method for model-based system engineering, and is also a coach for deployment of the method.