Formulla for calcuting number of days

Methodology : Object Oriented Methodology
                        Waterfall + Iterative + Prototyping

Total days
required for 1 module =    Requirement Capure ( usecase) 
                                      + Object modelling ( usecase/2) 
                                      + Normalisation (Usecase/2)
                                      + Database scripting(usecase/4)
                                      + Prototyping(usecase/4).

                                  = 2.5 UseCase + Delay (U/4)

Here Usecase = number of days required for captuing
                          requirements.


Kindy check it with your project and give me feedback.

HBJ
Monday, May 10, 2004

Use an array for the months and remember that there is a 100 yr exception to the leaps rule, but also a 400 yr exception to the 100 year one.

HTH,

Fred
Monday, May 10, 2004

Ehr... I don't think that's what he meant by calculating days, Fred.

And I don't think the formula works. It depends heavily on the type of application you're developing. And also (I've seen this happening) on the speed at which your client decides on their own requirements. If they decide very s.l.o.w.l.y. on some feature that is really easy to do, it would disturb your formula.

Use an array for the clients.
Tuesday, May 11, 2004

I wonder how you could adjust this for the times where the client changes their mind at any given (and usually inconvenient) time.

nakedCode
Tuesday, May 11, 2004

Sorry, not poking fun but I found it rather amusing.

For<mulla>. Mulla?? You mean like Moslem? That's what we call a dervish here in vernacular Hindi ;-)

I hope I didn't sound profane to our Moslem brothers, 'coz I didn't mean to.

Sathyaish Chakravarthy
Tuesday, May 11, 2004

If someone can find a reliable formulaic way of estimating project/task duration, I will bow to you (momentarily).


From everything I've seen, people I've worked with, and projects I've worked on, really the *ONLY* good estimation technique involves some experience in the given area and the skill of those involved.

"Let's see... doing X takes an experienced coder about Y days, so doing X2 will take Y2 days for a comparable coder."

That's one thing that's not factored into your equation.... skill and/or ability.  While it might take me a day to implement some things, it will take me longer to do a nice UI.

KC
Tuesday, May 11, 2004

It's easy to imagine a requirement this quick to specify but difficult to implement.

"This module should output the first prime number greater than an arbitrary input number in the range 1 through 2 to the 100th power. It should be coded in C, run on Windows, and take less than 50 KB and 1.5 seconds to execute."

It's difficult to implement however: so although it took only 30 seconds to specify, it would take more than a minute and a quarter to implement.

Similarly, it's possible to spend a long time specifying something that is easy to implement.

Christopher Wells
Tuesday, May 11, 2004

  Recent Topics

  Fog Creek Home