CMMI Process Research Articles

Research on the Evaluation System of Digital Management Process Improvement of Automobile Transaction Business Based on CMMI

With the rapid development of information technology, enterprise digitalization, and Internet + application, the digitalization and improvement of the used car trading business and its management process improvement are facing many challenges. This paper attempts to use the CMMI process improvement model to analyze the factors affecting the digital construction, business process optimization, and digital management process improvement of the used car market through research on the digital management process and the related theories of CMMI, such as talent training, application of information technology, immature business development, irregular business process, and industry policy restriction. The FAHP analysis method is used to establish a comparison matrix to explore the construction of an evaluation system model for the improvement of the digital management process of the used car trading market based on the CMMI model.

AN EXPERIENCE OF IMPLEMENTING SOFTWARE DEVELOPMENT MANAGEMENT SYSTEM BY COMBINING CMMI WITH AGILE IN SMALL AND MEDIUM-SIZED ORGANIZATION

Nowadays, the research on improvements of software development processes has been developing extensively in software organizations. Currently these researches are focusing on how to combine CMMI with Agile. In addition, most of the software development organizations all over the world are small or medium, not large. Such small and medium-sized organizations play a great role in the software industry. However, there is lack of case studies that small and medium-sized organizations implement CMMI process areas to establish their development management systems, especially practical and helpful case studies that such organizations may apply to combine with Agile for improving their management systems. Our goal is to share our experience in successful improvements of development process under the industrial environment from an empirical point of view. And these results cannot be generalized, but they point out that under some circumstances in small and medium-sized organizations, a combination strategy of CMMI and Agile can be a possible option for software professionals. In this paper we present our experience of implementing a DMS (Development Management System), in which CMMI is combined with Agile, for a small and medium-sized software development aiming at CMMI level 3. Moreover, we give the result that our organization applied this DMS.

A sustainable procedural method of software design process improvements

In practice, the software process is an intermediate phase for enhancement and improvements the design for different types of software products and help developers to converts the specified requirements into prototypes that implement the design into reality. The objective of this paper is to provide software developers, designers and software engineers who work in small companies with a standards-based process improvement using a procedural method technique including detailed steps for designing the small software systems into their companies. The method used in this paper includes 1) analysis four different types of commonly design processes used by industry such as CMMI, conventional or software process in ISO 19759, generic and engineering design processes. 2) mapping between those four design processes. 3) collect the dispersed design concepts proposed by those four processes. 4) proposed a sustainable procedural method of software design process improvements 5) Illustration of the applicability of the proposed approach using A template-based implementation. The primary result of this study is<strong> </strong>a guideline procedure with detailed steps for<strong> </strong>software design process improvements to help and guide developers in small companies to analyze and design a small software scales with limited cost and duration. In conclusion<strong>, </strong>this paper proposed a method to improve the design process for different kinds of the software systems<strong> </strong>using<strong> </strong>a template-based implementation to reduce the cost, effort and time needed in the implementation phase<strong> </strong>in small companies. The scientific implication<strong> </strong>behind a template-based implementation helps the system and software engineering to use this template easily in their small companies; because most of the time those engineering developers are responsible for analyzing, designing, implementing and testing their software systems during the whole software life cycle.

Structural Analisys of CMMI with the Software Development Process, Project Portfolio Management and PMBOK

Abstract. CMMI is one of the most used models in the software industry to certify the quality of its processes and products, reduces or eliminates rework, increases product and process reuse, reduces costs due to multiple evaluations and process improvement programs. On the other hand, companies that develop software apply traditional models or agile models, which manage the software development process. They also apply development standards such as ISO/IEC 12207 as well as project portfolio management standards and project management standards. The purpose of this paper is to relate the traditional and agile software development processes, project portfolio management and PMBOK with the CMMI standard. The results of this work allow us to determine the aspects that are missing from these standards and the best practices to reach a high level of CMMI maturity. It is concluded that for a company it is important to apply both agile processes and traditional processes, as well as all the standards that contribute improving the management of its projects. None of these practices and norms are opposed to the CMMI process areas, but rather are complemented to achieve a high level of quality in the final product and in achieving the objectives of the company.

CMMI 기반 시스템공학과 프로젝트관리 통합 프로세스 아키텍처 개발

