✍ Scribed by Fairley, Richard E
No coin nor oath required. For personal study only.
A comprehensive review of the life cycle processes, methods, and techniques used to develop and modify software-enabled systems
Systems Engineering of Software-Enabled Systemsoffers an authoritative review of the most current methods and techniques that can improve the links between systems engineering and software engineering. The author--a noted expert on the topic--offers an introduction to systems engineering and software engineering and presents the issues caused by the differences between the two during development process. The book reviews the traditional approaches used by systems engineers and software engineers and explores how they differ.
The book presents an approach to developing software-enabled systems that integrates the incremental approach used by systems engineers and the iterative approach used by software engineers. This unique approach is based on developing system capabilities that will provide the features, behaviors, and quality attributes needed by stakeholders, based on model-based system architecture. In addition, the author covers the management activities a systems engineer or software engineer must engage in to manage and lead the technical work to be done. This important book:
Offers an approach to improving the process of working with systems engineers and software engineers Contains information on the planning and estimating, measuring and controlling, managing risk, and organizing and leading systems engineering teams Includes a discussion of the key points of each chapter and exercises for review Suggests numerous references that provide additional readings for development of software-enabled physical systems Provides two case studies as running examples throughout the text Written for advanced undergraduates, graduate students, and practitioners,Systems Engineering of Software-Enabled Systemsoffers a comprehensive resource to the traditional and current techniques that can improve the links between systems engineering and software engineering.
Table of Contents......Page 2
Preface......Page 15
Part I: Systems Engineering and Software Engineering......Page 17
1.1 Introduction......Page 18
1.2 The Evolution of Engineering......Page 19
1.3 Characterizations of Systems......Page 23
1.4 Systems Engineering......Page 33
1.5 Applications of Systems Engineering......Page 37
1.6 Specialty Engineering......Page 39
1.7 Related Disciplines......Page 40
1.8 Software Engineering......Page 41
1.9 Applications of Software Engineering......Page 43
1.10 Physical Systems Engineers and Software Systems Engineers......Page 45
1.11 Key Points......Page 46
Exercises......Page 47
References......Page 49
2.2 Categories of Systems......Page 52
2.3 Common Attributes of PhSEs and SwSEs......Page 54
2.4 Ten Things PhSEs Need to Know About Software and Software Engineering......Page 55
2.5 Ten Things Software Engineers Need to Know About Systems Engineering......Page 69
Exercises......Page 77
References......Page 79
3.2 Some Background......Page 81
3.3 Professional Literacy......Page 83
3.4 Differences in Terminology......Page 89
3.5 Differences in Problem‐Solving Styles......Page 98
3.6 Holistic and Reductionist Problem Solving......Page 101
3.7 Logical and Physical Design......Page 102
3.9 Workplace Respect......Page 104
3.10 Key Points......Page 106
Exercises......Page 107
References......Page 108
Part II: Systems Engineering for Software‐Enabled Physical Systems......Page 110
4.1 Introduction......Page 111
4.2 Characteristics of Physical Elements and Software Elements......Page 112
4.3 Development Process Foundations......Page 115
4.4 Linear and Vee Development Models......Page 118
4.5 Iterative Development Models......Page 123
4.6 The ATM Revisited......Page 126
4.7 Key Points......Page 127
Exercises......Page 128
References......Page 130
5.2 Capabilities‐Based System Development......Page 132
5.3 The I3 System Development Model......Page 140
5.4 Key Points......Page 149
Exercises......Page 150
References......Page 151
6.2 Performing Business or Mission Analysis......Page 153
6.3 Identifying Stakeholders' Needs and Defining Their Requirements......Page 161
6.4 Identifying and Prioritizing System Capabilities......Page 177
6.5 Determining Technical Feasibility......Page 179
6.7 Key Points......Page 182
References......Page 184
7.1 Introduction......Page 186
7.2 The System Requirements Definition Process......Page 187
7.3 A Requirements Taxonomy......Page 188
7.4 Verifying and Validating System Requirements......Page 197
7.5 System Requirements for the RC‐DSS Case Study......Page 205
7.6 Key Points......Page 206
Exercises......Page 208
References......Page 209
8.1 Introduction......Page 210
8.2 Principles of Architecture Definition......Page 211
8.3 Defining System Architectures......Page 214
8.4 Architecture Evaluation Criteria......Page 218
8.5 Selecting the Architecture......Page 220
8.6 Principles of Design Definition......Page 222
8.7 RC‐DSS Architecture Definition......Page 229
8.8 RC‐DSS Design Definition......Page 236
8.9 Controlling the Complexity of System Architecture and System Design......Page 237
8.10 Key Points......Page 241
The System Modeling Language (SysML)......Page 242
References......Page 249
9.1 Introduction......Page 251
9.2 I3 Phases 5 and 6......Page 252
9.3 I3 System Implementation......Page 253
9.5 Key Points......Page 262
Exercises......Page 263
References......Page 264
Part III: Technical Management of Systems Engineering......Page 265
10.2 Documenting the Technical Work Plan (SEMP)......Page 266
10.3 The Estimation Process......Page 275
10.4 Estimation Techniques......Page 280
10.5 Documenting an Estimate......Page 290
10.6 Key Points......Page 294
Exercises......Page 295
References......Page 296
11.1 Introduction......Page 298
11.2 Assessing and Analyzing Process Parameters......Page 299
11.3 Assessing and Analyzing System Parameters......Page 323
11.4 Corrective Action......Page 328
11.5 Key Points......Page 331
Exercises......Page 333
References......Page 334
12.1 Introduction......Page 336
12.2 Managing Versus Leading......Page 337
12.3 The Influence of Corporate Culture......Page 338
12.4 Responsibility and Authority......Page 340
12.5 Teams and Teamwork......Page 341
12.6 Maintaining Motivation and Morale......Page 348
12.7 Can't Versus Won't......Page 350
12.8 Fourteen Guidelines for Organizing and Leading Engineering Teams......Page 351
12.9 Summary of the Guidelines......Page 368
12.10 Key Points......Page 369
Exercises......Page 370
References......Page 371
A.1 Background......Page 373
A.2 Purpose......Page 377
A.4 Systems Engineering Practices......Page 378
A.5 Lessons Learned......Page 381
References......Page 382
B.1 Introduction......Page 383
B.2 Electronic Control Units......Page 384
B.3 ECU Domains......Page 388
B.5 The Chassis Domain......Page 389
B.7 The Infotainment Domain......Page 390
B.10 Automotive Network Domains......Page 391
B.11 Network Protocols......Page 392
B.12 Summary......Page 393
References......Page 394
Glossary of Terms......Page 395
Index......Page 402
End User License Agreement......Page 413
📜 SIMILAR VOLUMES
<b>Discover the emerging science and engineering of System of Systems</b><p> Many challenges of the twenty-first century, such as fossil fuel energy resources, require a new approach. The emergence of System of Systems (SoS) and System of Systems Engineering (SoSE) presents engineers and professiona
Discusses open systems, object orientation, software agents, domain-specific languages, component architectures, as well as the dramatic IT-enabled improvements in memory, communication, and processing resources that are now available for sophisticated control algorithms to exploit.Useful for practi