Difference between revisions of "Functional requirements"

From ICA-AtoM
Jump to navigation Jump to search
Line 1: Line 1:
 
[[Main Page]] > [[System Requirements]] > Functional requirements
 
[[Main Page]] > [[System Requirements]] > Functional requirements
  
[[Functional requirements: intellectual and administrative control]]
+
[[Iintellectual 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 20:14, 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

Iintellectual 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:


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:
  • Support the arrangement and description of archival materials in order to make them accessible.
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:

  • requirement1
  • requirement2
Requirement quotation
  • link to ISAD(G).
  • link to ISAAR(CPF).
  • link to ISIAH.
  • link to ISDF.
  • link to OSARIS.
Associated metadata requirements
  • link to metadata requirement.
Associated quality requirements
  • link to quality requirement.
Associated technical requirements
  • link to technical requirement.
ICA-AtoM implementation
  • discuss how ICA-AtoM implements requirement.
Known issues
  • discuss how any known problems with ICA-AtoM's current implementation / functionality.
User Manual sections
  • link to User Manual pages.