| Part of a series on |
| Software development |
|---|
|
Core activities |
|
Paradigms and models |
|
Methodologies and frameworks |
|
Supporting disciplines |
|
Practices |
|
|
|
Standards and bodies of knowledge |
|
Glossaries |
|
Outlines |
|
|
The Software Engineering Body of Knowledge (SWEBOK (/ˈswiːˌbɒk/ SWEE-bok)) refers to the collective knowledge, skills, techniques, methodologies, best practices, and experiences accumulated within the field of software engineering over time. A baseline for this body of knowledge is presented in the Guide to the Software Engineering Body of Knowledge,[1] also known as the SWEBOK Guide, an ISO/IEC standard originally recognized as ISO/IEC TR 19759:2005[2] and later revised by ISO/IEC TR 19759:2015.[3] The SWEBOK Guide serves as a compendium and guide to the body of knowledge that has been developing and evolving over the past decades.
The SWEBOK Guide has been created through cooperation among several professional bodies and members of industry and is published by the IEEE Computer Society (IEEE),[4] from which it can be accessed for free. In late 2013, SWEBOK V3 was approved for publication and released.[5] In 2016, the IEEE Computer Society kicked off the SWEBOK Evolution effort to develop future iterations of the body of knowledge.[6]
The published version of SWEBOK V3 has the following 15 knowledge areas (KAs) within the field of software engineering:
It also recognized, but did not define, these related disciplines:
The 2004 edition of the SWEBOK Guide, known as SWEBOK 2004, defined ten knowledge areas (KAs) within the field of software engineering:
The following disciplines are also defined as being related to software engineering:
A similar effort to define a body of knowledge for software engineering is the "Computing Curriculum Software Engineering (CCSE)," officially named Software Engineering 2004 (SE2004). The curriculum largely overlaps with SWEBOK 2004 since the latter has been used as one of its sources, although it is more directed towards academia. Whereas the SWEBOK Guide defines the software engineering knowledge that practitioners should have after four years of practice, SE2004 defines the knowledge that an undergraduate software engineering student should possess upon graduation (including knowledge of mathematics, general engineering principles, and other related areas). SWEBOK V3 aims to address these intersections.
