Research & Innovation

Knowledge Resource Led by SERC at Stevens a Growing Influence in Global Systems Engineering Community

Nearly one million visitors since the launch of the Guide to the Systems Engineering Body of Knowledge (SEBoK)

With nearly one million visitors and close to two million page views since its launch, the Guide to the Systems Engineering Body of Knowledge (SEBoK) has become a prominent information resource for the systems engineering community. First released in 2012, the SEBoK is a result of seven years of hard work to capture and organize thousands of critical references on topics in systems engineering.

In 2009, the newly founded Systems Engineering Research Center (SERC), was presented with a challenge: create a body of knowledge that reflects the state of the systems engineering discipline and develop recommendations on a systems engineering graduate curriculum that utilizes that body of knowledge.  The challenge was met with the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) project.

“The BKCASE project is an important advancement in the field of systems engineering,” says Dr. Jon Wade, research professor; chief technology officer, SERC; director, Systems and Software Division at the Stevens School of Systems and Enterprises (SSE). Dr. Wade currently serves on the BKCASE Governing Board which oversees the policies of BKCASE products. “By providing the most current systems engineering knowledge available to decision-makers and researchers in industry and government, BKCASE is helping to improve the practice of systems engineering across the globe.” 

The SERC is a University-Affiliated Research Center (UARC) of the US Department of Defense led by Stevens Institute of Technology. SERC is one of three National Centers of Excellence at Stevens leading national research, development and education efforts to address crucial global needs.

Laying the groundwork

The BKCASE project needed to advance the discipline of systems engineering by creating a body of knowledge, something that was available for related disciplines such as software engineering (the SWEBOK) or project management (the PMBoK™). At the time, lack of a clear body of knowledge had been cited as a rationale for not recognizing systems engineering as a unique discipline in academia. By 2009 there had been multiple attempts to create a body of knowledge around systems engineering – none had succeeded. 

BKCASE was led by Dr. Art Pyster (of the Stevens Institute of Technology at the time) and Dr. David Olwell (of the Naval Postgraduate School at the time) from 2009-2013. They built a team of over seventy systems engineering experts from around the world to begin organizing the books, articles, presentations, and other existing systems engineering materials, utilizing an existing body of knowledge – the SWEBOK – as a template. 

The BKCASE team also developed a philosophy which continues to guide the work today:

  • Freely available to anyone in perpetuity. A major reason for doing the work was to help firmly establish systems engineering as a discipline and to enable people who are interested in systems engineering, or who work with systems engineers, to also have access to the information. Putting the SEBoK behind a pay wall simply would not support this goal.

  • A guide – not a compendium. While the SEBoK includes a rich discussion of topics in systems engineering, it does not incorporate the text of every single resource available. Instead, the BKCASE team writes summaries on topics – the state of the art, the state of practice, the different techniques or views of the community – but does not try to replicate all the available information. 

  • SEBoK to include as many references as possible. The BKCASE team aids users in navigating the references by identifying “Primary” references – the most critical, community-recognized resources on a topic – as well as “additional” references, which give depth on a subset of a topic or provide different perspectives. 

In 2009, the BKCASE team released SEBoK v. 0.25, which was a traditional document-based body of knowledge. Everyone in the systems engineering community with an interest had an opportunity to review this early version and provide feedback, comments and recommendations. Over 3,000 comments were received and these were all adjudicated and used to improve the SEBoK to create version 0.5.

From document to wiki – the first public release

In 2011, in addition to maturing the content and responding to the tremendous volume of review responses, the BKCASE team also made a choice that at the time was unique among bodies of knowledge: the SEBoK would not be a document as was tradition, but would instead be delivered as a wiki. Unlike Wikipedia, this was intended to be managed as a standard set of content, so it could not be freely edited by all. 

The team developed approaches and controls to ensure that anyone in the world with an internet connection could access the SEBoK and make comments or suggestions, but that only the carefully selected experts in the field could update the SEBoK. SEBoK v 0.5 was released in 2011 and hundreds of additional comments were received. 

SEBoK Structure Chart

With a working architecture and wiki-based approach, 2012 saw the final push towards SEBoK 1.0 – the first “official” version of the SEBoK for full public release. The teams finalized the architecture, matured the content, and worked with experts in related fields such as systems science to create SEBoK 1.0. The final architecture (See Figure 1) had evolved significantly from where the BKCASE team had started in 2009. 

Real world systems perspectives

In addition to the processes of systems engineering, the SEBoK was intended to include information on the foundations of systems science and systems thinking, information about the different ways systems engineering could be applied, insight into how systems engineering could be utilized by individuals, teams, and organizations, and information on disciplines that share critical overlaps with systems engineering. The BKCASE team developed many case studies and vignettes – examples that help to illustrate and provide real-world perspective on many of the SEBoK topics.

But despite all the hard work over several years, the team knew that the launch of SEBoK 1.0 was just the beginning. With the goal of keeping SEBoK content fresh, they adopted a rapid update cycle (semi-annual iterations) that reflected the growth and evolution of systems engineering field. The selection of a wiki for publication was part of this strategy – interconnections built into the wiki infrastructure helped to ensure that information updated in one area would be appropriately reflected in other areas as well. 

A growing influence 

As the SEBoK has evolved, it has also helped other disciplines to evolve. For example, after participating in the development of the SEBoK, the International Society of the Systems Sciences (ISSS) is working on developing a systems science body of knowledge. Likewise, the IEEE Computer Society has begun investigating publishing the Software Engineering Body of Knowledge (SWEBOK) as a wiki.

SEBoK Usage Trend Chart

Though the initial BKCASE work was funded by the US Department of Defense to support critical research in systems engineering, this was not intended to be a long-term support model. In 2012, Stevens Institute of Technology, the International Council on Systems Engineering (INCOSE), and the IEEE Computer Society formed the BKCASE Governing Board. Together, these three stewards ensure the maintenance and evolution of the SEBoK.

“This was a true community effort, led by the SERC at Stevens,” says Dr. Dinesh Verma, professor; executive director, Systems Engineering Research Center. “We are honored to have been involved with this project from the very beginning.”

With the increase in SEBoK users (See Figure 2) to provide new ideas and content, SEBoK will continue to evolve as it remains a valuable resource for growing and evolving systems engineering as a key professional discipline for the resolution of real-world and complex global problems.