egov message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [egov] Proposed Use Case template
- From: John.Borras@e-Envoy.gsi.gov.uk
- To: OASIS eGov list <egov@lists.oasis-open.org>
- Date: Mon, 9 Feb 2004 08:00:57 +0000
TC members
Could I have your views on this for
discussion at our next TC meeting please.
Farah - to include on agenda please.
John
Farrukh Najmi <Farrukh.Najmi@Sun.COM>
27/01/2004 16:18
|
To
| OASIS eGov list <egov@lists.oasis-open.org>
|
cc
|
|
Subject
| [egov] Proposed Use Case
template |
|
Folks,
We seem to agree on the value of use case identification as a tool to nail
down requirements. It would help
if we all use a consistent use case template.
To facilitate use case discussions, attached below is a sample use case
that I propose as a template for other use case discussion.
Feel free to suggest improvements or ask questions.
We could start by applying this template to use cases for Semantic Interoperability.
Thanks.
--
Regards,
Farrukh
-------- Original Message --------
(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
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…
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
PLEASE NOTE: THE ABOVE MESSAGE WAS RECEIVED FROM THE INTERNET.
On entering the GSI, this email was scanned for viruses by the Government
Secure Intranet (GSI) virus scanning service supplied exclusively by Energis
Communications in partnership with MessageLabs.
GSI users see http://www.gsi.gov.uk/main/notices/information/gsi-003-2002.pdf
for further details. In case of problems, please call your organisational
IT helpdesk.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]