Software Engineering Body of Knowledge
The Software Engineering Body of Knowledge (SWEBOK) is an international standard ISO/IEC TR 19759:2005[1] specifying a guide to the generally accepted Software Engineering Body of Knowledge.
It has been created by a co-operation of several bodies and the industry. Most importantly, the two leading computing authorities the Association for Computer Machinery (ACM) and the IEEE Computer Society (IEEE). The standard can be accessed freely from the IEEE Computer Society.[2] In mid-2013, a new updated version SWEBOK V3 will be released.[3] SWEBOK V3 is currently under a public review.
Contents |
Contents of the SWEBOK [edit]
As of the 2004 edition, the SWEBOK guide defines 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
- Quality management
- Software ergonomics (Cognitive ergonomics)
- Systems engineering
Controversy [edit]
Regarding the initial version in 2001, Cem Kaner and Grady Booch have publicly stated that the document could be improved.[4] Many claimed that the document may not accurately reflect the community's view of software engineering and recognize the effort to try to define the profession. Notkin, Gorlick, and Shaw's reported on the first version also less than positively.[5]
Due to concerns about the work being used to require a mandatory software engineering licensure, the ACM famously pulled out of the SWEBOK process in 2000, but when these concerns passed the ACM rejoined.[6]
German scientists[who?] support that the 2004 SWEBOK V2 regards sources which were published in English and is an accurate anglophone guide.[citation needed] Translations to other languages are available in French, Japanese, and Arabic.
Other similar efforts 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 the academia. Whereas the SWEBOK 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).
See also [edit]
- PMBOK — Project Management Body of Knowledge
- EABOK — Enterprise Architecture Body of Knowledge
- BABOK — Business Analysis Body of Knowledge
- ABOK — Automation Body of Knowledge
- TMBOK — Test Management Body of Knowledge
References [edit]
- ^ "ISO/IEC TR 19759:2005". Retrieved 2013-04-01.
- ^ "SWEBOK - Overview". Computer.org. Retrieved 2011-09-28.
- ^ "Software Engineering Body of Knowledge (SWEBOK) Home". Retrieved 2013-04-01.
- ^ "Cem Kaner’s Blog » Blog Archive » SWEBOK Problems, Part 2". Satisfice.com. 2003-06-27. Retrieved 2009-12-03.
- ^ "Bok assessment". 2000-05. Retrieved 2011-09-28.
- ^ "http://www.acm.org/serving/se_policy/selep_main.html" (PDF). 2000. Archived from the original on April 17, 2007. Retrieved 2009-12-03.
External links [edit]
- Official website
- An Assessment of Software Engineering Body of Knowledge Efforts — an ACM report critical of the SWEBOK
|
|||||||||||||||||||||||||||||||
