Use cases

Main Page > System Requirements > Use cases

Use cases describe scenarios from the end-users' perspective of their day to day activities. Individual use cases are clustered around the same broad categories as the functional requirements:

• USC-1 Establish a system of control
• USC-2 Add / edit content
• USC3 Translate content
• USC-4 Access content
• USC-5 Import / export content
• USC-6 Administer the system

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 the following information:

Use case name
Summary	ID number	USC-x.x.x (unique tracking number assigned to requirement)
	Overview	Brief description of the scenario.
	Primary actor	The main actor involved in the scenario.
	Secondary actor	Other actors 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.