Difference between revisions of "Requirements"
| Line 9: | Line 9: | ||
--Requirements pages-- | --Requirements pages-- | ||
| − | * [[ | + | * [[Archivists Toolkit integration]] |
| − | * [[ | + | * [[CONTENTdm integration]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* [[Database Data Management]] | * [[Database Data Management]] | ||
| + | * [[File Browser Requirements]] | ||
| + | * [[File identification requirements]] | ||
| + | * [[Format policy registry requirements|Format Policy Registry (FPR)]] | ||
| + | * [[Metadata import]] | ||
| + | * [[Transfer Backup Requirements]] | ||
| + | * [[Transfer and SIP creation]] | ||
| + | |||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Revision as of 17:50, 4 October 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--