Managing Model Quality in UML-Based Software Development

Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

Investigacion e Innovación en Ingenierias ◽

10.17081/invinno.3.1.2037 ◽

2015 ◽

Vol 3 (1) ◽

Author(s):

Adriana Iglesias ◽

Acellys Messino ◽

Patty Pedroza ◽

Ricardo Llanos

Keyword(s):

Best Practices ◽

Software Development ◽

Continuous Improvement ◽

Process Management ◽

Model Development ◽

Agile Development ◽

Total Quality ◽

Model Quality ◽

Development And Management ◽

Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

Download Full-text

Managing the Quality of UML Models in Practice

Model-Driven Software Development ◽

10.4018/978-1-60566-006-6.ch001 ◽

2009 ◽

pp. 1-36 ◽

Cited By ~ 4

Author(s):

Ariadi Nugroho

Keyword(s):

Software Development ◽

Software Quality ◽

Model Quality ◽

Model Driven ◽

Testing Phase ◽

Development Life Cycle ◽

Computer Scientists ◽

Model Driven Software Development ◽

Quality Assessments

Many studies have been carried out to investigate what makes up good quality software. Some of the early models that define the quality of software come from Boehm (1976) and McCall (1977). Works in this field of quality models have traditionally focused on quality of the final software product. Since the 1970’s models of software have been used and this has recently attracted much attention through the popularity of model-driven software development (MDSD). However, quality of software models has rarely been considered (Lange & Chaudron, 2005). In the software development life cycle, the ability to assure software quality long before the testing phase may save a lot of money since less defects found in the testing phase will mean less effort to be allocated for rework. Currently, the importance of model quality is starting to gain attention from computer scientists. Work in this area has since focused on developing tools, metrics, and frameworks to improve the quality of models that guide implementation, particularly in the context of UML modeling which has become the de facto standard for building object oriented software. Quality of models can be considered from many different perspectives. In this chapter, we will consider the following perspectives: Firstly, is the model complete in the sense that it describes the information that developers need to know about a system? Secondly, we look at the degree in which a model of a system and an implementation correspond. This degree of correspondence indicates to what extent analyses of—or predictions based on the model are valid for the implementation. We present the main findings from case studies into quality of modeling in the software industry as well as findings from a survey amongst professional software developers. We also provide a discussion on the contemporary methods for design quality assessments.

Download Full-text