<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Body_of_Knowledge</id>
	<title>Body of Knowledge - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://riskengineering.org/index.php?action=history&amp;feed=atom&amp;title=Body_of_Knowledge"/>
	<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Body_of_Knowledge&amp;action=history"/>
	<updated>2026-09-15T08:01:41Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://riskengineering.org/index.php?title=Body_of_Knowledge&amp;diff=239&amp;oldid=prev</id>
		<title>Pooyan: / Body of Knowledge</title>
		<link rel="alternate" type="text/html" href="https://riskengineering.org/index.php?title=Body_of_Knowledge&amp;diff=239&amp;oldid=prev"/>
		<updated>2025-02-12T14:37:54Z</updated>

		<summary type="html">&lt;p&gt;/ Body of Knowledge&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Bodies of Knowledge ==&lt;br /&gt;
&lt;br /&gt;
From **Risk Engineering/Civil Engineering**&lt;br /&gt;
&lt;br /&gt;
== Basic Considerations ==&lt;br /&gt;
A **body of knowledge (BoK)** is the accepted **ontology** for a specific domain. A BoK is more than simply a:&lt;br /&gt;
* Collection of terms&lt;br /&gt;
* Professional reading list&lt;br /&gt;
* Library or website&lt;br /&gt;
* Collection of information&lt;br /&gt;
&lt;br /&gt;
Instead, a BoK represents **consensus knowledge** that defines and organizes a profession&amp;#039;s **understanding of itself** and its **role in the global economy**. Additionally, these knowledge bodies allow **technical and lay personnel** to access structured knowledge through a **taxonomy** such as Bloom’s.&lt;br /&gt;
&lt;br /&gt;
### **Engineering Knowledge**&lt;br /&gt;
Unlike general knowledge, **engineering knowledge** is a specialized form of knowledge. Knowledge, in the broadest sense, can be defined as:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
&amp;quot;...a fluid mix of framed experience, values, contextual information, and expert insight that provides a framework for evaluating and incorporating new experiences and information.&amp;quot; &amp;lt;ref&amp;gt;Davenport, T.H. and Prusak, L. (2000), Working Knowledge: How Organizations Manage What They Know, Harvard Business School Press, Boston, MA.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In non-discipline cases, knowledge can be communicated through **documentation**. However, in fields like **civil engineering**, knowledge is embedded in **documents, repositories, organizational activities, processes, goodwill, and workflows**.&amp;lt;ref&amp;gt;Dutta/Madalli, Trends in Knowledge Modeling and Knowledge Management: An Editorial.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Logical Framework ==&lt;br /&gt;
(Section under construction)&lt;br /&gt;
&lt;br /&gt;
== Regulatory Framework ==&lt;br /&gt;
(Section under construction)&lt;br /&gt;
&lt;br /&gt;
== Practice Frameworks (Under Construction) ==&lt;br /&gt;
Several institutions have developed **bodies of knowledge** that define engineering and technical disciplines.&lt;br /&gt;
&lt;br /&gt;
### **Institute of Electrical and Electronics Engineers (IEEE) Computer Society**&lt;br /&gt;
The IEEE established **SWEBOK** to provide:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
&amp;quot;(A) consensually validated characterization of the bounds of the software engineering discipline and to provide topical access to the Body of Knowledge supporting that discipline. The descriptions of the Knowledge Areas (KA) are designed to discriminate among the various important concepts, permitting readers to find their way quickly to subjects of interest.&amp;quot;&amp;lt;ref&amp;gt;Abran, Alain, et al. &amp;quot;Guide to the Software Engineering Body of Knowledge: 2004 Edition-SWEBOK.&amp;quot; IEEE Computer Society (2004).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
### **American Society of Civil Engineers (ASCE) BoK**&lt;br /&gt;
(Details under construction)&lt;br /&gt;
&lt;br /&gt;
### **National Society of Professional Engineers (NSPE) Engineering Body of Knowledge (BoK)**&lt;br /&gt;
The **NSPE BoK** defines the **depth and breadth of knowledge, skills, and attitudes** required for **entry into professional engineering practice**:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
&amp;quot;A profession’s BoK is its common intellectual ground—it is shared by everyone in the profession regardless of employment or engineering discipline.&amp;quot;&amp;lt;ref&amp;gt;Engineering Body of Knowledge, National Society of Professional Engineers (NSPE) 2013.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Capabilities within the **NSPE BoK** are learned through a **combination of education and experience** and define **professional competency**.&lt;br /&gt;
&lt;br /&gt;
### **PMIBoK (Project Management Institute)**&lt;br /&gt;
The **PMI Body of Knowledge (PMIBoK)** defines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
“The sum of knowledge, published and unpublished, within the profession of project management. It consists of proven, traditional practices that are widely applied and innovative, yet evolving.”&amp;lt;ref&amp;gt;Project Management Institute, Body of Knowledge (PMIBoK), 5th edition, 2013.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The **PMIBoK Guide** identifies:&lt;br /&gt;
1. **Generally recognized practices** applicable to most projects.&lt;br /&gt;
2. **Good practices** that enhance success rates.&lt;br /&gt;
3. **Adaptable approaches** where practices should not be applied rigidly to all projects.&lt;br /&gt;
&lt;br /&gt;
### **ISO**&lt;br /&gt;
(Section under construction)&lt;br /&gt;
&lt;br /&gt;
== Limitations of the Definition ==&lt;br /&gt;
This **body of knowledge** represents a **distilled version** of the overall knowledge in engineering. Unlike **best practices**, PMI now refers to &amp;quot;good practices&amp;quot; to reflect the **evolutionary nature** of the profession.&amp;lt;ref&amp;gt;PMIBoK 5th Edition, 2013.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Working Definition of the Term ==&lt;br /&gt;
(Section under construction)&lt;br /&gt;
&lt;br /&gt;
== Beneficial Outcomes ==&lt;br /&gt;
Some of the **beneficial outcomes** of developing BoKs include:&lt;br /&gt;
* Achieving a **consistent national or global standard** for a profession.&lt;br /&gt;
* Establishing **disciplinary boundaries** between professions.&lt;br /&gt;
* Defining **policy or regulatory constraints** regarding professional responsibilities.&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Wiki article on Body of Knowledge]]&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
{{Notelist}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Pooyan</name></author>
	</entry>
</feed>