Review Details
Document: gLite Use Case : Parallel Jobs Review ID: docr1199 Review Name: Initial Document Version: 2 Review Started By: Morris Riedel - 08/10/2010 3:30 PM EDT	Outstanding Required Reviewers: David Wallom Outstanding Optional Reviewers: Due Date: 08/12/2010 1:00 AM EDT Review Status: Open

Responses

Etienne URBAH: 08/31/2010 12:51 PM EDT   Comment: I am sorry, but you used a BAD template, which is perhaps suitable for dissemination of applications and academic papers, but NOT for professional Software Engineering. A Use Case for Software Engineering should primarily describe interactions between Actors and the System : – Name, Goal and Summary – System boundaries, – Actors, Stakeholders, … – Preconditions, – Triggers, – Basic course of events, indicating who sends which message to whom for which goal. – Postconditions   Attachment: gLite-Use-Case-Parallel-Jobs-Review-Etienne.doc (44 KB)

Morris Riedel: 08/19/2010 11:30 AM EDT   Comment: Interesting use case - a few more specific details in how the PGI specifications should overcome the limitations of BES etc. would be nice - everything else looks like similiar use case classes like within the DEISA use case   Attachment: 2010-08-19_PARALLEL_JOBS_MRi.doc (43 KB)