Difference between revisions of "Use cases"
| Line 99: | Line 99: | ||
|} | |} | ||
| + | |||
Note that most of this detail will only be found at the lower-level cases. Higher-level cases will typically only include the case name, number, and overview, with links to the lower-level sub-requirements. | Note that most of this detail will only be found at the lower-level cases. Higher-level cases will typically only include the case name, number, and overview, with links to the lower-level sub-requirements. | ||
Revision as of 18:04, 5 May 2008
Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.
Main Page > System Requirements > Use cases
Purpose
Use cases describe interactions with the application from the end-users' point of view. Use cases provide tests of the application's functionality and identify issues that need to be addressed in future releases.
Structure
Use cases are clustered around the same broad categories as the functional requirements. Like the latter, use cases are organized hierarchy with high-level scenarios broken down into more specific tests (sub- and sub-sub-cases). To facilitate cross-references and links, each case has been assigned an alpha-numeric code: the alpha prefix designates its type (USC = use case), the number establishes its position in the hierarchy. Six main use cases have been identified:
- USC-1 Implement a system of control
- USC-2 Add / edit content
- USC-3 Translate content
- USC-4 Access content
- USC-5 Import / export content
- USC-6 Administer the system
Use case actors
The following generic actors are invoked in the use cases:
- Institution: a body having custody and control of archival materials.
- Archivist: a staff member of an Institution.
- Network: a group of Institutions sharing descriptions and other information relating to archival materials.
- Administrator: a person responsible for the application of an Institution or Network.
- Researcher: a person who accesses the archival materials held by Institutions.
Information
Each use case includes the following information:
| USC-x.x.x (unique tracking number assigned to case). | ||
| Summary | Use case name | Descriptive name assigned to use case |
|---|---|---|
| Overview |
Brief description of the scenario. | |
| Actor |
The main actor(s) involved in the scenario. | |
| Description | Preconditions |
Other use cases whose completion is a precondition for the current case. |
| Trigger |
The event that initiates the current case. | |
| Successful outcome |
The outcomes of a successful resolution of the scenario. | |
| Main scenario |
Step-by-step breakdown description of the scenario ("Scenario A"). | |
| Exceptions / variations |
Other possible variations, including unsuccessful outcomes ("Scenario B", "Scenario C" etc). | |
| Requirements | Functional requirements |
Links to associated functional requirements (FNC-x). |
| Metadata requirements |
Links to associated metadata requirements (MTD-x). | |
| Technical requirements |
Links to associated technical requirements (TCN-x). | |
| Diagrams |
Work-flow or other diagrams illustrating the scenario. | |
Note that most of this detail will only be found at the lower-level cases. Higher-level cases will typically only include the case name, number, and overview, with links to the lower-level sub-requirements.
Index
USC-1 Implement a system of control
- USC-2.5.1 Assign a unique identifier to a unit of archival material
- USC-2.5.2 Assign a title to a unit of archival material
- USC-2.5.3 Assign a unit to the hierarchy of arrangement
- USC-2.5.4 Record the dates of archival materials
- USC-2.5.5 Record the extent of archival materials
- USC-2.5.6 Identify the creator of archival materials
- USC-2.5.7 Describe the history of custody of archival materials
- USC-2.5.8 Describe the conditions of access and use of archival materials
- USC-2.5.9 Indicate the existence of related archival materials