This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.pgi-wg/discussion.meetings.topc4349 at Sun, 06 Nov 2022 11:28:03 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: pgi-wg     Discussion > Meetings > Meeting on 2010-09-30, 15:30 (CET) > List of Posts
Forum Topic - Meeting on 2010-09-30, 15:30 (CET): (1 Item)
View:  as 
 
 
Meeting on 2010-09-30, 15:30 (CET)
Participants:
Morris (chair), Etienne, Mark, Oxana, Emmanouil, Luigi, Steve, 

(1)
Agenda

Presenting the use cases with requirement

OGF!



(2)
PGI Glossary 

- Entered Public Comment Period
- 30 days comment
- encourage your colleagues to comment on it
- Link: http://www.ogf.org/gf/docs/?public_comment
- off-the-agenda now for 30 days, then revise



(3)
PGI use case document

- OGF Editor very soon
- Waiting for one final use case revision


(4)
Specification work

(i)
170 requirements - tough

(ii)
glossary - step done

(iii)
use cases - step done

(iv)
requirements & specification - next step 
- # 170 requirements 
- with use cases we can narrow them down on the critical few
- Reminder: OGF30 Event - use cases present with requirements
- categorize them!
-- job description
-- job submission & management
-- data management
-- information flow
- Major Goal: claritify towards reals specification work

(v)
overall approach discussions at OGF30 too
- modular approach as best as possible
- one spec for job description?
- one spec for job submission
- one spec for data management
- one overall PGI Profile (where are things put in that not match elsewhere)


Example: job description part
- requirements for job description
- JSDL 1.1 + JSDL SPMD 2.0 + PGI Profile (scalabale Time)
- JSDL 2.0 -> 

Comments:

Etienne
- requirements (prioritization)
- job description parts

Mark
- outline is ok
- use case -> requirements
- requirements -> spec

Oxana
- single doc per approach whether thats merged from different documents is not that important
- technical / user oriented - checked too --> Technical focus


Next step
- rough consensus usage towards specification
- overlaps
- prioritization
- outcome: smaller requirements list
- where profile/new version of another spec


PGI Requirements list 
- Only yes are allowed
- Link:

http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.pgi-wg/docman.root.drafts.condensed_requirement_lists/
doc16062


TBD (All) : 
Derive requirements from the use cases you stand for


Comments:

Emmanouil 
- travel, until thursday

Etienne
- publish beginning next week

Luigi
- probably beginning next

Mark
- Andrew...

Oxana (Gromacs)
- filter (use case)
- filter (requirement job description)
- filter (excel sheet yes only)
- filter (priority)
- can't promise

Steve
- aligned with Mark use cases
- pass-on the use cases


Shahbaz/Morris
- mide next week


AOB?!


- DGSI interested (Emmanouil)
- Perhaps late use case? 

 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.pgi-wg/discussion.meetings.topc4349 at Sun, 06 Nov 2022 11:28:03 GMT