##Analysis Documentation ## Headline such as "Analysis of Backup Requirements" = Analysis of Guide for Introducing New Collections / Material Into DOMS = ## 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 should consult the following TDR requirements: * Collection specific requirements we should consider to some degree in DOMS B1.3, B1.4, B1.6, B2.3, C2.1, R72 See [[TaskC.1AnalysisDocumentDetails#CollSpec]] == 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:''' ekstern + intern ? '''TE:''' Skal bruges af rigtige mennesker '''TSH:''' No comments. '''MKE:''' Differentiate internal and external doc. '''KFC:''' Eksternet henvendt dokumentation + internt henvendt dokumentation ##== 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. || ##== Resources == ## 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]