When you work in It department, you must have been ever requested to develop software to make automation of certain process in company. Then you did standard soft. development phase such us user requirement, system design, system test, trial and then implementation. after implementation, how exactly you measure quality of software ? there is one indication : quantity of change request to software. it is important factor to determine how software can satisfy business process in company. When user requirement stage was not done well, then many change request will come after implementation. [to be continued..]
In the ideal world. In the real world, you write the software that best fits the desires of most of the users, while being done in the required amount of time. Which - if you have stupid executives - means a program that sort of does something like what's needed.
measuring the quality of software must be tested first by comparing with software that already exists.....