Software Engineering Group assignment Two

JINKA UNIVERSITY

BASKETO LASKA CENTER

 Department - Computer Science
 Corse Title - Software Engineering
 Corse Code - CoSc3061
 Group - Three(3)
 Academic Year - 2016 e.c
 Group Assignment - Two
Assignment Title - Software Quality Assurance

Group Member
Name ID No
1 .Habiteneh Endale ----------------------------------- 12776/13
2. Enbakom Bukashaw ------------------------------- 12750/13
3. Jonh Tiliku -------------------------------------12791/13
4. Israel Meto -------------------------------------- 12789/13
5. Libene Defaru-------------------------------------12800/13
6. Bekelech shibru --------------------------------------12748/13
7. Emush Terefe --------------------------------------12796/13
8. Filmon Lakew ------------------------------------- 12769/13
9. Gidaje Yisntare -------------------------------------12774/13
10. Eyasu Tamiru ------------------------------------12761/13
11. Esayas Tariku---------------------------------------12753/13
12. Eminet Shibru -------------------------------------12747/13
0
Software Engineering Group assignment Two

Instructor:- Senbetu.
Software Quality Assurance Testing Activities

Software Quality Assurance

Software Quality Assurance (SQA) Software quality assurance is a planned effort to ensure that
a software product fulfills these criteria and has additional attributes specific to the project, e.g.,
portability, efficiency, reusability, and flexibility.

It is the collection of activities and functions used to monitor and control a software project so
that specific objectives are achieved with the desired level of confidence.

It is not the sole responsibility of the software quality assurance group but is determined by
the consensus of the project manager, project leader, project personnel, and users.

A formal definition of software quality assurance is that is ‘the systematic activities providing
evidence of the fitness for use of the total software product.” Software quality assurance is
achieved through the use of established guidelines. for quality control to ensure the Integrity
and prolonged life of software. The relationships between quality assurance, quality control,
the auditing function, and software testing are often confused.

Quality assurance is the set of support activities needed to provide adequate confidence that
processes are established and continuously improved in order to products that meet
specifications and are fit for use. Quality control is the process by which product quality is
compared with applicable standards and the action taken when nonconformance is detected.
Auditing is the inspection/ assessment activity that verifies compliance with plans, policies, and
procedures.

Software Quality Assurance Testing Activities

SQA is ensured through a Quality Management System (QMS), QMS is made of several
components; it is a system integrated in the bigger system of software development, which
comprises project, process and product management systems.

The Software Engineering Institute (SEI) recommends a set of activities, which, when
implemented effectively, assures the designed quality. These activities include:

• Quality assurance planning

• Data gathering on key quality defining parameters

• Data analysis and reporting

1
Software Engineering Group assignment Two

 Quality control mechanisms the first and foremost requirement in SQA is that it is a
separate group responsible for quality in the organization. They set the goals, standards
and mechanisms (systems) for SQA. The role of the SQA group is to assist the software
development team in managing the quality requirements of the software. Every
software has certain quality goals specified by the customer. These quality goals are to
be achieved by the development team by introducing a set of activities or ensuring the
delivery of quality to the customer.

SQA activities operate on the normal activities of quality management. These activities play the
role of monitoring, tracking, evaluations, auditing and reviews to ensure that the quality policy
of the organization is implemented. These activities are independently carried out, and
feedback is given to the development team. The responsibility of delivering the required quality
to the customer rests with the development team. The development team has an obligation to
implement quality policy in terms of goals, objectives, procedures, checks and controls,
documentation and feedback to management. For example, the quality policy stipulates
preparation of a test plan for stages for development as well as at the end of the development
process. SQA has a variety of tools to implement the policy. They are

• Auditing

• Inspection
Verify compliance with those norms and practices specified in QA policy; deviations are set
right. Ensure that deviations are documented and reported and put into the QA database for
guidance. Design and architecture is reviewed to ensure that standards are met and customer
quality is assured. Implement change management.
Collect data on various observations in the process of auditing, inspection and reviews to build
QA database and to improve various standards.

Testing activities

Testing is the process of executing a program to find 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.

Testing activities refer to the processes and tasks involved in evaluating a software application or
system to identify defects, bugs, or issues. These activities can include test planning, test case
design, test execution, defect reporting, and test result analysis.

Testing activities are crucial in ensuring the quality and reliability of software products before
they are released to end-users.
2
Software Engineering Group assignment Two

Principles of Testing

 All the tests should meet the customer’s requirements.

 To make our software testing should be performed by a third party.

 Exhaustive testing is not possible. As we need the optimal amount of testing based on the
risk assessment of the application.

 All the tests to be conducted should be planned before implementing it

 It follows the Pareto rule(80/20 rule) which states that 80% of errors come from 20% of
program components.

 Start testing with small parts and extend it to large parts.

Testing There are 3 Main Software Activities:

1 .Test planning

2 .Test implementation and dimension

3. Test output analysis and follow-up activities

Test Planning

This stage comprises such significant sub-phases: setting software testing purposes data
collection choosing general testing strategies and techniques making ready test cases making
ready the general test suite creating testing models making ready the software testing process

Test Implementation and Dimension

This stage comprises of 3 sub-phases:

 adjusting test time and resources

 invoking and running tests

 checking testing output and detecting system failures

Test Output Analysis

This stage comprises possible problem diagnosis and software bug correcting as a follow-up to
individual test runs, and analyses of general test outputs for management resolutions and quality
improvement activities.

3
Software Engineering Group assignment Two

These software testing activities may commonly be carried out and managed with the
involvement of a lot of people who have various roles and obligations:

Developers who are answerable for correcting software bugs (they can play the double role of
software testers as well)

Dedicated professional software testers and testing managers Independent professional software
testing companies Clients and users, who may operate as testers informally for usability testing
or beta testing Entirely automated support is not possible.

Some automated support, combined with a good comprehension of the specific test activities
and related techniques by software testing teams may assist us in performing planned software
testing activities to efficaciously identify software defects and to provide quality assurance.