Balazs, Morris, Luigi, Johannes and all, While populating the Requirement tables of the Requirements Wiki at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... : For the Requirement Status, I suggest to modify the list of possible values, and now use following list : - Proposed (Not validated as 'in scope' and open for detailed discussion yet) - Rejected (Not understandable, Out of scope, Contains hidden prerequisites, ...) - Dupl. (Duplicate, therefore Closed) - Premature (Detailed specification, Specification of implementation, ...) - Open (In scope, and under detailed discussion) - Agreed YES - Agreed NO Do not hesitate to make remarks or suggestions. Best regards. ----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr ----------------------------------------------------- On Wed, 17/03/2010 22:51, Etienne URBAH wrote:

Balazs, Morris, Luigi, Johannes and all,

Implementing point 1 of the PGI sessions notes taken Tuesday 16 March 2010, I have created a 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem...

This 'Requirements Wiki' is also referenced inside the main page of the PGI Wiki.

Compared to the sessions notes :

- I have added an 'Areas' column containing the list of areas to which the current requirement apply

- For the 'Status' column, I propose to add a 'Dupl.' value, meaning 'Duplicate, therefore Closed'.

I have chosen the {Area}{Req}.{SubReq} numbering schema, permitting to easily : - identify the main relevant area, - relate requirements and sub-requirements.

I have begun populating the Requirement tables, in particular in following areas : - Non‐functional - Information Service - Security (Authentication, Authorization, Delegation) - Job Management and I am continuing.

When proposing your own requirements, please keep the existing Wiki syntax, in order to : - keep an homogeneous layout, - facilitate editing.

Do not hesitate to make remarks or suggestions concerning the global layout, decomposition per main area, numbering schema, ... If any global modification is agreed, I can easily perform it.

I am available for further information and help.

Best regards.

----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr -----------------------------------------------------

On Tue, 16/03/2010 18:30, Johannes Watzl wrote:

...

Dear all,

See attached the notes from today's PGI sessions. Please send your comments to the list.

Best, Johannes

Balazs, Morris, Luigi, Johannes and all, Inside the 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... I have performed following work : - Inside the 'Activity Management' section, group similar requirements, and move a depending requirement after the base requirements it depends on - Add 1 requirement to the 'Application Repository' section - Add 1 requirement to the 'Job Description' section I am available for further information and help. Best regards. ----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr ----------------------------------------------------- On Fri, 26/03/2010 21:05, Etienne URBAH wrote:

Balazs, Morris, Luigi, Johannes and all,

Inside the 'Requirements Wiki' containing Requirements tables at http://forge.gridforum.org/sf/wiki/do/viewPage/projects.pgi-wg/wiki/Requirem... I have performed following work :

- Rename 'Job' as 'Activity' (except for Job Description = JSDL)

- Add 'Source' column (describing the origin of the requirement), and make some proposals

- Format as table rows the background information from the 'RFP of the US XD programme, NSF 08-571'

- Add requirements - Execution Service must NOT try to provide all grid functionalities - Execution Service MUST expose one or several state where the Activity is finished

- Inside Non Functional requirements : - Mention JSPG (Joint Security Policy Group), - Write traceability and logs as independent requirements

- For all requirements, check and if necessary update the 'Areas' attribute

- Move some requirements in appropriate section, and add appropriate dependencies

- Inside most sections (except Activity Management), move a depending requirement after the base requirements it depends on

- Add 'Application Repository' section and move appropriate requirements there

- For queries of Activity Status, clarify by having separate requirements inside following sections : - Information Service, - Logging and Bookkeeping (in particular for already finished jobs), - Activity Management

Besides, Morris RIEDEL has added counts of requirements.

Each time you know the source or origin of a requirement, please fill the 'Source' field accordingly.

Do not hesitate to make remarks or suggestions concerning the global layout, decomposition per main area, numbering schema, ... If any global modification is agreed, I can easily perform it.

I am available for further information and help.

I plan to attend the next OGF PGI telephone conference on Thursday 01 April 2010 at 15h30 CET.

Best regards.

----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr -----------------------------------------------------