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.
Use cases describe interactions with an application from the end-users' point of view in a variety of what if scenarios. Use cases:
- Test the application's current functionality.
- Identify issues that need to be addressed in future releases.
- Support development of user-end documentation.
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 (UC = use case), the number establishes its position in the hierarchy. Six main use cases have been identified:
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.
Each use case includes some or all of the following information:
- Use case number: UC-x.x.x, unique tracking number assigned to the use case.
- Use case name: descriptive name assigned to requirement.
- Context (parent requirements): links to higher-level cases, if applicable.
- Sub-requirements: links to lower-level cases, if applicable.
- Overview: brief description of the scenario.
- Actors: the main actor(s) involved in the scenario.
- 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 describing the scenario as leading to a successful outcome.
- Exceptions / variations: other possible variations, including unsuccessful outcomes ("Scenario B", "Scenario C" etc).
- Functional requirements: links to associated functional requirements (FR-x).
- Metadata requirements: links to associated metadata requirements (MR-x).
- Technical requirements: links to associated technical requirements (TR-x).
- Diagrams: work-flow or other diagrams illustrating the scenario.
- User Manual: links to the User manual sections that provide step-by-step instructions for activities relating to the scenario.
Index of use cases
The following is the full index to use cases identified to date.
- UC-1.1 Define system scope
- UC-1.2 Implement a system of intellectual control
- UC-2.5.1 Assign a unique identifier to a unit of archival material
- UC-2.5.2 Assign a title to a unit of archival material
- UC-2.5.3 Assign a unit to the hierarchy of arrangement
- UC-2.5.4 Record the dates of archival materials
- UC-2.5.5 Record the extent of archival materials
- UC-2.5.6 Identify the creator of archival materials
- UC-2.5.7 Describe the history of custody of archival materials
- UC-2.5.8 Describe the conditions of access and use of archival materials
- UC-2.5.9 Indicate the existence of related archival materials
- UC-2.6 Describe actors that interact with archival materials