fix tutorials from welcome page
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/AuthorPersp.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/AuthorPersp.JPG
deleted file mode 100644
index fa4e790..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/AuthorPersp.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/aboutepfcomposer.html b/1.5/plugins/org.eclipse.epf.help.doc/html/aboutepfcomposer.html
deleted file mode 100644
index 8ca5623..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/aboutepfcomposer.html
+++ /dev/null
@@ -1,164 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="About Eclipse Process Framework Composer" />
-<meta name="DC.Relation" scheme="URI" content="methodauthoringoverview.html#methodauthoringoverview" />
-<meta name="DC.Relation" scheme="URI" content="processauthoringoverview.html#processauthoringoverview" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="aboutepfcomposer" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>About Eclipse Process Framework Composer</title>
-</head>
-<body id="aboutepfcomposer"><a name="aboutepfcomposer"><!-- --></a>
-
-<h1 class="topictitle1">About Eclipse Process Framework Composer</h1>
-<div><p>Welcome to Eclipse Process Framework Composer (EPF Composer). EPF Composer is a tool platform that
-enables process engineers and managers to implement, deploy, and maintain
-processes for organizations or individual projects. Typically, two key problems
-need to be addressed to successfully deploy new processes.</p>
-<p>First, development teams need to be educated on the methods applicable
-to the roles that they are responsible for. Software developers typically
-need to learn how to do analysis and design, testers need to learn how to
-test implementations against requirements, managers need to learn how to manage
-the project scope and change, and so on. Some organizations assume that developers
-implicitly know how to do such work without documenting their methods, but
-many organizations want to establish common and regulated practices, to drive
-specific improvement objectives, and to meet compliance standards. </p>
-<p>Second, development teams need to understand how to apply these methods
-throughout a development lifecycle. That is, they need to define or select
-a development process. For example, requirements management methods have to
-be applied differently in early phases of a project where the focus is on
-elicitation of stakeholder needs and requirements and scoping a vision, than
-in later phases where the focus is on managing requirements updates and changes
-and performing impact analysis of these requirements changes. Teams also need
-clear understanding of how the different tasks of the methods relate to each
-other, for example, how the change management method impacts the requirements
-management method as well as regression testing method throughout the lifecycle.
-Even self-organizing teams need to define a process that gives at minimum
-some guidance on how the development will be scoped throughout the lifecycle,
-when milestones will be achieved and verified, and so on. </p>
-<div class="p">To that end, EPF Composer has two main purposes:<ul><li>To provide a knowledge base of intellectual capital which you can browse,
-manage and deploy. This content can include externally developed content,
-and, more importantly, can include your own content including of whitepapers,
-guidelines, templates, principles, best practices, internal procedures and
-regulations, training material, and any other general descriptions of your
-methods. This knowledge base can used for reference and education. It also
-forms the basis for developing processes (the second purpose). EPF Composer is designed
-to be a content management system that provides a common management structure
-and look and feel for all of your content, rather than being a document management
-system in which you would store and access hard to maintain legacy documents
-all in their own shapes and formats. All content managed in EPF Composer can be published
-to html and deployed to Web servers for distributed usage. </li>
-<li>To provide process engineering capabilities by supporting process engineers
-and project managers in selecting, tailoring, and rapidly assembling processes
-for their concrete development projects. EPF Composer provides catalogs of pre-defined
-processes for typical project situations that can be adapted to individual
-needs. It also provides process building blocks, called capability patterns,
-that represent best development practices for specific disciplines, technologies,
-or management styles. These building blocks form a toolkit for quick assembly
-of processes based on project-specific needs. EPF Composer also allows you to set up
-your own organization-specific capability pattern libraries. Finally, the
-processes created with EPF Composer can be published and deployed as Web sites. </li>
-</ul>
-</div>
-<div class="p"><strong>Eclipse Process Framework Composer Key Concepts</strong><ul><li>Provides completely redesigned tools for authoring, configuring, viewing,
-and publishing development processes. </li>
-<li>Provides just-in-time generation of publication previews in dedicated
-browsing perspective that allows rapid configuration switching. </li>
-<li>Manages method content using simple form-based user interfaces. Therefore,
-UML modeling skills are no longer required. </li>
-<li>Provides intuitive rich text editors for creating illustrative content
-descriptions. Editors allow use of styles, images, tables, hyperlinks, and
-direct HTML editing.</li>
-<li>Allows creating processes with breakdown structure editors and workflow
-diagrams through use of multi-presentation process editors. Breakdown structure
-editor supports different process views: work-breakdown view, work product
-usage view, and team allocation view. EPF Composer automatically synchronizes all presentations
-with process changes. </li>
-<li>Provides support for many alternative lifecycle
-models. For example, waterfall, incremental, or iterative models can be created
-with the same overlapping method content. </li>
-<li>Improved reuse and extensibility capabilities. The plug-in mechanisms
-from past versions have been extended to support extensions for breakdown
-structures.</li>
-<li>Supports reusable dynamically-linked process patterns of best practices
-for rapid process assembly via drag-and-drop. </li>
-</ul>
-</div>
-<p><strong>Key Terminology and Concepts</strong></p>
-<p>To effectively work with EPF Composer, you need to understand a few
-concepts that are used to organize the content. The pages Method Content Authoring
-Overview and Process Authoring Overview contain more detail and concrete examples
-of how to work in the tool. This page provides you with a general overview
-of these concepts. </p>
-<p>The most fundamental principle in EPF Composer is the separation of reusable core
-method content from its application in processes. This directly relates back
-to the two purposes of EPF Composer described in the first section. Almost all of EPF Composer's
-concepts are categorized along this separation. Method content describes what
-is to be produced, the necessary skills required and the step-by-step explanations
-describing how specific development goals are achieved. These method content
-descriptions are independent of a development lifecycle. Processes describe
-the development lifecycle. Processes take the method content elements and
-relate them into semi-ordered sequences that are customized to specific types
-of projects. </p>
-<p><img src="uma_hump.gif" alt="" /></p>
-<p>The figure above shows how this separation is depicted in Basic Unified
-Process. Method content, describing how development work is being performed,
-is categorized by disciplines along the y-axis of the diagram. The work described
-in a process is seen along the x-axis representing the timeline. This is the
-lifecycle of a development project. It expresses when what work will be performed.
-The graph in the illustration represents an estimated workload for each discipline.
-As you see, for example, one never stops working on requirements in OpenUP/Basic, but
-there are certainly peak times in which most of the requirements elicitation
-and description work is performed. There are also times at which a downward
-trend needs to be observed where fewer and fewer requirements changes have
-to be processed to bring the project to a close. This avoids what is referred
-to as feature creep in which requirements work remains constant or even increases.
-Hence, a lifecycle (process) expresses the variances of work performed in
-the various disciplines (method content). </p>
-<p><img src="meth_vs_proc.gif" alt="" /></p>
-<p>The picture above provides a summary of the key elements used in EPF Composer and
-how they relate to method content or process. As you see, method content is
-primarily expressed using work products, roles, tasks, and guidance. Guidance,
-such as checklists, examples, or roadmaps, can also be defined to provide
-exemplary walkthroughs of a process. On the right-hand side of the diagram,
-you see the elements used to represent processes in EPF Composer. The main element
-is the activity that can be nested to define breakdown structures as well
-as related to each other to define a flow of work. Activities also contain
-descriptors that reference method content. Activities are used to define processes
-of which EPF Composer support two main kinds: delivery processes and capability patterns.
-Delivery processes represent a complete and integrated process template for
-performing one specific type of project. They describe a complete end-to-end
-project lifecycle and are used as a reference for running projects with similar
-characteristics. Capability patterns are processes that express and communicate
-process knowledge for a key area of interest such as a discipline or a best
-practice. They are also used as building blocks to assemble delivery processes
-or larger capability patterns. This ensures optimal reuse and application
-of their key best practices in process authoring activities in EPF Composer.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodauthoringoverview.html#methodauthoringoverview">Method Content Authoring Overview</a></div>
-<div><a href="processauthoringoverview.html#processauthoringoverview">Process Authoring Overview</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/activity.html b/1.5/plugins/org.eclipse.epf.help.doc/html/activity.html
deleted file mode 100644
index a852149..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/activity.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Activity" />
-<meta name="DC.Relation" scheme="URI" content="developaworkbreakdownstructure.html#developaworkbreakdownstructure" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="activity" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Activity</title>
-</head>
-<body id="activity"><a name="activity"><!-- --></a>
-
-<h1 class="topictitle1">Activity</h1>
-<div><p>Activities represent the key building blocks for processes. Activities
-represent a grouping of breakdown elements such as other activities, task
-descriptors, role descriptors, <a href="workproductdescriptors.html#workproductdescriptors">work product descriptors</a>, and <a href="milestone.html#milestone">milestones</a>. In addition to breakdown structures, activities
-can also be presented in activity diagrams that graphically show the flow
-of work by showing which activities precede other activities. <a href="phase.html#phase">Phase</a> and <a href="iteration.html#iteration">iteration</a> are
-special types of activities that define specific properties.</p>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="developaworkbreakdownstructure.html#developaworkbreakdownstructure">Develop a Work Breakdown Structure</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addareferenceorhyperlink.html b/1.5/plugins/org.eclipse.epf.help.doc/html/addareferenceorhyperlink.html
deleted file mode 100644
index ad12501..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addareferenceorhyperlink.html
+++ /dev/null
@@ -1,74 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Add a Reference or Hyperlink" />
-<meta name="DC.Relation" scheme="URI" content="richtexteditor.html#richtexteditor" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="addareferenceorhyperlink" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Add a Reference or Hyperlink</title>
-</head>
-<body>
-
-<div class="nested0" id="addareferenceorhyperlink"><a name="addareferenceorhyperlink"><!-- --></a><h1 class="topictitle1">Add a Reference or Hyperlink</h1>
-<div><p>You can add two types of references or hyperlinks to your content text:
-references to other elements in the method library or references to external
-text with a URL that resides outside the method library.</p>
-<p>Text fields that support hyperlinks have a twisty symbol <img src="twisty symbol1.JPG" alt="" /> next to the text field's label. Click the symbol to expand
-the field into a full text editor. </p>
-<p>To insert a hyperlink to another element in the method library into a text
-field, locate the element you want to create a link to in the library or configuration
-view and then drag it into the appropriate text field, The link to the element
-is added as a method element with type prefix, meaning that the method element
-name is prefixed with the method element type. You can also drag a method
-element into an unexpanded text field that supports hyperlinks with the same
-result.</p>
-<div class="p">You can use the Add Link function in the rich text editor to add links
-that are references to other method elements or links to files or Web pages.
-This gives you further options in how your links are displayed.<ol><li>In the text editor, position the cursor where you want to insert the link
-and then click the <strong>Add Link</strong> button <img src="addlink_co.gif" alt="" /> in the tool bar. The Add Link dialog opens.</li>
-<li>Click the <strong>Browse</strong> button to locate and select the element you wish
-to create a link to. There are several options for creating links to other
-content elements, with each option offering a different way for displaying
-the link's name:<ul><li>Method element: the link displays the element name.</li>
-<li>Method with type prefix: the link displays the element name and type.</li>
-<li>Method element with custom text: the link displays user defined text.
-To define this text manipulate the text in between the <a></a<
-tags in the URL text field one you have selected an element using the <strong>Browse</strong> button.</li>
-</ul>
-</li>
-<li>To insert a hyperlink to an external URL, select URL from the Type drop
-down list, type the URL details in the URL field, and then click <strong>OK</strong>.</li>
-<li>To insert a hyperlink to a file, in the Type drop down list, click <strong>File</strong>,
-enter the file name or browse to find the file, and then click <strong>OK</strong>.
-Each time you add a link you can choose to have the target open in the same
-browser window or in a new window.</li>
-</ol>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="richtexteditor.html#richtexteditor">Rich Text Editor</a></div>
-</div>
-</div></div>
-
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addimg_co.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/addimg_co.gif
deleted file mode 100644
index ecbd720..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addimg_co.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addlink_co.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/addlink_co.gif
deleted file mode 100644
index 41a386a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addlink_co.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addordlist_co.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/addordlist_co.gif
deleted file mode 100644
index 971d677..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addordlist_co.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addtable_co.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/addtable_co.gif
deleted file mode 100644
index 2536dd9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addtable_co.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/addunordlist_co.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/addunordlist_co.gif
deleted file mode 100644
index 70749e7..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/addunordlist_co.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/applyacapabilitypattern.html b/1.5/plugins/org.eclipse.epf.help.doc/html/applyacapabilitypattern.html
deleted file mode 100644
index 3c7368a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/applyacapabilitypattern.html
+++ /dev/null
@@ -1,122 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Apply a Capability Pattern" />
-<meta name="DC.Relation" scheme="URI" content="capabilitypattern.html#capabilitypattern" />
-<meta name="DC.Relation" scheme="URI" content="createareusablecapabilitypattern.html#createareusablecapabilitypattern" />
-<meta name="DC.Relation" scheme="URI" content="replace.html#replaces" />
-<meta name="DC.Relation" scheme="URI" content="process.html#process" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="applyacapabilitypattern" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Apply a Capability Pattern</title>
-</head>
-<body id="applyacapabilitypattern"><a name="applyacapabilitypattern"><!-- --></a>
-
-<h1 class="topictitle1">Apply a Capability Pattern</h1>
-<div><div class="p">When developing a process, it is not necessary to develop the process
-from scratch, adding descriptors one by one. You can reuse existing capability
-patterns or even capability pattern parts to individually customize the pattern's
-content to the particular situation for which it is applied. A capability
-pattern must be applied to one specific activity in a process. For more information
-see <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a>.</div>
-<div class="section">There are two ways to apply a Capability Pattern: Copy and Extend. <p><strong>Copy
-a capability pattern:</strong></p>
-<div class="p">If a capability pattern is copied into a process,
-method content elements in the capability pattern are disconnected from the
-original. The capability pattern elements can be altered, deleted or changed
-as you want in the process editor without affecting the original method content
-elements. Method elements in a copied capability pattern appear in regular
-black font. To copy a capability pattern:<ol><li>In the <a href="configurationview.html#configurationview">Configuration View</a>,
-select a capability pattern or its parts that you want to copy into an activity
-in a process and drag the pattern or parts into the activity to which you
-want it to apply. To select multiple activities in a capability pattern, press
-the CTRL or SHIFT keys while you select. </li>
-<li>In the pop-up box that appears, click <strong>Copy</strong>. The capability pattern
-name is displayed in black and is now available for you to edit.</li>
-</ol>
-</div>
-<div class="p">Or,<ol><li>In the process view, right click an activity, and then click <strong>Apply
-Pattern > Copy</strong>. The Select Dialog For Processes window appears.</li>
-<li>Drill down into the process tree until you locate the capability pattern
-you want to copy.</li>
-<li>Select the pattern, and then click <strong>OK</strong>. The Select Dialog For Processes
-window closes and the capability pattern is applied.</li>
-</ol>
-</div>
-<p><strong>Extend a capability pattern:</strong></p>
-<div class="p">If a capability pattern
-is extended into a process, method content elements in the Capability Pattern
-retain a connection to the original. Extended capability pattern elements
-cannot be deleted or modified and appear as read-only in a green-italic font.
-To extend a capability pattern: <ol><li>In the <a href="configurationview.html#configurationview">Configuration View</a>,
-select a capability pattern or its parts that you want to extend into an activity
-in a process and drag the pattern or parts into the activity to which you
-want it to apply. To select multiple activities in a capability pattern, press
-the CTRL or SHIFT keys while you select.</li>
-<li>In the pop-up box that appears, click <strong>Extend</strong>. The capability pattern
-name is displayed in green, which indicates it is part of a process defined
-elsewhere.</li>
-</ol>
-</div>
-<div class="p">Or, <ol><li>In the process view, right click an activity and then click <strong>Apply
-Pattern > Extend</strong>. The Select Dialog For Processes window appears.</li>
-<li>Drill down into the process tree until you locate the capability pattern
-you want to extend.</li>
-<li>Select the pattern, and then click <strong>OK</strong>. The Select Dialog For Processes
-window closes and the capability pattern is applied.</li>
-</ol>
-</div>
-<div class="p"><div class="note"><span class="notetitle">Note:</span> If you do not want a specific activity or task in the capability
-pattern to be included in your process you can suppress it. The activity or
-task will not appear in the published process or be exported to a project
-planning tool. To suppress a process element, right click the element and
-then select <strong>Suppress</strong>. The element appears grayed out in the process
-view.</div>
-</div>
-</div>
-<div class="section"><div class="p">To add elements to an activity in an extended capability pattern:<ol><li>Find the activity's parent element. If this element is a not a local element
-that appears in green italic font, then you need create a contribution to
-this parent first. If the parent's parent is not local, also appearing in
-green italic font, then you need to create a contribution to the parent first,
-and so on. </li>
-<li>To create a contribution to an extended activity, right click the extended
-activity and then click <strong>Contribute</strong>. The activity becomes local and
-appears in a standard black font. Do this with all parent elements, top-down,
-until you reach the activity to which you want to apply the element. Once
-you click Contribute, the activity becomes local and is presented in standard
-black font.</li>
-</ol>
-For more information see <a href="contributes.html#contributes">Contributes</a>.</div>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a></div>
-<div><a href="replace.html#replaces">Replaces</a></div>
-<div><a href="process.html#process">Process</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createareusablecapabilitypattern.html#createareusablecapabilitypattern">Create a Reusable Capability Pattern</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/artifact.html b/1.5/plugins/org.eclipse.epf.help.doc/html/artifact.html
deleted file mode 100644
index 3fe5fc5..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/artifact.html
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Artifact" />
-<meta name="DC.Relation" scheme="URI" content="workproduct.html#workproduct" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Relation" scheme="URI" content="deliverable.html#deliverable" />
-<meta name="DC.Relation" scheme="URI" content="outcome.html#outcome" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="artifact" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Artifact</title>
-</head>
-<body id="artifact"><a name="artifact"><!-- --></a>
-
-<h1 class="topictitle1">Artifact</h1>
-<div><p>An artifact is a tangible work product that is consumed, produced, or modified
-by tasks. Artifacts may be composed of other artifacts. For example, a model
-artifact can be composed of model elements, which are also artifacts. </p>
-<p>Roles use artifacts to perform tasks and to produce other artifacts. Each
-artifact is the responsibility of a single role, making responsibility easy
-to identify and understand, and promoting the idea that every piece of information
-produced in a method requires the appropriate set of skills. Even though only
-one role is responsible for an artifact, other roles may use the artifacts.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="workproduct.html#workproduct">Work Product</a></div>
-<div><a href="deliverable.html#deliverable">Deliverable</a></div>
-<div><a href="outcome.html#outcome">Outcome</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/authoringperspective.html b/1.5/plugins/org.eclipse.epf.help.doc/html/authoringperspective.html
deleted file mode 100644
index dc64a65..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/authoringperspective.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Authoring Perspective" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html#browingperspective" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html#userinterfaceoverview" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="authoringperspective" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Authoring Perspective</title>
-</head>
-<body id="authoringperspective"><a name="authoringperspective"><!-- --></a>
-
-<h1 class="topictitle1">Authoring Perspective</h1>
-<div><p>The Authoring Perspective provides views and functions to navigate and
-author method content and processes. You must be in the Authoring Perspective
-to create or modify any element types.</p>
-<p>Click the Open Perspective button <img src="openpersp.JPG" alt="" /> and select Authoring to open the Authoring Perspective. </p>
-<p><img src="AuthorPersp.JPG" alt="" /></p>
-<p>The Authoring Perspective contains two Views: the <a href="libraryview.html#libraryview">Library View</a> and the <a href="configurationview.html#configurationview">Configuration View</a>. Double click any element in the
-Library View or Configuration View to open the Editor window on the right.
-The Editor window contains several tabs through which you can edit information
-about the element you have selected.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div class="nextlink"><strong>Next topic:</strong> <a href="browsingperspective.html">Browsing Perspective</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="browsingperspective.html#browingperspective">Browsing Perspective</a></div>
-<div><a href="userinterfaceoverview.html#userinterfaceoverview" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/bold.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/bold.gif
deleted file mode 100644
index f0c4685..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/bold.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/browseandpreviewmethodcontent.html b/1.5/plugins/org.eclipse.epf.help.doc/html/browseandpreviewmethodcontent.html
deleted file mode 100644
index 33cc014..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/browseandpreviewmethodcontent.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Browse and Preview Method Content" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="browseandpreviewmethodcontent" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Browse and Preview Method Content</title>
-</head>
-<body id="browseandpreviewmethodcontent"><a name="browseandpreviewmethodcontent"><!-- --></a>
-
-<h1 class="topictitle1">Browse and Preview Method Content</h1>
-<div><div class="p">You can browse method content in both the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a> and <a href="browsingperspective.html#browingperspective">Browsing Perspective</a>. While authoring method content, you can see a preview
-of the published page for the content you are editing by selecting the <strong>Preview</strong> tab
-at the bottom of the content editor. Click any link in the displayed page
-to go to that page. Use the buttons in the editor toolbar to perform familiar
-browser actions such as back or refresh. While browsing method content in
-the browsing perspective you can see a preview of any method and process content
-in a method configuration as it appears in a published Web site. </div>
-<div class="section"><p>To browse and preview <a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a> in the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>:</p>
-</div>
-<ol><li class="stepexpand"><span>Click the Open Perspective button <img src="openpersp.JPG" alt="" /> and select <strong>Authoring</strong>. The Authoring perspective
-opens with the <a href="libraryview.html#libraryview">Library View</a> and <a href="configurationview.html#configurationview">Configuration View</a> on
-the left and the content view on the right. If a method element is selected,
-the appropriate editor is open on the right.</span></li>
-<li class="stepexpand"><span>Explore the contents in the both the Library View and Configuration
-View by expanding the different content packages and method plug-ins down
-to their method elements. Double click an element to open it in the editor.</span></li>
-<li class="stepexpand"><span>Click the <strong>Preview</strong> tab at the bottom of the content editor
-to preview the content of any selected element.</span> <div class="note"><span class="notetitle">Note:</span> The preview
-page in the content editor does not resolve content variability relationships.
-If you are extending, contributing to, or replacing a base content item, you
-can only see the result of this in the Configuration View in the Browsing
-Perspective. For more information see <a href="variability.html#variability">Variability</a>.</div>
-<p></p>
-</li>
-</ol>
-<div class="section"><p>To browse and preview<a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a> in the <a href="browsingperspective.html#browingperspective">Browsing Perspective</a>:</p>
-<ol><li>Click the Open Perspective button <img src="openpersp.JPG" alt="" /> and select <strong>Browsing</strong>. The <a href="browsingperspective.html#browingperspective">Browsing Perspective</a> opens with the <a href="configurationview.html#configurationview">Configuration View</a> on the left and the Content View on the right.<p></p>
-</li>
-<li>Select a method configuration from the configuration drop-down list in
-the tool bar. The content of the method configuration appears in the content
-view, as it will appear in a published Web site.<p></p>
-</li>
-<li>Explore and preview the content in the Configuration View by expanding
-the categories and other folders down to method elements. Click a method element
-to open it in the content view.</li>
-</ol>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/browsepersp.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/browsepersp.JPG
deleted file mode 100644
index af691ff..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/browsepersp.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/browsingperspective.html b/1.5/plugins/org.eclipse.epf.help.doc/html/browsingperspective.html
deleted file mode 100644
index e61fe43..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/browsingperspective.html
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Browsing Perspective" />
-<meta name="DC.Relation" scheme="URI" content="authoringperspective.html#authoringperspective" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html#userinterfaceoverview" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Relation" scheme="URI" content="authoringperspective.html" />
-<meta name="DC.Relation" scheme="URI" content="configurationview.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="browingperspective" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Browsing Perspective</title>
-</head>
-<body id="browingperspective"><a name="browingperspective"><!-- --></a>
-
-<h1 class="topictitle1">Browsing Perspective</h1>
-<div><p>The Browsing Perspective allows you to preview and navigate through a Method
-Configuration without making any changes.</p>
-<p>Click the Open Perspective button <img src="openpersp.JPG" alt="" /> and select <strong>Browsing</strong> to open the Browsing Perspective.</p>
-<p><img src="browsepersp.JPG" alt="" /></p>
-<p>The Browsing perspective contains the <a href="configurationview.html#configurationview">Configuration View</a>, which shows the content in the currently
-selected configuration. Click any element in the Configuration
-View to preview the element in the Content View as it will appear in a published
-Web site. The Content View provides browser-like navigation features. Click
-any link in the displayed page to go to that page. Use the buttons in the
-Content View toolbar to perform familiar browser actions such as back or refresh.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div class="previouslink"><strong>Previous topic:</strong> <a href="authoringperspective.html">Authoring Perspective</a></div>
-<div class="nextlink"><strong>Next topic:</strong> <a href="configurationview.html">Configuration View</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="authoringperspective.html#authoringperspective">Authoring Perspective</a></div>
-<div><a href="userinterfaceoverview.html#userinterfaceoverview" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/capabilitypattern.html b/1.5/plugins/org.eclipse.epf.help.doc/html/capabilitypattern.html
deleted file mode 100644
index 9fe56ad..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/capabilitypattern.html
+++ /dev/null
@@ -1,65 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Capability Pattern" />
-<meta name="DC.Relation" scheme="URI" content="applyacapabilitypattern.html#applyacapabilitypattern" />
-<meta name="DC.Relation" scheme="URI" content="activity.html#activity" />
-<meta name="DC.Relation" scheme="URI" content="discipline.html#discipline" />
-<meta name="DC.Relation" scheme="URI" content="deliveryprocess.html#deliveryprocess" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="capabilitypattern" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Capability Pattern</title>
-</head>
-<body id="capabilitypattern"><a name="capabilitypattern"><!-- --></a>
-
-<h1 class="topictitle1">Capability Pattern</h1>
-<div><p>A Capability pattern is a special process that describes a reusable cluster
-of activities in common process areas. Capability patterns express and communicate
-process knowledge for a key area of interest such as a discipline and can
-be directly used by a process practitioner to guide his work. Capability patterns
-are also used as building blocks to assemble Delivery processes or larger
-capability patterns ensuring optimal reuse and application of the key practices
-they express.</p>
-<p>Examples of a capability pattern could be "use case-based requirements
-management", "use case analysis", or "unit testing". Typically, but not necessarily,
-capability patterns have the scope of one discipline providing a breakdown
-of reusable complex activities, relationships to the roles which perform tasks
-within these activities, as well as to the work products that are used and
-produced. A capability pattern does not relate to any specific
-phase or iteration of a development lifecycle, and should not imply any. In
-other words, a pattern should be designed in a way that it is applicable anywhere
-in a delivery process. thereby enabling its activities to be flexibly assigned
-to whatever phases there are in the delivery process to which it is being
-applied.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="activity.html#activity">Activity</a></div>
-<div><a href="discipline.html#discipline">Discipline</a></div>
-<div><a href="deliveryprocess.html#deliveryprocess">Delivery Process</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="applyacapabilitypattern.html#applyacapabilitypattern">Apply a Capability Pattern</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/checklist.html b/1.5/plugins/org.eclipse.epf.help.doc/html/checklist.html
deleted file mode 100644
index 5078ade..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/checklist.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Checklist" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="checklist" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Checklist</title>
-</head>
-<body id="checklist"><a name="checklist"><!-- --></a>
-
-<h1 class="topictitle1">Checklist</h1>
-<div><p>A Checklist is a specific type of guidance that identifies a series of
-items that need to be completed or verified. Checklists are often used in
-reviews such as a walk-throughs or inspections.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/clearcontent.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/clearcontent.gif
deleted file mode 100644
index ea35f47..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/clearcontent.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/collapsed.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/collapsed.gif
deleted file mode 100644
index 4e87759..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/collapsed.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/concept.html b/1.5/plugins/org.eclipse.epf.help.doc/html/concept.html
deleted file mode 100644
index f1982a9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/concept.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Concept" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="concept" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Concept</title>
-</head>
-<body id="concept"><a name="concept"><!-- --></a>
-
-<h1 class="topictitle1">Concept</h1>
-<div><p>A Concept is a specific type of guidance that outlines key ideas associated
-with basic principles underlying the referenced item. Concepts normally address
-more general topics than guidelines and span across several work product and/or
-tasks or activities.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/conf.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/conf.gif
deleted file mode 100644
index 4e5e6b9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/conf.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/configurationsandpublishingoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/configurationsandpublishingoverview.html
deleted file mode 100644
index 3fe11d7..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/configurationsandpublishingoverview.html
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Configurations and Publishing Overview" />
-<meta name="abstract" content="Put your short description here; used for first paragraph and abstract." />
-<meta name="description" content="Put your short description here; used for first paragraph and abstract." />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="configurationsandpublishingoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Configurations and Publishing Overview</title>
-</head>
-<body id="configurationsandpublishingoverview">
-<h3>Method Configurations Overview</h3>
-<p>Eclipse Process Framework Composer ships with a lot of content out of the box. It includes
- the OpenUP framework and various plug-ins extending
- OpenUP/Basic with domain-specific additions. No organization or project requires all of this
- documentation all at once, but would work with a selection of specific subsets.</p>
-<p> Eclipse Process Framework Composer (EPF Composer) manages for that purpose so-called method
- configurations, which allow you to specify working sets of content and processes
- for a specific context, such as a specific variant of the OpenUP framework that
- you want to publish and deploy for a given software project or as a foundation
- for a development organization. All content and processes in EPF Composer are organized
- in method plug-ins, which are organized into method packages. A method configuration
- is simply a selection of the method plug-ins and packages.</p>
-<p><img src="conf.gif" width="665"></p>
-<p>You create and specify a configuration using the configuration editor depicted
- in the figure above. You could start creating your own method configuration
- by copying one of the configurations that ship with EPF Composer and modify it to fit
- your specific needs. You can add or remove whole method plug-ins as well as
- make selection with each plug-in by checking or un-checking packages. </p>
-<p> You can use the resulting configuration as your working set for your EPF Composer
- work. The actual content of the configuration, i.e. the included method content
- and process elements are always accessible in the Configuration view. Use the
- combo box in the toolbar to select the currently used method configuration.</p>
-<h3>Publishing Overview</h3>
-<p>Method configurations are the basis for publishing method content and processes.
- A published configuration is an html Web site that presents all the method
- content and processes of the method configuration in a navigable and searchable
- way. It uses the relationships established during method content and process
- authoring to generate hyperlinks between elements as well as provides tree
- browsers based on the configuration view and user-defined categorizations of
- the content. The figure below shows an example of the published 'Classic RUP'
- method configuration.</p>
-<p><img src="pub.gif" width="550"></p>
-<p>For publishing simply create and select a configuration. The publication wizard
- will do the rest for you and only publish content that is part of the method
- configuration. It will also automatically adopt content to the configuration
- such as removing
- references of method content elements to elements outside of the configuration
- or removing activities from your processes that only contain work defined outside
- of the configuration set. Hence, publishing will only include the content that
- you really need. You can always preview a published configuration using EPF Composer's
-browsing perspective.</p>
-<p> </p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/configurationview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/configurationview.html
deleted file mode 100644
index c26192e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/configurationview.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Configuration View" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html#browingperspective" />
-<meta name="DC.Relation" scheme="URI" content="libraryview.html#libraryview" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html#userinterfaceoverview" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html" />
-<meta name="DC.Relation" scheme="URI" content="libraryview.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="configurationview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Configuration View</title>
-</head>
-<body id="configurationview"><a name="configurationview"><!-- --></a>
-
-<h1 class="topictitle1">Configuration View</h1>
-<div><p>The Configuration view shows the content elements in a library filtered
-by a configuration. </p>
-<p>A configuration is a subset of the <a href="standardmethodlibraryoverview.html#standardmethodlibraryoverview">method library</a> content. Once a configuration is selected
-in the Configuration selection box, the Configuration view is refreshed with
-the content from the selected configuration. The content in the Configuration
-view is always presented in the same way in standard categories, processes,
-custom categories, and guidance. The Configuration view does not show any
-physical folders. Folders are only shown in the Library view.</p>
-<p></p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div class="previouslink"><strong>Previous topic:</strong> <a href="browsingperspective.html">Browsing Perspective</a></div>
-<div class="nextlink"><strong>Next topic:</strong> <a href="libraryview.html">Library View</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="browsingperspective.html#browingperspective">Browsing Perspective</a></div>
-<div><a href="libraryview.html#libraryview">Library View</a></div>
-<div><a href="userinterfaceoverview.html#userinterfaceoverview" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/contributes.html b/1.5/plugins/org.eclipse.epf.help.doc/html/contributes.html
deleted file mode 100644
index 5c41bb4..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/contributes.html
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Contributes" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="extends.html#extends" />
-<meta name="DC.Relation" scheme="URI" content="replace.html#replaces" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="contributes" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Contributes</title>
-</head>
-<body id="contributes"><a name="contributes"><!-- --></a>
-
-<h1 class="topictitle1">Contributes</h1>
-<div><p>A contributing element adds to the base element. Contributes provides a
-way for elements to contribute their properties into their base element without
-directly changing any of its existing properties, such as in an additive fashion.
-The effect, after contribution, is that the base element is logically replaced
-with an element that combines the attributes and associations of the contributing
-element with the base element.</p>
-<p>Use the Content Variability section on the Description tab to make an element
-contribute to another element. Select <strong>Contributes</strong> as the Variability
-type and then select the base element to which this element will contribute.
-The base element must be the same type of element as the contributing element.</p>
-<p>Any information you enter in the contributing element is added to the base
-element. Text fields in the contributing element are added at the end of the
-respective text fields in the base element.</p>
-<p>Contribution only adds attributes and associations to the base. It never
-overrides or replaces any information from the base. In other words, if the
-base is allowed an association to exactly one other element and has this one
-already defined, it is not being replaced by a contributor's association.</p>
-<div class="p"><strong>Contribution rules:</strong><ul><li>Attributes are appended except for identifying/naming attributes and non-string
-attributes such as boolean, date, etc.</li>
-<li>Outgoing to-one associations of the contributor are ignored if the base
-already has such an association or if the base element has more than one contributing
-element (i.e. it cannot be decided which contribution should be chose, then
-none will be chosen).</li>
-<li>Outgoing to-many associations are added to the base elements of a contribution.</li>
-<li>Incoming associations to the contributing element with a to-one constraint
-on the other association end are ignored if the base already has such an incoming
-association or if there is more than one contribution to consider for the
-base element.</li>
-<li>Other incoming associations to the contributing element are added to the
-base elements of a contribution.</li>
-<li>A base element of a contribution can have more than one contributor</li>
-<li>Contribution works transitively, i.e. a contribution element contributes
-its own contributors.</li>
-</ul>
-See <a href="variabilityassociations.html#variabilityassociations">Variability Associations</a> to find the associations for each element
-type.</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-<div><a href="extends.html#extends">Extends</a></div>
-<div><a href="replace.html#replaces">Replaces</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/copy.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/copy.gif
deleted file mode 100644
index bc6dfe2..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/copy.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createacontentpackage.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createacontentpackage.html
deleted file mode 100644
index 9f58b8e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createacontentpackage.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Content Package" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html#createamethodplugin" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createcontentpackage" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Content Package</title>
-</head>
-<body id="createcontentpackage"><a name="createcontentpackage"><!-- --></a>
-
-<h1 class="topictitle1">Create a Content Package</h1>
-<div><div class="p"><p>Method content is organized into content packages which, in turn,
-are contained in method plug-ins.</p>
-Before creating a content package, you
-should create a method plug-in. For more information, see <a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a>.</div>
-<div class="section">You should always create a new <a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a> and <a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a> in a <a href="methodplugin.html#methodplugin">Method Plug-in</a> that
-you produce. This separates your content from original content shipped with
-the tool and allows you to update your own library with new library releases
-without affecting the content that you have created in your own plug-ins. <div class="note"><span class="notetitle">Note:</span> You
-cannot create a new content package or any other element in a locked plug-in.</div>
-<p>To
-create a content package:</p>
-</div>
-<ol><li><span>Find your method plug-in in the <a href="libraryview.html#libraryview">Library View</a>.</span></li>
-<li><span>Drill into the plug-in to locate the package called <strong>Content
-Packages</strong>. This package contains all packages that are allowed to contain
-method elements.</span></li>
-<li><span>Right click the content package and then select <strong>New > Content
-Package</strong>. The content package editor appears.</span></li>
-<li><span>Under General Information, give the new content package a unique
-name and provide a brief description.</span></li>
-<li><span>Save the new content package in one of three ways:</span><ol type="a"><li><span>Click the disk icon in the toolbar.</span></li>
-<li><span>Select <strong>File > Save</strong>.</span></li>
-<li><span>Simply close the content editor.</span></li>
-</ol>
-</li>
-</ol>
-<div class="section"><div class="note"><span class="notetitle">Note:</span> The tool automatically creates nodes for <a href="task.html#task">Task</a>, <a href="role.html#role">Role</a>, <a href="workproduct.html#workproduct">Work Product</a>, and <a href="guidance.html#guidance">Guidance</a> under the new content package.</div>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="methodcontentpackage.html">Method Content Package</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-<div><a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createadeliveryprocess.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createadeliveryprocess.html
deleted file mode 100644
index ecdef2e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createadeliveryprocess.html
+++ /dev/null
@@ -1,104 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Delivery Process" />
-<meta name="DC.Relation" scheme="URI" content="process.html#process" />
-<meta name="DC.Relation" scheme="URI" content="capabilitypattern.html#capabilitypattern" />
-<meta name="DC.Relation" scheme="URI" content="deliveryprocess.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createadeliveryprocess" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Delivery Process</title>
-</head>
-<body id="createadeliveryprocess"><a name="createadeliveryprocess"><!-- --></a>
-
-<h1 class="topictitle1">Create a Delivery Process</h1>
-<div><div class="p"><p>A Delivery Process describes a complete and integrated approach
-for performing a specific type of project. A Delivery Process describes what
-is produced, how it is produced and the required staffing for the entire project
-lifecycle.</p>
-A Delivery Process is created for a particular type of project
-to reflect the specific planning and project management needs. <p>Before
-creating a delivery process:</p>
-<ul><li>Select a method plug-in to hold your process. For more information, see <a href="methodplugin.html#methodplugin">Method Plug-in</a>.</li>
-<li>Find or create a process package.</li>
-</ul>
-</div>
-<div class="section">There are several ways to populate a process with method elements:<ul><li>By incorporating individual method elements by dragging the elements onto
-an activity in the process.</li>
-<li>By including already defined capability patterns.</li>
-<li>By including parts of already defined capability patterns.</li>
-<li>By creating descriptors directly in the process, which are either unrelated
-to any method content or related to method content at a later point in time.</li>
-</ul>
-To create a Delivery Process:</div>
-<ol><li class="stepexpand"><span>Once you have selected or created a process package, right click
-the process package.</span></li>
-<li class="stepexpand"><span>Click <strong>New > Delivery Process</strong>. The New Process Component
-dialog appears.</span></li>
-<li class="stepexpand"><span>Type a name for the delivery process into the <strong>Name</strong> field
-and then select a default configuration from the drop down list. Your process
-can contain content from many different method plug-ins. for this reason you
-need to define a configuration that defines the visible set of elements and
-relationships when the process is authored. This process authoring configuration
-is referred to as the Default Configuration for the process and should define
-the largest reasonable set of method plug-ins, content packages, and other
-processes from the method library that will be referred to by the process
-at some point.</span></li>
-<li class="stepexpand"><span>Click <strong>OK</strong>. The process is created and the process editor
-is opened.</span> <div class="note"><span class="notetitle">Note:</span> If the Properties window opens to the right of
-the process editor, click the <strong>x</strong> to close it.</div>
-</li>
-<li class="stepexpand"><span>In the process editor, under the Description tab, document your
-process using the available text fields.</span> <div class="note"><span class="notetitle">Note:</span> You can use the
-Rich Text Editor to edit or enter the text for any field that has a twisty
-symbol <img src="collapsed.gif" alt="" />. Simply click the symbol
-to access the Rich Text Editor. Click the symbol again to close the Rich Text
-Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a></div>
-</li>
-<li class="stepexpand"><span>Decide on your primary process authoring view. You develop a process
-using three different views:</span><ul><li><strong>Work Breakdown Structure</strong>: Define a work breakdown structure
-in your process. Create iterations and activities first, and then populate
-your activities by applying tasks from your Method Content. For more information
-see <a href="developaworkbreakdownstructure.html">Develop a Work Breakdown Structure</a>.</li>
-<li><strong>Team Allocation</strong>: Define which teams and roles shall participate
-in activities and then find responsible work products and tasks from there.
-For more information, see <a href="developateamallocationstructure.html#developateamallocationstructure">Develop a Team Allocation Structure</a>.</li>
-<li><strong>Work Product Usage</strong>: Define which work products should be created
-in activities and find tasks and roles from there. For more information see <a href="developaworkproductusagestructure.html#developaworkproductusagestructure">Develop a Work Product Usage Structure</a>.</li>
-</ul>
-</li>
-<li class="stepexpand"><span><a href="applyacapabilitypattern.html#applyacapabilitypattern">Apply a Capability Pattern</a> or capability pattern parts to the delivery process.</span></li>
-</ol>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="deliveryprocess.html">Delivery Process</a></strong><br />
-</li>
-</ul>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="process.html#process">Process</a></div>
-<div><a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodconfiguration.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodconfiguration.html
deleted file mode 100644
index 92ba465..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodconfiguration.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Method Configuration" />
-<meta name="DC.Relation" scheme="URI" content="methodconfigurations.html#methodconfigurations" />
-<meta name="DC.Relation" scheme="URI" content="methodplugin.html" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" />
-<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html" />
-<meta name="DC.Relation" scheme="URI" content="methodconfigurations.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createamethodconfiguration" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Method Configuration</title>
-</head>
-<body id="createamethodconfiguration"><a name="createamethodconfiguration"><!-- --></a>
-
-<h1 class="topictitle1">Create a Method Configuration</h1>
-<div><div class="p"><p>A method configuration allows you to select and deselect from the
-content packages and process available in the method library's set of plug-ins.
-The selections you make help you narrow down the content you are really interested
-in working with, as well as determine the content of the Web site you ultimately
-publish to deploy your process. A configuration is given a name and then saved
-so it can be changed and then re-published at a later date.</p>
-Before creating
-a method configuration, assess your needs and goals for the configuration.</div>
-<div class="section">There are two ways to create a method configuration:<a name="createamethodconfiguration__create"><!-- --></a><ul id="createamethodconfiguration__create"><li>Create a new method configuration from scratch.</li>
-<li>Create a method configuration by copying an existing configuration.</li>
-</ul>
-<strong>To create a new method configuration from scratch:</strong></div>
-<ol><li class="stepexpand"><span>Make sure you are working in the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>.</span></li>
-<li class="stepexpand"><span>In the Library view, right click the <strong>Configurations</strong> folder
-and then select <strong>New > Method Configuration</strong>. Your new configuration
-is created and the configuration editor is opened.</span></li>
-<li class="stepexpand"><span>In the configuration editor window, type a name for your configuration
-in the <strong>Name</strong> field. If you click anywhere in the <a href="libraryview.html#libraryview">Library View</a> or <a href="configurationview.html">Configuration View</a>, you
-will be able to see your new configuration name in the Configurations folder
-in the Library view tree.</span></li>
-<li class="stepexpand"><span>Type a description for your configuration in the Description field,
-and then select <strong>File > Save All</strong> to save your new method configuration.</span></li>
-<li class="stepexpand"><span>At the bottom of the editor window, click the <strong>Plug-in and Package
-Selection</strong> tab. </span></li>
-<li class="stepexpand"><span>The method configuration selection section displays a list of all
-method plug-ins their content packages and processes. Use the check boxes
-to add or remove plug-ins, packages, and processes to or from your configuration.
-Expand each plug-in to select and deselect individual packages and processes.</span> <p>As you make your selections, warning signs may appear against
-some of the plug-in and package names, and the Configuration Warning Log view
-may be displayed. These warnings are intended to help ensure that you create
-a configuration that "makes sense".</p>
-<p>If you reference an element in a
-package that is from another package, you can only see the full details for
-that element in a published Web site if the package containing the element
-is in the configuration. If the package containing the element is not in the
-configuration, the "offending" package is marked with a warning sign. You
-may choose not to include the full details of a referenced element. Click
-the <strong>Add Missing References</strong> button to automatically and recursively
-add packages containing any elements that are referenced in already selected
-packages. Since this is recursive, a large number of packages may be added,
-perhaps making your configuration larger than you want it to be.</p>
-<p>If
-you have elements in a package that contribute to, extend, or replace elements
-in another package, it is an error if the base package is not included in
-the configuration. Errors are marked with a red cross. If you drill down into
-a plug-in or package marked with a cross you will discover the "offending"
-package and then you can find the packages you need to include to resolve
-the error. Alternatively you can click the <strong>Make closure by fixing errors</strong> button
-to automatically fix the errors by adding the missing base packages.</p>
-<p>The
-Configuration Warning Log lists and explains all errors and warnings in the
-configuration.</p>
-</li>
-<li class="stepexpand"><span>Select <strong>File > Save All</strong></span></li>
-<li class="stepexpand"><span>Define the views for the method configuration. A view is a navigation
-tree browser in a published configuration. Every published configuration can
-have several views that are displayed as stacked tree browser tabs. The structure
-of the view is defined as a Custom Category.</span><ol type="a"><li><span>In the Configuration Editor, click the <strong>Views</strong> tab.</span></li>
-<li><span>Click the <strong>Add View</strong> button. The Select Categories dialog
-appears.</span></li>
-<li><span>If needed, click the (+) sign to expand the Custom Categories
-folder and then select the category you want to use as your view. Click the
-(+) sign to expand your chosen category and view it's contents. Press and
-hold the CTRL key to select multiple views.</span></li>
-<li><span>Click <strong>OK</strong>. The dialog window disappears and the views
-you selected are added to the Configuration.</span></li>
-</ol>
-</li>
-<li class="stepexpand"><span>Select the view you want to display as your configuration's start-up
-view and then click the <strong>Make Default</strong> button. The start-up view is the
-first view shown when a published configuration is displayed for the first
-time.</span></li>
-<li class="stepexpand"><span>Click <strong>File > Save all</strong> to save your configuration.</span></li>
-</ol>
-<div class="section"><strong>To create a method configuration by copying an existing configuration</strong>:<ol><li>Make sure you are working in the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>.<p></p>
-</li>
-<li>In the <a href="libraryview.html#libraryview">Library View</a>,
-expand the Configurations folder.<p></p>
-</li>
-<li> Right click the method configuration you want to copy and then click <strong>Copy</strong>.<p></p>
-</li>
-<li>Right click the <strong>Configurations</strong> folder and then click <strong>Paste</strong>.
-Type a name for the new configuration in the pop-up window. The copied method
-configuration is pasted into the Configurations folder.<p></p>
-</li>
-<li>Double click the newly pasted method configuration to open its configuration
-editor.<p></p>
-</li>
-<li>Follow steps 3 through 10 in <strong>To Create a New Method Configuration from
-Scratch</strong> above to continue.</li>
-</ol>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="methodconfigurations.html">Method Configuration</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodconfigurations.html#methodconfigurations">Method Configuration</a></div>
-<div><a href="methodplugin.html">Method Plug-in</a></div>
-<div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createamethodplugin.html">Create a Method Plug-in</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodplugin.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodplugin.html
deleted file mode 100644
index 48d6232..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodplugin.html
+++ /dev/null
@@ -1,78 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Method Plug-in" />
-<meta name="DC.Relation" scheme="URI" content="methodplugin.html#methodplugin" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" />
-<meta name="DC.Relation" scheme="URI" content="createacontentpackage.html#createcontentpackage" />
-<meta name="DC.Relation" scheme="URI" content="methodplugin.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createamethodplugin" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Method Plug-in</title>
-</head>
-<body id="createamethodplugin"><a name="createamethodplugin"><!-- --></a>
-
-<h1 class="topictitle1">Create a Method Plug-in</h1>
-<div><div class="p"><p>Method Plug-ins allow the extension or customization of base library
-content without directly changing that base content by defining the differences
-to the content. You should always create new content in a method plug-in that
-you produce to separate your content from the original OpenUP/Basic content. This
-also allows you to update your own library with new releases of the OpenUP/Basic Method
-Library without affecting the content that you have created in your own plug-ins.</p>
-<div class="note"><span class="notetitle">Note:</span> Plug-ins
-that are shipped with Eclipse Process Framework Composer are locked and read-only.
-These plug-ins are grayed out in the <a href="libraryview.html#libraryview">Library View</a>, indicating that they are locked.</div>
-</div>
-<div class="section">To create a new Method Plug-in:</div>
-<ol><li class="stepexpand"><span>Make sure you are in the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>.</span></li>
-<li class="stepexpand"><span>You can begin the method plug-in creation process in one of two
-ways:</span><ul><li>Click <strong>File > New > Method Plug-in</strong>. Or,</li>
-<li>In the Library view, right click an existing plug-in and select <strong>New
-Method Plug-in</strong>.</li>
-</ul>
- The New Method Plug-in wizard opens.</li>
-<li class="stepexpand"><span>Type a name for your new plug-in in the <strong>Name</strong> field and then
-select a plugin in the <strong>Referenced Plug-ins</strong> field. The plug-in you create
-extends the plug-in you select from the list and allows you to use content
-from the selected plug-in as you create your own plug-in content.</span></li>
-<li class="stepexpand"><span>Provide a brief description of the plug-in and list its authors
-to help you and others keep track of the plug-ins in the library. You can
-return to edit this information at any time.</span></li>
-<li class="stepexpand"><span>Click <strong>Finish</strong>. Your new plug-in now appears in the <a href="libraryview.html#libraryview">Library View</a> with the other
-Method Plug-ins.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="methodplugin.html">Method Plug-in</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodplugin.html#methodplugin">Method Plug-in</a></div>
-<div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createacontentpackage.html#createcontentpackage">Create a Content Package</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodviewwithcustomcategories.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodviewwithcustomcategories.html
deleted file mode 100644
index 90eda5c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createamethodviewwithcustomcategories.html
+++ /dev/null
@@ -1,82 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Method View with Custom Categories" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Relation" scheme="URI" content="publishingoverview.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createamethodviewwithcustomcategories" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Method View with Custom Categories</title>
-</head>
-<body id="createamethodviewwithcustomcategories"><a name="createamethodviewwithcustomcategories"><!-- --></a>
-
-<h1 class="topictitle1">Create a Method View with Custom Categories</h1>
-<div><div class="section">Custom categories allow you to categorize content according to any
-scheme you want. Custom categories can then be used to compose publishable
-views, providing a means to organize method content prior to publishing.<p>To
-create a new custom category:</p>
-</div>
-<ol><li><span>Switch to the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>.</span></li>
-<li><span>Open the <strong>Method Content</strong> folder in the method plug-in where
-you want to create the custom category.</span></li>
-<li><span>Right click the Custom Categories folder and select <strong>New > Custom
-Category</strong>. The editor window opens.</span></li>
-<li><span>Provide descriptive information about the custom category in the
-fields available under the <strong>Description</strong> tab.</span></li>
-<li><span>Under the <strong>Assign</strong> tab, you can select the things you want
-to include in the custom category. Select individual method elements, processes,
-standard categories or custom categories. The custom category
-is also available to add to individual elements on the <strong>Categories</strong> tab
-in the appropriate editor.</span></li>
-<li><span>Once you assign content to the custom category, you can modify
-the sequence of the items in the category. This affects the sequence of the
-items in the <a href="libraryview.html#libraryview">Library View</a> and <a href="configurationview.html#configurationview">Configuration View</a>, as
-well as in a published Web site if the custom category is included as a view
-in a configuration.</span></li>
-<li><span>To save your new custom category, click <strong>File > Save</strong> or close
-the editor and click <strong>Yes</strong> when prompted to save the changes.</span></li>
-</ol>
-<div class="section">You can now use the custom category as a view in a published configuration.<ol><li>Switch to the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>.</li>
-<li>In the <a href="libraryview.html#libraryview">Library View</a>,
-double click the configuration to which you want to add a view. The configuration
-editor opens.</li>
-<li>Click the <strong>Views</strong> tab and then click the <strong>Add View</strong> button.
-The Select Categories dialog appears. The Select Categories dialog displays
-all the standard and custom categories in the configuration.</li>
-<li>Select one or more categories to include as a view in your configuration
-and then click <strong>OK</strong>. The view display provides a preview of how the view
-will appear n the published tree browser.</li>
-<li>Select a view to display as the default start-up view in the published
-Web site, and then click the <strong>Make Default</strong> button.</li>
-<li>To save the configuration, click <strong>File > Save</strong> or close the configuration
-editor and click <strong>Yes</strong> when prompted to save the changes.</li>
-</ol>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-<div><a href="publishingoverview.html">Publishing Overview</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createareusablecapabilitypattern.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createareusablecapabilitypattern.html
deleted file mode 100644
index 539d364..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createareusablecapabilitypattern.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Reusable Capability Pattern" />
-<meta name="DC.Relation" scheme="URI" content="process.html#process" />
-<meta name="DC.Relation" scheme="URI" content="processauthoringoverview.html#processauthoringoverview" />
-<meta name="DC.Relation" scheme="URI" content="createadeliveryprocess.html#createadeliveryprocess" />
-<meta name="DC.Relation" scheme="URI" content="capabilitypattern.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createareusablecapabilitypattern" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Reusable Capability Pattern</title>
-</head>
-<body id="createareusablecapabilitypattern"><a name="createareusablecapabilitypattern"><!-- --></a>
-
-<h1 class="topictitle1">Create a Reusable Capability Pattern</h1>
-<div><div class="p"><p>A Capability pattern is a special process that describes a reusable
-cluster of activities in a general process area that provides a consistent
-development approach to common problems. Capability patterns can be used as
-building blocks to assemble delivery processes or larger capability patterns. </p>
-Before
-creating a capability pattern:<ul><li>Select a method plug-in to hold your process. For more information, see <a href="methodplugin.html#methodplugin">Method Plug-in</a>.</li>
-<li>Find or create a process package.</li>
-</ul>
-</div>
-<div class="section">A capability pattern does not relate to any specific phase or iteration
-of a development lifecycle, and should not imply any. In other words, a capability
-pattern should be designed in a way so that it is applicable anywhere in a
-delivery process. This enables the pattern's activities to be flexibly assigned
-to whatever phases there are in the delivery process to which it is being
-applied. For more information see <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a>.<div class="p">You do not need to develop your process from scratch;
-you can reuse existing capability patterns or even capability pattern parts.
-There are several ways to populate a process with method elements:<ul><li>By incorporating individual method elements by dragging the elements onto
-an activity in the process.</li>
-<li>By including already defined capability patterns.</li>
-<li>By including parts of already defined capability patterns.</li>
-<li>By creating descriptors directly in the process, which are either unrelated
-to any method content or related to method content at a later point in time.</li>
-</ul>
-</div>
-<p> To create a capability pattern:</p>
-</div>
-<ol><li class="stepexpand"><span>Once you have selected or created a process package, right click
-the <strong>Process Package</strong>.</span></li>
-<li class="stepexpand"><span>Click <strong>New –> Capability Pattern</strong>. The New Process Component
-dialog box appears.</span></li>
-<li class="stepexpand"><span>Type a name for the capability pattern into the <strong>Name</strong> field
-and then select a default configuration from the drop down list.</span></li>
-<li class="stepexpand"><span>Click <strong>OK</strong>. The process is created and the process editor
-is opened.</span></li>
-<li class="stepexpand"><span>In the process editor, under the Description tab, document your
-process using the available text fields.</span> <div class="note"><span class="notetitle">Note:</span> You can use the
-Rich Text Editor to edit or enter the text for any field that has a twisty
-symbol <img src="twisty symbol1.JPG" alt="" />. Simply click
-the symbol to access the Rich Text Editor. Click the symbol again to close
-the Rich Text Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a></div>
-</li>
-<li class="stepexpand"><span>Decide on your primary process authoring view. You develop a process
-using three different views: </span><ul><li><strong>Work Breakdown Structure</strong>: Define a work breakdown structure
-in your process. Create iterations and activities first, and then populate
-your activities by applying tasks from your method content. For more information
-see <a href="developaworkbreakdownstructure.html#developaworkbreakdownstructure">Develop a Work Breakdown Structure</a>.</li>
-<li><strong>Team Allocation</strong>: Define which teams and roles shall participate
-in activities and then find responsible work products and tasks from there.
-For more information, see <a href="developateamallocationstructure.html">Develop a Team Allocation Structure</a>.</li>
-<li><strong>Work Product Usage</strong>: Define which work products should be created
-in activities and find tasks and roles from there. For more information see <a href="developaworkproductusagestructure.html#developaworkproductusagestructure">Develop a Work Product Usage Structure</a>.</li>
-</ul>
- <p>Once you have created your capability pattern, you need to apply
-it. For more information, please see <a href="applyacapabilitypattern.html#applyacapabilitypattern">Apply a Capability Pattern</a>.</p>
-</li>
-</ol>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="capabilitypattern.html">Capability Pattern</a></strong><br />
-</li>
-</ul>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="process.html#process">Process</a></div>
-<div><a href="processauthoringoverview.html#processauthoringoverview">Process Authoring Overview</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createadeliveryprocess.html#createadeliveryprocess">Create a Delivery Process</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createarole.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createarole.html
deleted file mode 100644
index 6ea6901..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createarole.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Role" />
-<meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html#createatask" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html#createguidance" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createarole" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Role</title>
-</head>
-<body id="createarole"><a name="createarole"><!-- --></a>
-
-<h1 class="topictitle1">Create a Role</h1>
-<div><div class="p"><p>A <span class="keyword">Role</span> defines a set of related skills, competencies,
-and responsibilities of an individual or individuals.</p>
-You should always
-create new method content in a <a href="methodplugin.html#methodplugin">Method Plug-in</a> that you produce.</div>
-<div class="section">To create a role:</div>
-<ol><li class="stepexpand"><span>Expand the content package in which you want to create the role.</span></li>
-<li class="stepexpand"><span>Right click <strong>Roles</strong>, and then select <strong>New > Role</strong>. The
-role editor appears with the Description tab set as the default.</span></li>
-<li class="stepexpand"><span>In the Name field, type a unique name for your role. The role name
-is the file name that appears in the Library view.</span></li>
-<li class="stepexpand"><span>In the Presentation name field, type a presentation name. The presentation
-name is the name that appears in your published content and in the <a href="configurationview.html#configurationview">Configuration View</a>. You can also make this name appear in the <a href="libraryview.html#libraryview">Library View</a> by toggling the <strong>Show Presentation Names</strong> button
-in the Library View toolbar.</span></li>
-<li class="stepexpand"><span>In the Brief Description field, type a short description of the
-new Role. </span></li>
-<li class="stepexpand"><span>Type a more detailed description of the new Role in the Main Description
-field. The main description is a more detailed version of the description
-you typed into the Brief Description field. There are three ways you can create
-text for the description:</span> <ul><li>Directly, by typing it manually in the editor.</li>
-<li>Copy from another similar role and then modify by using the editor.</li>
-<li>Copy from an HTML source such as a published OpenUP/Basic Web site.</li>
-</ul>
-<div class="note"><span class="notetitle">Note:</span> You can use the Rich Text Editor to edit or enter the text for
-any field that has a twisty symbol <img src="collapsed.gif" alt="" />. Simply click the symbol to access the Rich Text Editor. Click the
-symbol again to close the Rich Text Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a>.</div>
-</li>
-<li class="stepexpand"><span>Under Version Information, provide any pertinent version information
-about the role.</span></li>
-<li class="stepexpand"><span>Click the <strong>Work Products</strong> tab and then click the <strong>Add</strong> button
-to the right of the "Role is responsible for:" field. The Select Dialog for
-Work Products dialog opens.</span></li>
-<li class="stepexpand"><span>Select one or more work products from the list. A description of
-the work product you select appears in the Brief Description field at the
-bottom of the dialog box.</span> <div class="note"><span class="notetitle">Note:</span> The list of work products in the
-"Work products that are output of tasks that this role performs" field is
-calculated and cannot be changed with the role editor. A work product appears
-here if it is an output of a task that the role performs.</div>
-</li>
-<li class="stepexpand"><span>Click <strong>OK</strong>. The dialog box closes and the "Role is responsible
-for:" field is populated.</span> <div class="note"><span class="notetitle">Note:</span> Selected elements in an Add/Remove
-section display both the element name (plug-in name) and the "path" (package
-name) to that element.</div>
-</li>
-<li class="stepexpand"><span>Click the <strong>Guidance</strong> tab. This part of the editor allows you
-to add and remove guidance for the role. To add guidance, click the <strong>Add</strong> button,
-select the guidance you want to add, and then click <strong>OK</strong>. To remove guidance,
-select it in the Guidance field and then click <strong>Remove</strong>. When you select
-a guidance element, the brief description of the guidance is displayed.</span></li>
-<li class="stepexpand"><span>Click the <strong>Categories</strong> tab. A role can be included in one
-or more rolesets and any number of custom categories. Open the appropriate
-Select dialog by clicking the <strong>Add</strong> button next to the category lists.
-You can remove a role from a category by selecting it and then clicking the <strong>Remove</strong> button.</span></li>
-<li class="stepexpand"><span>Click the <strong>Preview</strong> tab to view the newly created
-role and then save by closing the tab.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-
-<div class="linklist">
-<div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div>
-<div><a href="createatask.html#createatask">Create a Task</a></div>
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-<div><a href="createguidance.html#createguidance">Create Guidance</a></div>
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div></div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createatask.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createatask.html
deleted file mode 100644
index 712e204..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createatask.html
+++ /dev/null
@@ -1,137 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Task" />
-<meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html#createarole" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html#createguidance" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createatask" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Task</title>
-</head>
-<body id="createatask"><a name="createatask"><!-- --></a>
-
-<h1 class="topictitle1">Create a Task</h1>
-<div><div class="p"><p>A task is an assignable unit of work. Every task is assigned to
-a specific role. The granularity of a task is generally a few hours to a few
-days and usually affects one or only a small umber of work products.</p>
-You
-should always create new method content in a <a href="methodplugin.html#methodplugin">Method Plug-in</a> that you produce. </div>
-<div class="section">To create a task:</div>
-<ol><li class="stepexpand"><span>Expand the content package in which you want to create the task.</span></li>
-<li class="stepexpand"><span>Right click <strong>Tasks</strong>, and then select <strong>New > Task</strong>. The
-task editor appears with the <strong>Description</strong> tab set as the default.</span></li>
-<li class="stepexpand"><span>In the Name field, type a unique name for your task. the task name
-is the file name that appears in the <a href="libraryview.html#libraryview">Library View</a>.</span></li>
-<li class="stepexpand"><span>In the Presentation name field, type a presentation name. The presentation
-name is the name that appears in your published content and in the <a href="configurationview.html">Configuration View</a>.
-You can also make this name appear in the Library view by toggling the <strong>Show
-Presentation Names</strong> button in the Library view toolbar.</span> </li>
-<li class="stepexpand"><span>In the Brief Description field, type a short description of the
-new task.</span></li>
-<li class="stepexpand"><span>Type a more detailed description of the new task in the Main Description
-field. The main description is a more detailed version of the description
-you typed into the Brief Description field. There are three ways you can create
-text for the description:</span> <ul><li>Directly, by typing it manually in the editor.</li>
-<li>Copy from another similar role and then modify by using the editor.</li>
-<li>Copy from an HTML source such as a published OpenUP/Basic Web site.</li>
-</ul>
-<div class="note"><span class="notetitle">Note:</span> You can use the Rich Text Editor to edit or enter the text for
-any field that has a twisty symbol <img src="collapsed.gif" alt="" />. Simply click the symbol to access the Rich Text Editor. Click the
-symbol again to close the Rich Text Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a>.</div>
-</li>
-<li class="stepexpand"><span>Complete the other task specific fields in Detail Information as
-needed. See <a href="variability.html#variability">Variability</a> for
-information on creating variability. </span></li>
-<li class="stepexpand"><span>Click the <strong>Steps</strong> tab. The Steps Editor appears.</span> <div class="p">A
-task can have a series of steps that detail how to perform that task. The
-Step Editor allows you to:<ul><li>Create a new step<ul><li>Click the <strong>New</strong> button.</li>
-<li>Give the Task a name in the <strong>Name</strong> field.</li>
-<li>Describe the Task in the <strong>Description</strong> field.</li>
-</ul>
-</li>
-<li>Remove a step<ul><li>Select the step to remove in the <strong>Steps</strong> field.</li>
-<li>Click the <strong>Delete</strong> button.</li>
-</ul>
-</li>
-<li>Move a step up the list<ul><li>Select the step you want to move up.</li>
-<li>Click the <strong>Move Up</strong> button.</li>
-</ul>
-</li>
-<li>Move a step down the list<ul><li>Select the step you want to move down.</li>
-<li>Click the <strong>Move Down</strong> button</li>
-</ul>
-</li>
-</ul>
-</div>
-</li>
-<li class="stepexpand"><span>Click the <strong>Roles</strong> tab. This part of the editor allows you
-to define the roles that perform the task. You should select a role as the
-Performing Role for this task. You can also add one or more roles as Additional
-Performers. To add a role, click the <strong>Select</strong> or <strong>Add</strong> button as
-appropriate, select the role you want to add, and then click <strong>OK</strong>. To
-remove a role, select it in the Guidance box, and then click <strong>Clear</strong> or <strong>Remove</strong> as
-appropriate. When you select a role the brief description of that role is
-displayed.</span></li>
-<li class="stepexpand"><span>Click the <strong>Work Products</strong> tab. This part of the editor allows
-you to define the work products that are inputs and outputs for this task.
-You can select any number of work products as Mandatory Inputs, Optional Inputs,
-and Outputs. To add a work product, click the appropriate <strong>Add</strong> button,
-select the work products you want to add, and then click <strong>OK</strong>. To remove
-a work product, select it in the appropriate box and then click the corresponding <strong>Remove</strong> button.
-When you select a work product the brief description of the work product is
-displayed.</span></li>
-<li class="stepexpand"><span>Click the <strong>Guidance</strong> tab. This part of the editor allows you
-to add and remove guidance for the task. To add guidance, click the <strong>Add</strong> button,
-select the guidance you want to add, and then click <strong>OK</strong>. To remove guidance,
-select it in the Guidance box and then click <strong>Remove</strong>. When you select
-a guidance element the brief description of the guidance is displayed.</span></li>
-<li class="stepexpand"><span>Click the <strong>Categories</strong> tab. A task can be included in one
-discipline and any number of custom categories. Open the Select dialog by
-clicking the appropriate <strong>Select</strong> or <strong>Add</strong> button next to the category
-lists. Select a single discipline or any number of custom categories, and
-then click <strong>OK</strong>. You can remove a task from a category by selecting it
-and then clicking the appropriate <strong>Remove</strong> button.</span></li>
-<li class="stepexpand"><span>Click the <strong>Preview</strong> tab to view the newly created task as
-it will appear in a published Web page, and then save by closing the tab.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div>
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createarole.html#createarole">Create a Role</a></div>
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-<div><a href="createguidance.html#createguidance">Create Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createaworkproduct.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createaworkproduct.html
deleted file mode 100644
index 5f74f91..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createaworkproduct.html
+++ /dev/null
@@ -1,122 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create a Work Product" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html#createarole" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html#createguidance" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createaworkproduct" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create a Work Product</title>
-</head>
-<body id="createaworkproduct"><a name="createaworkproduct"><!-- --></a>
-
-<h1 class="topictitle1">Create a Work Product</h1>
-<div><div class="p"><div class="p">Work product is a general term for task inputs and outputs. There
-are three types of work product:<ul><li><a href="artifact.html#artifact">Artifact</a></li>
-<li><a href="outcome.html#outcome">Outcome</a></li>
-<li><a href="deliverable.html#deliverable">Deliverable</a></li>
-</ul>
-</div>
-You should always create new method content in a <a href="methodplugin.html#methodplugin">Method Plug-in</a> that you produce.</div>
-<div class="section">To create a work product:</div>
-<ol><li class="stepexpand"><span>Expand the Content Package in which you want to create the work
-product.</span></li>
-<li class="stepexpand"><span>Right click <strong>Work Products</strong>, and then select one of the following:</span> <ul><li><strong>New > Artifact</strong></li>
-<li><strong>New > Outcome</strong></li>
-<li><strong>New > Deliverable</strong></li>
-</ul>
-The Work Product editor for the specific type of work product you are
-creating appears with the Description tab set as the default.</li>
-<li class="stepexpand"><span>In the Name field, type a unique name for your work product. The
-work product name is the file name that appears in the <a href="libraryview.html#libraryview">Library View</a>. </span></li>
-<li class="stepexpand"><span>In the Presentation name field, type a presentation name. the presentation
-name is the name that appears in your published content and in the <a href="configurationview.html#configurationview">Configuration View</a>. You can also make this name appear in the library
-view by toggling the <strong>Show Presentation Names</strong> button in the library
-view toolbar.</span></li>
-<li class="stepexpand"><span>In the Brief Description field, type a short description of the
-new work product.</span></li>
-<li class="stepexpand"><span>Type a more detailed description of the new work product in the
-Main Description field. The main description is a more detailed version of
-the description you typed into the Brief Description field. There are three
-ways to create text for the description:</span> <ul><li>Directly, by typing it manually in the editor.</li>
-<li>Copy from another similar work product and then modify using the editor.</li>
-<li>Copy from an HTML source, such as a published OpenUP/Basic Web site.</li>
-</ul>
-<div class="note"><span class="notetitle">Note:</span> You can use the Rich Text Editor to edit or enter the text for
-any field that has a twisty symbol <img src="collapsed.gif" alt="" />. Simply click the symbol to access the Rich Text Editor. Click the
-symbol again to close the Rich Text Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a>.</div>
-</li>
-<li class="stepexpand"><span>Under <strong>Notation</strong>, provide any notations about the Work Product.</span> <div class="note"><span class="notetitle">Note:</span> Artifacts and Deliverables contain the Notation fields, while
-Outcomes do not.</div>
-</li>
-<li class="stepexpand"><span>Under <strong>Icon</strong> you can select a node icon to appear with the
-work product in the Library and Configuration views and in the tree browser
-in a published Web site. The node icon should be 16 x 16 pixels. You can also
-select a Shape icon to appear at the top of the published Web page for the
-work product. the Shape icon should be 32 x 32 pixels.</span></li>
-<li class="stepexpand"><span>Complete the other work product specific fields as needed. See <a href="variability.html#variability">Variability</a> for information
-on adding variability to your work product.</span></li>
-<li class="stepexpand"><span>Select the <strong>Guidance</strong> tab. This part of the editor allows
-you to add and remove guidance for the work product. To add guidance, click
-the <strong>Add</strong> button, select the guidance you want to add, and then click <strong>OK</strong>.
-To remove guidance, select it in the Guidance field, and then click <strong>Remove</strong>.
-When you select a guidance element the brief description of the guidance is
-displayed.</span></li>
-<li class="stepexpand"><span>Select the <strong>Categories</strong> tab. A work product can be included
-in one domain, any number of work product types, and any number of custom
-categories. Open the appropriate Select dialog by clicking the <strong>Select</strong> or <strong>Add</strong> button
-next to the category lists. Select a single domain or any number of work product
-kinds or custom categories and then click <strong>OK</strong>. You can remove a work
-product from a category by selecting it and then clicking the appropriate <strong>Remove</strong> button.</span></li>
-<li class="stepexpand"><span>If the work product is a deliverable, you can define what the deliverable
-consists of on the Deliverable Parts tab. Click the <strong>Deliverable Parts</strong> tab.
-This part of the editor only appears for deliverables and it allows you to
-add other work products as part of the deliverable. To add work products,
-click the <strong>Add</strong> button, select the work products you want to add, and
-then click <strong>OK</strong>. To remove a work product, select it in the work products
-as deliverable parts: field, and then click <strong>Remove</strong>. When you select
-a work product the brief description of the work product is displayed.</span></li>
-<li class="stepexpand"><span>Select the <strong>Preview</strong> tab to view the newly created work product,
-and then save by closing the tab.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-<div><a href="createarole.html#createarole">Create a Role</a></div>
-<div><a href="createatask.html">Create a Task</a></div>
-<div><a href="createguidance.html#createguidance">Create Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createguidance.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createguidance.html
deleted file mode 100644
index e9f3308..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createguidance.html
+++ /dev/null
@@ -1,102 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create Guidance" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createguidance" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create Guidance</title>
-</head>
-<body id="createguidance"><a name="createguidance"><!-- --></a>
-
-<h1 class="topictitle1">Create Guidance</h1>
-<div><div class="p"><p>Guidance is a general term for additional information related to <a href="role.html#role">Role</a>, <a href="task.html#task">Task</a>, and <a href="workproduct.html">Work Product</a>. Guidance
-provides information on how to perform your role, how to create a work product,
-how to perform your task, and so on. For more information see <a href="guidance.html#guidance">Guidance</a>.</p>
-<p>You should always create new <a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a> in a <a href="methodplugin.html#methodplugin">Method Plug-in</a> that
-you produce.</p>
-</div>
-<div class="section"><p>To create<strong>Guidance</strong>:</p>
-</div>
-<ol><li class="stepexpand"><span>Expand the Content Package in which you want to create Guidance
-until you see the Method Elements (Roles, Tasks, Work Products, Guidance).</span></li>
-<li class="stepexpand"><span>Right click <strong>Guidance</strong> and then click <strong>New > "guidance type"</strong>.
-The guidance editor for that particular guidance type opens. </span> <div class="p">The
-following guidance types have the same editor which includes a Description
-tab and a Preview tab:<ul><li><a href="concept.html#concept">Concept</a></li>
-<li><a href="example.html#example">Example</a></li>
-<li><a href="guideline.html#guideline">Guideline</a></li>
-<li><a href="report.html#report">Report</a></li>
-<li><a href="reusableasset.html#reusableasset">Reusable Asset</a></li>
-<li><a href="roadmap.html#roadmap">Roadmap</a></li>
-<li><a href="supportingmaterial.html">Supporting Material</a></li>
-<li><a href="termdefinition.html#termdefinition">Term Definition</a></li>
-<li><a href="toolmentor.html#toolmentor">Tool Mentor</a></li>
-<li><a href="whitepaper.html#whitepaper">Whitepaper</a></li>
-</ul>
-</div>
-</li>
-<li class="stepexpand"><span>Use the fields in the content element editor to specify the guidance
-details. Start by assigning a unique name to the guidance element along with
-a presentation name that is used as the external visible name when other elements
-refer to this element, or when the element is published. Every guidance type
-has specific content fields in the content editor that are distributed over
-two or more stacked tabs. Use the content fields to describe your guidance
-type.</span> <div class="note"><span class="notetitle">Note:</span> You can use the Rich Text Editor to edit or enter
-the text for any field that has a twisty symbol <img src="collapsed.gif" alt="" />. Simply click the symbol to access the Rich Text Editor.
-Click the symbol again to close the Rich Text Editor. For more information
-see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a>.</div>
-</li>
-<li class="stepexpand"><span>In the Icon section, select a Node icon to appear with the work
-product in the <a href="libraryview.html#libraryview">Library View</a> and <a href="configurationview.html#configurationview">Configuration View</a> and
-in the tree browser in a published Web site. The node icon should be 16 x
-16 pixels. You can also select a Shape icon to appear at the top of the published
-page for the work product. The shape icon should be 32 x 32 pixels.</span></li>
-<li class="stepexpand"><span>Select the <strong>Preview</strong> tab to view the newly created work product
-and then save by closing the tab.</span></li>
-</ol>
-<div class="section">It is possible to change the types of some types of guidance to a
-limited number of other guidance types. To change a guidance type, click the <strong>Change
-Type</strong> button and select an available new type.<p>If the type of guidance
-is a <a href="practice.html#practice">Practice</a>, you can add
-references to other elements. If the guidance is a <a href="template.html">Template</a>,
-you can attach a file to the guidance.</p>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-<div><a href="createarole.html">Create a Role</a></div>
-<div><a href="createatask.html">Create a Task</a></div>
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/createmethodcontent.html b/1.5/plugins/org.eclipse.epf.help.doc/html/createmethodcontent.html
deleted file mode 100644
index a1f26fd..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/createmethodcontent.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Create Method Content" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html#createarole" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html#createatask" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html#createguidance" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html" />
-<meta name="DC.Relation" scheme="URI" content="variability.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="createmethodcontent" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Create Method Content</title>
-</head>
-<body id="createmethodcontent"><a name="createmethodcontent"><!-- --></a>
-
-<h1 class="topictitle1">Create Method Content</h1>
-<div><div class="p"><p>Method content provides step-by-step explanations,
-describing how specific development goals are achieved independent of the
-placement of these steps within a development lifecycle. Processes take the
-method elements and relate them into semi-ordered sequences that are customized
-to specific types of projects.</p>
-<p>Method content elements are:</p>
-<ul><li><a href="task.html#task">Task</a></li>
-<li><a href="role.html#role">Role</a></li>
-<li><a href="workproduct.html#workproduct">Work Product</a></li>
-<li><a href="guidance.html">Guidance</a></li>
-</ul>
-Click here for more information about <a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a>.</div>
-<div class="section">To create method content:</div>
-<ol><li class="stepexpand"><span>In the <a href="libraryview.html#libraryview">Library View</a>,
-expand the content package in which you want to create new method content.</span></li>
-<li class="stepexpand"><span>Right click the folder containing the type of method element you
-want to create, click <strong>New</strong> and then select the element that appears.
-The new element is created and its respective editor opens.</span> <div class="note"><span class="notetitle">Note:</span> For
-Work Products, choose between Artifact, Outcome, or Deliverable. For Guidance,
-choose from the list of guidance types.</div>
-</li>
-</ol>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="createarole.html">Create a Role</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="createatask.html">Create a Task</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="createaworkproduct.html">Create a Work Product</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="createguidance.html">Create Guidance</a></strong><br />
-</li>
-<li class="ulchildlink"><strong><a href="variability.html">Variability</a></strong><br />
-Variability allows elements in one content package to influence
-or modify elements in other content packages without actually directly modifying
-the original content. Variability enables changes to the content while keeping
-the changes separate and optional.</li>
-</ul>
-
-<div class="linklist">
-<div><a href="createarole.html#createarole">Create a Role</a></div>
-<div><a href="createatask.html#createatask">Create a Task</a></div>
-<div><a href="createaworkproduct.html">Create a Work Product</a></div>
-<div><a href="createguidance.html#createguidance">Create Guidance</a></div></div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/cut.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/cut.gif
deleted file mode 100644
index 0cf11d4..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/cut.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/deliverable.html b/1.5/plugins/org.eclipse.epf.help.doc/html/deliverable.html
deleted file mode 100644
index 23b266e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/deliverable.html
+++ /dev/null
@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Deliverable" />
-<meta name="DC.Relation" scheme="URI" content="workproduct.html#workproduct" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Relation" scheme="URI" content="artifact.html#artifact" />
-<meta name="DC.Relation" scheme="URI" content="outcome.html#outcome" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="deliverable" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Deliverable</title>
-</head>
-<body id="deliverable"><a name="deliverable"><!-- --></a>
-
-<h1 class="topictitle1">Deliverable</h1>
-<div><p>A deliverable is a collection of work products, usually artifacts. A deliverable
-is used to pre-define typical or recommended content in the form of work products
-packaged for delivery. Deliverables are used to represent an output from a
-process that has value, material or otherwise, to a client, customer, or other
-stakeholder.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="workproduct.html#workproduct">Work Product</a></div>
-<div><a href="artifact.html#artifact">Artifact</a></div>
-<div><a href="outcome.html#outcome">Outcome</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/deliveryprocess.html b/1.5/plugins/org.eclipse.epf.help.doc/html/deliveryprocess.html
deleted file mode 100644
index 0d5e9ba..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/deliveryprocess.html
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Delivery Process" />
-<meta name="DC.Relation" scheme="URI" content="createadeliveryprocess.html#createadeliveryprocess" />
-<meta name="DC.Relation" scheme="URI" content="createadeliveryprocess.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="deliveryprocess" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Delivery Process</title>
-</head>
-<body id="deliveryprocess"><a name="deliveryprocess"><!-- --></a>
-
-<h1 class="topictitle1">Delivery Process</h1>
-<div><p>A Delivery Process is the process that covers a whole development lifecycle
-from beginning to end. A Delivery Process can be used as a template for planning
-and running a project. It provides a complete lifecycle model with predefined
-phases, iterations, and activities.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="createadeliveryprocess.html">Create a Delivery Process</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createadeliveryprocess.html#createadeliveryprocess">Create a Delivery Process</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/developateamallocationstructure.html b/1.5/plugins/org.eclipse.epf.help.doc/html/developateamallocationstructure.html
deleted file mode 100644
index 7123a93..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/developateamallocationstructure.html
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Develop a Team Allocation Structure" />
-<meta name="DC.Relation" scheme="URI" content="developaworkbreakdownstructure.html#developaworkbreakdownstructure" />
-<meta name="DC.Relation" scheme="URI" content="developaworkproductusagestructure.html#developaworkproductusagestructure" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="developateamallocationstructure" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Develop a Team Allocation Structure</title>
-</head>
-<body id="developateamallocationstructure"><a name="developateamallocationstructure"><!-- --></a>
-
-<h1 class="topictitle1">Develop a Team Allocation Structure</h1>
-<div><div class="p">In the Team Allocation view, you can create a process by defining
-which roles participate in activities and find responsible work products and
-tasks from there. You can also review the roles in a process that has been
-created by adding tasks or work products to the process. Before you create
-a team allocation structure, ensure the configuration selected in the tool
-bar is the same as the configuration you selected as the default configuration
-for your process.</div>
-<div class="section">To develop a team allocation structure:</div>
-<ol><li class="stepexpand"><span>To access the team allocation editor, select the <strong>Team Allocation</strong> tab
-in the process editor.</span> <div class="note"><span class="notetitle">Note:</span> For the purposes of this topic, the
-breakdown element example used is <a href="activity.html#activity">Activity</a>.
-Other breakdown elements include (but are not limited to) <a href="phase.html#phase">Phase</a> and <a href="iteration.html#iteration">Iteration</a>.
-The element you use depends on the scope of the process you create.</div>
-</li>
-<li class="stepexpand"><span>Right click the element (either a <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a> or <a href="deliveryprocess.html#deliveryprocess">Delivery Process</a>) to which you want to add structure, and then click <strong>New
-Child > Activity</strong> to create a new activity. If needed, create more activities
-to set up your breakdown structure. Activities (as well as phases and iterations)
-can be nested inside each other according to how each relates in the hierarchy.
-You can add roles directly to your activities.</span></li>
-<li class="stepexpand"><span>In the Configuration view, review the list of roles. In this view,
-tasks are sorted by role sets.</span></li>
-<li class="stepexpand"><span>Drill into the role sets hierarchy to see which roles are available
-in this configuration.</span></li>
-<li class="stepexpand"><span>Select a role and drag it on top of the appropriate activity. The
-role is added as a role descriptor. If the role is responsible for work products
-in the configuration's method content, a wizard appears prompting you to add
-work products.</span></li>
-<li class="stepexpand"><span>Select one or more work products and then click <strong>OK</strong>. For
-each selected work product the next wizard window prompts you to select tasks
-that produce these work products. Again, select one or more tasks and then
-click <strong>OK</strong> to add these elements to your process.</span></li>
-<li class="stepexpand"><span>Review the role descriptor's details in its properties view. If
-the properties view is not displayed, in the work breakdown structure editor,
-right click the role and then select <strong>Properties</strong>. Use the tabs on the
-side of the properties view to review different aspects of the role descriptor.
-In the properties view, you can also perform individual modifications of the
-role descriptor, such as change the presentation name, add textual descriptions,
-change work products the role is responsible for, and more. When changing
-the task descriptor's relationships under the roles or work products tabs,
-you can add new elements from your method content by clicking the <strong>Add...</strong> button,
-or connect your task descriptor with tasks already present in this activity.
-For more information, see <a href="processelementpropertiesview.html#processelementpropertiesview">Process Element Properties View</a></span></li>
-<li class="stepexpand"><span>Continue adding roles to your activities.</span></li>
-</ol>
-<div class="section">You can preview what your process will look like in a published Web
-site at any time by switching to the <a href="browsingperspective.html#browingperspective">Browsing Perspective</a> and then selecting the process, or an activity in the
-process, in the <a href="configurationview.html">Configuration View</a>. You can use the
-links on the page to navigate through the process. Switch back to the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a> to
-continue editing your process.</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="developaworkbreakdownstructure.html#developaworkbreakdownstructure">Develop a Work Breakdown Structure</a></div>
-<div><a href="developaworkproductusagestructure.html#developaworkproductusagestructure">Develop a Work Product Usage Structure</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkbreakdownstructure.html b/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkbreakdownstructure.html
deleted file mode 100644
index 8747eb0..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkbreakdownstructure.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Develop a Work Breakdown Structure" />
-<meta name="DC.Relation" scheme="URI" content="developateamallocationstructure.html#developateamallocationstructure" />
-<meta name="DC.Relation" scheme="URI" content="developaworkproductusagestructure.html#developaworkproductusagestructure" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="developaworkbreakdownstructure" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Develop a Work Breakdown Structure</title>
-</head>
-<body id="developaworkbreakdownstructure"><a name="developaworkbreakdownstructure"><!-- --></a>
-
-<h1 class="topictitle1">Develop a Work Breakdown Structure</h1>
-<div><div class="p">A work breakdown structure is a hierarchical breakdown of work, such
-as activities, tasks, and steps, defining a process. <p>Before creating a
-work breakdown structure, be sure that the configuration selected in the tool
-bar is the same as the configuration selected as the default configuration
-for your process.</p>
-</div>
-<div class="section">To develop a work breakdown structure:</div>
-<ol><li class="stepexpand"><span>To access the work breakdown structure editor, select the <strong>Work
-Breakdown Structure</strong> tab in a process editor.</span> <div class="note"><span class="notetitle">Note:</span> A breakdown
-structure is created with breakdown elements. Examples of breakdown elements
-are <a href="phase.html#phase">Phase</a>, <a href="iteration.html#iteration">Iteration</a>, <a href="activity.html#activity">Activity</a>,
-or task descriptor. Typically, a process is created by defining
-its phases and iterations within or across these phases. Phases and iterations
-are then further broken down into levels of activities. Finally, you can populate
-a work breakdown structure's activity with task descriptors.</div>
-</li>
-<li class="stepexpand"><span>Right click the element (either a <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a> or <a href="deliveryprocess.html#deliveryprocess">Delivery Process</a>) to which you want to add structure, and then click <strong>New
-Child > Activity</strong> to create the new activity. If needed, create more activities
-to set up your breakdown structure. Activities (as well as phases and iterations)
-can be nested inside each other according to how each relates in the hierarchy.</span></li>
-<li class="stepexpand"><span>Right click the activity and then select <strong>Properties</strong> to open
-the Properties view. Complete the information under the Documentation tab
-for the activity. This information appears in the published Web page for the
-activity.</span></li>
-<li class="stepexpand"><span>Review the list of tasks in the configuration view to see which
-tasks are available.</span></li>
-<li class="stepexpand"><span>Select a task to add to the breakdown structure and then drag it
-on top of the activity to which you want it to belong. The task is added as
-a task descriptor to that activity.</span></li>
-<li class="stepexpand"><span>If the properties view for the activity is not displayed, select
-the task in the work breakdown structure editor, right click, and then select <strong>Properties</strong>.
-Click the <strong>Documentation</strong> tab and then complete the information required
-under this tab. This information appears in the published Web page for the
-activity. Use the tabs on the side of the properties view to review different
-aspects of the task descriptor. In the properties view, you can perform individual
-modifications of the task descriptor, such as change the presentation name,
-add textual descriptions, and change performing roles, among others. When
-changing the task descriptor's relationships under the roles or work products
-tabs, you can add new elements from your method content by clicking the <strong>Add...</strong> button,
-or connect your task descriptor with tasks already present in this activity.
-For more information, see <a href="processelementpropertiesview.html#processelementpropertiesview">Process Element Properties View</a>.</span></li>
-<li class="stepexpand"><span>Continue adding tasks to the activity or activities.</span></li>
-</ol>
-<div class="section">You can preview what your process will look like in a published Web
-site at any time by switching to the <a href="browsingperspective.html#browingperspective">Browsing Perspective</a> and then selecting the process, or an activity in the
-process, in the <a href="configurationview.html">Configuration View</a>. You can use the
-links on the page to navigate through the process. Switch back to the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a> to
-continue editing your process.</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="developateamallocationstructure.html#developateamallocationstructure">Develop a Team Allocation Structure</a></div>
-<div><a href="developaworkproductusagestructure.html#developaworkproductusagestructure">Develop a Work Product Usage Structure</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkproductusagestructure.html b/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkproductusagestructure.html
deleted file mode 100644
index c40a063..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/developaworkproductusagestructure.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Develop a Work Product Usage Structure" />
-<meta name="DC.Relation" scheme="URI" content="developaworkbreakdownstructure.html#developaworkbreakdownstructure" />
-<meta name="DC.Relation" scheme="URI" content="developateamallocationstructure.html#developateamallocationstructure" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="developaworkproductusagestructure" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Develop a Work Product Usage Structure</title>
-</head>
-<body id="developaworkproductusagestructure"><a name="developaworkproductusagestructure"><!-- --></a>
-
-<h1 class="topictitle1">Develop a Work Product Usage Structure</h1>
-<div><div class="p">In the Work Product Usage view, you can create a process by defining
-which work products will be created and used in the process, and then finding
-responsible roles and tasks from there. You can also review the work products
-in a process that has been created by adding tasks or roles to the process.<p>Before
-you create a work product usage structure, ensure the configuration selected
-in the tool bar is the same as the configuration you selected as the default
-configuration for your process.</p>
-</div>
-<div class="section">To develop a work product usage structure:</div>
-<ol><li class="stepexpand"><span>To access the work product usage editor, select the <strong>Work Product
-Usage</strong> tab in the process editor.</span> <div class="note"><span class="notetitle">Note:</span> For the purposes of
-this topic, the breakdown element example used is <a href="activity.html#activity">Activity</a>. Other breakdown elements include (but are not limited
-to) <a href="phase.html#phase">Phase</a> and <a href="iteration.html#iteration">Iteration</a>. The element you use depends on the scope of the process
-you create.</div>
-</li>
-<li class="stepexpand"><span>Right click the element (either a <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a> or <a href="deliveryprocess.html#deliveryprocess">Delivery Process</a>) to which you want to add structure, and then click <strong>New
-Child > Activity</strong> to create a new activity. If needed, create more activities
-to set up your breakdown structure. Activities (as well as phases and iterations)
-can be nested inside each other according to how each relates in the hierarchy.</span></li>
-<li class="stepexpand"><span>Review the list of work products in the <a href="configurationview.html#configurationview">Configuration View</a>. In this view, work products are sorted by domain as
-well as work product kinds. Drill into either of these hierarchies to see
-which work products are available in this configuration.</span></li>
-<li class="stepexpand"><span>Select a work product to add to activity and then drag it on top
-of the activity which you want it to belong. The work product is added as
-a work product descriptor to that activity. If the work product is an output
-to one or more tasks in the configuration, a wizard appears prompting you
-to add the task. </span> <div class="note"><span class="notetitle">Note:</span> It is not required to add a task. A valid
-process can contain just roles and work products.</div>
-</li>
-<li class="stepexpand"><span>Specify the entry and exit states of the work product for the activity
-to which it was added.</span></li>
-<li class="stepexpand"><span>Review the new work product descriptor details in the properties
-view. If the properties view is not displayed, right click the work product
-descriptor in the process editor, and then select <strong>Properties</strong>. Use the
-tabs on the side of the properties view to review different aspects of the
-work product descriptor. In the Properties view, you can also perform individual
-modifications of the role descriptor, such as change the presentation name,
-add textual descriptions, add entry and exit states, and more. When changing
-the role descriptor's relationships under the Roles or Work Products tabs,
-you can add new elements from your method content by clicking the <strong>Add...</strong> button,
-or connect your role descriptor with tasks already present in this activity.
-For more information, see <a href="processelementpropertiesview.html#processelementpropertiesview">Process Element Properties View</a>.</span></li>
-<li class="stepexpand"><span>Continue adding work products to your activities. </span></li>
-</ol>
-<div class="section">See also:</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="developaworkbreakdownstructure.html#developaworkbreakdownstructure">Develop a Work Breakdown Structure</a></div>
-<div><a href="developateamallocationstructure.html#developateamallocationstructure">Develop a Team Allocation Structure</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/differencesbetweenexistingandmigratedcontent.html b/1.5/plugins/org.eclipse.epf.help.doc/html/differencesbetweenexistingandmigratedcontent.html
deleted file mode 100644
index ee0b1b1..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/differencesbetweenexistingandmigratedcontent.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Differences Between IBM RUP 2003 and Migrated Content" />
-<meta name="DC.Relation" scheme="URI" content="migrationoverview.html#migrationoverview" />
-<meta name="DC.Relation" scheme="URI" content="migrateanrpw2003plugin.html#migrateanrpw2003plugin" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="differencesbetweenexistingandmigratedcontent" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Differences Between IBM RUP 2003 and Migrated Content</title>
-</head>
-<body id="differencesbetweenexistingandmigratedcontent"><a name="differencesbetweenexistingandmigratedcontent"><!-- --></a>
-
-<h1 class="topictitle1">Differences Between IBM RUP 2003 and Migrated Content</h1>
-<div><p>Eclipse Process Framework Composer content is based on IBM Unified
-Method Architecture.</p>
-<ul><li><strong>Activities have been renamed to task</strong>: To provide a tighter link
-to process enactment and project management we renamed the lowest assignable
-units of work to Task, because this is the term most commonly used.</li>
-<li><strong>Workflow details renamed to activity</strong>: Workflows are commonly expressed
-in hierarchies of activity diagrams (e.g. activity diagrams defined in the
-UML 2.0). Although RUP only provided one level of workflow breakdown, UMA
-is designed to provide multiple levels of such a breakdown. Because the word
-Activity was more commonly used to express the elements of activity diagrams
-as well as the activity diagram itself, we decided to replace the name Workflow
-Detail used in RUP with the name Activity. We realize that the shift in the
-usage of the word Activity might cause confusion with existing RUP users.
- However, one important goal of the UMA work was to use terms in the way they
-are most commonly used in standards and industry. </li>
-<li><strong>Tasks (former RUP Activities) can be performed by many roles</strong>:
-In RUP 2003 an activity was modeled as an operation of a role. Customer feedback,
-a look at other process modeling approaches, as well as changes introduced
-in UML 2.0 indicated that this was a too restrictive way of modeling human
-behavior. This approach did not allow expressing that some work was performed
-as a collaboration of different roles. UMA addresses this issue by making
-Task an independent model element to which performing roles can be assigned
-as resources. UMA therefore now allows several roles to be assigned to a
-task. For backward compatibility, it still allows a primary performing role
-to be identified (being responsible for the task) as well as several additional
-performers.</li>
-<li><strong>Refinement of the artifact concept</strong>: RUP only used the concept of
-artifact to define things that are used and produced in a development project.
- UMA defines an extended taxonomy for these concepts. It defines the general
-concept of work product, which has three different specializations (specific
-work product types): Artifacts (managed work products), Deliverables (packaged
-work products that will be delivered to a stakeholder for review), and Outcome
-(unmanaged, intangible work products).</li>
-<li><strong>Different categorizations for work products and roles</strong>: In RUP,
-artifacts and roles were all categorized by discipline. However, sometimes
-artifacts were used across disciplines and a categorization to only one discipline
-caused confusion. In UMA different categories have been defined for work
-definitions (discipline for tasks and activities), work products (domain and
-work product kind), and roles (role sets).</li>
-<li><strong>Process Components renamed to Method Package</strong>: The concept of component
-is commonly used in many standards and technologies. Most applications of
-component link it to the abstraction of encapsulation defining a component
-as a black box which can be used via well-defined interfaces. RUP component
-did not fulfill this black box criterion. Also the SPEM standard defined
-packages as well as components. To be compliant to SPEM and the industry usage
-of the word component, we renamed Process Component to Method Package ('method'
-because it can contain method elements or process elements)</li>
-<li><strong>Separation of method content elements from process elements</strong>: In
-RUP 2003 you created a new process by defining a new configuration and documenting
-manually in a development case artifact changes to standard RUP. UMA provides
-extended concepts in addition to the configuration concept for tailoring processes.
- It allows you to model concretely for a process what work defined in the
-method content you want to actually do in each phase, because you can easily
-add, remove, and reorder elements in the process structure, reusing or not
-reusing whatever you want from the method content. It achieves these features
-by a more clear separation of method content (e.g. tasks defined for disciplines)
-and the application of method content in process (expressed with activity
-diagrams and/or work breakdown structures) as well as the modeling of processes
-(i.e. creating new or adapted activity diagrams or new or adapted work breakdown
-structures). It introduces a few new concepts such as descriptor that support
-this separation and achieve new capabilities for maintaining and reusing many
-different families of alternative processes and process parts all within the
-same configuration.</li>
-</ul>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="migrationoverview.html#migrationoverview">Migration Overview</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="migrateanrpw2003plugin.html#migrateanrpw2003plugin">Migrate an IBM RUP 2003.06 Plugin</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/discipline.html b/1.5/plugins/org.eclipse.epf.help.doc/html/discipline.html
deleted file mode 100644
index 1f5a29d..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/discipline.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Discipline" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="discipline" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Discipline</title>
-</head>
-<body id="discipline"><a name="discipline"><!-- --></a>
-
-<h1 class="topictitle1">Discipline</h1>
-<div><p>A discipline is a collection of <a href="task.html#task">Tasks</a> that
-are related to a major area of concern within the overall IT environment.
-For example, on a software development project, it is common to perform certain
-requirements tasks in close coordination with analysis and design tasks. Separating
-these tasks into separate disciplines makes the tasks easier to comprehend.
-Disciplines can be organized using Discipline Groupings.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/domain.html b/1.5/plugins/org.eclipse.epf.help.doc/html/domain.html
deleted file mode 100644
index ca42351..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/domain.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Domain" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="domain" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Domain</title>
-</head>
-<body id="domain"><a name="domain"><!-- --></a>
-
-<h1 class="topictitle1">Domain</h1>
-<div><p>A Domain is a refineable, logical, hierarchy of related <a href="workproduct.html#workproduct">Work Products</a> grouped together based on timing, resources,
-or relationship. While a Domain categorizes many work products, a work product
-belongs to only one Domain. Domains can be further divided into sub-domains. </p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/example.html b/1.5/plugins/org.eclipse.epf.help.doc/html/example.html
deleted file mode 100644
index 1d1a512..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/example.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Example" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="example" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Example</title>
-</head>
-<body id="example"><a name="example"><!-- --></a>
-
-<h1 class="topictitle1">Example</h1>
-<div><p>An Example is a specific type of guidance that provides an example of a
-completed work product. </p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/extends.html b/1.5/plugins/org.eclipse.epf.help.doc/html/extends.html
deleted file mode 100644
index 7e1fb43..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/extends.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Extends" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="replace.html#replaces" />
-<meta name="DC.Relation" scheme="URI" content="contributes.html#contributes" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="extends" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Extends</title>
-</head>
-<body id="extends"><a name="extends"><!-- --></a>
-
-<h1 class="topictitle1">Extends</h1>
-<div><p>An extending element inherits characteristics of the base element. Extension
-allows Method Plug-ins to easily reuse elements from a base plug-in by providing
-a kind of inheritance for the extending element. Attribute values and association
-instances are inherited from the "based-on" element to the extending element.
-The result is that the extending element has the same properties as the "based-on"
-element, but might define its own additions. Extends is not used to modify
-content of the base plug-in, but to provide the ability for the extending
-plug-in to define its own content which is a variant of content already defined.
-For example, a special version of a generic Review Record for a specific type
-of review. The effect of this is that the base element and any number of extending
-elements can be used side by side, but refer to each other through the extends
-relationship. Extends also provides the key mechanism for binding capability
-patterns to processes: A pattern is applied by defining an extends relationship
-from an activity of the applying processes to the capability pattern. The
-activity inherits association instances from the pattern and the pattern appears
-to be part of the resulting process after interpretation.</p>
-<p>Use the Content Variability section on the Description tab to make an element
-extend another element. Select <strong>Extends</strong> as the Variability Type, and
-then select the base element which this element extends. The base element
-must be the same type of element as the extending element.</p>
-<p>Any information you enter in the extending element is added to the base
-element in creating an additional element. Text fields in the extending element
-are added at the end of the respective text fields in the base element.</p>
-<p>Extends only defines inheritance for the extending element. The base remains
-untouched. If the extending element is allowed an association to only one
-other element and has such an element defined itself, inheritance will not
-override this association.</p>
-<div class="p"><strong>Extends rules:</strong><ul><li>Attribute values of the base element are inherited to the extending element
-if the extending element has not defined its own values.</li>
-<li>Outgoing to-many associations of the base element are inherited to the
-extending element.</li>
-<li>Outgoing to-one associations are only inherited if the extending element
-does not define its own to-one association.</li>
-<li>Extends works transitively, i.e. if an extending element is extended itself,
-the second extension inherits from its direct and indirect base elements.</li>
-<li>Contribution precedes Extends, i.e. contribution is evaluated first and
-then extending elements inherit afterwards from the base element (including
-all of its contribution).</li>
-<li>Replace precedes Extends, i.e. if a base element has a replace and extends
-relationship, the extending element inherits from the replacing element.</li>
-</ul>
-See <a href="variabilityassociations.html#variabilityassociations">Variability Associations</a> for more information on the associations for each element
-type.</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-<div><a href="replace.html#replaces">Replaces</a></div>
-<div><a href="contributes.html#contributes">Contributes</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/findreplace.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/findreplace.gif
deleted file mode 100644
index 383963b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/findreplace.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/guidance.html b/1.5/plugins/org.eclipse.epf.help.doc/html/guidance.html
deleted file mode 100644
index e772a4f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/guidance.html
+++ /dev/null
@@ -1,104 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Guidance" />
-<meta name="DC.Relation" scheme="URI" content="createguidance.html#createguidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="guidance" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Guidance</title>
-</head>
-<body id="guidance"><a name="guidance"><!-- --></a>
-
-<h1 class="topictitle1">Guidance</h1>
-<div><div class="p">Guidance is a general term for additional information related to <a href="role.html#role">roles</a>, <a href="task.html#task">tasks</a>, and <a href="workproduct.html#workproduct">work products</a>. Examples of guidance are:<ul><li><strong><span class="keyword">Guideline</span></strong> - Provides additional detail on how
-to perform a particular task or grouping of tasks, or that provides additional
-detail, rules, and recommendations on work products and their properties.
-Amongst others, it can include details about best practices and different
-approaches for doing work, how to use particular types of work products, information
-on different subtypes and variants of the work product and how they evolve
-throughout a lifecycle, discussions on skills the performing roles should
-acquire or improve upon, and measurements for progress and maturity.<p></p>
-</li>
-<li><strong><span class="keyword">Template</span></strong> - A specific type of guidance that
-provides for a work product a predefined table of contents, sections, packages,
-and/or headings, a standardized format, as well as descriptions how the sections
-and packages are supposed to be used and completed. Templates cannot only
-be provided for documents, but also for conceptual models or physical data
-stores.<p></p>
-</li>
-<li><strong><span class="keyword">Checklist</span></strong> - A specific type of guidance that
-identifies a series of items that need to be completed or verified. Checklists
-are often used in reviews such as walkthroughs or inspections.<p></p>
-</li>
-<li><strong><span class="keyword">Tool Mentor</span></strong> - A specific type of guidance that
-shows how to use a specific tool to accomplish some piece of work, either
-in the context of, or independent from, a task or activity.<p></p>
-</li>
-<li><strong><span class="keyword">Supporting Material</span></strong> - Used as a catch all for
-other types of guidance not specifically defined elsewhere. It can be related
-to all kinds of content elements, including other guidance elements.<p></p>
-</li>
-<li><strong><span class="keyword">Report</span></strong> - A predefined template of a result that
-is generated on the basis of other work products as an output from some form
-of tool automation. An example for a report would be a use case model survey,
-which is generated by extracting diagram information from a graphical model
-and textual information from documents and combines these two types of information
-into a report.<p></p>
-</li>
-<li><strong><span class="keyword">Concept</span></strong> - A specific type of guidance that outlines
-key ideas associated with basic principles underlying the referenced item.
-Concepts normally address more general topics than guidelines and span across
-several work product and/or tasks or activities.<p></p>
-</li>
-<li><strong><span class="keyword">Practice</span></strong> - Represents a proven way or strategy
-of doing work to achieve a goal that has a positive impact on work product
-or process quality. Practices are defined orthogonal to methods and processes.
-They could summarize aspects that impact may different parts of a method or
-specific process. <p></p>
-</li>
-<li><strong><span class="keyword">Reusable Asset</span></strong> - Provides a solution to a problem
-for a given context. The asset may have a variability point, which is a location
-in the asset that may have a value provided or customized by the asset consumer.
-The asset has rules for usage which are the instructions describing how the
-asset should be used.<p></p>
-</li>
-<li><strong><span class="keyword">Term Definition</span></strong> - Defines concepts and is used
-to build up the Glossary. A term definition is not directly related to content
-elements, but its relationship is being derived when the term is used in the
-content elements description text.<p></p>
-</li>
-<li><strong><span class="keyword">White Paper</span></strong> - A special concept guidance that
-has been external reviewed or published and can be read and understood in
-isolation of other content elements and guidance.<p></p>
-</li>
-<li><strong><span class="keyword">Example</span></strong> - A specific type of guidance that provides
-an example of a completed work product.</li>
-</ul>
-See also:</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createguidance.html#createguidance">Create Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/guideline.html b/1.5/plugins/org.eclipse.epf.help.doc/html/guideline.html
deleted file mode 100644
index 79e788f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/guideline.html
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Guideline" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="guideline" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Guideline</title>
-</head>
-<body id="guideline"><a name="guideline"><!-- --></a>
-
-<h1 class="topictitle1">Guideline</h1>
-<div><p>A Guideline is a specific type of guidance that provides additional detail
-on how to perform a particular task or grouping of tasks, or that provides
-additional detail, rules, and recommendations on work products and their properties.
-Amongst others, it can include details about best practices and different
-approaches for doing work, how to use particular types of work products, information
-on different subtypes and variants of the work product and how they evolve
-throughout a lifecycle, discussions on skills the performing roles should
-acquire or improve upon, measurements for progress, and maturity.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/ibmdita.css b/1.5/plugins/org.eclipse.epf.help.doc/html/ibmdita.css
deleted file mode 100644
index 7da26c5..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/ibmdita.css
+++ /dev/null
@@ -1,231 +0,0 @@
-/*
- * Copyright (c) 2005, 2006 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- *
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * IBM Corporation - initial implementation
- */
-
-.unresolved { background-color: skyblue; }
-.noTemplate { background-color: yellow; }
-
-.sidebar {background: silver }
-.toc {font-size: small; }
-
-.base { background-color: #ffffff; }
-.breadcrumb { font-size : smaller;}
-.prereq { margin-left : 20px;}
-.hierarchy { display: block; border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; border-color : Silver;}
-
-.nested0 { margin-top : 1em;}
-.nested1 { }
-.nested2 { }
-
-.p {margin-top: 1em}
-
-.tableborder { margin-top: 1em; margin-bottom: 1em }
-.tablenoborder { margin-top: 1em; margin-bottom: 1em }
-caption { text-align: left; font-style: italic }
-.simpletableborder { margin-top: 1em; margin-bottom: 1em }
-.simpletablenoborder { margin-top: 1em; margin-bottom: 1em }
-.choicetableborder { margin-top: 1em; margin-bottom: 1em }
-.choicetablenoborder { margin-top: 1em; margin-bottom: 1em }
-
-.figcap { font-style: italic }
-.figdesc { font-style: normal }
-
-.fignone {margin-top: 1em}
-.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;}
-.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;}
-.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;}
-.figbottom { border-bottom : 2px solid; border-color : Silver;}
-.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;}
-
-.synnone {margin-top: 1em}
-.synborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;}
-.synsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;}
-.syntop { border-top : 2px solid; margin-top: 1em; border-color : Silver;}
-.synbottom { border-bottom : 2px solid; border-color : Silver;}
-.syntopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;}
-
-.skip { margin-top: 1em }
-.skipspace { margin-top: 1em; margin-bottom: 1em }
-.ullinks { list-style-type: none }
-.ulchildlink { margin-top: 1em; margin-bottom: 1em }
-.olchildlink { margin-top: 1em; margin-bottom: 1em }
-.linklist { margin-bottom: 1em }
-.linklistwithchild { margin-left: 1.5em; margin-bottom: 1em }
-.sublinklist { margin-left: 1.5em; margin-bottom: 1em }
-.relconcepts { margin-top: 1em; margin-bottom: 1em }
-.reltasks { margin-top: 1em; margin-bottom: 1em }
-.relref { margin-top: 1em; margin-bottom: 1em }
-.relinfo { margin-top: 1em; margin-bottom: 1em }
-div.breadcrumb {margin-bottom: 1em }
-
-.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; }
-.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; }
-.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; }
-.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; }
-.topictitle5 { font-size: 1.17em; font-weight: bold; }
-.topictitle6 { font-size: 1.17em; font-style: italic; }
-.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;}
-.section { margin-top: 1em; margin-bottom: 1em }
-.example { margin-top: 1em; margin-bottom: 1em }
-
-.note { margin-top: 1em; margin-bottom : 1em;}
-.notetitle { font-weight: bold }
-.notelisttitle { font-weight: bold }
-.tip { margin-top: 1em; margin-bottom : 1em;}
-.tiptitle { font-weight: bold }
-.fastpath { margin-top: 1em; margin-bottom : 1em;}
-.fastpathtitle { font-weight: bold }
-.important { margin-top: 1em; margin-bottom : 1em;}
-.importanttitle { font-weight: bold }
-.remember { margin-top: 1em; margin-bottom : 1em;}
-.remembertitle { font-weight: bold }
-.restriction { margin-top: 1em; margin-bottom : 1em;}
-.restrictiontitle { font-weight: bold }
-.attention { margin-top: 1em; margin-bottom : 1em;}
-.attentiontitle { font-weight: bold }
-.dangertitle { margin-top: 1em; font-weight: bold }
-.danger { padding: 5px 5px 5px 5px; border: solid; border-width: thin; font-weight: bold; margin-top: 2px; margin-bottom : 1em; }
-.cautiontitle { margin-top: 1em; font-weight: bold }
-.caution { font-weight: bold; margin-bottom : 1em; }
-
-ul.simple { list-style-type: none }
-
-.firstcol { font-weight : bold;}
-
-.bold { font-weight: bold; }
-.boldItalic { font-weight: bold; font-style: italic; }
-.italic { font-style: italic; }
-.underlined { text-decoration: underline; }
-.uicontrol { font-weight: bold; }
-.parmname { font-weight: bold; }
-.defparmname { font-weight: bold; text-decoration: underline; }
-.kwd { font-weight: bold; }
-.defkwd { font-weight: bold; text-decoration: underline; }
-.var { font-style : italic;}
-.shortcut { text-decoration: underline; }
-
-.ptocH1 {font-size: x-small; }
-.ptocH2 {font-size: x-small; }
-
-.smallCaps { text-transform: uppercase; font-size: smaller; }
-.stitle { font-style: italic; text-decoration: underline; }
-.nte {}
-
-.dlterm { font-weight: bold; }
-.dltermexpand { font-weight: bold; margin-top: 1em; }
-.defListHead { font-weight: bold; text-decoration: underline; }
-.parmListKwd { font-weight: bold; }
-.parmListVar { font-style: italic; }
-.pk { font-weight: bold; text-decoration: underline; }
-
-*[compact="yes"]>li { margin-top: 0em;}
-*[compact="no"]>li { margin-top: .53em;}
-.liexpand { margin-top: 1em; margin-bottom: 1em }
-.sliexpand { margin-top: 1em; margin-bottom: 1em }
-.dlexpand { margin-top: 1em; margin-bottom: 1em }
-.ddexpand { margin-top: 1em; margin-bottom: 1em }
-.stepexpand { margin-top: 1em; margin-bottom: 1em }
-.substepexpand { margin-top: 1em; margin-bottom: 1em }
-
-div.imageleft { text-align: left }
-div.imagecenter { text-align: center }
-div.imageright { text-align: right }
-div.imagejustify { text-align: justify }
-
-pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre}
-
-CITE { font-style: italic; }
-EM { font-style: italic; }
-STRONG { font-weight: bold; }
-VAR { font-style: italic; }
-
-/************************************************************************
- Styles added to support .NET output. Not used by standard processing.
- ************************************************************************/
-
-body.dotnet /* This body tag requires the use of one of the sets of banner and/or text div ids */
- {
- margin: 0px 0px 0px 0px;
- padding: 0px 0px 0px 0px;
- background: #ffffff;
- color: #000000;
- width: 100%;
- }
-
-div.nstext /* Creates the scrolling text area for Nonscrolling region topic */
- {
- padding: 5px 10px 0px 22px;
- }
-
-div.nsbanner /* Creates Nonscrolling banner region */
- {
- position: relative;
- left: 0px;
- padding: 0px 0px 0px 0px;
- border-bottom: 1px solid #999999;
- }
-
-div.bannerrow1 /* provides full-width color to top row in running head */
- {
- background-color: #99ccff;
- }
-
-/* STYLES FOR RUNNING HEADS */
-
-table.bannerparthead, table.bannertitle /* General values for the Running Head tables */
- {
- position: relative;
- left: 0px;
- top: 0px;
- padding: 0px 0px 0px 0px;
- margin: 0px 0px 0px 0px;
- width: 100%;
- height: 21px;
- border-collapse: collapse;
- border-style: solid;
- border-width: 0px;
- background-color: #99ccff;
- font-size: 100%;
- }
-table.bannerparthead td /* General Values for cells in the top row of running head */
- {
- margin: 0px 0px 0px 0px;
- padding: 2px 0px 0px 4px;
- vertical-align: middle;
- /*border-width: 0px 0px 1px 0px; */
- border-width: 0px
- border-style: solid;
- border-color: #999999;
- background: transparent;
- font-style: italic;
- font-weight: normal;
- }
-table.bannerparthead td.product /* Values for top right cell in running head */
- { /* Allows for a second text block in the running head */
- text-align: right;
- padding: 2px 5px 0px 5px;
- }
-
-h1.dtH1 {
- margin-left: -18px;
- }
-div.titlerow /* provides non-scroll topic title area (requires script) */
- {
- width: 100%; /* Forces tables to have correct right margin */
- padding: 0px 10px 0px 22px;
- background-color: #99ccff;
- }
-div.titlerow h1
- {
- margin-top: 0em;
- font-weight: bold;
- margin-bottom: .2em
- }
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/indent.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/indent.gif
deleted file mode 100644
index a21fb77..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/indent.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/italic.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/italic.gif
deleted file mode 100644
index dfe3e0d..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/italic.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/iteration.html b/1.5/plugins/org.eclipse.epf.help.doc/html/iteration.html
deleted file mode 100644
index 854a36f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/iteration.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Iteration" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="iteration" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Iteration</title>
-</head>
-<body id="iteration"><a name="iteration"><!-- --></a>
-
-<h1 class="topictitle1">Iteration</h1>
-<div><p>Iteration is a group of nested Activities that are repeated more than once.
-Iteration represents an important structuring element to organize work in
-repetitive cycles.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/libraryview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/libraryview.html
deleted file mode 100644
index 7f27e95..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/libraryview.html
+++ /dev/null
@@ -1,54 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Library View" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html#userinterfaceoverview" />
-<meta name="DC.Relation" scheme="URI" content="configurationview.html#configurationview" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Relation" scheme="URI" content="configurationview.html" />
-<meta name="DC.Relation" scheme="URI" content="browseandpreviewmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="libraryview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Library View</title>
-</head>
-<body id="libraryview"><a name="libraryview"><!-- --></a>
-
-<h1 class="topictitle1">Library View</h1>
-<div><p>The Library View displays the Method Plug-ins and Configurations contained
-in a <a href="standardmethodlibraryoverview.html">Method Library</a>.</p>
-<p>The Library View is available only in the <a href="authoringperspective.html">Authoring Perspective</a> and,
-when open, enables the creation, modification and viewing of all element types.</p>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div class="previouslink"><strong>Previous topic:</strong> <a href="configurationview.html">Configuration View</a></div>
-<div class="nextlink"><strong>Next topic:</strong> <a href="browseandpreviewmethodcontent.html">Browse and Preview Method Content</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="userinterfaceoverview.html#userinterfaceoverview" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div><a href="configurationview.html#configurationview">Configuration View</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/mc.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/mc.gif
deleted file mode 100644
index 6e2cee1..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/mc.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/meth_vs_proc.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/meth_vs_proc.gif
deleted file mode 100644
index b145ab2..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/meth_vs_proc.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodauthoringoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodauthoringoverview.html
deleted file mode 100644
index e9d567d..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodauthoringoverview.html
+++ /dev/null
@@ -1,95 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Content Authoring Overview" />
-<meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="methodauthoringoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Content Authoring Overview</title>
-</head>
-<body id="methodauthoringoverview"><a name="methodauthoringoverview"><!-- --></a>
-
-<h1 class="topictitle1">Method Content Authoring Overview</h1>
-<div><p>Method content is described by defining tasks that have work products as
-inputs and outputs and that are performed by roles. The roles also define
-responsibility relationships to the work products.</p>
-<p><img src="mc.gif" alt="" /></p>
-<p>The figure above depicts typical sources for method content, as well as
-how the method content is represented. To learn about development methods,
-people research in libraries or receive training. Development methods are
-typically described in publications such as books, articles, training material,
-standards and regulations, or any other form of documentation. These sources
-usually document methods by providing step-by-step explanations for a particular
-way of achieving a specific development goal under general circumstances.
-Some examples are: transforming a requirements document into an analysis model;
-defining an architectural mechanism based on functional and non-functional
-requirements; creating a project plan for a development iteration; defining
-a quality assurance plan for functional requirements; redesigning a business
-organization based on a new strategic direction, and so on. </p>
-<p>This tool takes content such as the content described above, and structures
-it in one specific way using a predefined schema of concepts. This schema
-supports the organization of large amounts of descriptions for development
-methods and processes. Such method content and processes do not have to be
-limited to software engineering, but can also cover other design and engineering
-disciplines such as mechanical engineering, business transformation, sales
-cycles, and so on. </p>
-<p>The schema for method content is represented this tool as a construct of
-roles defining development skills and responsibilities for work products.
-These work products are produced by tasks that are performed by the roles
-and have the work products as inputs and outputs. The screen capture in the
-figure above shows how such method content elements are organized in tree
-browsers on the left. These tree browsers, similar to a library, provide different
-indexes of the available elements for rapid access. The screen capture shows
-on the right an example of a task presentation. This task presentation defines
-the task in terms of steps that need to be performed to achieve the task's
-purpose. You can see that the task has various relationships, such as relationships
-to performing roles as well as work products that serve as inputs and outputs
-to the task. Find more details on tasks, role, and work products in the online
-help here. In addition to roles, tasks, and work products, this tool supports
-the addition of guidance elements. Guidance are supplementary free-form documentation
-such as white papers, concept descriptions, guidelines, templates, examples,
-and so on. </p>
-<p>This tool provides various form-based editors to create new method content
-elements. Document your task, roles, work products, and guidance elements
-using intuitive rich-text editors that allow you to copy and paste text from
-other sources such as web pages or documents. Use simple dialogs to establish
-relationships between content elements. For example, make a work product the
-input to your task simply by selecting it in a dialog.</p>
-<p>Using this tool, you can organize content in physical content packages
-that allow you to manage your content in configurable units. You can also
-categorize your content based on a set of predefined categories (for example,
-categorize your tasks into development disciplines, or your work products
-into domains) or create your own categorization schemes for your content with
-your own user-defined categories that allow you to index content in any way
-you want. </p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodconfigurations.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodconfigurations.html
deleted file mode 100644
index b700f2c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodconfigurations.html
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Configuration" />
-<meta name="DC.Relation" scheme="URI" content="createamethodconfiguration.html#createamethodconfiguration" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="methodconfigurations" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Configuration</title>
-</head>
-<body id="methodconfigurations"><a name="methodconfigurations"><!-- --></a>
-
-<h1 class="topictitle1">Method Configuration</h1>
-<div><p>Method configurations are user-defined subsets of elements contained in
-the Method Library.</p>
-<p>A method configuration defines a working set of packages within the method
-library that helps you limit your view to a subset of elements. The elements
-that are part of a selected configuration are displayed in the <a href="configurationview.html#configurationview">Configuration View</a>. Method configurations are used for creating processes
-and for publication by defining which elements are published in HTML and which
-are not.</p>
-<p>A method configuration consists of three specifying parts:</p>
-<ul><li>A description of the configuration.</li>
-<li>A selection from the set of plug-ins and packages.</li>
-<li>A selection of views to be published in the Web site.</li>
-</ul>
-<p>In a method configuration, you are able to select and deselect from the
-content packages and process available in the method library's
-set of plug-ins. The selections you make help determine the content of your
-published Web site. A configuration is given a name and then saved so it can
-be changed and then re-published at a later date.</p>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createamethodconfiguration.html#createamethodconfiguration">Create a Method Configuration</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontent.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontent.html
deleted file mode 100644
index d3cbddd..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontent.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Content" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html#createamethodplugin" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="creatingreusablemethodcontents" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Content</title>
-</head>
-<body id="creatingreusablemethodcontents"><a name="creatingreusablemethodcontents"><!-- --></a>
-
-<h1 class="topictitle1">Method Content</h1>
-<div><p>Method content provides step-by-step explanations, describing
-how specific development goals are achieved, independent of the placement
-of these steps within a development lifecycle. Processes take these method
-elements and relate them into semi-ordered sequences that are customized to
-specific types of projects.</p>
-<p>Method content elements are:</p>
-<ul><li><a href="task.html#task">Task</a></li>
-<li><a href="role.html#role">Role</a></li>
-<li><a href="workproduct.html#workproduct">Work Product</a></li>
-<li><a href="guidance.html">Guidance</a></li>
-</ul>
-<p>A Process Engineer authors these elements, defines the relationships between
-them, and then categorizes them. Method content provides step-by-step explanations,
-describing how specific development goals are achieved independent of the
-placement of these steps within a development lifecycle. Processes take these
-method elements and relate them into semi-ordered sequences that are customized
-to specific types of projects.</p>
-<p>For example, a software development project that develops an application
-from scratch performs development tasks such as "Develop Vision" or "Use Case
-Design" similar to a project that extends an existing software system. However,
-the two projects will perform the tasks at different points in time with a
-different emphasis, i.e., they perform the steps of these tasks at different
-points of time and perhaps apply individual variations and additions. </p>
-<p>Method content elements are contained within method content packages which,
-in turn, are contained within a Method plug-in. In order to separate your
-own content from original OpenUP content, you should always create new
-method content in a method plug-in that you produce. Creating method content
-in a method plug-in of your own also allows you to update your own library
-with new releases of the OpenUP library without affecting the content
-that you have created in your own plug-ins.</p>
-<p>See also:</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-<div><a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentcategories.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentcategories.html
deleted file mode 100644
index e3a6494..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentcategories.html
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Content Categories" />
-<meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="methodcontentcategories" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Content Categories</title>
-</head>
-<body id="methodcontentcategories"><a name="methodcontentcategories"><!-- --></a>
-
-<h1 class="topictitle1">Method Content Categories</h1>
-<div><p>Method Content elements are organized into logical categories. The categories
-can appear in your final, published Web site as views.</p>
-<p>There are two types of category: Standard and Custom.</p>
-<p></p>
-<div class="section"><h4 class="sectiontitle">Standard Categories</h4><p>Standard Categories provide
-a means to categorize core method content in line with the best practices
-for creating structured methods. Standard Categories are linked with a specific
-method content type, e.g. Disciplines contain only tasks. </p>
-<div class="p">Standard
-Category types are:<ul><li><strong>Disciplines</strong> - A discipline is a collection of <a href="task.html#task">Tasks</a> that are related to a major area of concern within
-the overall IT environment. For example, on a software development project,
-it is common to perform certain requirements tasks in close coordination with
-analysis and design tasks. Separating these tasks into separate disciplines
-makes the tasks easier to comprehend. Disciplines can be organized using Discipline
-Groupings.</li>
-<li><strong>Domains</strong> - A Domain is a refineable, logical, hierarchy of related <a href="workproduct.html#workproduct">Work Products</a> grouped
-together based on timing, resources, or relationship. While a Domain categorizes
-many work products, a work product belongs to only one Domain. Domains can
-be further divided into sub-domains. </li>
-<li><strong>Work Product Kinds</strong> - Work Product Kind is another category for
-grouping <a href="workproduct.html#workproduct">Work Products</a>.
-A work product can have many work product kinds. As an example, you might
-want to have a series of work product kinds that correspond to the overall
-intent of work products, such as specification, plan, or model.</li>
-<li><strong>Role Sets</strong> - A Role Set is used to group <a href="role.html#role">Roles</a> with certain commonalities together. For example,
-in a software development environment, an Analyst role set could be used to
-group together roles such as Business Process Analyst, System Analyst and
-Requirements Specifier. Each of these roles work with similar techniques and
-have overlapping skills, but may be responsible for performing certain tasks
-and creating certain work products. Role sets can be organized using Role
-Set Groupings.</li>
-<li><strong>Tools</strong> - Tools is a container for <a href="toolmentor.html#toolmentor">Tool Mentors</a>. Tools can also provide general descriptions
-of a tool and it's general capabilities.</li>
-</ul>
-</div>
-</div>
-<div class="section"><h4 class="sectiontitle">Custom Categories</h4><p>Custom Categories are highly customizable
-and can contain any type of element. Custom Categories allow you to categorize
-content according to any scheme you want and can then be used to compose publishable
-Views, providing a means to organize the method content prior to publishing.
-For example, you could create a custom category that logically organizes content
-relevant to your development organization department, such as a Testing category
-that groups together all roles, work products, tasks, and guidance elements
-relevant to testing.</p>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div>
-<div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentpackage.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentpackage.html
deleted file mode 100644
index fa85f95..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodcontentpackage.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Content Package" />
-<meta name="DC.Relation" scheme="URI" content="createacontentpackage.html#createcontentpackage" />
-<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html#createamethodplugin" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="methodcontentpackage" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Content Package</title>
-</head>
-<body id="methodcontentpackage"><a name="methodcontentpackage"><!-- --></a>
-
-<h1 class="topictitle1">Method Content Package</h1>
-<div><p>A Method package is a container for method elements. Elements are organized
-in method packages to structure a large scale of method content and processes
-as well as to define a mechanism for reuse. Method elements from one package
-can reuse elements from other packages by defining a link between them. For
-example, a work product defined in one package can be used as an input for
-tasks defined in another package, ensuring that no redundant definitions of
-the same elements are required. Also, maintenance of method content is greatly
-improved as changes can be performed in only one place.</p>
-<p></p>
-<div class="section"><h4 class="sectiontitle">Structure of a Method Package</h4><p>Although a method
-package is a container for method elements, its structure is broken down into
-smaller packages to better organize the content, such as content packages,
-standard categories, and custom categories.</p>
-</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createacontentpackage.html#createcontentpackage">Create a Content Package</a></div>
-<div><a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a></div>
-<div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/methodplugin.html b/1.5/plugins/org.eclipse.epf.help.doc/html/methodplugin.html
deleted file mode 100644
index e83904c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/methodplugin.html
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Method Plug-in" />
-<meta name="DC.Relation" scheme="URI" content="createamethodplugin.html#createamethodplugin" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="methodplugin" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Method Plug-in</title>
-</head>
-<body id="methodplugin"><a name="methodplugin"><!-- --></a>
-
-<h1 class="topictitle1">Method Plug-in</h1>
-<div><p>All content is organized in method plug-ins. A method plug-in is a container
-for method packages which, in turn, contain the method and process content.
-Method plug-ins and method packages allow you to organize your content at
-a level of granularity that suits your needs for authoring and reusing the
-content. </p>
-<p>When you create a method plug-in, you will usually want to reuse content
-in other plug-ins. You may want to modify or extend the content in these other
-plug-ins or add your own content. When you create a plug-in you
-can reference any number of other plug-ins that want to use in this way. A
-method plug-in can also be stand-alone and not reference other plug-ins.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createamethodplugin.html#createamethodplugin">Create a Method Plug-in</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/milestone.html b/1.5/plugins/org.eclipse.epf.help.doc/html/milestone.html
deleted file mode 100644
index 59cc774..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/milestone.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Milestone" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="milestone" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Milestone</title>
-</head>
-<body id="milestone"><a name="milestone"><!-- --></a>
-
-<h1 class="topictitle1">Milestone</h1>
-<div><p>A Milestone describes a significant event in a project, such
-as a major decision, completion of a deliverable, or meeting of a major dependency
-such as the completion of a project phase.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/openpersp.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/openpersp.JPG
deleted file mode 100644
index ba4a604..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/openpersp.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/outcome.html b/1.5/plugins/org.eclipse.epf.help.doc/html/outcome.html
deleted file mode 100644
index 6d3fbe8..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/outcome.html
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Outcome" />
-<meta name="DC.Relation" scheme="URI" content="workproduct.html#workproduct" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html" />
-<meta name="DC.Relation" scheme="URI" content="artifact.html#artifact" />
-<meta name="DC.Relation" scheme="URI" content="deliverable.html#deliverable" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="outcome" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Outcome</title>
-</head>
-<body id="outcome"><a name="outcome"><!-- --></a>
-
-<h1 class="topictitle1">Outcome</h1>
-<div><p>An outcome is an intangible work product that may be a result or state.
-Outcomes may also be used to describe work products that are not formally
-defined. </p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="workproduct.html#workproduct">Work Product</a></div>
-<div><a href="artifact.html#artifact">Artifact</a></div>
-<div><a href="deliverable.html#deliverable">Deliverable</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createaworkproduct.html">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/outdent.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/outdent.gif
deleted file mode 100644
index ad64691..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/outdent.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/paste.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/paste.gif
deleted file mode 100644
index ed7e690..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/paste.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/perspectives.html b/1.5/plugins/org.eclipse.epf.help.doc/html/perspectives.html
deleted file mode 100644
index a8c3e5c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/perspectives.html
+++ /dev/null
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Perspectives" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html#userinterfaceoverview" />
-<meta name="DC.Relation" scheme="URI" content="authoringperspective.html#authoringperspective" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html#browingperspective" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="perspectives" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Perspectives</title>
-</head>
-<body id="perspectives"><a name="perspectives"><!-- --></a>
-
-<h1 class="topictitle1">Perspectives</h1>
-<div><p>A Perspective defines a set of views and functions available for specific
-tasks. Eclipse Process Framework Composer contains two working perspectives: an
-Authoring Perspective and a Browsing Perspective.</p>
-<p>The <a href="authoringperspective.html#authoringperspective">Authoring
-Perspective</a> provides views and functions to navigate and author method
-content and processes, while the <a href="browsingperspective.html#browingperspective">Browsing Perspective</a>, as its name implies, allows you
-to preview and navigate through a <a href="methodconfigurations.html#methodconfigurations">Method Configuration</a> without making any changes.</p>
-<p>To select a perspective, click the Open Perspective button <img src="openpersp.JPG" alt="" />.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="userinterfaceoverview.html#userinterfaceoverview" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div><a href="authoringperspective.html#authoringperspective">Authoring Perspective</a></div>
-<div><a href="browsingperspective.html#browingperspective">Browsing Perspective</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/phase.html b/1.5/plugins/org.eclipse.epf.help.doc/html/phase.html
deleted file mode 100644
index a32fea9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/phase.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Phase" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="phase" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Phase</title>
-</head>
-<body id="phase"><a name="phase"><!-- --></a>
-
-<h1 class="topictitle1">Phase</h1>
-<div><p>A Phase is a special type of activity that represents a significant
-period in a project, ending with a major management checkpoint, milestone
-or set of deliverables.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/practice.html b/1.5/plugins/org.eclipse.epf.help.doc/html/practice.html
deleted file mode 100644
index ce74ca2..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/practice.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Practice" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="practice" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Practice</title>
-</head>
-<body id="practice"><a name="practice"><!-- --></a>
-
-<h1 class="topictitle1">Practice</h1>
-<div><p>A practice represents a proven way or strategy of doing work to achieve
-a goal that has a positive impact on work product or process quality. Practices
-are defined orthogonal to methods and processes. They could summarize aspects
-that impact many different parts of a method or specific processes. Examples
-for practices would be manage risks, continuously verify quality, architecture
-centric, and component based development, to name a few.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/preview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/preview.html
deleted file mode 100644
index 37a4f9b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/preview.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Preview" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="preview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Preview</title>
-</head>
-<body id="preview"><a name="preview"><!-- --></a>
-
-<h1 class="topictitle1">Preview</h1>
-<div><p>Preview displays your content in browser format similar to
-how it will appear to an end user browsing a published Web site.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/procauth.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/procauth.gif
deleted file mode 100644
index cbf8e88..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/procauth.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/process.html b/1.5/plugins/org.eclipse.epf.help.doc/html/process.html
deleted file mode 100644
index e2fc82c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/process.html
+++ /dev/null
@@ -1,68 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Process" />
-<meta name="DC.Relation" scheme="URI" content="processauthoringoverview.html#processauthoringoverview" />
-<meta name="DC.Relation" scheme="URI" content="createadeliveryprocess.html#createadeliveryprocess" />
-<meta name="DC.Relation" scheme="URI" content="createareusablecapabilitypattern.html#createareusablecapabilitypattern" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="process" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Process</title>
-</head>
-<body id="process"><a name="process"><!-- --></a>
-
-<h1 class="topictitle1">Process</h1>
-<div><div class="section"><p>A <span class="keyword">process</span> describes how a particular piece
-of work should be done. The work may have a relatively small scope, in which
-case it can be described as a capability pattern, or may address a full project
-lifecycle, in which case it can be described as a delivery process. A process
-can reuse method elements and combines them into a structure and sequence
-for carrying out work.</p>
-<p>There are two main types of process, a <a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a> and
-a <a href="deliveryprocess.html#deliveryprocess">Delivery Process</a>.
-A capability pattern is a special process that describes a reusable cluster
-of activities in common process areas, while a delivery process describes
-a complete and integrated approach for performing a specific type of project.</p>
-<p>Each
-time a task is included in a process, a reference object to that task is created
-in the context of the process. This is called a task descriptor. The same
-task can be referenced any number of times in the same process. In other words,
-one task can have many task descriptors. A task descriptor can also modify
-the base task without actually changing the task. For example, roles and work
-products can be added or suppressed, and steps can be suppressed or re-sequenced.</p>
-<p>Roles
-and work products can also be included in processes as role descriptors and
-work product descriptors. Roles and work products can be customized to fit
-with the content of the process in which they are used.</p>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="processauthoringoverview.html#processauthoringoverview">Process Authoring Overview</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createadeliveryprocess.html#createadeliveryprocess">Create a Delivery Process</a></div>
-<div><a href="createareusablecapabilitypattern.html#createareusablecapabilitypattern">Create a Reusable Capability Pattern</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/processauthoringoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/processauthoringoverview.html
deleted file mode 100644
index 15ccb4b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/processauthoringoverview.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Process Authoring Overview" />
-<meta name="DC.Relation" scheme="URI" content="process.html#process" />
-<meta name="DC.Relation" scheme="URI" content="createareusablecapabilitypattern.html#createareusablecapabilitypattern" />
-<meta name="DC.Relation" scheme="URI" content="createadeliveryprocess.html#createadeliveryprocess" />
-<meta name="DC.Relation" scheme="URI" content="process.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="processauthoringoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Process Authoring Overview</title>
-</head>
-<body id="processauthoringoverview"><a name="processauthoringoverview"><!-- --></a>
-
-<h1 class="topictitle1">Process Authoring Overview</h1>
-<div><p>A development process defines sequences of tasks performed by roles and
-work products produced over time. </p>
-<p><img src="procauth.gif" alt="" /></p>
-<p>Processes are typically expressed as workflows or breakdown
-structures. Defining a strict sequence as in a waterfall model is as much
-a process as defining semi-ordered sequences in iterations of parallel work.
-They just represent different development approaches. Hence, for defining
-a process, one can take method content and combine it into structures that
-specify how the work shall be organized over time, to meet the needs of a
-particular type of development project (such as software for a online system
-versus software and hardware for an embedded system). EPF Composer supports processes
-based on different development approaches across many different lifecycle
-models, including waterfall, incremental, and iterative lifecycles. EPF Composer also
-supports different presentations for process, such as work-breakdown structure
-or workflow presentations. You can also define processes in EPF Composer that use a
-minimal set of method content to define processes for agile, self-organizing
-teams.</p>
-<p>The EPF Composer screen capture above shows an example of a process presented as
-a breakdown structure of nested activities as well as a workflow or activity
-diagram for one particular activity, the inception phase. It also indicates
-with the two blue arrows that the particular method content task "Detail a
-Use Case" has been applied in the process twice; firstly in the inception
-phase under the activity "Define the System," and secondly, in the elaboration
-phase in the activity "Refine the system definition". You see below each of
-these task applications, referred to as a task descriptors in EPF Composer, lists of
-the performing roles as well as the input and output work products. If you
-look closely, you see that these lists are different for each of these two
-task descriptors, expressing differences in performing the "Detail a Use Case"
-method throughout the lifecycle. You see different roles involved and changes
-in the list of inputs to be considered and outputs to be produced or updated.
-These changes were defined by the author that created this process to express
-the exact focus of the task performance for each occurrence. In addition to
-updating the roles, input and output work products for a task descriptor,
-you can also provide additional textual descriptions as well as define the
-exact steps of the task that should and should not be performed for this particular
-occurrence of the task. </p>
-<p>EPF Composer provides you with a process editor that supports different breakdown
-structure views as well as graphical process presentations. As a process author,
-you typically start by creating an activity breakdown, dividing and breaking
-your process down into phases, iterations, and high-level activities. Instead
-of creating your activities in the breakdown structure editor, you can alternatively
-work in a graphical activity diagram editor that allows you to graphically
-create a workflow for your activities. To assign method content to your process,
-you then have the choice of working in different process views (work breakdown
-structure, work product usage, or team allocation view). Each view supports
-a different approach for creating a process. You can define the work to be
-done, define the results to be produced, or define responsibilities for your
-roles. If requested, the editor updates the other process views semi-automatically
-using wizards that prompt you for decisions on selecting method content elements. </p>
-</div>
-<div>
-<ul class="ullinks">
-<li class="ulchildlink"><strong><a href="process.html">Process</a></strong><br />
-</li>
-</ul>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="process.html#process">Process</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createareusablecapabilitypattern.html#createareusablecapabilitypattern">Create a Reusable Capability Pattern</a></div>
-<div><a href="createadeliveryprocess.html#createadeliveryprocess">Create a Delivery Process</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/processelementpropertiesview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/processelementpropertiesview.html
deleted file mode 100644
index 21142ea..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/processelementpropertiesview.html
+++ /dev/null
@@ -1,101 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Process Element Properties View" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="processelementpropertiesview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Process Element Properties View</title>
-</head>
-<body id="processelementpropertiesview"><a name="processelementpropertiesview"><!-- --></a>
-
-<h1 class="topictitle1">Process Element Properties View</h1>
-<div><p>When you are editing a process, the process element properties view allows
-you to edit all the details for a single element in the process. If you click
-in any row in a process display, you will see the full details of the process
-element in the row in the properties view.</p>
-<p>If the properties view is not open, right click any row in a process and
-select <strong>Show Properties View</strong>.</p>
-<p>The properties view is the editor for activities, task descriptors, roles
-descriptors, and work product descriptors. The information for
-a descriptor is similar to the corresponding method element editor, but it
-also has information related to the element in the process. The process information
-is also displayed in the corresponding row in the process display.</p>
-<p><strong>General Information tab:</strong></p>
-<p>The Name and Presentation Name default to the corresponding names in the
-base method element. These names can be changed in a descriptor.</p>
-<div class="p">The following attributes are used to specify certain aspects of the element
-in the process and can be set for all types of process elements:<ul><li><strong>Optional</strong>: If this is checked (true), it indicates that the element
-is considered optional in the process. This means that it is safe to remove
-the element. If this is not checked (false), the element is considered mandatory
-and should not be removed from the process.</li>
-<li><strong>Multiple Occurrences</strong>: If this is checked (true), it indicates that
-when the process is instantiated as a project or other process, it is expected
-that there will be multiple occurrences of this element. If this is not checked
-(false), it indicates that there should only be a single occurrence of this
-element when the process is instantiated.</li>
-<li><strong>Planned</strong>: If this is checked (true), the element will be included
-in an export to a project management tool. If this is not checked (false),
-it will not be included in an export.</li>
-<li><strong>Suppressed</strong>: If this is checked (true), the element will not appear
-in a published process. This is usually used to modify a capability pattern
-included in a process. This is not checked (false) as default.</li>
-</ul>
-</div>
-<div class="p">The following elements can be set for task descriptors and activities:<ul><li><strong>Event Driven</strong>: If this is checked (true), it indicates that the
-task or activity will be initiated when a particular event occurs. If this
-is not checked (false), it indicates that the task or activity will be initiated
-based on other tasks in the process.</li>
-<li><strong>Ongoing</strong>: If this is checked (true), it indicates that the task
-or activity is continuous. If this is not checked (false), it indicates that
-the task or activity has a clear start and finish in the process.</li>
-<li><strong>Repeatable</strong>: If this is checked (true), it indicates that the task
-or activity can iterate when the process is instantiated. If this is not checked
-(false), it indicates that the task or activity will only occur once in the
-process.</li>
-</ul>
-</div>
-<p>Dependency Field: You can add one or more dependencies for a task or activity.
-Click the <strong>Add...</strong> button and enter the index number for the task or
-activity on which the current element is dependent. The dependency (type)
-defaults to Finish-to-Start. If you want to set another dependency type, click
-the <strong>Edit</strong> button and select the required dependency type in the dependency
-drop down box. You can enter a different index number on the Edit dialog.
-You can also remove a dependency by selecting the dependency and clicking
-the <strong>Remove</strong> button.</p>
-<p>The base method element for the descriptor is displayed on the page. You
-can select a different element by clicking the <strong>Link Method Element</strong> button
-and selecting the required element.</p>
-<p><strong>Documentation tab:</strong></p>
-<p>The documentation tab contains descriptive attributes for the descriptor
-or activity.</p>
-<p><strong>Roll-Up tabs:</strong></p>
-<p>The properties view for an activity includes roll-up tabs that provide
-lists of tasks, roles, or work products "rolled up", or summarized, for the
-activity.</p>
-<p><strong>Association tabs:</strong></p>
-<p>The remaining tabs are used to add or remove associations between the activity
-or descriptor to method elements.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/pub.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/pub.gif
deleted file mode 100644
index 0725474..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/pub.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/publishingamethodconfigurationtoamethodweb.html b/1.5/plugins/org.eclipse.epf.help.doc/html/publishingamethodconfigurationtoamethodweb.html
deleted file mode 100644
index 6f29a5a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/publishingamethodconfigurationtoamethodweb.html
+++ /dev/null
@@ -1,71 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Publishing a Method Configuration to a Method Web" />
-<meta name="DC.Relation" scheme="URI" content="publishingoverview.html#publishingoverview" />
-<meta name="DC.Relation" scheme="URI" content="exportaprocessormethodcontenttoaplanningtool.html" />
-<meta name="DC.Relation" scheme="URI" content="methodconfigurations.html#methodconfigurations" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="publishingamethodconfigurationtoamethodweb" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Publishing a Method Configuration to a Method Web</title>
-</head>
-<body id="publishingamethodconfigurationtoamethodweb"><a name="publishingamethodconfigurationtoamethodweb"><!-- --></a>
-
-<h1 class="topictitle1">Publishing a Method Configuration to a Method Web</h1>
-<div><div class="p">Using the Publish Method Configuration wizard, you can select from
-a series of publication options to turn a method configuration into a published
-method Web.</div>
-<div class="section">To publish a method configuration:</div>
-<ol><li class="stepexpand"><span>From the toolbar, select <strong>Configuration > Publish</strong>. The Publish
-Method Configuration wizard appears.</span></li>
-<li class="stepexpand"><span>On the Select Configuration page, select the configuration you
-want to publish from the list of method configurations in the library and
-then click <strong>Next</strong>.</span></li>
-<li class="stepexpand"><span>On the Specify Publishing Options page:</span><ul><li>Provide a destination directory for the published Web site in the
-Publication path field.</li>
-<li>Provide a title for the published method web.</li>
-<li>Select a banner image to use.</li>
-<li>Select a file to use for the "about" information.</li>
-<li>Provide a feedback URL</li>
-<li>Choose to include a glossary, index, search capability and/or process
-tree customization.</li>
-<li>Choose to check that external hyperlinks are valid.</li>
-<li>Choose to publish activity diagrams that have not been edited, such
-as activity diagrams that have been generated by the tool, but not manually
-edited.</li>
-</ul>
- <div class="note"><span class="notetitle">Note:</span> Choosing to include either the search capability or to support
-customization of the process view will include the browser applet in the published
-Web site. If you choose not to publish with the last two options, the browser
-applet will not be included.</div>
-</li>
-<li class="stepexpand"><span>Click <strong>Finish</strong>. Publishing is initiated.</span></li>
-</ol>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="publishingoverview.html#publishingoverview">Publishing Overview</a></div>
-<div><a href="methodconfigurations.html#methodconfigurations">Method Configuration</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/publishingoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/publishingoverview.html
deleted file mode 100644
index 93980e1..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/publishingoverview.html
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Publishing Overview" />
-<meta name="DC.Relation" scheme="URI" content="createamethodviewwithcustomcategories.html#createamethodviewwithcustomcategories" />
-<meta name="DC.Relation" scheme="URI" content="publishingamethodconfigurationtoamethodweb.html#publishingamethodconfigurationtoamethodweb" />
-<meta name="DC.Relation" scheme="URI" content="exportaprocessormethodcontenttoaplanningtool.html#exportaprocessormethodcontenttoaplanningtool" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="publishingoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Publishing Overview</title>
-</head>
-<body id="publishingoverview"><a name="publishingoverview"><!-- --></a>
-
-<h1 class="topictitle1">Publishing Overview</h1>
-<div><p>The ultimate output of EPF Composer is a published Web site with method
-guidance and processes that can be used by a project team. The information
-contained in the Web site provides a project team with a consistent method
-for the entire team to follow and a complete description of the end-to-end
-work lifecycle. </p>
-<p>It is easy to configure a process for a particular type or size of project
-and to publish the guidance to a Web site. A Method Configuration is a selection
-of Content Packages across different Method Plug-ins containing the method
-and process content that will be included in the published Web site. At publishing
-time, the configuration is combined with different Method Views which define
-the Web site's navigation structures and content organization.</p>
-<p>The Browsing Perspective renders the Method Configuration content in HTML
-format within the tool, providing a navigable representation of the method
-or process content associated with the configuration.</p>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createamethodviewwithcustomcategories.html#createamethodviewwithcustomcategories">Create a Method View with Custom Categories</a></div>
-<div><a href="publishingamethodconfigurationtoamethodweb.html#publishingamethodconfigurationtoamethodweb">Publishing a Method Configuration to a Method Web</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/replace.html b/1.5/plugins/org.eclipse.epf.help.doc/html/replace.html
deleted file mode 100644
index ccee2f2..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/replace.html
+++ /dev/null
@@ -1,87 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Replaces" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="extends.html#extends" />
-<meta name="DC.Relation" scheme="URI" content="contributes.html#contributes" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="replaces" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Replaces</title>
-</head>
-<body id="replaces"><a name="replaces"><!-- --></a>
-
-<h1 class="topictitle1">Replaces</h1>
-<div><p>A replacing element replaces parts of the base element. Replaces provides
-a way for an element to replace a base element without directly changing any
-of the base element's existing properties. This is, in most cases, used for
-method plug-ins that aim to replace specific content elements such as roles,
-tasks, or activities with either a completely new variant or to change the
-fundamental relationships of these elements. The effect of this, is that the
-base content element is logically replaced with the new replacing element
-to which all incoming associations still point as before, but which has potentially
-new attribute values and outgoing association properties.</p>
-<p>Use the Content Variability section on the Description tab to make an element
-replace another element. Select <strong>Replaces</strong> as the variability type and
-select the base element that this element will replace. The base element must
-be the same type of element as the replacing element.</p>
-<p>When you replace an element, all the description attributes are replaced
-by the replacing element. If a description attribute in the replacing element
-is blank, but the base element has content, the attribute will be blank in
-the resulting element.</p>
-<p>Replace always replaces attributes and associations of the base element
-with the replacing element's attributes and associations, except for incoming
-associations, which are only added to the base, but do not replace the base's
-incoming associations.</p>
-<div class="p"><strong>Replaces rules:</strong><ul><li>Attributes of the base element are replaced with attributes of the replacing
-element including identifier of the base element.</li>
-<li>Outgoing to-one and to-many associations of the replacing element replace
-any outgoing associations of the base element. If the contributor does not
-have any outgoing associations, then neither will the resulting element.</li>
-<li>Incoming associations with a to-many constraint on the other association
-end to the replaced element are preserved and augmented with incoming associations
-of the replacing element.</li>
-<li>Incoming associations with a to-one constraint on the other association
-end to the replaced element are replaced with the respective incoming association
-of the replacing element. If the replacing element does not have such an association
-then the resulting element keeps the incoming association of the base element.</li>
-<li>A base element of a replacement can have only one replacing element per
-configuration. If more than one replacing element is present, no replacement
-takes place.</li>
-<li>Replacement works transitively, i.e. if a replacing element is replaced
-itself, the final replacer prevails.</li>
-<li>Contribution precedes Replacement, i.e. contribution is evaluated first
-and then replacement performed afterward. The evaluation of contribution and
-replacement is performed top-down in the specialization hierarchy.</li>
-</ul>
-See <a href="variabilityassociations.html#variabilityassociations">Variability Associations</a> for more information on the associations for each element
-type.</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-<div><a href="extends.html#extends">Extends</a></div>
-<div><a href="contributes.html#contributes">Contributes</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/report.html b/1.5/plugins/org.eclipse.epf.help.doc/html/report.html
deleted file mode 100644
index d253a2b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/report.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Report" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="report" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Report</title>
-</head>
-<body id="report"><a name="report"><!-- --></a>
-
-<h1 class="topictitle1">Report</h1>
-<div><p>A Report is a predefined template of a result that is generated on the
-basis of other work products as an output from some form of tool automation.
-For example, a report may combine a graphical model from a design tool with
-textual information documents into a report.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/reusableasset.html b/1.5/plugins/org.eclipse.epf.help.doc/html/reusableasset.html
deleted file mode 100644
index ae0114e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/reusableasset.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Reusable Asset" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="reusableasset" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Reusable Asset</title>
-</head>
-<body id="reusableasset"><a name="reusableasset"><!-- --></a>
-
-<h1 class="topictitle1">Reusable Asset</h1>
-<div><p>A reusable asset provides a solution to a problem for a given context.
-The asset has rules for usage which are the instructions describing how the
-asset should be used.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/richtexteditor.html b/1.5/plugins/org.eclipse.epf.help.doc/html/richtexteditor.html
deleted file mode 100644
index f5c1a42..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/richtexteditor.html
+++ /dev/null
@@ -1,63 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Rich Text Editor" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="richtexteditor" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Rich Text Editor</title>
-</head>
-<body id="richtexteditor"><a name="richtexteditor"><!-- --></a>
-
-<h1 class="topictitle1">Rich Text Editor</h1>
-<div><p>The Rich Text Editor provides simple text formatting functions
-that allow an author to change how sections of text appear in a published
-Web site. The Rich Text Editor allows individual components of text to be
-changed within the context of the overall style sheet(s) that determine the
-style and format of a published Web site.</p>
-<div class="p">The Rich Text Editor allows you to:<ul><li>Copy, cut and paste text. Simply highlight the text you want to cut or
-copy and then click the Cut <img src="cut.gif" alt="" /> or Copy <img src="copy.gif" alt="" /> buttons. To paste text, place the cursor
-where you want to include the text and then click the Paste button <img src="paste.gif" alt="" />.</li>
-<li>Remove all the contents in the text editor window at once by clicking
-the Clear Content button <img src="clearcontent.gif" alt="" />.</li>
-<li>Change the appearance of your text by making it bold, italicized, or underlining
-it. Highlight the text you want to change and then click the Bold <img src="bold.gif" alt="" />, Italics <img src="italic.gif" alt="" />,
-or Underline <img src="underline.gif" alt="" /> button.</li>
-<li>Create Super or Sub script by clicking the Superscript <img src="superscript.gif" alt="" /> or Subscript <img src="subscript.gif" alt="" /> buttons.</li>
-<li>Add numbered or bulleted lists using the ordered <img src="addordlist_co.gif" alt="" /> or unordered list <img src="addunordlist_co.gif" alt="" /> buttons.</li>
-<li>Indent or Outdent text using the Indent <img src="indent.gif" alt="" /> or Outdent <img src="outdent.gif" alt="" /> buttons.</li>
-<li>Find and replace text. Click the Find/Replace button <img src="findreplace.gif" alt="" />. The Find/Replace dialog box appears. Type the text you
-want to find in the Find field and, if you are replacing that text, type the
-replacement text in the Replace with field. You can search forward or back
-and specify whether you want your search to be case sensitive or search for
-only parts of words.</li>
-<li>Add or create hyperlinks using the Add link button <img src="addlink_co.gif" alt="" />. For more information see <a href="addareferenceorhyperlink.html#addareferenceorhyperlink">Add a Reference or Hyperlink</a>.</li>
-<li>Add images. Click the Add Image button <img src="addimg_co.gif" alt="" />. The Add Image dialog box appears. Browse for the image you'd like
-to add and then click <strong>OK</strong>.</li>
-<li>Add tables. Click the Add Table button <img src="addtable_co.gif" alt="" />. The Add Table dialog box appears. Specify the table parameters
-and then click <strong>OK</strong>.</li>
-</ul>
-</div>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/roadmap.html b/1.5/plugins/org.eclipse.epf.help.doc/html/roadmap.html
deleted file mode 100644
index aa99bd9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/roadmap.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Roadmap" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="roadmap" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Roadmap</title>
-</head>
-<body id="roadmap"><a name="roadmap"><!-- --></a>
-
-<h1 class="topictitle1">Roadmap</h1>
-<div><p>A Roadmap is a specific type of guidance that describes how a process is
-typically performed. Often process can be much easier understood by providing
-a walkthrough with a linear thread of a typical instantiation of the process.
-In addition to making the process practitioner understand how work in the
-process is being performed, a roadmap provides additional information about
-how activities and tasks relate to each other over time. </p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/role.html b/1.5/plugins/org.eclipse.epf.help.doc/html/role.html
deleted file mode 100644
index 0aabd9f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/role.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Role" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html#createarole" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="role" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Role</title>
-</head>
-<body id="role"><a name="role"><!-- --></a>
-
-<h1 class="topictitle1">Role</h1>
-<div><p>A Role defines a set of related skills, competencies, and responsibilities
-of an individual or individuals.</p>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createarole.html#createarole">Create a Role</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/roleset.html b/1.5/plugins/org.eclipse.epf.help.doc/html/roleset.html
deleted file mode 100644
index 79bbc1c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/roleset.html
+++ /dev/null
@@ -1,46 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Role Set" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="roleset" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Role Set</title>
-</head>
-<body id="roleset"><a name="roleset"><!-- --></a>
-
-<h1 class="topictitle1">Role Set</h1>
-<div><p>A Role Set is used to group <a href="role.html#role">Roles</a> with
-certain commonalities together. For example, in a software development environment,
-an Analyst role set could be used to group together roles such as Business
-Process Analyst, System Analyst and Requirements Specifier. Each of these
-roles work with similar techniques and have overlapping skills, but may be
-responsible for performing certain tasks and creating certain work products.
-Role sets can be organized using Role Set Groupings.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/rolesetgrouping.html b/1.5/plugins/org.eclipse.epf.help.doc/html/rolesetgrouping.html
deleted file mode 100644
index fc75fb0..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/rolesetgrouping.html
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Role Set Grouping" />
-<meta name="DC.Relation" scheme="URI" content="roleset.html#roleset" />
-<meta name="DC.Relation" scheme="URI" content="role.html" />
-<meta name="DC.Relation" scheme="URI" content="createarole.html#createarole" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="rolesetgrouping" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Role Set Grouping</title>
-</head>
-<body id="rolesetgrouping"><a name="rolesetgrouping"><!-- --></a>
-
-<h1 class="topictitle1">Role Set Grouping</h1>
-<div><p>Role sets can be categorized into role set groupings. For example, different
-method might define similar Role Sets which, however, need to be distinguished
-from each other on a global scale. Thus, Role Set Groupings allow distinguishing,
-for example, Software Services Manager Role sets from Software Development
-Organization Manager Role Sets.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="roleset.html#roleset">Role Set</a></div>
-<div><a href="role.html">Role</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createarole.html#createarole">Create a Role</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethcont.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethcont.JPG
deleted file mode 100644
index d9c50df..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethcont.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethodcontent.html b/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethodcontent.html
deleted file mode 100644
index 58d2555..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/searchformethodcontent.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="task" />
-<meta name="DC.Title" content="Search for Method Content" />
-<meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" />
-<meta name="DC.Relation" scheme="URI" content="userinterfaceoverview.html" />
-<meta name="DC.Relation" scheme="URI" content="browseandpreviewmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="searchformethodcontent" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Search for Method Content</title>
-</head>
-<body id="searchformethodcontent"><a name="searchformethodcontent"><!-- --></a>
-
-<h1 class="topictitle1">Search for Method Content</h1>
-<div><div class="section">To Search for Method Content:</div>
-<ol><li class="stepexpand"><span>There are three ways to begin your search for method content.</span><ul><li>Select <strong>Search > Search</strong></li>
-<li><strong>Search > File</strong></li>
-<li>Click the Search button <span class="uicontrol"><img src="searchformethcont.JPG" alt="" /></span> in the tool bar.</li>
-</ul>
- The Search dialog window opens.</li>
-<li class="stepexpand"><span>Click either the <strong>File Search</strong> tab or the <strong>Method Search</strong> tab
-and then set your criteria. Using the <strong>File Search</strong> tab, you can search
-for content by the file name of the content. Using the <strong>Method Search</strong> tab,
-you can search the method content itself.</span><ul><li><strong>Using File Search</strong>: Type a text string to search for within
-the files (optional), or type a file name pattern to use for matching file
-names. You must use a pattern. Use * if you want to search for the text in
-all files. Leave all other options as default.</li>
-<li><strong>Using Method Search</strong>: Type a text string to search for within
-the files (optional), or type a name pattern for matching element names and
-presentation names. You must use a pattern. Use * if you want to search for
-text in all files. In the Scope section, you can restrict your search to a
-subset of element types.</li>
-</ul>
-</li>
-<li class="stepexpand"><span>Click <strong>Search</strong>. The Search View opens with your search results.</span></li>
-<li class="stepexpand"><span>In the Search View, you can drill down into the search results
-and double-click an element to open the editor for the selected element. If
-you have Link with Editor selected in the library view, the library view display
-changes to show you where the selected element is in the library.</span></li>
-</ol>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="userinterfaceoverview.html" title="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:">Tool Interface</a></div>
-<div class="previouslink"><strong>Previous topic:</strong> <a href="browseandpreviewmethodcontent.html">Browse and Preview Method Content</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/standardmethodlibraryoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/standardmethodlibraryoverview.html
deleted file mode 100644
index f9baeae..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/standardmethodlibraryoverview.html
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Standard Method Library Overview" />
-<meta name="abstract" content="A Method Library is a physical container for method plug-ins and method configuration definitions. All method elements are stored in a method library." />
-<meta name="description" content="A Method Library is a physical container for method plug-ins and method configuration definitions. All method elements are stored in a method library." />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="standardmethodlibraryoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Standard Method Library Overview</title>
-</head>
-<body id="standardmethodlibraryoverview"><a name="standardmethodlibraryoverview"><!-- --></a>
-
-<h1 class="topictitle1">Standard Method Library Overview</h1>
-<div><p>A Method Library is a physical container for method plug-ins and
-method configuration definitions. All method elements are stored in a method
-library.</p>
-<p>Much like a library has books, a method library has method plug-ins. Where
-a library book is made up of sections or chapters and content within those
-chapters, <a href="methodplugin.html#methodplugin">method
-plug-ins</a> are made up of <a href="methodcontent.html#creatingreusablemethodcontents">method content</a> and processes. Method content contains
-content packages and both <a href="methodcontentcategories.html#methodcontentcategories">standard and custom categories</a>, while processes structure
-this content into process fragments called <a href="capabilitypattern.html#capabilitypattern">capability patterns</a> and full lifecycle processes called <a href="deliveryprocess.html">delivery processes</a>.</p>
-<p>A method library also has one or more <a href="methodconfigurations.html#methodconfigurations">method configurations</a> that filter the library and provide
-smaller working sets of library content for the end user.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/step.html b/1.5/plugins/org.eclipse.epf.help.doc/html/step.html
deleted file mode 100644
index 11ed0ac..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/step.html
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Step" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="step" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Step</title>
-</head>
-<body id="step"><a name="step"><!-- --></a>
-
-<h1 class="topictitle1">Step</h1>
-<div><p>A Step is a part of the overall work described for a task. The collection
-of steps defined for a task represents all the work that should be done to
-achieve the overall goal of the task. Not all steps are necessarily performed
-each time a task is invoked in a process.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/subscript.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/subscript.gif
deleted file mode 100644
index 1033c83..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/subscript.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/superscript.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/superscript.gif
deleted file mode 100644
index a3675ca..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/superscript.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/supportingmaterial.html b/1.5/plugins/org.eclipse.epf.help.doc/html/supportingmaterial.html
deleted file mode 100644
index c1c6d15..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/supportingmaterial.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Supporting Material" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="supportingmaterial" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Supporting Material</title>
-</head>
-<body id="supportingmaterial"><a name="supportingmaterial"><!-- --></a>
-
-<h1 class="topictitle1">Supporting Material</h1>
-<div><p>Supporting Material is a catch-all for other types of guidance
-not specifically defined elsewhere. It can be related to all kinds of content
-elements, including other guidance elements.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/task.html b/1.5/plugins/org.eclipse.epf.help.doc/html/task.html
deleted file mode 100644
index ec55775..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/task.html
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Task" />
-<meta name="DC.Relation" scheme="URI" content="createatask.html#createatask" />
-<meta name="DC.Relation" scheme="URI" content="createmethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="task" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Task</title>
-</head>
-<body id="task"><a name="task"><!-- --></a>
-
-<h1 class="topictitle1">Task</h1>
-<div><p>A Task is an assignable unit of work. Every Task is assigned to a specific
-Role. The granularity of a Task is generally a few hours to a few days and
-usually affects one or only a small umber of Work Products.</p>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createatask.html#createatask">Create a Task</a></div>
-<div><a href="createmethodcontent.html">Create Method Content</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/template.html b/1.5/plugins/org.eclipse.epf.help.doc/html/template.html
deleted file mode 100644
index 5557110..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/template.html
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Template" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="template" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Template</title>
-</head>
-<body id="template"><a name="template"><!-- --></a>
-
-<h1 class="topictitle1">Template</h1>
-<div><p>A Template is a specific type of guidance that provides a work product
-with a predefined table of contents, sections, packages, and/or headings,
-a standardized format, as well as descriptions of how the sections
-and packages are supposed to be used and completed. Templates can be provided
-for documents as well as conceptual models or physical data stores.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/termdefinition.html b/1.5/plugins/org.eclipse.epf.help.doc/html/termdefinition.html
deleted file mode 100644
index 1d5a356..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/termdefinition.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Term Definition" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="termdefinition" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Term Definition</title>
-</head>
-<body id="termdefinition"><a name="termdefinition"><!-- --></a>
-
-<h1 class="topictitle1">Term Definition</h1>
-<div><p>Term definitions defines a specific term, concept, or other idea relevant
-to method and process content. A term definition is not directly related to
-any content elements, but relationships are derived when the term is used
-in the description text in a content element.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/toolmentor.html b/1.5/plugins/org.eclipse.epf.help.doc/html/toolmentor.html
deleted file mode 100644
index 613ef40..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/toolmentor.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Tool Mentor" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="toolmentor" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Tool Mentor</title>
-</head>
-<body id="toolmentor"><a name="toolmentor"><!-- --></a>
-
-<h1 class="topictitle1">Tool Mentor</h1>
-<div><p>A Tool Mentor is a specific type of guidance that shows how to use a specific
-tool to accomplish a piece of work.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_1.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_1.htm
deleted file mode 100644
index ef930b8..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_1.htm
+++ /dev/null
@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 1: Explore the User Interface </a></h2>
-<p>The purpose of this exercise is to become familiar with the major parts of the Eclipse Process Framework Composer user interface. </p>
-<ol>
- <li>
- <p>Switch perspective. The current perspective is displayed near the top right of the screen. You will see either Authoring or Browsing. Click on the <strong>Open Perspective</strong> icon, and select the other perspective. </p>
- </li>
- <li>
- <p>Explore the <strong>Library</strong> <strong>View</strong>. The library view is available in authoring perspective – it is not shown in the browsing perspective. The Library View shows you all the content in the current library. The highest level content unit is a plugin. Click on some <strong>+</strong> signs and explore the content. </p>
- </li>
- <li>
- <p>Drill down into a plugin as follows: <strong>Method Content > Content Packages > [any] > Tasks</strong>. Double click on a task. The Task Editor is displayed on the right of the screen. There are separate editors for the different types of content that you can create in a library. Each editor has a series of tabs and a number of form elements on each tab. You can find out more about these in the <u>Create Method Content </u>tutorial. </p>
- </li>
- <li>
- <p>Click the <strong>Preview </strong> tab. A preview of an HTML page is displayed. This is what the selected element will look like in a published web site. </p>
- </li>
- <li>
- <p>Switch to the <strong>browsing perspective</strong>. The Configuration View is now displayed. The configuration view always has the same structure but the content changes based on which configuration is currently selected. Drill down into the Disciplines folder until you get to tasks and click on a task. The HTML preview of the selected item is shown on the right of the screen. </p>
- </li>
- <li>
- <p>Switch configurations. The current configuration is displayed in the selection box below the main menu bar. Select a configuration from the drop down list. You will see the Configuration View refresh when you do this. </p>
- </li>
- <li>Switch to the <strong>authoring</strong> <strong>perspective</strong>. Drill down into a plugin as follows: <strong>Processes > Capability Patterns > [any] > Capability Patterns</strong>. Note that not all plugins have capability patterns. Double-click on a capability pattern. The right side of the screen is now filled with the Capability Pattern editor and the Properties View. You can find out more about these in the <u>Working with Processes</u> tutorial.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_2.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_2.htm
deleted file mode 100644
index 407a920..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_2.htm
+++ /dev/null
@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 2: Browse Method Content via Browsing Perspective </a></h2>
-<p>The purpose of this exercise is to become familiar with browsing method content in a library using the browsing perspective. </p>
-<ol>
- <li>
- <p>Select <strong>RUP for Small Projects </strong> in the current configuration drop-down list located underneath the main menu bar. </p>
- </li>
- <li>
- <p>Select <strong>Browsing perspective</strong>. The Configuration View appears on the left. </p>
- </li>
- <li>
- <p>To view a Task, click <strong>Disciplines > RUP Disciplines > Analysis & Design > Design the User Interface</strong>. A preview of the published Web page for the selected element is displayed. </p>
- </li>
- <li>
- <p>Click the <strong>Primary Performer </strong>link in the relationships section. This will show the preview page for the User-Interface Designer. </p>
- </li>
- <li>
- <p>You can click on any links in the preview and use the back icon in the preview toolbar to return to previous pages. </p>
- </li>
- <li>
- <p>View other elements in the Configuration View tree – e.g. under Domains, Role Sets, etc. </p>
- </li>
-</ol>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_3.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_3.htm
deleted file mode 100644
index 1e11a81..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_3.htm
+++ /dev/null
@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 3: Browse Process Content via Browsing Perspective </a></h2>
-<p> The purpose of this exercise is to become familiar with browsing process content in a library using the browsing perspective </p>
-<ol>
- <li>
- <p>Make sure you are in the Browsing perspective. </p>
- </li>
- <li>
- <p>To view a Capability Pattern, click <strong>Processes > Capability Patterns > Classic RUP > Discipline Workflows > Analysis and Design</strong>. A preview of the published Web page for the selected Capability Pattern is displayed. </p>
- </li>
- <li>A Capability Pattern contains a large amount of information and is displayed over four tabs – Description, Work Breakdown Structure, Work Product Usage and Team Allocation. Explore the information on each tab.
- <p>Note that when you click on a task in the Work Breakdown Structure tab you preview a ‘Task Descriptor'. A Task Descriptor is a task within a process. The task descriptor page has information about the task as it is used at a specific point in a process. The task descriptor has a link to the Task on which it is based. </p>
- <p>Clicking on a role or work product in a task descriptor takes you to a Role Descriptor or a Work Product Descriptor. These provide information about the role or work product at the same point in the process and also provide links back to the core method element on which they are based. </p>
- </li>
- <li>To view a Delivery Process, click <strong>Processes > Delivery Processes > Classic RUP Lifecycle</strong>. The display for a Delivery Process is similar to a Capability Pattern. </li>
-</ol>
-<p> </p>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_4.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_4.htm
deleted file mode 100644
index 1b6f45b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_4.htm
+++ /dev/null
@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 4: Browse Method Content via Authoring Perspective </a></h2>
-<p> The purpose of this exercise is to become familiar with browsing library content while in the authoring perspective. </p>
-<ol>
- <li>
- <p>Switch to Authoring perspective. </p>
- </li>
- <li>
- <p>In the Library View, navigate to <strong>RUP > Method Content > Content Packages > Design > GUI Design > Role</strong>s. </p>
- </li>
- <li>
- <p>Select a role (double click) and use the preview tab at the bottom of the role window to view the html representation of that role and its relationships to other method elements. View the other tabs to see the information presented when authoring the method content and relationships for a role. </p>
- </li>
- <li>
- <p>Repeat step 3 to preview a <strong>task</strong> , <strong>work product</strong>, and <strong>guidance element</strong>. </p>
- </li>
-</ol>
-<p> </p>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_5.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_5.htm
deleted file mode 100644
index 61451c7..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_ex_5.htm
+++ /dev/null
@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 5: Search for Method Content </a></h2>
-<p>The purpose of this exercise is to become familiar with the search function in Eclipse Process Framework Composer. </p>
-<ol>
- <li>
- <p>Switch to <strong>Authoring </strong>perspective. </p>
- </li>
- <li>Open up the Search dialog by : </li>
- <blockquote>
- <p>• Clicking on the Flashlight icon in the toolbar </p>
- <blockquote>
- <blockquote>
- <p><strong>Or </strong></p>
- </blockquote>
- </blockquote>
- <p>• Selecting <strong>Search / Search</strong> in the main menu. </p>
- </blockquote>
- <li>
- <p>Click on the <strong>Method Search</strong> tab. Enter <span class="style1">Database</span> in the text box and click on <strong>Search</strong>. It will take a few seconds to find all the hits. </p>
- </li>
- <li>
- <p>Drill down in the search results and double-click on an element. The editor for the selected item is opened. If you have <strong>Link with Editor</strong> selected in the library view, the library view display changes to show you where the selected item is in the library. </p>
- </li>
- <li>
- <p>Open the search dialog again and repeat the same search but this time reduce the scope to just look for tasks. Uncheck all the other content types in the scope panel. The search should be quicker and result in fewer hits. </p>
- </li>
- <li>
- <p>Open the search dialog again and repeat the same search but this time add <strong>rup_*</strong> as a file name pattern. Make sure the scope is still set to tasks. The search should be even quicker and result in even fewer hits. </p>
- </li>
- <li>Experiment with other Method Searches.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_intro.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_intro.htm
deleted file mode 100644
index 65a2deb..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_intro.htm
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h1><a>Tutorial:
-
-
- Navigate the User Interface
-
-</a></h1>
-<h2><a>Introduction </a></h2>
-<p>The purpose of this tutorial is to get familiar with user interface and the way method and process content is stored and viewed. </p>
-<p>A Method Library consists of a series of <strong><em>method plug-ins. </em></strong>Within a plugin, content is separated into <strong><em>Method Content </em></strong> (tasks, roles, work products and guidance) and <strong><em>Processes </em></strong> (capability patterns and delivery processes). This is how the Library View, which shows all the content in the library is organized. </p>
-<p>A configuration is a subset of the method library content. The Configuration View shows the content in the currently selected configuration. Once a configuration is selected, the configuration view is refreshed with the content from the configuration. The content in the configuration view is always laid out using the same set of folders regardless of which configuration is selected. </p>
-<p>EPF Composer has two ‘perspectives'. The Authoring Perspective provides full browsing and authoring capabilities. The Browsing Perspective allows browsing content in the currently selected configuration. </p>
-<p>Content is created and maintained using a series of <strong><em>editors. </em></strong></p>
-<h2> </h2>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_1.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_1.htm
deleted file mode 100644
index 4d41c82..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_1.htm
+++ /dev/null
@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a></a><a>Exercise 1: Create or Modify a Method Content Package </a></h2>
-<p>The purpose of this task is to create a new <strong>Content Package </strong> within a <strong>Method Plug-in</strong>. </p>
-<p>To create a new Method Plug-in: </p>
-<ol>
- <li>
- <p> Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>Click <strong>File > New > Method Plug-in</strong>.
- <p>Or </p>
- <p>Right-click an existing Plug-in and select <strong>New Method Plug-in</strong>. <br>
- The New Method Plug-in wizard is launched. </p>
- </li>
- <li>
- <p>In the New Method Plug-in wizard, provide a name for the new plug-in. In this instance, we'll call it My Plugin. </p>
- </li>
- <li>
- <p>Select <strong>RUP </strong> in the Referenced Plug-ins panel, and then click <strong>Finish</strong>. This means that your plug-in will extend the RUP plug-in and you will be able to select content from the RUP plug-in as you create your own plug-in content. <br>
- <span class="style1">My Plugin</span> now appears in the Library View on the left side of your screen. It is not grayed out indicating that it is not locked and that you can edit it. </p>
- </li>
- <li>Double click on <span class="style1">My Plugin</span> to open the Plugin editor. About halfway down the page you will see the ‘Lock Plugin' checkbox. This will be unchecked for your new plugin. If you open the plugin editor for the RUP plugin this field will be checked. </li>
-</ol>
-<p>To create a Method Package: </p>
-<ol start="6">
- <li>
- <p>In the Library View, click <strong>My Plugin > Method Content > Content Packages</strong>. </p>
- </li>
- <li>
- <p>Right-click <strong>Content Packages</strong>. </p>
- </li>
- <li>
- <p> Highlight <strong>New</strong> and then click <strong>Content Package</strong> to create a new Content Package. <br>
- The Content Package editor is displayed and you can name the package and provide a Brief Description. We'll call it “My Content Package”. <br>
- <strong>Note: </strong> You cannot create a new Content Package or any other element in a locked plugin. </p>
- </li>
- <li>Save your new content. </li>
-</ol>
-<p><strong>Note: </strong> When you create a new element or modify an existing element, a ‘*' appears in the tab next to the name of the element, indicating that the element needs to be saved. An element can be saved by closing the editor, clicking the disk icon in the toolbar, or clicking <strong>File > Save </strong>. </p>
-<p><strong>Note: </strong> EPF Composer automatically creates nodes for tasks, roles, work products and guidance under the new content package. </p>
-<h1> </h1>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_2.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_2.htm
deleted file mode 100644
index e9f4557..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_2.htm
+++ /dev/null
@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a></a><a>Exercise 2: Create Work Product</a>s </h2>
-<p>The purpose of this exercise is to create new method content. Specifically, <strong>Work Products </strong>of type <strong> Artifact </strong>. You can create any content but some examples are provided if you want to use them. These examples are referred to in other tutorials. </p>
-<p>Method and Process elements have two names in EPF Composer: Name and Presentation Name. </p>
-<p>The Name field is used as the file name for the item. In RUP, we are careful how we name the files and use conventions such as lower case, no spaces, and no special characters. We do this so that the name is a valid file name on all operating systems and for integration with source control software in the future. The Name is shown in the Library View. </p>
-<p>The Presentation Name is the name that is shown on published pages and it is also shown in the Configuration View. This name can contain any characters, but by convention in RUP, we use the same text as the Name, just prettier. </p>
-<p>In the Library view you can choose to display Names or Presentation Names. You can switch the name display using the ‘Show Presentation Names' button in the Library view toolbar. </p>
-<p>In general, you create new elements by right-clicking the folder that will contain the new element. For example, to create a new role in a content package, right-click the <strong>Roles </strong> folder, highlight <strong>New </strong> and then click <strong>Role</strong>. </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Within <span class="style1">My Content Package</span> right-click on the <strong>Work Products</strong> folder. </p>
- </li>
- <li>
- <p> Highlight <strong>New</strong> and then click <strong>Artifact</strong>. The artifact editor is displayed. </p>
- </li>
- <li>
- <p> In the Name field, type the new Artifact name. In this instance, we'll call it <strong>my_rup_navmap</strong>. </p>
- </li>
- <li> In the <strong>Presentation Name</strong> field, type: </li>
- <blockquote>
- <p>My RUP Navigation Map</p>
- </blockquote>
- <li>In the <strong>Brief Description</strong> field, type:
- <blockquote>
- <p>The Navigation Map expresses the structure of the user-interface elements in the system, along with their potential navigation pathways.</p>
- </blockquote>
- </li>
- <li> In the <strong>Purpose</strong> field type:
- <blockquote>
- <p>There is one Navigation Map per system. The purpose of the Navigation Map is to express the principal user interface paths through the system. These are the main pathways through the screens of the system and not necessarily all of the possible paths. It can be thought of as a road map of the system's user interface. The Navigation Map makes it easy to see how many "clicks" it will take a user to get to a specific screen. </p>
- </blockquote>
- </li>
- <li>
- <p>Click the preview tab to view the new Artifact. </p>
- </li>
- <li>
- <p> Save the Artifact. </p>
- </li>
- <li> Repeat steps 2 through 9 using the following information:
- <blockquote>
- <p>• <strong>Artifact Name</strong>: my_rup_user_interface_prototype </p>
- <p>• <strong>Presentation Name</strong>: My RUP UI Prototype </p>
- <p>• <strong>Brief Description</strong>: A user-interface prototype is an example of the user interface that is built in order to explore and/or validate the user-interface design. </p>
- <p>• <strong>Purpose: </strong> The following roles use the user-interface prototype: </p>
- <blockquote>
- <p>- <strong>user-interface designers</strong> , to explore and/or validate the user-interface design before too much is invested in it </p>
- <p>- <strong>requirements specifiers </strong>, to understand the user interface for a Use Case </p>
- <p><strong>- system analysts </strong>, to understand how the user interface impacts the analysis of the system </p>
- <p>- <strong>designers </strong>, to understand how the user interface impacts and what it requires from the "inside" of the system </p>
- <p> - <strong>managers </strong>, to plan development and testing activities </p>
- </blockquote>
- </blockquote>
- </li>
-</ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3.htm
deleted file mode 100644
index c8d6e84..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3.htm
+++ /dev/null
@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a>Exercise 3: Create Roles </a></h2>
-<p>To create a Role in My Content Package: </p>
-<ol>
- <li>
- <p> Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>Within My Content Package right-click on the <strong>Roles </strong> folder. </p>
- </li>
- <li>
- <p>Highlight <strong>New </strong> and then click <strong>Role</strong>. </p>
- </li>
- <li>
- <p>In the <strong>Name field </strong> type: my_rup_user_interface_designer. </p>
- </li>
- <li>
- <p>In the <strong>Presentation Name</strong> field type: My UI Designer. </p>
- </li>
- <li>In the <strong>Brief Description </strong> field type: </li>
- <blockquote>
- <p>The user-interface designer coordinates the design of the user interface. User-interface designers are also involved in gathering usability requirements and prototyping candidate user-interface designs to meet those requirements. </p>
- <p><strong>Tip </strong> - there are different ways that you can create the text above for the new role: </p>
- <blockquote>
- <p>• Directly, by typing it manually in the EPF Composer editor. </p>
- <p>• By copying from another similar role and then modify using the editors (e.g. rup_user_interface_designer). </p>
- • By copying from an html source such as the tutorial you are reading. </blockquote>
- </blockquote>
- <li> Try the <strong>Rich Text Editor </strong> for editing the <strong>Main Description. </strong>You can open the Rich Text Editor for any item that has a ‘twisty' <img width="13" height="13" src="tutorial_2_ex_3_clip_image002.gif">symbol
- <blockquote>
- <p>• The user-interface designer role is not responsible for implementing the user interface. Instead, this role focuses on the design and the "visual shaping" of the user interface, by: </p>
- </blockquote>
- </li>
- <ol>
- <blockquote>
- <p> - Capturing requirements on the user interface, including usability requirements. </p>
- <p>- Building user-interface prototypes.</p>
- <p>- Involving other stakeholders of the user interface, such as end-users, in usability reviews and use testing sessions. </p>
- <p>- Reviewing and providing the appropriate feedback on the final implementation of the user interface, as created by other developers; that is, designers and implementers. </p>
- </blockquote>
- </ol>
- <blockquote>
- <p><strong>Note</strong> – if you copy text from a Microsoft Word document you will get a lot of formatting information that is not needed in Eclipse Process Framework Composer. You can see this if you open the HTML editor in the Rich Text Editor. </p>
- </blockquote>
- <li>
- <p>Click the <strong>WorkProducts </strong> tab; make this new role responsible for the my_rup_navmap and my_rup_user_interface_prototype artifacts that you previously created. </p>
- </li>
- <li>
- <p>Click the <strong>Add </strong> button. This displays a selection dialog where you can select the Work Products to add. </p>
- </li>
- <li>Once you have selected the appropriate Work Products, click <strong>OK</strong>. The work products you selected appear in the <strong>Responsible for: </strong> panel.
- <blockquote>
- <p>Note that selected elements in an Add/Remove section display both the element name and the ‘path' to that element – the Plugin name and package name. </p>
- </blockquote>
- </li>
- <li>Click the <strong>Preview </strong> tab to view the newly created role and then save by closing the editor. </li>
-</ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3_clip_image002.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3_clip_image002.gif
deleted file mode 100644
index bb2fc81..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_3_clip_image002.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_4.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_4.htm
deleted file mode 100644
index 15f921c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_4.htm
+++ /dev/null
@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a></a><a>Exercise 4: Create Tasks </a></h2>
-<p>The purpose of this exercise is to create a task and then relate that task to the other elements you have created. </p>
-<p>To create a Task in My Content Package: </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Within My Content Package right-click on the <strong>Tasks </strong> folder. </p>
- </li>
- <li>
- <p> Highlight <strong>New </strong> and then click <strong>Task</strong>. </p>
- </li>
- <li>Use the following information to create the task: </li>
- <blockquote>
- <p>• <strong>Task: </strong> my_design_user_interface </p>
- <p>• <strong>Presentation Name </strong>: My Design User Interface </p>
- <p>• <strong>Brief Description: </strong> To produce a design of the user interface that supports the reasoning about, and the enhancement of, its usability. </p>
- <p>• <strong>Steps </strong>(Use steps tab):</p>
- <blockquote>
- <p>- Describe the characteristics of related users </p>
- - Identify the primary user interface elements </blockquote>
- <p>• <strong>Roles (Primary Performer): </strong>my_rup_user_interface_designer </p>
- <p>• <strong>Work Products (Mandatory Input) </strong> rup_software_requirement (under requirements) <strong></strong></p>
- <p>• <strong>Work Products </strong> (Outputs): my_rup_navmap </p>
- <p>• <strong>Guidance: </strong>representing_graphical_user-interfaces (under gui_design) <strong></strong></p>
- • <strong>Categories: </strong>rup_analysis_design_discipline <strong></strong></blockquote>
- <li>
- <p>Click the <strong>Preview </strong> tab to view the newly created task and save by closing the editor. </p>
- </li>
- <li> Create another task using the following information:
- <blockquote>
- <p>• <strong>Task: </strong> my_prototype_user_interface </p>
- <p>• <strong>Presentation name </strong>: My Prototype User Interface </p>
- <p>• <strong>Brief Description: </strong> To prototype the system's user interface in an attempt to validate the user-interface design against the functional and usability requirements. </p>
- <p>• <strong>Steps: </strong></p>
- <blockquote>
- <p>- Design the user interface prototype </p>
- <p>- Implement the user interface prototype </p>
- </blockquote>
- <p>• <strong>Roles (Primary Performer): </strong>my_rup_user_interface_designer </p>
- <p>• <strong>Work Products (Mandatory Input) </strong> my_rup_navmap </p>
- <p>• <strong>Work Products (Outputs): </strong>my_rup_user_interface_prototype </p>
- <p>• <strong>Categories: </strong>rup_analysis_design_discipline </p>
- </blockquote>
- </li>
- </ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_5.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_5.htm
deleted file mode 100644
index dcadeaf..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_5.htm
+++ /dev/null
@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a></a><a>Exercise 5: Working with Steps </a></h2>
-<p>The purpose of this exercise is to understand the Step Editor that is part of the Task Editor. </p>
-<p>When you create a task, you can define a series of steps that detail how to perform the task. The Step Editor allows you to add new steps, change the sequence of steps and to delete steps. </p>
-<ol>
- <li>
- <p>Open the my_design_user_interface task or create a new task. Click on the <strong>Steps</strong> tab. </p>
- </li>
- <li>Create a new step: </li>
- <blockquote>
- <p>• Enter a name for the step in the ‘Steps' box. </p>
- <p>• Enter a <strong>Description </strong> – you can use the Rich Text Editor for this. </p>
- <p>• Click the <strong>Add </strong> button. </p>
- <p>• See the results on the <strong>Preview </strong> tab. </p>
- </blockquote>
- <li> Remove a step : </li>
- <blockquote>
- <p>• Return to the <strong>Steps</strong> tab. </p>
- <p>• Click the step to remove in the Steps panel. </p>
- <p>• Click the <strong>Delete </strong> button. </p>
- <p>• See the results on the <strong>Preview </strong> tab. </p>
- </blockquote>
- <li> Move a step up the list: </li>
- <blockquote>
- <p>• Return to the <strong>Steps</strong> tab. </p>
- <p>• Click the step you want to move up.</p>
- <p>• Click the <strong>Up </strong> button.</p>
- <p>• See the results on the <strong>Preview </strong> tab. </p>
- </blockquote>
- <li>Move a step down the list : </li>
- <blockquote>
- <p>• Return to the <strong>Steps</strong> tab. </p>
- <p>• Click the step you want to move down.</p>
- <p>• Click the <strong>Down </strong> button.</p>
- <p>• See the results on the <strong>Preview </strong> tab. </p>
- </blockquote>
-</ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_6.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_6.htm
deleted file mode 100644
index 4912df5..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_6.htm
+++ /dev/null
@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a></a><a></a><a>Exercise 6: Create Guidance </a></h2>
-<p>The purpose of this exercise is to create method <strong>Guidance </strong> elements. There is a range of different types of guidance that can be created. For this task we will simply create a representative guidance element, a checklist. Once you have done this, try authoring additional Guidance types. </p>
-<p>In a checklist, Check Items are created in the same way as Steps in a task are created using the <strong>Check Items </strong> tab in the <strong>Checklist Editor</strong>. </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>Within <span class="style1">My Content Package</span> right-click on the <strong>Guidance </strong> folder. </p>
- </li>
- <li>
- <p>Highlight <strong>New </strong> and then click <strong>Checklist</strong>. </p>
- </li>
- <li>
- <p>Name the guidance, my_create_physical_appearance_checklist, and provide the presentation name, My Create Physical Appearance Checklist. </p>
- </li>
- <li> Add the following check items: </li>
- <blockquote>
- <p>• Create branding specifications </p>
- <p>• Define physical specifications </p>
- </blockquote>
- <li>Add the checklist to the <strong> my_prototype_user_interface </strong>task and then look for it on the preview page. </li>
-</ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_7.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_7.htm
deleted file mode 100644
index 09d460f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_7.htm
+++ /dev/null
@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a></a><a></a><a></a><a>Exercise 7: Manage Guidance </a></h2>
-<p>Guidance can be attached to any Core Method Content or Process Element. Guidance can even be attached to a Guidance element. </p>
-<p>The goal of this exercise is to carry out some simple guidance management tasks (i.e., adding and removing guidance.)</p>
-<ol>
- <li>
- <p>Navigate to the artifact <strong>my_rup_navmap </strong> that you created in exercise 2 in this tutorial. </p>
- </li>
- <li> Add the Concept Paper <strong>process_view </strong> from the RUP plug-in. </li>
- <blockquote>
- <p>The list of items in the Select Dialog is restricted to just those items that are allowed to be added. The list can be long though. You can enter a search string, such as ‘pro' in the ‘Name patterns' box to filter the items that are displayed. Note that you can use the Collapse All and Expand All buttons on this dialog to change the way the tree is displayed. </p>
- </blockquote>
- <li>
- <p>Add <strong>my_create_physical_appearance_checklist </strong> Checklist. </p>
- </li>
- <li>
- <p>Click the <strong>Preview </strong> tab to view your work. </p>
- </li>
- <li>
- <p>Remove the Concept Paper process_view. </p>
- </li>
- <li>Click the <strong>Preview </strong> tab to view your work. </li>
-</ol>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_8.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_8.htm
deleted file mode 100644
index 3d23694..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_8.htm
+++ /dev/null
@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a></a><a></a><a></a><a></a><a></a><a>Exercise 8: Create New Standard Category </a></h2>
-<p>The purpose of this exercise is to understand and use <strong>Standard Categories. </strong>In practice, this will not be done very often, as Standard Categories tend to be relatively stable. Also, if you are creating a plug-in that extends RUP, you should attempt to use the RUP Standard Categories before creating new ones. </p>
-<p><strong>Standard Categories </strong> provide a means to categorize core method content in line with best practices for creating structured methods. In order to encourage good method structure we provide standard categories for grouping <strong>Tasks </strong>into <strong><em>Disciplines </em></strong>, <strong>Work Products </strong> into <strong><em>Domains </em></strong>, <strong>Roles </strong> into <strong><em>Role Sets </em></strong>, and <strong>Tool-Mentors </strong> into <strong><em>Tools </em></strong>. Unlike <strong><em>Custom </em> Categories </strong>, <strong>Standard Categories </strong> by definition are linked with a specific method content type – e.g. Role Sets with Roles, Disciplines with Tasks, and Domains with Work Products. </p>
-<ol>
- <li>
- <p>Click <strong>My Plugin > Method Content > Standard Categories</strong>. </p>
- </li>
- <li>
- <p> Create a new <strong>Role Set </strong>named <span class="style1">my_design</span> with a presentation name of <span class="style1">My Design</span>. </p>
- </li>
- <li> Add the role <span class="style1">my_rup_user_interface_designer</span> to the<span class="style1"> my_design</span> <strong>Role Set</strong>. </li>
-</ol>
-<blockquote>
- <p>There are two ways you can do this: </p>
- <blockquote>
- <p>• In the Standard Category editor for <span class="style1">my_design</span>, open the <strong>Roles</strong> tab, and add the role to the roleset. </p>
- <p>• In the Role editor for <span class="style1">my_rup_user_interface_designer</span>, open the <strong>Categories</strong> tab and add the <span class="style1">my_design</span> category as a Selected Roleset. </p>
- </blockquote>
-</blockquote>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_9.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_9.htm
deleted file mode 100644
index ee78930..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_ex_9.htm
+++ /dev/null
@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a></a><a></a><a></a><a></a><a>Exercise 9: </a>Adding Your Plug-in to the Configuration View </h2>
-<p>The purpose of this exercise is to learn how to include your plug-in in a configuration. </p>
-<p>Before your new elements can be seen in the Configuration View, you need to first add your new plug-in to a configuration. We'll add the new plug-in to the Config for RUP configuration and see the results in the Configuration View. </p>
-<ol>
- <li>
- <p>Switch to the <strong>Browsing </strong>perspective and in the <strong>Configuration View </strong>try to find your new content. For example look for My Design Roleset. You shouldn't see it. </p>
- </li>
- <li>
- <p> Switch to the <strong>Authoring </strong>perspective and then click <strong>Configurations </strong> at the bottom of the tree display. </p>
- </li>
- <li>
- <p> Make a copy of the <strong>RUP for Small Projects </strong> configuration. Right-click on the <strong>RUP for Small Projects </strong> configuration and select <strong>Copy </strong>. Then right-click on the Configurations folder and click <strong>Paste </strong>. Name the new configuration <strong>My RUP for Small Projects. </strong></p>
- </li>
- <li>
- <p> Double-click on the <strong>My RUP for Small Projects </strong> configuration to open the Configuration Editor. </p>
- </li>
- <li>
- <p> Click on the <strong>Plug-in and Package Selection</strong> tab. </p>
- </li>
- <li>
- <p> Add <strong>My Plugin </strong> to the configuration by checking the box next to it in the Configuration Components field. If you expand <strong>My Plugin </strong> you will see that the full contents of the plug-in have been selected.
- You may see some errors in the Library Error Log view. You can click through these errors or ignore them for now. </p>
- </li>
- <li>
- <p> Close the editor and save the changes. </p>
- </li>
- <li>
- <p> Change the current configuration to <strong>My RUP for Small Projects </strong>in the configuration selection box in the EPF Composer toolbar, just below the main menu bar. </p>
- </li>
- <li> Switch to the <strong>Browsing </strong> perspective and now look for your content in the <strong>Configuration View</strong>. You should now see <strong>My Design Roleset </strong>. You should also see your new Work Products in the Uncategorized folder under Domains. </li>
-</ol>
-<blockquote> </blockquote>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_intro.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_intro.htm
deleted file mode 100644
index b3eca88..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_intro.htm
+++ /dev/null
@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h1><a>Tutorial: Create Method Content </a></h1>
-<h2><a>Introduction </a></h2>
-<p>EPF Composer separates reusable <strong>method content </strong> from its application in <strong>processes </strong>. The primary method content elements are <strong>tasks </strong>, <strong>roles </strong>, <strong>work products </strong> and <strong>guidance </strong>. A Process Engineer uses EPF Composer to author these elements, define the relationships between them, and to categorize them. Method content provides step-by-step explanations, describing how specific development goals are achieved independent of the placement of these steps within a development lifecycle. Processes take these method elements and relate them into semi-ordered sequences that are customized to specific types of projects. </p>
-<p>EPF Composer supports the concept of <strong>Method Plug-ins </strong> that allows the extension or customization of base library content without directly changing that base content. When we ship a library with EPF Composer the library is protected from direct modification. The RUP plugins are grayed out in the Library view indicating that they are locked. </p>
-<p><strong>You should always create new content in a Method Plug-in that you produce. </strong>This separates your content from the original OpenUP content and allows you to update your own library with new releases of the OpenUP library without affecting the content that you have created in your own plug-ins. </p>
-<p>In this tutorial you will use several ‘editors'. Each editor opens in its own tab in the content display section of the screen. It is good practice to close an editor when you have finished with it. This ensures that you save any changes you make. </p>
-<p>If you do have several editors open, you may want to turn on the ‘Link with Editor' feature by clicking on the Link with Editor button in the Library view toolbar. If this is selected, when you switch between editors, the element in the current editor is highlighted in the Library view. </p>
-<p>The following exercises take you through the creation of “core method content”. </p>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_1.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_1.htm
deleted file mode 100644
index a289b09..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_1.htm
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 1: Adding to base method content associated with a role using Contribution </a></h2>
-<p>The purpose of this exercise is to extend a role in RUP using ‘contribution'. </p>
-<ol>
- <li>
- <p>Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>This exercise adds content to the My Plugin plugin. If you have not carried out the ‘Create Core Method Content tutorial, create it now. </p>
- </li>
- <li>
- <p>Create a Content Package in the My Plugin plug-in called <span class="style1">Contribution</span> Test. </p>
- </li>
- <li>
- <p>In the new Contribution Test content package, create a new Role: <span class="style1">my_contributing_ui_designer</span>. </p>
- </li>
- <li>
- <p>Page down the Description tab to the Content Variability section and then, in the <strong>Variability Type </strong>, select <strong>Contributes </strong> and choose the base role: <strong>rup_user_interface_designer </strong>. You will find this in <strong>RUP > Design > GUI Design</strong>. </p>
- </li>
- <li> Complete the following: </li>
- <blockquote>
- <p>• Add Brief Description: Contributing brief description text </p>
- <p>• Add Main Description : Contributing main description text </p>
- <p>• Save (by closing the role editor). </p>
- </blockquote>
- <li>
- <p>Create a new Configuration by selecting the <strong>Configurations </strong> folder in the Library View tree. </p>
- </li>
- <li>
- <p>Right click the folder to create new configuration and then name the configuration <span class="style1">Variability Configuration</span>. </p>
- </li>
- <li>
- <p> Select the RUP base and your plug-in (My Plugin) by marking the checkboxes. Save the configuration (close the configuration tab). </p>
- </li>
- <li>
- <p>Set “current configuration” – located under main menu bar as “Variability Configura tion”. </p>
- </li>
- <li>
- <p>Switch to the <strong>Browsing</strong> perspective and then open the User-Interface Designer role. </p>
- </li>
- <li> You should see the text that you included in the Contributing role displayed in the User-Interface Designer. </li>
-</ol>
-<blockquote>
- <p><strong>Note: </strong> The Configuration View resolves the variability relationships between related plug-ins in a configuration and shows the results as they will be published in a published web site. </p>
-</blockquote>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_2.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_2.htm
deleted file mode 100644
index 937973e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_2.htm
+++ /dev/null
@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 2: Adding to base method content associated with a work product using <u>Contribution</u> </a></h2>
-<p>The purpose of this exercise is to extend a <strong>Work Product </strong> (<strong>Artifact</strong>) in RUP using ‘contribution'. </p>
-<ol>
- <li>
- <p>Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Within the Contribution Test package create a new artifact called <span class="style1">my_contributing_navmap</span>. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description, Main Description</strong>, <strong>Purpose</strong>, etc., : <span class="style1">Contributing Brief Description, Contributing Main Description, and Contributing Purpose</span>. </p>
- </li>
- <li>
- <p> In <strong>Variability Relationship </strong> select <strong>Contributes </strong>, and for <strong>base artifact </strong> select <span class="style1">rup_navmap</span>. Save by closing the Work Product editor. </p>
- </li>
- <li>
- <p> Switch to the Browsing perspective and view the Navigation Map artifact in the <strong>Analysis and Design Domain </strong> folder in <strong>Configuration View. </strong></p>
- </li>
- <li> You should see the text that you included in the Contributing role displayed in the User-Interface Designer. </li>
-</ol>
-<blockquote> </blockquote>
-<h2> </h2>
-<h1> </h1>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_3.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_3.htm
deleted file mode 100644
index 344d90c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_3.htm
+++ /dev/null
@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 3: Adding base method content associated with a task using <u>Contribution</u> </a></h2>
-<p>The purpose of this exercise is to extend a <strong>Task </strong> in RUP using ‘contribution'. </p>
-<ol>
- <li>
- <p>Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>Within the <span class="style1">Contribution Test </span>package create a new <strong>Task</strong>: <span class="style1">my_contributing_design_user_interface</span>. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description, Main description </strong>, <strong>Purpose</strong>, etc.,: <span class="style1">Contributing Brief Description text, Contributing Main Description text, and Contributing Purpose text. </span></p>
- </li>
- <li>
- <p> Add two new steps: <span class="style1">Contributing Step 1 </span>and<span class="style1"> Contributing Step 2</span>. </p>
- </li>
- <li>
- <p> In <strong>Variability Relationship </strong> select <strong>Contributes</strong>, and for base <strong>task </strong> select, <span class="style1">design_user_interface</span>. </p>
- </li>
- <li>
- <p> Go back to the <strong>Steps </strong> tab and click the <strong>Order </strong> button. You can now insert your new steps into the original steps. </p>
- </li>
- <li>
- <p>Save the new task by closing the task editor. </p>
- </li>
- <li>
- <p> Switch to the Browsing perspective and view the <span class="style1">Design the User Interface</span> task in the <strong>Disciplines </strong> folder in <strong>Configuration View </strong>. You will find it under the <span class="style1">Analysis_& Design</span> discipline. </p>
- </li>
- <li>
- <p> Look at the descriptions and the steps to see how your new material was contributed. You should see the text that you included in the Contributing role displayed in the User Interface task. </p>
- </li>
- <li> You can also try specifying additional <strong>artifacts </strong>, <strong>guidance </strong>, <strong>additional performer roles</strong>, etc., in the contributing task (in Authoring perspective) and then view the result in the Configuration View to see the behavior. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_4.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_4.htm
deleted file mode 100644
index 845ce43..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_4.htm
+++ /dev/null
@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 4: Extending base method content associated with a role using <u>Extends</u> </a></h2>
-<p>The purpose of this exercise is to extend base method content via extends variability. Extends variability works differently than Contributes variability in that the method content element that extends the base method element inherits the attributes of the extended base element. </p>
-<ol>
- <li>
- <p> Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Create a new <strong>Content Package </strong> in the My Plugin Plug-in called Extends Test. </p>
- </li>
- <li>
- <p> Create a new <strong>Role </strong>: <span class="style1">my_extends_ui_designer,</span> with the presentation name, <span class="style1">Extends RUP UI Designer</span>. </p>
- </li>
- <li>
- <p> In the Variability Type select <strong>Extends </strong> and choose the base role: <span class="style1">rup_user_interface_designer</span>. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description</strong>: Extends Role Brief Description. </p>
- </li>
- <li>
- <p> Add a <strong>Main Description </strong>: Extends Role Main Description. </p>
- </li>
- <li>
- <p> Save the new role by closing the role editor. </p>
- </li>
- <li> Update the Variability Configuration to include the new content package. </li>
- <blockquote>
- <p> • Open the <span class="style1">Variability Configuration</span> and expand <strong>My Plugin > Method Content > Content Packages. </strong> </p>
- <p>• Uncheck Contribution Test. </p>
- <p>• Make sure <strong>Extends Test </strong>is checked. This is done so there that are no conflicting extensions to the same method element. </p>
- <p>• Close and save the changes to the configuration. </p>
- </blockquote>
- <li>
- <p> Switch to <strong>Browsing </strong> perspective. </p>
- </li>
- <li> In the <strong>Configuration View</strong>, select the <span class="style1">Extends RUP UI Designer role</span> in the Uncategorized Roles folder under the “<strong>Role Sets</strong>” folder. You will see in the html page that content entered in the extending role has been replaced, whereas content not provided has been inherited from the base artifact. Note that the extended role <span class="style1">User-Interface Designer</span> remains unchanged. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_5.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_5.htm
deleted file mode 100644
index 44b851f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_5.htm
+++ /dev/null
@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 5: Extending base method content associated with a Work Product using <u>Extends</u> </a></h2>
-<p>The purpose of this exercise is to extend a base method work product using extends variability. </p>
-<ol>
- <li>
- <p> Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Create a new <strong>Work Product </strong> in the <span class="style1">Extends Test</span> Content Package called <span class="style1">my_extends_rup_navmap</span> with the presentation name, <span class="style1">Extends RUP Navmap</span>. </p>
- </li>
- <li>
- <p> In the <strong>Variability Type </strong> select <strong>extends </strong> and choose the base <strong>Work Product </strong><span class="style1">rup_navmap</span>. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description </strong>: Extends Navmap Brief Description. </p>
- </li>
- <li>
- <p> Save and then switch to the <strong>Browsing </strong> perspective. </p>
- </li>
- <li>In the <strong>Configuration View</strong>, select the <span class="style1">Extends RUP Navmap</span> work product in the <strong>Uncategorized Folder </strong> under <strong>Domains </strong>. You will see in the html page that content entered in the extending artifact has been replaced, whereas content not provided has been inherited from the base artifact. Note that the extended artifact <span class="style1">Navigation Map</span> remains unchanged.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_6.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_6.htm
deleted file mode 100644
index 8db4c51..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_6.htm
+++ /dev/null
@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 6: Extending base method content associated with a Task using <u>Extends</u> </a></h2>
-<p>The purpose of this exercise is to extend a base method task using extends variability. </p>
-<ol>
- <li>
- <p> Create a new <strong>task </strong> in the Extends Test content package called <span class="style1">my_extends_design_user_interface</span>, with presentation name, <span class="style1">Extends Design User Interface. </span></p>
- </li>
- <li>
- <p> In the <strong>Variability Type, </strong> select <strong>extends </strong> and choose the base task design_user_interface. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description </strong>: <span class="style1">Extends Task Brief Description</span>. </p>
- </li>
- <li>
- <p> Add <strong>Steps </strong>: <span class="style1">Extend Step 1, Extend Step 2 </span></p>
- </li>
- <li>
- <p> Add the <strong>Role </strong> created in exercise 4: <span class="style1">my_extends_ui_designer</span>, as Primary Performer. </p>
- </li>
- <li>
- <p> Add the Work Product created in exercise 5: <span class="style1">my_extends_rup_navmap</span>, as an Output. </p>
- </li>
- <li>
- <p> Add <strong>Guidance </strong>(choose any guidance) </p>
- </li>
- <li>
- <p> Add the <strong>task </strong> to the appropriate Standard Category: <span class="style1">rup_analysis_design_discipline</span>. </p>
- </li>
- <li>
- <p> Save and then switch to the <strong>Browsing </strong> perspective. </p>
- </li>
- <li>In the <strong>Configuration View</strong>, select the <span class="style1">Extends Design User Interface</span> task under the <strong>Disciplines </strong> folder in the <span class="style1">Analysis & Design</span> discipline. You will see in the html page that method content and relationships have been inherited from the base task and extended by the plug-in extending content and relationships. Note that the extended task remains unchanged.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_7.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_7.htm
deleted file mode 100644
index a115d46..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_ex_7.htm
+++ /dev/null
@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 7: Extending base method content using <u>Replace</u> variability </a></h2>
-<p>The purpose of this exercise is to extend base method content using replace variability. </p>
-<ol>
- <li>
- <p>Switch to the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Create a new <strong>content package </strong> named, <span class="style1">Replace Test</span>, in the My Plugin plug-in. </p>
- </li>
- <li>
- <p> Create a new <strong>role </strong>: <span class="style1">my_replace_ui_designer role</span> with presentation name, <span class="style1">My Replace UI Designer</span>. </p>
- </li>
- <li>
- <p> In the <strong>Variability Type </strong> select <strong>replaces </strong> and then choose the <strong>base role </strong>: <span class="style1">rup_user_interface_designer</span>. </p>
- </li>
- <li>
- <p> Add a <strong>Brief Description </strong>: <span class="style1">Replace Brief Description.</span> </p>
- </li>
- <li>
- <p> Add a <strong>Main Description </strong>: <span class="style1">Replace Main Description</span>. </p>
- </li>
- <li>
- <p> Save the role by closing the role editor. </p>
- </li>
- <li> Update the Variability Test Configuration: </li>
- <blockquote>
- <p> • Open the Variability Configuration and expand <strong>My Plugin > Method Content > Content Packages</strong>. </p>
- <p>• Uncheck <strong>Extends Test</strong>. </p>
- <p>• Check <strong>Replace Test</strong>. This is done so there are no conflicting extensions in the same method element. </p>
- </blockquote>
- <li>
- <p> Switch to the <strong>Browsing </strong> perspective. </p>
- </li>
- <li>In the <strong>Configuration View</strong>, you will see that there is no longer a (RUP) <span class="style1">User-Interface Designer</span> role in the <strong>Role Sets </strong> folder. It was replaced by <span class="style1">My Replace UI Designer</span> role. Moreover, other content elements in the base plug-in that referenced the (RUP) <span class="style1">User-Interface Designer</span> role now reference the replacing role instead (e.g., if you open the disciplines folder and view the task <span class="style1">Design The User Interface</span> you will see that the <strong>Performing Role </strong> is now <span class="style1">My Replace UI Designer</span>.) <strong>Replace </strong> works in a similar way for <strong>tasks</strong>, <strong>artifacts </strong>, <strong>guidance </strong> and <strong>categories </strong> (feel free to try it out). </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_intro.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_intro.htm
deleted file mode 100644
index c1a78ca..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_intro.htm
+++ /dev/null
@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a></a><a></a><a></a><a></a></h2>
-<h1><a></a><a>Tutorial: Create Reusable Method Content </a></h1>
-<p>The purpose of this tutorial is to understand the variety of ways in which the content in a base plug-in can be extended and modified by content in other plug-ins. </p>
-<p>The ‘Create Core Method Content' tutorial shows how to create new content in a plug-in. In this tutorial we will see how to extend existing content in a plug-in. </p>
-<p><strong>Note: </strong>In the following exercises we create separate Content Packages to demonstrate each of the ways that a method plug-in can modify content in another plug-in (i.e. extends, replaces, and/or contributes). This is for easy illustration of the effect of applying each type of method element variability. </p>
-Managing content via the Method Plug-in mechanism is a key and very powerful feature of EPF Composer. This tutorial explores the effects of the different variability types in the following exercises.
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_1.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_1.htm
deleted file mode 100644
index 346333c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_1.htm
+++ /dev/null
@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 1: Publishing a pre-defined configuration </a></h2>
-<p>The purpose of this exercise is to publish a <strong>Configuration </strong>that is included in Eclipse Process Framework Composer. </p>
-<ol>
- <li>
- <p> Select the <strong>Authoring </strong> perspective. </p>
- </li>
- <li> In the <strong>Library View</strong>, open the Configurations folder and select the configuration: My RUP for Small Projects. This opens the Configuration Editor.
- <p>The Plug in and Package Selection tab shows the plug-ins and packages within each plug-in that are included in the Configuration. The plug-ins and packages in the Configuration can be adjusted by selecting and deselecting them in the tree display. </p>
- </li>
- <li> Review <strong>Configuration </strong><strong>Views </strong>: (i.e. how the published site will be laid out).
- <p>Select the <strong>Views </strong> tab in the configuration editor. A View is a Custom Category that is designed for publication. Required packages and content elements are assigned to a Custom Category. The Custom Category can then be added as a View to a Configuration. </p>
- </li>
- <li> Select <strong>Default</strong> View.
- <p>One of the views can be selected as the Default View by selecting the View and clicking the ‘Make Default' button. When the configuration is published, the Default View will be selected when the published configuration is opened in the EPF Composer Browser. </p>
- </li>
- <li>
- <p> Close the configuration editor. </p>
- </li>
- <li>
- <p> Select <strong>My RUP for Small Projects</strong> in the configuration selection box in the EPF Composer toolbar. </p>
- </li>
- <li>
- <p> Select <strong>Configuration > Publish </strong> from the main menu bar. </p>
- </li>
- <li> Step through Publish wizard, accepting the defaults, and publish the configuration. It will take a few minutes to generate the web site. Assuming that you have the right java environment, the EPF Composer Browser applet should launch allowing you to view the resulting published web site (accept the security warnings when the applet fires up). </li>
-</ol>
-<blockquote>
- <p><strong>Note: </strong> The published web site has a richer organization and lay-out as defined by the Configuration View, as compared to the more simple view of the configuration content available within the EPF Composer <strong>Configuration View</strong>. </p>
-</blockquote>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_2.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_2.htm
deleted file mode 100644
index acc8e37..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_2.htm
+++ /dev/null
@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 2: Create New Custom Category </a></h2>
-<p>The purpose of this exercise is to understand and use <strong>Custom Categories </strong>. </p>
-<p><strong>Custom Categories </strong> allow you to categorize content according to any scheme you want. Custom Categories can then be used to compose publishable <strong>Views </strong> providing a means to organize method content prior to publishing. </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p> Navigate to <strong>My Plug-in > Method Content > Custom Categories</strong>. If you have not already created this plugin, create it now, or go through the <u>Create Core Method Content</u> tutorial. </p>
- </li>
- <li>
- <p> Create a new custom category named, <span class="style1">my_custom_category</span>. Right-click on the <strong>Custom Categories</strong> folder, highlight <strong>New, </strong> and then click <strong>Custom Category </strong>. </p>
- </li>
- <li> Open the <strong>Assign </strong> tab. If you have previously created <span class="style1">my_content_packag</span>e, add the <strong>roles </strong>, <strong>artifacts</strong>, <strong>tasks, </strong> and <strong>guidance </strong> from it into the custom category. If you do not have this package, add content from another area in the library. </li>
- <blockquote>
- <p><strong>Note: </strong> You can do multiple select using shift or control key . </p>
- </blockquote>
- <li>
- <p> Add the <span class="style1">rup_analysis_design_discipline</span>. You will find this under <strong>RUP > Disciplines > rup_disciplines. </strong></p>
- </li>
- <li> Open one of the elements you assigned to the new custom category. Observe how the custom category is now reflected in the <strong>Categories </strong> tab. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_3.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_3.htm
deleted file mode 100644
index 64d139b..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_3.htm
+++ /dev/null
@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<style type="text/css">
-<!--
-.style1 {font-family: "Courier New", Courier, mono}
--->
-</style>
-</head>
-
-<body>
-<h2><a>Exercise 3: Create a customized configuration </a></h2>
-<p>The purpose of this exercise is to create your own customized configuration. </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>Click <strong>File > New > Configuration</strong>. Or, you can right-click on the <strong>Configurations</strong> folder in the Library View and select <strong>New Configuration. </strong>The Configuration Editor is launched.</p>
- </li>
- <li>
- <p> Name the configuration, <span class="style1">my_configuration</span>.</p>
- </li>
- <li>
- <p> Click on the <strong>Plug-in and Package Selection </strong> tab. In the list of Plugins, check My Plugin that you created in the <u>Create Core Method Content</u> tutorial. This plugin has RUP as a base and references parts of the RUP content, and also has elements that extend, contribute to, and replace base RUP content. <br>
- If you do not have this plugin, consider completing the <u>Create Core Method Content</u> tutorial before continuing with this tutorial. </p>
- </li>
- <li>
- <p> The display will give you a series of warnings and the Library Error Log view will be displayed. <br>
- Eclipse Process Framework Composer gives these warnings to help ensure that you create a configuration that ‘makes sense'. If you reference an element, you will only be able to see the full details for that element in a published web site if the package containing the element is in the configuration. If the package containing the element is not in the configuration, the ‘offending' package is marked as a warning – you may choose not to include the full details of the referenced element. </p>
- </li>
- <li>
- <p> Check the <strong>Add Missing References</strong> button. This will automatically and recursively add packages containing any elements that are referenced in already selected packages. Explore what packages have been added to the configuration. You will probably now see all of RUP selected. This is because of the inter-connected nature of RUP. Uncheck RUP to restore the warnings. </p>
- </li>
- <li>
- <p> Drill down into the content packages in the My Plugin, plugin package by clicking on the <strong>+</strong> signs. Uncheck the<strong> Extends Test </strong>and <strong>Replace Test </strong>content packages. Unchecking these avoids conflicts that may occur because the same base element is affected by the plugins. </p>
- </li>
- <li>
- <p> There should be a <strong>+</strong> by the <strong>Contribution Test</strong> package. Click the <strong>Make Closure by Fixing Errors</strong> button. This automatically makes your configuration complete based on what is currently selected. </p>
- </li>
- <li>
- <p> Drill down into the RUP plugin, and see what packages have been selected. These will be the packages that contain the elements used as base elements in the Configuration Test content package. </p>
- </li>
- <li> Click on the <strong>Views</strong> tab.
- <p>Any custom category can be added as a view to a configuration. You can created any number of custom categories and they are very flexible in terms of the content that you can add to a custom category and in the order in which the content appears. </p>
- <p>Add the <span class="style1">my_custom_category</span> custom category as a view in the configuration. </p>
- <p>Experiment with adding other custom categories as views. </p>
- </li>
- <li>
- <p> Make <span class="style1">my_custom_category</span> the default view by selecting the <span class="style1">my_custom_category</span> tab and clicking the <strong>Make Default</strong> button. </p>
- </li>
- <li>
- <p> Save the configuration by closing the Configuration Editor. </p>
- </li>
- <li>
- <p> Select <span class="style1">my_configuration</span> in the configuration selection box at the top of the screen. You will see the items displayed in the Configuration View change. </p>
- </li>
- <li> Switch to the <strong>Browsing</strong> perspective. Explore the content in the configuration view. You should see the content you created in your plugins and some RUP content. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_4.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_4.htm
deleted file mode 100644
index 7d8be1d..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_ex_4.htm
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 4: Publishing a custom configuration </a></h2>
-<ol>
- <li>
- <p> Select <strong>Configuration > Publish </strong> from the main menu bar. </p>
- </li>
- <li>
- <p> Select my-configuration in the list of configurations. </p>
- </li>
- <li> Step through Publish wizard, accepting the defaults, and publish the configuration. It will take a few minutes to generate the web site. Assuming that you have the right java environment, the EPF Composer Browser applet should launch allowing you to view the resulting published web site (accept the security warnings when the applet fires up). </li>
-</ol>
-<blockquote>
- <p><strong>Note: </strong> The published web site has a richer organization and lay-out as defined by the Configuration View, as compared to the more simple view of the configuration content available within the EPF Composer <strong>Configuration View </strong>. </p>
-</blockquote>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_intro.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_intro.htm
deleted file mode 100644
index 421db7e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_intro.htm
+++ /dev/null
@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h1><a>Tutorial: Publishing and Exporting </a></h1>
-<p>EPF Composer is essentially a content management application. The ultimate output of EPF Composer is a Web site with published method guidance and processes that can be viewed by a project team. </p>
-<p>EPF Composer makes it easy to configure a process for a particular type or size of project and to publish the guidance to a Web site. A Method <strong>Configuration </strong> is a selection of <strong>Content Packages </strong> across different <strong>Method Plug-ins </strong> containing the method and process content that will be included in the published web site. At publishing time, the configuration is combined with different Method <strong>Views </strong> which define the website's navigation structures and content organization. </p>
-<p>The EPF Composer <strong>Browsing Perspective </strong> renders the Method <strong>Configuration </strong> content in html format within EPF Composer, providing a navigable representation of the method/process content associated with that Configuration. </p>
-<p>This tutorial uses content that is created in the ‘Create Core Method Content' and ‘Extending base method content using Variability' tutorials. </p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_1.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_1.htm
deleted file mode 100644
index 0b2b81e..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_1.htm
+++ /dev/null
@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 1: Browse Process Content using Browsing Perspective </a></h2>
-<p>The purpose of this exercise is to get a basic understanding of processes in EPF Composer. </p>
-<p>(Note that this is a repeat of exercise 2 in the <u>Browse the Library</u> tutorial.) </p>
-<ol>
- <li>
- <p>Make sure you are in the <strong>Browsing</strong> perspective. </p>
- </li>
- <li>
- <p> Select the <strong>My RUP for Small Projects</strong> configuration. If you have not created this configuration, select the <strong>RUP for Small Projects</strong> configuration. </p>
- </li>
- <li>
- <p> To view a Capability Pattern, click <strong>Processes > Capability Patterns > Classic RUP > Discipline Workflows > Analysis and Design</strong>. A preview of the published Web page for the selected Capability Pattern is displayed. </p>
- </li>
- <li>
- <p> A Capability Pattern contains a large amount of information and is displayed over four tabs – <strong>Description, Work Breakdown Structure, Work Product Usage, </strong>and<strong> Team Allocation</strong>. Explore the information on each tab. </p>
- </li>
- <li>To view a Delivery Process, click <strong>Processes > Delivery Processes > Classic RUP Lifecycle</strong>. The display for a Delivery Process is similar to a Capability Pattern. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_2.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_2.htm
deleted file mode 100644
index 518efa9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_2.htm
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a>Exercise 2: Explore a Process using Authoring perspective </a></h2>
-<p>The purpose of this tutorial is to explore the information and editors for processes. A Capability Pattern is used as an example but the same applies to Delivery Processes. </p>
-<ol>
- <li>
- <p>Switch to <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>In the Library View, click <strong>RUP > Processes > Capability Patterns > Classic RUP > Discipline Workflows</strong>. </p>
- </li>
- <li>
- <p>Double click the <strong>Analysis and Design Capability Pattern</strong> and examine the Capability Pattern. </p>
- </li>
- <li>The <strong>Description</strong> tab provides a number of sections that can be used to fully describe the Capability Pattern.
- <p>A Capability Pattern or Delivery Process must be associated with at least one configuration but can be associated with many. The configuration sets the scope for core method content and other process elements that can be included in a process. </p>
- </li>
- <li> Click the <strong>Work Breakdown Structure</strong> tab.
- <p>This shows the Activities in the Capability Pattern and the (core method content) tasks that are included in each Activity. </p>
- <p>When a task is added to a process, the roles and work products that are associated with the task are also pulled into the process. </p>
- <p>Each task, role, and work product shown in the activity is actually an instance of the element as it is used at the particular point in the process. So what you see in the process are actually Task Descriptors, Role Descriptors and Work Product Descriptors. </p>
- </li>
- <li> Click the <strong>Team Allocation</strong> tab.
- <p>This shows the activities in the capability pattern and the roles that are the performers of the tasks in the activities. </p>
- </li>
- <li> Click the <strong>Work Product Usage</strong> tab.
- <p>This shows the activities in the capability pattern and the work products that are input and outputs of the tasks in the activities. </p>
- </li>
- <li> Click on the <strong>Consolidated View</strong> tab.
- <p>This shows the full set of information for each activity in the Capability Pattern. It shows the tasks, work products and roles within each activity. </p>
- </li>
- <li> Right click any <strong>task </strong> in the <strong>Work Breakdown Structure view, </strong> and click on <strong>Show Properties View</strong>.
- <p>This displays a new view that shows all the information about the task (task descriptor) as it is used in the process and allows you to customize the task as it is used at this point in the process. </p>
- <p>The Properties View has a number of tabs that organize the task descriptor information. </p>
- </li>
- <li>
- <p>Click on the <strong>Documentation</strong> tab. This allows you to enter information that is specific to this Task Descriptor. </p>
- </li>
- <li>
- <p>Click on the <strong>Roles</strong> tab. This allows you to replace, remove or add to the roles that are associated with the core method task for this specific instance of the task in the process. </p>
- </li>
- <li>
- <p>Click on the <strong>Work Products</strong> tab. This allows you to replace, remove or add to the work products that are associated with the core method task for this specific instance of the task in the process. </p>
- </li>
- <li>
- <p>Click on the <strong>Steps</strong> tab. This allows you to adjust the task steps as they are applied at this point in the process. </p>
- </li>
- <li>
- <p>When a role is selected in the Team Allocation view, or a work product is selected in the Work Product Usage view, the Properties View allows you to edit these elements in the context of the process. </p>
- </li>
- <li>Click on an <strong>Activity</strong> in the process. <br>
- The properties view allows you to see roll-ups of the tasks, roles, and work products in the activity. Roll-ups can also be displayed in the main content window by selecting the <strong>Roll-Up</strong> option in the context sensitive menu. The Roll-Up view can be turned off by selecting, <strong>Roll-Down</strong>. </li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_3.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_3.htm
deleted file mode 100644
index 5435afe..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_3.htm
+++ /dev/null
@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a>Exercise 3: Create a Delivery Process </a></h2>
-<p>The purpose of this exercise is to learn how to create a delivery process using core method content directly. </p>
-<p>In <strong>Process Authoring </strong> we do not directly include the definitions of the core method elements in the WBS but rather create local references termed <strong>descriptors </strong> that refer back to the elements in the method library but also contain additional information that is only relevant to the local process. </p>
-<p>Descriptors also provide a mechanism whereby relationships defined in core method authoring (e.g. roles associated with a task, input and output, work products, etc.), can be defined or changed locally within the process. </p>
-<ol>
- <li> Create a new Delivery Process in the My Plugin, plug-in called, My RUP. </li>
- <blockquote>
- <p>When you create a process you are asked to identify the default Configuration to be used with the process. Select the My RUP for Small Projects configuration. If you nave not created this configuration, select RUP for Small Projects. </p>
- <p>A process has a hierarchy of activities and can include the special types of activity – Phases and Iterations. These structures can also be created in Capability Patterns. First of all, we'll create some activities directly and reuse some capability patterns later. </p>
- </blockquote>
- <li>
- <p> To create the Inception Phase, in the Work Breakdown Structure view, right click the <strong>My RUP </strong>Process, and then select, <strong>New Child > Phase </strong>. Call the Phase, <strong>Inception</strong>. </p>
- </li>
- <li>
- <p>To create the Requirements Discipline in Inception, in the <strong>Work Breakdown Structure </strong> view, right click <strong>Inception, </strong> and select <strong>New </strong><strong>Child > Activity </strong>. Call this <strong>Requirements</strong>. </p>
- </li>
- <li>To add Tasks to the Requirements activity, in the <strong>Configuration </strong> view, open the Requirements Discipline and then drag and drop the following tasks onto the Requirements Activity you have just created: </li>
- <blockquote>
- <p>• Develop Vision </p>
- <p>• Detail the Software Requirements </p>
- <p>• Find Actors and use Cases </p>
- <p>When you include these tasks in your process, the associated roles and work products are also included in the process. </p>
- </blockquote>
- <li>
- <p> You can review the information for each method element in the <strong>Properties </strong> view. </p>
- </li>
- <li>
- <p> Customize the steps from the Find Actors and Use Cases task for the Inception phase. Click on the <strong>Find Actors and Use Cases</strong> task descriptor, and open the <strong>Properties</strong> view. Click on the <strong>Steps</strong> tab. Remove the last four steps and close the properties view. </p>
- </li>
- <li>
- <p> Switch to the <strong>Browsing</strong> perspective and select <strong>Processes > Delivery Processes > My RUP</strong>. The Work Breakdown Structure tab is displayed. Click on <strong>Find Actors and Use Cases</strong>. Only the first three steps from the core method task are included. </p>
- </li>
- <li>Make other changes to the tasks in the delivery process you have just created and see how they are reflected when you view the process in the Browsing perspective.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_4.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_4.htm
deleted file mode 100644
index 7260d2a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_4.htm
+++ /dev/null
@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a>Exercise 4: Create a new delivery Process using capability patterns. </a></h2>
-<p>The purpose of this exercise is to learn how to create a delivery process using <strong>Capability Patterns </strong>. </p>
-<p>A Capability Pattern is a process ‘fragment'. It represents a process that can be reused many times in the same process and / or in different processes. Organizing core method content into capability patterns and then using the capability patterns to construct full life-cycle delivery processes is a key feature of Eclipse Process Framework Composer. </p>
-<p>A capability pattern can be included in another process (another capability pattern or a delivery process) in two ways: </p>
-<blockquote>
- <p>• Copy – this creates a full copy of the capability pattern in the target process but does not retain any links back to the original capability pattern. The capability pattern can be customized in the new process. Any changes that are subsequently made to the capability pattern are not reflected in the process into which it was copied. </p>
- <p>• Extends – this extends the capability pattern into the process. The process retains links to the capability pattern and any subsequent changes to the capability pattern are reflected in the process into which it is extended. The capability pattern can be customized by suppressing tasks, roles, and work products. Other changes cannot be made. </p>
-</blockquote>
-<p>We will add some Capability Patterns to the Delivery Process you created in Exercise 3. </p>
-<p>To add a Capability Pattern using Copy: </p>
-<ol>
- <li>
- <p> Switch to the authoring perspective and open the My RUP delivery process you created in Exercise 3. </p>
- </li>
- <li>
- <p> In the Configurations View click <strong>Processes > Capability Patterns > Classic RUP > Discipline Workflows > Project Management. </strong></p>
- </li>
- <li>
- <p> Drag and drop the <strong>Project Management </strong> Capability Pattern onto the Inception phase in My RUP delivery process. </p>
- </li>
- <li>
- <p> Select <strong>Copy </strong> in the pop-up box. </p>
- </li>
- <li> Expand one of the activities in the Project Management capability pattern to the Task level. Note that the task name is displayed in black. This indicates that the task is available for you to edit. Any changes in the Capability Pattern will not be reflected in your process. You can edit the task in the Properties view. </li>
-</ol>
-<p>To add a Capability Pattern using Extends: </p>
-<ol start="6">
- <li>
- <p> Create a new Phase in the My RUP delivery process. Right-click on the first row and select <strong>New Child > Phase </strong>. Call the phase, Elaboration. </p>
- </li>
- <li>
- <p> Create a new Iteration in the Elaboration phase. Right-click on the Elaboration phase and select <strong>New Child > Iteration </strong>. Call the iteration, Elaboration Iteration 1. </p>
- </li>
- <li>
- <p> In the Configurations View, click <strong>Processes > Capability Patterns > Classic RUP > Discipline Workflows > Project Management. </strong></p>
- </li>
- <li>
- <p> Drag and drop the <strong>Project Management </strong> Capability Pattern onto the Elaboration Iteration 1 iteration in My RUP Process. </p>
- </li>
- <li>
- <p> Select <strong>Extend </strong> in the pop-up box. </p>
- </li>
- <li>
- <p> Expand one of the activities in the Project Management capability pattern you have just added to the Task level. Note that the task name is displayed in green italics. This indicates that the task is in a part of a process defined elsewhere – a Capability Pattern. Any changes to the Capability Pattern will be reflected in your process. Also, the Properties view shows the task details, but they cannot be edited. </p>
- </li>
- <li>Right click on a task in the extended capability pattern and select <strong>Suppress </strong>. The task is grayed out. The task will not appear in the published version of the delivery process, nor will it be included in an export of the process.</li>
-</ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_5.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_5.htm
deleted file mode 100644
index 8dbf82f..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_ex_5.htm
+++ /dev/null
@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h2><a></a><a>Exercise 5: Create Process Diagrams </a></h2>
-<p>The purpose of this exercise is to explore the diagram features of Eclipse Process Framework Composer. </p>
-<p>EPF Composer supports three types of process diagram. These are: </p>
-<blockquote>
- <p>• <strong>Activity Diagram</strong> </p>
- <blockquote>
- <p> This shows the (sub) activities in a higher level activity. It shows the sequence relationships between the activities. </p>
- </blockquote>
- <p>• <strong>Activity Detail</strong> – similar to RUP Workflow Detail </p>
- <blockquote>
- <p> This shows the tasks in an activity with their performing roles and input and output work products. </p>
- </blockquote>
- <p>• <strong>Work Product Dependency Diagram</strong> </p>
- <blockquote>
- <p>This diagram can be used to show how a work product is dependent on other work products. </p>
- </blockquote>
-</blockquote>
-<p>These diagrams can then be included in the published web site. The diagrams are automatically generated (to a degree) and inherently synchronized with the WBS. Changes to the process structure using the diagram editor are automatically reflected in the WBS, and vice versa. </p>
-<ol>
- <li>
- <p>Switch to <strong>Authoring </strong> perspective. </p>
- </li>
- <li>
- <p>Select the My RUP delivery process that you have been working on. </p>
- </li>
- <li>
- <p>Highlight the delivery process in the WBS and then right-click. </p>
- </li>
- <li>
- <p>Click <strong>Diagrams > Open Activity Diagram</strong>. The diagram editor should open, showing the top level activities - phases. </p>
- </li>
- <li>
- <p>Expand the <strong>Palette </strong> on the right of the diagram view. All the elements required to create an <strong>Activity Diagram </strong> are available on the palette. Add a new phase to the diagram – call it, Construction. Create links between the phases to show the sequence of the phases. </p>
- </li>
- <li>
- <p>Switch back to the <strong>Work Breakdown Structure </strong>view and notice the new phase. Also notice that the links you added on the diagram are reflected in the Predecessors column. </p>
- </li>
- <li>
- <p>Double click the <strong>Inception Phase</strong> in the diagram – it will drill down to show the contained Activities (the rule is that the editor will display the process elements at the level below the current selected element). Successive drill down through the levels is possible by clicking on the diagram elements. </p>
- </li>
- <li>
- <p>Close the diagrams you have opened. </p>
- </li>
- <li>In the Work Breakdown Structure, right-click on the Requirements activity and select, <strong>Diagrams > Open Activity Detail Diagram. </strong>The Activity Detail Diagram is automatically generated. It shows: </li>
- <blockquote>
- <p>• The Roles that perform tasks in the activity </p>
- <p>• The Tasks that the roles perform </p>
- <p>• The input and output work products for each task </p>
- <p>You can change the layout of the diagram but you cannot add or remove any elements from the diagram. </p>
- </blockquote>
- <li>
- <p>Close the diagrams you have opened. </p>
- </li>
- <li> In the Work Breakdown Structure, right-click on the Requirements activity and select, <strong>Diagrams > Open Work Product Dependency Diagram. </strong>The work products used in the activity are automatically added to the diagram. </li>
-</ol>
-<blockquote>
- <p>Add a (dependency) link between two work products. This indicates that the work product at the arrow end of the link is dependent on the other work product, i.e., the other work product needs to be created in order to create the second work product.
- </p>
- <p>Add a work product descriptor to the diagram. </p>
-</blockquote>
-<ol start="12">
- <li>
- <p>Switch back to the delivery process and open the <strong>Work Product Usage</strong> view. Notice the new work product in the Requirements activity. </p>
- </li>
- <li>
- <p>Once you have edited a diagram, you can choose to include it or exclude it when publishing the process in a configuration. In the Work Breakdown Structure, right-click on the <strong>Requirements</strong> activity and select <strong>Diagrams > Publishing Options. </strong>Check or uncheck the types of diagram listed. If a diagram type is not listed, it means that you have not edited that diagram type for the activity yet. </p>
- </li>
- </ol>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_intro.htm b/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_intro.htm
deleted file mode 100644
index eea3513..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_intro.htm
+++ /dev/null
@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<html>
-<head>
-<title>Untitled Document</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body>
-<h1><a></a><a>Tutorial: Working with Processes </a></h1>
-<p><strong><em>Process Authoring </em></strong> allows a Process Engineer to incorporate <strong><em>Method Elements </em></strong> into process structures. For example, a Work Breakdown Structure format familiar to Project Managers. The processes can be included in a configuration to be published as part of the published web site. </p>
-<p>In <strong><em>Method </em> Authoring </strong> the Process Engineer defines roles, tasks, work products and guidance and defines the relationships between these elements. </p>
-<p>In <strong><em>Process </em> Authoring </strong> the process engineer defines additional lifecycle elements such as <strong>Activities </strong> (summary tasks), <strong>Phases </strong>, <strong>Iterations </strong> and <strong>Milestones </strong>, that can then be used to compose the core elements into processes. A complete process corresponding to a project plan or a phase we call a <strong><em>Delivery Process </em></strong><em>(corresponding to Small RUP, for example) </em>. We can also create smaller more granular sections of process, termed <strong><em>Capability Patterns </em></strong> that can be used as building blocks to more easily compose delivery processes. </p>
-<p>Each time a task is included in a process, a copy of that task is created in the context of the process. We call this a Task Descriptor. The same task can be included any number of times in the same process. This allows, for example, the same RUP task to be included in each Iteration in each RUP Phase. A Task Descriptor can also modify the base task without actually changing the task. For example, roles and work products can be added or suppressed, steps can be suppressed or re-sequenced. </p>
-<p>oles and Work Products are also included in processes as Role Descriptors and Work Product Descriptors. So roles and work products can also be customized to fit with the context of the process in which they are used.</p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/twisty symbol1.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/twisty symbol1.JPG
deleted file mode 100644
index 23b11b3..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/twisty symbol1.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/uma_hump.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/uma_hump.gif
deleted file mode 100644
index 66f4544..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/uma_hump.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/underline.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/underline.gif
deleted file mode 100644
index db768c9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/underline.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/userinterface.JPG b/1.5/plugins/org.eclipse.epf.help.doc/html/userinterface.JPG
deleted file mode 100644
index 0b368aa..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/userinterface.JPG
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/userinterfaceoverview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/userinterfaceoverview.html
deleted file mode 100644
index 4a28395..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/userinterfaceoverview.html
+++ /dev/null
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Tool Interface" />
-<meta name="abstract" content="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:" />
-<meta name="description" content="Eclipse Process Framework Composer is built on the Eclipse Integrated Development Environment (IDE). The parts of the workspace are:" />
-<meta name="DC.Relation" scheme="URI" content="authoringperspective.html#authoringperspective" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html#browingperspective" />
-<meta name="DC.Relation" scheme="URI" content="authoringperspective.html" />
-<meta name="DC.Relation" scheme="URI" content="browsingperspective.html" />
-<meta name="DC.Relation" scheme="URI" content="configurationview.html" />
-<meta name="DC.Relation" scheme="URI" content="libraryview.html" />
-<meta name="DC.Relation" scheme="URI" content="browseandpreviewmethodcontent.html" />
-<meta name="DC.Relation" scheme="URI" content="searchformethodcontent.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="userinterfaceoverview" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Tool Interface</title>
-</head>
-<body id="userinterfaceoverview"><a name="userinterfaceoverview"><!-- --></a>
-
-<h1 class="topictitle1">Tool Interface</h1>
-<div><p>Eclipse Process Framework Composer is built on the Eclipse Integrated
-Development Environment (IDE). The parts of the workspace are:</p>
-<p><img src="userinterface.JPG" alt="" /></p>
-<div class="p"><ul><li><strong>Configuration drop-down selection box</strong> - The configuration drop-down
-selection box allows you to select a <a href="configurationview.html#configurationview">configuration</a> in which to work. </li>
-<li><strong>Open Perspective button</strong> - Click the Open Perspective button
-to select a <a href="perspectives.html#perspectives">perspective</a>.
-There are two perspectives to select from: The <a href="browsingperspective.html#browingperspective">Browsing Perspective</a> and the <a href="authoringperspective.html#authoringperspective">Authoring Perspective</a>. </li>
-<li><strong>Library View</strong> - The <a href="libraryview.html#libraryview">Library
-View</a> displays the Method Plug-ins and Configurations contained in a
-Method Library.</li>
-<li><strong>Configuration View</strong> - The <a href="configurationview.html#configurationview">Configuration View</a> shows the content elements in a library
-filtered by a configuration.</li>
-<li><strong>Content Editors and Preview</strong> - When you are working in the <a href="authoringperspective.html#authoringperspective">Authoring
-Perspective</a>, the window on the right side of your screen contains content
-editors, which allow you to create or modify element types. When the <a href="browsingperspective.html#browingperspective">Browsing
-Perspective</a> is open, the window on the right contains a preview of
-your content as it will appear in a published Web site.</li>
-</ul>
-</div>
-</div>
-<div>
-<ol>
-<li class="olchildlink"><a href="authoringperspective.html">Authoring Perspective</a><br />
-</li>
-<li class="olchildlink"><a href="browsingperspective.html">Browsing Perspective</a><br />
-</li>
-<li class="olchildlink"><a href="configurationview.html">Configuration View</a><br />
-</li>
-<li class="olchildlink"><a href="libraryview.html">Library View</a><br />
-</li>
-<li class="olchildlink"><a href="browseandpreviewmethodcontent.html">Browse and Preview Method Content</a><br />
-</li>
-<li class="olchildlink"><a href="searchformethodcontent.html">Search for Method Content</a><br />
-</li>
-</ol>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="authoringperspective.html#authoringperspective">Authoring Perspective</a></div>
-<div><a href="browsingperspective.html#browingperspective">Browsing Perspective</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/userrolesandrolespecifictasks.html b/1.5/plugins/org.eclipse.epf.help.doc/html/userrolesandrolespecifictasks.html
deleted file mode 100644
index cdf1643..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/userrolesandrolespecifictasks.html
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="topic" />
-<meta name="DC.Title" content="User Roles and Role Specific Tasks" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="userrolesandrolespecifictasks" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>User Roles and Role Specific Tasks</title>
-</head>
-<body id="userrolesandrolespecifictasks"><a name="userrolesandrolespecifictasks"><!-- --></a>
-
-<h1 class="topictitle1">User Roles and Role Specific Tasks</h1>
-<div><p>There are four primary roles played by the users of this tool:</p>
-<ul><li>Method Author</li>
-<li>Process Author</li>
-<li>Process Configurator</li>
-<li>Practitioner</li>
-</ul>
-<div class="p"><strong>Method Author</strong> - The Method Author uses the tool on a regular basis
-to provide standard processes for use in an organization. The Method Author
-uses the full functionality of the tool to:<ul><li>Create plug-ins.</li>
-<li>Create new method elements.</li>
-<li>Extend existing method elements.</li>
-<li>Create reusable capability patterns by reusing method elements.</li>
-<li>Create delivery processes by reusing capability patterns and method elements.</li>
-<li>Create custom categories for use as views in a configuration.</li>
-<li>Create and modify configurations.</li>
-<li>Publish configurations or processes.</li>
-</ul>
-</div>
-<div class="p"><strong>Process Author</strong> - The Process Author's goal is to produce a delivery
-process for their project(s) by reusing method elements. The Process Author
-uses the tool occasionally, as project needs dictate, typically supporting
-one or, more likely, several projects by specifying the processes to be followed.
-The Process Author uses the process authoring and configuration publishing
-functionality of this tool to:<ul><li>Create plug-ins.</li>
-<li>Create reusable capability patterns by reusing method elements.</li>
-<li>Create delivery processes by reusing capability patterns and method elements.</li>
-<li>Create custom categories for use as views in a configuration. </li>
-<li>Create and modify configurations.</li>
-<li>Publish configurations or processes.</li>
-</ul>
-</div>
-<div class="p"><strong>Process Configurator</strong> - The Process Configurator's goal is to produce
-a delivery process for their project(s) by rapidly leveraging ready-made plug-ins.
-The Process Configurator uses this tool occasional, as project needs dictate,
-typically supporting one or several projects by specifying the process for
-the projects. The Process Configurator uses the configuration
-publishing functionality in this tool to:<ul><li>Create and modify configurations.</li>
-<li>Publish configurations or processes.</li>
-</ul>
-</div>
-<p><strong>Practitioner</strong> - A Practitioner's goal is to correctly use the organization's
-processes and best practices effectively. A Practitioner uses a published
-configuration on a regular basis driven by the work being performed to view
-processes and methods.</p>
-</div>
-<div></div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/variability.html b/1.5/plugins/org.eclipse.epf.help.doc/html/variability.html
deleted file mode 100644
index 24aa9b7..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/variability.html
+++ /dev/null
@@ -1,117 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Variability" />
-<meta name="abstract" content="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional." />
-<meta name="description" content="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional." />
-<meta name="DC.Relation" scheme="URI" content="variabilityassociations.html#variabilityassociations" />
-<meta name="DC.Relation" scheme="URI" content="contributes.html" />
-<meta name="DC.Relation" scheme="URI" content="replace.html#replaces" />
-<meta name="DC.Relation" scheme="URI" content="extends.html#extends" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="variability" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Variability</title>
-</head>
-<body id="variability"><a name="variability"><!-- --></a>
-
-<h1 class="topictitle1">Variability</h1>
-<div><p>Variability allows elements in one content package to influence
-or modify elements in other content packages without actually directly modifying
-the original content. Variability enables changes to the content while keeping
-the changes separate and optional.</p>
-<p>Variability allows you to factor your method content and processes in interrelated
-units and to architect method content and processes in layers that extend
-each other with new capabilities. Variability also allows you to extend and
-tailor method content and processes you do not own and cannot directly modify,
-and to easily upgrade to newer versions by simply reapplying your personal
-changes to the upgrades.</p>
-<p>The use of variability affects two characteristics of a method element:
-its attributes and its relationships with other content elements. If an element
-allows variability, the specification is shown at the bottom of the element's
-description view.</p>
-<div class="p">For the purposes of variability, there are three groups of information
-for any element to be considered:<ul><li><strong>Attributes</strong> - pieces of data about an element such as Main Description.</li>
-<li><strong>Incoming Associations</strong> - associations to other elements where the
-association reference is held in the other element. In other words, the other
-element has references to the subject element.</li>
-<li><strong>Outgoing Associations</strong> - associations to other elements where the
-association reference is held in the subject element. In other words, the
-subject element has references to the other element.</li>
-</ul>
-In addition, associations can be one-to-one or one-to-many. See <a href="variabilityassociations.html#variabilityassociations">Variability Associations</a> for
-a full list of the associations for each type of element.</div>
-<div class="section"><h4 class="sectiontitle">Variability Type</h4><div class="p">Variability
-type defines the nature of how one element affects another element using variability.
-The variability types are:<ul><li><strong>Not Applicable</strong> - The element is a base element and does not affect
-another element through variability. This is the default value of an element's
-variability type.</li>
-</ul>
-<ul><li><strong><span class="keyword">Contributes</span></strong> -
-A contributing element adds to the base element. Contributes provides a way
-for elements to contribute their properties into their base element without
-directly changing any of its existing properties, such as in an additive fashion.
-The effect, after contribution, is that the base element is logically replaced
-with an element that combines the attributes and associations of the contributing
-element with the base element.</li>
-</ul>
-<ul><li><strong><span class="keyword">Replaces</span></strong> -
-A replacing element replaces parts of the base element. Replaces provides
-a way for an element to replace a base element without directly changing any
-of the base element's existing properties. This is, in most cases, used for
-method plug-ins that aim to replace specific content elements such as roles,
-tasks, or activities with either a completely new variant or to change the
-fundamental relationships of these elements. The effect of this, is that the
-base content element is logically replaced with the new replacing element
-to which all incoming associations still point as before, but which has potentially
-new attribute values and outgoing association properties.</li>
-</ul>
-<ul><li><strong><span class="keyword">Extends</span></strong> -
-An extending element inherits characteristics of the base element. Extension
-allows Method Plug-ins to easily reuse elements from a base plug-in by providing
-a kind of inheritance for the extending element. Attribute values and association
-instances are inherited from the "based-on" element to the extending element.
-The result is that the extending element has the same properties as the "based-on"
-element, but might define its own additions. Extends is not used to modify
-content of the base plug-in, but to provide the ability for the extending
-plug-in to define its own content which is a variant of content already defined.
-For example, a special version of a generic Review Record for a specific type
-of review. The effect of this is that the base element and any number of extending
-elements can be used side by side, but refer to each other through the extends
-relationship. Extends also provides the key mechanism for binding capability
-patterns to processes: A pattern is applied by defining an extends relationship
-from an activity of the applying processes to the capability pattern. The
-activity inherits association instances from the pattern and the pattern appears
-to be part of the resulting process after interpretation.</li>
-</ul>
-</div>
-</div>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variabilityassociations.html#variabilityassociations">Variability Associations</a></div>
-<div><a href="contributes.html">Contributes</a></div>
-<div><a href="replace.html#replaces">Replaces</a></div>
-<div><a href="extends.html#extends">Extends</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/variabilityassociations.html b/1.5/plugins/org.eclipse.epf.help.doc/html/variabilityassociations.html
deleted file mode 100644
index 49a3d2a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/variabilityassociations.html
+++ /dev/null
@@ -1,192 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Variability Associations" />
-<meta name="DC.Relation" scheme="URI" content="variability.html#variability" />
-<meta name="DC.Relation" scheme="URI" content="variability.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="variabilityassociations" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Variability Associations</title>
-</head>
-<body id="variabilityassociations"><a name="variabilityassociations"><!-- --></a>
-
-<h1 class="topictitle1">Variability Associations</h1>
-<div><div class="p">The following table lists the incoming and outgoing associations for each
-element type for which variability can be used. Associations also have a cardinality
-of to-many or to-one.
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e16">Element Type</th>
-<th valign="bottom" id="d0e18">Associated Element Type</th>
-<th valign="bottom" id="d0e20">Association</th>
-</tr>
-</thead>
-<tbody><tr><td rowspan="8" valign="top" headers="d0e16 ">Work Product</td>
-<td valign="top" headers="d0e18 ">contained artifacts</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">deliverable parts</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">guidance</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">container artifact</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">deliverable</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">responsible role</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">input and output to tasks</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="4" valign="top" headers="d0e16 ">Role</td>
-<td valign="top" headers="d0e18 ">responsible for work product</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">guidance</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">performer in task</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="7" valign="top" headers="d0e16 ">Task</td>
-<td valign="top" headers="d0e18 ">primary performer role</td>
-<td valign="top" headers="d0e20 ">out-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">additional performer roles</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">input and output work products</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">guidance</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">steps</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">discipline</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e16 d0e18 d0e20 ">Categories</td>
-</tr>
-<tr><td rowspan="2" valign="top" headers="d0e16 ">Custom Category</td>
-<td valign="top" headers="d0e18 ">categorized elements</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">other custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="4" valign="top" headers="d0e16 ">Discipline</td>
-<td valign="top" headers="d0e18 ">categorized tasks</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">referenced workflow activity</td>
-<td valign="top" headers="d0e20 ">out-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">discipline grouping</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="2" valign="top" headers="d0e16 ">Discipline Grouping</td>
-<td valign="top" headers="d0e18 ">categorized disciplines</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="4" valign="top" headers="d0e16 ">Domain</td>
-<td valign="top" headers="d0e18 ">categorized work products</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">sub-domains</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">super-domains</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="2" valign="top" headers="d0e16 ">Work Product Type</td>
-<td valign="top" headers="d0e18 ">categorized work products</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="3" valign="top" headers="d0e16 ">Role Set</td>
-<td valign="top" headers="d0e18 ">categorized roles</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">role set grouping</td>
-<td valign="top" headers="d0e20 ">in-one</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td rowspan="2" valign="top" headers="d0e16 ">Role Set Grouping</td>
-<td valign="top" headers="d0e18 ">categorized role sets</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e18 ">custom categories</td>
-<td valign="top" headers="d0e20 ">in-many</td>
-</tr>
-<tr><td colspan="3" valign="top" headers="d0e16 d0e18 d0e20 ">Guidance</td>
-</tr>
-<tr><td valign="top" headers="d0e16 ">Practice</td>
-<td valign="top" headers="d0e18 ">content element</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-<tr><td valign="top" headers="d0e16 ">Other Guidance Types</td>
-<td valign="top" headers="d0e18 ">sections via content descriptions</td>
-<td valign="top" headers="d0e20 ">out-many</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-<div>
-<div class="familylinks">
-<div class="parentlink"><strong>Parent topic:</strong> <a href="variability.html" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-</div>
-<div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="variability.html#variability" title="Variability allows elements in one content package to influence or modify elements in other content packages without actually directly modifying the original content. Variability enables changes to the content while keeping the changes separate and optional.">Variability</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/conf.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/conf.gif
deleted file mode 100644
index 4e5e6b9..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/conf.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc.gif
deleted file mode 100644
index d4342c2..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc_vs_p.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc_vs_p.gif
deleted file mode 100644
index cdf1b09..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/mc_vs_p.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/methodauthoring.html b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/methodauthoring.html
deleted file mode 100644
index 838dd05..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/methodauthoring.html
+++ /dev/null
@@ -1,69 +0,0 @@
-<html>
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<head>
-<title>Method Content Authoring Overview</title>
-</head>
-<body>
-<h3>Method Content Authoring Overview</h3>
-<p>Method content describes roles, the tasks that they perform, the work products
- that are used and produced by those tasks, and supporting guidance.</p>
-<p><img src="mc.gif"></p>
-<p>The figure above depicts typical sources for method content, as well as how
- the method content is represented in EPF Composer. Many development methods are described
- in publications such as books, articles, training material, standards and regulations,
- and other forms of documentation. These sources usually document methods by
- providing step-by-step explanations for a particular way of achieving a specific
- development goal under general circumstances. Some examples are: transforming
- a requirements document into an analysis model; defining an architectural mechanism
- based on functional and non-functional requirements; creating a project plan
- for a development iteration; defining a quality assurance plan for functional
- requirements; redesigning a business organization based on a new strategic direction,
- and so on.</p>
-<p>EPF Composer takes content such as that described above, and structures it in a specific
- schema of roles, work products, tasks, and guidance. This schema supports the
- organization of large amounts of descriptions for development methods and processes.
- Such method content and processes do not have to be limited to software engineering,
- but can also cover other design and engineering disciplines such as mechanical
- engineering, business transformation, sales cycles, and so on.</p>
-<p> The EPF Composer screen capture in the figure above shows how such method content elements
- are organized in tree browsers on the left. These tree browsers, similar to
- a library, provide different indexes of the available elements for rapid access.
- The screen capture shows on the right an example of a task presentation. This
- task presentation defines the task in terms of steps that need to be performed
- to achieve the task's purpose. You can see that the task has various relationships,
- such as relationships to performing roles as well as work products that serve
- as inputs and outputs to the task. Find out more details on tasks, role, and
- work products in the online help <a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/methodauthoringoverview.html">here</a>.
- In addition to roles, tasks, and work products, EPF Composer supports the addition of
- guidance elements. Guidance are supplementary free-form documentation such as
- whitepapers, concept descriptions, guidelines, templates, examples, and so on.</p>
-<p>EPF Composer provides various form-based editors to create new method content elements.
- Document your task, roles, work products, and guidance elements using intuitive
- rich-text editors that allow you to copy and paste text from other sources such
- as web pages or documents. Use simple dialogs to establish relationships between
- content elements.</p>
-<p>EPF Composer organizes content in physical content packages that allow you to manage
- your content in configurable units. EPF Composer also allows you to categorize your content
- based on a set of predefined categories (for example, categorize your tasks
- into development disciplines, or your work products into domains) or create
- your own categorization schemes for your content with your own user-defined
- categories that allow you to index content in any way you want.</p>
-<p>For more details on method content authoring see the online help:</p>
-<div align="left">
-<ul>
- <li><a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/methodauthoringoverview.html">Method
- Authoring Overview</a></li>
-</ul>
-</div>
-<p> </p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/overview.html b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/overview.html
deleted file mode 100644
index 03f9148..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/overview.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<html>
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<head>
-<title>Eclipse Process Framework Composer Overview</title>
-</head>
-<body>
-<h3>Introduction to Eclipse Process Framework Composer (EPF Composer)</h3>
-<p>Welcome to Eclipse Process Framework Composer (EPF Composer). EPF Composer is a tool platform that enables
- process engineers and managers to implement, deploy, and maintain processes
- for organizations or individual projects. Typically, two key problems need to
- be addressed to successfully deploy new processes.</p>
-<p> First, development teams need to be educated on the methods applicable to
- the roles that they are responsible for. Software developers typically need
- to
- learn
- how
- to
- do analysis and design, testers need to learn how to test implementations against
- requirements, managers need to learn how to manage the project scope and change,
-
- and so on. Some organizations assume that developers implicitly know how to
- do such work without documenting their methods, but many organizations want
-
- to establish common and regulated practices, to drive specific improvement
- objectives, and to meet compliance standards.</p>
-<p> Second, development teams need to understand how to apply these methods throughout
- a development lifecycle. That is, they need to define or select a development
- process. For
-
- example, requirements management methods have to be applied differently in
- early phases of a project where the focus is on elicitation of stakeholder
- needs and
- requirements and scoping a vision, than in later phases where the focus is
- on managing requirements updates and changes and performing impact analysis
- of
- these requirements changes. Teams also need clear understanding of how the
- different tasks of the methods relate to each other, for example, how the
- change management
- method impacts the requirements management method as well as regression testing
- method throughout the lifecycle. Even self-organizing teams need to define
- a
- process that gives at minimum some guidance on how the development will be
- scoped throughout the lifecycle, when milestones will be achieved and verified,
- and
- so on. </p>
-<p>To that end, EPF Composer has two main purposes: </p>
-<div align="left"><ul>
- <li>To provide a knowledge base of intellectual capital which you can browse,
- manage and deploy. This content can include externally developed content,
- and, more importantly, can include your own content including of whitepapers,
- guidelines, templates, principles, best practices, internal procedures and
- regulations, training material, and any other general descriptions of your
- methods. This knowledge base can used for reference and education. It also
- forms the basis for developing processes (the second purpose). EPF Composer is designed
- to be a content management system that provides a common management structure
- and look and feel for all of your content, rather than being a document management
- system in which you would store and access hard to maintain legacy documents
- all in their own shapes and formats. All content managed in EPF Composer can be published
- to html and deployed to Web servers for distributed usage.<br>
- </li>
- <li>To provide process engineering capabilities by supporting process engineers
- and project managers in selecting, tailoring, and rapidly assembling processes
- for their concrete development projects. EPF Composer provides catalogs of pre-defined
- processes for typical project situations that can be adapted to individual
- needs. It also provides process building blocks, called capability patterns,
- that represent best development practices for specific disciplines, technologies,
- or management styles. These building blocks form a toolkit for quick assembly
- of processes based on project-specific needs. EPF Composer also allows you to set up
- your own organization-specific capability pattern libraries. Finally, the
- processes created with EPF Composer can be published and deployed as Web sites.</li>
-</ul>
-</div>
-<h3>Eclipse Process Framework Composer's Key Capabilities</h3>
-<p>Eclipse Process Framework Composer provides the following new key capabilities:</p>
- <div align="left">
-<ul>
- <li> Provides completely redesigned tools for authoring, configuring, viewing,
- and publishing development processes.</li>
- <li> Provides just-in-time generation of publication previews in dedicated browsing
- perspective that allows rapid configuration switching.</li>
- <li> Manages method content using simple form-based user interfaces. Therefore,
- UML modeling skills are no longer required.</li>
- <li> Provides intuitive rich text editors for creating illustrative content
- descriptions. Editors allow use of styles, images, tables, hyperlinks, and
- direct html editing.</li>
- <li>Allows creating processes with breakdown structure editors and workflow
- diagrams through use of multi-presentation process editors. Breakdown structure
- editor supports different process views: work-breakdown view, work product
- usage view, and team allocation view. EPF Composer automatically synchronizes all presentations
- with process changes. </li>
- <li>Provides support for many alternative lifecycle
- models. For example, waterfall, incremental, or iterative models can be created
- with the same overlapping method content.</li>
- <li>Improved reuse and extensibility capabilities. The plug-in mechanisms from
- past versions have been extended to support extensions for breakdown structures.</li>
- <li>Supports reusable dynamically-linked process patterns of best practices
- for rapid process assembly via drag-and-drop.</li>
-</ul>
-</div>
-<h3>Key Terminology and Concepts</h3>
-<p>To effectively work with EPF Composer, you need to understand a few concepts
- that are used to organize the content. The pages <a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/methodauthoringoverview.html">Method
- Content Authoring Overview</a> and <a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/processauthoringoverview.html">Process
- Authoring Overview</a> contain more detail and concrete examples of how to work
- in the tool. This page provides you with a general overview of these concepts.</p>
-<p>The most fundamental principle in EPF Composer is the separation of reusable core method
- content from its application in processes. This directly relates back to the
- two purposes of EPF Composer described in the first section. Almost all of EPF Composer's concepts
- are categorized along this separation. Method content describes what is to be
- produced, the necessary skills required and the step-by-step explanations describing
- how specific development goals are achieved. These method content descriptions
- are independent of a development lifecycle. Processes describe the development
- lifecycle. Processes take the method content elements and relate them into semi-ordered
- sequences that are customized to specific types of projects.</p>
-<p><img src="uma_hump.gif"></p>
-<p>The figure above shows how this separation is depicted in Basic Unified
- Process. Method content, describing how development work is being performed,
- is categorized by disciplines along the y-axis of the diagram. The work described
- in a process is seen along the x-axis representing the timeline. This is the
- lifecycle of a development project. It expresses when what work will be performed.
- The graph in the illustration represents an estimated workload for each discipline.
- As you see, for example, one never stops working on requirements in RUP, but
- there are certainly peak times in which most of the requirements elicitation
- and description work is performed. There are also times at which a downward
- trend needs to be observed where fewer and fewer requirements changes have to
- be processed to bring the project to a close. This avoids what is referred to
- as feature creep in which requirements work remains constant or even increases.
- Hence, a lifecycle (process) expresses the variances of work performed in the
- various disciplines (method content).</p>
-<p><img src="mc_vs_p.gif"></p>
-<p>The picture above provides a summary of the key elements used in EPF Composer and how
- they relate to method content or process. As you see, method content is primarily
- expressed using work products, roles, tasks, and guidance. Guidance, such as
- checklists, examples, or roadmaps, can also be defined to provide exemplary
- walkthroughs of a process. On the right-hand side of the diagram, you see the
- elements used to represent processes in EPF Composer. The main element is the activity
- that can be nested to define breakdown structures as well as related to each
- other to define a flow of work. Activities also contain descriptors that reference
- method content. Activities are used to define processes of which EPF Composer support
- two main kinds: delivery processes and capability patterns. Delivery processes
- represent a complete and integrated process template for performing one specific
- type of project. They describe a complete end-to-end project lifecycle and are
- used as a reference for running projects with similar characteristics. Capability
- patterns are processes that express and communicate process knowledge for a
- key area of interest such as a discipline or a best practice. They are also
- used as building blocks to assemble delivery processes or larger capability
- patterns. This ensures optimal reuse and application of their key best practices
- in process authoring activities in EPF Composer. </p>
-
-<p>For more details on Eclipse Process Framework Composer, see the online help:</p>
-<div align="left">
-<ul>
- <li><a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/aboutepfcomposer.html">Overview</a></li>
- <li><a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/standardmethodlibraryoverview.html">Getting
- Started</a></li>
-</ul>
-</div>
-<p></p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/p.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/p.gif
deleted file mode 100644
index cb86887..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/p.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/processauthoring.html b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/processauthoring.html
deleted file mode 100644
index 438422d..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/processauthoring.html
+++ /dev/null
@@ -1,74 +0,0 @@
-<html>
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<head>
-<title>Process Authoring Overview</title>
-</head>
-<body>
-<h3>Process Authoring Overview</h3>
-<p>A development process defines sequences of tasks performed by roles and work
- products produced over time.</p>
-<p><img src="p.gif"></p>
-<p>The figure above shows that processes are typically expressed as workflows
- or breakdown structures. Defining a strict sequence as in a waterfall model
- is as much a process as defining semi-ordered sequences in iterations of parallel
- work. They just represent different development approaches. Hence, for defining
- a process, one can take method content and combine it into structures that specify
- how the work shall be organized over time, to meet the needs of a particular
- type of development project (such as software for a online system versus software
- and hardware for an embedded system). EPF Composer supports processes based on different
- development approaches across many different lifecycle models, including waterfall,
- incremental, and iterative lifecycles. EPF Composer also supports different presentations
- for process, such as work-breakdown structure or workflow presentations. You
- can also define processes in EPF Composer that use a minimal set of method content to
- define processes for agile, self-organizing teams.</p>
-<p> The EPF Composer screen capture above shows an example of a process presented as a
- breakdown structure of nested activities as well as a workflow or activity diagram
- for one particular activity, the inception phase. It also indicates with the
- two blue arrows that the particular method content task "Detail a Use Case"
- has been applied in the process twice; firstly in the inception phase under
- the activity "Define the System," and secondly, in the elaboration
- phase in the activity "Refine the system definition". You see below
- each of these task applications, referred to as a task descriptors in EPF Composer, lists
- of the performing roles as well as the input and output work products. If you
- look closely, you see that these lists are different for each of these two task
- descriptors, expressing differences in performing the "Detail a Use Case"
- method throughout the lifecycle. You see different roles involved and changes
- in the list of inputs to be considered and outputs to be produced or updated.
- These changes were defined by the author that created this process to express
- the exact focus of the task performance for each occurrence. In addition to
- updating the roles, input and output work products for a task descriptor, you
- can also provide additional textual descriptions as well as define the exact
- steps of the task that should and should not be performed for this particular
- occurrence of the task.</p>
-<p>EPF Composer provides you with a process editor that supports different breakdown structure
- views as well as graphical process presentations. As a process author, you typically
- start by creating an activity breakdown, dividing and breaking your process
- down into phases, iterations, and high-level activities. Instead of creating
- your activities in the breakdown structure editor, you can alternatively work
- in a graphical activity diagram editor that allows you to graphically create
- a workflow for your activities. To assign method content to your process, you
- then have the choice of working in different process views (work breakdown structure,
- work product usage, or team allocation view). Each view supports a different
- approach for creating a process. You can define the work to be done, define
- the results to be produced, or define responsibilities for your roles. If requested,
- the editor updates the other process views semi-automatically using wizards
- that prompt you for decisions on selecting method content elements.</p>
-<p>For more details on process authoring see the online help:</p>
-<div align="left">
-<ul>
- <li><a href="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/processauthoringoverview.html">Process
- Authoring Overview</a></li>
-</ul>
-</div>
-<p> </p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/pub.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/pub.gif
deleted file mode 100644
index 0725474..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/pub.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/publishing.html b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/publishing.html
deleted file mode 100644
index 80b8c1c..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/publishing.html
+++ /dev/null
@@ -1,59 +0,0 @@
-<html>
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-
-<head>
-<title>Configuration and Publishing</title>
-</head>
-<body>
-<h3>Method Configurations Overview</h3>
-<p>Eclipse Process Framework Composer ships with a lot of content out of the box. It includes
- the Open Unified Process (OpenUP) framework and various plug-ins extending
- OpenUP/Basic with domain-specific additions. No organization or project requires all of this
- documentation all at once, but would work with a selection of specific subsets.</p>
-<p> Eclipse Process Framework Composer (EPF Composer) manages for that purpose so-called method
- configurations, which allow you to specify working sets of content and processes
- for a specific context, such as a specific variant of the RUP framework that
- you want to publish and deploy for a given software project or as a foundation
- for a development organization. All content and processes in EPF Composer are organized
- in method plug-ins, which are organized into method packages. A method configuration
- is simply a selection of the method plug-ins and packages.</p>
-<p><img src="conf.gif"></p>
-<p>You create and specify a configuration using the configuration editor depicted
- in the figure above. You could start creating your own method configuration
- by copying one of the configurations that ship with EPF Composer and modify it to fit
- your specific needs. You can add or remove whole method plug-ins as well as
- make selection with each plug-in by checking or un-checking packages. </p>
-<p> You can use the resulting configuration as your working set for your EPF Composer
- work. The actual content of the configuration, i.e. the included method content
- and process elements are always accessible in the Configuration view. Use the
- combo box in the toolbar to select the currently used method configuration.</p>
-<h3>Publishing Overview</h3>
-<p>Method configurations are the basis for publishing method content and processes.
- A published configuration is an html Web site that presents all the method
- content and processes of the method configuration in a navigable and searchable
- way. It uses the relationships established during method content and process
- authoring to generate hyperlinks between elements as well as provides tree
- browsers based on the configuration view and user-defined categorizations of
- the content. The figure below shows an example of the published 'Classic RUP'
- method configuration.</p>
-<p><img src="pub.gif"></p>
-<p>For publishing simply create and select a configuration. The publication wizard
- will do the rest for you and only publish content that is part of the method
- configuration. It will also automatically adopt content to the configuration
- such as removing
- references of method content elements to elements outside of the configuration
- or removing activities from your processes that only contain work defined outside
- of the configuration set. Hence, publishing will only include the content that
- you really need. You can always preview a published configuration using EPF Composer's
-browsing perspective.</p>
-<p> </p>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/uma_hump.gif b/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/uma_hump.gif
deleted file mode 100644
index 4e98f28..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/welcome/uma_hump.gif
+++ /dev/null
Binary files differ
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/whitepaper.html b/1.5/plugins/org.eclipse.epf.help.doc/html/whitepaper.html
deleted file mode 100644
index dece33a..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/whitepaper.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Whitepaper" />
-<meta name="DC.Relation" scheme="URI" content="guidance.html#guidance" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="whitepaper" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Whitepaper</title>
-</head>
-<body id="whitepaper"><a name="whitepaper"><!-- --></a>
-
-<h1 class="topictitle1">Whitepaper</h1>
-<div><p>A Whitepaper is a special type of concept guidance that is externally reviewed
-or published and can be read and understood in isolation of other content
-elements and guidance.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="guidance.html#guidance">Guidance</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/workproduct.html b/1.5/plugins/org.eclipse.epf.help.doc/html/workproduct.html
deleted file mode 100644
index 98a2c13..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/workproduct.html
+++ /dev/null
@@ -1,46 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Work Product" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html#createaworkproduct" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="workproduct" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Work Product</title>
-</head>
-<body id="workproduct"><a name="workproduct"><!-- --></a>
-
-<h1 class="topictitle1">Work Product</h1>
-<div><div class="p">Work product is a general term for task inputs and outputs,
-descriptions of content elements that are used to define anything used, produced,
-or modified by a task. The three types of work product are:<ul><li><a href="artifact.html#artifact">Artifact</a></li>
-<li><a href="outcome.html#outcome">Outcome</a></li>
-<li><a href="deliverable.html#deliverable">Deliverable</a></li>
-</ul>
-</div>
-</div>
-<div><div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createaworkproduct.html#createaworkproduct">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/workproductdescriptors.html b/1.5/plugins/org.eclipse.epf.help.doc/html/workproductdescriptors.html
deleted file mode 100644
index c4fca95..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/workproductdescriptors.html
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Work Product Descriptors" />
-<meta name="DC.Relation" scheme="URI" content="workproduct.html#workproduct" />
-<meta name="DC.Relation" scheme="URI" content="createaworkproduct.html" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="workproductdescriptors" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Work Product Descriptors</title>
-</head>
-<body id="workproductdescriptors"><a name="workproductdescriptors"><!-- --></a>
-
-<h1 class="topictitle1">Work Product Descriptors</h1>
-<div><p>A work product descriptor is a work product in the context of one specific
-activity. Every breakdown structure can define different relationships of
-work product descriptors of task descriptors and role descriptors. One work
-product can be represented by many work product descriptors, each within the
-context of an activity with its own set of relationships.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="workproduct.html#workproduct">Work Product</a></div>
-</div>
-<div class="reltasks"><strong>Related tasks</strong><br />
-<div><a href="createaworkproduct.html">Create a Work Product</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.help.doc/html/workproductkind.html b/1.5/plugins/org.eclipse.epf.help.doc/html/workproductkind.html
deleted file mode 100644
index 87ddb29..0000000
--- a/1.5/plugins/org.eclipse.epf.help.doc/html/workproductkind.html
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-us" xml:lang="en-us">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" />
-<meta name="security" content="public" />
-<meta name="Robots" content="index,follow" />
-<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
-<meta name="DC.Type" content="concept" />
-<meta name="DC.Title" content="Work Product Kind" />
-<meta name="DC.Relation" scheme="URI" content="methodcontentcategories.html#methodcontentcategories" />
-<meta name="DC.Format" content="XHTML" />
-<meta name="DC.Identifier" content="workproductkind" />
-<meta name="DC.Language" content="en-us" />
-<!--
- Copyright (c) 2005, 2006 IBM Corporation and others.
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- Contributors:
- IBM Corporation - initial implementation
--->
-<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
-<title>Work Product Kind</title>
-</head>
-<body id="workproductkind"><a name="workproductkind"><!-- --></a>
-
-<h1 class="topictitle1">Work Product Kind</h1>
-<div><p>Work Product Kind is another category for grouping <a href="workproduct.html#workproduct">Work Products</a>. A work product can have many work product
-kinds. As an example, you might want to have a series of work product kinds
-that correspond to the overall intent of work products, such as specification,
-plan, or model.</p>
-</div>
-<div><div class="relconcepts"><strong>Related concepts</strong><br />
-<div><a href="methodcontentcategories.html#methodcontentcategories">Method Content Categories</a></div>
-</div>
-</div>
-</body>
-</html>
diff --git a/1.5/plugins/org.eclipse.epf.ui.intro/introContent.xml b/1.5/plugins/org.eclipse.epf.ui.intro/introContent.xml
index 60d15dd..26793fe 100644
--- a/1.5/plugins/org.eclipse.epf.ui.intro/introContent.xml
+++ b/1.5/plugins/org.eclipse.epf.ui.intro/introContent.xml
@@ -223,34 +223,34 @@
<anchor id="beginAnchor"/>
<link
label="Explore the user interface"
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/tutorials/tutorial_1_intro.htm&"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/tutorials/tut1_intro.html&"
id="epf-tut-navigate"
class-id="left">
<text>Learn to navigate through the user interface: perspectives, views, and search.</text>
</link>
<link
label="Working with processes"
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/tutorials/tutorial_5_intro.htm&"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/tutorials/tut4_intro.html&"
id="epf-tut-process">
<text>Learn how to create and reuse capability patterns and delivery processes.</text>
</link>
<link
label="Create method content "
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/tutorials/tutorial_2_intro.htm&"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/tutorials/tut2_intro.html&"
id="epf-tut-element"
class-id="left">
<text>Learn how to use the editors to create roles, tasks, work products and guidance.</text>
</link>
<link
label="Publishing and Exporting"
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/tutorials/tutorial_4_intro.htm&"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/tutorials/tut5_intro.html&"
id="epf-tut-pubexp">
<text>Learn how to publish configurations to a web site and how to export processes to a planning tool.</text>
</link>
<link
label="Reuse method content"
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/html/tutorials/tutorial_3_intro.htm&"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.epf.help.doc/tutorials/tut3_intro.html&"
id="epf-tut-content"
class-id="left">
<text>Learn how to extend, replace, and contribute to base content elements.</text>
