Quality view

David Garvins explained this 5 different perspectives

1)Transcendental view: the quality can be recognized but not be

defined
2)user view: it checks whether the product meets the user’s needs. It is
measured by reliability and usability.
3)manufacturing view: it focuses on how well the product was
constructed in avoid to rework
4)Product view: it assures that measuring and controlling the internal
product properties will result to improve external product
properties/behaviour.
5) Value based view : quality based on how much customer is willing to
pay for it. Software quality is customer satisfaction.

Financial Aspect of quality?

Cost of Quality: It is the sum of the costs of preventing and detecting

defects and the costs of defect events.
1)Prevention cost: the cost arises from the effort to prevent defects.
Quality palnning, formal technical reviews. Test equipment, training
etc.
2)Appraisal cost: the cost arises from the effort to detect defects. IN
process and inter-process inspection, equipment calibration and
maintenance, testing etc.
3)Failure cost: a) Internal Failure cost- the cost arises from defects
identified internally and efforts to correct them.
b) external Failure cost- the cost arises from defects identified by the
client or end users and effort to correct them.
Core components of quality?

F2RPUS
1)Functionality: the quality or state of being functional
2)Reliability: the quality of being able to be trusted or believed
because of working or behaving well
3)Performance:  performance is measured by velocity,
generally measured by how fast a team can get new features
released to users. But what makes great teams exceptional
isn’t just their ability to create new code – it’s the way in
which they work together as a unit.
4) Flexibility: Flexibility is the ability of software
to add/modify/remove functionality without damaging the
current system.
5) Usability:

6) Security: it protects against malicious attacks.

Customer, Supplier and Processes?

Customer: The customer can be Client or buyer. The
customer is an end user of the product. The end
user is very important. This testing evolves around
the expectation of the user from the product or
service.
Supplier: A supplier is a person, company or
organization that sells or supplies goods or
equipment to other organization.
Processes: In this involved steps in order to achieve
a particular end.

TQM?
PT, IS, CS, EC, TEC, DBF, ST, CI

continuous improvement?
continuous describes something that occurs over space or time without
interruption.
Continuous improvement is dynamic in nature. the changes are done at
every stages and every time to improve further. Environment
continuously changed.
Quality In different areas?
Benchmarking?
Benchmarking is a process of comparing your own organization, its operation or
processes against the best in the industry.
1)Improving process
2)Reduce cost and increase profit
3)Customer loyalty and satisfaction
Benchmarking is a process for obtaining a measure of a benchmark.
There are two types of benchmarking:
a)internal b)external
Advantages: Competitive analysis, monitor performance, continuous
improvement, encourages ownership, understand your companies advantages .
Explain the Problem-solving technique in TQM.

Problem solving software tools?

1)Flowchart: a flowchart is a diagram that represent

a process that can simple or quite complex.
2)Fishbone chart:
It is also called a cause-and-effect diagram or
Ishiwaka diagram.
Requirement of a product? OR What are the
Different types of requirements?

1)user requirement: Requirement should capture

expectations of product.
2)customer requirement: Requirement contributes
by a customer.
3)Usability: Ease of use.
4)Customer Experience: Requirement intended to
improve the end-to-end Customer Experience.
5)Function: Specification of goals that can be
accomplished with the product.
6)performance: performance targets for the
product.

Characteristics of software?

FRUEPMSIS

SDLC OR Explain software development processes?

A software life cycle model (also termed process model) is a
pictorial and diagrammatic representation of the software life
cycle.

MTRD2
Types of products?
Categories of software

System software: it is base for application software

which responsible for managing hardware. eg.MS
Windows, UNIX, Linux.
Application software: it is also called as productivity
program because they enable the user to complete
task, such as creating, designing, sending emails,
graphics.
Severity of defects OR How product are classified

depending upon their criticality?

Which are the problematic areas of SDLC?

Difference between quality assurance and quality
control/ quality planning OR Explain software
quality management?

Software quality management is a process that ensures the

required level of software quality is achieved when it reaches the
users, so that they are satisfied by the performance.
1)quality assurance: they make sure that the frameworks they are
using is high quality software.
2) quality planning: they make sure that the frameworks they are
using is high quality software.
And adapt for a specific software project.
3) quality control: making sure they follows the quality procedures
and standards.
Quality Assurance(QA): it ensures that the approaches, techniques,
methods and processes are designed for the projects are
implemented correctly.
Why software has defect?

SQA? OR Which processes are related to software

quality?
SQA goals?

1)Requirement quality:
Completeness, model clarity, volatility
2) Design quality:
Patterns, component completeness
3) code quality:
Complexity, reusability, documentation, maintainability
4)quality control effectiveness:
Resource allocation, testing effectiveness

QMS(Quality Management System)?

QMS is set of coordinated activities to direct and control an
organization in order to continually improve the effectiveness and
efficiency of its performance.
 MPPWR
Pillars of QMS?

1) Management responsibility :
Planning, management review, customer focus.
2) Resources management:
Human resources, infrastructure, work environment.
3) product realization:
Purchasing, customer-related process, design or development.
4) measurement, analysis and improvement:
General, planning, Improvement analysis of data.

Why testing is necessary?

List and explain fundamental test processes?

Explain unit testing?
Unit testing focuses verification effort on the smallest unit of
software design the software component-module.

Integration testing:
This is a second integration testing
Integration Testing is defined as a type of testing where software
modules are integrated logically and tested as a group. A typical
software project consists of multiple software modules, coded by
different programmers.
In integration testing there are two types of testing:
1) Top-down approach
2) Bottom-up approach
Validation testing:

Validation testing is testing where the tester performed

