Difference between revisions of "Functional requirements"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
[[Main Page]] > [[System Requirements]] > Functional requirements | [[Main Page]] > [[System Requirements]] > Functional requirements | ||
− | [[ | + | [[Intellectual and administrative control]] |
Functional requirements state what the system must be able to do. The requirements provide: | Functional requirements state what the system must be able to do. The requirements provide: |
Revision as of 19:15, 25 January 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 > Functional requirements
Intellectual and administrative control
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 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: support arrangement and description of archival holdings).
- Search and use descriptions: support search and use of archival materials by researchers.
Each functional requirement includes the following information:
- Requirement number (for cross-reference purposes).
- Requirement name.
- Requirement specification (system must do X).
- Requirement quotation (which section of which standard requires that the system do X?).
- Associated metadata requirements (what data must the system capture to do X?).
- Associated quality requirements (what features must the system have to do X well from a user / interface point of view?).
- Associated technical requirements (what system architecture, programming rules, hardware / software configurations must the system implement to do X?)
- ICA-AtoM implementation (how does ICA-AtoM implement X?).
- Known issues (problems with current implementation / functionality).
- User Manual sections (links to step-by-step user 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
Implement descriptive standards
Create and control description records
Describe archival materials
Describe actors
Describe archival institutions
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 |
|