AIRCC's International Journal of Computer Science and Information Technology

Open Access Open Access  Restricted Access Subscription Access

A Process Quality Improvement Mechanism for Reducing the Risk of CI Environment


Affiliations
1 Dept. of Information Technology and Management, Shih Chien University, Taipei, 104, Taiwan, Province of China
 

In the age of fast evolution, software development project must accept many challenges of unpredicted requirements change and new technology environment. Software development processes should have adjustable and extendable features to meet the multifaceted needs of the users. Iterative and Incremental Development (IID) is a practical approach to overcome the various challenges of software development. However, continuous testing and building new versions need to spend more time and human resources that is a major obstacle of IID. The other, the iterative operations must have a sound communication skills. Lack of standard version control and intercommunication manner often lead to failure of software project. High quality Continuous Integration (CI) environment can effectively make up the defects of IID. In this paper, CI environment and advantages are deeply surveyed. In order to overcome the defects of IID, CI environment needs combine the perfect procedures and qualified tools, and concretely enhance the quality of CI environment. Based on the process quality measurement model, this paper proposes the Process Quality Improvement Mechanism (PQIM). Applying PQIM, in software development, the processes problems and the CI environment quality defects can identify timely and indeed revise to reduce the risk of CI environment.

Keywords

Continuous Integration, IID, Development Risk, CI Environment, Quality Improvement.
User
Notifications
Font Size

  • Eveleens J. L. and Verhoef, C. (2010) “The Rise and Fall of the Chaos Report Figures, IEEE Software,” vol. 27, no. 1, pp30-36

  • Boehm, B. W. (1991) “Software risk management: Principles and practices,” IEEE Software, vol. 8, no. 1, pp32-41.

  • Schach S. R. (2011) Object-Oriented and Classical Software Engineering, Eighth Edition, McGraw-Hill, New York.

  • Larman C. and Basili, V. R. (2004) Iterative and Incremental Development: A Brief History, Computer, IEEE CS Press, pp47-56.

  • Martin, R. C. (2002) Agile Software Development, Principles, Practices and Patterns, Prentice Hall,

  • Martin Fowler, (2006) “Continuous Integration,” martinfowler.com, http://www.martinfowler.com/articles/continuousIntegration.html

  • Duvall, P.: Continuous Integration Servers and Tools, DZone Refcardz. (2015) https://dzone.com/refcardz/continuous-integration-servers#, (accessed Auguest 9, 2015)

  • Duvall, P. and Matyas, S. and Glover, A. (2007) Continuous Integration: Improving Software Quality and Reducing Risk, Pearson Education, Inc.

  • Saff, D. and Erns,M. D. (2003) Reducing Wasted Development Time via Continuous Testing, Proceeding of IEEE International Symposium on Software Reliability Engineering (ISSRE), pp281-292

  • Hornstein, H. A. (2015) “The integration of project management and organizational change management is now a necessity,” International Journal of Project Management, vol. 33, no. 2, pp291-298.

  • STEWART J. (2015) Top 10 Reasons Why Projects Fail, http://project-management.com/top-10-reasons-why-projects-fail/.

  • Symonds M. (2011) 15 CAUSES OF PROJECT FAILURE, https://www.projectsmart.co.uk/15-causes-of-project-failure.php.

  • Szalvay, V. (2004) An Introduction to Agile Software Development,” CollabNet, Inc.

  • Hoda, Rashina, et al. (2017) “Systematic literature reviews in agile software development: A tertiary study,” Information and Software Technology 85 pp60-70.

  • Santos, M. A., et al. (2013) “Improving the Management of Cost and Scope in Software Projects Using Agile Practices,” International Journal of Computer Science & Information Technology (IJCSIT) 5(1).

  • Booch, G. (1994) Object-Oriented Analysis and Design with applications 2nd edition, Addison Wesley Longman.

  • Beck, K. (2003) Test-Driven Development: By Example, Addison-Wesley.

  • Beck, K. (2004) Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series) 2nd Edition

  • Leon, A. (2015) Software Configuration Management Handbook, Third Edition, Artech House Inc.

  • Fenton, N. E. (1991) Software Metrics - A Rigorous Approach, Chapman & Hall.

  • Galin, D. (2004) Software Quality Assurance – From theory to implementation, Pearson Education Limited, England .

  • Boehm, B.W. (1981) Software Engineering Economics, Prentice-Hall, New Jersey.


Abstract Views: 326

PDF Views: 129




  • A Process Quality Improvement Mechanism for Reducing the Risk of CI Environment

Abstract Views: 326  |  PDF Views: 129

Authors

Sen-Tarng Lai
Dept. of Information Technology and Management, Shih Chien University, Taipei, 104, Taiwan, Province of China

Abstract


In the age of fast evolution, software development project must accept many challenges of unpredicted requirements change and new technology environment. Software development processes should have adjustable and extendable features to meet the multifaceted needs of the users. Iterative and Incremental Development (IID) is a practical approach to overcome the various challenges of software development. However, continuous testing and building new versions need to spend more time and human resources that is a major obstacle of IID. The other, the iterative operations must have a sound communication skills. Lack of standard version control and intercommunication manner often lead to failure of software project. High quality Continuous Integration (CI) environment can effectively make up the defects of IID. In this paper, CI environment and advantages are deeply surveyed. In order to overcome the defects of IID, CI environment needs combine the perfect procedures and qualified tools, and concretely enhance the quality of CI environment. Based on the process quality measurement model, this paper proposes the Process Quality Improvement Mechanism (PQIM). Applying PQIM, in software development, the processes problems and the CI environment quality defects can identify timely and indeed revise to reduce the risk of CI environment.

Keywords


Continuous Integration, IID, Development Risk, CI Environment, Quality Improvement.

References