Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:14
Size: 2755
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:09:35
Size: 2756
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
See ["TaskC.1AnalysisDocumentDetails#ITMaintenance"] See [[TaskC.1AnalysisDocumentDetails#ITMaintenance]]
Line 20: Line 20:
See ["TaskC.1AnalysisDocumentDetails#ITMaintenanceFeedback"] See [[TaskC.1AnalysisDocumentDetails#ITMaintenanceFeedback]]
Line 22: Line 22:
See ["TaskC.1AnalysisDocumentDetails#ActiveBitPreservation"] See [[TaskC.1AnalysisDocumentDetails#ActiveBitPreservation]]
Line 52: Line 52:
||["Drift"] ||Responsible for system maintenance. || ||[[Drift]] ||Responsible for system maintenance. ||
Line 56: Line 56:
 * [:Bitstorage:Our requirements]  * [[Bitstorage|Our requirements]]

Analysis of Coordinate Bit Storage and Preservation

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

Prerequisites and Assumptions

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

Stakeholders

Stakeholder

Knowledge

Drift

Responsible for system maintenance.

Ressources

TaskA.3AnalysisDocument (last edited 2010-03-17 13:09:35 by localhost)