Q.1) Define the term quality and elaborate different views on quality.

=> Quality can be defined as the different things to different people it is highly
dependent upon the situation different views on the quality are as follows

1.Transcendental View –
• Quality does not have fixed definition but it can be recognised through
experience
2.User-View –
• according to the user perspective product should meet the its
requirement
• this view can be measured with reliability and usability
3.Manufacturing View –
• It focuses on product build quality
• Defects and rework are two factors to measure this view
4.Product view –
• It depends upon internal and external properties
• External is a feature and internal is the quality of code written
5.Value-based View –
• It is trade off between the cost and quality
• It focuses on quality of product and increase number of customers

Q.2) What are quality principles of total quality management(TQM)

=>TQM stands for the total quality management it focuses on the long term
satisfaction of customer rather than short term
1. process approach – In order to ensure the consistency proper steps must be
taken
2. customer satisfaction – All requirement should be fulfilled and customer
must be happy with end result
3. total employee commitment – new employee should be added or removed
based on the goal and resources available
4. strategic thinking – build strategy and assign different task to employee to
approach product
5. Integrated system – there are different department in an organisation where
everyone must understand goals, vision and mission
6. continuous improvement – it includes improvement in process approach and
meeting stakeholder expectation
7. effective communication - it involves strategies, method and timeliness
where employee, stakeholder communicate with each to meet goal
Q.3) Explain structure of quality management system
=>

• Manual –
1. the manual should fit organization. The structure and the content
of the manual can change depending on the size of the
organization and the complexity of its operations
2. Small organizations can document the entire QMS in one manual.
On the other side, large international organizations may have
several different quality manuals
• Policy –
1. A policy represents a declarative statement by an organization. A
Quality Policy should state the declaration of the organization to
quality and continual improvement
• Procedure –
1. Quality procedures can have different formats and structures.
They can be narrative, i.e., described through text; they can be
more structured by using tables; they can be more illustrative
• Work Instruction –
1. Work instructions can be part of a procedure, or they can be
referenced in a procedure. Generally, work instructions have a
similar structure to the procedures and cover the same elements
• Records and forms-
1. In order to demonstrate that our processes met their
requirements, we have to keep some evidence; this is where
forms and records are used. A record is what has been chosen by
the process owner
Q.4) How Quality and productivity replated with each other
=>
• Improvement in quality directly leads improvement to productivity
• Effective way to improve productivity is to reduce scrap and rework
• Quality improvement leads to cost reduction
• Proper communication between management and employee is essential
• Employee participate and contribute in improvement process
• Employee shares responsibility for innovation quality improvement

Q.5) write short note in continual improvement cycle

=> Continual improvement ongoing improvement cycle to improve products,
services or processes
Phases
• Process selection and definition – It involves selecting and defining
critical process having scope for continuous improvement
It includes 1. Internal external customers 2. Inputs 3. Process and output
• Process evaluation and standardization – this involves
1. Defining and describing selected process
2. Measure and performance of process on basis of described
performance measure
3. Analysing available process data
4. Performing cause and effect analysis
5. Identifying root cause
• Process improvement – PDCA cycle is used to improve selected process
Plan – The improvement objectives are defined and improvement plan is
formulated
Do – improvement plan is executed , solution are tested and strategies
are implemented
Check – the effect of process change are measured and result of these
improvement actions are reviewed based on performance
Act – process is bought under control, final process change is made and
results are assessed

---------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Q.6) What is quality? Explain its core components
=> Quality can be defined as the different things to different people it is highly
dependent upon the situation its core components of the quality are as follows
 • Functionality – It should meet all the functional requirement of user
• Reliability – product quality should be high so that risk factor can be
decreased and failure can be avoided
• Performance – It is about response time of the software and how quickly
it can make changes
• Flexibility – product should adapt the upcoming future changes and
should be able to upgrade software and hardware to increase
compatibility
• Usability – it must be easy to use and comfortable to the user
• Security – product should protect against security attacks and do not
exposes user data

Q.7) explain important aspects of quality management

=> design, build, deployment, control, measurement – measures effectiveness
and efficiency, review, improvement

Q.9) Explain any 5 requirements of product

=>
• User expectations – requirement of product should be designed
according to the customer demand
• Customer requirement – customer can have different requirement and
according to their expectations product should be build
• Usability – product should be easy to use and create pleasant experience
• Customer experience – customer should get meaningful and pleasant
experience using the product like animations, no bugs, easy to use
• Functions – all the customer demands should be completed by offering
them required functionality
• Performance – product should be rich in performance to meet their
needs where its response time should be low as possible

Q.10) what are problematic areas of software development

=>
• Lack of flexibility – repetitive changes in project requirement bring the
issue of waste and rework as there is no flexibility in project so all
assumption should be made according to requirements
• Lack of user feedback and input – user gets end result directly so its too
late or too expensive to make changes
• Quality issues – testing is necessary
 • Integration issues – different components are developed by different
group so it create integration issue so use incremental and iterative
development
• Excessive overhead - SDLC is mostly document driven so it creates more
burden to use to communicate face to face and collaboration and less
documentation
• Lack of ownership

Q.11) what is severity of a defect

=> severity is defined degree of impact a defect has on the development of the
product
It is categorized into four classes –
• Critical – It states complete shut-down of the process and nothing can be
done further
• Major – major defects are of high severity which can affect software
functionality this defect can be fixed but it’s not easy
• Minor – this affect minor functionality which are not very critical and it
can cause undesirable behaviour bot system will still function
• Low – these defect does not affects functionality these are generally
cosmetic defects which do not affects system

Q.12) explain problem solving techniques

=> 1. Identify the problem – identify the scope, nature and severity of the
problem
2. Determine the cause – try to find root cause of problem to permanently
fix the problem
3. Iterate potential solution – use brainstorming and choose the best
solution also called as trade off analysis
4. test action – plan and implement the solution

Q.13) explain flowchart with fishbone diagram

=> flowchart is a diagram that represents process they can be simple or
complex depending upon the project it ensures all options of problem solving
are checked and nothing is left
Fishbone – it is also called as cause and effect diagram as it represent the cause
of problem and what problem it can create it is mostly used in brainstorming
session as in below diagram problem is website went down and above lines are
Cause of this problem and unable to connect server is effect of problem

Q.14) what are characteristics of software

=>
• functionality
• reliability – provides desired functionality under some conditions
• usability
• efficiency – response time
• maintainability
• portability – function properly in different software and hardware
changes
• interoperability- able to communicate with other system,
• scalability – easy to upgrade components

Q.15) explain SDLC

=> SDLC- software development life cycle
Phases – requirements, design, deployment, testing, maintenance