Content deleted Content added
Line 9:
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, we can call these factors as predicates 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.
[[Image:Qualitymodel.gif]]
'''Goal Oriented Measurement''': Let's take the goal "Testability" for instance. The software metric "Cyclomatic Complexity" has considerable influence on the testability of a function, module and eventually the software as a whole. In simple terms CC(Cyclomatic Complexity) increase as the number of conditional constructs in a function increases, which actually mean that more testing effort is needed. So, we can consider Cyclomatic Complexity as a predicate for the goal "Testability", and as CC increases Testability becomes tougher (decreases).
| |||