A METHOD TO DESIGN A DOMAIN-SPECIFIC SOFTWARE PROCESS ARCHITECTURE IN A MULTIMODEL IMPROVEMENT ENVIRONMENT

In the multimodel improvement context, software organizations have the need to incorporate into its processes different practices of several software process improvement models (SPIMs) simultaneously (i.e. CMMI, PSP, ISO 15504 and others). Currently, a clear trend to the specialization of SPIMs to d...

ver descrição completa

Detalhes bibliográficos
Autor: MERY HELEN PESANTES ESPINOZA
Tipo de documento: tese
Estado:Versión aceptada para publicación
Data de publicação:2015
País:México
Recursos:Centro de Investigación en Matemáticas
Repositório:Repositorio Institucional CIMAT
OAI Identifier:oai:cimat.repositorioinstitucional.mx:1008/526
Acesso em linha:http://cimat.repositorioinstitucional.mx/jspui/handle/1008/526
Access Level:Acceso aberto
Palavra-chave:info:eu-repo/classification/MSC/Desarrollo de Software
info:eu-repo/classification/cti/1
info:eu-repo/classification/cti/12
info:eu-repo/classification/cti/1203
info:eu-repo/classification/cti/330406
Descrição
Resumo:In the multimodel improvement context, software organizations have the need to incorporate into its processes different practices of several software process improvement models (SPIMs) simultaneously (i.e. CMMI, PSP, ISO 15504 and others). Currently, a clear trend to the specialization of SPIMs to domain specific was identified. Over the last few years, software process architectures have been considered a means to harmonize these technologies. However, it is unclear how to design a software process architecture supporting a multimodel improvement environment. In this research, a method to design a domain-specific software process architecture supporting a multimodel environment (DS-SPAM) with a focus on the capture and organization of the domain knowledge to facilitate its reuse and maintainability is presented. This proposes a structure called the Software Process Architectural Domain Assets Set (SPADAS) as an approach for organizing domain knowledge. This method is described using basic concepts, phases, activities, tasks, roles and artifacts. Thus, our method mostly will assist process stakeholders in the extraction, design and documentation of their software process architecture as part of a multimodel solution