Muutke küpsiste eelistusi

Model-Based System Architecture [Kõva köide]

5.00/5 (2 hinnangut Goodreads-ist)
, , ,
Teised raamatud teemal:
  • Kõva köide
  • Hind: 163,83 €*
  • * saadame teile pakkumise kasutatud raamatule, mille hind võib erineda kodulehel olevast hinnast
  • See raamat on trükist otsas, kuid me saadame teile pakkumise kasutatud raamatule.
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Lisa soovinimekirja
  • Raamatukogudele
Model-Based System ArchitectureSuurem pilt
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9781118893647.html
Märksõnad:
Presents modeling approaches that can be performed in SysML and other modeling languages

This book combines the emerging discipline of systems architecting with model-based approaches using SysML. The early chapters of the book provide the fundamentals of systems architecting; discussing what systems architecting entails and how it benefits systems engineering. Model-based systems engineering is then defined, and its capabilities to develop complex systems on time and in a feasible quality are discussed. The remainder of the book covers important topics such as: architecture descriptions; architecture patterns; perspectives, viewpoints, views and their relation to system architecture; the roles of a system architect, their team, and stakeholders; systems architecting processes; agile approaches to systems architecting; variant modeling techniques; architecture frameworks; and architecture assessment. The book's organization allows experts to read the chapters out of sequence. Novices can read the chapters sequentially to gain a systematic introduction to system architecting.

Model-Based System Architecture: 





Provides comprehensive coverage of the Functional Architecture for Systems (FAS) method created by the authors and based on common MBSE practices Covers architecture frameworks, including the System of Systems, Zachman Frameworks, TOGAF®, and more Includes a consistent example system, the Virtual Museum Tour system, that allows the authors to demonstrate the systems architecting concepts covered in the book

Model-Based System Architecture is a comprehensive reference for system architects and systems engineers in technology companies. This book will also serve as a reference to students and researchers interested in functional architectures. 

Tim Weilkiens is the CEO at the German consultancy oose Innovative Informatik and co-author of the SysML specification. He has introduced model-based systems engineering to a variety of industry sectors.  He is author of several books about modeling and the MBSE methodology SYSMOD.

Jesko G. Lamm is a Senior Systems Engineer at Bernafon, a Swiss manufacturer for hearing instruments. With Tim Weilkiens, Jesko G. Lamm founded the Functional Architectures working group of the German chapter of INCOSE.

Stephan Roth is a coach, consultant, and trainer for systems and software engineering at the German consultancy oose Innovative Informatik. He is a state-certified technical assistant for computer science from Physikalisch-Technische Lehranstalt (PTL) Wedel and a certified systems engineer (GfSE)®- Level C.

