Process Improvement in Mechanical Design Using a Derivation of The Systems Engineering Capability Maturity Model

Author(s):  
I. Egan ◽  
I. Black ◽  
J. M. Ritchie ◽  
P. D. Gardiner
2014 ◽  
pp. 1385-1400 ◽  
Author(s):  
Maged Abdullah ◽  
Rodina Ahmad ◽  
Lee Sai Peck ◽  
Zarinah Mohd Kasirun ◽  
Fahad Alshammari

Software Process Improvement (SPI) has become the survival key of numerous software development organizations who want to deliver their products cheaper, faster, and better. A software process ultimately describes the way that organizations develop their software products and supporting services; meanwhile, SPI on the other hand, is the act of changing the software process and maintenance activities. This chapter purposefully describes the benefits of software process improvement. The Capability Maturity Model (CMM) and the Capability Maturity Model Integration (CMMI) are briefly surveyed and extensively discussed. Prior literature on the benefits and impacts of CMM and CMMI-based software process improvement is also highlighted.


Author(s):  
Badariah Solemon ◽  
Shamsul Sahibuddin ◽  
Abdul Azim Abd Ghani

Requirements Engineering (RE) is a key discipline in software development, and several standards and models are available to help assess and improve RE processes. However, different standards and models can also help achieve different improvement goals. Thus, organizations are challenged to select these standards and models to best suit their specific context and available resources. This chapter presents a review of selected RE-specific and generic process improvement models that are available in the public domain. The review aims to provide preliminary information that might be needed by organizations in selecting these models. The chapter begins with analyses of how RE maturity is addressed in the Capability Maturity Model Integration (CMMI) for Development. Then, it describes the principal characteristics of, and the assessment and improvement framework applied in four RE-specific process assessment and improvement models: the Requirements Engineering Good Practice Guide (REGPG), the Requirements Engineering Process Maturity(REPM), the Requirements Capability Maturity Model (R-CMM), and the Market-Driven Requirements Engineering Process Model (MDREPM). This chapter also examines the utility and lesson learned of these models.


Author(s):  
Farley Simon Nobre ◽  
Andrew M. Tobias ◽  
David S. Walker

This chapter is concerned with the implementation of The Capability Maturity Model in the organization of study. In this application, we define measures of organization process improvement and we propose correlations between them and organizational cognition. Among these measures are included organization process maturity, capability, and performance. Therefore, we define correlations between organizational cognition and organization process maturity, and also between organizational cognition and organization process capability and performance. From such correlations, we also define an association between organizational cognition and organizational learning. Hence, we outline new directions to the development of approaches to assess, to evaluate and to measure the degree of organizational cognition from appraisal methods of The Capability Maturity Model and of other organization process improvement models. Moreover, Chapter IX is complemented by Appendix I which summarizes concepts and characteristics about the five maturity levels of The Capability Maturity Model.


Author(s):  
Rick Gibson

This chapter will identify the key aspects of software engineering and systems engineering in an effort to highlight areas of consensus and conflict to support current efforts by practitioners and academics in both disciplines in redefining their professions and bodies of knowledge. By using the Software Engineering Institute’s Capability Maturity Model –Integrated (CMMISM) project, which combines best practices from the systems and software engineering disciplines, it can be shown that significant point of agreement and consensus are evident. Nevertheless, valid objections to such integration remain as areas of conflict. This chapter will provide an opportunity for these two communities to resolve unnecessary differences in terminology and methodologies that are reflected in their different perspectives and entrenched in their organizational cultures.


Sign in / Sign up

Export Citation Format

Share Document