Content uploaded by Francisco Ruiz
Author content
All content in this area was uploaded by Francisco Ruiz on Nov 25, 2014
Content may be subject to copyright.
A preview of the PDF is not available
Agil_MANTEMA: Una Metodología de Mantenimiento de Software para Pequeñas Organizaciones.
Figures
Figures - uploaded by Francisco Ruiz
Author content
All figure content in this area was uploaded by Francisco Ruiz
Content may be subject to copyright.
... Esto puede generar problemas en la calidad y eficiencia del mantenimiento. Esta opinión también es compartida por [12], quien afirma que raramente existen procesos establecidos, de modo que el mantenimiento se lleva a cabo como se pueda. Según [13], el mantenimiento de software puede tener varios efectos secundarios, que se detallan en la Tabla I, II y III. ...
... La metodología Ágil MANTEMA (proviene de la combinación de las palabras "MANTenimiento" y "MÉTodo") basada en SCRUM, se centra en la gestión eficiente de las etapas y actividades relacionadas con el mantenimiento de software, transformándolas en procesos supervisables y medibles de manera efectiva [12]. Ágil MANTEMA define varios niveles de servicio, destacando dos tipos de mantenimiento correctivo: urgente (no planificable) y no urgente (planificable). ...
El sistema CACTU (Corporación de Asociaciones Comunitarias de Cotopaxi y Tungurahua), diseñado para gestionar la correspondencia entre niños afiliados y sus patrocinadores extranjeros, presentaba problemas operativos críticos. Para resolver esta situación, se identificaron las áreas problemáticas clave y se implementaron soluciones técnicas a través de un mantenimiento correctivo basado en la metodología Ágil MANTEMA. Posteriormente, se evaluó la fiabilidad del sistema conforme a la norma ISO/IEC 25010, utilizando herramientas como JMeter, Enlightn y R. Los resultados de la prueba U de Mann-Whitney revelaron mejoras significativas en los tiempos medios entre fallos, antes y después del mantenimiento. En particular, la fiabilidad del sistema aumentó de manera sustancial, pasando del 34.38% al 88.80%, lo que se tradujo en mejoras notables en la madurez, disponibilidad, tolerancia a fallos y capacidad de recuperación del sistema.
... Initially MoProSoft provided a base for COMPETISOFT which turns out expanded and enhanced. The main improvements were the incorporation of the Software Maintenance agile process [13] ...
The spread of the interest and the need for process reference models, specifically for small and medium software development organizations, has been a catalyst for generating ISO/IEC 29110 Software Engineering — Lifecycle profiles for Very Small Entities. Based on the Mexican standard NMX-I-059-NYCE-2005, better known as MoProSoft, ISO/IEC 29110 is the first international standard specifically designed for very small entities.
Thanks to the COMPETISOFT Project and MoProSoft, the background knowledge and models adoption experience have been introduced in Latin America. In Mexico more than 300 organizations have been evaluated in NMX-I-059-NYCE-2005, in 2009 MoProSoft became a national standard in Peru, while COMPETISOFT included the experience and viewpoints of 13 countries and 23 research groups of the region. As a whole, it gives small software development organizations in the region an advantage in adopting an international standard.
This paper clarifies the gap between ISO/IEC 29110 and MoProSoft level 2. As a result of a theoretical and practical review both standards have been mapped defining the coverage level between processes, considering the defined tasks, work products and roles. Several recommendations have been suggested to bridge the gap between these standards. Finally, the effort needed to adopt the Basic Profile of the new international standard starting from the Mexican standard has been estimated. The results have been extended to also consider organizations that adopted COMPETISOFT as their process reference model.
Competisoft provides the Latin American software industry with a reference framework for improvement and certification of its software processes.The project is based on proven solutions, including the MoProSoft model that four Mexican software companies applied to increase their processes' capacity level.
The maintenance of information systems is one of the greatest
problems in the software life cycle. It is the most conflictive, costly,
less planificable; and the process requiring the most resources. In
spite of this reality, most organizations do not possess methodologies
for software maintenance. These facts, key to the imperative need of
controlling the maintenance process, have carried us to propose a
maintenance methodology. In this paper an adjustment of the ISO/IEC
12207 standard for the processes of life cycle maintenance is presented.
This methodology is being used by Atos ODS, one of the most important
European consultants on software outsourcing and maintenance
SPI in a very small team: a case with CMM. Software Process: Improvement and Practice
- J Batista
- A Figueiredo
Batista, J. and A. Figueiredo, SPI in a very small team: a case with CMM. Software Process:
Improvement and Practice, 2000. Vol. 5(4) December pp. 243-250.
- F Pino
- F Ruiz
- S Salas
Pino, F., F. Ruiz, and S. Salas. Agil_Mantema. COMPETISOFT_IT_2. CYTED. Ciudad Real. 2008.
Disponible en: http://alarcos.inf-cr.uclm.es/competisoft/Agil_MANTEMA_Ver1
(E) Information technology -Process assessment -Part 2: Performing an assessment. International Organization for Standardization
- Iso Iso
ISO. ISO/IEC 15504-2:2003/Cor.1:2004(E). Information technology -Process assessment -Part 2:
Performing an assessment. International Organization for Standardization. Geneva. 2004
Métrica Versión 3. Metodología de Planificación, Desarrollo y Mantenimiento de sistemas de información
MAP. Métrica Versión 3. Metodología de Planificación, Desarrollo y Mantenimiento de sistemas de
información. 2007. http://www.csi.map.es/csi/metrica3/index.html