Review Details
Document: NAREGI/RENKEI Use Case Review ID: docr1213 Review Name: Review of Doc ( instead of PPT) Document Version: 2 Review Started By: Morris Riedel - 08/19/2010 12:26 PM EDT	Outstanding Required Reviewers: Outstanding Optional Reviewers: Due Date: 08/20/2010 1:00 AM EDT Review Status: Closed

Responses

Etienne URBAH: 08/31/2010 2:22 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: NAREGI-RENKEI-Use-Case-Review-Etienne.doc (1.54 MB)

Oxana Smirnova: 08/19/2010 1:41 PM EDT   Comment: It is clearly a challenging application, but the description of the use case should be improved in order to put it into the PGI context. Specifically, it is not clear where lies the border between application-specific functionality and the generic grid functionality. Also, relevance to OGF standards and interoperability/interoperation issues has to be outlined.   Attachment: RENKEI-NAREGI.usecase-OS.doc (1.54 MB)

Morris Riedel: 08/19/2010 12:28 PM EDT   Comment: Nice use case and having a great application. The use case would benefit from a few more details on how the PGI specification might be beneficial to overcome limitations of BES/JSDL et al. or current proprietary approaches.   Attachment: 2010-08-19_RENKEI-NAREGI.usecase.r0_MRi.doc (1.54 MB)