Track UMD Requirements
|UMD (TCB)||Operations (OMB)||User Support (UCB)|
Status at TCB
Please be familiar with a TCB requirements management process
Requirements were discussed at OMB and UCB and transfered to TCB. Tickets are ordered by Priority (descending)
Submitted - Prior to a TCB Face-to-Face meeting, the UCB, and the OMB and DMSU deliver a Catalogue of Requirements (CoR) detailing all outstanding requirements and their current state. Requirements that were not submitted to the TCB before may be included in the CoR, and by this change their state to Submitted by this transition with the submission to the TCB to the state Submitted to record their formal proceeding.
In Clarification - A requirement in state In Clarification is handed back by the TCB to the originating community management board for further clarification (see section 3.2). That is, the TCB decided that the requirement does not match the TCB’s catalogue of requirements criteria (see section 5), for example the requirement may lack specific information, may address low-level issues, etc. Requirements in state In Clarification may be included in the CoR submitted to the TCB, if the managing body feels the TCB’s instructions for clarification were adequately met (see section 3.5.7).
Reviewed - The originating community (via the OMB or the UCB) further amended and clarified a requirement according to the TCB request. Requirements for which the TCB previously requested more information (i.e. in state In Clarification) are re-submitted to the TCB in state Reviewed indicating that it is not a new requirement but a reviewed requirement that was submitted at an earlier TCB meeting.
Endorsed - At a Face-to-Face meeting, the TCB participants may decide to endorse a requirement (see section 3.2), reflecting the agreement that the pertinent requirement indeed reflects a need of the EGI community, Following endorsement, the requirement shall be further assessed by Technology Providers for the necessary effort to implement it and a proposed development and provisioning schedule to successfully deliver the requirement shall be created.
Assessed - Technology Providers take endorsed requirements and develop an implementation and deployment strategy for software in order to deliver the requirement, and delivers this as a set of Statements of Solution (SoS) to the TCB. When the Technology Provider has fully assessed the requirement it returns it to the TCB in status Assessed.
Planned - The TCB prioritises all assessed requirements, and assigns priorities to all or a subset of those. All requirements for which a priority was assigned are in state Planned.
Delivered - At some point in time after being planned, a Technology Provider delivers software that satisfies a given requirement for provisioning for deployment onto the EGI Production infrastructure. If the software is successfully provisioned (i.e. is part of a published UMD update), that implemented requirement is transitioned into state Delivered.
Returned - The TCB may decide that a requirement is out of scope for the TCB to deal with. In this case the TCB documents the reason why the requirement is out of scope, and returns the requirement to the originating EGI community in state Returned.