Difference between revisions of "Requirements"

From Archivematica
Jump to navigation Jump to search
Line 4: Line 4:
 
The Archivematica [[UML Activity Diagrams]] are the baseline requirements for the system's default [[Micro-services|micro-services]] workflow. These were derived from an in-depth analysis of the [http://en.wikipedia.org/wiki/OAIS ISO-OAIS] functions which led to a series of [[OAIS Use Cases]] and [[OAIS Activity Diagrams]].
 
The Archivematica [[UML Activity Diagrams]] are the baseline requirements for the system's default [[Micro-services|micro-services]] workflow. These were derived from an in-depth analysis of the [http://en.wikipedia.org/wiki/OAIS 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.
+
Each Archivematica software release builds on the OAIS use cases and implements a growing set of [[format policies]]. 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 [http://groups.google.com/group/archivematica discussion list]. They are documented in the [[development roadmap]] and [http://code.google.com/p/archivematica/issues/list issues list].
 
End-user requirements are derived from Archivematica pilot implementation projects and the project's [http://groups.google.com/group/archivematica discussion list]. They are documented in the [[development roadmap]] and [http://code.google.com/p/archivematica/issues/list issues list].

Revision as of 15:54, 1 November 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 format policies. 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--