##Analysis Documentation ## Headline such as "Analysis of Backup Requirements" = Analysis of Document fulfilled TDR requirements = ## 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 documentation, we should consult the following TDR requirements: * Communicate requirements out of scope for DOMS but relevant for SB: A2.*, A3.3, A4.*, A5.*, B1.2, B3.11, C1.*, C2.1, C3.1, C4.*, D1.6, D1.8, D1.9, D2.3, D3.1, D3.3, D3.4, D3.5, D3.6, R01-10, R13-14, R16-47, R57-58, R72, R74-76, R78 * Organizational procedures required around deployment A3.*, D1.8, D.2.2 See [[TaskC.1AnalysisDocumentDetails#CommunicateReqsOutOfScope]] See [[TaskC.1AnalysisDocumentDetails#OrgProcDeployment]] == 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]