Difference between revisions of "Use cases"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
| − | <span id="USC-"></span> | + | <span id="USC-1.2.1"></span> |
{| border="1" cellpadding="2" | {| border="1" cellpadding="2" | ||
|- valign="top" align="left" style="background:#00008B; color:white" | |- valign="top" align="left" style="background:#00008B; color:white" | ||
| − | | colspan="3" | | + | | colspan="3" | Implement arrangement policy |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| width="100" rowspan="4" style="background:silver" | Summary | | width="100" rowspan="4" style="background:silver" | Summary | ||
! width="150" | ID number | ! width="150" | ID number | ||
| − | | width="700" | | + | | width="700" | 1.2.1 |
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Overview | ! Overview | ||
| | | | ||
| − | + | An institution establishes its arrangement policy and customizes the application to implement it. | |
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Primary actor | ! Primary actor | ||
| − | | | + | | Institution. |
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Secondary actor | ! Secondary actor | ||
| − | | | + | | Administrator. |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| rowspan="5" style="background:silver" | Description | | rowspan="5" style="background:silver" | Description | ||
! Preconditions | ! Preconditions | ||
| − | | | + | | n/a |
| − | |||
| − | |||
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Trigger | ! Trigger | ||
| − | | | + | | n/a |
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Successful outcome | ! Successful outcome | ||
| | | | ||
| − | * | + | *Application customized so users implement policy. |
| − | |||
| − | |||
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Main scenario | ! Main scenario | ||
| | | | ||
| − | + | 1. Institution establishes the highest level of arrangement it will employ. | |
| − | + | ||
| − | + | 2. Institution establishes the number of levels of arrangement it will employ. E.g. series is the highest level, three series levels (series, sub- and sub-sub-series) allowed. | |
| + | |||
| + | 3. Administrator edits "Levels of description" taxonomy so drop-down lists use levels and terms allowed by policy. | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
Revision as of 17:29, 30 April 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 >
| Implement arrangement policy | ||
| Summary | ID number | 1.2.1 |
|---|---|---|
| Overview |
An institution establishes its arrangement policy and customizes the application to implement it. | |
| Primary actor | Institution. | |
| Secondary actor | Administrator. | |
| Description | Preconditions | n/a |
| Trigger | n/a | |
| Successful outcome |
| |
| Main scenario |
1. Institution establishes the highest level of arrangement it will employ. 2. Institution establishes the number of levels of arrangement it will employ. E.g. series is the highest level, three series levels (series, sub- and sub-sub-series) allowed. 3. Administrator edits "Levels of description" taxonomy so drop-down lists use levels and terms allowed by policy. | |
| Exceptions / variations | TextHere | |
| Requirements | Functional requirements | |
| Metadata requirements | ||
| Quality requirements |
| |
| Technical requirements | ||
| Diagrams | DiagramHere | |
| ICA-AtoM | Implementation | TextHere |
| Known issues |
| |