Differences between revisions 10 and 11
Revision 10 as of 2008-12-19 09:21:11
Size: 5477
Editor: jrg
Comment:
Revision 11 as of 2010-03-17 13:12:30
Size: 5477
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 85: Line 85:
[[BR]] <<BR>>
Line 106: Line 106:
[[BR]] <<BR>>
Line 122: Line 122:
[[BR]] <<BR>>

How far are we, and how far do we need to get

On 16-12-2008 the DOMS-team had a planning day where we broke down the DOMS system in parts. For each part we estimated percentages showing how far we are in implementing the part fully, and percentages showing how far we need to get in order to satisfy the political goal of a DOMS housing "De Danske Aviser" (that DOMS is codenamed DOMS-Beta).

Percentages are estimates

System part or chore

Status 16-12-2008

Needed for DOMS-Beta

Needed for final DOMS

DOMS-GUI

80%

80%

100%

DOMS-GUI-Summa

40%

not needed

100%

DOMS-GUI-Export

10%

not needed

100%

DOMS-GUI-Import Quadriga (streams)

10%

not needed

100%

DOMS-GUI-Import Horizon (poster)

10%

not needed

100%

Object creation

87%

not needed

100%

PID generator

65%

65%

100%

Fedora

80%

80%

100%

Validator

30%

30%

100%

License

0%

not needed

100%

LDAP

0%

not needed

100%

Connection to real Summa

30%

60%

100%

Add file

17%

60%

100%

Bit storage

80%

82%

100%

Agreements with maintenance

25%

100%

100%

Ingester for "De Danske Aviser"

30%

100%

100%

Content "De Danske Aviser"

0%

100%

100%

The bold-faced percentages relate to what needs to be done in order to meet the political goal of "De Danske Aviser".

How much time / manpower do we need to get it done

On 17-12-2008 the DOMS-team had a planning day where we gave first early estimates to the efforts needed for meeting the Avis-goal.

The following were our estimates of how much intensive development time we need for meeting the required Avis-goal percentages. The estimates were guessed for the two people (JRG and PKO) who have been assigned time in this low-priority DOMS-period.

Connection to real Summa

  • Simple harvester
    • Wrapping (2 md JRG)
    • Summa-input discussion (1 md JRG)
    • Code (4-5 md JRG)
  • index.xslt - general (3 md JRG)
  • html.xslt -> Avis? (4 md JRG + 4 md Niels/Gitte/Dorete)

Add file

  • Bitstorage part (5 - 8 md JRG)
  • GUI object manipulation (1 - 2 md JRG)
  • Object manipulation (2 - 3 md JRG)
  • File characterizer (1 - 2 md JRG)

Bit storage (1 md JRG)

Agreements with maintenance

  • Machines for installations and bitstorage (4 md JRG)
  • Install scripts and installation guide (8 md JRG)

Ingester for "De Danske Aviser"

  • FoxML ingest (1 md PKO)
  • Bulk file attach (10 md PKO + 10 md JRG)
  • Bulk publish -> Validator (4 - 6 md JRG)

Content "De Danske Aviser"

  • 3-4 content models (4 md PKO + 4 md JRG)
  • Templates (1 md JRG)
  • Schemas + learning (2 md PKO + 2 md ABR + 2 md EK)
  • Converting-batch-script/tool (20 - 40 md PKO + 7 md JRG)
  • Modelling (data model) (2 md PKO + 2 md JRG + 2 md EK)
  • (Pre)-Ingest of the product (including test + release test) (10 - 20 md PKO + 6 md JRG)

In summary, the time needed for intense development was estimated to:

PKO: 49 - 79 md

JRG: 70 - 79 md

EK: 4 md

Niels/Gitte/Dorete: 4 md

With our given manpower, when can we be done

In total, PKO has 15 hours per week, and JRG has 37 per week.

20% is scheduled for knowledge building. That leaves 12 hrs PKO and 29.6 hrs JRG.


With the assumption that all meetings, lunch, and non-productive parts of a day were not included in the estimates given by the DOMS team:

A survey of the last 80 days has shown that 20% of the time is spent on meetings. Lunch takes 7% of a day. We assume 10% of a day is non-productive. These leave 7.6 hrs PKO and 18.6 hrs JRG.

PKO has 100% DOMS time, whereas JRG has 50% DOMS time. That leaves 7.6 hrs PKO and 9.3 hrs JRG, DOMS time.

JRG is assigned with project management as well as development. After talking with experienced project managers (TSH & MV), project management time was estimated to 25%. This leaves 7.6 hrs PKO and 7.0 hrs JRG, DOMS development time.

Not counting holidays and sick-days, a rough guess would be that

PKO's part of DOMS-Beta would take between 48 and 77 weeks. JRG's part of DOMS-Beta would take between 74 and 84 weeks.


With the assumption that all meetings, lunch, and non-productive parts of a day were included in the estimates given by the DOMS team:

PKO has 100% DOMS time, whereas JRG has 50% DOMS time. That leaves 12 hrs PKO and 14.8 hrs JRG, DOMS time.

JRG is assigned with project management as well as development. After talking with experienced project managers (TSH & MV), project management time was estimated to 25%. This leaves 12 hrs PKO and 11.1 hrs JRG, DOMS development time.

Not counting holidays and sick-days, a rough guess would be that

PKO's part of DOMS-Beta would take between 30 and 49 weeks. JRG's part of DOMS-Beta would take between 47 and 53 weeks.


In summary

Our lowest possible estimate is: PKO's part of DOMS-Beta would take 30 weeks. JRG's part of DOMS-Beta would take 47 weeks.

Our highest possible estimate is: PKO's part of DOMS-Beta would take 77 weeks. JRG's part of DOMS-Beta would take 84 weeks.

And those are not counting holidays and sick-days.

DOMSBetaEstimates (last edited 2010-03-17 13:12:30 by localhost)