Artifact: Workspace
Workspace |
Workspaces
enable access to artifacts and resources required to develop and assemble the deliverable product.
There are two kinds of workspaces.
The development workspace is a private development area within which a worker can make changes to artifacts without the changes becoming immediately visible to other workers. The integration workspace is shared workspace and accessible to all members of the project team. The overall product is built and baselined in the integration workspace. |
| UML representation: | Package, stereotyped as a <<workspace>> |
| Worker: | Any Worker and Integrator |
| More information: | |
| Input to Activities: | Output from Activities: |
Purpose 
The purpose of a workspace is to enable access to artifacts and resources required to develop and assemble the deliverable product. Development workspaces refer to æprivateÆ areas where developers can implement and test code in relative isolation from other developers. Integration workspaces refer to public areas where individual work is delivered for incorporation into the overall product build and baselines.
Properties
On a project, there is one shared integration workspace, and possibly multiple development workspaces. Each project member needs to work within a workspace to gain access to the project artifacts that are baselined, and retained in the project repository. The integrator creates builds within the integration workspace and makes baselines that are visible to the overall development team.
Timing
Each worker on joining a project is granted a development workspace, and access to the integration workspace. The integration workspace that provides access to the baselined set of artifacts is created as soon as the project CM environment has been established. Development workspaces can be created whenever a worker joins the project effort.
Responsibility
The Development Workspace can be created by Any Worker. The Integration Workspace is created by the Integrator.
