New Requirement Manual

From EGIWiki
Jump to: navigation, search

This page describes the process of submitting requirements to EGI through the EGI RT system. Other aspects of requirement gathering and processing in EGI is described on another page.

The evolution of the European Grid Infrastructure is driven by the users. Therefore capturing feedback, requirements and recommendations from various EGI communities is a key goal for the EGI-InSPIRE project and for the EGI collaboration as a whole. The EGI-InSPIRE project has setup and operates a Request Tracker system (RT) to collect requirements from EGI stakeholders and to track the evolution and resolution of these needs. This page is a manual for those who wish to communicate requirements and feedback to EGI with the RT system.


1) New requirements can be submitted by anybody who has an account in the EGI Single Sign On (SSO) System. Register for an EGI SSO account if you do not have one yet.


2) Login with your SSO account into the RT system. You can also go to one of the RT dashboards, for example to the dashboard for NGIs

Note: if you still cannot access the requirements queue, please send an e-mail to ucst@egi.eu including your SSO username in the message


3) Go to requirement submission form by choosing the "requirements" queue in the top right drop-down listbox and then clicking the "New ticket in" button next to it. (Clicking the button is not mandatory in some browsers.)

Note: make sure that the queue called "Requirements" is chosen!

Rtlogin.PNG


4) Specify the details of your requirement in the form

Note: make sure that at least the following fields are filled: "Subject", "Category (level 1)", "Requestor (level 1)", "Impact" and "Describe the issue below"

  1. Provide a succinct, still descriptive title as Subject of the requirements Mandatory
  2. Choose from the "Category (level 1)" and "Category (level 2)" lists to classify the type of requirement. In the Category 1 list Mandatory
    1. "Support Service" covers user-facing tools such as the applications database, training event registry, Web sites, etc.
    2. "Support action" covers human services provided for user communities, for example training, consultancy, etc.
    3. "Unified Middleware Distribution (UMD)" covers middleware services, such as componenst and tools of the ARC, gLite, UNICORE middleware
    4. "Operational tools" cover software services provided for operators of EGI components
    5. "User tools and applications" cover software tools and applications that sit on top of the middleware and provide generic or domain specific functionality for scientific communities
    6. "Non-functional" covers requirements that cross-cut multiple domains thus cannot be linked to a single category. Note: Choose any of the relevant categories if the requirements cuts multiple categories.
  3. In the Requestor (level 1) and Requestor (level 2) fields specify the community on behalf you submit the requirement Mandatory
  4. "Tags": associate words to requirements in order to simplify the lookup and grouping of requirements. Optional
  5. "Impact": choose the impact of your requirement Optional
  6. Try to be informative with the description of the requirements in the Describe the issue below field. Cover the motivations and reasons for the requirement Mandatory


New req colored.png



The submitted requirements are processed according to the requirement processing workflow.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export