Re: How to design proper classes when the requirements are quite
complex?
Arne VajhQj wrote:
Lew wrote:
Mark Space wrote:
Two years is not that long for a new software project.
But it is way, way, waaaaaaay too long to wait for such a project to
produce any useful product.
If you are managing a software project, set it up so that first useful
product results start happening in about a week. A month is not too
soon to have a prototype of important basic features.
When the actual development start something should be delivered
frequently. Every 2 month or every 2 weeks or whatever (every week
sound as XXP though).
But the project start long time before that. It is not unusual
to spend 6 months on requirements.
Even requirements should work with prototypes iteratively.
Don't wait six months to put something on the screen. You might find that it
doesn't look or work the same on a computer as it did on paper.
For this to work, management must tolerate wholesale tossing out of prototypes
and complete rewrites in the coding phase, at least sometimes and at least at
first.
--
Lew