Systematic Study of Software Quality Models

Software Quality, Change Management and Testing
A systematic study of software quality models by Tomar and Thakare
Name
Institution
Professor
Course
Date

Introduction
A systematic review study of the software quality models article provides the basis of
evaluating the quality of the software. (Tomar & Thakare 2011, pp.61). The primary goal of the
paper is to address software quality metrics and at which stage of software development should
each parameter be measurable. The content of the article would be presented in several sections
such as an overview of the selected journal. Since subjected article is presented as a report,
methodologies used in the collection of data would be addressed. On the same note, issues faced
by system developers and other system users would be highlighted. Unless these challenges are
addressed adequately, the quality of the software will remain to be a perennial issue. Next, it
would analyze change management in software development processes. Change management
would focus on procedures that should be considered in order to have a dynamic project schedule
as well as budget. Change management remains a significant aspect of software development
because it involves project management concepts. It would also address some of the necessary
skills required to have successful project implementation. Most of the projects have been failing
due to a lack of essential skills to manage project changes. Project changes are unavoidable and
if not adequately controlled, results to project creep or total project failure. Finally, the article
would address software testing parameters and necessary testing features to be considered as part
of quality assurance. Once the system has been developed, it should be tested before and after
deployment. Testing is used to ascertain whether all software metrics have been met and their
success rate in project implementation.

The content of the article
The article presents a range of metrics through which both software developers and
regular system users can use to evaluate the quality of any system. Software quality has remained
to be a great challenge in the software industry due to unmet specifications. The authors of the
article pinpoint most of the software characteristics to be considered (Tomar & Thakare 2011,
pp.64-65). From the article, it can be deduced that if the quality of the software depends on the
satisfaction of requirements presented, some features should be captured in the development
processes. To develop a quality product, the software should conform to given specifications, the
degree of the software having all desired characteristics and users perspective on software
requirements being met. To achieve all the software quality metrics, all future aspects of the
users should be translated into measurable characteristics. Important to note is that software
quality is quite dynamic and varies from system users. If a product does not meet required
standards, it may inflict user on some injuries or resulting in financial loss. Software metrics are
features that must be captured by system developers as indicators of quality assurance. The
article focuses on software quality metrics that system developers and designers should address.
Despite efforts made to meet all requirements and specifications, system developers have been
faced with the issue of measuring if all metrics have been addressed (Suman & Rohtak 2014, pp.
5636). Some software metrics are unmeasurable, and this makes it difficult to control an
unmeasurable aspect. The aspect of unmeasurable parameters is brought about by attributes
which are un-tangible.
The authors' review of other literature advocated that software quality is an aspect that
should be monitored from the initial stages of the project implementation. To make the
implementation of quality software successful, the authors focused on the triangle of quality