Various bodies of knowledge standards and guidance
The SBOK Guide was developed as a means to create a necessary guide for organizations and professionals who want to implement Scrum, as well as those already doing so who want to make needed improvements to their existing processes. It is based on experience drawn from thousands of projects across a variety of organizations and industries. The contributions of many Scrum experts and project management practitioners have been considered in its development.
The Guide to the Systems Engineering Body of Knowledge (SEBoK) was created by the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) project. The SEBoK provides a compendium of the key knowledge sources and references of systems engineering organized and explained to assist a wide variety of users. It is a living product, accepting community input continuously, with regular refreshes and updates. Systems engineering is an interdisciplinary approach and means to enable the full life cycle of successful systems, including problem formulation, solution development and operational sustainment and use. Those new to Systems Engineering can find introductory articles which provide an overview of systems engineering, place it in historical context, and discuss its economic value in Part 1 of this body of knowledge. In Part 2-7 extensive guidelines are given. The complete SEBoK is over 1000 pages.
Enterprise Architecture practice is growing quickly, accelerating in pace and adoption throughout the world but lacks an authoritative, unbiased place to learn about the wide array of experiences, methods and practices, and experiences. The EA Body of Knowledge is a unique endeavor created by people who believe, first and foremost, that the best way to gather the knowledge about Enterprise Architecture is to ask practitioners and researchers to simply share what they know, what they do, and how well it works. This is practical knowledge. The EABOK is home to terms and concepts, standards and practices, methods and patterns, and perspectives on what works... and what fails to work. We are striving first for breadth and usefulness. Consistency will evolve with maturity. The EABOK Consortium has senior leaders in the Enterprise Architecture community, including representatives from industry, government, and professional associations. But we are not looking only to ourselves for knowledge. On the contrary! While we have seeded the EABOK, we believe it will not be complete, actionable, and balanced, until we have input and insight from practitioners, researchers, and stakeholders. We aspire to have the EABOK become an ever-evolving map to insightful and useful information about enterprise architecture. Whether you are an experienced practitioner, an aspiring architect, or just someone interesting in this fascinating field, we welcome you to join our consortium hosted by MITRE and become a part of the Enterprise Architecture Body of Knowledge.
Software engineering, both as a discipline and as a profession, is at a pivotal point in its evo-lution. Although software has become critical in the development of most new human-created systems, the concepts, principles, and methods for engineering software are still neither well defined nor uniformly agreed upon. The lack of consensus regarding software engineering practice and the requisite competencies creates confusion and has serious consequences for the evaluation, acquisition, and application of software engineering knowledge. This report presents an effort to organize and catalogue a body of knowledge for software engineering and to provide a systematic, concise, and complete description of the software engineering discipline. This body of knowledge can assist organizations in defining and improving the software engineering competencies of their workforces; it can help educational institutions in defining software engineering curricula; it can provide a basis for classifying academic and industrial research and development efforts; and it can improve the understanding and prac-tice of software engineering.
The CISSP curriculum covers subject matter in a variety of Information Security topics. The CISSP examination is based on what (ISC)terms the Common Body of Knowledge (or CBK). According to (ISC), "the CISSP CBK is a taxonomy -- a collection of topics relevant to information security professionals around the world. The CISSP CBK establishes a common framework of information security terms and principles that allow information security professionals worldwide to discuss, debate and resolve matters pertaining to the profession with a common understanding.
The purpose of the Guide to the EA Body of Knowledge (EABOK) is to provide a characterization of and structure to the knowledge content of the EA discipline, promote a consistent view of EA, begin to bound the scope of the discipline, and place the EA discipline in the context of related disciplines. The guide provides topical access to the EABOK. It subdivides EA into knowledge areas and topics within each knowledge area, presents overviews of each topic, and gives references to sources of further information.The Guide to the EABOK is a guide, not the EA body of knowledge itself.
The Usability Body of Knowledge (BoK) project is dedicated to creating a living reference that represents the collective knowledge of the usability profession. Preliminary work has started, but there is more to do. This website introduces the subject areas that will eventually be included in the Usability Body of Knowledge and a preview of what to come.