Re: [egov] Proposed Use Case template

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Diane.Lewis@usdoj.gov wrote:

>Thanks Farrukh... 
>i will start using it.... dl
>  
>
Thanks Diane.

I realized from your posting that the message I sent may had information 
loss when sent as HTML.
This time I am attaching the proposed template so that people can 
download it as an attachment without
losing the diagram and other formatting.

BTW the diagram is done with Together UML tool.

For a good and free UML tool see:

http://argouml.tigris.org/features.html

Thanks.

-- 
Regards,
Farrukh

Title: Use Case Template

Title

• Associate 2 RegistryObjects using an Ontology Class

Description

Currently ebXML Registry allows content to be associated using an
Association which has an optional
associationType that is defined by  a ClassificationNode within a
ClassificationScheme.

This use case envisions allowing content to be associated using an
Association which has an optional
associationType that is defined by  a Class
within an Ontology.
 
The meaning of the resulting association would be much more clearer and
precise.

Use Case Diagram: Associate 2 RegistryObjects using an Ontology Class

Actors

• Domain Expert
  
• Content Publisher
  
• Registry
  

Priority (Low, Medium, High)

• High

Pre-conditions

• Ontology must already be defined or be submitted along with the content being associated
  

Post-conditions

• None
  

Basic Flow

1. Domain experts publishes an ontology
2. Content Publisher publishes content #1
3. Content Publisher publishes content #2
4. Content Publisher publishes an Association that associates content #1 and content #2 using an ontology class reference as an associationType
   

Alternative flows…

• None

Exceptions

• None

Includes Use Cases

• None

Special Requirements

• None

Assumptions

• An Association class is used to associate the two content instances as is the case in version ebXML Registry 2.5
• Queries (different use case) may be submitted that discover associated content not only based on  associationType but also specific attributes  of the ontology class that  was used  as associationType.
  

Use Case Relationships

• None

Issues

• None