PIT-ProcessM: A Software Process Improvement Meta-Model (original) (raw)
Related papers
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.
PSEE -Process-centered Software Engineering Environment -PSEE has one of its intentions to provide that phases of the software process life cycle (definition, simulation, enacting and evaluation) can be automatized. This work presents the structure and the automation of a software process meta-model capable to group terminologies of processes based on quality models/norms and to help in the implementation and refinement these types of processes. This implementation must be made from characteristics and properties that define an organization or a specific domain of software project. The meta-model services were automatized trough a tool and the description of them can be found in this paper.
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.
A modest but practical software process modeling technique for software process improvement
Software Process: Improvement and Practice, 2002
One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals.
SP2MN: A Software Process Meta-Modelling Language
In the last two decades, software process modeling has been an area of interest within both academia and industry. Software process modeling aims at defining and representing software processes in the form of models. A software process model represents the medium that allows better understanding, management and control of the software process. Software process meta-modeling rather, provides standard metamodels which enable the defining of customized software process models for a specific project in hand by instantiation. Several software process modeling/meta-modeling languages have been introduced to formalize software process models. Nonetheless, none of them has managed to introduce a compatible yet precise language to include all necessary concepts and information for software process modeling. This paper presents Software Process Meta-Modeling and Notation (SP2MN); a meta-modeling language that provides simple and expressive graphical notations for the aim of software process modeling. SP2MN has been evaluated based upon the well-known ISPW-6 process example, a standard benchmark problem for software process modeling. SP2MN has proved that it presents a valid and expressive software process modeling language.
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.
A conceptual map of software process improvement
2001
Software organisations have for many years struggled to mature engineering practices using a variety of approaches. Over the last decade a new approach, known as software process improvement (SPI), has emerged and become widely used in the software industry. In this paper we position SPI in the landscape of initiatives that can be used in software organisations to mature their operations. A map is offered describing the characteristic features of SPI initiatives, the benefits and risks related to such initiatives, and the relations to complementary approaches to professionalise the industry. The map highlights management, approach, and perspective as three main concerns of SPI and lists three key ideas for each of these concerns. The map is based on an extensive survey of the SPI literature combined with experiences from SPI practice. Practitioners can use the map strategically to make decisions on whether to initiate SPI initiatives, to integrate SPI efforts with other improvement initiatives, and, more generally, to create and manage improvement programs based on SPI ideas. Researchers can use the map to identify key questions and areas of knowledge that can fruitfully inform SPI theory and practice.
Empirical Research in Software Process Modeling: A Systematic Literature Review
2011 International Symposium on Empirical Software Engineering and Measurement, 2011
Recognized as one of the powerful technologies in software process engineering, Software Process Modeling (SPM) has received significant attention over the last three decades. Although empirical research plays a critical role in software engineering, the state-of-the-practice of empirical research in SPM has not been systematically reviewed. This paper serves as a status report of the assessment of empirical research in SPM by analyzing all refereed studies that were published in relevant venues from 1987 to 2008 using systematic review methodology. The primary findings indicate that in current SPM-related empirical studies, (1) software process management and improvement (SPI) was not yet the most popular primary research objectives; (2) exploratory empirical research methods, e.g., case study and action research, were dominantly used; (3) there were common issues in empirical research reports in terms of following rigorous reporting guidelines. Based on the review results, we also suggest the future needs for empirical research in SPM, in terms of research topics, SPM techniques, the strengths of research methodology and the rigors of empirical studies.
Software Process Definition and Improvement
This textbook comprises software and system engineering processes, advanced process technologies, software process management, and foundations of process improvement. The goal of this textbook is to provide knowledge and skills for understanding, designing, analyzing, applying, deploying, and improving software and system engineering processes. After reading this book, the reader should be able to: - understand the benefits of using software process models and process management, - identify goals for process modeling and management, - understand the underlying principles of software process modeling, management, and improvement, - analyze the advantages and disadvantages of different process modeling techniques and notations, - design and model software development processes for different purposes, - apply methods and notations for process modeling, - understand existing industrial software and system development processes, - analyze software and system development processes, - apply process management effectively for different purposes, - understand the importance of software process improvement, - identify software-related improvement goals for an organization and set priori-ties for improvement, - understand process maturity frameworks (e.g., CMMI), - understand the differences between existing process improvement approaches, - critically evaluate software process improvement approaches, - understand important mediators and obstacles when modeling, deploying, managing, and improving software development processes, - name and distinguish different lifecycle process models, - develop process handbooks, - deploy a prescriptive process model to an organization, understand the use of simulation in software process modeling, - be able to distinguish different types of process simulation models.
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.