## page was renamed from 2009Tasks/APIAnalysisDocument
##Analysis Documentation

## Headline such as "Analysis of Backup Requirements"

= Analysis of API =

## Add detailed explanation/analysis of the task.

## This may include use-case diagrams etc. attached like this:
## Link to original: [http://merkur/svn/doms/trunk/MODULE/docs/MyUseCase.dia]
## png on the wiki page: http://merkur/svn/doms/trunk/MODULE/docs/MyUseCase.png

We need the following webservice interfaces.
 * Wrapper of Fedora API-M (approx. 15 methods, estimate 2 md)
 * PID generator - including making the code ready for production (1 method, estimate 2 md)
 * ECM (enhanced content models, 3 methods, estimate below)
 * Characterization (1 method, estimate below)
 * Bitstorage (4 methods, estimate below)
 * Object manipulation (2 methods, estimate below)
   * Preparation of the four tasks above is estimated to 2 md.

And in addition
 * Open sourcing of the API (estimate 3 md)



== 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 Stakeholders are of course important to the analysis, but we have dedicated pages for these, and they should only be included here if this task poses additional risks or new problems...


What other tasks does this task rely on? Which other tasks have parts that we need before performing this task?

We list, for each of the above subtasks, the tasks they depend on.

 * API-M wrapper potentially depends on Fedora 3 project integration
 * PID-generator has no dependencies
 * ECM depends on Fedora 3 project integration and Fedora 3.2 setup
 * Characterization depends on Characterization :D
 * Bitstorage depends on Bitstorage and Maintenance agreement
 * Object manipulation depends on Bitstorage, Fedora 3 project integration, and Fedora 3.2 setup
 * Open sourcing depends on Maintenance agreement, Fedora 3.2 setup, Bitstorage, Fedora 3 project integration, and Characterization


== 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]