(Note change in use case template. Now submitting use case diagram
inline rather than as an attachment)
ID: 5
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)
Pre-conditions
- Ontology must already be defined or be submitted along with the
content being associated
Post-conditions
Basic Flow
- Domain experts publishes an ontology
- Content Publisher publishes content #1
- Content Publisher publishes content #2
- Content Publisher publishes an Association that associates
content #1 and content #2 using an ontology class
reference as an associationType
Alternative flows…
Exceptions
Includes Use Cases
Special Requirements
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
Issues
--
Regards,
Farrukh
|