Content deleted Content added
→Goal oriented measurement: Repairing links to disambiguation pages - You can help! using AWB |
|||
Line 4:
The first step in this direction is to decide the goals and their definitions, for example the following are some of the common goals of any [[software]] development / maintenance project.
This solves the first level of ambiguity, but the job of defining software quality has just begun. The very next step is to determine what predicates a quality goal. There can be several factors which can influence a particular goal positively or negatively, these factors can be [[predicate]]s of a goal and these predicates can be as simple as a naming convention to be followed or as complex as a desired "useful" comments percentage per class. In general these predicates are nothing but the "[best practices]]" to be followed and standard "[[software metrics]]" which are collected to determine different quality aspects of the software solution.
| |||