Software Engineering Body of Knowledge

Software development

Core activities

* Processes
* Requirements
* Design
* Engineering
* Construction
* Testing
* Debugging
* Deployment
* Maintenance

Paradigms and models

* Agile
* Cleanroom
* Incremental
* Prototyping
* Spiral
* V model
* Waterfall

Methodologies and frameworks

* ASD
* DevOps
* DAD
* DSDM
* FDD
* IID
* Kanban
* Lean SD
* LeSS
* MDD
* MSF
* PSP
* RAD
* RUP
* SAFe
* Scrum
* SEMAT
* TSP
* UP
* XP

Supporting disciplines

* Configuration management
* Documentation
* Software quality assurance (SQA)
* Project management
* User experience

Practices

* ATDD
* BDD
* CCO
* CI
* CD
* DDD
* PP
* SBE
* Stand-up
* TDD

Tools

* Compiler
* Debugger
* Profiler
* GUI designer
* Modeling
* IDE
* Build automation
* Release automation
* Infrastructure as code
* Testing

Standards and Bodies of Knowledge

* BABOK
* CMMI
* IEEE standards
* ISO 9001
* ISO/IEC standards
* PMBOK
* SWEBOK
* ITIL

Glossaries

* Artificial intelligence
* Computer science
* Electrical and electronics engineering

* v
* t
* e

The Software Engineering Body of Knowledge (SWEBOK (/ˈswiːˌbɒk/ SWEE-bok[1])) is an international standard ISO/IEC TR 19759:2005[2] specifying a guide to the generally accepted software engineering body of knowledge.

The Guide to the Software Engineering Body of Knowledge (SWEBOK Guide) has been created through cooperation among several professional bodies and members of industry and is published by the IEEE Computer Society (IEEE).[3] The standard can be accessed freely from the IEEE Computer Society.[4] 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]

## Contents

* 1 SWEBOK Version 3
* 2 2004 edition of the SWEBOK
* 3 Similar efforts
* 4 See also
* 5 References
* 6 External links

## SWEBOK Version 3

The published version of SWEBOK V3 has the following 15 knowledge areas (KAs) within the field of software engineering:

* 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
* Software engineering economics
* Computing foundations
* Mathematical foundations
* Engineering foundations

It also recognized, but did not define, these related disciplines:

* Computer engineering
* Systems engineering
* Project management
* Quality management
* General management
* Computer science
* Mathematics

## 2004 edition of the SWEBOK

The 2004 edition of the SWEBOK guide defined ten knowledge areas (KAs) within the field of software engineering:

* Software requirements
* Software design
* Software construction
* Software testing
* Software maintenance
* Software configuration management
* Software engineering management (engineering management)
* Software engineering process
* Software engineering tools and methods
* Software quality

The SWEBOK also defines disciplines related to software engineering:

* Computer engineering
* Computer science
* Management
* Mathematics
* Project management
* Quality management
* Software ergonomics (cognitive ergonomics)
* Systems engineering

## Similar efforts

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 the 2004 SWEBOK V2 because the SWEBOK has been used as one of its sources; however, 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.

## See also

* Project Management Body of Knowledge (PMBOK)
* Enterprise Architecture Body of Knowledge (EABOK)
* Systems Engineering Body of Knowledge (SEBOK)
* Automation Body of Knowledge (ABOK)
* Data Management Body of Knowledge (DMBOK)
* ISO/IEC JTC 1/SC 7

## References

1. ↑ "IEEE Computer Society SWEBOK Certificate Program (SCP) benefits for students". https://www.youtube.com/watch?v=4bvT9KtFQCk. Retrieved 22 January 2021.
2. ↑ "ISO/IEC TR 19759:2005". http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=33897.
3. ↑ "Guide to the software engineering body of knowledge : 2004 version," Library of Congress Online Catalog, 2005, http://lccn.loc.gov/2005921729. Retrieved 16 July 2013.
4. ↑ "SWEBOK". Computer.org. https://www.computer.org/education/bodies-of-knowledge/software-engineering.
5. ↑ "SWEBOK Guide V3.0". https://www.computer.org/education/bodies-of-knowledge/software-engineering/v3.
6. ↑ "SWEBoK Evolution". https://www.computer.org/volunteering/boards-and-committees/professional-educational-activities/software-engineering-committee/swebok-evolution.

## External links

* v
* t
* e

Software engineering

Fields|

* Computer programming
* Requirements engineering
* Software deployment
* Software design
* Software maintenance
* Software testing
* Systems analysis
* Formal methods

Concepts|

* Data modeling
* Enterprise architecture
* Functional specification
* Modeling language
* Orthogonality
* Programming paradigm
* Software
* Software archaeology
* Software architecture
* Software configuration management
* Software development methodology
* Software development process
* Software quality
* Software quality assurance
* Software verification and validation
* Structured analysis

Orientations|

* Agile
* Aspect-oriented
* Object orientation
* Ontology
* Service orientation
* SDLC

Models|

| Developmental|

* Agile
* EUP
* Executable UML
* Incremental model
* Iterative model
* Prototype model
* RAD
* UP
* Scrum
* Spiral model
* V-Model
* Waterfall model
* XP

|

Other|

* SPICE
* CMMI
* Data model
* ER model
* Function model
* Information model
* Metamodeling
* Object model
* Systems model
* View model

Languages|

* IDEF
* UML
* USL
* SysML

Software
engineers

* Victor Basili
* Kent Beck
* Grady Booch
* Fred Brooks
* Barry Boehm
* Peter Chen
* Danese Cooper
* Ward Cunningham
* Tom DeMarco
* Edsger W. Dijkstra
* Delores M. Etter
* Martin Fowler
* Adele Goldstine
* Margaret Hamilton
* C. A. R. Hoare
* Lois Haibt
* Mary Jean Harrold
* Grace Hopper
* Watts Humphrey
* Michael A. Jackson
* Ivar Jacobson
* Alan Kay
* Nancy Leveson
* Stephen J. Mellor
* Bertrand Meyer
* David Parnas
* Trygve Reenskaug
* Winston W. Royce
* James Rumbaugh
* Mary Shaw
* Peri Tarr
* Elaine Weyuker
* Niklaus Wirth
* Edward Yourdon

Related fields|

* Computer science
* Computer engineering
* Project management
* Risk management
* Systems engineering

* Category
* Commons

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Software Engineering Body of Knowledge. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Software_Engineering_Body_of_Knowledge&oldid=3150974"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template