| Description |
1 online resource |
| Contents |
Front Cover; Agile Systems Engineering; Copyright Page; Dedication; Contents; About the Author; Preface; Audience; Goals; Tooling; Where to Go After the Book; Acknowledgments; 1 What Is Model-Based Systems Engineering?; 1.1 Key Systems Engineering Activities; 1.1.1 Identifying Customer Needs; 1.1.2 Specifying System Requirements; 1.1.3 Assess Dependability; 1.1.4 Evaluating Alternative Architectures and Technologies; 1.1.5 Selecting Specific Architectures and Technologies; 1.1.6 Allocating Requirements and Interfaces to Architectures; 1.1.7 Hand Off to Downstream Engineering |
|
1.1.8 Integrate Discipline-Specific Designs into System Composite1.1.9 Verify System as a Whole; 1.1.9.1 Syntactic verification; Audits; Syntactic reviews; 1.1.9.2 Semantic verification; Semantic review; Testing; Formal methods; 1.1.9.3 System verification; 1.1.10 System Validation; 1.2 Systems Engineering Data; 1.2.1 System Development Plan; 1.2.2 Stakeholder Requirements; 1.2.3 System Requirements; 1.2.4 Certification Plan; 1.2.5 Subsystem Requirements; 1.2.6 Discipline-Specific Requirements; 1.2.7 Safety Analysis; 1.2.8 Reliability Analysis; 1.2.9 Security Analysis |
|
1.2.10 System Architecture1.2.10.1 Subsystems; 1.2.10.2 Deployment architecture; 1.2.10.3 Dependability architecture; 1.2.10.4 Distribution architecture; 1.2.11 Integration Test Plan; 1.2.12 Integration Tests; 1.2.13 Verification Plan; 1.2.14 Verification Tests; 1.2.15 Validation Plan; 1.2.16 Trace Matrix; 1.2.17 Integration Test Results; 1.2.18 Verification Results; 1.2.19 Validation Results; 1.3 Lifecycles of the Systems Engineer; 1.3.1 V-Model Lifecycle; 1.3.2 Incremental; 1.3.3 Hybrid; 1.4 Model-Based Systems Engineering (MBSE); 1.4.1 The Modeling Advantage |
|
1.4.1.1 Precision of engineering data1.4.1.2 Data consistency across work products and engineering activities; 1.4.1.3 A common source of engineering truth; 1.4.1.4 Improved visualization and comprehension of engineering data; 1.4.1.5 Ease of integration of disparate engineering data; 1.4.1.6 Improved management and maintenance of engineering data; 1.4.1.7 Early verification of the correctness of engineering data; 1.4.2 High-Precision Modeling with UML and SysML; 1.4.2.1 The fundamental truth of modeling: drawing≠modeling; 1.4.3 Modeling Is Essential for Agile Systems Engineering |
|
1.4.3.1 The fundamental truth of agile systems engineering: verifiable models are required for agile systems engineering1.4.4 Adopting Modeling in Your Organization or Project; 1.4.4.1 Antipatterns of adopting MBSE; 1.4.4.2 Recommend approaches for adopting MBSE; Assessment; Planning for adoption; Pilot; Deployment; 1.4.5 The Rules (of Modeling); 1.5 Summary; References; 2 What Are Agile Methods and Why Should I Care?; 2.1 The Agile Manifesto; 2.2 Benefits of Agile Methods; Improved Quality of Engineering Data; Improved Engineering Efficiency; Early Return on Investment (ROI) |
| Summary |
Presenting a vision of systems engineering where precise specification of requirements, structure, and behavior meet larger concerns as such as safety, security, reliability, and performance in an agile engineering context, this book discusses the lifecycle of systems development, including requirements, analysis, design, and the handoff to specific engineering disciplines. -- Edited summary from book |
| Notes |
Includes index |
| Bibliography |
Includes bibliographical references |
| Notes |
Vendor-supplied metadata |
| Subject |
Systems engineering.
|
|
Agile software development.
|
|
SysML (Computer science)
|
|
systems engineering.
|
|
TECHNOLOGY & ENGINEERING / Engineering (General)
|
|
TECHNOLOGY & ENGINEERING / Reference
|
|
Agile software development
|
|
SysML (Computer science)
|
|
Systems engineering
|
| Form |
Electronic book
|
| LC no. |
2017275025 |
| ISBN |
9780128023495 |
|
012802349X |
|
