##Analysis Documentation ## Headline such as "Analysis of Backup Requirements" = Analysis of Create preservation strategy documentation = ## Add detailed explanation/analysis of the task(problem)/action. ## This may include use-case diagrams etc. attached like this: ## attachment:MyUseCase.png When addressing this task, we must address the following TDR requirements: * Must have preservation strategy for certain classes of digital material B1.1, B3.1, R65, R66 * It must be possible to document how we ensure integrity A3.6 * Need preservation strategy (Planets): B3.1, B3.2, B3.5, B3.9, B3.10, R65-67 See [[TaskC.1AnalysisDocumentDetails#FormatPreservationStrategy]] See [[TaskC.1AnalysisDocumentDetails#Integrity]] See [[TaskC.1AnalysisDocumentDetails#PreservationStrategy]] == Prerequisites and Assumptions == ## Describe any prerequisites and assumptions that are important for this analysis, e.g.: ## What can we rely on? ## Which assumptions must hold in order to solve the problem described in this document? == Risks and Potential Problems == ## Describe anything that may cause problems when solving this task. == Stakeholders == ## List of links to any relevant stakeholders. That is, people who has knowledge about this task or in any other way are relevant to contact for input. ||Stakeholder ||Knowledge|| ||[[Link to stakeholder]] ||Usability expert. || ||[[Link to Bart Ender]] ||Expert on mixing margaritas || ||[[Link to out esteemed customer]] ||The guy with the money who actually may know what he wants. || == Ressources == ## List links to documents, wiki pages etc. that are relevant to this analysis. * [[LinkToMyRessource|Use case diagram xx]] * [[LinkToMyVersionControlledDocument|Link to document on user studies e.g. stored in SVN]]