Difference between revisions of "Release 0.3 Documentation"

From Archivematica
Jump to navigation Jump to search
Line 4: Line 4:
  
 
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 add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.
 
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 add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.
 +
 +
*[[0.3 Ingest]]
 +
*[[0.3 Archival Storage]]
 +
*[[0.3 Data Management]]
 +
*[[0.3 Access]]
 +
*[[0.3 Administration]]

Revision as of 14:44, 4 September 2009

Main Page > Documentation > Release 0.3

The system documentation for release 0.3 corresponds directly to each numbered activity in the Archivematica UML Activity Diagrams. The documentation provides instructions on how these activities might be carried out using the current Archivematica release.

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 add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.