Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Use Case - Iterative registration of information models
Use Case Number | Initdbw8.S1 U1 |
---|---|
Brief Description | An information modeler needs to be able to begin recording semantics the of the information model automatically from the moment he begins his design. He needs to be able to find existing content or register new content, deriving the semantics needed for registration from his model throughout the development of the information modeling process capturing changes and recording then automatically as he edits the model. |
Use Case Level: (Business Summary, User Goals, Subfunctions) | Business Summary level |
Actor(s) for this particular use case | |
Pre-condition | - Information modeler has a documented end user scenario for which he needs to develop a information model. |
Post condition | The information model has been recorded in the semantic infrastructure and appropriate registries for others to discover and use. |
Steps to take | 1. Modeler opens his modeling tool to begin designing his information model |
Alternate Flow |
|
Priority |
|
Associated Links |
| Fit criterion/Acceptance Criterion | 1.
Use Case - Descriptive Name
creates and names the associations between classes in the diagram | |
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
1. All or parts of the model already exist in the repository by a different 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 | High |
---|---|
Associated Links | |
Fit criterion/Acceptance Criterion |
|
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?
...
A new model can be developed and the system finds a prior version, allows the modeler to reuse it. |
Scrollbar | ||
---|---|---|
|
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?
...