Software engineering body of knowledge

from Wikipedia, the free encyclopedia

The Guide to the Software Engineering Body of Knowledge ( SWEBOK ) is a document from the IEEE Computer Society . It structures the collected knowledge ( English body of knowledge ) in the field of software technology and makes it available to the general public.

History and goals

The SWEBOK project was launched by the IEEE and ACM companies in 1993–1998; ACM withdrew again during the course of the project. The aim of the project within the field of software technology is to present, structure and standardize the state of the art and to differentiate it from other disciplines. The document should also be the basis for the qualification and certification of computer scientists.

The project was carried out in three phases from 1998 to 2004, in which the structure and content of the SWEBOK was defined, refined and validated. The interim results were subjected to a review process by experts worldwide . For version 0.7 of the second phase, 378 reviewers were involved, whose qualifications were proven by the publication of their bibliographic data.

Version V3.0 is currently (2014) available.

Areas of knowledge

The structure of the SWEBOK is based on the division of software technology into 10 knowledge areas ( Knowledge Areas , KA ). These are:

  1. Software requirements : Requirements analysis
  2. Software design : software design
  3. Software construction : programming
  4. Software testing : software testing
  5. Software maintenance : software maintenance
  6. Software configuration management : configuration management
  7. Software engineering management : project management
  8. Software engineering process : process model
  9. Software engineering tools and methods : Development tools and methods
  10. Software quality : software quality

The 11th field of knowledge is the scientific status of related disciplines:

rating

The attempt to create a cross-sectional and reference work of software technology cannot succeed without numerous criticisms. During the review phases, among other things, the lack of depth and the use as a basis for qualification and certification were criticized.

Despite criticism, the project is academically sound and has established itself as a quasi-standard.

Individual evidence

  1. https://www.computer.org/education/bodies-of-knowledge/software-engineering
  2. ACM: An Assessment of Software Engineering Body of Knowledge Efforts (PDF; 52 kB), 2000
  3. Cem Kaner: IEEE's "Body of Knowledge" ( Memento of May 8, 2009 in the Internet Archive ), 2003
  4. Software-Kompetenz.de SWEBOK as a taxonomy standard , 2005

Web links