An Overview of the SWEBOK Guide

The Preface to the 2004 version of the Guide to the Software Engineering Body of Knowledge states external link: http://www.swebok.org]:

The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a consensually validated characterization of the bounds of the software engineering discipline and to provide a topical access to the Body of Knowledge supporting that discipline.

SWEBOK Guide Version 3

Version 3 of the SWEBOK Guide is being developed and will be completed in late 2011 or early 2012. Version 3 of the SWEBOK Guide contains 15 knowledge areas:

Software Requirements
Software Design
Software Construction
Software Testing
Software Engineering Methods
Software Maintenance
Software Configuration Management
Software Quality
Software Engineering Process
Software Engineering Management
Software Professional Practice
Software Economics
Computing Foundations
Mathematical Foundations
Engineering Foundations

The description of each knowledge area includes an introduction, a descriptive breakdown of topics and sub-topics, recommended references, references for further reading, and a list of standards most relevant to the knowledge area.

SWEBOK and SEBoK Knowledge Areas

The following table indicates the correspondences between SWEBOK knowledge areas and SEBoK knowledge areas. The similarities and differences are described below [{Systems Engineering and Software Engineering: Similarities and Differences}].

Table 1. Correspondences between SWEBOK and SEBoK Knowledge Areas

NOTE: Table 1 To be completed

Related Disciplines

The SWEBOK Guide also contains a chapter on related disciplines, which include:

Computer Engineering
Business Management
Project Management
Quality Management
Systems Engineering

The related disciplines are those that share a boundary, and often a common intersection, with software engineering. The SWEBOK Guide does not characterize the knowledge of the related disciplines but rather indicates how those disciplines interact with the software engineering discipline.

References

Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Citations

List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.

Primary References

All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.