EMI Requirement Tracking Policy

Requirements Tracker

The EMI Requirements Tracker is here:

Location: https://savannah.cern.ch/task/?group=emi-req
Administrator: B.Konya (TD and PTB chair)

How EMI requirements are Received and Managed

Whoever considers a requirements relevant should send it to the TD. Before doing so make sure it it relevant to EMI and reprensents a real need of some user community.

• Requirements are sent to the project:
  • to the TD by email or from established bodies (EGI, WLCG, etc)
  • via GGUS tickets and assigned to the TD
  • directly received by the TD from the PTs. It is the PT leader's responsibility to propagate the request to the TD.

• The TD will create an item in the Requirements tracker with the ID of the ticket.
• The link to the Savannah item is added in the GGUS ticket.

How to use the Requirement Tracker

• It tracks ALL user requirements of the EMI software.
• These requirements are communicated via the management bodies of EMI and the DCIs.
• Requirements can also arrive directly from the PTs.
• The originator (requestor field) of the requirement and possibly the corresponding ticket or request should be referred.

• Requirement must be related to the corresponding Development Trackers of the Product Teams. Maybe one requirement involves several components and requires several tasks to be added.

How EMI Requirements are Accepted (new section)

• The requirements are analysed and prioritized by the EMI Technical Director,
• EMI Technical Director is responsible for making sure that a task is created in Requirements Tracker for each user requirement.
• EMI Technical Director is responsible for tracking the open tasks and closing them when the user requirements have been implemented.

• Area Leader are responsible making sure that the tasks deriving by the EMI requirements are mapped into the Areas Workplans and in the PTs trackers.
• The tasks in the Areas Workplans should refer to the ID of the requirement that they are depending on.

• Product Teams and Area Leaders should report to the TD any deviation from the planned implementation of the accepted requirements.

Main Fields

The following fields are available for each requirement:

• Should Start On
• Should be Finished On
• Category (details below)
• Status (details below)
• Assigned To
• Priority (details below)
• Planned Release
• Requestor
• Related ticket
• Components

Category

• general requirement
• component requirement
• documentation requirement
• bug report
• non-emi (out-of-scope)
• other

Status

• Submitted - The requirement has been recorded in the tracker.
• Need Info - The requirement is not sufficiently defined.
• Under Discussion - The request is being discussed by the EMI technical management (PTB).
• Endorsed - The requirement is accepted as a valid EMI requirement
• Endorsed with modification - A modified version of the original requirement is accepted as a valid EMI requirement.
• Ongoing - In Progress. Some activity is already going on in order to address the endorsed requirement. E.g. code is being written, documentation/report is being updated/prepared.
• Postponed - The requirement will be processed later (no date given)
• Duplicate - This requirements is already covered by another description
• Resolved - The requirement has been implemented and released with an EMI component release.
• Returned - The requirement is rejected in its current form.

Priority

• 0 - unknown
• 1 - lowest
• 2 - lower
• 3 - medium
• 4 - high
• 5 - top