Software Process Improvement

Software Process Improvement

Introduction

Software development is just not the science, but it is the combination of science and arts. Software development is very fast today, and it is very important in its life cycles. Software development is not an easy task. It is challenging, and becoming difficult day by day. Software development requires the full attention of the people of one project team. In previous years, there were tools and techniques used for the improvements of the software development. Many of these techniques were successful. All organizations need improved and new technological data in order to make developments.

Discussion

The need of process improvement is when the organizations who are running the software houses encounter problems. This problem require the sudden change: otherwise, these problems may get big trouble. The common problems may include when customer is not satisfied, software quality is not good, not able to deliver in time, not matching the budget, and other problems. When these issues are in front, then is sudden need to overcome these problems. The improvement should start soon, and there should be support from the high level in the organization. In some cases, improvements require the customer's certification and proficiency level. Some customer needs little improvements or just to do little better than previous. The motivations should be focused and once the motivation is achieved then strategies should be kept in mind while improving the program. Process improvement is the process which guarantees no success. We can start the improvement program by mapping the whole software development. There are models for software programs. There is a well known model namely Capability Maturity Model for Software (CMM). It is developed by the Software Engineering Institute in Carnegie-Mellon University. This software is successfully working within ten years. This model provides various frameworks to the improvement of software programs. These programs are well structured in the way that they look sophisticated and proficient. This model serves as a guide line for organizations and helps the organizations at every level. Every small and large Information Technology organization needs Software Processes for different projects they work for. There is an effort behind every single software process to support and improve it. This support and improvement is the Software Process Improvement (SPI). In last ten years, there is much effort in Software Process Improvement (SPI) and is all based on software capability maturity model (CMM) (Paulk, Curtis et al. 1993). The purpose of SPI is to develop infrastructure which support the project models and support the business in any condition. It is not easy to achieve such goals. There are risks and threats associated with SPI, and it is facing challenges every other day. We do not know the actual figure that how many companies have adopted SPI and how many refused to adopt SPI. In order to reach at a high level organization has to go through certain processes such as Capability maturity models (CMM). Software development is not an easy process. That is why SPI need lot of ...