MOSHI CO-OPERATIVE UNIVERSITY (MoCU)

FACULTY : FBIS

PROGRAME : BSc.BICT

COURSE NAME : SOFTWARE QUALITY ASSURANCE

COURSE INSTRUCTOR : Mr. S. MADILA

TASK : GROUP ASSGNMENT

SUBMISSION DATE : 18-6-2020

COURSE ANTE : CIT 307

QUESTION :

1. Explain the software quality management activities.

 GROUP NAMES:

NO. NAMES: REG NO:

1. EMMANUEL N. MASINDIKE MoCU/BSC.BICT/151/17
2. LUCAS .J. DEREDE MoCU/BSC.BICT/142/17
3. CHRISTOPHER .G. MARTIN MoCU/BSC.BICT/171/17
4. PROSPA M. AGUSTI MoCU/BSC.BICT/150/17
5. RAYMOND MSUNGU MoCU/BSC.BICT/165/17
6. CHRISTOPHER TINGO MoCU/BSC.BICT/156/17
7. FATMAH S. MIRAMBO MoCU/BSC.BICT/137/17
8. JOHN LUGENZI MoCU/BSC.BICT/180/17
9. RODRICK S. SWAI MoCU/BSC.BICT/168/17
10. KELVIN. S. GODFREY MoCU/BSC.BICT/154/17

Software Quality Assurance Activities

Software quality assurance is a process which assures that all software engineering processes,

methods, activities and work items are monitored and comply against the defined standards.
Incorporates all software development processes starting from defining requirements to coding
until release, you analyze and ensure software quality assurance by doing a series of activities. It
is also a step-by-step process, and the tester reports the results for the final evaluation process.

A management plan

Designed and developed for the software quality assurance process. It includes appropriate
technical methods to manage software quality assurance activities. Planning is always essential
since it will be the base or the leads of the process .selection of appropriate procedures and
standards from this framework and adaptation of these to specific software project

Software engineering techniques

Are selected to achieve software quality techniques to be used for software quality assurance are
determined by analyzing the requirements gathered. Using some methods, it can be more like,
for example, is the Facilitated Application Specification Technique. Another thing is that the
project estimate undergoes preparation by using techniques such as Work Break Down and
Source Line of Code Estimation.

Conducting formal technical reviews

One conducts formal technical reviews to test the quality and design of the quality management
plan. One performs this in the presence of the technical team. Moreover, it will help find and
identify the defects in the early stages. Formal technical reviews also help to avoid the need for
repeating the same work since the reviews in each phase are performed by discussing the
technical experts. An formal technical reviews is done to evaluate the quality and design of the
prototype. In this process, a meeting is conducted with the technical staff to discuss regarding the
actual quality requirements of the software and the design quality of the prototype. This activity
helps in detecting errors in the early phase of Software Development Life Cycle and reduces
rework effort in the later phases.

Application of multi-tiered testing strategy

Is the basic activity aimed at detecting and solving technical issues in the software source code
and assessing the overall product usability, performance, security, and compatibility It has a very
narrow focus and is performed by the test engineers in parallel with the development process or
at the dedicated testing stage depending on the methodological approach to the software
development cycle. It is based on the policies of the company, and the stages of each test phase
execution are scheduled for the particular person. Before delivering the product, you select the
conducting of Alpha Testing and Beta Testing. By multi-testing strategy, we mean that one should
not rely on any single testing approach; instead, multiple types of testing should be performed so that
the software product can be tested well from all angles to ensure better quality.

Enforcing process adherence

This activity insists the need for process adherence during the software development process.
The development process should also stick to the defined procedures.

This activity is a blend of two sub-activities which are explained below in detail:
(i) Product Evaluation:
This activity confirms that the software product is meeting the requirements that were discovered
in the project management plan. It ensures that the set standards for the project are followed
correctly.

(ii) Process Monitoring:

This activity verifies if the correct steps were taken during software development. This is done
by matching the actually taken steps against the documented steps.

The change control process

A The change control process in project management ensures that each change proposed during a
project is adequately defined, reviewed and approved before implementation. The change control
process helps avoid unnecessary changes that might disrupt services and also ensures the
efficient use of resources. In this activity, we use a mix of manual procedures and automated
tools to have a mechanism for change control.
By validating the change requests, evaluating the nature of change and controlling the change
effect, it is ensured that the software quality is maintained during the development and
maintenance phases

Performing audits

It inspects the software development process by comparing it to the established procedure. You
may also only assess the quality of the product by the results of the review by the Software
Quality Assurance Auditor.

Software quality assurance- the main person who checks and reviews the activities undergo
implementation to the highest standards possible. The (Software Quality Assurance) audit
inspects the entire actual Software Development Life Cycle process followed by comparing it
against the established process.

It also checks whatever reported by the team in the status reports were actually performed or not.
This activity also exposes any non-compliance issues.

Keeping records and reporting

One should generate all activities for future references. This can evaluate the project quality and
also assess the way of handling the project management process. Therefore, keeping records and
reporting ensures the collection and circulation of information.

REFERENCES
 Balla, K., Bemelmans, T., Kusters, R., & Trienekens, J. (2001). Quality through managed
improvement and measurement (QMIM): Towards a phased development and
implementation of a quality management system for a software company. Software
Quality Journal, 9(3), 177-193.

e Abreu, F. B., & Melo, W. (1996, March). Evaluating the impact of object-oriented design on
software quality. In Proceedings of the 3rd international software metrics symposium (pp.
90-99). IEEE.

Gill, N. S. (2005). Factors affecting effective software quality management revisited. ACM
SIGSOFT Software Engineering Notes, 30(2), 1-4.

John W. Horch. (2003). Practical guide to software quality management. Artech House.

Lee, M. C., & Chang, T. (2006). Applying TQM, CMM and ISO 9001 in knowledge
management for software development process improvement. International Journal of
Services and Standards, 2(1), 101-115.

Stelzer, D., Mellis, W., & Herzwurm, G. (1997). A critical look at ISO 9000 for software quality
management. Software Quality Journal, 6(2), 65-79.

Subramanian, G. H., Jiang, J. J., & Klein, G. (2007). Software quality and IS project
performance improvements from software development process maturity and IS
implementation strategies. Journal of Systems and Software, 80(4), 616-627.

Selection of appropriate procedures and standards from this framework and adaptation of these
to specific software project