Current Situation

We have two lists currently that hold the requirements from LCG clients.

From the HEP/NA4 list:

Heading Comment
Index Identification. Savannah takes care of this.
Issue/Requirement Subject of req. Savannah takes care of this.
Origin Who/what proposes this, can be multiple sources.
The next entries are "votes" by each stakeholder below  
Sum Sum of the above votes.
Result Link to the resulting action, Savannah or other.
Estimated Cost Got used as an ad-hoc schedule for the work. Savannah has field.
Comments Self-explanatory. Savannah takes care of this.
Status Self-explanatory. Savannah takes care of this.
Category Categories grouped by rows. Not a column.

An interesting use of the votes above is the ability to see whether a particular requirement voting was dominated by one stakeholder or more equally by all. ie. We can make a deduction on the RMS of a voting.


Heading Comment
Num Identification.
ADDED BY Here the different federations that make the request are noted. Can be multiple
DESCRIPTION Self-explanatory. Has been used for the work progress as well.
DATE ADDED Self-explanatory.
STATUS Used very simply. In progress etc.

New Requirements Mechanism

A super-set of the data from the above two pages would result in:

Data Comment Who enters this*
Index Number RGM takes care of this. ---
Origin Who/what proposes this, can be multiple sources. Task submitter Auto by RGM
Issue/Requirement Description Title of requirement and original comment. Stakeholder
Category Which middleware area does this fit? TMB/Provider
Result Here the subsequent comments in RGM can detail the resulting actions. TMB/Provider
Estimated Cost RGM has a field. TMB/Provider
Comments RGM takes care of this. All
Starting date Projected date for work to start Provider
Ending date Projected date for work to be completed Provider
Status RGM takes care of this. Current owner of task
Votes This has to be investigated to see whether the votes can be attributed to the various stakeholders All stakeholders
Priority Urgency of a task... determined by stakeholder voting. TMB/Stakeholders

* Stakeholder -- a client of the middleware stack.
* Provider -- Activity/Group that will make the necessary software changes according to the requirement.
* TMB -- Group made up of Stakeholders and Providers.

From Steven's email

  • Who will benefit.

  • Implications (in post EGEE world) of not doing the changes, etc.

These bits of information should be provided by the requirements originator in the original submission to the requirements gathering mechanism (RGM, Savannah or other). As above, this information should be entered into the "Issue/Requirement Description" at time of submission.


The process may not differ much from the current situation.

  1. Stakeholders submit their requirements. The requirement must contain:
    1. Title and description.
    2. Who will benefit.
    3. Implications of not following the requirement.
    4. Post EGEE considerations.
  2. Duplicate requirements are removed at TMB-wide level.
  3. The remaining requirements are voted on by the stakeholders.
    1. The priority of a task is now determined.
  4. Requirements are ordered by votes with each category by the TMB.
    1. Provider that will do the work determined.
    2. Starting date may be assigned.
  5. Requirements are assigned to the provider that will do the work.
    1. The first assignee is the leader.
    2. Leader subsequently assigns to the group/developer that will do the work.
    3. Starting date may be modified
    4. Ending date can be determined.
  6. The work for requirements should be linked to the work plan of the provider.
    1. Subsequently, the provider work plan should be linked to software patches.
  7. The progress of the requirements tasks is monitored.
    1. As task end-dates come due, the task should be reviewed.

-- JohnWhite - 15 Jan 2009

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2009-01-15 - JohnWhite
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback