Software Engineering Body of Knowledge
From Wikipedia, the free encyclopedia
The Software Engineering Body of Knowledge (SWEBOK) is a product of the Software Engineering Coordinating Committee sponsored by the IEEE Computer Society.
The software engineering body of knowledge is an all-inclusive term that describes the sum of knowledge within the profession of software engineering. Since it is usually not possible to put the full body of knowledge of even an emerging discipline, such as software engineering, into a single document, there is a need for a Guide to the Software Engineering Body of Knowledge. This Guide will seek to identify and describe that subset of the body of knowledge that is generally accepted, even though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines.[1]
Contents |
[edit] Contents of the SWEBOK
As of the 2004 edition, the SWEBOK guide define 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
- 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
[edit] Criticism and alternatives
Cem Kaner and Grady Booch have publicly stated that the document could be improved.[2][citation needed] Many claim 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 report was also less than positive.[3]
The ACM famously pulled out of the SWEBOK process due to concerns about the work being used to require licensure.[4]
German scientists support that the SWEBOK regards sources which were published in English and is an accurate anglophone guide.[citation needed] Other versions, which include other authors, are available in French, Japanese, and Arabic.
Other efforts to define a body of knowledge for software engineering is the "Computing Curriculum Software Engineering (CCSE)", officially named Software Engineering 2004 (SE2004). The difference is that whereas 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).
[edit] External links
- swebok.org - official site. (Documents available from left sidebar)
- An Assessment of Software Engineering Body of Knowledge Efforts - an ACM report critical of the SWEBOK
- Cem Kaner's blog - criticism by a reviewer[dead link]
[edit] See also
- PMBOK - Project Management Body of Knowledge
- EABOK - Enterprise Architecture Body of Knowledge
- BABOK - Business Analysis Body of Knowledge
- CMBOK - Configuration Management Body of Knowledge
[edit] References
- ^ [1][dead link]
- ^ "Cem Kaner’s Blog » Blog Archive » SWEBOK Problems, Part 2". Satisfice.com. 2003-06-27. http://www.satisfice.com/kaner/?p=7. Retrieved 2009-12-03.
- ^ http://www.cs.washington.edu/homes/notkin/bok_assessment.pdf
- ^ "http://www.acm.org/serving/se_policy/selep_main.html" (PDF). http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep_main.pdf. Retrieved 2009-12-03.
