Process Management Methodology (original) (raw)

A COMPARATIVE ANALYSIS OF VARIOUS SOFTWARE PROCESS IMPROVEMENT MODELS

It is rightly said that the 'change is inevitable' and when the change has been witnessed in the positive direction it is termed as improvement. It can be either in terms of enhancement to the existing system or adaptability to cater the changing requirements of the users. Software Process Improvement is a process based approach to software development which lay stress on the techniques and tools for the improvement of software development processes. Software Process Improvement (SPI) consists of a set of activities that will lead to a better software process, and as a consequence, high quality software is delivered in a desired time span. Although it is an never ending process and is difficult to find any particular standardized model for all systems but SPI models provide a yardstick to access the existing processes and hence setting a path for designing the new models for development of new systems. The existing paper studies the various process models and explores the possibility of further improvement.

Software Process Improvement Model Comparison and Organizational Factors: A Review

Process and Continuous Process Improvement is a very important aspect of the software organization to meet the cost effective objectives of organizations in competitive environment. So it is a very big challenge for the organizations to constantly analyze their processes and improve them whenever necessary, to make a successful and quality software projects. Considering the importance of Software Process Improvement (SPI), we make a review of different models and make comparison of those. In the end we identify some success and resistance critical factors in the literature, which can be helpful for the organizations to improve their processes.

Some Key Topics to be Considered in Software Process Improvement

2014

This chapter summarizes a set of relevant aspects that may have a strong influence on the effectiveness of software process improvement and, as a consequence, on the competitiveness of software companies. Also included are the results obtained from a survey carried out in large companies on their processing needs in order to be more competitive. The organizational structures seen in different projects highlight the relevance of suitable processes as well as a culture of individual and organizational commitment. With this focus in mind, this chapter provides detailed information about teams, their construction and performance so that they can be effective in developing and implementing the processes. Finally, the chapter provides information about successful change management as well as advice on qualification of the workforce and technological tendencies, which is of key importance to achieve the objectives of competitiveness and process improvement.

Software Process Models and Project Performance

Information Systems Frontiers

In this paper we review the progress in software process research and the role of process improvement in enhancing business outcomes of software projects. We first describe the process view of software development. Next, we review the literature on software process research and discuss some of the leading software process models. The business value of software process improvements and empirical evidence from the software industry are also discussed in this paper. We conclude with a discussion of current challenges in software process research and directions for future research. Peer Reviewed http://deepblue.lib.umich.edu/bitstream/2027.42/46018/1/10796\_2004\_Article\_242160.pdf

Applying Software Process Modeling and Improvement in Academic

2004

This work is about the software process of a software engineering course project work. The quality manual contains a general process model, written in a formal software process modeling language that describes activities, tools, products, responsibilities, and measures. The quality manual serves as a basis for obtaining project specific plans, and for communicating the process to students, colleagues, and customers. The formal process model is the basis for analyzing and improving the process over the years, thus improving the quality of the provided education. The analysis of a given project run has revealed some problems and errors in the original model. This list of problems has been used as an action list to design a new process model. The new model will be exploited for the next years project runs.

Design of Software Process Improvement Model

International Journal of Computer Applications, 2012

Software process improvement (SPI) approaches have been designed to produce changes at many levels, i.e. in the strategies, culture and working practices, of software development. Studies have shown that nearly two thirds of all SPI efforts have failed or fallen short of expectations. SPI Software process improvement (SPI) today is based mainly on a perception of software processes as artifacts and this perception has led SPI efforts to focus on perfecting such artifacts as a means to improve the practices of the people supposed to execute these software processes. Such SPI efforts thus tend to view the design of software processes as separate from their use. In this approach process designers are expected to provide process knowledge to software developers, and software developers are expected to provide experiences and problems to the process designers. This focus on software processes as artifacts implies an emphasis on formalization and externalization of process models possibly at the expense of the process knowledge in the heads of the process users.

Expanding on the Process Perspective in Software Process Improvement Practices

2018

Process modeling is an essential part of software process improvement. This article aims at expanding the dominant paradigm of processes modeling where the organization's operations is seen as an idealistic mechanistic process. Our view is that enhancement of the process improvement practices requires re-evaluation of the main concept, that is the process view. Process philosophy and system thinking is offered to expand the perspective. Modeling involves essentially the ability of the modeler to abstract, i.e., the ability to look at the modeling object from a chosen point of view, and thereby distinguish and conceptualize the properties considered relevant to the purpose of the modeling.

Applying a framework for the improvement of software process maturity

Software: Practice and Experience, 2006

and maintenance of software for information systems. The aim of FMESP is to provide companies with a conceptual and technological framework for the management of their process models and measurement models in an integrated way. Modelling and measurement are two key factors to promote continuous process improvement. As a result, important benefits were obtained. The company improved the maturity of its processes which allowed it to obtain the ISO 9000 certification. From a research point of view, are Capability Maturity Model for Software (SW-CMM) [1], Capability Maturity Model Integration (CMMI) and Software Process Improvement and Capability Determination (SPICE), which has been standardized as ISO 15504 .

Applying software process modeling and improvement in academic setting

1997

Abstract This work concerns the software process of a software engineering course project work. The quality manual contains a general process model, written in a formal software process modeling language that describes activities, tools, products, responsibilities, and measures. The quality manual serves as a basis for obtaining project specific plans, and for communicating the process to students, colleagues, and customers.

A case study applying Process and Project Alignment Methodology

Software Process Improvement (SPI) is one of the main software development challenges. However, SPI standards and models (CMMI, SPICE) have not been always adopted with success. The current problem is a lack of strategy to implement successfully these standards and models. To undertake this objective is essential observe real life experiences and detect process and project mutual relationships. Without this alignment it will not be possible to find out how process management is really important to achieve organization's strategic objectives. This paper proposes a methodology that allows the definition, evaluation and improvement of an organization software development process. This proposal, called a Process and Project Alignment Methodology (ProPAM), allows the specification of an organization development process, as well process and project alignment. ProPAM presents the following life cycle: (1) process definition; (2) project definition considering a base process model; (3) project coordination and monitoring and (4) process improvement assessment. This paper also provides an overview of the action plan to be taken within the software organizations that intent to conduct a SPI initiative. This plan includes two distinct phases: (1) specify the development process and (2) analyze projects, starting an SPI effort. In order to evaluate ProPAM, a study case is undertaken. The case study is performed following the action plan and presents all the steps of the ProPAM. Final results show that, when the organization started using ProPAM, process and project alignment reduced project planning time and effort. ProPAM also introduced new organizational practices that result in a SPI program.