The Practical Implication of Software Quality Assurance of Change Control Management: Why Overall IT Project Activities Matters?
Changes can be made frequently throughout a project. Software change control (SCC) as a subset of software quality assurance (SQA) is responsible for examining, approving changes, assuring quality of changes made and quality of the newer version of system with changes implemented. While a system is...
Saved in:
Published in | 2019 IEEE 7th Conference on Systems, Process and Control (ICSPC) pp. 131 - 136 |
---|---|
Main Authors | , , |
Format | Conference Proceeding |
Language | English |
Published |
IEEE
01.12.2019
|
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | Changes can be made frequently throughout a project. Software change control (SCC) as a subset of software quality assurance (SQA) is responsible for examining, approving changes, assuring quality of changes made and quality of the newer version of system with changes implemented. While a system is often broken down into a number of releases, these SCC tasks can be fulfilled by integrating approved changes to planned releases. As such, SCC tasks can be achieved simultaneously with project releases. However, a number of relevant discussions are focusing on the process of handling change request as a cycle itself and neglected the integration of changes to project. The overall view of IT project activities and sequence is not readily presented has too lead to the blurred vision of how changes can be integrated. This paper then addresses two main areas. One on establishing the association between project life cycle (PLC) and system development lifecycle (SDLC) to present an overall picture of IT project activities since changes can impact any area of a project and eventually integrate in it; and the other is on the integration between IT project and change requests that can achieve SCC concurrently considering the project throughput as a whole. |
---|---|
DOI: | 10.1109/ICSPC47137.2019.9067982 |