The real problem is often that management tries to make a estimate of the
time.
the WORST thing a developer can do is accept some time frame that ANOTHER
person tells YOU.
Only YOU know how fast you can develop.
On a typical development team, the productivity will vary by as much as 10
times.
That means one guy can do in 3 weeks what another person will take 30.
That means your estimate of time to completing can be 4.5 weeks to 52 weeks
(1 month, or a year?).
So, the only reliable estimate is one made BY YOU!
Further more, you need to write out a functional spec. This is simply a
English narrative of what the product will do. You also should consider
throwing in some screen designs (use your favorite drawing
program...especially one that comes with pre-built widgets you can place on
the screen. (you MUST use something that lets you work at least as fast as
drawing on paper).
Once you got this functional spec, you THEN can start the estimating
process.
You can read about doing this, and WHY you should do this here:
So, if you ask developer a, he might be able to do the project in 4 weeks
(and, that is fair and honest answer).
If you ask developer B, he might be able to the project in 15 weeks (and,
that is a fair and honest answer).
Also, if any estimate breaks down parts the of development process into
days...you need to throw it out. The finer you can break down the parts, and
make a estimate for each part..the better you are off. The estimate needs to
be broken down by hours for each task.
You next question at this point is:
Well, golly, if I design the thing..then yes..I can make a good
estimate!
So, writing out on paper what the system has to do FORCES you to do a lot of
design work first.
Further, you don't mention what is the skill level of the developers (and,
also..what tools?). With a possible 200 users..are you talking about a 100%
web based system here?
How many different data entry screens do you need? (25, or 150?).
So, you got to start breaking this down into parts and pieces. You don't
have to design the whole thing, but you better come up with some screen
mockups, or something..as you have to have SOME idea as the number of
screens involved.
It is kind of like building a house. Until you have SOME idea as to the
number of bedrooms, and the kinds of finishing and how large they will
be...you can't really come up with a good estimate.