|
|
| (289 intermediate revisions by 10 users not shown) |
| Line 1: |
Line 1: |
| − | '''Please note that in order to provide review comments, you will use the DISQUS feature at the bottom of each article. You may login to DISQUS using existing accounts (e.g. Google, Yahoo, Twitter, or Facebook) or you may create a DISQUS account. Please look for the BKCASE posts under the discussion for each article, which provide specific guidance for reviewers.'''
| + | [[File:Hutchison,Nicole Profile.jpeg|right|200px]] |
| − | | |
| − | ==Overview==
| |
| − | BKCASE (pronounced "Bookcase") is the acronym for the Body of Knowledge and Curriculum to Advance Systems Engineering project. The BKCASE team is developing two products, a Guide to the Systems Engineering Body of Knowledge (SEBoK) and a Graduate Reference Curriculum for Systems Engineering (GRCSE).
| |
| − | | |
| − | The current content of [[Guide to the Systems Engineering Body of Knowledge (SEBoK) v. 0.75|www.sebokwiki075.org]] represents version 0.75 of the SEBoK. To be clear:
| |
| − | * The SEBoK is not the compendium of all systems engineering knowledge; instead, in its final form it is intended to be the definitive guide to systems engineering (SE) knowledge. To this end, each article has been intentionally limited to about 2000 words (not including references or tables).
| |
| − | * The materials in version 0.75 should ''not'' be considered final.
| |
| − | *With 0.75, the authors have attempted to improve the consistency in terms of scope and level of detail for each article. However, where reviewers note inconsistency, comments would be extremely helpful.
| |
| − | *Only some of the articles were updated for 0.75 (see "Articles Updated for SEBoK 0.75") below. All other articles in the wiki are essentially the same as version 0.5 (with minor updates to reflect changes elsewhere).
| |
| − | | |
| − | Version 0.75 offers the public SE community a view into the state of the SEBoK as its authors evolve it towards the September 2012 Version 1.0 release. Most importantly, the authors are soliciting comments from the community to improve the content for version 1.0. The ideal outcome is that the SEBoK will be supported worldwide by the SE community as the authoritative BoK for the SE discipline.
| |
| − | | |
| − | ==State of the SEBoK==
| |
| − | Summarizing the current state of the SEBoK at this point, the SEBoK team believes the following:
| |
| − | | |
| − | #The SEBoK is more mature than version 0.5. The quality of the writing, the choice of topics, the architecture of the SEBoK, and the completeness of the writing have been improved over version 0.5. The author team is quite proud of how far the SEBoK has come. Yet, the choice of version "0.75" does reflect the fact that much more work remains before the SEBoK will be fully ready for broad use and adoption.
| |
| − | #The architecture of the SEBoK into ''parts'', ''knowledge areas'', and ''topics'' is fundamentally correct and will persist in version 1.0, although there may be some minor adjustments.
| |
| − | #The choice of ''primary references'' - considered the most important readings in the field for a given topic - is immature. Reviewer feedback to help mature those choices is especially vital.
| |
| − | #Integration among articles is better than in version 0.5, but much remains to be done.
| |
| − | #Even though the articles in the wiki have been edited, there are still shortcomings in the writing. Nevertheless, version 0.75 captures extremely valuable information about the field, and provides a solid foundation for the final version.
| |
| − | #Moving to a wiki environment for the development and delivery of the SEBoK has been a huge step for the authors, but well worth it.
| |
| − | | |
| − | Reviewers will provide an external check on these beliefs.
| |
| − | | |
| − | ===Articles Updated for SEBoK 0.75===
| |
| − | The following is the list of articles that have been heavily revised in the transition from SEBoK 0.5 to SEBoK 0.75 or are new articles entirely. Many of these updates were done in response to the SEBok 0.5 reviews (please see the [http://www.sebokwiki.org/075/images/c/cf/Adjudication_report_for_0_75_Final.pdf Adjudication Report] for additional information). Reviewers are welcome to comment on all articles, not only the ones updated for SEBok 0.75.
| |
| | | | |
| | {| | | {| |
| | |- | | |- |
| − | | | + | |<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> |
| − | *[[SEBoK 0.5 Introduction|Part 1: SEBoK 0.5 Introduction]]
| |
| − | **[[Scope and Context of the SEBoK]]
| |
| − | **[[Structure of the SEBoK]]
| |
| − | **[[Economic Value of Systems Engineering]]
| |
| − | **[[Systems Engineering: Historic and Future Challenges]]
| |
| − | **[[Systems Engineering and Other Disciplines]]
| |
| − | ***[[Use Case 1: Practicing Systems Engineers]]
| |
| − | *[[Systems|Part 2: Systems]]
| |
| − | **Knowledge Area: [[Systems Thinking]]
| |
| − | ***Topic: [[What is a System?]]
| |
| − | ***Topic: [[Types of Systems]]
| |
| − | ***Topic: [[What is Systems Thinking?]]
| |
| − | **Knowledge Area: [[System Science]]
| |
| − | ***Topic: [[History of System Science]]
| |
| − | ***Topic: [[System Methodology]]
| |
| − | ***Topic: [[Groupings of Systems]]
| |
| − | **Knowledge Area: [[Systems Approach]]
| |
| − | ***Topic: [[Overview of the Systems Approach]]
| |
| − | ***Topic: [[Engineered System Context]]
| |
| − | ***Topic: [[Identifying and Understanding Problems and Opportunities]]
| |
| − | ***Topic: [[Synthesizing Possible Solutions]]
| |
| − | ***Topic: [[Analysis and Selection between Alternative Solutions]]
| |
| − | ***Topic: [[Implementing and Proving a Solution]]
| |
| − | ***Topic: [[Deploying, Using, and Sustaining Systems to Solve Problems]]
| |
| − | ***Topic: [[Acquirer/Supplier Responsibility]]
| |
| − | ***Topic: [[Applying the Systems Approach]]
| |
| − | *[[Systems Engineering and Management|Part 3: Systems Engineering and Management]]
| |
| − | ***Topic: [[System Life Cycle Process Models: Vee]]
| |
| − | ***Topic: [[System Life Cycle Process Models: Iterative]]
| |
| − | **Knowledge Area: [[Concept Definition]]
| |
| − | ***Topic: [[Mission Analysis]]
| |
| − | ***Topic: [[Stakeholder Needs and Requirements]]
| |
| − | **Knowledge Area: [[System Definition]]
| |
| − | ***Topic: [[Architectural Design: Logical]]
| |
| − | ***Topic: [[Architectural Design: Physical]]
| |
| − | **Knowledge Area: [[System Realization]]
| |
| − | ***Topic: [[System Verification]]
| |
| − | ***Topic: [[System Validation]]
| |
| − | **Knowledge Area: [[System Deployment and Use]]
| |
| − | ***Topic: [[Operation of the System]]
| |
| − | ***Topic: [[System Maintenance]]
| |
| − | ***Topic: [[Logistics]]
| |
| − | **Knowledge Area: Systems Engineering Management
| |
| − | ***Topic: [[Planning]]
| |
| − | |
| |
| − | *[[Applications of Systems Engineering|Part 4: Applications of Systems Engineering]]
| |
| − | **Knowledge Area: [[Product Systems Engineering]]
| |
| − | ***Topic: [[Product Systems Engineering Background]]
| |
| − | ***Topic: [[Product as a System Fundamentals]]
| |
| − | ***Topic: [[Business Activities Related to Product Systems Engineering]]
| |
| − | ***Topic: [[Product Systems Engineering Key Aspects]]
| |
| − | ***Topic: [[Product Systems Engineering Special Activities]]
| |
| − | *[[Enabling Systems Engineering|Part 5: Enabling Systems Engineering]]
| |
| − | ***Topic: [[Systems Engineering Governance]]
| |
| − | **Knowledge Area: [[Enabling Businesses and Enterprises to Perform Systems Engineering]]
| |
| − | ***Topic: [[Deciding on Desired Systems Engineering Capabilities within Businesses and Enterprises]]
| |
| − | ***Topic: [[Organizing Business and Enterprises to Perform Systems Engineering]]
| |
| − | ***Topic: [[Assessing Systems Engineering Performance of Business and Enterprises]]
| |
| − | ***Topic: [[Developing Systems Engineering Capabilities within Businesses and Enterprises]]
| |
| − | ***Topic: [[Culture]]
| |
| − | *[[Related Disciplines |Part 6: Related Disciplines]]
| |
| − | **Knowledge Area: [[Systems Engineering and Software Engineering]]
| |
| − | ***Topic: [[The Nature of Software]]
| |
| − | ***Topic: [[An Overview of the SWEBOK Guide]]
| |
| − | ***Topic: [[Ten Things a Systems Engineer Needs to Know about Software Engineering]]
| |
| − | ***Topic: [[Ten Things a Systems Engineer Needs to Know about Managing a Software Team]]
| |
| − | **Knowledge Area: [[Systems Engineering and Project Management]]
| |
| − | ***Topic: [[The Nature of Project Management]]
| |
| − | ***Topic: [[An Overview of the PMI Guide to the Project Management Body of Knowledge (PMBOK(TM))]]
| |
| − | ***Topic: [[Relationships between Systems Engineering and Project Management]]
| |
| − | ***Topic: [[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]]
| |
| − | **Knowledge Area: [[Systems Engineering and Industrial Engineering]]
| |
| − | ** Knowledge Area: [[Systems Engineering and Specialty Engineering]]
| |
| − | ***Topic: [[Security Engineering]]
| |
| − | ***Topic: [[System Assurance]]
| |
| − | ***Topic: [[Affordability]]
| |
| − | ***Topic: [[Environmental Engineering]]
| |
| − | ***Topic: [[Lean Engineering]]
| |
| | |} | | |} |
| | | | |
| − | ==About the SEBok 0.75 Review== | + | <div style="text-align:right">'''20 November 2023'''</div> |
| − | This is the third phase of SEBoK reviews. The first review of version 0.25 was completed with a [[Acknowledgements|limited audience]] of reviewers in Fall 2010. The report on the 0.25 comments can be found [http://www.bkcase.org/fileadmin/bkcase/files/Review_Documents/SEBOKVersion0.25AdjudicationReportFINAL1.pdf here].
| |
| − | | |
| − | The second review of version 0.5 was open worldwide in Fall 2011; an additional review was conducted by INCOSE working groups (WGs) in association with the INCOSE International Workshop. For comments received in the 0.5 wiki, the comments and any author actions to date can be viewed on each page under the heading "Comments from 0.5 Wiki." For comments received outside the wiki, please view the adjudication report [http://www.sebokwiki.org/075/images/c/cf/Adjudication_report_for_0_75_Final.pdf here].
| |
| − | | |
| − | The third review, of version 0.75, is open to the public; the deadline for reviewer comments is April 15, 2012.
| |
| − | | |
| − | In version 0.25, the guide was presented as a PDF document with sixteen chapters. Version 0.5 was presented in a wiki. Version 0.75 is also presented in a wiki with seven major parts, [http://www.www.sebokwiki.org/05/index.php/Category:Knowledge_Area 28 knowledge areas], and about [[SEBoK Table of Contents|160 total articles]] with hyperlinks between articles and to a set of [http://www.www.sebokwiki.org/05/index.php/Category:Primary_Reference primary references], a [http://www.www.sebokwiki.org/05/index.php/Category:Glossary_of_Terms glossary], and a list of [[Acronyms|acronyms]]. (Please see [[How to Read the SEBoK|Reading the SEBoK]] for a detailed explanation of the different article types.) The review of version 0.75 will use embedded discussion functionality for each article.
| |
| − | | |
| − | ===Review Process===
| |
| − | The SEBoK version 0.75 review process is intended to provide the SE community an opportunity to comment on the approach, provide feedback on current draft content, provide feedback on the wiki format, and make recommendations about future content and wiki features. The author team recommends that all reviewers read [[SEBoK 0.75 Introduction|Part 1: SEBoK 0.75 Introduction]] including the complete set of Part 1 articles, which provide the context for the rest of the materials. In addition, reviewers are encouraged to review the materials most relevant to their current roles or interests.
| |
| | | | |
| − | '''Please note that in order to provide review comments, you will use the DISQUS feature at the bottom of each article. You may login to DISQUS using existing accounts (e.g. Google, Yahoo, Twitter, or Facebook) or you may create a DISQUS account. Please look for the BKCASE posts under the discussion for each article, which provide specific prompts for reviewers to consider.''' | + | 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.” |
| | | | |
| − | ==Two types of input requested==
| + | 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. |
| − | There are two forms of reviewer feedback:
| |
| − | #Each of the articles has a set of discussion prompts in the embedded discussion at the bottom of the page. Reviewers are asked to consider these prompts as they conduct their reviews.
| |
| − | #The word document [http://www.sebokwiki.org/075/images/2/26/SEBoK075_ReviewForm_Final.docx SEBoK 0.75 Review Form] is provided to collect specific comments on the overall SEBoK and the wiki. Please provide responses by question number and return the document to [mailto:bkcase@stevens.edu bkcase@stevens.edu].
| |
| | | | |
| − | Please note that reviewers may download a PDF of SEBoK 0.75 [http://www.sebokwiki.org/075/images/2/28/SEBoK075_Final.pdf click here] or may download a specific Part for review by going to [[Download SEBoK PDF]]. Please note that this is a large file (~50 MB) and so may take several minutes to download.
| + | 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]]. |
| | | | |
| − | ==Thank you==
| + | 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. |
| − | The opinions and constructive criticism the BKCASE author team receives from you, the reviewer, plays an extremely valuable and important role in the worldwide success and acceptance of SEBoK. If you would like to obtain further project information, please visit the project’s website at [http://www.bkcase.org/ bkcase.org] and if you have any questions during your review, please contact us at [mailto:bkcase@stevens.edu bkcase@stevens.edu].
| |
| | | | |
| − | The BKCASE author team sincerely thanks you for volunteering your time to help us with this important effort. | + | 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. |
| | | | |
| − | ~The BKCASE Team
| + | 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. |
| | | | |
| − | [mailto:bkcase@stevens.edu bkcase@stevens.edu] | + | Sincerely, |
| − | {{DISQUS}}
| + | [[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