Software development has spawned an independent industry in its own right. But the processes of asking for service, offering service, and pricing are all somewhat haphazard. Perhaps it's time to focus efforts on resolving the key paradoxes of software estimation.
code of federal regulations
activities—say, for coding, for code walk-through, for testing, and so on—to arrive at the resource requirements for each of these activities. And by summing up the individual requirements, we can arrive at the total resource requirements for the project. Software estimation becomes contentious, however, when we estimate for software pricing. We need to arrive at an estimate that is understood by the client's purchaser, who is to be assumed not to be a software developer, and who is expected to be