Contents of this Page

Mark CDE as preferred for class

Use Case Number	Init1hm1.pm25.1
Brief Description	When creating registering a class in the metadata repository, it may be desirable to mark a common data element as having a preferred definition for that class. This will enable CDE and class reuse later.
Actor(s) for this particular use case	Metadata Specialist
Pre-condition The state of the system before the user interacts with it	A class has been registered in the metadata repository with associated attributes as a set of CDEs.
Post condition The state of the system after the user interacts with it	A CDE has been marked as preferred for a class.
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 Metadata Specialist discovers the class in the metadata repository The Metadata Specialist selects a preferred CDE to use as the definition for class reuse. The Metadata Specialist saves the selection back to the metadata repository.
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.	ICR IRWG requirements Init1hm1 - ICR IRWG requirements
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	The "preferred" CDE/definition must be discoverable.

Discover preferred CDE for class

Use Case Number	Init1hm1.pm25.2
Brief Description	When reusing a class, it is desirable to select a definition that the original modeler considers preferred.
Actor(s) for this particular use case	Metadata Specialist
Pre-condition The state of the system before the user interacts with it	A class has been registered and has a preferred CDE selected.
Post condition The state of the system after the user interacts with it	The user has discovered the preferred CDE.
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 Metadata Specialist discovers a class for reuse The Metadata Specialist discovers whether a CDE has been marked as preferred If not, the Metadata Specialist looks for CDEs within the class that have been most reused in other information models
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.	ICR IRWG requirements Init1hm1 - ICR IRWG requirements
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Reuse CDE and constrain value set

Use Case Number	Init1hm1.pm25.3
Brief Description	After a CDE has been discovered for reuse, it should be possible to constrain the CDE allowable values by a specific value set.
Actor(s) for this particular use case	Metadata Specialist
Pre-condition The state of the system before the user interacts with it	A CDE exists in the metadata repository.
Post condition The state of the system after the user interacts with it	The CDE has been constrained by a set of allowable values.
Steps to take The step-by-step description of how users will interact with the system to achieve a specific business goal or function	A Metadata Specialist discovers a CDE for reuse The Metadata Specialist selects a set of allowable values for the CDE The Metadata Specialist reuses the newly constrained CDE
Alternate Flow Things which would prevent the normal flow of the use case	The value set may be selected from a registered ontology.
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.	ICR IRWG requirements Init1hm1 - ICR IRWG requirements
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Non-technical metadata management interface

Use Case Number	Init1hm1.pm25.4
Brief Description	Most of the expertise in any given domain rests with the subject matter experts, many of which are often non-technical. Therefore, it is critical to provide an interface that allows for metadata to be created and annotated by non-technical users.
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	Metadata has been created and updated by a non-technical 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 accesses the metadata management interface The Cancer Researcher creates and updates metadata in an intuitive fashion. The system provides step-by-step guidance on reuse and harmonization The Cancer Researcher saves the metadata
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.	ICR IRWG requirements Init1hm1 - ICR IRWG requirements
Fit criterion/Acceptance Criterion How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?	None.

Content

Space Tools

Init1hm1.pm25 - ICR IRWG requirements

Mark CDE as preferred for class

Discover preferred CDE for class

Reuse CDE and constrain value set

Non-technical metadata management interface