functional and non-functional testing. Here functional
testing includes Unit Testing (UT), Integration Testing (IT) and
System Testing (ST), and non-functional testing includes User
acceptance testing (UAT).

Validation testing is also known as dynamic testing, where we

are ensuring that "we have developed the product
right." And it also checks that the software meets the
business needs of the client.

Acceptance testing:

Acceptance testing is usually performed by business

customers, end-users, or testers from the company.

Boundary value testing?

Boundary value testing is a clack boxing testing design technique
based on test cases. This technique is applied to see if there are any
bugs at the boundary of the input domain.
Example of boundary value example:

Advantages:
1)this technique doesn’t fit well when it comes to Boolean variables.
2)the dependencies with BVA are not tested between two inputs.
3)it only works well with an independent variable that depicts quantity. 2

Robust Boundary?
Worst boundary value testing?
Random testing?
The user tests the application by providing random input is called
as monkey testing.
Advantages:

Equivalence classes?
1) Equivalence class testing is a black box technique.
2)it is applied to any of testing, like unit, or integration.
3) a test case design technique used to divide input data into
different equivalence classes.

Edge testing?
Decision table?
Also known as a cause and effect table, a decision table is a
representation of the different combinations of inputs in line with
their associated action or outputs.
Examples:

Cause and effect in graph?

(path testing) Program Graph?
1) Its program graph is a directed graph in which nodes are
statements and statement fragments, and edges represent the flow
of control.
2) Two nodes are connected if the execution can proceed from one
to the other.
DD path?
Test coverage matrices?

(Data flow testing) use of testing?

Types of data flow testing :

Slice bread testing?

1)S(V,n) is a slice on one variable, that is, the set V consist of a

single variable, v.
2)n(in S(V,n)) is a defining nod for v, then n is included in the slice.
3) n(in S(V,n)) is a usage nod for v, then n is not included in the
slice.
4) O-use, L-use and I-use nodes are excluded from slices.

Program Slicing?
It is a program analysis technique. It is mainly used during
debugging and engineering.

limitation Data flow testing:

Requirement traceability matrix?

Assume we have total requirement and total test case 10

Whenever a new test case is written will updated in this matrix
a) forward traceability- mapping requirement to test case is called
forward traceability. It is used to ensure whether the project
progress in the desired direction.
b) backward traceability- mapping test case to requirement is
called backward traceability. It is used to ensure whether the
current product remains on the right track.

Essential of software testing?

Principles of software testing?

Workbench?

An important feature of the testing process?

Misconception about testing?

Salient feature of testing?

Test policy, test strategy and test Approach?

Software testing also has its proper procedure with common
principles which are called “test policy”. It is a system, which
describes the approach that should be applied towards the testing.
These standards include test objectives, benefits, indicators of
quality and performance, test environment and priority targets
The test strategy is an organizational-level document that describes
the general test approach i.e. what needs to be achieved and how
to achieve it.
A test approach is the test strategy implementation of a
project which defines how testing would be carried out, defines the
strategy which needs to be implemented and executed, to carry
out a particular task. The test approach defines the testing
methodology, tools, techniques, and strategies that will be used to
test the software application.
Test level?

Unit testing focuses verification effort on the smallest unit of

software design the software component-module.

Integration testing:
This is a second integration testing
Integration Testing is defined as a type of testing where software
modules are integrated logically and tested as a group. A typical
software project consists of multiple software modules, coded by
different programmers.
In integration testing there are two types of testing:
1) Top-down approach
2) Bottom-up approach

System testing:
System testing is a type of software testing that evaluates the
overall functionality and performance of a complete and fully
integrated software solution.

Acceptance testing :

Acceptance testing is usually performed by business

customers, end-users, or testers from the company.
Mutation testing?
Explain the process of developing test methodology?
Testing goes hand-in-hand with preparation, designing, and
executing the code; treating it as an isolated procedure would be
wrong. 

 It enhances software app performance, security, and quality

assurance.
 It boosts software efficiency and improves Test Automation
ROI. 
 On the flip side, not testing in the early hours results in poor
software quality and exacerbates issues that aren’t only
expensive and time-taking. 

Components of test plan:

Which skills are required in good tester?

Cost aspect of testing?
COQ-
It includes –prevention cost, appraisal cost, internal failure cost and
external failure cost

Defect severity and priority?

Priority-
There are three classes:
a) High
b) Medium
c) Low
defect severity four classes:
a) critical
b) major
c) minor
d) low
prototyping model?

Explain Verification in detail with its Advantages?

Verification and Validation is the process of investigating that a
software system satisfies specifications and standards and it fulfills
the required purpose. Barry Boehm described verification and
validation as the following:
Verification:  Are we building the product right?
Verification is the process of checking that a software achieves its
goal without any bugs. It is the process to ensure whether the
product that is developed is right or not. It verifies whether the
developed product fulfills the requirements that we have.
Verification is Static Testing
Activities involved in verification:
Write short on Verification Work Benchmark?
Explain Types of Review on the Basis of Stage/Phase?

review:
 Explain Entities involved in verification?

Explain Coverage in Verification (Test Designing) in detail?

Difference between verification and validation?
Validation workbench?
Coverage in validation?

1. requirement coverage:
V model?

Sandwich testing?
Big Bang Testing?
Big Bang Testing is an Integration testing approach in which all
the components or modules are integrated together at once and
then tested as a unit. This combined set of components is
considered as an entity while testing. If all of the components in
the unit are not completed, the integration process will not
execute.
Advantages:

 Convenient for small systems.

Disadvantages:

 Fault Localization is difficult.

 Given the sheer number of interfaces that need to be tested
in this approach, some interfaces link to be tested could be
missed easily.