SYSTEMS ENGINEERING HANDBOOK

1 SYSTEMS ENGINEERING HANDBOOKA GUIDE FOR system LIFE CYCLE PROCESSES AND ACTIVITIESINCOSE-TP-2003-002-03 June 2006 INCOSE SYSTEMS ENGINEERING HANDBOOK v. 3 Copyright 2006 International Council on SYSTEMS ENGINEERING , subject to restrictions listed on the inside ENGINEERING HANDBOOKA GUIDE FOR system LIFE CYCLE PROCESSES AND ACTIVITIESINCOSE-TP-2003-002-03 INCOSE SYSTEMS ENGINEERING HANDBOOK , version 3 June 2006 Edited by:Cecilia HaskinsiiCopyright 2006 International Council on SYSTEMS ENGINEERING , subject to restrictions listed on the inside 2006 INCOSE SYSTEMS ENGINEERING HANDBOOK v. 3 This INCOSE Technical Product was prepared by the SYSTEMS ENGINEERING HANDBOOK Development Team of the International Council on SYSTEMS ENGINEERING (INCOSE).

2 It is approved by INCOSE for release as an INCOSE Technical 2006 by INCOSE, subject to the following restrictions:Author use: Authors have full rights to use their contributions in a totally unfettered way with credit to this INCOSE Technical Product. Abstraction is permitted with credit to the use: Permission to reproduce this document and use this document or parts thereof by members of INCOSE and to prepare derivative works from this document for INCOSE use is granted, with attribution to INCOSE and the original author(s) where practical, provided this copyright notice is included with all reproductions and derivative works.

3 Content from ISO/IEC 15288:2002(E) are used by permission, and are not to be reproduced other than as part of this total use: This document may not be shared or distributed to any non-INCOSE third party. Requests for permission to reproduce this document in whole or part, or to prepare derivative works of this document for external and commercial use, should be addressed to the INCOSE Central Office, 2150 N. 107th St., Suite 205, Seattle, WA 98133-9009 version use: Any electronic version of this SYSTEMS ENGINEERING HANDBOOK is to be used for personal use only and is not to be placed on a non-INCOSE sponsored server for general use.

4 Any additional use of these materials must have written approval from : INCOSE has granted permission to member companies of the INCOSE Corporate Advisory Board to post and use this document internally, subject to the external use 2006 International Council on SYSTEMS ENGINEERING , subject to restrictions listed on the inside 2006 INCOSE SYSTEMS ENGINEERING HANDBOOK v. 3 PrefaceObjectiveThe INCOSE SYSTEMS ENGINEERING HANDBOOK , version 3 (SEHv3), represents a shift in paradigm toward global industry application consistent with the SYSTEMS ENGINEERING Vision. The objective for this document is to provide an updated description of the key process activities performed by SYSTEMS engineers.

5 The intended audience is the new SYSTEMS engineer, an engineer in another discipline who needs to perform SYSTEMS ENGINEERING or an experienced SYSTEMS engineer who needs a convenient descriptions in this HANDBOOK show what each SYSTEMS ENGINEERING process activity entails, in the context of designing for affordability and performance. On some projects, a given activity may be performed very informally ( , on the back of an envelope, or in an engineer s notebook); on other projects, very formally, with interim products under formal configuration control. This document is not intended to advocate any level of formality as necessary or appropriate in all situations.

6 The appropriate degree of formality in the execution of any SYSTEMS ENGINEERING process activity is determined by:a. the need for communication of what is being done (across members of a project team, across organizations, or over time to support future activities),b. the level of uncertainty,c. the degree of complexity, andd. the consequences to human smaller projects, where the span of required communications is small (few people and short project life cycle) and the cost of rework is low, SYSTEMS ENGINEERING activities can be conducted very informally (and thus at low cost). On larger programs, where the cost of failure or rework is high, increased formality can significantly help in achieving program opportunities and in mitigating program a project environment, work necessary to accomplish project objectives is considered in scope; all other work is considered out of scope.

7 On every project, thinking is always in scope. Thoughtful tailoring and intelligent application of the SYSTEMS ENGINEERING process described in this HANDBOOK is essential to achieve the proper balance between the risk of missing project technical and business objectives on the one hand, and process paralysis on the other. Chapter 10 provides tailoring guidelines to help achieve that 2006 International Council on SYSTEMS ENGINEERING , subject to restrictions listed on the inside 2006 INCOSE SYSTEMS ENGINEERING HANDBOOK v. 3It is the intention of the SEHv3 steering committee that appendices will be developed to elaborate on significant topics, and that these appendices will be available on-line to members in the INCOSE Product Asset Library (IPAL).

8 The addition of these on-line descriptions, work sheets, checklists, and how-to guides will evolve over time, and it is anticipated that all INCOSE members, working groups, and Corporate Advisory Board member companies will contribute to the creation of this resource. Actual content will be under the control of the IPAL working :Terje Fossnes, Chair, INCOSE SEHv3 Development TeamKevin Forsberg, Co-Chair, INCOSE SEHv3 Development TeamEric Aslaksen, INCOSE Associate Director, Technical ReviewSamantha Brown, INCOSE Technical DirectorvCopyright 2006 International Council on SYSTEMS ENGINEERING , subject to restrictions listed on the inside 2006 INCOSE SYSTEMS ENGINEERING HANDBOOK v.

9 3 AcknowledgmentsThe INCOSE SYSTEMS ENGINEERING HANDBOOK version 3 development team owes a debt of gratitude to all the contributors to prior editions (versions 1, 2, and 2a). The framework they provided gave a solid basis for moving ahead with this version. However this present document represents a significant departure from its predecessors since the goal was to create a shorter document consistent with the international standard ISO/IEC 15288:2002(E) SYSTEMS ENGINEERING system life cycle processes. As a result, we will not list all the contributors to earlier versions; interested readers are referred to the acknowledgment pages in those want to thank the two co-chairs who worked with us in the formative stages of this HANDBOOK : John Leonard and Jim Chism.

10 They provided valuable guidance and leadership in the difficult transition from a HANDBOOK based on the earlier versions to one based on ISO/IEC would be difficult to accurately characterize the specific contributions of each of the volunteers section leads, steering committee, authors, and reviewers. Many served in multiple roles. A great deal of effort and enthusiasm was provided by the section leads and key authors, most of who also served on the steering committee. We acknowledge them in alphabetical order: Karen Bausman, Joe Carl, Sandy Friedenthal, Karl Geist, Ken Kepchar, Mike Krueger, Harold Kurstedt, Sean O Neill, Mike Persson, Mary Redshaw, Andy Schuster, L.