Use Case 19 - Approve version

Approve a new versioned set of artifacts for a target.

Flow

Pre-conditions

The target must be in the "new" state, meaning there are updates for it.

Basic flow

1. The target operator reviews the details of the updates.
2. When he is satisfied, he approves those changes.
3. A new version of the software for that target is generated.
4. The target is put in "approved" state.

Post-conditions

The target is in the "approved" state.

Alternative flows

• After reviewing the changes, the target operator decides not to approve them. The target then remains in the "new" state.

Details

• When a target is configured to "auto-approve" updates, this whole use case takes place without human interaction from the target operator.
• The use case purposely does not describe how a new version number for the target is generated, because that is a configurable aspect (which might or might not include user interaction).