scholarly journals Obstáculos al implantar el modelo CMMI / Difficulties when implementing the CMMI organizational model

Author(s):  
Himelda Palacios ◽  
Néstor Porcell

RESUMENEsta investigación analiza y propone estrategias de intervención que permiten identificar y superar los obstáculos de aprendizaje organizacional, que experimenta una organización cuando decide implantar el modelo de calidad para el desarrollo y mantenimiento de software, CMMI (Capability Maturity Model Integrated). Implantar el CMMI es más que definir procesos, procedimientos y formatos, lo que realmente implica es cambiar la cultura organizacional de las áreas y/o empresas de desarrollo de software, cambiar el comportamiento de los Ingenieros de Software. Las estrategias de intervención propuestas facilitan el cambio de la cultura organizacional requerido, para que una organización dedicada al desarrollo y mantenimiento de software pueda alcanzar con éxito los niveles de madurez definidos por el modelo CMMI. Este cambio de cultura implica orientar a la organización hacia los lineamientos definidos por la gestión de la calidad del software, la ingeniería de software, la gerencia de proyectos, la gerencia de procesos, el mejoramiento continuo de procesos, la gestión cuantitativa de procesos y el aprendizaje continuo.ABSTRACTThis research aims at analysing and proposing intervention strategies which allow to identify and avoid the risks in organization learning processes, when an organization decides to implement a quality model for the development and maintenance of specialized softwares, such as CMMI (Capability Maturity Model Integrated). This software design means much more than identifying processes, procedures and formats, which implies an organizational cultural change in the corresponding areas and companies in charge of software development changing the behavior of software design engineers. The intervention strategies suggested facilitate a change in organizational culture in this type of organization reaching success at high maturity levels based on the CMMI model. This will lead the organization to high quality standards in software design, software engineering, project management, process management, a continuing successful follow- up processes, quantitative process management and systematic learning.RESUMÉÉCette étude analyse et propose différentes stratégies d’intervention aidant à l’identification et à la résolution de problèmes liés à l’apprentissage organisationnel. Cela peut être le cas pour une organisation qui déciderait de mettre en place le modèle de qualité pour le développement et la maintenance de logiciels, CMMI (Capability Maturity Model Integrated). En effet, pour intégrer le CMMI aux processus organisationnels de l’entreprise, il s’agit moins de définir les procédures, formats et processus que de modifier la culture organisationnelle des départements et/ou entreprises informatiques de développement de logiciel ainsi que le comportement des ingénieurs informatiques. Les stratégies d’intervention proposées favorisent le changement de culture organisationnelle nécessaire pour qu’une organisation, tournée vers le développement et la maintenance de logiciel, puisse atteindre avec succès des niveaux de maturité définis par le modèle CMMI. Ce changement culturel implique une orientation de l’organisation aux directives définies par la gestion qualitative des logiciels, la gestion de projet, celle des processus de gestion, de l’amélioration continue des processus, de la gestion quantitative des processus et de l’apprentissage continu.RESUMOEsta pesquisa analisa e propõe estratégias de intervenção que permitem identificar e superar os obstáculos de aprendizado organizativo experimentados por uma organização quando decidir implantar o modelo de qualidade para o desenvolvimento e manutenção de software, CMMI (Capability Maturity Model Integrated). Implantar o CMMI é mais do que definir processos, procedimentos e formulários; em realidade implica a mudança da cultura organizativa das áreas e/ou empresas de desenvolvimento de software, mudar o comportamento dos engenheiros de software. As estratégias de intervenção propostas facilitam a mudança da cultura organizativa requerida, para que uma organização dedicada ao desenvolvimento e manutenção de software possa atingir com sucesso os níveis de maturidade definidos pelo modelo CMMI. Esta mudança de cultura implica orientar a organização em direção aos lineamentos definidos pela gestão da qualidade do software, a engenharia de software, a gerência de projectos, a gerência de processos, o melhoramento contínuo de processos, a gestão quantitativa de processos e o aprendizado contínuo.

2021 ◽  
Vol 2021 ◽  
pp. 1-10
Author(s):  
Li Hou ◽  
Qi Liu ◽  
Kiran Saeed ◽  
Saqib Ali Haidery ◽  
M. Irfan Uddin ◽  
...  

Business process modeling was suggested by academia and implemented by the industry to trigger device requirements. Maturity models of software processes are also similar in the software industry. Therefore, business software requirement engineering approaches-based process should aim to fulfil with the maturity models. Although researchers in the area of Software Engineering, Project Management, and Business Intelligent have addressed planning and execution and a lot of research still needs to be done, in this study, we focused on doing a questionnaire based on different prominent universities, major companies, and software houses. The purpose of the questionnaire was to dig out the main factors that negatively affect software houses and their products and services, especially in the medical field. A questionnaire was generated to accomplish these reasons, and interviews were conducted to extract the key explanation why software developers and software houses in developing countries are not familiar with the CMMI (Capability Maturity Model Integration) model for medical software projects. This analysis attempted to figure out why the tech enterprises of developing countries are behind foreign competitors. We aimed to determine why software developers do not meet the international requirements for software. The novelty of the research is that attempts were made to strengthen the new approach by adding agile at level 3 to keep the local software industry appropriate and reveal the requirements for medical software life cycle study, because accurate decision support is really necessary for healthcare systems.


2017 ◽  
Vol 5 (3) ◽  
pp. 67-73 ◽  
Author(s):  
Daniel Adrian Doss ◽  
Raymond Tesiero ◽  
Balakrishna Gokaraju ◽  
David McElreath ◽  
Rebecca Goza

Sign in / Sign up

Export Citation Format

Share Document