Documents / gridforge / Input Documents / Use cases / EDGI Use Case 'Prepare Desktop Grid Version of Application'
Revisions
2010-09-09 10:49:49 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Remove duplicated text and footnote.
7.0
None
application/msword
64 kB
2010-09-09 09:33:48 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
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.
6.0
None
application/msword
64.5 kB
2010-09-09 05:29:00 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Shorten description of the Bridge
5.0
None
application/msword
58 kB
2010-09-01 10:21:09 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Lot of thanks to Ilya SAVERCHENKO for his valuable comments. This Use Case is performed more easily if the Application already runs on the Service Grid, but this is NOT an absolute prerequisite. 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. This Bridge does not simply forward the Activities from one Grid to another Grid, but it is a stateful server performing syntactic translations, Activity buffering, Activity concatenation or expansion, Activity wrapping, ..., which is summarized here as 'marshaling'. Detailed description of this Bridge is outside the scope of the Use Case : Only the Bridge Manager needs to have a detailed knowledge of it. The other Actors only need to know that this Bridge exists, and trust it.
4.0
None
application/msword
58 kB
2010-08-12 08:02:40 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Lot of thanks to Tim for his valuable comments. I have taken into account most of them.
3.0
None
application/msword
56.5 kB
2010-08-12 06:49:36 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Tim Parkinson / Steve Crouch Review Comments
2.0
None
application/msword
60.5 kB
2010-07-16 12:57:53 by Redmine Admin
EDGI Use Case 'Prepare Desktop Grid Version of Application'
gridforge/Input Documents/Use cases/EDGI-Use-Case-Prepare-Desktop-Grid-Version-Of-Application.doc
Extracted from the 'Marshal Activities from Service Grid to Desktop Grid' EDGI Use Case
1.0
None
application/msword
54.5 kB
(1-7/7)