<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-h7N3-dEGv5zV3zn2iBQbnw" name="new_concept,_-SxxEITWEd2AfZddKTmDRA" guid="-h7N3-dEGv5zV3zn2iBQbnw" changeDate="2008-10-09T07:32:41.683-0700" version="7.5.0">
  <mainDescription>&lt;br />&#xD;
&lt;br />&#xD;
&lt;table width=&quot;95%&quot; summary=&quot;layout table&quot; border=&quot;1&quot;>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;IterativePlan&quot; name=&quot;IterativePlan&quot;>Iteration Plan Editor&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Iteration Plan Editor lets you to create or modify an iteration plan. Work items that are targeted for&#xD;
                the same iteration are automatically added to the plan.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;IterationType&quot; name=&quot;IterationType&quot;>Iteration Type&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Teams can define iteration types. Each iteration can be assigned an iteration type. Teams can configure&#xD;
                    behavior for all iterations of a given type. This allows for more succinct process specifications.&#xD;
                &lt;/p>&#xD;
                &lt;p>&#xD;
                    For example, if a team divides each milestone into a development phase and a stabilization phase, they&#xD;
                    can create an iteration type named &quot;Milestone Stabilization Phase&quot; and apply it to the appropriate&#xD;
                    iterations. The permissions/behavior for all of these iterations can then be configured at once by&#xD;
                    configuring the iteration type.&#xD;
                &lt;/p>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;OperationPreCondition&quot; name=&quot;OperationPreCondition&quot;>Operation Precondition&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    RTC&amp;nbsp;users&amp;nbsp;can enforce the desired behavior of their teams' process by configuring&#xD;
                    preconditions and followup actions. Preconditions are checked before an operation is run (such as&#xD;
                    before delivering code) and may prevent the operation from executing if its condition is not met.&#xD;
                &lt;/p>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;TeamProcessComponent&quot; name=&quot;TeamProcessComponent&quot;>Team Process Component&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    The Team Process Component provides RTC's process support foundations. In the RTC context, process&#xD;
                    refers to the collection of practices, rules, guidelines, and conventions used to organize a project's&#xD;
                    work. A team's process is the sum total of the ways the team has decided (or evolved) to do things.&#xD;
                &lt;/p>&#xD;
                &lt;p>&#xD;
                    For a very small team, the process is usually informal and undocumented. As a team grows, parts of the&#xD;
                    process may get documented on the team's project home page so that new team members can absorb them&#xD;
                    quickly. A large organization may have written descriptions of the general practices and procedures&#xD;
                    their project teams are expected to adhere to; a project team is expected to start with standard&#xD;
                    process templates and customize them to suit the project and team. Some organizations and teams go one&#xD;
                    step further, and create formal models covering significant portions of their processes.&#xD;
                &lt;/p>&#xD;
                &lt;p>&#xD;
                    RTC&amp;nbsp;is designed to allow comprehensive support across the entire software development lifecycle.&#xD;
                    One thread that runs throughout all phases of a project is the process that the team members have&#xD;
                    agreed to follow.&#xD;
                &lt;/p>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;ProcessIterations&quot; name=&quot;ProcessIterations&quot;>Process Iterations&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The &lt;strong>Process&amp;nbsp;Iteration&lt;/strong> page of the &lt;strong>Process Template&#xD;
                Editor&lt;/strong>&amp;nbsp;specifies the current iteration for the project. This process state is described using&#xD;
                XML. The Outline view provides a structured view of its contents. Iteration start and end dates can be&#xD;
                specified here also.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;ProcessSpecification&quot; name=&quot;ProcessSpecification&quot;>Process Specification&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Just as a computer program is a static description of how things are supposed to unfold dynamically at&#xD;
                    runtime, a process specification is a static description of how things are supposed to unfold during&#xD;
                    the software development process. In the case of the latter, what unfolds dynamically is the work that&#xD;
                    the team members perform; the project area is the runtime context; the project artifacts are the&#xD;
                    runtime objects.&#xD;
                &lt;/p>&#xD;
                &lt;p>&#xD;
                    Process specifications are expressed in a declarative form, while primitive actions are expressed as&#xD;
                    Java code. Process specifications are kept in a compiled form that can be executed efficiently.&#xD;
                    Executing the process specification in a particular situation means determining and executing the&#xD;
                    process rules that apply. Process specifications stored in project areas are instantiated from process&#xD;
                    templates.&amp;nbsp;RTC provides means to author process templates, to edit process specifications and&#xD;
                    process states of project areas, and to edit process customizations of team areas. Process descriptions&#xD;
                    authored with tools like provided by the Eclipse Process Framework can be deployed to a&amp;nbsp;RTC&#xD;
                    repository and be associated with existing process templates. They can then be viewed in the context of&#xD;
                    project areas whose process specifications have been derived from these process templates.&#xD;
                &lt;/p>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;ProcessTemplate&quot; name=&quot;ProcessTemplate&quot;>Process Template Editor&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Process Template Editor allows you to author &lt;strong>Process Specifications&lt;/strong> that can be reused&#xD;
                for more than one project. It allows you to create a process description, process specification, process&#xD;
                state, and process content URL.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;ProcessTemplateExplorer&quot; name=&quot;ProcessTemplateExplorer&quot;>Process Template&#xD;
                Explorer&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                This view is used to create or modify process templates.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;ProjectArea&quot; name=&quot;ProjectArea&quot;>Project Area Editor&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Project Area editor is a multi-page tabbed editor used to modify a project area after it has been&#xD;
                created&lt;font color=&quot;#0000ff&quot;>.&lt;/font> It gives you access to the project area's process specification,&#xD;
                development lines, and categories.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;RTCWorkItem&quot; name=&quot;RTCWorkItem&quot;>RTC Work Item&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Work Item is a central team artifact in a&amp;nbsp;RTC development process.&amp;nbsp; A Work Item is a&#xD;
                generalized notion of a development task. Typical work item types are defects, enhancements and tasks. Jazz&#xD;
                allows to add new work item types or extend existing types via the &lt;strong>Process Specification&lt;/strong>.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;TeamArea&quot; name=&quot;TeamArea&quot;>Team Area Editor&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Team Area editor is&amp;nbsp;visually similar to the project area editor, this editor is used to define&#xD;
                team members, choose the development line, and optionally, customize the team's process.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;TeamArtifactsView&quot; name=&quot;TeamArtifactsView&quot;>Team Artifacts View&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Team Artifacts view manages your connections to a repository and a project area. Once you are connected&#xD;
                to a project area you can access its artifacts. The artifacts are grouped into different nodes as shown&#xD;
                below.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;WorkItemCategories&quot; name=&quot;WorkItemCategories&quot;>Work Item Categories&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Work Item Categories page is used to add and remove work item categories and to associate them with&#xD;
                specific team areas. The team area with which the work item category is associated will determine the&#xD;
                process which governs work items created with the category. For example, the team areas process&#xD;
                configuration may specify required work item properties).&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;WorkItem&quot; name=&quot;WorkItem&quot;>Work Item Editor&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Work Item Editor lets you create or modify a work item, change its state, add comments, attachments,&#xD;
                and links to other artifacts. When you save the editor, the updated work item will be transmitted to the&#xD;
                repository.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>&lt;a id=&quot;WorkItemView&quot; name=&quot;WorkItemView&quot;>Work Items View&lt;/a>&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                The Work Items View shows you the work items returned when running a work item query.&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&lt;br />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
