EGEE Home | Intranet Home | EDMS Documents | Calendar | Meetings | Glossary
 
PTF Home | Meetings | Services | Testing | Requirements | Contacts
 
Responsibilities

The Project Technical Forum (PTF) will:

  • Merge requirements and use cases from the application, security, and operations groups.
  • Manage the evolution of the requirements and use cases.
  • Prioritize the requirements and verify if (and how) the defined use cases are satisfied by the EGEE architectural design.
  • Review the grid service specifications and control changes to those specifications and external interfaces.
  • Seek and promote common solutions where commonalities exist in the middleware or application domains.
  • Promote convergence with other grid projects by incorporating requirements from external projects using (or hoping to use) EGEE software and by discussing the EGEE design with other projects.

Notes:

  • The initial collection of requirements and use cases is expected to be done within each activity group although the PTF will by necessity work in parallel with this activity.
  • Input from outside application groups (e.g. ARDA, GAG) will be actively solicited, but formal representation is through the appropriate application representative.
  • JRA1 is responsible for the middleware services architecture and design and changes to the internals thereof. The PTF controls changes to external service specifications and interfaces.
  • Input from external projects is expected to happen after the first set of requirements, use cases, and design are completed.
  • The PTF is not formally responsible for any EGEE deliverables (specifically the architecture or evaluation documents), but will help those responsible and review where appropriate.
  • The group will meet monthly (in person at CERN) with additional meetings called when deemed necessary by the PTF members.

Composition

All of the members of the PTF should have significant experience with either developing or using grid systems. Application representatives should additionally have an excellent understanding of the computing needs of their field and of the methods typically employed by scientists working within that field.

The PTF should consist initially of a moderator and representatives from:

  • middleware re-engineering (JRA1)
  • applications (NA4)
  • operations (SA1)
  • security (JRA3)
  • networks (SA2 & JRA4)
The number and profile of the representatives from each activity will be reevaluated periodically to ensure that the PTF accurately reflects the focus within the project.

Other project members can be invited to the PTF meetings as required by the agenda.

Decisions

The PTF moderator reports directly to the project technical director. An agenda for each meeting will be published prior to each meeting. Minutes of all meetings will be kept with decisions made during the meeting clearly indicated. The minutes will be made available to all members of the project.

Decisions and recommendations will be made by clear concensus of the PTF representatives. If such a concensus cannot be achieved, then decisions will be made by concensus (as determined by moderator) when possible. If a concensus cannot be reached then the topic will be revisted at a later meeting after soliciting outside advice. If no concensus can be reached, the moderator will make the decision and the minutes will reflect the major issues for and against the decision. Such decisions should be reviewed by the technical director and the PEB.