UML Activity Diagrams

From Archivematica
Revision as of 18:36, 11 February 2020 by Sallain (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main Page > Requirements > UML Activity Diagrams

This page is no longer being maintained and may contain inaccurate information. Please see the Archivematica documentation for up-to-date information.

These Archivematica UML Activity Diagrams are the baseline requirements for Archivematica.

Wherever possible, these activities are assigned to software or technical tools. If it is not possible to automate these functions in the current system iteration, the functions are incorporated into a manual procedure to be carried out by the end user. This ensures that the entire set of requirements are being carried out in the system, which is an integrated whole of software, people and procedures. The goal is to improve the level of automation and sophistication with each system iteration.

These diagrams are revisions of the OAIS Activity Diagrams which, in turn, were derived from the OAIS Use Cases analysis. These revisions were based on a scenario analysis that tried to focus on the pragmatic steps necessary to accomplish each core OAIS function using existing technology and archival business processes.

Each activity is likely to generate some metadata and have one or more information entities as an input and output. However, these will be captured in a separate metadata requirement analysis and information model. Likewise, each activity may be governed or restricted by one or more policy or procedures but these are also intentionally left out of the diagram for simplicity. Except where they are explicitly noted, these diagrams assume that there no errors in the activity flow, i.e. these are 'sunny-day' scenarios.

[edit] Ingest

[edit] Archival Storage

[edit] Data Management

[edit] Access

[edit] Administration

Personal tools