The Software Engineering Body of Knowledge (SWEBOK) is an international standard ISO/IEC From Wikipedia, the free encyclopedia. Jump to navigation. Looking for online definition of SWEBOK or what SWEBOK stands for? about us, add a link to this page, or visit the webmaster’s page for free fun content. Please register as a user of the Guide at , after January You will have the rules that at least partially constrain the free use of natural.

Author: Vigor Kazigul
Country: Liechtenstein
Language: English (Spanish)
Genre: Relationship
Published (Last): 25 March 2011
Pages: 266
PDF File Size: 8.62 Mb
ePub File Size: 14.51 Mb
ISBN: 478-3-57903-648-5
Downloads: 95380
Price: Free* [*Free Regsitration Required]
Uploader: Shaktill

Swebom 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 identifies and describes that subset of the body of knowledge that is generally acceptedeven though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines.


SWEBOK V3.0 Guide to the Software Engineering Body of Knowledge

Software engineers worldwide can participate in the Guide’s development. Anyone can sign up to be a reviewer. As software becomes the center of critical systems, it is only natural that standards of practice, knowledge, and training would arise in software engineering, as the usage section explains. Its Guide to the Project Management Body of Knowledge defines “generally accepted” knowledge for project management in the following rree. The Industrial Advisory Board for the SWEBOK Guide better defines “generally accepted” as knowledge to be included in the study material of a software engineering licensing exam that a graduate would pass after completing four years of work experience.

SWEBOK V3 • IEEE Computer Society

These two definitions should be seen as complementary. When an editor proposes a draft knowledge area, a selected group of invited experts provide wide ranging comments, in a review similar to that for academic papers. The group discusses these comments, and the editor then incorporates the accepted changes.

Next, a larger group of invited practitioners answers a set list of about 14 questions on the new draft. These questions have to do with relevancy and usefulness, and the editor uses the responses to further refine the draft.


The last review is open to the public, but comments must be specific, and reference a particular line or item ewebok the draft. Advances in Software Maintenance Management: Idea Group Publishing, After the Gold Rush: Code Complete, 2nd ed. Encyclopedia of Software Engineering, Marciniak, J. Software Safety and Reliability: Is a Data Model, in Fact, a Model?

Practicing Software Engineering in the 21st Century. Software Engineering – A Practitioner’s Approach, 6th ed.

Software Engineering Body of Knowledge

Software Requirements, 2nd ed. Anyone who develops software should be familiar with the Guide and use it where applicable. A simple definition is “established traditional practices recommended by many organizations. Its Guide to the Project Management Body of Knowledge defines “generally accepted” knowledge for project xwebok in the following manner: Comments characters or less.