Difference between revisions of "Release 0.3 Documentation"
Jump to navigation
Jump to search
(Created page with ' The system documentation for release 0.3 corresponds directly to each numbered activity in the Archivematica UML Activity Diagrams. The documentation provides instructions o…') |
|||
Line 1: | Line 1: | ||
+ | [[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. | 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. | 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. |
Revision as of 16:44, 3 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.