Hmm.. tricky!
Somewhere there have been a document stating time needed based map complexity.
Also it comes down to what kind of documents, specefikations and so on it exists....
Easiest is to give a statment like "IF requiered documentation and test data exists" .. as this part always are a hassle.
as for breakup...
1. Data Collection
( specs... and so on )
2. Data Analyzing.
(check that all is up to date and is enough to work with )
3. Format analyzing
( what format is required ... do it allready exists
and if not how is the structure )
4. Format Creation.
( nope it didnt exist.. create a new typetree from specs )
5. Map prestudy.
( Where from and where to ... passwords..usersinfo and
so on.. both test and prod environemtn )
5. Map generation
( Create mappings with requiered typetrees...)
6. Tests
( with all data in test environemnt )
7. System creation and Deployment
8. "real tests" .. start to end... with live data...
9. Swap it all to production when working
and all this times 150
Hmm.. not to easy... I guess it all depends on how well
you know the product...
We usally say
2 days for a simple map
5 days for a moderate map
7 days for a complex map
and this is all IF all documents and specs , testdata is in order... As this usally are things you can affect and are delivered by the customer...
I shall se if i can find the document with the definition of map complexity and tme required... and post it.
// Myggiz