Difference between revisions of "Editor's Corner"

From SEBoK
Jump to navigation Jump to search
Line 1: Line 1:
 
A very warm welcome to all SEBoK users. The BKCASE Editor in Chief (EIC) has overall responsibility for the continuing review and update of the SEBoK.  Many thanks to the BKCASE Governors and the current members of the Editorial Board for supporting me.
 
A very warm welcome to all SEBoK users. The BKCASE Editor in Chief (EIC) has overall responsibility for the continuing review and update of the SEBoK.  Many thanks to the BKCASE Governors and the current members of the Editorial Board for supporting me.
  
I am delighted to be able to talk to you about SEBoK v. 1.9, which continues our commitment to regular review of the information referenced in our "Guide to the Systems Engineering Body of Knowledge".
+
It is an honor to become the third EIC for the SEBoK. Since being named to this position, I have held listening sessions at the INCOSE IS in Washington, D.C., met with the Board of Governors and the SEBoK Editors for the various parts of the SEBoK. Let me share some of those ideas and insights with you. Below are the more significant inputs:
  
The approach taken by the BKCASE Editorial Board to manage and evolve the SEBoK is itself continuing to evolve.  SEBoK v1.4 was a significant milestone in this evolution, creating an alignment of SEBoK content with significant updates of [[ISO/IEC/IEEE 15288|ISO/IEC/IEEE. 15288:2015 Systems and Software Engineering - System Life Cycle Processes]] and the [[INCOSE Systems Engineering Handbook|INCOSE SE Handbook v4.0, 2015]]. This marked something of a culmination of work started within the community working across all three of these products reaching back to the beginnings of the BKCASE project in 2009. Since then effort has been split between continuing to build on and mature content within the existing SEBoK and exploring other areas of related knowledge.
+
1. A large number of systems engineers know of the SEBoK, and have used it from time to time.
 +
2. The PDF version of the SEBoK is very popular - it is portable and searchable - and we should continue to produce this product with each new release of the SEBoK
 +
3. The organization of the SEBoK still needs some tweaking
 +
4. There are recommendations for potential new sections to be added: SE Research, SE 2025 Vision, and Systems Engineering for Non-systems engineers
 +
5. Additional topics that should be added: Systems Thinking, TRIZ, Digital Thread/Digital Twin are some of the recommendations
 +
6. Provide more related engineering topics: Civil engineering, Coastal engineering, Mechanical engineering, Data engineering, etc.
 +
7. Need a better tool for submitting new knowledge to the SEBoK editors
 +
8. Time to incorporate multimedia into the SEBoK
 +
9. Add more examples of successful systems implementations, tool information, and modeling techniques
  
Subsequent SEBoK updates have continued tp evolve the content in response to new knowledge and community feedback. We have also made a number of structural changes to facilitate the ongoing evolution of the SEBoK. In particular a new section was included in Part 1 to reflect the ongoing [[Introduction to SE Transformation|transformation of the discipline of SE]] and associated emerging areas of knowledge.  The first two of these being in [[Model-Based Systems Engineering (MBSE) (glossary)|Model Based Systems Engineering (MBSE)]] and the expansion of SEBoK to cover domain specific SE knowledge.
+
From those listening opportunities, a vision for SEBoK 2.0 has emerged.
  
Version 1.9 contains more ongoing evolution of the SEBoK, working closely with the SE community.
+
SEBoK 2.0 will be multimedia enabled. We will begin to incorporate video and audio links. Because we need to be sensitive to copyrights, original content from our user base will be solicited. If you are an expert in areas that are already a part of the SEBoK, and would like to create short, 3-5 minute vignettes, please contact one of the editors or myself. We will also be leveraging the INCOSE YouTube channel for some of this content. Since many are accessing the SEBoK via their phones and tablets, we will work to improve the accessibility on mobile devices. Finally, we will continue to fine-tune the organization of the SEBoK, adding more content "as appropriate".
=== SEBoK v. 1.9 ===
 
  
SEBoK v1.9 contains detailed changes to article content organisation in [[Related Disciplines|Part 6 Related Disciplines]] and [[Systems Engineering Implementation Examples|Part 7:Systems Engineering Implementation Examples]].  
+
Why put "as appropriate" in quotes? As you may know, the SEBoK is a curated Wiki. That means that the information contained in the SEBoK should be established knowledge. While research is becoming more and more important to systems engineering, it is also important to differentiate what is new knowledge, and what is considered 'settled' knowledge, or general knowledge. To handle this, the editors are considering adding a new section to the SEBoK where research type topics can be cataloged, but with the understanding that it is still research.
  
