Archival and Preservation Services Implementation Plan
- Patrick Schmitz (Unlicensed)
Boilerplate structure and text below
Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page.
Plans
This may begin with prose, and expand into something like a project plan at some point. This need not be a complete schedule, but it will make sense to include the steps and approaches, milestones, etc.
Dependencies
This should be a description of the major dependencies of the Archival and Preservation Services implementation. Example dependencies could be 3rd party utility classes, core classes or packages, other services, etc.
Test Plan
This should describe how the Archival and Preservation Services implementation will be tested. The testing here could include white box style test, unit test, and/or integration tests.