Applied Systems Engineering
Applied Systems Engineering
Author(s): Michael J. Ryan; R. Ian Faulconbridge
ISBN: 978-1-921138-13-3
Pages: 348
Published: 2021
Subject: Management
Format: Print
Overview | Preface | Table of Contents | Sample Chapter |
In line with the top-down approach of systems engineering, we focus in this book on the early stages of the system life cycle since the activities in these stages have the greatest impact on the successful acquisition and fielding of a system. In the interests of balance, however, we use the systems engineering framework to provide an overview of all other aspects related to systems engineering.
This applied systems engineering book is used as a text for a number of professional education and university courses, as well as for a number of in-house courses. In particular, it is complimentary to attendees on the edVirtus Systems Engineering--Introduction and Systems Engineering--Advanced training courses delivered by the authors Dr Ian Faulconbridge and Dr Mike Ryan. The text also supports the Coursera Massive Open Online Course (MOOC) Introduction to Systems Engineering.
The need to manage complexity is now commonplace in almost all fields of undertaking. Complex systems such as cars, aeroplanes, airports, financial systems, and communications networks commonly involve millions of hours of work by thousands of people from a wide range of disciplines and backgrounds spread across a number of companies in a number of countries. Projects often take decades and involve a large number of disparate stakeholders, developers, operators and customers. At the same time, the need to accommodate changes in the market place has created considerable pressure on traditional engineering processes. It is little wonder therefore that we have become used to hearing of the difficulties associated with complex projects—cost and schedule overruns, dramatic failures to achieve requirements, project cancellations, and so on.
These problems cannot be solved by simply ensuring that each of the associated disciplines pays more attention to their individual professions. Complex technical projects can only be managed effectively by addressing the whole life cycle. First, requirements must be defined formally to provide a comprehensive description of the functionality of the system to be procured—a functional architecture. These functional requirements are analyzed and elaborated to create a functional description of subsystem requirements, which are then allocated to physical configuration items to provide a physical architecture of the system. The aim of developing the physical configuration items is to reduce the complex system to a series of well-defined subsystems that can be designed and then built by manageable teams using extant processes and procedures. The subsequent development of these separate subsystems must be managed, however, so that they are verified, tested and integrated into the final system to be delivered. To be successful, the entire process must be planned, documented, and managed.
This book provides a basic but complete coverage of the discipline known as systems engineering. We offer a framework encapsulating the entire systems engineering discipline, clearly showing where the multitude of associated activities fits within the overall effort, providing an ideal vehicle for understanding the complex discipline.
We take a top-down approach that introduces the philosophical aspects of the discipline and provides a framework within which the reader can assimilate the associated activities. Without such a reference, the practitioner is left to ponder the plethora of terms, standards and practices that have been developed independently and often lack cohesion, particularly in nomenclature and emphasis. The field of systems engineering is often viewed as dry, detailed, complicated, acronym-intensive, and uninteresting. Yet, the discipline holds the solution to delivering complex technical projects on time and within budget, and avoiding many of the failures of the past. The intention of this book is both to cover all aspects of the discipline and to provide a framework for the consideration of the many issues associated with engineering complex systems.
Our secondary purpose is to describe a complex field in a simple, easily-digested manner that is accessible to a wide spectrum of readers, from students to professionals, from novices to experienced practitioners. It is directed at a wide audience and aims to be a valuable reference for all professions associated with the management of complex technical projects: project managers, systems engineers, quality assurance representatives, integrated logistic support practitioners, maintainers, and so on.
Chapter 1 introduces systems engineering and related issues and Chapter 2 provides the framework within which the remainder of the book is written. Chapters 3 and 4 examine in more detail the issues associated with Conceptual Design and Preliminary Design. Emphasis is given to these early activities, as they have the greatest impact on the system development. Chapters 5, 6 and 7 deal with respectively Detailed Design and Development, Construction and/or Production, and Operational Use and Support. Chapter 8 deals with the broad topic of systems engineering management and details some of the associated activities. Some of the more common and popular systems engineering standards are introduced in Chapter 9 and their application to engineering management and process is explained. Chapter 10 explains the interrelationship between the systems engineering effort and other closely related disciplines such as project management, quality management and integrated logistics support management. Finally, Chapter 11 discusses the relationship between systems engineering methodologies and a number of acquisition methods.
Systems engineering is a broad discipline, and its application to different projects always requires individual and independent thought. There is never a single solution that will work with all projects, and there is rarely a solution that is either completely right or wrong. This book aims to introduce the main systems engineering issues to the reader to facilitate some of that individual and independent thought.
Ian Faulconbridge
Mike Ryan
Canberra, 2021
1 INTRODUCTION TO SYSTEMS ENGINEERING |
1 |
1.1 What is a System? |
2 |
1.1.1 Definition of a System |
3 |
1.1.2 Types of Systems |
4 |
1.1.3 A System and its Environment |
4 |
1.1.4 A System as a Product |
5 |
1.1.5 A System as a Capability—A Capability System |
6 |
1.1.6 Logical and Physical Descriptions of a System |
7 |
1.1.7 Hierarchical Descriptions of a System |
9 |
1.1.8 Collections of Systems |
11 |
1.1.9 Problem Domain and Solution Domain |
14 |
1.2 System Life Cycle |
14 |
1.2.1 Parties Involved |
16 |
1.3 Acquisition and Utilization Phases |
17 |
1.3.1 Acquisition Phase |
18 |
1.3.2 Utilization Phase |
21 |
1.3.3 Retirement Phase |
21 |
1.4 Systems Engineering and Development Approaches |
21 |
1.5 What is Systems Engineering? |
22 |
1.5.1 Top-Down Approach |
23 |
1.5.2 Requirements Engineering |
25 |
1.5.3 Focus on Life Cycle |
26 |
1.5.4 System Optimization and Balance |
26 |
1.5.5 Integration of Disciplines and Specializations |
27 |
1.5.6 Management |
28 |
1.6 Systems Engineering Relevance |
28 |
1.7 Systems Engineering Benefits |
29 |
1.8 Analysis, Synthesis, and Evaluation |
32 |
1.8.1 Analysis |
32 |
1.8.2 Synthesis |
33 |
1.8.3 Evaluation |
33 |
1.9 A Systems Engineering Framework |
33 |
1.9.1 Systems Engineering Processes |
35 |
1.9.2 Systems Engineering Management |
36 |
1.9.3 Systems Engineering Tools |
36 |
1.9.4 Related Disciplines |
36 |
1.1 Summary |
37 |
1.11 Revision Questions |
37 |
|
|
|
|
2 REQUIREMENTS ENGINEERING FRAMEWORK |
|
2.1 Introduction |
45 |
2.1.1 Concepts, Needs and Requirements |
45 |
2.1.2 What is a Requirement? |
49 |
2.1.3 Requirements Characteristics and Attributes |
50 |
2.1.4 What Not How |
53 |
2.1.5 Emergent Properties |
54 |
2.2 What Is Requirements Engineering? |
54 |
2.2.1 Why We Need Requirements |
55 |
2.2.2 Why We Need Requirements Engineering |
56 |
2.3 Requirements Elicitation and Elaboration |
56 |
2.3.1 Difficulties in Eliciting and Elaborating Requirements |
59 |
2.3.2 Techniques for Eliciting/Generating Requirements |
61 |
2.4 Requirements Validation |
67 |
2.5 Requirements Documentation |
68 |
2.6 Requirements Management |
69 |
2.6.1 Requirements Change Management |
69 |
2.6.2 Change Management—Traceability |
69 |
2.6.3 Requirements Management Tools |
70 |
2.7 Requirements-Engineering Tools |
72 |
2.7.1 Requirements Breakdown Structure (RBS) |
73 |
2.7.2 Functional Flow Block Diagrams (FFBD) |
74 |
2.8 Summary |
76 |
2.9 Review Questions |
76 |
|
|
3 CONCEPTUAL DESIGN |
|
3.1 Introduction |
85 |
3.2 C1—Define Business Needs and Requirements |
86 |
3.2.1 C1.1—Identify Major Stakeholders and Constraints |
87 |
3.2.2 C1.2—Elicit Business Needs |
90 |
3.2.3 C1.3—Scope System |
105 |
3.2.4 C1.4—Define Business Requirements |
111 |
3.2.5 C1.5—Finalise Business Needs and Requirements (BNR) |
114 |
3.3 C2—Define Stakeholder Needs and Requirements |
115 |
3.3.1 C2.1—Define Stakeholder Needs |
115 |
3.3.2 C2.2—Define Stakeholders Requirements |
116 |
3.3.3 C2.3—Finalise Stakeholder Needs and Requirements (SNR) |
118 |
3.4 C3—Define System Requirements |
118 |
3.4.1 C3.1—Establish Requirements Framework |
121 |
3.4.2 C3.2—Perform Requirements Analysis and Allocation |
121 |
3.4.3 C3.3—Draft System Requirement Specification (SyRS) |
125 |
3.4.4 C3.4—Define Technical Performance Measures (TPM) |
126 |
3.4.5 C3.5—Conduct System Requirements Reviews (SRR) |
131 |
3.4.6 Engineering Management Considerations |
132 |
3.5 C4—Conduct System-Level Synthesis |
133 |
3.6 C5—Conduct System Design Review (SDR) |
135 |
3.7 Review Questions |
137 |
|
|
4 PRELIMINARY DESIGN |
|
4.1 Introduction |
141 |
4.2 Subsystem Requirements Analysis |
141 |
4.3 Requirements Allocation |
145 |
4.3.1 Identify Candidate Subsystems |
146 |
4.3.2 Group and Allocate Requirements |
150 |
4.3.3 Confirm Subsystem Selection |
153 |
4.4 RBS versus WBS |
154 |
4.5 Interface Identification and Design |
155 |
4.5.1 Interface Control Document (ICD) |
155 |
4.5.2 Types of Interface |
158 |
4.5.3 Interface Control Working Group (ICWG) |
159 |
4.5.4 Interface Definition Using the N2 Diagram |
160 |
4.6 Subsystem-Level Synthesis and Evaluation |
161 |
4.6.1 Review Sources of Subsystem Requirements |
161 |
4.6.2 Investigate Design Alternatives |
162 |
4.6.3 Make Optimal Use of Design Space |
168 |
4.6.4 Selecting the Preferred Solution |
173 |
4.7 Preliminary Design Review (PDR) |
173 |
4.8 Tools |
175 |
4.8.1 Schematic Block Diagrams |
176 |
4.8.2 Physical Modelling |
176 |
4.8.3 Mathematical Modelling and Simulation |
177 |
4.8.4 Trade-Off Analysis |
178 |
4.8.5 Model-based Systems Engineering (MBSE) |
182 |
4.9 Review Questions |
184 |
|
|
5 DETAILED DESIGN AND DEVELOPMENT |
|
5.1 Introduction |
187 |
5.2 Detailed Design Requirements |
187 |
5.3 Detailed Design of Hardware |
189 |
5.3.1 Generic Hardware Detailed Design Process |
190 |
5.3.2 Preparing for Detailed Hardware Design |
190 |
5.3.3 Performing Detailed Hardware Design |
191 |
5.3.4 Proving the Detailed Hardware Design |
193 |
5.3.5 Documenting the Detailed Hardware Design |
194 |
5.4 Detailed Design of Software |
196 |
5.4.1 Software Design Process |
196 |
5.4.2 Preparing for Software Design |
197 |
5.4.3 Performing Detailed Software Design |
197 |
5.4.4 Documenting the Detailed Software Design |
198 |
5.5 Integrating System Elements |
199 |
5.6 Detailed Design Reviews |
201 |
5.6.1 Equipment/Software Design Reviews |
201 |
5.6.2 Critical Design Review (CDR) |
201 |
5.7 Review Questions |
204 |
|
|
6 CONSTRUCTION AND/OR PRODUCTION |
|
6.1 Introduction |
207 |
6.2 Production Requirements |
207 |
6.3 Engineering Management Issues |
210 |
6.3.1 Major Audits |
210 |
6.3.2 Major Reviews |
214 |
6.3.3 Configuration Management |
215 |
6.4 Review Questions |
215 |
|
|
7 OPERATIONAL USE AND SYSTEM SUPPORT |
|
7.1 Introduction |
217 |
7.2 Failure Reporting, Analysis and Corrective Action System (FRACAS) |
220 |
7.3 Retirement |
222 |
7.5 A Final Thought: Systems Engineering and Sustainable Development |
225 |
7.4 Review Questions |
226 |
|
|
8 SYSTEMS ENGINEERING MANAGEMENT |
|
8.1 Introduction |
229 |
8.2 Technical Review and Audit Management |
229 |
8.3 Test and Evaluation |
232 |
8.3.1 Developmental Test and Evaluation (DT&E) |
234 |
8.3.2 Acceptance Test and Evaluation (AT&E) |
235 |
8.3.3 Operational Test and Evaluation (OT&E) |
236 |
8.3.4 Test Management |
237 |
8.3.5 Testing Activities and the System Life Cycle |
237 |
8.3.6 Test and Evaluation Master Plan (TEMP) |
242 |
8.4 Technical Risk Management |
243 |
8.4.1 Risk Identification |
245 |
8.4.2 Risk Analysis |
246 |
8.4.3 Risk Treatment |
247 |
8.4.4 Risk Management Documentation |
248 |
8.5 Configuration Management |
248 |
8.5.1 Establishing the Baselines |
249 |
8.5.2 Configuration Management Functions |
250 |
8.5.3 Configuration Management in Acquisition and in Utilization |
255 |
8.5.4 Configuration Management Documentation |
255 |
8.6 Specifications and Standards |
257 |
8.6.1 Specifications |
257 |
8.6.2 Standards |
260 |
8.7 Systems Engineering Management Planning |
262 |
8.8 Review Questions |
265 |
|
|
9 SYSTEMS ENGINEERING STANDARDS |
|
9.1 Standards |
269 |
9.1.1 MIL-STD-499B—Systems Engineering (Draft) |
269 |
9.1.2 EIA/IS-632—Systems Engineering |
275 |
9.1.3 IEEE-Std-1220—IEEE Standard for Application and Management of the Systems Engineering Process |
277 |
9.1.4 ANSI/EIA-632—Processes For Engineering A System |
284 |
9.1.5 ISO/IEC 15288 System And Software Engineering—System Life Cycle Processes |
290 |
9.1.6 SAE1001: Integrated Project Processes for Engineering a System |
293 |
9.1.7 Other Useful Standards |
294 |
9.2 Review Questions |
296 |
|
|
10 RELATED DISCIPLINES |
|
10.1 Introduction |
299 |
10.2 Project Management |
299 |
10.3 Quality Assurance |
304 |
10.4 Integrated Logistics Support |
305 |
10.5 Operations |
306 |
10.6 Software Engineering |
306 |
10.7 Hardware Engineering |
308 |
10.8 Review Questions |
309 |
|
|
11 SYSTEMS ENGINEERING AND DEVELOPMENT APPROACHES |
|
11.1 Introduction |
311 |
11.2 Waterfall Development |
312 |
11.3 Incremental Development |
314 |
11.4 Evolutionary Development |
317 |
11.5 Prototyping and System Development |
319 |
11.6 Spiral Development Model |
321 |
11.7 Agile Development |
323 |
11.8 Summary |
324 |
11.9 Review Questions |
324 |
|
|
GLOSSARY |
327 |
|
|
INDEX |
331 |