Functional requirements
Jump to navigation
Jump to search
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 > Functional requirements
Functional requirements state what the system must be able to do. The requirements provide:
- Parameters for designing the system.
- Criteria for testing the system (used in initial release and future iterations and upgrades).
- Planning guidelines for developing the system (improve existing or add new functionality).
- Documentation for standards compliance (link requirements to relevant international or national descriptive standards)
- A framework for structuring user-end documentation (step-by-step procedures for how to do things in the system).
Functional requirements are organized hierarchically, with core requirements, broken down into sub- and sub-sub-requirements. around the core functions of repositories holding archival material. ICA-AtoM currently focuses on two functions, breaking these down into sub- and sub-sub-requirements:
- Establish intellectual and administrative control over archival materials
- Provide an interface that supports user interaction with the system (create, read, update, delete, search
Each functional requirement includes the following information:
Requirement number | FR-x.x.x (unique tracking number assigned to requirement) |
---|---|
Requirement name | Descriptive name assigned to requirement. |
Requirement specification | Brief description of requirement: system must do X. |
Sub-requirements | If the requirement is broken down into sub-requirements, provides links to these. |
Requirement quotation | Links to standards or other documents: why must the system be able to do X? |
Associated metadata requirements | Links to functional requirements: what data must the system capture in order to be able to do X? |
Associated quality requirements | Links to quality requirements: what design and interface features must the system have to do X well? |
Associated technical requirements | Links to technical requirements: what system architecture, hardware / software configurations, and programming rules must the system implement to do X? |
ICA-AtoM implementation | Brief description of how ICA-AtoM implements X. |
Known issues | Brief indication of known problems or limitations in the current version of ICA-AtoM that should be addressed in future releases. |
User Manual sections | Links to the User manual sections that provide step-by-step instructions for doing X. |
Establish intellectual and administrative control over archival materials
Requirement number | FR-1 |
---|---|
Requirement name | Establish intellectual and administrative control over archival materials |
Requirement specification | The system must:
|
Sub-requirements |
---
Implement a system of control
Requirement number | FR-1.1 |
---|---|
Requirement name | Implement a system of control. |
Requirement specification | The system must: |
Sub-requirements |
---
Support multi-level description
Requirement number | FR-1.1.1 |
---|---|
Requirement name | Support multi-level description. |
Requirement specification | The system must be able to: |
Requirement quotation | |
Associated metadata requirements | |
Associated quality requirements | |
Associated technical requirements | |
ICA-AtoM implementation | |
Known issues | |
User Manual sections |
---
Accommodate different levels as the highest level of arrangement and description
Requirement number | FR-1.1.2 |
---|---|
Requirement name | Accommodate different levels as the highest level of arrangement and description. |
Requirement specification | The system must be able to: |
Requirement quotation | |
Associated metadata requirements | |
Associated quality requirements | |
Associated technical requirements | |
ICA-AtoM implementation | |
Known issues | |
User Manual sections |
---
Accommodate different systems for assigning reference codes
Requirement number | FR-1.1.3 |
---|---|
Requirement name | Accommodate different systems for assigning reference codes. |
Requirement specification | The system must be able to: |
Requirement quotation | |
Associated metadata requirements | |
Associated quality requirements | |
Associated technical requirements | |
ICA-AtoM implementation | |
Known issues | |
User Manual sections |
---
Implement descriptive standards
Requirement number | FR-1.2 |
---|---|
Requirement name | Implement descriptive standards. |
Requirement specification | The system must: |
Sub-requirements |
Create and control description records
Requirement number | FR-1.3 |
---|---|
Requirement name | Create and control descriptions |
Requirement specification | The system must: |
Sub-requirements |
|
Describe archival materials
Requirement number | FR-1.4 |
---|---|
Requirement name | Describe archival materials. |
Requirement specification | The system must: |
Sub-requirements |
|
Describe actors
Requirement number | FR-1.5 |
---|---|
Requirement name | Describe actors. |
Requirement specification | The system must: |
Sub-requirements |
|
Describe archival institutions
Requirement number | FR-1.6 |
---|---|
Requirement name | Describe archival institutions. |
Requirement specification | The system must: |
Sub-requirements |
Template
Requirement number | MR-x |
---|---|
Requirement name | Name |
Requirement specification |
The system must:
|
Requirement quotation |
|
Associated metadata requirements |
|
Associated quality requirements |
|
Associated technical requirements |
|
ICA-AtoM implementation |
|
Known issues |
|
User Manual sections |
|