Managing the software process
Communications of the ACM - Special issue on analysis and modeling in software development
ICSE '97 Proceedings of the 19th international conference on Software engineering
Improving software organizations: from principles to practice
Improving software organizations: from principles to practice
CMMI distilled: a practical introduction to integrated process improvement
CMMI distilled: a practical introduction to integrated process improvement
Industrial-Strength Management Strategies
IEEE Software
Factors affecting effective software quality management revisited
ACM SIGSOFT Software Engineering Notes
Quality gates in use-case driven development
Proceedings of the 2006 international workshop on Software quality
Measurement repository for Scrum-based software development process
CEA'08 Proceedings of the 2nd WSEAS International Conference on Computer Engineering and Applications
Experiences of implementing a value-based approach to software process and product assessment
CEA'08 Proceedings of the 2nd WSEAS International Conference on Computer Engineering and Applications
Experiences of implementing a value-based approach
WSEAS Transactions on Information Science and Applications
Integrated specification and quality assurance for large business information systems
Proceedings of the 2nd India software engineering conference
WOSQ'09 Proceedings of the Seventh ICSE conference on Software quality
Proceedings of the 15th WSEAS international conference on Systems
Hi-index | 0.00 |
The purposes to use quality gates in software development are many. Quite often companies see that the usage of quality gates improves their overall efficiency, effectiveness and output quality of software delivery chain. They also see that the usage of quality gates helps them to make things right at once by not skipping quality assurance actions. This paper defines quality gate model for a software company. As well it shows that even quality gates might be in place they are not always followed because of a business reason. Companies can forget their well structured quality gate systems when business reason justifies it. The results of neglecting quality gates might lead to a situation where software asset output is not trusted anymore and quality is not known. In a longer run quality gate system seems to be as good as human being who is keeping it. This paper discusses about the most typical software development quality gates in an industrial context. As well it gives reasoning why these gates are usable and defines general criteria for each of them. Paper notifies that even quality gates are in place, they are not useful if not followed. The theoretical discussion in this paper is constructive and follows the constructive research method. Industrial experiments are explained using a case study method.