Experiences From Creating the Guide to the Systems Engineering Body of Knowledge (SEBoK) v. 1.0

Abstract

Version 1.0 of the Guide to the Systems Engineering Body of Knowledge (SEBoK) was released in September 2012. Seventy authors from around the world working for three years created the SEBoK. This paper discusses twelve factors that were critical to the successful development and on-time release of the SEBoK. The approach taken is elaborated, and lessons learned along the way are highlighted. These experiences and recommendations based on them would be useful to any collaborative research effort that shares one or more of the characteristics of SEBoK development.

Systems Engineering and Project Management — Crossing the Great Divide

“…According to the SEBoK, most failures that surface in projects are linked to schedule, cost, and performance [5]. Most projects' problems are also due to upstream issues at the beginning of the project or systems creation [8].…”

“…Henry et al [5] note that PM and SE are inextricably linked. Still, they are viewed as separate disciplines by the literature, learning institutions, and organisations with independent PM and SE functional structures.…”

“…The different cultures, competencies, and accountabilities affect their interrelationship. As a result, significant overlaps and conflict areas between SE and PM exist [5], [6].…”