Development of SEBoK v. 1.0

The development of SEBoK v. 1.0 was the work of 70 authors from around the world and took three years – from 2009 to 2012. The first three years of the project were sponsored by the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)), as outlined in detail below. The author team developed 3 draft versions of the SEBoK and received over 3,000 review comments from over 300 reviewers. Complete details on the team that built SEBoK v. 1.0 can be found below.

• Version 0.25 on September 15, 2010 – A prototype that would create the first architecture and early content of the SEBoK for limited review and validation.
• Version 0.5 on September 19, 2011 – A version suitable for early adopters.
• Version 0.75 on March 15, 2012 – An interim version used to gather further community feedback and to address the most critical shortcomings identified in version 0.5.
• Version 1.0 – The first version intended for broad use, v. 1.0 was release on September 14 2012.

After the release of v. 1.0, the BKCASE Governing Board was established; the Governing Board is made of representatives from the International Council on Systems Engineering (INCOSE), the IEEE Computer Society, and the Systems Engineering Research Center (SERC).

Original Editor-in-Chief and Co-Editor-in-Chief

The original BKCASE project was lead by Editor in Chief Art Pyster and Co-Editor in Chief Dave Olwell, who served from 2009 through early 2014. Without their leadership, vision, and drive the project would not have succeeded.

BKCASE Editors-in-Chief
Editor in Chief Art Pyster Stevens Institute of Technology (US) art.pyster@stevens.edu	Co-Editor in Chief David H. Olwell Naval Postgraduate School (US) dholwell@nps.edu

Original Sponsor