Part 6 the SEBoK considers the relationships between SE and other disciplines. One challenge of part 6 is to align the knowledge discussed with the body of knowledge of the related disciplines, while still making it appropriate for systems engineers. To help do this the part 6 editors have created a standard article template which provides a structure within which to discuss discipline specific standards, practices and tools. In SEBoK v1.9 we have continued to populate these sections in collaboration with representatives from the related areas with an update of the [[System Resilience]] (formerly "Resilience Engineering") article.  
+
The SEBoK Editorial Board is always seeking more collaborators and new and/or updated content. It is important to note that the editors primary role is not to create the content (though many of them are also content creators). It is to edit and curate the content. Content creation should be coming from the consumers of the SEBoK.
  
Part 7 has been restructured, removing the old framework for examples ("vignettes" and "case studies", which reflected how the examples were developed). The example have been organized based on the organizational context: examples from commercial organizations, government organization, or examples in which development was a partnership between the two. These changes provide a better baseline to continue to evolve the content and role of these examples across the SEBoK.
+
SEBoK Version 1.9.1 Changes
 
+
===========================
In addition, a new example has been added around the [[Applying a Model-Based Approach to Support Requirements Analysis on the Thirty-Meter Telescope|use of model based systems engineering for the thirty-meter telescope]].
+
This minor update, Version 1.9.1 contains minor updates - fixed links, updated Editorial Board members and their contact information, and this letter.
 
 
See [[Acknowledgements and Release History]] for a more detailed list of all changes made for v1.9.
 
 
 
===Future Direction for SEBoK===
 
 
 
It has been my continuing privilege over the last 12 months to continue working with the group of dedicated and knowledgeable [[Acknowledgements and Release History|contributing authors and reviewers]] who make up the BKCASE community; and to help grow this community to expand our relationships with key organizations and groups both within systems engineering and outside of it.
 
 
 
The role of the Editorial Board is to work with this community of interest on an ongoing review of the current SEBoK content and structure and to develop plans for its maintenance and evolution. Our overall goals in evolving the SEBoK remain broadly the same as those outlined in previous SEBoK updates.  I have restated and slightly modified those goals below:
 
 
 
*Improve the ways in which [[SEBoK Introduction|Part 1 (SEBoK Introduction)]] provides a starting point for different SEBoK users to find and navigate knowledge relevant to them.  This will include consideration of some of the [[SEBoK Users and Uses|SEBoK Use Cases]] which were not expanded in previous releases, and possible new case studies covering application domains such as Defense, Health Care or Transport.  
 
*Review Part 2 ([[Foundations of Systems Engineering]]) with help from the International Society for the Systems Sciences (ISSS) to better understand the relationships between [[Systems Science (glossary)]] and [[Systems Thinking (glossary)]] as applied to [[Engineered System (glossary)|engineered systems]]. We hope this will lead to an improved integration of systems principles, concepts, patterns and models into the other systems engineering focused knowledge areas across the SEBoK.
 
*Look for broader views on the key practices of [[Systems Engineering and Management|Part 3 (Systems Engineering and Management)]] to feed back into the ongoing co evolution of key standards.  In particular make more direct reference to the continuing evolution of [[Agile (glossary)|Agile]] life cycle thinking and bring in more knowledge sources from the [[Model-Based Systems Engineering (MBSE) (glossary)|model based SE (MBSE)]] community.
 
*Expand our coverage of knowledge on systems engineering application and practices.  In particular look for ways to bring in more knowledge on how systems engineering practices such as architecting, life cycle tailoring and model based systems engineering are applied in other domains.
 
