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.
Sound like you need a couple of tools (Visual UML, Project 2002, Source Safe, etc...). However, UML is definately a great tool to use for documenting and architecting your application. Unfortunately, this is not something that you'll learn over night.
I can give you a couple places to start:
UML Distilled: A Brief Guide to the Standard Object Modeling Language (2nd Edition) by Martin Fowler, Kendall Scott Publisher: Addison-Wesley Pub Co; ISBN: 020165783X; 2nd edition (August 25, 1999)
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, 2/e Copyright: 2002 Format: Cloth, 650 pp. ISBN: 0-13-092569-1
Both are excellent books and easy reading. I knock each book in a weekend. These books won't make you an expert but it'll give you an idea of whether you wish to continue with UML or not. If you do wish to continue there are tons of resources listed in each book.
