Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Home

Common Project - Semantic Requirements

Error rendering macro 'rw-search'

null

Page History

Versions Compared

Old Version 5

changes.mady.by.user Unknown User (mcconnellp)

Saved on Mar 22, 2010

compared with

New Version 6

changes.mady.by.user Unknown User (mcconnellp)

Saved on Apr 12, 2010

Key

This line was added.
This line was removed.
Formatting was changed.

...

Use Case Number	Init1dbw6.pm8.4
Brief Description	Once a user identifies a service workflow of interest, he should be able to share that workflow in a way that makes it easy to encode, share with colleagues, reuse/rerun, modify, and extend.
Actor(s) for this particular use case	Cancer Researcher
Pre-condition The state of the system before the user interacts with it	A set of services of interest has been identified.
Post condition The state of the system after the user interacts with it	The service workflow is stored and shared.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Cancer Researcher encodes and saves the workflow The Cancer Researcher identifies the other uses that can access the workflow The Cancer Researcher reruns the workflow at a later date The Cancer Researcher modifies the workflow at a later date The Cancer Researcher copies and extends the workflow with additional steps
Alternate Flow Things which would prevent the normal flow of the use case	The steps listed above can be performed in any order any number of times with the exception that the workflow must be encoded and saved first.
Priority The priority of implementing the use case: High, Medium or Low	Low.
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1dbw6 - Support caB2B to integrate services on caGrid Support caB2B Services to integrate data on grid
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	The workflow must be accessible in much the same way as any other service.

Define a metadata category

Use Case Number	Init1dbw6.pm8.5
Brief Description	The Metadata Category is the ability to save a particular view of classes and their associations in order to find services that match. For example, a Cancer Researcher may be interested in A->B->C and wants to be able to query services that support those classes and associations.
Actor(s) for this particular use case	Cancer Researcher
Pre-condition The state of the system before the user interacts with it	None.
Post condition The state of the system after the user interacts with it	A Metadata Category has been defined.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Cancer Researcher discovers a set of classes, attributes, and associations that he is interested in The Cancer Researcher saves these as a Metadata Category in a repository
Alternate Flow Things which would prevent the normal flow of the use case	The Cancer Researcher may want to load, update, delete, or share an existing Metadata Category.
Priority The priority of implementing the use case: High, Medium or Low	Low.
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1dbw6 - Support caB2B to integrate services on caGrid Support caB2B Services to integrate data on grid
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Discover services by metadata category

Use Case Number	Init1dbw6.pm8.6
Brief Description	Once a Metadata Category is created, a Cancer Researcher can use it to discover services that support the underlying classes, attributes, and associations.
Actor(s) for this particular use case	Cancer Researcher
Pre-condition The state of the system before the user interacts with it	A Metadata Category has been identified.
Post condition The state of the system after the user interacts with it	A set of services of interest have been identified.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Cancer Researcher loads the Metadata Category The Cancer Researcher invokes the appropriate function to discover services that support the underlying parts of the Metadata Category The Cancer Researcher selects a subset of the services of interest
Alternate Flow Things which would prevent the normal flow of the use case	None.
Priority The priority of implementing the use case: High, Medium or Low	Low.
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1dbw6 - Support caB2B to integrate services on caGrid Support caB2B Services to integrate data on grid
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Perform operations based on metadata category

Use Case Number	Init1dbw6.pm8.7
Brief Description	Once a user has identified a set of services that support a Metadata Category, he can invoke operations across those services and aggregate the results based upon the classes, attributes, and associations within the Metadata Category.
Actor(s) for this particular use case	Cancer Researcher
Pre-condition The state of the system before the user interacts with it	A set of services of interest has been identified via the Metadata Category.
Post condition The state of the system after the user interacts with it	The results from the cross-service operation are aggregated and presented to the user.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	The Cancer Researcher selects the operation (such as "query") he would like to invoke on the selected services The services are invoked and results are returned The results are aggregated based upon the Metadata Category The aggregated results are returned to the user
Alternate Flow Things which would prevent the normal flow of the use case	None.
Priority The priority of implementing the use case: High, Medium or Low	Low.
Associated Links The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.	Init1dbw6 - Support caB2B to integrate services on caGrid Support caB2B Services to integrate data on grid
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Accessibility | Contact CBIIT | FOIA | HHS Vulnerability Disclosure | Comment Policy
U.S. Department of Health and Human Services | National Institutes of Health | National Cancer Institute | USA.gov
NIH ... Turning Discovery Into Health®

Powered by Atlassian Confluence, themed by RefinedTheme