Systems engineering of software-enabled systems

414 Pages·2019·6.114 MB·English

by  Fairley, Richard E

Table of Contents
Cover
Preface
Part I: Systems Engineering and Software Engineering
1 Introduction and Overview
1.1 Introduction
1.2 The Evolution of Engineering
1.3 Characterizations of Systems
1.4 Systems Engineering
1.5 Applications of Systems Engineering
1.6 Specialty Engineering
1.7 Related Disciplines
1.8 Software Engineering
1.9 Applications of Software Engineering
1.10 Physical Systems Engineers and Software Systems Engineers
1.11 Key Points
Exercises
References
2 Systems Engineering and Software Engineering
2.1 Introduction
2.2 Categories of Systems
2.3 Common Attributes of PhSEs and SwSEs
2.4 Ten Things PhSEs Need to Know About Software and Software
Engineering
2.5 Ten Things Software Engineers Need to Know About Systems
Engineering
2.6 Key Points
Exercises
References
3 Issues and Opportunities for Improvements
3.1 Introduction
3.2 Some Background
3.3 Professional Literacy
3.4 Differences in Terminology
3.5 Differences in Problem‐Solving Styles
3.6 Holistic and Reductionist Problem Solving
3.7 Logical and Physical Design
3.8 Differences in Process Models and Technical Processes
3.9 Workplace Respect
3.10 Key Points
Exercises
References
Part II: Systems Engineering for Software‐Enabled Physical Systems
4 Traditional Process Models for System Development
4.1 Introduction
4.2 Characteristics of Physical Elements and Software Elements
4.3 Development Process Foundations
4.4 Linear and Vee Development Models
4.5 Iterative Development Models
4.6 The ATM Revisited
4.7 Key Points
Exercises
References
5 The Integrated‐Iterative‐Incremental System Development Model
5.1 Introduction
5.2 Capabilities‐Based System Development
5.3 The I3 System Development Model
5.4 Key Points
Exercises
References
6 The I3 System Definition Phase
6.1 Introduction
6.2 Performing Business or Mission Analysis
6.3 Identifying Stakeholders' Needs and Defining Their Requirements
6.4 Identifying and Prioritizing System Capabilities
6.5 Determining Technical Feasibility
6.6 Establishing and Maintaining Traceability
6.7 Key Points
References
7 System Requirements Definition
7.1 Introduction
7.2 The System Requirements Definition Process
7.3 A Requirements Taxonomy
7.4 Verifying and Validating System Requirements
7.5 System Requirements for the RC‐DSS Case Study
7.6 Key Points
Exercises
References
8 Architecture Definition and Design Definition
8.1 Introduction
8.2 Principles of Architecture Definition
8.3 Defining System Architectures
8.4 Architecture Evaluation Criteria
8.5 Selecting the Architecture
8.6 Principles of Design Definition
8.7 RC‐DSS Architecture Definition
8.8 RC‐DSS Design Definition
8.9 Controlling the Complexity of System Architecture and System Design
8.10 Key Points
Exercises
The System Modeling Language (SysML)
References
9 System Implementation and Delivery
9.1 Introduction
9.2 I3 Phases 5 and 6
9.3 I3 System Implementation
9.4 I3 System Delivery
9.5 Key Points
Exercises
References
Part III: Technical Management of Systems Engineering
10 Planning and Estimating the Technical Work
10.1 Introduction
10.2 Documenting the Technical Work Plan (SEMP)
10.3 The Estimation Process
10.4 Estimation Techniques
10.5 Documenting an Estimate
10.6 Key Points
Exercises
References
11 Assessing, Analyzing, and Controlling Technical Work
11.1 Introduction
11.2 Assessing and Analyzing Process Parameters
11.3 Assessing and Analyzing System Parameters
11.4 Corrective Action
11.5 Key Points
Exercises
References
12 Organizing, Leading, and Coordinating
12.1 Introduction
12.2 Managing Versus Leading
12.3 The Influence of Corporate Culture
12.4 Responsibility and Authority
12.5 Teams and Teamwork
12.6 Maintaining Motivation and Morale
12.7 Can't Versus Won't
12.8 Fourteen Guidelines for Organizing and Leading Engineering Teams
12.9 Summary of the Guidelines
12.10 Key Points
Exercises
References
Appendix A: The Northwest Hydroelectric System
A.1 Background
A.2 Purpose
A.3 Challenges
A.4 Systems Engineering Practices
A.5 Lessons Learned
References
Appendix B: Automobile Embedded Real‐Time Systems
B.1 Introduction
B.2 Electronic Control Units
B.3 ECU Domains
B.4 The Powertrain Domain (Engine and Transmission)
B.5 The Chassis Domain
B.6 The Body Domain
B.7 The Infotainment Domain
B.8 An Emerging Domain
B.9 The ECU Network
B.10 Automotive Network Domains
B.11 Network Protocols
B.12 Summary
References
Glossary of Terms
Index
End User License Agreement
List of Tables
Chapter 1
Table 1.1 Attributes of the systems engineering profession.
Table 1.2 Attributes of the software engineering profession.
Chapter 2
Table 2.1 Three categories of systems.
Table 2.2 Mutual adaptation of methods by PhSEs and SwSEs.
Chapter 4
Table 4.1 Physical and performance parameters of HSRL.
Table 4.2 15288:2015 and 12207:2017 technical processes.
Chapter 5
Table 5.1 ATM system capabilities/feasible hardware and software.
Table 5.2 Capability prioritization criteria and rationale.
Table 5.3 System development activities for the I3 development phases....
Table 5.4 I3 development phase and 15288/12207 processes.
Chapter 6
Table 6.1 Business or mission analysis.
Table 6.2 Stakeholder needs and requirements definition.
Table 6.3 An RC‐DSS use case.
Table 6.4 Capability prioritization and rationale.
Chapter 7
Table 7.1 Inputs, processes, and outputs of system requirements definit...
Table 7.2 Some examples of quality attributes.
Table 7.3 Some users and uses of system requirements.
Table 7.4 A traceability example.
Table 7.5 Examples of RC‐DSS system capabilities and system requirement...
Chapter 8
Table 8.1 Architecture definition inputs, process, and outputs.
Table 8.2 Design definition inputs, process, and outputs.
Table 8.3 RC‐DSS architecture options and criteria satisfied.
Table 8.4N 2 diagram for the RC‐DSS system elements.
Chapter 9
Table 9.1 I3 phases and 15288/12207 processes.
Table 9.2 Implementation of inputs, processes, and outputs.
Table 9.3 Previous I3 phases and 15288/12207 technical processes.
Chapter 11
Table 11.1 An example of project status using binary assessment.
Table 11.2 Percent of effort for various work activities.
Table 11.3 Earned value terminology.
Table 11.4 Earned value relationships.
Table 11.5 Some commonly occurring risk factors for systems projects.
Table 11.6 Qualitative determination of risk exposure.
Table 11.7 Risk mitigation strategies.
Table 11.8 Example of an immediate action plan.
Table 11.9 Example of a deferred action plan.
Table 11.10 A hierarchy of measurement scales.
Table 11.11 Some direct measures.
Table 11.12 Some indirect measures.
Chapter 12
Table 12.1 Some antidotes for teamicide.
Table 12.2 Four combinations of can't and won't.
Table 12.3 Four situations and leadership styles.
Table 12.4 Agenda and follow‐up activities for weekly status meetings.
List of Illustrations
Chapter 1
Figure 1.1 A stationary steam engine.
Figure 1.2 The 5C levels of a smart factory architecture.
Figure 1.3 The NOAA NPOESS context diagram.
Figure 1.4 A complex natural system (the Blue Marble).
Figure 1.5 A software‐enabled natural/engineered system.
Figure 1.6 A complex software‐enabled engineered system.
Figure 1.7 Launch of Saturn V and Apollo spacecraft.
Figure 1.8 The Apollo spacecraft.
Figure 1.9 A complex engineered system in a natural environment.
Figure 1.10 Attributes of an engineering profession.
Figure 1.11 An enterprise information system (EIS) in context.
Chapter 2
Figure 2.1 The Ariane 5 rocket at Le Bourget Air and Space Museum, Paris....
Figure 2.2 Iterative software development.
Figure 2.3 Quality assurance observation of a systems project.
Chapter 3
Figure 3.1 Template for a partial product breakdown structure.
Figure 3.2 A generalization/specialization class hierarchy.
Figure 3.3 A software product line instantiation.
Figure 3.4 Aggregation of ATM hardware elements.
Figure 3.5 Composition of ATM software elements.
Chapter 4
Figure 4.1 A linear one‐pass system development model.
Figure 4.2 A linear‐revisions system development model.
Figure 4.3 A Vee system development model.
Figure 4.4 An incremental Vee system development model.
Figure 4.5 An overlapping incremental Vee development model.
Chapter 5
Figure 5.1 A capabilities‐based approach to system development.
Figure 5.2 The I3 system development model.
Chapter 6
Figure 6.1 Package diagram of the RC‐DSS driving simulator.
Figure 6.2 Some project relationships.
Figure 6.3 Simpler project relationships.
Figure 6.4 A state machine diagram for RC‐DSS authentication and terminati...
Figure 6.5 An activity diagram for RC‐DSS authentication and termination....
Figure 6.6 A use case diagram.
Chapter 7
Figure 7.1 The I3 system development model.
Figure 7.2 A requirements taxonomy.
Figure 7.3 A capabilities‐based approach to requirements realization.
Figure 7.4 Context diagram for the RC‐DSS driving system simulator.
Chapter 8
Figure 8.1 The I3 system development model.
Figure 8.2 Allocation of system requirements to architectural elements.
Figure 8.3 Selecting the system architecture.
Figure 8.4 The inspection process.
Figure 8.5 RC‐DSS functional block diagram.
Figure 8.6 A partially decomposed RC‐DSS system structure.
Figure 8.7 An RC‐DSS sequence diagram.
Figure 8.8 An RC‐DSS activity diagram.
Figure 8.9 An RC‐DSS state diagram.
Figure 8.10 An RC‐DSS use case diagram.
Figure 8.A.1 Nine types of SysML diagrams.
Figure 8.A.2 A template for a block definition diagram.
Figure 8.A.3 Template for a sequence diagram.
Figure 8.A.4 An example of a sequence diagram.
Figure 8.A.5 Template for an activity diagram.
Chapter 9
Figure 9.1 The I3 system development model.
Figure 9.2 A template for adapter patterns.
Figure 9.3 An example of a bridge pattern.
Chapter 10
Figure10.1 The change management process.
Figure 10.2 Quality assurance for systems engineering projects.
Figure 10.3 The P‐80 Shooting Star jet fighter.
Figure 10.4 The Lockheed Martin Skunk Works logo.
Figure 10.5 An estimation process.
Figure 10.6 An inverted estimation process.
Figure 10.7 Illustrating Monte Carlo estimation.
Figure 10.8 An effort histogram.
Figure 10.9 A partial WBS. ATMHD, hardware drivers; FINAT, financial trans...
Chapter 11
Figure 11.1 A taxonomy of project effort.
Figure 11.2 Illustrating the 95% complete syndrome.