SourceForge : artf5566: Need an archetypical usecase section

Project: TSC Trackers > Tasks for our Technical Strategy Document > View Artifact

Artifact artf5566 : Need an archetypical usecase section

Tracker:	Tasks for our Technical Strategy Document
Title:	Need an archetypical usecase section
Description:	Mark L. commented: "By “use case pattern” I am referring to an “archetype”. An archetype is an idealized model of a person, object or concept from which similar instances are derived, copied, patterned or emulated. An example might be “Compute-intensive Grid” for resource sharing and utilization with vaiations having to do with “static versus “ dynamic”; single versus mulitple data center; single versus multiple domain; etc. These archetype patterns can be further composed into things such as “execution” “data access and movement”, etc." ----- The implication being that the usecases in the current document (v0.3) fail to capture a high enough level of abstraction.
Submitted By:	David Snelling
Submitted On:	09/04/2006 10:18 AM EDT
Last Modified:	01/03/2007 1:08 PM EST

	Status / Comments		Change Log		Associations		Attachments

Status
Group: *
Status:*	Open
Category: *
Customer: *
Priority: *	5
Assigned To: *	None
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

David Snelling: 01/03/2007 1:08 PM EST
	Comment:	Agreed to put this on hold for now and use the OGSA use case document as a reference to expand the functional use cases in the document. Left open but set priority to lowest (meaning defered).
	Action:	Update Priority changed from 1 to 5

David Snelling: 09/04/2006 11:06 AM EDT

Comment:

One approach is as follows:

1) Describe the usecase like the following example:

Use Case Description: This use case deals with sharing compute resources across multiple server clusters running grid/resource scheduling software 
from different providers 

Use Case Attributes: Compute-intensive, static resource sharing, single data center, single domain 

2) Build the Road map around these use cases with one table per use case. Assuming our segmentation is by area, the table structure might look like 
this:

Area          Spec or BKM       Status      NextMilestone

Compute      OGSA-BES        Draft         Oct 06 - Spec

Security       ....

Data            ....

... 

Doing this requires agreement on the segmentation and a level of detail in the use cases and the spec/BKM.

Action:

Update

David Snelling: 09/04/2006 10:18 AM EDT
	Action:	Create

Return