##Analysis Documentation ## Headline such as "Analysis of Backup Requirements" = Analysis of Write White Paper = ## Add detailed explanation/analysis of the task(problem)/action. While solving this task, we must address the following TDR requirements: * Document and communicate repository principles for TDR fulfilling requirements from A1.1, A1.2, A3.4, D1.8, R12, R73 * Need documentation of software dependencies: D2.2 * Requirements to IT maintenance department (Note: these are also addressed in Task A.3): D1.1, D1.2, D1.5, D1.6, D1.7, D1.10, D2.1, D3.1, R30-47, R60, R74-76 See [[TaskC.1AnalysisDocumentDetails#DocumentRepositoryPrinciples]] See [[TaskC.1AnalysisDocumentDetails#DocumentSoftwareDependencies]] See [[TaskC.1AnalysisDocumentDetails#ITMaintenance]] ## This may include use-case diagrams etc. attached like this: ## attachment:MyUseCase.png == 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]