Message Boards (Guide) Message Boards (Guide)
« Back

What goes in a BOK?

Combination View Flat View Tree View
Threads [ Previous | Next ]
What goes in a BOK?
10/1/12 1:08 PM
Hi, All,
So far, we have been using Enterprise IT and Execs as our target audience. That provides some recognizable boundaries for the contents of the CC BOK. To narrow it a bit more, we should assume that our audience understands the standard operations and principles of IT organizational work and information processing. (IT itself will be covered in the ITBOK.) So, our focus is on what is commonly known about cloud technology and how the cloud changes IT. Later IEEE work may elect to add other areas -- for researchers, for example.
In addition, it might be helpful to review the following info from the “vanilla” package we are putting together for authors of BOKs published by the IEEE CS. I’ll be ending a couple of other mails about requirements for authors and common timelines.

What Do We Mean by “Generally Recognized Knowledge”?
A “Body of Knowledge” is an all-inclusive term that describes the sum of knowledge within a given profession. However, the IEEE-CS BOK Guides seek to identify and describe that subset of the body of knowledge in a given field that is generally recognized or, in other words, the core body of knowledge. To better illustrate what “generally recognized knowledge” is relative to other types of knowledge, Figure 1 proposes a three-category schema for classifying knowledge.
The Project Management Institute in its Guide to the Project Management Body of Knowledge defines “generally recognized” knowledge for project management as being:
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. Good practice does not mean the knowledge described should always be applied uniformly to all projects; the organization and/or project management team is responsible for determining what is appropriate for any given project.
“Generally accepted” knowledge could also be viewed as knowledge to be included in the study material of a licensing exam in the field that a college graduate would take after completing four years of work experience. These two definitions should be seen as complementary.
Knowledge Area Editors are also expected to be somewhat forward looking in their interpretation by taking into consideration not only what is “generally recognized” today and but what they expect will be “generally recognized” in a 3- to 5-year timeframe.

Categories of Knowledge

Specialized Knowledge-- Practices used only for certain types of software
Generally Recognized -- Established traditional practices recommended by many organizations
Innovative practices -- tested and used only by some organizations and concepts still being developed and tested in Advanced and Research organizations

Length of Knowledge Area Description
Knowledge Area Descriptions are to be roughly 10 to 20 pages, or 6,000-12,000 words. This includes text, reference citations, appendices, tables, etc.
Chuck Walrad