Body of Knowledge (glossary)

(1) The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a consensually validated characterization of the bounds of the software engineering discipline and to provide a topical access to the Body of Knowledge supporting that discipline. (Abran,A. 2004)

(2) Identifies that subset of the project management body of knowledge generally recognized as good practice. “Generally recognized” means the knowledge and practices described are applicable to most projects most of the time, and there is consensus about their value and usefulness. “Good practice” means there is general agreement that the application of these skills, tools, and techniques can enhance the chances of success over a wide range of projects...The PMBOK Guide also provides and promotes a common vocabulary within the project management profession…The Project Management Institute views this standard as a foundational project management reference for its professional development programs and certifications. (PMI 2008)

(3) Document explicitly intended to capture the knowledge for entry into the practice of [an] engineering [discipline] at the professional level. (ASCE 2008)

Source

(1) Abran, A., J. W. Moore, P. Bourque, R. Dupuis, and L. L. Tripp. 2004. SWEBOK: Guide to the Software Engineering Body of Knowledge: 2004 version. Los Alamitos, CA; Tokyo, Japan: IEEE Computer Society Press.

(2) PMI. 2008. A Guide to the Project Management Body of Knowledge (PMBOK Guide). 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).

(3) ASCE. 2008. Civil Engineering Body of Knowledge for the 21st Century: Preparing the Civil Engineer for the Future, 2nd edition. Reston, VA, USA: American Society of Civil Engineers.

Discussion

Discussion as to why this is the "consensus" definition for the SEBoK.