Software Engineering Body of Knowledge

The Software Engineering Body of Knowledge (SWEBOK) is a standard defining the generally recognized knowledge areas of the software engineering discipline, published by the IEEE Computer Society. It aims to characterize the contents of the discipline and promote a consistent view of software engineering worldwide, and underlies bodies like the IEEE's software-engineering-related certifications and curricula guidance.

Knowledge areas

SWEBOK organizes the discipline into knowledge areas spanning software requirements, software design, software construction, software testing, software maintenance, software configuration management, software engineering management, software engineering process, software engineering models and methods, software quality, software engineering professional practice, and software engineering economics — plus related disciplines it draws boundaries against (computer science, project management, and others).

How it relates to this collection's other software-engineering skills

• Software Engineering — the general discipline; SWEBOK is one specific, formally published standard attempting to codify that discipline's recognized knowledge areas.
• Software Engineering Guide — a specific, more opinionated and prescriptive published guide with concrete chapter-by- chapter best-practice guidance; SWEBOK, by contrast, aims at defining and organizing what the discipline consists of rather than prescribing specific practices in detail.
• Project Management Body of Knowledge (PMBOK) — the parallel standard for project management specifically, published by a different body (PMI rather than IEEE); the two overlap at software engineering management but have distinct scope and origin.

Common pitfalls

• Treating SWEBOK as a how-to guide — it defines and organizes the discipline's knowledge areas rather than prescribing specific step-by- step practices the way a methodology or style guide would.
• Confusing SWEBOK with a certification — SWEBOK is the body of knowledge itself; specific certifications and curricula may reference it without being identical to it.
• Assuming a fixed, unchanging version — SWEBOK has been revised across multiple versions as the discipline evolves; confirm which version a specific claim or curriculum reference is drawn from.
• Treating it as interchangeable with PMBOK — the two are structured similarly (a body of knowledge organized into knowledge areas) but cover different disciplines, published by different organizations.

Learn more

• IEEE Computer Society SWEBOK Guide — the official standard.
• Software Engineering for the general discipline this standard codifies.
• Software Engineering Guide for a more prescriptive, chapter-by-chapter published guide.
• Project Management Body of Knowledge for the parallel standard in project management.