*Identify the other groups, both within the systems engineering community and beyond, with interest in the topics of [[Enabling Systems Engineering|Part 5 (Enabling Systems Engineering)]] and [[Related Disciplines|Part 6 Related Disciplines]] and form stronger relationships with them.  For example we are working with the IEEE Computer Society about the relationship between SE and Software Engineering.
 
 
 
We continue to work towards ensuring that our coverage of existing systems engineering knowledge is complete and to push the boundaries of that knowledge into new approaches and domains. I also want to strengthen further our links to all members of the systems engineering community through things like the [[Sandbox|SEBoK Sandbox]]. If you are interested in any of the activity discussed above or if you have other topics which we should be considering please contact me or the appropriate member of the [[BKCASE Governance and Editorial Board|Editorial Board]] directly or use one of the available feedback mechanisms.
 
 
 
We have continued to gather review comments and content suggestions from as wide a variety of individuals as possible to make the SEBoK a truly community-led product.  Thank you to all those who have already joined this effort and I continue to look forward to working with many of you on future SEBoK releases.
 
 
 
Thank you,
 
 
 
 
 
[[File:RickSignature_Full.png|left|200px]]
 

Revision as of 16:15, 6 September 2018

A very warm welcome to all SEBoK users. The BKCASE Editor in Chief (EIC) has overall responsibility for the continuing review and update of the SEBoK. Many thanks to the BKCASE Governors and the current members of the Editorial Board for supporting me.

It is an honor to become the third EIC for the SEBoK. Since being named to this position, I have held listening sessions at the INCOSE IS in Washington, D.C., met with the Board of Governors and the SEBoK Editors for the various parts of the SEBoK. Let me share some of those ideas and insights with you. Below are the more significant inputs:

1. A large number of systems engineers know of the SEBoK, and have used it from time to time. 2. The PDF version of the SEBoK is very popular - it is portable and searchable - and we should continue to produce this product with each new release of the SEBoK 3. The organization of the SEBoK still needs some tweaking 4. There are recommendations for potential new sections to be added: SE Research, SE 2025 Vision, and Systems Engineering for Non-systems engineers 5. Additional topics that should be added: Systems Thinking, TRIZ, Digital Thread/Digital Twin are some of the recommendations 6. Provide more related engineering topics: Civil engineering, Coastal engineering, Mechanical engineering, Data engineering, etc. 7. Need a better tool for submitting new knowledge to the SEBoK editors 8. Time to incorporate multimedia into the SEBoK 9. Add more examples of successful systems implementations, tool information, and modeling techniques

From those listening opportunities, a vision for SEBoK 2.0 has emerged.

SEBoK 2.0 will be multimedia enabled. We will begin to incorporate video and audio links. Because we need to be sensitive to copyrights, original content from our user base will be solicited. If you are an expert in areas that are already a part of the SEBoK, and would like to create short, 3-5 minute vignettes, please contact one of the editors or myself. We will also be leveraging the INCOSE YouTube channel for some of this content. Since many are accessing the SEBoK via their phones and tablets, we will work to improve the accessibility on mobile devices. Finally, we will continue to fine-tune the organization of the SEBoK, adding more content "as appropriate".

Why put "as appropriate" in quotes? As you may know, the SEBoK is a curated Wiki. That means that the information contained in the SEBoK should be established knowledge. While research is becoming more and more important to systems engineering, it is also important to differentiate what is new knowledge, and what is considered 'settled' knowledge, or general knowledge. To handle this, the editors are considering adding a new section to the SEBoK where research type topics can be cataloged, but with the understanding that it is still research.

The SEBoK Editorial Board is always seeking more collaborators and new and/or updated content. It is important to note that the editors primary role is not to create the content (though many of them are also content creators). It is to edit and curate the content. Content creation should be coming from the consumers of the SEBoK.

SEBoK Version 1.9.1 Changes

===============

This minor update, Version 1.9.1 contains minor updates - fixed links, updated Editorial Board members and their contact information, and this letter.