Task: Plan Subsystem Integration
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{502B4138-0772-4A4E-A183-C647497AFCB8}", "{197B2D0F-6B49-4998-8A71-0799BC29D13F}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_IY0NkAISEdqTna4sZVFRow", "_yd3ExNnmEdmO6L4XMImrsA", "{197B2D0F-6B49-4998-8A71-0799BC29D13F}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{502B4138-0772-4A4E-A183-C647497AFCB8}", "{197B2D0F-6B49-4998-8A71-0799BC29D13F}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_kC0pcN7GEdm8G6yT7-Wdqw", "_yd3ExNnmEdmO6L4XMImrsA", "{197B2D0F-6B49-4998-8A71-0799BC29D13F}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);
Task: Plan Subsystem Integration
This task describes how to plan the order in which the elements contained in an implementation subsystem should be integrated.
Disciplines: Implementation
Relationships
RolesPrimary Performer:
Integrator
Additional Performers:
InputsMandatory:
Implementation Subsystem
Iteration Plan
Optional:
Implementation Element
Implementation Model
Integration Build Plan
Use-Case Realization
Outputs
Integration Build Plan
Process Usage
Implementation
>
Implement Components
>
Plan Subsystem Integration
Steps
Define the Builds
Study the use cases and scenarios that have been selected for the current iteration. Select one, or several scenarios,
that will be the goal for each increment of the integration. It may be necessary to select only a part of a scenario
that concerns this subsystem.
Capture the plan to integrate the subsystem, either in the project's Integration Build Plan, or in an integration build
plan local to the subsystem.
Identify the Classes
Identify the classes that participate in the selected scenarios. Each scenario is described in a design use-case
realization's sequence diagrams, communication diagrams, or class diagrams. Identify which classes you need to
implement, and which classes have already been implemented. Also identify the classes that do not participate in the
scenario, but are needed as stubs.
Classes are identified from design use-case realizations.
Update the Subsystem's Imports
Identify which other implementation subsystems are needed for this build. Decide which version of each subsystem to
use. Update import dependencies for this subsystem to the correct versions of the other subsystems.
If new system baselines have recently been promoted, the integrator will also have to decide when to update
(rebaseline) the subsystem integration workspace. This decision is based on where in the development cycle you are. If
your subsystem development is unstable in some critical area, then you may decide to postpone rebaselining.
When it is late in the project, and close to a release (whether internal or external), it is crucial that subsystems
have consistent import sets. Then there is a greater urgency to stay current with the system baselines.
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
Wyszukiwarka
Podobne podstrony:
plan subsystem integration5FBE46plan subsystem integration5FBE46plan the integration11CF4A2plan the integration0EC233plan the integration0EC233plan the integration0EC233plan the integration0EC233plan the integration11CF4A2plan the integration11CF4A2plan system integration+706402plan the integration11CF4A2plan system integration?1306E2plan the integration11CF4A2csps integration build planteoria integracji plan wykladow?integrate?ch subsystem?835A47integrate?ch subsystem4DF846Bintegrate?ch subsystem4DF846Bintegrate?ch subsystem4DF846Bwięcej podobnych podstron