## page was renamed from A.3AnalysisDocument ##Analysis Documentation ## Headline such as "Analysis of Backup Requirements" = Analysis of Coordinate Bit Storage and Preservation = ## Add detailed explanation/analysis of the task(problem)/action. We, the developers of SB-DOMS, and Drift both agree that the bits of the DOMS data should be safely stored. However, we need to know what Drift means by "safe" and we need to influence their procedures, if we do not find them safe enough. To do that, we first need to agree among ourselves what we expect from bit storage. Following that, we'll approach Drift with these wishes and requirements and work out an agreement. The following TDR requirements need to be addressed when we fulfill this task: * Requirements to IT maintenance department: D1.1, D1.2, D1.5, D1.6, D1.7, D1.10, D2.1, D3.1, R30-47, R60, R74-76 * Requirements to IT maintenance department which we need to have feedback on: D1.3, D1.4, D3.4, R53, R61 * Active bit preservation required: B3.7, D1.5, R61 See [[TaskC.1AnalysisDocumentDetails#ITMaintenance]] See [[TaskC.1AnalysisDocumentDetails#ITMaintenanceFeedback]] See [[TaskC.1AnalysisDocumentDetails#ActiveBitPreservation]] ## 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? The estimation of this task is based on these notes, which also should be taken into consideration when implementing the task: '''BAM:''' Løbende kommunikation '''TE:''' Kåre+Toke, bitbevaring laves af drift '''TSH:''' IT håndeterer bitbev. Tid til forhandling, kommunikation, test osv. '''MKE:''' Test, kommunkation, 2 pers. hold. ansvarlige... '''KFC:''' Bitbevaring opfyldes af IT, men kommunikation og test ##== 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|| ||[[Drift]] ||Responsible for system maintenance. || == Ressources == ## List links to documents, wiki pages etc. that are relevant to this analysis. * [[Bitstorage|Our requirements]] ## * [:LinkToMyVersionControlledDocument:Link to document on user studies e.g. stored in SVN]