“SOFTWARE PROCESS IMPROVEMENTS WITH CMM”
ABSTRACT
“Understanding how software works will help to know how it can fail”
Abhishesh Kumar Sharma (AKS)
There are always these three questions going in the mind of any software implementers [19]:
Why is it so expensive to support and maintain my software products?
What is the reliability of our product?
What is the average cost of one software bug?
Software development organizations do not respond well to the process improvement innovations related to software development. Fear surrounds the thought of trying something new; this fear is accentuated by constant pressure to produce the product on time and within budget. Until recently, the vast majority of software companies did not view software development process management and improvement to be of strategic importance to the future of the company. Process improvement and its relationship to software quality, cost, and ability to meet schedules were never considered to be either useful weapons or, very often, differentiating factors against the competition. Nonetheless, a well-managed software development process can be viewed as an iterative process of information exchange and allows software development organizations a clear view and understanding of available information, providing a foundation for analysis and management of the software process based on hard facts and not vague assumptions. To be able to withstand the pressure of competition, to save money, and to improve the quality of production software, a progressive software development organization needs to realize the necessity for implementing and managing an efficient and effective software development process [16].
This paper presents the conceptual model of the Capability Maturity Model Integration (CMMI) which is being examined of multiple relationships between measurable process quantities and characteristics. The quality in software project management has evolved over a period of time and CMM has matured to a significant level that almost all software companies follows this model. The next big model used is the ISO for the quality but CMMI has upper hand in advancement of tools and techniques [22].
Although CMMI has matured to enormous level but still many short coming has been found while following the procedure mentioned in the CMMI technical specification. Lots of research has been done in this upcoming field but still there is lot of scope for improvement hence this paper is going to discuss the shortcomings of CMMI and will provide many new tools to help overcome these problems.
The concept of system thinking has been used so that the various ideas will focus on the relationships between the parts forming a purposeful whole [3, 6, 11]. The concept of system dynamics has been incorporated as that will give the continuous view of events. Feedback from the external environment has formed the integral part of the model development. Organizations will be able to design, build, and implement high-quality software products in spite of unexpected organizational and personnel changes, implementation of new technologies, or changes in customer requirements.
ABSTRACT
“Understanding how software works will help to know how it can fail”
Abhishesh Kumar Sharma (AKS)
There are always these three questions going in the mind of any software implementers [19]:
Why is it so expensive to support and maintain my software products?
What is the reliability of our product?
What is the average cost of one software bug?
Software development organizations do not respond well to the process improvement innovations related to software development. Fear surrounds the thought of trying something new; this fear is accentuated by constant pressure to produce the product on time and within budget. Until recently, the vast majority of software companies did not view software development process management and improvement to be of strategic importance to the future of the company. Process improvement and its relationship to software quality, cost, and ability to meet schedules were never considered to be either useful weapons or, very often, differentiating factors against the competition. Nonetheless, a well-managed software development process can be viewed as an iterative process of information exchange and allows software development organizations a clear view and understanding of available information, providing a foundation for analysis and management of the software process based on hard facts and not vague assumptions. To be able to withstand the pressure of competition, to save money, and to improve the quality of production software, a progressive software development organization needs to realize the necessity for implementing and managing an efficient and effective software development process [16].
This paper presents the conceptual model of the Capability Maturity Model Integration (CMMI) which is being examined of multiple relationships between measurable process quantities and characteristics. The quality in software project management has evolved over a period of time and CMM has matured to a significant level that almost all software companies follows this model. The next big model used is the ISO for the quality but CMMI has upper hand in advancement of tools and techniques [22].
Although CMMI has matured to enormous level but still many short coming has been found while following the procedure mentioned in the CMMI technical specification. Lots of research has been done in this upcoming field but still there is lot of scope for improvement hence this paper is going to discuss the shortcomings of CMMI and will provide many new tools to help overcome these problems.
The concept of system thinking has been used so that the various ideas will focus on the relationships between the parts forming a purposeful whole [3, 6, 11]. The concept of system dynamics has been incorporated as that will give the continuous view of events. Feedback from the external environment has formed the integral part of the model development. Organizations will be able to design, build, and implement high-quality software products in spite of unexpected organizational and personnel changes, implementation of new technologies, or changes in customer requirements.
1 comments:
Dear Abhishek
I very much appreciate your thought process towards real life scenario in the organizations.
I would like to have closure look at your paper.
Please inform access-url.
Regards Goyal
Post a Comment