To use Rational® Change
Distributed effectively, develop a plan for the flow of information
between databases. The plan must address the Rational Change life cycle (transitions
between states). The plan must also address the corresponding DCM
configuration management flow (hand over of control from one database
to another).
As a starting point, consider these questions. Your
answers help determine your Rational Change
Distributed methodology and topology.
- In which databases are change requests to be entered?
- Are change requests verified and then moved in the
same database in which they were entered?
- Are change requests assigned to personnel in remote
databases?
- Are the tasks for a change request created and assigned
from a single controlling database for that change request?
- Are tasks created and assigned in more than one
database against the same change request?
- In which databases are change requests resolved?
- In which databases are change requests concluded?
- Do reporting or query requirements require visibility
of change requests from other databases? If so, do these requirements
include a breakdown of associated tasks?
- Is reporting on associated objects required?
- If change request replication is required, must
replication be selective? If so, is replication based on product name,
or on some other criteria?
- Is replication of registered or task_assigned tasks
required? Or is replication of tasks that are in the completed state
sufficient?
- Are there issues regarding commercial sensitivity
of configuration Management data in remote databases? How are these
issues addressed?
- What email triggers are required? How is email notification
against different databases implemented?