Estimating Software from Requirements
Author: Arlene F. Minkiewicz
Category: White Papers
With software, the process of going from requirements to architecture is lengthy and often quite involved. Once you have completed the process, you may have invested considerable time and resources into the project. For this reason, it is often not practical to wait until an architectural view is available to start estimating the cost of your software development project. Clearly an estimate based only on an understanding of what the software is going to do, without a clear picture of exactly how the software will accomplish it, is not going to meet all of your estimation needs. However, if properly done, it should offer enough information to make it possible to early identify those software projects that have the best chance of delivering what is needed when it is needed. It should also offer a sound basis for many of the decisions that need to be made by senior management early in the software lifecycle.