Unified Harmonization Process

Use Case Number	Init1bes9.pm11.1
Brief Description	Common data elements can be entered into the metadata repository through a variety of different tools, including a UML loader, manual curation through the web interface, and forms development. There must be a common harmonization mechanism enforced by the metadata repository such that all mechanisms by which CDEs are entered can be reused by all types of users.
Actor(s) for this particular use case	Metadata Specialist
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	CDEs are harmonized in the system
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
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. ..

Use Case - Descriptive Name

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
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...

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
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...

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
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...

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
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...