CodeSWAT.COM - Quality Model

Deprecated: Assigning the return value of new by reference is deprecated in /home/content/s/w/a/swatadmin/html/cswat/templates/ja_bellatrix/ja_cssmenu/ja-cssmenu.php on line 73

You are here:Home

Swat4j™

Quality Model

Quality Model: Software quality can be defined as 'conformance to requirements' and/or 'fitness of use'. Quality achievements start with a loud and clear definition of what "quality of source code" means to your organization or project. In simple terms all the stakeholders must be well informed of what is expected, what are the goals to be achieved, what is evaluation criteria and how they can contribute to achieve the goal.

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.

Testability: Ease of testing.
Maintainability: The ease of change.
Team Goal: Improve performance…
Developer Goal: Conformance of coding standard..

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 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.

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).

Predicate Contribution: There can be many factors which can influence the quality goal "Testability". Swat4J provides a normalized framework to include as many predicate as we see fit. Predicate contribution to the goal can vary; Swat4J allows tagging weight to each predicate to prioritize their contribution. Simply, by setting weights we can control which predicates contribute more to the goal of concern. Now, that might seem a lot of "do it yourself", to overcome this Swat4J comes with prepackaged configuration which are widely used in the industry, it can be customized to fit specific needs.

Swat4j provides 150+ predicates to qualify six quality goals across five levels of Java.
Goals: Design Quality, Testability, Maintainability, Understandability, Performance, Reusability.
Levels: Method, Class, File, Package, Project.

SWAT4J - Download Quality Model Presentation

SWAT4J - Quality MODEL IN ACTION - WATCH A DEMO [5 MIN]

Reference & further reading on measuring software quality
[ISO 9126] http://en.wikipedia.org/wiki/ISO_9126
[Measuring Software Product Quality: the ISO 25000 Series and CMMI] http://www.sei.cmu.edu/sema/presentations/zubrow/esepg/
Metrics and Models in Software Quality Engineering, 2nd Edition
[Software Quality Metrics Overview] http://www.awprofessional.com/articles/article.asp?p=30306&rl=1