Users, lifecycles, and states

In a Rational Synergy session, each user can work as a developer or build manager. If a user has been set up to work as a developer and build manager, Rational Synergy allows the user to perform the appropriate operations without any interference. Typically, developers perform operations for developing and testing software. Build managers perform operations for integrating software, and configuring and building area where developers can access the integrated software. Build managers also configure and build test areas and prepare software for release.

All objects follow a lifecycle. The lifecycle refers to the possible states of an object, and to which states an object can move based on its current state. The state of an object defines the stage in its lifecycle and the actions that can be performed, such as who can modify it.

By default, the three states that objects use in Rational Synergy’s task-based methodology are working, integrate, and released. The figure illustrates the lifecycle sequence of the default states of an object.

Use these states as follows:

Your organization can use other lifecycle schemes. Several optional states, such as rejected, shared, and visible, are included with Rational Synergy.

The lifecycle for an object associated with a task is closely linked to its task state. It is the task lifecycle that moves the object through the process. For example, you can check in an object at any time, but it is not picked up for integration testing until you complete its associated task.

By default, a task can have the following states: registered, task_assigned, and completed. The figure illustrates the lifecycle sequence of the default states of a task.

The task_assigned state is used for tasks that have been assigned to a developer. When a task is in the task_assigned state, it is modifiable and can be used by the resolver (the person the task is assigned to). By default, build managers can assign tasks. Developers can assign tasks to themselves only.

The completed state is used for tasks that are finished. When a task is in the completed state, it is checked in and can be modified only by the CM administrator. All object versions associated with a task must be checked in before the task can be completed. Only the resolver of a task can complete a task. The resolver can be a developer or build manager.


Feedback