|
One of the most critical steps in custom programming is the estimating phase. You must have a good estimate if you want a good program. By “good”, we mean accurate.
But how will I know if the estimate is accurate? Very good question. Let’s start with a few things which, if true, are good indicators that you do not have an accurate estimate:
- the estimate was made without written specifications which include all file layouts, all screen layouts, all data validation and edit checking rules, all report layouts, formatting rules, data selection and sorting rules, all special processes such as automatic e-mail and faxing functions, etc. In other words, everything the program is supposed to do and all aspects of its appearance. This is what we call the program design.
If you are having a program converted and like the way the original program works, we can use the existing program as the basis for the design
- the program design was too general. Every screen, every report, all the data and all special processes need to be written down.
- you and your staff have not devoted considerable time developing specifications. It is hard work and very time consuming but the payoff can be enormous.
|
