|
|
| (181 intermediate revisions by 8 users not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| + | [[File:Hutchison,Nicole Profile.jpeg|right|200px]] |
| − | ==History, Motivation, and Value==
| |
| − | The Body of Knowledge and Curriculum to Advance Systems Engineering Project (BKCASE) began to create a community-based ''Guide to the Systems Engineering Body of Knowledge (SEBoK)'' and a ''Graduate Reference Curriculum for Systems Engineering (GRCSE)'' in fall of 2009 (Pyster and Olwell et al. 2012) (Please see http://www.bkcase.org for more information). The SEBoK came into being out of a recognition that the systems engineering (SE) discipline could benefit greatly by having a living authoritative guide that discusses what is included in the discipline, how the discipline should be structured to facilitate understanding, and what documents are the most important to the discipline. A key principle of the BKCASE project is that the SEBoK and GRCSE will always be available free worldwide – including the revisions to those products.
| |
| | | | |
| − | Through the end of 2012, BKCASE was led by Stevens Institute of Technology and the Naval Postgraduate School in coordination with several professional societies and sponsored by the U.S. Department of Defense (DoD), which provided generous funding. Volunteers from dozens of companies, universities, and professional societies across 10 countries contributed many thousands of hours writing the SEBoK articles; their organizations provided significant other contributions in-kind. For additional information on the BKCASE authors, please see the [[Acknowledgements]] article.
| + | {| |
| − | | + | |- |
| − | 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.
| + | |<center>''The ''Editor’s Corner'' provides perspective from the Editor in Chief on critical topics for systems engineering, either through their own words or by inviting a guest writer.''</center> |
| − | | + | |} |
| − | 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.
| |
| − | | |
| − | 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]].
| |
| − | | |
| − | The earliest value of the SEBoK has simply been the greater sense of community that has developed among the authors, which include many fellows of professional societies and other leaders in the field. For example, the relationship between Systems Science and Systems Engineering is now more clearly understood than in the past. This relationship is captured in Parts 2 and 3 of the SEBoK.
| |
| − | | |
| − | The greater value of the SEBoK, of course, comes from use by the community. As of the end of October 2013, SEBoK articles have been accessed more than 200,000 times and early usage reports are quite encouraging. We hope the SEBoK will regularly be used by thousands of systems engineers around the world as they undertake such activities as creating systems architectures, developing career paths for systems engineers, and deciding new curricula for systems engineering university programs.
| |
| − | | |
| − | 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.
| |
| − | | |
| − | At the beginning of 2013, with version 1.0 of both SEBoK and GRCSE released, BKCASE transitioned to a new governance model with shared stewardship between the Systems Engineering Research Center (SERC) (see http://www.sercuarc.org), the International Council on Systems Engineering (INCOSE) (see http://www.incose.org), and the Institute of Electrical and Electronics Engineers Computer Society (IEEE-CS) (see http://www.computer.org). This new governance structure was formalized in an agreement between the three stewards that was finalized in spring of 2013. The stewards have reconfirmed their commitment to the key principle that SEBoK and GRCSE will be available at no cost to the users.
| |
| − | | |
| − | ==SEBoK Philosophy==
| |
| − | The SEBoK is sometimes compared to Wikipedia. The SEBoK is like Wikipedia in its most fundamental structure, as it is a collection of wiki articles built on MediaWiki technology. However, the SEBoK is unlike Wikipedia in that its content is carefully controlled. Anyone in the community can suggest changes be made to SEBoK articles, but no one except the SEBoK Editors can actually implement those changes in the SEBoK wiki. Wikipedia is a much more open wiki, allowing virtually anyone to change any article, while reserving the right to undo changes that are offensive or otherwise violate Wikipedia's rules. Tight control over SEBoK content is a tradeoff. Such control ensures a stable baseline whose quality and integrity are assured by its editors. On the other hand, such control discourages some members of the community from contributing improvements to the SEBoK.
| |
| − | | |
| − | To satisfy both the need for a stable baseline and the desire for broader community involvement, we have implemented a new collaborative space. The ''SEBoK Sandbox'' is a copy of the SEBoK that is separate from the baseline version where anyone in the community can edit articles, recommend new content, or provide comments on existing articles. It is important to note that while anyone in the community can gain access to the Sandbox, all submissions must still be approved by the Editorial Board before they will be folded into a new baseline version of the SEBoK. For more information on how this works, please '''[http://www.sebokwiki.org/sandbox visit the Sandbox]'''.
| |
| − | | |
| − | ==Version 1.2==
| |
| − | This version of the SEBoK was released 15 November 2013. This is a minor release of the SEBoK which includes two new articles, a rewrite of one article, updates to existing articles, and new primary references. The Editorial Board plans to release the next version of the Sandbox in late November 2013.
| |
| − | | |
| − | Changes between versions 1.1.2 and version 1.2 include:
| |
| − | *Two new articles: [[Integrating Supporting Aspects into System Models]] and [[Technical Leadership in Systems Engineering]]
| |
| − | *Heavy revision to [[Decision Management]]
| |
| − | *Minor edits to articles in Parts 1, 2, 3, 4, 5, and 6 and
| |
| − | *Two new primary references.
| |
| − | | |
| − | ==Version 1.1.2==
| |
| − | Version 1.1.2 was released 1 August 2013 as a micro release that corrected some errors and added some wiki functionality. The biggest change in the release of v. 1.1.2 was the co-release of the companion SEBoK Sandbox, a collaborative space for the systems engineering community.
| |
| | | | |
| − | Changes between versions 1.1.1 and 1.1.2 included:
| + | <div style="text-align:right">'''20 November 2023'''</div> |
| − | * Version numbers were removed from page titles to improve maintenance of links
| |
| − | * Reflection of the governance of the SEBoK and oversight through the Editorial Board, including a page called [[Meet the Editors]].
| |
| − | * A few references were updated, notably in the [[Safety Engineering]] article.
| |
| | | | |
| − | No comments were adjudicated for this micro release.
| + | The formal discipline of systems engineering emerged in the first half of the 20th century. Over the last 80+ years, it has evolved from first principles to a process-focused field that generally operates in the defense and aerospace domains to a transdisciplinary one focusing on the integration and interaction between technology and people across a variety of domains. In its ''Vision 2035'', the International Council on Systems Engineering (INCOSE), states that “the practice of systems engineering will further evolve to support the demands of ever-increasing system complexity and enterprise competitiveness. By 2035, systems engineering will leverage the digital transformation in its tools and methods and will be largely model-based using integrated descriptive and analytical digital representations of the systems. Systems design, analysis, and simulation models, immersive technologies, and an analytic framework will enable broad trade-space exploration, rapid design evolution, and provide a shared understanding of the system throughout its life cycle.” |
| | | | |
| − | ==Version 1.1.1 ==
| + | The Systems Engineering Research Center [http://www.sercuarc.org (SERC)] led the initial creation of the ''Guide to the Systems Engineering Body of Knowledge'' (SEBoK, pronounced “see-bach”). In 2009, the SERC began the three-year process of developing the SEBoK with a team of over 70 authors from around the world. Version 1.0 was published in 2012 and inpast 11 years the SEBoK has evolved in many ways: new topics, the inclusion of videos, a major rearrangement of the discussion, and perhaps most importantly, the addition of an area dedicated to the emerging topics of systems engineering. |
| | | | |
| − | This version was released 14 June 2013 as a micro release that corrected some errors and added some wiki functionality.
| + | Over the years, the SEBoK has been led by several Editors in Chief: |
| | + | *Art Pyster and Dave Olwell led the development of SEBoK through version 1.0, including the decision to implement the SEBoK as a wiki. |
| | + | *Rick Adcock, appointed the first Editor in Chief after the transition of SEBoK from a research task to a community-led effort, helped identify new members of the editorial board and oversaw the addition of the first domain-focused knowledge area, [[Healthcare Systems Engineering]]. |
| | + | *Rob Cloutier added the first new part to the SEBoK since its initial release: [[Emerging Knowledge]], which captures topics that are critical for systems engineers but for which the knowledge is not yet settled (e.g. artificial intelligence applications to systems engineering). Rob also fostered the addition of multi-media to the SEBoK and created and built upon articles about the discipline, including [[A Brief History of Systems Engineering]]. |
| | | | |
| − | Changes between versions 1.1 and 1.1.1 included:
| + | I am honored to have been asked to be the newest Editor in Chief of the SEBoK. And like every Editor in Chief before me, I am extremely lucky to work with a group of editors and authors from around the world that have consistently supported the SEBoK. These people are critical representatives of the global systems engineering community, and the SEBoK would not be possible without their tireless efforts. |
| − | * Version numbers were removed from page titles to improve maintenance of links
| |
| − | * Spelling errors in contributor names were corrected.
| |
| − | * 'Cite This Page' was revised and improved.
| |
| − | * A few references were updated, notably in the [[Safety Engineering]] article.
| |
| − | * Meta-tags were improved to increase visibility to search engines
| |
| − | * Wiki navigational features --- especially breadcrumbs --- were improved.
| |
| − | * A counter was added to record PDF downloads.
| |
| − | | |
| − | No comments were adjudicated for this micro release.
| |
| − | | |
| − | ==Version 1.1==
| |
| − | This version, released 26 April 2013, is a minor release which updates many topic articles and glossary articles.
| |
| − | | |
| − | Changes that were made include:
| |
| − | * Fourteen topic articles were updated in Parts 1, 2, 3, and 6, for the purpose of expanding or improving the explanation of the topic, or in some cases to add new references.
| |
| − | * Sixteen glossary terms were updated and two new glossary terms were added.
| |
| − | * The [[Acknowledgements]] page was updated to reflect the significantly revised governance structure for the SEBoK, which added many new contributors in varying roles.
| |
| − | * The [[Main Page]] and other Quicklinks pages were modified to reflect the new version.
| |
| − | * The SEBoK Evolution article formerly in SEBoK v. 1.1 Introduction was deleted, being replaced by an updated version – this Editor's Note article.
| |
| − | | |
| − | There were no changes to wiki navigation and operation. Comments from version 1.0.1 that were adjudicated were deleted from DISQUS, while comments still to be adjudicated remain in the wiki.
| |
| − | | |
| − | ==Upcoming Releases==
| |
| − | | |
| − | We will regularly update the SEBoK to correct errors, improve existing articles, add new articles, and respond to specific comments from the user community. The current plan is to issue occasional micro updates and two minor updates a year for the first two years, and then decide whether a larger more major revision is needed in the third year or whether additional micro and minor revisions are adequate. Micro updates correct spelling errors and sentence grammar and make other very modest changes and occur as needed. They are identified by three digits - Version 1.x.y. Version 1.0.1 was the first micro release. Minor updates will correct errors, continue to add content to existing articles, including any new references published recently, and perhaps add articles to existing knowledge areas. Minor updates will not change the basic organization of the SEBoK. The editors may not respond to all comments posted in DISQUS for the minor updates. This release, Version 1.1, is the first minor update. Major updates will be unconstrained. All accumulated comments and suggestions will be adjudicated for the major updates, and the adjudication results will be posted for the community.
| |
| − | | |
| − | New releases are under the control of a Governing Board appointed by the stewards, who oversee the SEBoK Editor-in-Chief, Co-Editor-in-Chief, and an Editorial Board. The stewards contribute resources to manage the SEBoK wiki, support new releases, and encourage SEBoK adoption. Volunteer authors from the world-wide SE community continue to propose and create new content and other volunteers review that new content.
| |
| − | | |
| − | The next minor release will be Version 1.2, currently scheduled for release in October 2013. At least one new article on ''Systems Engineering Education'' will be included in Part 5, but we suspect several more new articles will be included as well. The editors also plan to have implemented the process for updating references systematically, and intend to include references published since version 1.0, as appropriate to each article.
| |
| − | | |
| − | | |
| − | [[File:EditorsinChiefSignatures.png||center|400px]]
| |
| − | | |
| − | | |
| − | | |
| − | <center>
| |
| − | {|
| |
| − | |-
| |
| − | |style="background-color: #ffffff"|[[File: Stevens.jpg|300px|center|Stevens Institute of Technology]] |
| |
| − | |style="background-color: #ffffff"|[[File:Systems_Engineering_Logo_r3.JPG|552px|center|Naval Postgraduate School's Systems Engineering Department]]
| |
| − | |}
| |
| − | </center>
| |
| | | | |
| − | ==Works Cited==
| + | Looking forward as the discipline of systems engineering evolves, the SEBoK will need to evolve with it. At my first INCOSE International Symposium in 2008, I heard about something called "model-based systems engineering". The last 5 years have seen a tremendous push toward "digital engineering". Both of these are currently reflected in the SEBoK, but we need to do more. Digital transformation is a critical topic for systems engineers and will continue to be for at least the next decade. But the true end state is not that we as a discipline create new pockets of practice but that instead we move as a community toward a data- and model-enabled way of working. My sincere hope is that in 2033, we will talk not about MBSE or DE but about systems engineering with models and data a standard part of practice. To that end, I'm pleased to share that we have assembled a team whose mission is to integrate the discussion of using models and data throughout the SEBoK and that Rob Cloutier has agreed to spearhead this effort. |
| | | | |
| − | Pyster, A., D.H. Olwell, T.L.J. Ferris, N. Hutchison, S. Enck, J.F. Anthony, D. Henry, and A. Squires (eds). 2012. ''Graduate Reference Curriculum for Systems Engineering (GRCSE™),'' version 1.0. Hoboken, NJ, USA: The Trustees of the Stevens Institute of Technology ©2012. Available at: http://www.bkcase.org/grcse-10/.
| + | Finally, I encourage anyone with an interest to reach out to the SEBoK team [mailto:sebok@incose.net sebok@incose.net]. We welcome your feedback and insights and look forward to partnering with you as we move toward the SEBoK of the future. |
| | | | |
| − | {{DISQUS}}
| + | Sincerely, |
| | + | [[File:Hutchison_Signature.png|200px|left]] |
Error creating thumbnail: File missing
| The Editor’s Corner provides perspective from the Editor in Chief on critical topics for systems engineering, either through their own words or by inviting a guest writer.
|
20 November 2023
The formal discipline of systems engineering emerged in the first half of the 20th century. Over the last 80+ years, it has evolved from first principles to a process-focused field that generally operates in the defense and aerospace domains to a transdisciplinary one focusing on the integration and interaction between technology and people across a variety of domains. In its Vision 2035, the International Council on Systems Engineering (INCOSE), states that “the practice of systems engineering will further evolve to support the demands of ever-increasing system complexity and enterprise competitiveness. By 2035, systems engineering will leverage the digital transformation in its tools and methods and will be largely model-based using integrated descriptive and analytical digital representations of the systems. Systems design, analysis, and simulation models, immersive technologies, and an analytic framework will enable broad trade-space exploration, rapid design evolution, and provide a shared understanding of the system throughout its life cycle.”
The Systems Engineering Research Center (SERC) led the initial creation of the Guide to the Systems Engineering Body of Knowledge (SEBoK, pronounced “see-bach”). In 2009, the SERC began the three-year process of developing the SEBoK with a team of over 70 authors from around the world. Version 1.0 was published in 2012 and inpast 11 years the SEBoK has evolved in many ways: new topics, the inclusion of videos, a major rearrangement of the discussion, and perhaps most importantly, the addition of an area dedicated to the emerging topics of systems engineering.
Over the years, the SEBoK has been led by several Editors in Chief:
- Art Pyster and Dave Olwell led the development of SEBoK through version 1.0, including the decision to implement the SEBoK as a wiki.
- Rick Adcock, appointed the first Editor in Chief after the transition of SEBoK from a research task to a community-led effort, helped identify new members of the editorial board and oversaw the addition of the first domain-focused knowledge area, Healthcare Systems Engineering.
- Rob Cloutier added the first new part to the SEBoK since its initial release: Emerging Knowledge, which captures topics that are critical for systems engineers but for which the knowledge is not yet settled (e.g. artificial intelligence applications to systems engineering). Rob also fostered the addition of multi-media to the SEBoK and created and built upon articles about the discipline, including A Brief History of Systems Engineering.
I am honored to have been asked to be the newest Editor in Chief of the SEBoK. And like every Editor in Chief before me, I am extremely lucky to work with a group of editors and authors from around the world that have consistently supported the SEBoK. These people are critical representatives of the global systems engineering community, and the SEBoK would not be possible without their tireless efforts.
Looking forward as the discipline of systems engineering evolves, the SEBoK will need to evolve with it. At my first INCOSE International Symposium in 2008, I heard about something called "model-based systems engineering". The last 5 years have seen a tremendous push toward "digital engineering". Both of these are currently reflected in the SEBoK, but we need to do more. Digital transformation is a critical topic for systems engineers and will continue to be for at least the next decade. But the true end state is not that we as a discipline create new pockets of practice but that instead we move as a community toward a data- and model-enabled way of working. My sincere hope is that in 2033, we will talk not about MBSE or DE but about systems engineering with models and data a standard part of practice. To that end, I'm pleased to share that we have assembled a team whose mission is to integrate the discussion of using models and data throughout the SEBoK and that Rob Cloutier has agreed to spearhead this effort.
Finally, I encourage anyone with an interest to reach out to the SEBoK team sebok@incose.net. We welcome your feedback and insights and look forward to partnering with you as we move toward the SEBoK of the future.
Sincerely,
Error creating thumbnail: File missing