SQE NOTES

OPEN ENDED QUESTION AND ANSWERS

Q.All web services are API. Do you agree with this opinion? Justify your opinion with a
suitable example?

Yes, All web services are APIs, but not all APIs are web services because an API is a set of
functions and procedures that allow you to access and build upon the data and functionality of
an existing application , while a web service is a network-based resource that fulfills a specific
task.
Let us consider an example of a login system which requires an email address and a password
for signing in to the web application to use its features. This is an example of a “web service” but
the same login system has an option to sign in with the help of your google credentials , the
website is using “Google API” which has been integrated with the application to make it easier
and more convenient to use.

Q.Why do we need quality models when we have various software process models?
What is the significance of Software Quality Models?

A software process model is a digital or hand-written model that details the software
development process. Process models help provide a visual representation of the development
process for both the team and the customer to review whereas Software Quality models help
us to depict and express software quality. A quality model makes it easier to compare one
product with another. They defines the characteristics to be assessed and suggest some
measures to capture those characteristics so that the product which is going to be build meets
the expected standards.These standards claims that the factors of software product quality
(usability , reliability etc) are comprehensive i.e. any component of software quality can be
described in terms of some aspect of one or more of the Factors.
Q.George is an exceptional programmer. Testing his software modules reveals very few
errors, far fewer than the team’s average. He keeps his schedule promptly, and only
rarely is he late in completing his task. He always finds original ways to solve
programming difficulties, and uses an original, individual version of the coding style. He
dislikes preparing the required documentation, and rarely does it according to the team’s
templates.He was called to the chief’s office and warned by the company’s chief that he
would be fired unless he began to fully comply with team’s coding and documentation
instructions.
● Do you agree with the chief?
● Yes/No. Justify your opinion

Yes.
The use of non-standard coding and documentation methods by George cause:
– Extra difficulties to other programmers who have to develop software modules that need to
interface with George’s module that may result in errors.
– Extra difficulties to an inspection team and testing team that may result in lower than regular
rates of error detecting.
– Extra difficulty to replace programmers who might be recruited to continue the work of George
in the case of his leaving the company or being promoted to a higher position in another project.
Misunderstanding George’s coding and documentation may result in software errors.
– Extra difficulty in performing maintenance tasks of failure repairs, adaptation of the software to
new customers and system improvement tasks.

Q. SQA (Expanded Definition): A systematic, planned set of actions necessary to provide

adequate confidence that the software development process or the maintenance process
of a software system product conforms to established functional technical requirements
as well as with the managerial requirements of keeping the schedule and operating
within the budgetary confines.

It is claimed that the expanded definition of SQA corresponds with client satisfaction.
● Do you Agree?
● Yes/No; provide arguments.

1. I agree.
2. (a) The expanded SQA definition adds the elements of managerial schedule and budget
control. As projects that do not keep to schedule and / or exceed their budget tend to be under
severe managerial pressures to save project resources and perform procedures more quickly,
the prospects of fully achieving all the quality goals and an acceptable extent of software errors
are reduced substantially. Thus the inclusion of schedule and budget control in the SQA controls
reduces the prospect of failure – increases the customer’s satisfaction.
(b) Another element added to the SQA expanded definition refers to software maintenance
quality. Maintaining SQA efforts throughout the software life cycle leads to the continuing
satisfaction of the client extended over long years of operation.
Q.When or at what defect level do we need to Stop Testing?

Testing can be stopped when:

● Defined / Desired Defect count is reached.

● All Show Stopper defects or Blockers are fixed and No known Critical / Severity 1 defect
is in Open Status.
● All High Priority defects are identified and fixed.
● Defect Rate falls below the defined acceptable rate.
● Very few Medium Priority defects are open and have a workaround in place.
● Very few low priority open defects that do not impact software usage.
● All High Priority defects are re-tested and closed and corresponding Regression
scenarios are successfully executed

Q.Does a project of only 40 working days duration, to be developed by one professional

entity, justify the investment of a man-day in order to prepare a full scale quality and
development plan?

Disagree, since the project is small and professionals are working on it they can manage their
activities efficiently thus only plans made for specifying goals and for those activities that need
everyone to work together will be required. Also time duration is less so can not give too much
time on scheduling. It should be clear that the development and quality plan procedures
applicable to large projects cannot be automatically applied to small projects.

Q. Differentiate between walkthrough and inspection.

S.No INSPECTION WALKTHROUGH

1 It is formal. It is informal.

2 Initiated by the project team. Initiated by author.

3 A group of relevant persons from Usually team members of the same project
different departments participate in the take part in the walkthrough. Author
inspection. himself acts as a walkthrough leader.

4 Checklist is used to find faults. No checklist is used in the walkthrough.

5 Inspection processes include overview, Walkthrough process includes overview,

preparation, inspection, and rework and little or no preparation, little or no
follow up. preparation examination (actual
walkthrough meeting), and rework and
follow up.

6 Inspection takes a longer time as the list Shorter time is spent on walkthrough as
 of items in the checklist is tracked to there is no formal checklist used to
completion. evaluate programs.

Q.Southcottage Inc. is a manufacturer of washing machines and dishwashers. The

requirements document for the new control unit included the following specifications:
a. The firmware should be suitable for all six variations of model 2002 washing machines.
b. The water level control module of the washing machine should be suitable for use as a
water level control module in the new model 2002 dishwasher.
1. To which of the factors do the above requirements belong?
2. Explain your answer.

1. The specifications refer to the flexibility and reusability factors respectively.

2. Requirement (a) refers to flexibility in the use of a complete firmware product that by its very
design will enable it to be used as firmware in several variations of washing machines by using
a variety of parameter sets.
Requirement (b) refers to the reuse of part of a firmware product, to a module that is introduced
into entirely different firmware products and saves the efforts of developing a new module,
which will only serve dishwashers.

Q.In what circumstances we use V-model and in what situations we should avoid
V-model?

V model is applicable when:

● The requirement is well defined and not ambiguous
● Acceptance criteria are well defined.
● The project is short to medium in size.
● The technology and tools used are not dynamic.

V model is not suitable for:

● bigger and complex projects
● if the requirements are not consistent.
● No working software is produced in the intermediate stage.
● No provision for doing risk analysis so uncertainty and risks are there.

Q.When do we prefer walkthrough and when do we prefer inspection to review software

products?

Q.Is it necessary to prepare a quality plan document for internal projects? Yes/no.
Justify.