Standards » Architecture Area » PGI WG

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. Service Grids (Federations of managed computing resources) trust Users and push Activities, while Desktop Grids (Loose opportunistic Grids using idle resources) trust Applications and pull Activities. So, there is no interoperability at all. Interoperation can be achieved only by using a Bridge specially designed for this purpose. Detailed description of the Bridge marshaling Activities from Service Grids to Desktop Grids is outside the scope of this Use Case : The User wishing to submit an Activity only needs to know that this Bridge exists, and trust it. Other Actors of this Use Case do not even need to know that this Bridge exists.

Extract 'Prepare Desktop Grid Version of Application' as a prerequisite Use Case, and perform other improvements.

Provide the postconditions created by the preparatory steps

In the summary, indicate that the Application first has to be chosen.

The goal is to enforce the OO principle of encapsulation as much as possible for the User experience. This still requires administrators to perform a certain amount of preparatory steps, and the User to retrieve specific Credentials.

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

Add that the System keeps persistent detailed Log and Accounting for the Activity

First draft