시스템의 규모와 요구기능은 점점 대형화되고 복잡해지고 있다. 이러한 시스템 개발 프로젝트의 성공적인 수행을 위해서는 프로세스에 따른 체계적인 시스템공학(SE)과 프로젝트관리(PM) 활동이 요구되고 있다. 시스템 개발 조직에서는 SE&PM 프로세스 개선 및 능력평가 모델인 CMMI를 채택하여 SE&PM 능력 확보에 노력하고 있으며, 이를 위해 조직의 비즈니스 특성에 맞는 조직 표준 프로세스를 구축하여 적용하고 있다. 하지만 시스템 개발조직 현장에서는 CMMI 프로세스영역 간 상호연관성에 대한 충분한 이해부족으로 조직 프로세스 구축에 어려움이 따르고 있다. 또한 SE와 PM활동은 시스템 개발에 있어서 상호 밀접하게 연관되어 있기 때문에 SE와 PM 프로세스는 상호 통합 및 연계성이 확보되어야만 효과적이고 효율적인 프로젝트 수행이 될 것이다. 본 논문에서는 시스템 개발 조직에서 CMMI 기반 조직 프로세스 구축에 참조되고 활용될 수 있는 조직의 SE&PM 통합 프로세스 아키텍처를 제시한다. 【The scale and required functionality of modern systems have increased and become more complicated. To successfully carry out the systems development projects, appropriate systems engineering (SE) and project management (PM) activities are required for the underlying process. In a system development organization, it is an effort to secure the SE & PM capability by adopting the CMMI is an evaluation model of improvement and ability of SE&PM process. To achieve the goal each organization establishes and uses its own organizational standard process, which satisfies the business characteristics. However, in practice, due to the lack of sufficient understanding on the interrelationship among different CMMI process areas, there still exist some difficulties with constructing organization processes. In systems development, the activities of SE are closely related with those of PM. Thus, the processes of SE and PM need to be fully integrated and explicitly linked to each other in order to complete the projects successfully. In this paper, we propose a SE&PM integration process architecture of organization that can be utilized in the system development organization is referenced in the construction of CMMI-based organizational process.】

MAPPING INFORMATION TECHNOLOGY INFRASTRUCTURE LIBRARY WITH OTHER INFORMATION TECHNOLOGY STANDARDS AND BEST PRACTICES

Information Technology (IT) has become an important strategic resource that any organization has to manage. It has been recognized that IT services are crucial and strategic organizational assets, therefore, organizations are investing considerable amount of resources into the support and delivery of IT services and the systems that underpins them. Various IT standards and IT best practices are being implemented by the enterprises to support their business and IT services. A number of these standards are different from others but they contain some similarities. This study discusses these IT standards and best practices and maps their processes to ITIL. CobiT, ISO/IEC 27002-2005, Six Sigma, TOGAF, eTOM, CMMI, PCI DSS and Common Security Framework (CSF) processes will be mapped to ITIL processes. This study will show the similarities between several IT standards and ITIL that helps in adopting these standards concurrently with ITIL. ITIL and other standards have many similarities that will benefit enterprises in implementing these standards concurrently.

Research and Analysis of CMMI Process Improvement Based on SQCS System

Traditional software development methods have been unable to meet the software implementation quality guarantee with current cross-cutting and a variety of system features. Over the years using complex project, it continuously explore and in-depth study of the CMMI quality system application. The project thoughts are applied to the complicated software development process management and quality assurance. With new ideas and methods, it achieves effectively control to multi-dimensional and multi-level heterogeneous feature model system of the software engineering quality. So it can enhance software efficiency and quality of development. After the results analysis of implementation in recent years, the system has a certain degree of practicality, maneuverability and popularization. DOI: http://dx.doi.org/10.11591/telkomnika.v10i7.1584

Role of Requirement Management as a CMMI Process Area in Requirement Engineering

The research shows role of requirement management as a CMMI process area in requirement engineering (a phase of software engineering). Requirement engineering (RE) activity consists of several activities like requirement elicitation by feasibility studies, requirement analysis, requirement validation and requirement management. While performing RE, recognized formal standards should follow like CMMI, ISO etc. Proposed work helps in RE process by acquiring CMMI requirement management process area at level 2. There is confusion in the minds of software personnel between the requirements management process area in CMMI and manage requirements activity in the requirement engineering. So they don’t consider requirement management process area as development improvement approach, they think that we don’t need anything which requires explicit methods to apply on existing process. Mistake leads to inefficient requirement engineering. The study gives an idea about importance of requirement management while gathering, analyzing and implementing the requirements which are given by the stakeholders. Sometimes stakeholders don’t know about their actual requirements and due to this, misunderstanding takes place which brings dissatisfaction of stakeholders and ultimately results poor reputation of organizations. General Terms et. al.

A Quality-Distinction Model of IT Capabilities: Conceptualization and Two-Stage Empirical Validation Using CMMi Processes

In this paper, we develop a model of information technology (IT) service provider capabilities termed the quality distinction (QD) model that is theoretically rooted in the resource-based view and quality management literatures, and operationalized using the widely used capability maturity model (CMM) framework. The QD model is theorized to consist of one dynamic capability (i.e., process adaptation capability) and three operational capabilities (i.e., life cycle, prevention quality, and appraisal quality capabilities). These four capabilities are initially operationalized using definitions of the 22 processes in the CMM integration framework. A panel of experts is used to assign the 22 processes to the four capabilities in the QD model. Rigorous scale-refinement procedures are used and 15 CMM processes are retained as a result. Survey data collected from IT service providers are, then, used to compare the theorized QD model with the staged and continuous models in the CMM framework. Results from a covariance-based structural equation modeling analysis provide good support to the hypothesis that the QD model is superior to the two CMM models (the staged and continuous representations), with the theorized model showing high fit indices and high psychometric properties. Results also provide support for the hypothesis that processes should be operationalized as routines with a combination of both ostensive and performative aspects.

