Volunteers are in the process of refreshing the Guide to the Software Engineering Body of Knowledge – SWEBOK – adding new knowledge areas (KAs) and revising others. For the latest materials available for public review, please check the SWEBOK V3 Public Review site.

Each of the 15 KAs will be posted online when they become available for review. Three knowledge areas are currently available for public review:

  • Software Engineering Models and Methods
  • Software Maintenance
  • Mathematical Foundations

Notification will be provided as other knowledge areas become available for review. Reviewers should read the review instructions and enter their review comments along with the requested information.

Three knowledge areas have completed public review:

  • Software Construction
  • Software Configuration Management
  • Computing Foundations

Developed concurrently, the SWEBOK Guide (2004 edition), the Software Engineering 2004 (SE2004) curriculum guide, and the Certified Software Development Professional (CSDP) certification each provided a characterization of the discipline of software engineering. Despite nearly independent development, the three instruments agreed to a remarkable extent. The primary purpose of the current revision of the SWEBOK Guide is to perfect the correspondence between the three items.

The purposes of the SWEBOK Guide are to:

  • characterize the contents of the software engineering discipline;
  • promote a consistent view of software engineering worldwide;
  • clarify the place of, and set the boundary of, software engineering with respect to other disciplines;
  • provide a foundation for training materials and curriculum development;
  • provide a basis for certification and licensing of software engineers.

Changes to the 2004 version of the SWEBOK Guide include updating of topic descriptions, inclusion of topics that have gained general acceptance since 2004, retirement of topics that are no longer relevant, addition of five new knowledge areas (KAs) that provide a guide to foundational knowledge in software engineering, better integration of the related disciplines, and renaming and distribution of some material into different knowledge areas.