Removed redundant "basic process concepts" page
diff --git a/epf_prac_151/practice.bus.mdev.base/guidances/concepts/basic_process_concepts.xmi b/epf_prac_151/practice.bus.mdev.base/guidances/concepts/basic_process_concepts.xmi
deleted file mode 100644
index 2f1f5f5..0000000
--- a/epf_prac_151/practice.bus.mdev.base/guidances/concepts/basic_process_concepts.xmi
+++ /dev/null
@@ -1,140 +0,0 @@
-<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-a_GVkaZUqQL6T1r_ksL-PQ" name="new_concept,_js1CIJ8vEd-dppiOhprtkA" guid="-a_GVkaZUqQL6T1r_ksL-PQ" changeDate="2010-08-03T11:48:07.000-0700" version="7.5.0">
- <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: a method library, which includes method plug-ins
- and method configurations.&nbsp;
-</p>
-<p>
- Plug-ins consist of roles, tasks, work products, guidance, capability patterns and delivery processes. Plug-ins may be
- further organized using content packages. For example, all content related to a specific content area may be placed in
- the same content package. Each of these packages might be further divided into sub-packages representing sub-topics.
- For example,&nbsp;within a specific development content package,&nbsp;you may want to&nbsp;have a sub-package
- that&nbsp;includes specific information about visual modeling.
-</p>
-<p>
- From the end-user perspective, a method configuration&nbsp;is a selection of method elements to be published.&nbsp;The
- published configuration is often loosely referred to as a process website.&nbsp; Internally, configurations are a
- selection of plug-ins and content packages, along with (optionally) a set of navigation views.&nbsp; Taking the earlier
- example a little further, you can add or remove&nbsp;visual modeling&nbsp;specifics from&nbsp;a configuration by just
- including or excluding the visual modeling content package to/from the configuration.&nbsp;
-</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>
- Documents, such as a Vision, or a Project Plan.
- </li>
- <li>
- A model, such as a Use-Case Model or a Design Model. These can contain model elements (sub-artifacts) such as
- Design Classes, Use Cases, and Design Subsystems.
- </li>
- <li>
- Databases, spreadsheets, and other information repositories.
- </li>
- <li>
- Source code and executables.
- </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>
- Role
-</h4>
-<p>
- A role&nbsp;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>
-<h4>
- Guidance
-</h4>
-<p>
- Guidance can be associated to any method element and comes in a number of different varieties, each with their own
- specific characteristics (e.g., checklist, concept, example, guideline, practice, report, reusable asset, roadmap,
- supporting material, template, term definition, tool mentor, white paper, etc).<br />
-</p>
-<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&nbsp;(WBS).&nbsp;&nbsp;Activities or tasks can be marked as "planned" to identify work that you expect to
- assign and track.
-</p>Note that a reusable partial process is sometimes referred to as a capability pattern, whereas a more complete,
-end-to-end process is sometimes referred to as a delivery process. <br /></mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/epf_prac_151/practice.bus.mdev.base/plugin.xmi b/epf_prac_151/practice.bus.mdev.base/plugin.xmi
index ab93bf3..88045bd 100644
--- a/epf_prac_151/practice.bus.mdev.base/plugin.xmi
+++ b/epf_prac_151/practice.bus.mdev.base/plugin.xmi
@@ -14,13 +14,12 @@
<resourceDescriptors xmi:id="_-7IlgLekEd-D7YZN9NgldQ" id="-fGepq7Yt-PmW_jH9cOMsHg" uri="guidances/practices/method_development.xmi"/>
<resourceDescriptors xmi:id="_-7IlgbekEd-D7YZN9NgldQ" id="-8HIJRiG1VwF8mwvxuZ0c2Q" uri="guidances/roadmaps/how_to_adopt_mdev.xmi"/>
<resourceDescriptors xmi:id="_-7IlgrekEd-D7YZN9NgldQ" id="-pNLG5Sw3YW-HjuCTssLRYA" uri="guidances/concepts/method_authoring.xmi"/>
- <resourceDescriptors xmi:id="_-7SWgLekEd-D7YZN9NgldQ" id="-a_GVkaZUqQL6T1r_ksL-PQ" uri="guidances/concepts/basic_process_concepts.xmi"/>
<resourceDescriptors xmi:id="_-7SWgbekEd-D7YZN9NgldQ" id="-EvdZRG7js6dnleNgGOQYfQ" uri="guidances/concepts/practice.xmi"/>
<resourceDescriptors xmi:id="_-7SWgrekEd-D7YZN9NgldQ" id="-IMDeKIiADfZMg8gyWT_JYw" uri="guidances/concepts/umf.xmi"/>
<resourceDescriptors xmi:id="_-7cHgLekEd-D7YZN9NgldQ" id="-XV4rH8guz_Py0zgFgqXCsw" uri="guidances/guidelines/testing_a_method_asset.xmi"/>
<resourceDescriptors xmi:id="_-7cHgbekEd-D7YZN9NgldQ" id="-nTT9dDA_7wXIt7w09kNZjg" uri="guidances/supportingmaterials/release_info.xmi"/>
</org.eclipse.epf.uma.resourcemanager:ResourceManager>
- <org.eclipse.epf.uma:MethodPlugin xmi:id="_HVCXcE7xEd-ttuvo_zEJ_g" name="practice.bus.mdev.base" guid="_HVCXcE7xEd-ttuvo_zEJ_g" presentationName="Method Development" briefDescription="This practice describes a method to develop method content." changeDate="2010-04-29T02:31:29.000-0700">
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_HVCXcE7xEd-ttuvo_zEJ_g" name="practice.bus.mdev.base" guid="_HVCXcE7xEd-ttuvo_zEJ_g" presentationName="Method Development" briefDescription="This practice describes a method to develop method content." changeDate="2011-07-13T12:07:26.391-0700">
<methodElementProperty xmi:id="_-gnMwbekEd-D7YZN9NgldQ" name="plugin_synFree" value="true"/>
<copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_uuunoPsDEdmyhNQr5STrZQ"/>
<methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_9Tui0LekEd-D7YZN9NgldQ" name="Content" guid="_9Tui0LekEd-D7YZN9NgldQ">
@@ -69,8 +68,24 @@
<contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_dxRsUEH-Ed-bmYzvomIdMg" name="structuring_practice" guid="_dxRsUEH-Ed-bmYzvomIdMg" presentationName="Structuring a Practice" briefDescription="This guideline provides recommendations for structuring a practice.">
<presentation xmi:id="-WuAi2XsisktfzngHrIxJ0g" href="uma://-WuAi2XsisktfzngHrIxJ0g#-WuAi2XsisktfzngHrIxJ0g"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_lFYasFImEd-S-5uzDh9e9Q" name="method_development" guid="_lFYasFImEd-S-5uzDh9e9Q" presentationName="Method Development" briefDescription="This practice describes a method to develop method content." contentReferences="_sh3v4iMmEd-VobohmWswkw __I8S0D2kEd-lU6YVR9_PJQ _EXvLwD3NEd-realK_We5vA _fx7TMD3REd-realK_We5vA _1V5psEH9Ed-bmYzvomIdMg _E9J1kD9EEd-Xgadv74rzHA _dxRsUEH-Ed-bmYzvomIdMg _kY8j4EH-Ed-bmYzvomIdMg _PTzXQE8REd-xRf1mYeAI9w _ghjHwDusEd-0GPJdQkFa_A _Z7gHED08Ed-lU6YVR9_PJQ _ytd9kKDhEd-nMJcdx60YsA _Bb4xMJ8eEd-1Fp7x64HaLA _js1CIJ8vEd-dppiOhprtkA _WBtggJ8wEd-dppiOhprtkA _wtFW8J8wEd-dppiOhprtkA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_lFYasFImEd-S-5uzDh9e9Q" name="method_development" guid="_lFYasFImEd-S-5uzDh9e9Q" presentationName="Method Development" briefDescription="This practice describes a method to develop method content.">
<presentation xmi:id="-fGepq7Yt-PmW_jH9cOMsHg" href="uma://-fGepq7Yt-PmW_jH9cOMsHg#-fGepq7Yt-PmW_jH9cOMsHg"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Roadmap" href="#_sh3v4iMmEd-VobohmWswkw"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#__I8S0D2kEd-lU6YVR9_PJQ"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_EXvLwD3NEd-realK_We5vA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_fx7TMD3REd-realK_We5vA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_1V5psEH9Ed-bmYzvomIdMg"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_E9J1kD9EEd-Xgadv74rzHA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_dxRsUEH-Ed-bmYzvomIdMg"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_kY8j4EH-Ed-bmYzvomIdMg"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_PTzXQE8REd-xRf1mYeAI9w"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_ghjHwDusEd-0GPJdQkFa_A"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_Z7gHED08Ed-lU6YVR9_PJQ"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Guideline" href="#_ytd9kKDhEd-nMJcdx60YsA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Concept" href="#_Bb4xMJ8eEd-1Fp7x64HaLA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Concept" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_FxJEkFUKEd2_rMtRMt_EMg"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Concept" href="#_WBtggJ8wEd-dppiOhprtkA"/>
+ <contentReferences xsi:type="org.eclipse.epf.uma:Concept" href="#_wtFW8J8wEd-dppiOhprtkA"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_sh3v4iMmEd-VobohmWswkw" name="how_to_adopt_mdev" guid="_sh3v4iMmEd-VobohmWswkw" presentationName="How To Adopt This Practice" briefDescription="This roadmap describes how to adopt the Method Development Practice.">
<presentation xmi:id="-8HIJRiG1VwF8mwvxuZ0c2Q" href="uma://-8HIJRiG1VwF8mwvxuZ0c2Q#-8HIJRiG1VwF8mwvxuZ0c2Q"/>
@@ -78,9 +93,6 @@
<contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_Bb4xMJ8eEd-1Fp7x64HaLA" name="method_authoring" guid="_Bb4xMJ8eEd-1Fp7x64HaLA" presentationName="Method Authoring" briefDescription="Authoring a method is all about taking the time to capture what you do and how you do it so that the same process can be performed in a consistent way by everyone involved. ">
<presentation xmi:id="-pNLG5Sw3YW-HjuCTssLRYA" href="uma://-pNLG5Sw3YW-HjuCTssLRYA#-pNLG5Sw3YW-HjuCTssLRYA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_js1CIJ8vEd-dppiOhprtkA" name="basic_process_concepts" guid="_js1CIJ8vEd-dppiOhprtkA" presentationName="Basic Process Concepts" briefDescription="All users of a process should be familiar with these basic process concepts.">
- <presentation xmi:id="-a_GVkaZUqQL6T1r_ksL-PQ" href="uma://-a_GVkaZUqQL6T1r_ksL-PQ#-a_GVkaZUqQL6T1r_ksL-PQ"/>
- </contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_WBtggJ8wEd-dppiOhprtkA" name="practice" guid="_WBtggJ8wEd-dppiOhprtkA" presentationName="Practice" briefDescription="A practice is an approach to solving one or several commonly occurring problems. Practices are intended as "chunks" of process for adoption, enablement, and configuration. ">
<presentation xmi:id="-EvdZRG7js6dnleNgGOQYfQ" href="uma://-EvdZRG7js6dnleNgGOQYfQ#-EvdZRG7js6dnleNgGOQYfQ"/>
</contentElements>
@@ -102,5 +114,6 @@
<methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9Tui3bekEd-D7YZN9NgldQ" name="DeliveryProcesses" guid="_9Tui3bekEd-D7YZN9NgldQ"/>
<methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_9Tui3rekEd-D7YZN9NgldQ" name="ProcessContributions" guid="_9Tui3rekEd-D7YZN9NgldQ"/>
<bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
</org.eclipse.epf.uma:MethodPlugin>
</xmi:XMI>