Strengthening maturity levels by a legal assurance process

AbstractOne of the key elements for the viability of information system projects is given by the adoption of legal assurance activities and measures since nowadays they can arise legal risks that, in some cases, can suppose a serious threat for project commercial and financial success. When calculating the return of investment (ROI) for a software process improvement initiative, readers would not take care which are the cost issues impacting on such values, supposing the activities generating such value are referable only to the processes included in a Maturity Model (MM) such as CMMI or ISO 15504. During last years, moving from the initial Philip Crosby's idea for measuring and checking the organizational evolution of an organization, a plenty of MM have been created, but there is no news about a legal assurance (LAS) process that make more systematic the way legal risks are (or should be) managed. On the other hand, professional practice usually does not incorporate standardized processes in order to discipline the legal assurance activities and measures, returning a feeling for a lack of project legal security.This article proposes to take care of LAS process as an additional process area within an MM, in order to provide a suitable instrument for the management of inherent legal risks to any information systems project. After presenting main elements for this new process, it will be presented using the typical CMMI Process Area architecture, where it would be configurable as a support process at Maturity Level 2 (ML2). Copyright © 2009 John Wiley & Sons, Ltd.

Applying UML and software simulation for process definition, verification, and validation

Process definition, verification, and validation are recognized as critical elements in software process improvement, whereas CMMI is a process improvement approach that provides organizations with the essential elements of effective processes. Organizations must define their own processes to meet the requirements of CMMI. A friendly, unambiguous process modeling language and tool are thus very important for organizations to define, verify, and validate the processes. Nevertheless, hardly has any research yet been done on how to embed CMMI process area goals into process definition stage to satisfy organization process improvement. In this research, we propose a UML-based approach to define, verify, and validate an organization’s process. Our approach can also be applied to a process learning environment for students and project members.

지능형 성숙도 모델을 이용한 소프트웨어 집약 시스템의 전투실험 프로세스 설계 및 적용

We propose the design of the warfighting experiment process for software intensive systems using the intelligent maturity model and suggest the application results of the target searching capability in smart UAV. For this, we design the intelligent maturity model to evaluate the intelligent degree of the software intensive systems considering the domain and intelligent level. Then we classify the IS0/1EC-12207 process and CMMI process as LITO domain for designing the warfighting experiment process, map the classifed process to the five factors of the warfighting experiment and derive the process as warfighting experiment element and phase. Based on the derived process, we design the warfighting experiment process using the IDEF0. Finally we apply the proposed process to the target search capability and suggest the results which are required to develop and acquire the smart UAV.

10.2.3 Guidance on Tailoring of Systems Engineering Processes for Quick Reaction Capability (QRC) Developments

AbstractAlthough the very basis for establishment of the discipline of systems engineering is grounded in development of large, complex systems, the principles and processes are also extremely valuable for other types of systems. As discussed in (INCOSE Handbook 2004) the responsibilities of systems engineers, that include “requirements analysis, functional analysis and allocation, architecture/design, systems analysis and control, and verification and validation of the system”, while “most apparent on large, complex systems … are also important in the development, production, deployment, and support of much smaller systems.”A Quick Reaction Capability (QRC), the focus of this paper, is a type of system development characterized by deployment of a critical capability to satisfy an urgent need in which the normal acquisition process is accelerated. That is, the driving requirement is the timely delivery of the system to operations. In this paper, we provide guidance on tailoring the CMMI processes for QRC developments to achieve mission success while satisfying the shortened development schedule. We assert that identifying and implementing the right SE processes is of even greater value for conducting a QRC development, precisely because time is such an important consideration.

An evaluation of CMMI process areas for small‐ to medium‐sized software development organisations

AbstractIn this article, we describe the results of CMMI software process appraisal work with six small‐ to medium‐sized software development companies. Our analysis of six CMMI process areas appraised within each of these organisations is presented. Commonly practiced or not practiced elements of the model are identified, leading to the notion of perceived value associated with each specific CMMI practice. A finer‐grained framework, which encompasses the notion of perceived value within specific practices, is presented. We argue that such a framework provides incentive to small‐ to medium‐sized enterprises starting process improvement programmes. Copyright © 2005 John Wiley & Sons, Ltd.

5.2.2 Self Organizing Maps (SOMs) for Systems, Software, Management and CMMI Document Relevancy

AbstractThe size of the systems engineering book of knowledge is unknown, but continuously expanding! The systems and software standards are quagmires of legacy and evolution. Stacks of documents (books, standards, guidebooks, handbooks, papers, process manuals) relate to the subject of systems engineering and engineering management. Developing ‘best practices‘, from systems engineering bodies of knowledge (Beshore 2001), is critical to the future engineering success of large programs. The CMMI (CMMI) represents the latest internationally driven model requirements standard for systems engineering, software engineering and integrated product development. An automated method is presented in this paper to determine document relevance to any body of knowledge or sets of process or process assessment standards. Specific examples and uses of new tools have been used to improve documentation relevancy of Raytheon's IPDS (Integrated Product Development System) to the CMMI process requirements models. With this approach there is a way out of the document and standards quagmire through more focused process planning on programs.