Sadia Tahsin Mukta - Lesson - 1 - Exercise - 1

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

Sadia Tahsin Mukta

2018511460035

A tiny Bug could be a big Problem such an example when software flaws have caused billions of
dollars in waste or even lead to casualties, from Starbucks coffee shops being forced to give
away free drinks because of a register malfunction, to the F-35 military aircraft being unable to
detect the targets correctly because of a radar failure. So, this is why Quality Assurance is
important issue. it is the set of activities that determine the procedures and standards to develop a
product. Software Quality Assurance, QA, is a planned and systematic way of creating an
environment to assure that the software product being developed meets the quality
requirements.QA refers to the implementation of well-defined standard practices and methods. It
is a pro-active quality process. This process is controlled and determined at managerial level.
Quality assurance focuses on the process checklists, process standards, project audits,
methodology and procedures for development.

It is a preventive process that aims at establishing the correct methodology and standards to
provide a quality conducive environment to the product being developed.
Software Quality Assurance is a process which works parallel to development of a software. It
focuses on improving the process of development of software so that problems can be
prevented before they become a major issue. Software Quality Assurance is a kind of an
Umbrella activity that is applied throughout the software process.

Software Quality Assurance have:


1. A quality management approach
2. Formal technical reviews
3. Multi testing strategy
4. Effective software engineering technology
5. Measurement and reporting mechanism
Major Software Quality Assurance Activities:
1. SQA Management Plan:
Make a plan how you will carry out the sqa through out the project. Think which set
of software engineering activities are the best for project.check level of sqa team
skills.
2. Set The Check Points:
SQA team should set checkpoints. Evaluate the performance of the project on the
basis of collected data on different check points.
3. Multi testing Strategy:
Do not depend on single testing approach. When you have lot of testing approaches
available use them.
4. Measure Change Impact:
The changes for making the correction of an error sometimes re introduces more
errors keep the measure of impact of change on project. Reset the new change to
change check the compatibility of this fix with whole project.
5. Manage Good Relations:
In the working environment managing the good relation with other teams involved
in the project development is mandatory. Bad relation of sqa team with
programmers team will impact directly and badly on project. Don’t play politics.

Testing (QA software)


 Test Management
 Bug and Issue Tracking
 Browser, Device, and OS Testing
 Usability Testing
 Load Testing
 Automated Testing & Continuous Integration

Types of Software Testing

Testing is the process of executing a program with the aim of finding errors. To make
our software perform well it should be error-free. If testing is done successfully it will
remove all the errors from the software. 
 

Principles of Testing:

(i) All the test should meet the customer requirements 


(ii) To make our software testing should be performed by a third party 
(iii) Exhaustive testing is not possible. As we need the optimal amount of testing based
on the risk assessment of the application. 
(iv) All the test to be conducted should be planned before implementing it  
(v) It follows the Pareto rule(80/20 rule) which states that 80% of errors come from
20% of program components. 
(vi) Start testing with small parts and extend it to large parts.

You might also like