Posted by Jerry Stuckle on 10/07/07 22:15

Ben C wrote:
> On 2007-10-07, Jerry Stuckle <jstucklex@attglobal.net> wrote:
> [...]
>> There is a formal process to managing projects, just like there is for a
>> lot of things. And it works. But when you've never used this process,
>> you can come up with all kinds of rationalizations as to why it won't work.
>
> But apparently when you have used it you can't come up with any as to
> why it does.

Read back through this thread. I have. You've just ignored it. Or
you've (incorrectly) claimed it isn't so.

But here is a lot more detail - just so you can poo-poo it again.

A good design process starts with requirements gathering, and ensures
everyone agrees on the requirements for the project.

From the requirements you design the project - database, classes, etc.
You look at the flow between objects.

Once the design is completed, you can start writing the code. You
already know what is required, and the code fits together. There is no
trial and error. There is no rewriting code because everything was
designed first.

And when there are changes to the requirements, you can see exactly what
needs to be changed in the design - and therefore in the code.

It works, And it's worked for a lot of years by people who know how to
build complex projects.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]