Quiz #04

MAZHAR SUBHANI Siddiqui01-134171-101

Submitted To:
Ma’am Zubaria Inayat.
Read the paper titled “Software Quality Assessment in Practice: A Hypothesis-driven
Framework” attached with this assignment and answer the following questions:

1) Provide a brief summary of the paper (less than or equal to 250 words)
2) Provide critical review (i.e. strengths and weaknesses of the paper)

Summary:

Software quality models describe decompositions of quality characteristics. However, in practice, there
is a gap between quality models, quality measurements, and quality assessment activities.

This paper is about the methods and they were applied in 2 cases which were real world
systems and the results are further discussed here. They found that results from automated
tools can be misleading. Many of the tools that check the efficiency of quality control
mechanism tools work but they detect many false positives.

As a first step of bridging the gap, this paper presents a novel and structured framework to perform
quality assessments. Together with our industrial partner, we applied this framework in two case

For case A the problems faced were of UML which has to be made from the source code with
the help of which mapping of the functionality became clearer. The software faces a
modifiability issue that decreases its maintainability.

For case B the issues found were far less as compared to A. The artifacts were up to date and
easy to walk through. The assessment answered whether the system is technically sustainable
and suitable for future requirements.
 Critical Review:
Input

As shown in Figure 1, we grouped the input information into three categories. One category captures
system and project artefacts. Typical examples of system artefacts are source code, data model,
documentation, and other material needed to reproduce the technical

Process

The quality assessment process consists of three phases: overview, building hypotheses, and analysis.

Process

The quality assessment process consists of three phases:

1. Overview
2. building hypotheses
3. and analysis.

Building Hypotheses: Figure 1 visualizes that the phase of building up hypotheses consists of two
aspects: Initial hypothesis and working hypothesis.

Analysis: The actual analysis is guided by the hypotheses and is divided into three activities.

Assessment: The presented framework allows quality consultants to use any quality assessment method

Output After several rounds of iteration, the quality consultants come to a conclusion. This conclusion is
combined with the context information about the system to identify possible root causes for the
observed quality defects.

 Strengths & weaknesses:

 Hypothesis driven test should not be used in mechanical fashion.
 Results of significant test are based on probabilities and the results cannot be expressed
with full certainty.
 If the software suffers from code cloning that decreases the software maintainability.
 The identifiers naming convention does either not exist or it is not maintained which
affects the program comprehension.
 It was impossible to store more than one telephone number per one person.