Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Init1pm1.1 - System Compatibility Review
Use Case Number | Init1pm1.1 |
---|---|
Brief Description | Since its inception, caBIG has been founded on (1) developing and defining standards, tooling, and architecture to enable interoperability, and (2) determining whether existing systems meet the basic requirements for interoperability. While the nature of the "compatibility reviews" may change, there is a clear need to provide the community a way to understand at what level different applications meet interoperability requirements. It is highly desirable that the review process be as simple and transparent as possible both for the developer/owner of a system and the reviewers. In this way, review artifacts should be able to be generated in an automated fashion based on the model itself or its registration in the metadata repository. Furthermore, a reviewer using the compatibility review software should be able to access real-time the artifacts that they need to perform a review. |
Init1pm1.1 - 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?
...
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
---|---|
Pre-condition | A model has been created with all the necessary semantic information for registration and a "compatibility" review. |
Post condition | The artifacts have been generated for the compatibility review and they have been linked in the compatibility review system. |
Steps to take |
2. |
Alternate Flow | It should not be a requirement to use the caBIG-defined tooling to generate compatibility artifacts. Instead, there should be an alternate flow that involves the creation of the artifacts de novo, registration of the metadata, and providing the artifacts to the review system. |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion |
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
|
Fit criterion/Acceptance Criterion | 1. |
Use Case - Descriptive Name
|
Init1pm1.2 - Metadata Reuse and Registration
Use Case Number | Init1pm1.2 |
---|---|
Brief Description | The modeling tool and metadata registry should facilitate easy reuse of existing metadata. Specifically, this includes sophisticated/seamless type-ahead functionality for finding common data elements and semantic concepts, the metadata repository should support the notion of common data elements that overlap between system and provide touch-points for interoperability, the registration process should be linked directly with the modeling tool, and Information Modelers should have the ability to perform metadata loads into a "sandbox" metadata repository on their own. |
Use Case Number | n.n |
Brief Description | |
Actor(s) for this particular use case | Information Modeler |
Pre-condition | None |
Post condition | A model has been created, semantic metadata has been added, and it has been registered in the metadata repository. |
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
| Fit criterion/Acceptance Criterion | 1.
Use Case - Descriptive Name
| ||
Use Case Number | n.n | |
Brief Description |
| |
Actor(s) for this particular use case |
| |
Pre-condition |
| |
Post condition |
| |
Steps to take | 1. 2. | |
Alternate Flow | None. | |
---|---|---|
Priority | High | |
Associated Links | ||
Fit criterion/Acceptance Criterion | |
|
Scrollbar | ||
---|---|---|
|