Standards » Architecture Area » PGI WG

Add collaboration diagram. Inside chapter 'Use Case Situation Analysis and PGI Expectations', provide relevant standards for each required high level functionality.

Place the footnote about 'Activity' at the first occurrence of this term.

This document was originally designed using a template adequate for Software Engineering.
It is formatted here using the currently OGSA-based official PGI template, which is adequate for dissemination and academic papers about Applications, but inadequate and misleading for software engineering of Grid Middleware.

Lot of thanks to Ilya SAVERCHENKO for his valuable comments. 'Activity' is defined by GLUE 2.0 as 'Unit of work which is submitted to a Service via an Endpoint'. What needs to be frozen is NOT the physical resources processing work of the malicious User, but the tasks created locally for this malicious User. 'Use Cases' are NOT literary work requiring perfect English , but technical work requiring accuracy and precision; therefore, from the suggested corrections about English, I have taken into account only those which do NOT pose a risk of confusion or imprecision.

Lot of thanks to Tim PARKINSON for his valuable comments. I have taken into account all of them.

Most Grid Resources are not managed centrally, but locally on Sites, which are separate administrative domains. The ‘Business rules’ section details in which extent Grid Operation enforces the OO principle of encapsulation.

For the System, give as examples EGI, EELA, DEISA

Improve and reformat using the 'PGI Software Engineering Use Case' template

A Service Grid User is a member of a UserDomain

Give VO as example of UserDomain (Glue 2.0) - Add immediate rejection of User credentials as first devious flow

Minor improvements

Add devious flows

First draft