The Department of Defense (DoD) recognizes the importance of SEBoK to its own workforce development and has provided substantial financial support and partnership to the BKCASE project. The office of the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)) is the original Department of Defense sponsor for the BKCASE Project. DASD(SE) graciously provided much of the funding for SEBoK development through their Systems Engineering Research Center (SERC) (see http://www.sercuarc.org). Those funds have primarily paid for the time spent by the SEBoK leadership, enabled the many volunteer authors to conduct quarterly physical workshops, and provided for the technical and administrative infrastructure to conduct such a complex distributed project. DASD(SE) has not determined the content of the SEBoK, but instead has allowed the author team and the community to determine what the SEBoK should contain. Without this support over the life of the project, the creation of the SEBoK would not have been possible. Moreover, DASD(SE) has continued to provide substantial support to BKCASE in 2013 through the SERC. Special thanks go to Stephen Welby, Kristen Baldwin, Nicholas Torelli, Don Gelosh, Scott Lucero, and Darren Dusza for their support throughout the BKCASE lifetime.

‘‘This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Systems Engineering Research Center (SERC) under Contract H98230-08-D-0171. SERC is a federally funded University Affiliated Research Center managed by Stevens Institute of Technology. Any opinions, findings, conclusions, or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United States Department of Defense.’’

Core Team

The BKCASE project was supported by a small Core Team of individuals. The Core Team provided content editing support, technical editing support, and handled planning, scheduling, and logistics for the first four years of the project.

BKCASE Core Team
Stephanie Enck Naval Postgraduate School	Nicole Hutchison Stevens Institute of Technology
Devanandham Henry Stevens Institute of Technology	Alice Squires Stevens Institute of Technology
Jame F. Anthony, Jr. Sevatec, Inc.

Part Team Leads

The SEBoK is divided into seven primary Parts (see SEBoK Table of Contents). Through the release of SEBoK v. 1.0, someone graciously volunteered to lead a team of authors in writing the articles and coordinating article integration for each of the Parts. This was an enormous amount of work. We would like to thank each of these individuals for their time, dedication, and leadership. In addition, a member of the editorial staff supported each of the part team leads.

• Part 1 - Barry Boehm
• Part 2 - Richard Adcock
• Part 3 - Garry Roedler
• Part 4 - Harold (Bud) Lawson
• Part 5 - Art Pyster
• Part 6 - David Olwell
• Part 7 - Heidi Davidz

Authors

As a primarily volunteer effort, the BKCASE project depended on dozens of authors from around the world to provide their own time and expenses. Each of the individuals listed below worked many hours to develop and improve SEBoK v. 1.0 and GRCSE v. 1.0. Without each of them, it would have been impossible to succeed. Many of them were supported by their organizations during this effort, including support for travel and labor, and we also gratefully acknowledge the organizational contributions.

Table 1. SEBoK v.1.0 and GRCSE v. 1.0 Authors. (SEBoK Original)

Author	Author
Richard Adcock, Cranfield University and INCOSE, UK	Mo Jamshidi, University of Texas San Antonio, USA
James F. Anthony, Jr., Sevatec, Inc., USA	Cheryl Jones, United States Army, USA
Erik Aslaksen, Sinclair Knight Merz, Australia	Chul Whan Kim, Advisor of KCOSE, Korea
Richard Beasley, Rolls Royce, UK	Naohiko Kohtake, KEIO University, Japan
Barry Boehm, University of Southern California, USA	Harold (Bud) Lawson, Lawson Konsult AB, Sweden
Stuart Booth, Office of the Secretary of Defense, USA	Yeaw Lip Alex Lee, Defence Science and Technology Agency, Singapore
John Brackett, Boston University, USA	Ray Madachy, Naval Postgraduate School, USA
Chuck Calvano, Naval Postgraduate School, USA	James Martin, The Aerospace Corporation, USA
Aaron Eng Seng Chia, National University of Singapore, Singapore	Gregory Mayhew, Boeing, USA
Kyung-il Choe, HUFS, Korea	Steven Mitchell, Lockheed Martin, USA
Matthew Cilli, Stevens Institute of Technology (PhD Candidate), USA	Yaniv Mordecai, Technion - Israel Institute of Technology, Israel
Edmund Conrow, Management and Technology Associates, USA	Ken Nidiffer, Carnegie Mellon SEI and IEEE Systems Council, USA
Paul Croll, CSC, USA	David H. Olwell, Naval Postgraduate School, USA
Cihan Dagli, Missouri University of Science and Technology, USA	Bo Oppenheim, Loyola Marymount University, USA
Judith Dahmann, The MITRE Corporation, USA	Gregory Parnell, United States Military Academy, USA
Heidi Davidz, Pratt & Whitney Rocketdyne, USA	Andy Pickard, Rolls-Royce, USA
Leopoldo Decardenas, Raytheon, USA	Ricardo Pineda, University Texas at El Paso, USA
Johann (Hans) Demmel, Raytheon, USA	Daniel Prun, Ecole Nationale de l'Aviation Civile (ENAC), France
Jeremy Dick, Integrate Systems Engineering Ltd. , USA	Art Pyster, Stevens Institute of Technology, USA
Charles Dickerson, Loughborough University, UK	Garry Roedler, Lockheed Martin, USA
David Dorgan, Raytheon, USA	Jean-Claude Roussel, EADS, France
Dov Dori, Technion, Israel Institute of Technology, Israel and Massachusetts Institute of Technology, USA	Samuel Seymour, Johns Hopkins University, USA
Joseph J. Ekstrom, Brigham Young University, USA	Seiko Shirasaka, KEIO University, Japan
Stephanie Enck, Naval Postgraduate School, USA	Hillary Sillitto, Thales Group and INCOSE, UK
Marcia Enos, Lockheed Martin, USA	Janet Singer, International Society for the Systems Sciences, USA
Dick Fairley, Observer and Author from IEEE, USA	John Snoderly, Defense Acquisition University, USA
Alain Faisandier, Association Francaise d 'Ingenlerie Systeme, France	Ariela Sofer, George Mason University, USA
T.L.J. Ferris, University of South Australia and INCOSE, Australia	Alice Squires, Stevens Institute of Technology, USA
Kevin Forsberg, OGR Systems, USA	Bill Stiffler, Raytheon, USA
G. Richard Freeman, Air Force Institute of Technology, USA	Richard Swanson, ORGANIZATION, USA
Sanford Friedenthal, SAF Consulting, Lockheed Martin (retired) , USA	Massood Towhidnejad, Embry-Riddle Aeronautical University, USA
Brian Gallagher, CACI, USA	Guilherme Horta Travassos, Universidade Federal do Rio de Janeiro (UFRJ), Brazil
Devanandham Henry, Stevens Institute of Technology, USA	Ricardo Valerdi, University of Arizona, USA
Michael Henshaw, Loughborough University, UK	Mary VanLeer, Perceptive Systems, Inc. , USA
Thomas Hilburn, Embry-Riddle Aeronautical University and IEEE Computer Society, USA	Qing Wang, Institute of Software Chinese Academy of Sciences, China
Nicole A.C. Hutchison, Stevens Institute of Technology, USA	Brian Wells, Raytheon, USA (retired)
Duane Hybertson, The MITRE Corporation, USA	Brian White, CAU<SES, USA
Scott Jackson, University of Southern California, USA	Ken Zemrowski, TASC, Inc. , USA

Partners

Partner organizations supported the development of the SEBoK by providing personnel and opportunities to discuss the SEBoK in open forums such as conferences and workshops, and providing valued feedback on draft SEBoK materials. Some organizations have also chosen to have an official representative(s) participate in BKCASE, as shown below. A special thanks to our partners.

• The Institute of Industrial Engineers (IIE). The official IIE representative was Johann "Hans" Demmel.
• The Association for Computing Machinery (ACM). The official ACM Representative was Andrew McGettrick.
• The National Defense Industrial Association (NDIA) Systems Engineering Division. The official NDIA Systems Engineering Division representative was Garry Roedler.

In addition, most authors came from organizations that, although not officially affiliated with BKCASE, nevertheless supported author time and expenses to participate. Collectively, those organizations provided the majority of the labor and expenses that went into creating the SEBoK.

Finally, special thanks go out to INCOSE Presidents Samantha Robitaille and John Thomas for their early and constant support to the SEBoK development.

Wiki Team

The transition from a traditional document to a wiki-based platform was a long one. We are tremendously grateful to the folks who have helped us install, manage, and update the wiki:

• Nicole Hutchison (team lead), Stevens Institute of Technology
• Stephanie Enck (co-lead), Naval Postgraduate School
• Devanandham Henry, Stevens Institute of Technology
• Hans-Peter de Koning, European Space Agency
• Paola Di Maio, University of Strathclyde
• Ray Jorgensen, Rockwell Collins
• Sanford Friedenthal, SAF Consulting
• Jude Ken-Kwofie, Stevens Institute of Technology
• Steven Mitchell, Lockheed Martin
• Robin Valeson, formerly of Stevens Institute of Technology

The wiki is currently supported and hosted by Stevens Institute of Technology. Special thanks go to the Stevens' IT organization.

Technical Editors

Every article went through rounds of technical editing to improve writing quality and consistency. Thanks go to:

• Emily Leach
• Abraham Raher
• Renee Malove
• Justin Gercken
• Dona Lee

Participants in SEBoK Development

The following individuals have provided support to the BKCASE team over the course of the project:

• Johann Amsenga
• John Baras
• Johan Bendz
• Stuart Booth
• Dan Cernoch
• Richard Frost
• Edward Ghafari
• Mike Gourley
• Richard Gryzbowski
• Peter Jackson
• Kenneth Kepchar
• Mike Kreuger
• JoAnn Lane
• Richard Rosenthal
• Sven-Olaf Schulze
• Robert (Bob) Shishko
• Mary Jane Willshire

SEBoK Reviewers

Reviewers are critical to the success and growth of the SEBoK. By providing feedback that represents the diversity of views and opinions on systems engineering, reviewers help the author team identify and describe ground truths for SE as well as areas of contention. The reviewers who provided feedback for earlier versions are listed in Table 3, below. In addition, there are a number of other reviewers who provided their comments directly on the wiki with only a user ID (and not a full name) and reviewers who were part of a group that provided a collective review; these reviewers are not listed in Table 3. Many thanks to all reviewers!

The author team would like to particularly acknowledge the efforts of several INCOSE working groups (WGs) who provided feedback:

• Systems Science WG
• Architecture WG
• Requirements WG
• Decision Analysis WG
• In Service WG
• Lean Systems Engineering WG
• System of Systems WG
• Process Improvement WG

The adjudication of all SEBoK review comments for all versions can be found at SEBoK Review and Adjudication.

Table 3. Reviewers of earlier SEBoK versions. (SEBoK Original)

Reviewer	Reviewer
Aase Jakobsson	Julie P. Gann, Northrop Grumman Information Systems
Ada Hunter, Lockheed Martin	Kal Toth, Portland State University
Adeel Khalid, Southern Polytechnic State University	Karen Charron, Raytheon
Alan D Harding, BAE Systems	Karen J Richter, Institute for Defense Analyses
Alan Knott, Parsons Brinckerhoff	Karl Best, Project Management Institute
Ali Bahraman, Raytheon	Ken Ellis, Northrop Grumman Aerospace Systems
Andrew Farncombe, John Boardman Associates	Kennedy Conway
Andrew McGettrick, The Association for Computing Machinery (ACM)	Kenneth Morris
Anne Sigogne, THALES	Kim Halladay
Annette Reilly, Lockheed Martin	Krister Sutinen, Siemens Industry Software AB
Arjan van Druten	Lajuane Brooks, Aurora Sciences
Arnold Neville Pears, Uppsala University	Larri Rosser, Raytheon IIS
Bart Terrery, Lockheed Martin	Laurie Nasta, Booz Allen Hamilton
Berger, Northrop Grumman Corporation	Loïc Fejoz, RealTime-at-Work
Bernadette Gasmi, EADS Airbus	Lori Zipes, NAVSEA NSWC Panama City Division (US Dept of Navy)
Beth Wilson, Raytheon	Lou Oddo, Northrop Grumman Aerospace Systems
Bob Epps and a consolidated review, Lockheed Martin	Louisa Guise, Raytheon
Bobinis, Lockheed Martin	M.T.F.M. van de Ven, INCOSE ISSWG
Bruce Elliott, Arbutus Technical Consulting	Marcel van de Ven, Movares Nederland b.v.
Bruce Munro, Raytheon Space and Airborne Systems	Mark Ardis, Stevens Institute of Technology
Bryan E. Herdlick, Applied Physics Laboratory, Johns Hopkins University	Mark Lane, IBM
Chia Eng Seng Aaron, National University of Singapore	Mark Maier, The Aerospace Corporation
Curran Hawkins	Martin Griss, Carnegie Mellon University
Curt Zielinski, Lockheed Martin	Martin Nazareth
Dahai Liu, Embry-Riddle Aeronautical University	Matthew Petty
Dan Dillery	Measurement While Drilling
Daniel J Dechant, Raytheon	Michael Bisconti, Lockheed Martin
Daniel Mulvihill, Pratt & Whitney Rocketdyne	Michael C. Dapp, Lockheed Martin MS2
David D. Walden, INCOSE & Sysnovation LLC	Michael Coughenour, Lockheed Martin
David Kraus, Northrop Grumman Electronic Systems	Michael O'Neill, Georgia Tech Research Institute
David Mason, Lockheed Martin	Michael Ryan, INCOSE Requirements Working Group
David Quastel	Michael Stringer, US Air Force
David Yarbrough, Northrop Grumman Corporation	Michael Wilkinson, Niteworks/Atkins
Dawn Sabados, University of Alabama Huntsville	Michaelson, Lockheed Martin
Denis Bertrand & others, Department of National Defence	Michele Hanna, Lockheed Martin
Dennis Moen, Lockheed Martin	Mike Gayle, Boeing
Donald Larson	Mike O’Neill, Georgia Tech Research Institute
Donald Robertson, Lockheed Martin MS2	Mike Prendergast
Duncan Kemp, Department for Transport	Mike Stemig, Raytheon
Edmond Tonnellier, Thales	Mike Yokel, Lockheed Martin
Emile Anderson, Raytheon IDS	MPHO R
Florian Schneider	MWD Tools
Francis M. Joyner, Raytheon	Nelson Roberts, Lockheed Martin
Frédéric Autran, EADS - Cassidian Systems	Odile Mornas, Thales Université
Gauthier Fanmuy, AND	Paola Di Maio, University of Strathclyde
Geoffrey A. Shuebrook, Lockheed Martin	Patra Stroemer, Lockheed Martin
George Rebovich, MITRE	Paul Joannou, IEEE Computer Society
Gerald H. Fisher	Paul Martellock, LMT
Gerard Auvray, Astrium Satellite	Peter Brook, Dashwood Consulting Ltd
Gerlach	Peter Mcgee, Lockheed Martin
Gilles Meuriot, AREVA TA	Pierre Labreche, CMC Electronics
Gorman Findley, Raytheon	Pieter Botman, Independent
Greg Brown, Lockheed Martin	Ray Jorgensen, Rockwell Collins
Hagar, Lockheed Martin	Reagan Harper, SEAKR Engineering Inc.
Hans van Vliet, VU University, Amsterdam	Richard Rifelli, Northrop Grumman Corporation
Harold Baker	Rob Schaaf, IEEE
Harold Mooz, HMA	Robert Cantrell, Raytheon IDS
Henry Broodney	Robert Mottl, NGAS
Howard Eisner, George Washington University	Robert Rathbone, EADS - Cassidian Systems
Hubert Ernest Cody, Raytheon	Robert Shishko, NASA
IEEE Computer Society (collective review)	Roddey Smith, NGC/NGAS/AMS/CWIN
Ian Sommerville, University of St. Andrews	Roger C. Pare, Lockheed Martin MS2
Ivan Mactaggart, AWE PLC	Rolan Mazzella, Thales
J Mason, Stevens Institute of Technology	Ronald Fradenburg, Ingalls Shipbuilding
Jack Ring, Educe LLC	Roxann Marumoto, Raytheon
Jaluane Brooks, Aurora Sciences	Scott Werner, Honeywell Technology Services Inc.
James Mason, Cornell University	Shirley Tseng, INCOSE
James J. Peter, Johns Hopkins University	Spurge Norman, MITRE
James Jamison, IBM	Stan Rifkin, Stevens Institute of Technology
James Lentz, Northrop Grumman Corporation	Stephanie White, Long Island University, C.W. Post Campus
James van Gaasbeek, Northrop Grumman Aerospace Systems	Stephen Townsend, PMI
Jay Mandelbaum, Institute for Defense Analyses	Susan Ferreira, University of Texas at Arlington
Jean-luc Garnier	Susan Murray, Missouri S&T
Jean-Luc Wippler, LUCA Ingénierie	Theodora Saunders, IEEE AES, IEEE Sys Council, AHS
Jeff Lankford, The Aerospace Corporation	Thomas Tudron, Lockheed Martin
Jennifer Milligan, Lockheed Martin MS2	Timothy W. Lohr, Lockheed Martin MS2
Jeremy I. Stuart, Boeing	Velda G. Musgrove, Lockheed Martin MS2
JG Demmel, Raytheon	Vidyut Navelkar, Tata Consultancy Services Ltd.
Jim Smith, Lockheed Martin	Vincenzo Arrichiello, SELEX Sistemi Integrati SpA
Joan E. Nolan, Northrop Grumman Corporation	Wayne Collier, Siemens PLM Software
JoAnn Lane	Wayne O’Brien, Raytheon
Joe Jenney	Weaver, Lockheed Martin
John Clark, Northrop Grumman Corporation and INCOSE	William Ely
John Goodwin, US Navy	William Golaz, Lockheed Martin Aeronautics
John Harauz, Jonic Systems Engineering	William J. Brocker, Brocker Engineering
John R Tubb	William Moore, Northrop Grumman Corporation
Johnny Duckworth, Space & Airborne Systems/Systems Development Center	William R. Lyders, ASSETT Inc.
Jon Holt, Atego	Yoshihiro Matsumoto, ASTEM Research Institute
Jose Luis Fernandez Sanchez, Madrid Technical University (UPM)	Yvonne Simms, Boeing
Julie DeMeester, Raytheon

Development of the SEBoK

Previous work to develop a guide to the systems engineering (SE) body of knowledge includes an International Council on Systems Engineering (INCOSE) sponsored online version of the Guide to the Systems Engineering Body of Knowledge (G2SEBOK) (INCOSE 2002). The G2SEBOK effort, which ended around 2004, is unrelated to BKCASE and the SEBoK despite the similarity in name. The INCOSE SE Handbook is quite popular and has continued to evolve, and has been the de facto community statement of systems engineering (SE) knowledge and structure until the SEBoK (INCOSE 2012).

Systems engineering (SE) knowledge has also been documented through the standards bodies, including ISO/IEC/IEEE 15288 Systems Engineering-System Life Cycle Processes (2008), IEEE/EIA 12207 Software Life Cycle Processes (2008), and ANSI/EIA 632 Processes for Engineering a System (2003).

These efforts offer a foundation for the SEBoK, which goes beyond them by providing a comprehensive and regularly refreshed view of all SE knowledge.

The scale and complexity of BKCASE emerged over the first few months of the project. Systems engineering is large and relatively immature when compared to more classic engineering disciplines, such as electrical and mechanical engineering. We are extremely pleased with how the community rose to the challenge. New authors continually stepped up when gaps in the writing team were identified and we routinely assembled 25 to 30 authors every three months in a multi-day workshop to iron out issues and make key decisions.

One of the most critical decisions occurred in January 2011, when the team confirmed a switch to a wiki-based presentation for the body of knowledge. This added much complexity to the effort, but offered great advantages in terms of the modularity for update, access to interim material by the authors, easy review and suggestions for improvements, and flexible navigation. In hindsight, the impact of choosing a wiki was much greater than we understood, but we are very happy we went down that path. We believe this format to present the body of knowledge will serve the SE community much better than if we had produced a traditional PDF or Word document.

The SEBoK is intended to evolve and morph with use and with changes in the field. The wiki structure is particularly well-suited for promoting that purpose. Users are asked to comment about what they like and dislike, what is missing and what should be removed. New articles will be added and existing articles updated regularly.

To help ensure both the quality of the SEBoK and its acceptance by the community, it was vital that the SEBoK be created with an open collaborative process. Specifically, each version had public review and each review comment was adjudicated. The adjudication results can be found at SEBoK Review and Adjudication.

SEBoK Version 0.25

The first version of the SEBoK – a prototype labeled version 0.25 – was released as a document for limited review in September of 2010. A total of 3135 comments were received on this document from 114 reviewers across 17 countries. The author team reviewed these comments, paying particular attention to the reviews related to content and highlighting diversity within the community. The adjudication of version 0.25 comments may be seen here.

SEBoK Version 0.75

Based on the review comments, the authors first began by reorganizing the SEBoK to better align with the types of information included. The architecture was amended to add a handful of new articles and also about a third of the articles were revised.

SEBoK Version 0.5

In January of 2011, the authors agreed to transition from a document-based SEBoK to a wiki-based SEBoK, with the intent to make the information readily accessible worldwide, provide additional methods for searching and navigating the content, and provide a forum for the community to provide feedback while keeping the content of the SEBoK stable between versions.

This second version of the SEBoK was released for world-wide comment in September of 2011. About 500 comments from approximately 40 reviewers were received. Selected comments were addressed in version 0.75, while others were deferred until version 1.0.

SEBoK Version 1.0

Version 1.0, released in September of 2012, was the first version for broad community use. It made further revisions to the architecture, through adding, deleting, and moving articles. Most of the issues from the 0.5 and 0.75 reviews that had been deferred were addressed, though some issues were deferred to post-version 1.0 releases. All comments from all previous review cycles were entered into the final adjudication matrix and addressed. Additional wiki enhancements were added.

SEBoK Version 1.0.1

This micro update, released in November of 2012, fixed a number of spelling and grammatical errors, corrects errors in acknowledgments, and made other very modest improvements to version 1.0 of the SEBoK. There were no edits to individual articles to: improve clarity or content, add references to new publications since version 1.0 was released, improve wiki navigation and operation, or make other more substantial changes. Comments from version 1.0 were collected and archived for adjudication in version 1.1 or later.

References

Works Cited

ANSI/EIA. 2003. Processes for Engineering a System. Philadelphia, PA, USA: American National Standards Institute (ANSI)/Electronic Industries Association (EIA), ANSI/EIA 632‐2003.

INCOSE. 2002. "Guide to the Systems Engineering Body of Knowledge -- G2SEBoK." San Diego, CA, USA: International Council on Systems Engineering (INCOSE).

INCOSE. 2012. INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2008.

ISO/IEEE. 2008. Systems and Software Engineering - Software Life Cycle Processes. Geneva, Switzerland: International Organization for Standards (ISO)/Institute of Electrical & Electronics Engineers (IEEE) Computer Society, ISO/IEEE 12207:2008(E).

Primary References

ANSI/EIA. 2003. Processes for Engineering a System. Philadelphia, PA, USA: American National Standards Institute (ANSI)/Electronic Industries Association (EIA), ANSI/EIA 632‐2003.

INCOSE. 2012. INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2

ISO/IEC/IEEE. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2008.

Additional References

None.