Review Details
Document: SpecialQoSComputingUsecase.docx Review ID: docr1194 Review Name: Initial review Document Version: 1 Review Started By: Oxana Smirnova - 08/05/2010 9:17 AM EDT	Outstanding Required Reviewers: Outstanding Optional Reviewers: Due Date: 08/31/2010 1:00 AM EDT Review Status: Closed

Responses

Morris Riedel: 08/19/2010 9:03 AM EDT   Comment: Interesting use case - initially reservations have been agreed to be a lower priority in PGI, because of two reasons: (1) overlap with WS-Agreement folks - (2) too complex to start with and no existing implementations - however it may become a higher priority again   Attachment: 2010-08-19_Special_Quality-of-Service_Computing_MRi.docx (25.5 KB)

Etienne URBAH: 08/09/2010 1:44 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: Genesis-Use-Case-Special-Quality-of-Service-Computing-Review-Etienne.doc (40 KB)

Oxana Smirnova: 08/05/2010 9:21 AM EDT   Comment: A very nice description of a use case; since it does not mention any specific infrastructure or middleware, it may serve as one of the example for the EGI use case, as surely EGI will face same issues, and advance reservation (as well as other Special QoS capabilities) will need to be implemented in a standard manner across different middlewares.