<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="_2OOYAtnmEdmO6L4XMImrsA" name="development_and_integration_workspaces,1.2252946942508563E-305" guid="_2OOYAtnmEdmO6L4XMImrsA" changeDate="2010-11-22T17:09:43.630-0800" version="7.1.0">
  <mainDescription>&lt;a id=&quot;Top&quot; name=&quot;Top&quot;>&lt;/a> &#xD;
&lt;p>&#xD;
    A system is typically implemented by teams of individual implementers working together and in parallel. To make this&#xD;
    possible, several workspaces are needed such as:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        a &lt;a href=&quot;#Development_Workspace&quot;>development workspace&lt;/a> for each individual implementer&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        an subsystem &lt;a href=&quot;#Integration_Workspace_for_the_Team&quot;>integration workspace for the team&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        an system &lt;a href=&quot;#Integration_Workspace_for_Integrators_at_the_System_Level&quot;>integration workspace for&#xD;
        integrators&lt;/a> at the system level&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    &lt;a id=&quot;XE_development_area&quot; name=&quot;XE_development_area&quot;>&lt;/a>&lt;a id=&quot;XE_configuration_management__development_area&quot;&#xD;
    name=&quot;XE_configuration_management__development_area&quot;>&lt;/a>&lt;a id=&quot;Development_Workspace&quot;&#xD;
    name=&quot;Development_Workspace&quot;>&lt;/a>Development Workspace&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Individual implementers have a development workspace where they implement the subsystems and the contained elements for&#xD;
    which they are responsible. To compile, link, execute, and test the code in the subsystem, other parts of the system&#xD;
    are needed. Normally the implementers do not need the entire system to develop their subsystem. It's usually enough to&#xD;
    have the subsystems required to compile, link, and execute the subsystem in the development workspace. These other&#xD;
    subsystems do not have to reside in any one implementer's private development workspace as physical copies. Instead&#xD;
    they can reside in a common repository with the internally released subsystems. When implementers compile the precise&#xD;
    location of the other subsystems, it's defined in a separate file; for example, a makefile.&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;exampleheading&quot;>&#xD;
    Example:&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;example&quot;>&#xD;
    The Monthly Account Telephone subsystem (in a banking system) needs the subsystems that are directly or indirectly&#xD;
    imported by the subsystem to compile, link, and execute its elements. In this case, six of the ten subsystems will be&#xD;
    needed for the implementers of the Monthly Account Telephone subsystem.&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;picturecenter&quot; align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;444&quot; alt=&quot;Diagram is described in the content.&quot; src=&quot;resources/co_dvin1.gif&quot; width=&quot;611&quot; />&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;picturetext&quot;>&#xD;
    The development workspace for implementers of the subsystem Monthly Account Telephone&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    &lt;a id=&quot;XE_integration_area&quot; name=&quot;XE_integration_area&quot;>&lt;/a>&lt;a id=&quot;XE_configuration_management__integration_area&quot;&#xD;
    name=&quot;XE_configuration_management__integration_area&quot;>&lt;/a>&lt;a id=&quot;Integration_Workspace_for_the_Team&quot;&#xD;
    name=&quot;Integration_Workspace_for_the_Team&quot;>&lt;/a>Integration Workspace for the Team&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    At times there may be a team of implementers who simultaneously develop the same subsystem. In this case implementers&#xD;
    need to integrate their elements into a subsystem before it can be propagated on to system integration. Team&#xD;
    integration is often done in a &lt;b>subsystem integration workspace&lt;/b> dedicated to the integration of individual team&#xD;
    member's work. One team member acts as the integrator and is responsible for the integration workspace and its&#xD;
    performance.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    &lt;a id=&quot;XE_integration_workspace_integrators&quot; name=&quot;XE_integration_workspace_integrators&quot;>&lt;/a>&lt;a&#xD;
    id=&quot;Integration_Workspace_for_Integrators_at_the_System_Level&quot;&#xD;
    name=&quot;Integration_Workspace_for_Integrators_at_the_System_Level&quot;>&lt;/a>Integration Workspace for Integrators at the&#xD;
    System Level&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    System integrators have an integration workspace where they can add one or several software elements or one or several&#xD;
    subsystems at a time, thereby creating builds that are then integration tested.&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;picturecenter&quot; align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;171&quot; alt=&quot;Diagram is described in the content.&quot; src=&quot;resources/co_dvin2.gif&quot; width=&quot;501&quot; />&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;picturetext&quot;>&#xD;
    An integration workspace for system integrators where subsystems are added in each integration increment&#xD;
&lt;/p>&lt;br />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
