Use Case Number

Init1pm13.pm14.1

Brief Description

A user should be able to capture a collection of metadata "things" - forms, CDEs, etc. that are named and have privileges.  There are some in global scope (managed by a certain few people), a user can create any number of them, and that user can make his publicly available (say, give me John's public collections, then give me John's Breast Stdy 123 collection).  There would be a service (API) with these types of functions.

Actor(s) for this particular use case

Metadata Specialist

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

A number of forms and CDEs are registered in the metadata repository.

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

The forms and CDEs of interest are captured in a 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. The Metadata Specialist creates a new Metadata Collection by
   1. The Metadata Specialist gives the Metadata Collection a name
   2. The Metadata Specialist gives the Metadata Collection a set of privileges that restrict viewing and editing to himself
2. The Metadata Specialist queries the metadata repository for forms of interest
3. The Metadata Specialist selects forms to be added to the Metadata Collection
4. The Metadata Specialist queries the metadata repository for CDEs of interest
5. The Metadata Specialist selects CDEs to be added to the Metadata Collection

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

Any number of forms and CDEs can be added to the Metadata Collection in any order

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.

Init1pm13 - Medidata

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

None.

Use Case Number

Init1pm13.pm14.2

Brief Description

Once created, a user should be able to modify a metadata collection by adding forms and CDEs, removing forms and CDEs, and modifying the privileges. 

Actor(s) for this particular use case

Metadata Specialist

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

A Metadata Collection has been created and the Metadata Specialist has privileges to modify it.

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

The Metadata Collection has been modified.

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. The Metadata Specialist selects the Metadata Collection to modify
2. The Metadata Specialist selects the forms and/or CDEs to remove
3. The Metadata Specialist changes the privileges for who can view and edit the Metadata Collection
4. The Metadata Specialist selects whether the Metadata Collection is globally discoverable and viewable by any user of the metadata repository
5. The Metadata Specialist adds forms and/or CDEs to the Metadata Collection

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

Any number of modifications can be applied in any order.

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.

Init1pm13 - Medidata

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

Certain users can make Metadata Collections globally accessible.

Use Case Number

Init1pm13.pm14.3

Brief Description

A user can query the metadata repository for all globally shared metadata collections and/or those that he has privileges to edit or view.

Actor(s) for this particular use case

Metadata Specialist

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

Metadata Collections exist and are shared with the user either globally or privately.

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

The Metadata Specialist has discovered Metadata Collections of interest.

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. The Metadata Specialist queries the metadata repository for globally available Metadata Collections
2. The Metadata Specialist queries the metadata repository for Metadata Collections he has permission to read
3. The Metadata Specialist queries the metadata repository for Metadata Collections he has permission to edit

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

The Metadata Specialist can query for any or all of the above Metadata Collection categories.

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.

Init1pm13 - Medidata

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

None.

Use Case Number

Init1pm13.pm14.4

Brief Description

A user can import the forms and CDEs associated with a metadata collection into a tool of interest, such as a CMDS (e.g. Medidata).

Actor(s) for this particular use case

Metadata Specialist

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

Metadata Collections exist and are shared with the user either globally or privately.

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

The Metadata Collection has been imported into the Metadata Specialist's tool, including all forms and CDEs.

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. The Metadata Specialist discovers a Metadata Collection of interest through his local tool
2. The Metadata Specialist selects the Metadata Collection to import
3. The Metadata Specialist completes the import.

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.

Init1pm13 - Medidata

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

None.