Difference between revisions of "Requirements"
| Line 9: | Line 9: | ||
--Requirements pages-- | --Requirements pages-- | ||
| + | * [[CONTENTdm_integration]] | ||
* [[File_identification_requirements]] | * [[File_identification_requirements]] | ||
* [[Format_policy_registry_requirements|Format Policy Registry (FPR)]] | * [[Format_policy_registry_requirements|Format Policy Registry (FPR)]] | ||
* [[File_Browser_Requirements]] | * [[File_Browser_Requirements]] | ||
| − | * [[ | + | * [[Archivists_Toolkit_integration]] |
* [[Transfer_Backup_Requirements]] | * [[Transfer_Backup_Requirements]] | ||
* [[Transfer_and_SIP_creation]] | * [[Transfer_and_SIP_creation]] | ||
Revision as of 14:08, 18 September 2012
Main Page > Documentation > Requirements
The Archivematica UML Activity Diagrams are the baseline requirements for the system's default micro-services workflow. These were derived from an in-depth analysis of the ISO-OAIS functions which led to a series of OAIS Use Cases and OAIS Activity Diagrams.
Each Archivematica software release builds on the OAIS use cases and implements a growing set of media type preservation plans. These are based on an analysis of open standards, open source normalization tools and the significant characteristics of specific media types.
End-user requirements are derived from Archivematica pilot implementation projects and the project's discussion list. They are documented in the development roadmap and issues list.
--Requirements pages--