Rule Operation

Only one rule may be defined for each item type. The rule is used to determine, for relevant items of that type, what status (lifecycle state) or build stage is acceptable, or to be preferred, for any revision to be included in a baseline.

To specify the rule, any one of the states or build stages in the normal lifecycle associated with that type may be chosen, together with one of the rules described in this topic, which determines how that state and others in the normal lifecycle are to be grouped and arranged in an order of preference. (A normal lifecycle consists of a single chain of states, starting with the first state at the beginning of the chain, and progressing upward through later states to the final state at the end of the chain.)

For each relevant item which is of the type concerned within this rule, we look at each grouping of normal lifecycle states in the order of preference indicated by the rule, until we find the first group which is not empty, i.e. where there is at least one revision of the relevant item in that group. If we then find that there are two or more revisions in that group, we always select the revision which has been created/updated most recently; this is often, but need not necessarily be, the one with the highest entry in the revision field. If all groups in the order of preference are empty, then that item will not be included in any baseline specified using this template.

NOTE Except when an *ALL rule is used (this is detailed later), no more than one revision of any item is selected for inclusion in a release baseline.

Rule | Grouping and order of preference
Latest from state (LFS) | Latest from specified state and upward: there is just one group it consists of all revisions which are at any of the normal lifecycle states between the specified state and the final state, both of these states inclusive. (Conversely, if a relevant item of the given type has all its revisions at states which are not in the normal lifecycle, and/or at states which are in the normal lifecycle but are below (earlier than) the specified state, then such a relevant item is not selected using this template.)
Most progressed state above specified state or specified state (MPS) | Most progressed state not below specified state: there are several groups, each of which includes revisions (if any) at just one lifecycle state. The order of preference for the groups is then: t he group for the final state in the normal lifecycle t he group for the next-to-final state then so on downwards, ending with the group for the specified lifecycle state.
Specified state or most progressed state (SMP) | Specified state or most progressed state: there are several groups, each of which includes revisions (if any) at just one lifecycle state. The order of preference for the groups is then: the group for the specified lifecycle state the group for the final state in the normal lifecycle that for the next-to-final state then so on downwards to earlier states, ending with the group for the next state upwards from the specified state.
Specified state or next existing state upward (SUP) | Specified state or upward: there are several groups, each of which includes revisions (if any) at just one lifecycle state. The order of preference for the groups is then: the group for the specified lifecycle state the group for the next later normal lifecycle state upward from this then so on, ending with the group for the final state.
Specified state only (EQS) | Equal to specified state: there is just one group – it consists of revisions which are at the specified lifecycle state only. (A relevant item of the given type, which has no revision at this state, will not be selected using this template.)
Specified build stage and all next existing build stages upward (BUP) | Latest from specified build stage and upward: there are several groups, each of which includes revisions (if any) at just one build stage. (Conversely, if a relevant item of the given type has all its revisions at stages which are below the specified build stage, then such a relevant item is not selected using this template.) The order of preference is then: the group for the specified build stage the group for the next existing higher build stage upward from this then so on, ending with the group for the final stage.
Specified build stage only (EQB) | Equal to specified build stage: there is just one group – it consists of revisions which are at the specified build stage only. (A relevant item of the given type, which has no revision at this stage, will not be selected using this template.)

For an example of how rules work, see Illustration of Rule Operation.

Instead of specifying a particular state in the normal lifecycle, you can choose an implicit state. For details, see Rules Using Implicit States.

Related Topics

What is a Baseline Template?

About Request Baseline Template Selection Criteria

About Item Baseline Template Selection Criteria