Jimi,

UML will help you with the diagraming piece of the problem.

With the planning piece of the problem you will need is a "software development process" (e.g. Rational Unified Process, Extreme Programming)

A modeling language and a "software development process" are two different things. Take a look at my whitepaper on UML on http://visionds.net/hcorrea


>Hello everybody,
>
>In the past few years, I never have any real planning before starting a system, I know it's a waste of time and the system will never be good enough.
>
>Now, not only cause I want to have my work done easier/better, i also need to cooperate with other programmers. I need to present the system design and communicate with them effectively. Someone told me UML is the way to go, but I'm not sure if it's suitable for our systems.
>
>For example, an accounting system written in VFP, all functions are put in the menu bar for users to choose (Most of our VFP programs are in similar structure).
>I need documents to:
>(1) present the system to customers,
>(2) let other programers know what to do without telling them everything by myself, and
>(3) let other programers to follow the job easily even when the old programers are left.
>Should I use UML? Does UML suits VFP products? We need a standard to follow when designing any new systems in the future.
>
>Any suggestions or ideas will be greatly appreciated, and suggested readings are welcomed too :)
>
>thanks a lot!
>Jimi