Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Init1hm2.pm6.1

Brief Description

Users of systems that are designed to collect data items may need to collect data elements that were not previously described by metadata.  In this case, it is necessary that the user is able to create the metadata necessary to begin data capture.

Brief Description

Actor(s) for this particular use case

  Metadata Specialist

Pre-condition
The state of the system before the user interacts with it

Metadata for a data element does not exist 

Post condition
The state of the system after the user interacts with it

Metadata for the data element exists and data can be captured 

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.
..

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or 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.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

1. The Metadata Specialist identifies data elements to be added to a system for data capture
2. The Metadata Specialist searches all available data elements and determines that none of them meet his needs
3. The Metadata Specialist creates new data elements locally for data capture and adds it to the system
4. The Metadata Specialist begins data collection using the newly created data elements

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

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

High 

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.
 

• Init1hm2 - Reuse or create new data elements at runtime
• Reuse or create new data elements at runtime

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?  
1.
2...

The data element is stored locally for reuse in local cancer center systems.  It contains all the necessary metadata for sharing data (next use case).

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Init1hm2.pm6.2

Brief Description

Once data elements are dynamically created for local use in data capture, it is necessary to publish the metadata for data sharing.  It may be necessary to harmonize the metadata with other systems, but it is desirable that the metadata be managed at least locally.

Brief Description

Actor(s) for this particular use case

Metadata Specialist 

Pre-condition
The state of the system before the user interacts with it

The data element is locally available. 

Post condition
The state of the system after the user interacts with it
 

The data element is shared with other organizations in a distributed fashion and contains all metadata necessary for data sharing.

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or 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.

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

1.
2...

1. The Metadata Specialist selects the data elements to share with other organizations
2. The Metadata Specialist adds any additional information needed
3. The Metadata Specialist performs any additional harmonization needed
4. The Metadata Specialist completes the sharing of the data elements

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1.
2.

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

High. 

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.
 

• Init1hm2 - Reuse or create new data elements at runtime
• Reuse or create new data elements at runtime

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?
1.
2...

The data elements are available to other researchers for reuse, and all metadata necessary for data sharing is available.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Init1hm2.pm6.3

Brief Description

Data elements that have been created dynamically locally and shared should be reusable by other researchers and organizations.  Users should be able to browse for, select, and reuse them in their data collection forms.

Brief Description

Actor(s) for this particular use case

Metadata Specialist 

Pre-condition
The state of the system before the user interacts with it

Data elements are shared by other users in other organizations. 

Post condition
The state of the system after the user interacts with it

Shared data elements are reused for data collection. 

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function
1.
2.

1. The Metadata Specialist identifies data elements to be added to a system for data capture
2. The Metadata Specialist searches all local and shared data elements to determine if any match his needs
3. The Metadata Specialist identifies shared data elements and reuses them in his forms for data capture

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

High. 

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.
 

• Init1hm2 - Reuse or create new data elements at runtime
• Reuse or create new data elements at runtime

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

1.
2.. Data elements are reused, data can be captured, and data can be shared based on reused metadata.