Markus Walker works at Schindler Elevator in the research and development division as elevator system architect. He is an INCOSE Certified Systems Engineering Professional (CSEP) and is engaged in the committee of the Swiss chapter of INCOSE.
Foreword xi
Preface xv
About the Companion Website xix
1 Introduction 1(4)
2 An Example: The Virtual Museum Tour System 5(4)
3 Better Products - The Value of Systems Architecting 9(10)
3.1 The Share of Systems Architecting in Making Better Products
9(1)
3.2 The Benefits that can be Achieved
10(4)
3.3 The Benefits that can be Communicated inside the Organization
14(1)
3.4 The Beneficial Elements of Systems Architecting
15(1)
3.5 Benefits of Model-Based Systems Architecting
16(3)
4 Definition of System Architecture 19(8)
4.1 What is Architecture? -Discussion of Some Existing Definitions
20(2)
4.2 Modeling the Definitions of "System" and "System Architecture"
22(5)
5 Model-Based System Architecture 27(8)
6 Architecture Description 35(14)
6.1 Why Spending Effort to Describe the Architecture?
35(2)
6.2 The Architecture Description
37(7)
6.3 How to Get an Architecture Description?
44(5)
7 Architecture Patterns and Principles 49(26)
7.1 The SYSMOD Zigzag Pattern
50(7)
7.2 The Base Architecture
57(4)
7.3 Cohesion and Coupling
61(2)
7.4 Separation of Definition, Usage and Run-Time
63(2)
7.5 Separate Stable from Unstable Parts
65(1)
7.6 The Ideal System
65(1)
7.7 View and Model
66(2)
7.8 Diagram Layout
68(1)
7.9 System Model Structure
69(2)
7.10 Heuristics
71(4)
8 Requirements and Use Case Analysis 75(14)
8.1 Identify and Define Requirements
76(4)
8.2 Specify the System Context
80(2)
8.3 Identify Use Cases
82(2)
8.4 Describe Use Case Flows
84(2)
8.5 Model the Domain Knowledge
86(3)
9 Perspectives, Viewpoints and Views in System Architecture 89(42)
9.1 Overview
89(2)
9.2 The Functional Perspective
91(5)
9.3 The Physical Perspective
96(4)
9.4 The Behavioral Perspective
100(1)
9.5 The Layered Perspective
100(12)
9.6 System Deployment Perspective
112(3)
9.7 Other Perspectives
115(2)
9.8 Relation to the System Context
117(3)
9.9 Mapping Different Perspectives and Levels
120(5)
9.10 Traceability
125(1)
9.11 Perspectives and Views in Model-Based Systems Architecting
125(6)
10 Typical Architecture Stakeholders 131(26)
10.1 Overview
131(2)
10.2 Requirements Engineering
133(2)
10.3 Verification
135(2)
10.4 Configuration Management
137(1)
10.5 Engineering Disciplines
138(3)
10.6 Project and Product Management
141(4)
10.7 Development Roadmap Planners
145(3)
10.8 Production and Distribution
148(1)
10.9 Suppliers
149(1)
10.10 Marketing and Brand Management
150(2)
10.11 Management
152(5)
11 Roles 157(16)
11.1 Roles
157(1)
11.2 The System Architect Role
158(4)
11.3 System Architecture Teams
162(2)
11.4 System Architecture Stakeholders
164(1)
11.5 Recruiting System Architecture People
165(2)
11.6 Talent Development for System Architects
167(6)
12 Processes 173(10)
12.1 The Systems Architecting Processes
173(9)
12.2 Change and Configuration Management Processes
182(1)
12.3 Other Processes Involving the System Architect
182(1)
13 Agile Approaches 183(6)
13.1 The History of Iterative-Incremental and Agile Development
184(2)
13.2 System Architects in an Agile Environment
186(3)
14 The FAS Method 189(42)
14.1 Motivation
190(2)
14.2 Functional Architectures for Systems
192(3)
14.3 The FAS Method
195(4)
14.4 FAS Heuristics
199(3)
14.5 FAS with SysML
202(8)
14.6 Modeling Tool Support
210(5)
14.7 Mapping of a Functional Architecture to a Physical Architecture
215(3)
14.8 Experiences with the FAS Method
218(1)
14.9 FAS Workshops
219(3)
14.10 Nonfunctional Requirements and the Functional Architecture
222(2)
14.11 Completeness of the Functional Architecture
224(3)
14.12 Functional Architectures and the Zigzag Pattern
227(4)
15 Product Lines & Variants 231(12)
15.1 Definitions Variant Modeling
232(1)
15.2 Variant Modeling with SysML
233(6)
15.3 Other Variant Modeling Techniques
239(4)
16 Architecture Frameworks 243(22)
16.1 Enterprise Architectures
244(2)
16.2 System of Systems (SoS)
246(3)
16.3 An Overview of Architecture Frameworks
249(12)
16.4 The UPDM Standard
261(1)
16.5 What to do when we Come in Touch with Architecture Frameworks
262(1)
16.6 Conclusion
263(2)
17 Cross-Cutting Concerns 265(6)
17.1 The Game-Winning Nonfunctional Aspects
265(1)
17.2 Human System Interaction and Human Factors Engineering
266(1)
17.3 Risk Management
267(1)
17.4 Trade Studies
268(1)
17.5 Budgets
269(2)
18 Architecture Assessment 271(6)
19 Making it Work in the Organization 277(14)
19.1 Overview
277(1)
19.2 Organizational Structure for Systems Architecting
278(5)
19.3 Recipes from the Authors' Experience
283(8)
20 Soft Skills 291(20)
20.1 It's all about Communication
292(11)
20.2 Personality Types
303(4)
20.3 Intercultural Collaboration Skills
307(4)
21 Outlook: The World after Product Line Engineering 311(4)
A OMG SysML 315(28)
A.1 Diagram and Model
316(2)
A.2 Structure Diagrams
318(11)
A.3 Behavior Diagrams
329(8)
A.4 Requirements Diagram
337(3)
A.5 Extension of SysML with Profiles
340(1)
A.6 Architecture of the Language
341(2)
B The V-Model 343(10)
B.1 A Brief History of the V-Model or the Systems Engineering VEE
343(2)
B.2 A Handy Illustration but No Comprehensive Process Description
345(3)
B.3 Critical Considerations
348(3)
B.4 Reading Instruction for a Modern Systems Engineering VEE
351(2)
Bibliography 353(10)
Index 363
Tim Weilkiens is the CEO at the German consultancy oose Innovative Informatik and co-author of the SysML specification. He has introduced model-based systems engineering to a variety of industry sectors.  He is author of several books about modeling and the MBSE methodology SYSMOD.

Jesko G. Lamm is a Senior Systems Engineer at Bernafon, a Swiss manufacturer for hearing instruments. With Tim Weilkiens, Jesko G. Lamm founded the Functional Architectures working group of the German chapter of INCOSE.

Stephan Roth is a coach, consultant, and trainer for systems and software engineering at the German consultancy oose Innovative Informatik. He is a state-certified technical assistant for computer science from Physikalisch-Technische Lehranstalt (PTL) Wedel and a certified systems engineer (GfSE)®- Level C.

Markus Walker works at Schindler Elevator in the research and development division as elevator system architect. He is an INCOSE Certified Systems Engineering Professional (CSEP) and is engaged in the committee of the Swiss chapter of INCOSE.