241337 Adding basic process concepts page
diff --git a/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/basic_process_concepts.xmi b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/basic_process_concepts.xmi
index 5c66974..9b2deb9 100644
--- a/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/basic_process_concepts.xmi
+++ b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/basic_process_concepts.xmi
@@ -1,7 +1,203 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore"
- xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-xL8v-tHFI6eyHLEaZ4rblA"
- name="new_concept,_FxJEkFUKEd2_rMtRMt_EMg" guid="-xL8v-tHFI6eyHLEaZ4rblA" changeDate="2008-07-18T13:43:53.562-0700">
- <mainDescription>[Placeholder]</mainDescription>
+ xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.5.0" xmi:id="-xL8v-tHFI6eyHLEaZ4rblA"
+ name="new_concept,_FxJEkFUKEd2_rMtRMt_EMg" guid="-xL8v-tHFI6eyHLEaZ4rblA" changeDate="2008-07-28T13:09:14.343-0700">
+ <mainDescription><h3>
+ The Basic Elements
+</h3>
+<p>
+ The basic elements of a process website are:
+</p>
+<ul>
+ <li>
+ <strong>Work product</strong>: what is produced
+ </li>
+ <li>
+ <strong>Task</strong>: how to perform the work
+ </li>
+ <li>
+ <strong>Role</strong>: who performs the work
+ </li>
+ <li>
+ <strong>Process</strong>: used to define work breakdown and workflow
+ </li>
+ <li>
+ <strong>Guidance</strong>: templates, checklists, examples, guidelines. concepts, …
+ </li>
+</ul>
+<p>
+ These "basic elements" are the building blocks from which processes are composed.
+</p>
+<h3>
+ Organizing Elements
+</h3>
+<p>
+ The basic elements are organized/grouped using the following elements.
+</p>
+<h4>
+ Practice
+</h4>
+<p>
+ A practice is a documented approach to solving one or several commonly occurring problems. Practices are intended as
+ "chunks" of process for adoption, enablement, and configuration. Practices are built from the basic elements described
+ above.
+</p>
+<h4>
+ Configuration
+</h4>
+<p>
+ From the end-user perspective, a configuration is a selection of method content to be published.&nbsp; Most
+ configurations consist of a selection of practices plus some&nbsp;content to tie the practices together.&nbsp;&nbsp;
+ The published configuration is often loosely referred to as a process website.
+</p>
+<h3>
+ Details and Examples
+</h3>
+<p>
+ The following provides more detail about the basic elements and provides some examples.
+</p>
+<h4>
+ Work product
+</h4>
+<p>
+ Work products may take various shapes or forms, such as:
+</p>
+<ul>
+ <li>
+ A model, such as the Use-Case Model or the Design Model. These contain model elements (sub-artifacts) such as
+ Design Classes, Use Cases, and Design Subsystems.
+ </li>
+ <li>
+ Databases or other types of tabular information repositories such as spreadsheets
+ </li>
+ <li>
+ Source code and executables
+ </li>
+ <li>
+ Various types of documents, for example a specification document, such as Requirements Specification, or a plan
+ document, such as the Software Development Plan.
+ </li>
+</ul>
+<p>
+ Work products can be classified as "artifacts" if they are concrete things, "outcomes" if they are not concrete, and
+ "deliverables" if they are a packaging of artifacts.
+</p>
+<h4>
+ <br />
+ Role
+</h4>
+<p>
+ A role defines the behavior and responsibilities of an individual, or a set of individuals working together as a team,
+ within the context of a software engineering organization.<br />
+ Note that roles are not individuals; instead, roles describe responsibilities. An individual will typically take on
+ several roles at one time, and frequently will change roles over the duration of the project.
+</p>
+<p>
+ Some examples:
+</p>
+<ul>
+ <li>
+ <strong>Analyst&nbsp;-</strong>&nbsp;Represents customers and end users, gathers input from stakeholders and
+ defines requirements.
+ </li>
+ <li>
+ <strong>Developer -</strong> Develops a part of the system, including designing, implementing, unit testing, and
+ integrating.
+ </li>
+</ul>
+<h4>
+ Task
+</h4>
+<p>
+ A task is work performed by a role. It is usually defined as a series of steps that involve creating or updating one or
+ more work products.
+</p>
+<p>
+ Some examples:
+</p>
+<ul>
+ <li>
+ <strong>Develop a vision -</strong> Develop an overall vision for the system, including capturing the problem to be
+ solved, the key stakeholders, the scope/boundary of the system, the system's key features, and any constraints.
+ </li>
+ <li>
+ <strong>Plan Iteration -</strong> Define the scope and responsibilities of a single iteration.
+ </li>
+</ul><br />
+<h4>
+ Process
+</h4>
+<p>
+ Processes pull together tasks, work products, and roles, and add structure and sequencing information.&nbsp; Tasks or
+ work products can be grouped into higher level activities, called a work breakdown structure
+ (WBS).&nbsp;&nbsp;Activities or tasks can be marked as "planned" to identify work that you expect to assign and track.
+</p><br />
+<br />
+<center>
+ <img
+ alt="This is an example work breakdown structure, showing a hierarchy of activities with sub-activities and tasks."
+ src="./resources/wbs_example.jpg" align="center" />&nbsp;<br />
+ Figure 1: Example Work Breakdown
+</center><br />
+<br />
+<p>
+ Diagrams can be added to providing sequencing information.&nbsp; The following example shows an initial activity, "Plan
+ Test Cycle", followed by two activities that go in parallel, "Monitor and Control Test" and "Test".
+</p><br />
+<br />
+<center>
+ <img height="453"
+ alt="Example UML activity diagram, showing a start, an initial activity, then two activities in parallel, and an end."
+ src="./resources/activity_diag_ex.jpg" width="566" align="center" /><br />
+ Figure&nbsp;2: Example Activity Diagram
+</center><br />
+<br />
+<p>
+ Note that a&nbsp;reusable partial process is sometimes referred to as a capability pattern.
+</p>
+<h3>
+ For More Information
+</h3>
+<p>
+ These basic process concepts are the building blocks used by EPF Composer and Rational(R) Method Composer.
+</p>
+<ul>
+ <li>
+ For more information on EPF Composer,&nbsp;visit <a
+ href="http://www.ibm.com/developerworks/rational/library/dec05/haumer/">http://www.ibm.com/developerworks/rational/library/dec05/haumer/</a>
+ </li>
+ <li>
+ To learn more about the Eclipse Process Framework Project, visit<br />
+ <a
+ href="http://www-128.ibm.com/developerworks/rational/library/05/1011_kroll/index.html">http://www-128.ibm.com/developerworks/rational/library/05/1011_kroll/index.html</a>
+ </li>
+ <li>
+ For more information on Rational Method Composer, see: 
+ <ul>
+ <li>
+ The RMC Product Page on developer works <a
+ href="http://www-306.ibm.com/software/awdtools/rmc/">http://www-306.ibm.com/software/awdtools/rmc/</a>
+ </li>
+ <li>
+ Article: "IBM Rational Method Composer: Part 1: Key concepts" at <a
+ href="http://www.ibm.com/developerworks/rational/library/dec05/haumer/index.html">http://www.ibm.com/developerworks/rational/library/dec05/haumer/index.html</a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ For an in-depth explanation of the meta-model on which EPF Composer and Rational Method Composer are based, see:
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ OMG, "Software Process Engineering Meta model," version 1.1, formal/2005-01-06, 2005. <a
+ href="http://www.omg.org/technology/documents/formal/spem.htm">http://www.omg.org/technology/documents/formal/spem.htm</a><br />
+ <br />
+ <br />
+ </li>
+ </ul>
+ </li>
+</ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
diff --git a/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/activity_diag_ex.jpg b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/activity_diag_ex.jpg
new file mode 100644
index 0000000..67f588a
--- /dev/null
+++ b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/activity_diag_ex.jpg
Binary files differ
diff --git a/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/wbs_example.jpg b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/wbs_example.jpg
new file mode 100644
index 0000000..e4833d3
--- /dev/null
+++ b/libraries/EPF_Practices_Library/core.default.uma_concept.base/guidances/concepts/resources/wbs_example.jpg
Binary files differ
