Agile, Web Engineering and Capability Maturity ModelI ntegration : A systematic literature review

Context Agile approaches are an alternative for organizations developing software, particularly for those who develop Web applications. Besides, CMMI (Capability Maturity Model Integration) models are well-established approaches focused on assessing the maturity of an organization that develops software. Web Engineering is the field of Software Engineering responsible for analyzing and studying the specific characteristics of the Web. The suitability of an Agile approach to help organizations reach a certain CMMI maturity level in Web environments will be very interesting, as they will be able to keep the ability to quickly react and adapt to changes as long as their development processes get mature. Objective This paper responds to whether it is feasible or not, for an organization developing Web systems, to achieve a certain maturity level of the CMMI-DEV model using Agile methods. Method The proposal is analyzed by means of a systematic literature review of the relevant approaches in the field, defining a characterization schema in order to compare them to introduce the current state-of-the-art. Results The results achieved after the systematic literature review are presented, analyzed and compared against the defined schema, extracting relevant conclusions for the different dimensions of the problem: compatibility, compliance, experience, maturity and Web. Conclusion It is concluded that although the definition of an Agile approach to meet the different CMMI maturity levels goals could be possible for an organization developing Web systems, there is still a lack of detailed studies and analysis on the field

Issues with Incorporating Regulatory Compliance into Agile Development: A Critical Analysis

Agile development methodology is widely used for software development in organizations. Incorporating regulatory compliance aspects in development process is important. This paper discusses various issues in considering compliance aspects into development process. An analysis of different aspects of compliance related issues is presented

Using Agile Software Development Practices in a Research Oriented Distributed Simulation

Although sometimes controversial, agile methodologies have proven to be a viable choice for some software development projects. Projects suited to agile methodologies are those that involve new technology, have requirements that change rapidly, and are controlled by small, talented teams. Much literature about agile software development leans towards business products and non-government entities. Only a handful of literature resources mention agile software development being used in government contracts and even fewer resources mention research projects. NASA\u27s Airspace and Traffic Operations Simulation (ATOS) is a research oriented simulation that doesn\u27t follow the traditional business project mold. In an effort to gain a better understanding if agile could be used effectively in a NASA contract for a research oriented simulation project, this research looked at what agile practices could be effectively used to help gain simulation reliability while simultaneously allowing routine maintenance, current experiment support, new modeling additions, and comprehensive architectural changes

Capability Maturity Model Integration (Cmmi) for Small Organizations

Software Process Improvement (SPI) is a large area of expertise that deals with software development standard processes and is a progression of proven methods of process improvement from many different methodologies. Personal Software Process (PSP) and Team Software Process (TSP) complement the implementation of Capability Maturity Model Implementation (CMMI) and can be applied gradually from the individual, to the team, and then to the organization. These solutions from Carnegie Melon\u27s Software Engineering Institute (SEI) are leading edge for the field of process improvement. Solutions like this consume many resources, are very complex, require years to implement, and can be costly. The SEI solutions offer an industry standard for SPI. Three case studies were analyzed to provide insight into the benefits of CMMI for small organizations. Decisions that steer these solutions generally involve scheduling, quality, and cost. Depending on the individual needs of an organization, the CMMI technology can fulfill what is required. The example case studies were examined and concluded that given favorable conditions, implementing CMMI is feasible for small organizations

The influence of managerial experience and style on software development process

This paper presents the results of a study of how software process and software process improvement is applied in actual practice in the software industry using the indigenous Irish software product industry as a test-bed. This study focuses on the role and influence of both the Company Founder and the Software Development Manager on the initial formation of software development process practices. The results of this study contain useful lessons for software entrepreneurs who need to make decisions about process and process change within their organisations as they grow

Quality model for software development pymes located in the valle de Aburrá metropolitan area

Modelo de calidad para pymes desarrolladoras de software ubicadas en el área metropolitana del valle de AburráMediante este artículo se desea mostrar el proyecto de investigación (Modelo de Calidad para PYMES Desarrolladoras de Software ubicadas en el Área Metropolitana del Valle de Aburra) se presenta un Modelo de Calidad que busca servir de apoyo a las Pymes desarrolladoras de software del Área Metropolitana del Valle de Aburra. Para su creación se realizó un análisis de modelos importantes como: MoProSoft, TST/PSP, Mosca, CMI, CMMI, de los cuales se toman como base las mejores prácticas. De igual manera se analiza conceptos importantes como Modelos de Calidad, Gestión de Procesos, Metodologías de Desarrollo, Gestión de proyectos. Este modelo de calidad busca servir de base a las pequeñas empresas, creando apoyo a los equipos desarrolladores de software mejorando su rendimiento y efectividad en la elaboración de los proyectos.AbstractThe purpose of this article is to showcase a research project (Quality Model for Software Development Pymes Located in the Aburrá Valley Metropolitan Area), and to present the resulting Quality Model, intended to support PYMES that develop software and are located in the Aburrá Valley Metropolitan Area. Many important models were analyzed for its development, such as MoProSoft, TST/PSP, Mosca, CMI, CMMI, from which the best practices were extracted. Additionally, important concepts were taken into account, such as Quality Models, Process Management, Development Processes, and Project Management. This quality model aims serve as a basis for small companies by supporting their software development teams, improving their performance and effectiveness in project elaboration.Keywords: Software, Software Development Process, Quality Models, Software Qualit

The Main and Interaction Effects of Process Rigor, Process Standardization, and Process Agility on System Performance in Distributed IS Development: An Ambidexterity Perspective

Information systems (IS) development is becoming increasingly more geographically dispersed. Although process rigor, process standardization, and process agility are generally believed to have a positive impact on software development, it has not been well understood how these process capabilities affect distributed IS development. More important, no prior research has investigated their interaction effects. Drawing upon prior literature on organizational ambidexterity, we hypothesize: positive main effects of process rigor, process standardization, and process agility; a positive interaction effect of process rigor and process agility; and a positive interaction effect of process standardization and process agility on system performance in distributed development. Our data analysis results support a positive main effect of the three process capabilities. We find a positive interaction effect of process rigor and process agility suggesting positive process ambidexterity of rigor and agility. Surprisingly, we find a negative interaction effect of process agility and process standardization suggesting negative process ambidexterity of agility and standardizatio

Comparative Analysis of Methodological Trends in the Management of Software Projects: Identification of the Main Variables

Nowadays, there are many methodological proposals that support the various aspects of software development projects. In general terms, there are two big identifiable trends: traditional and agile. In the first instance, traditional methods are those characterized by privileging detailed planning work to ensure the quality of the final product. On the other hand, agile methodologies put prediction aside and open a space to changes in planning. This article presents the results obtained from the application of a comparative analysis to 12 methodologies for software projects management, and from 149 software development companies surveyed, leading to identify, from a theoretical - experimental model, the variables that generate the greatest impact on the success of this type of projects. The importance of studying this topic resided in the impact that the correct application of a management methodology has on the results of a project and thus on its success. Regardless of the methodology used, they all propose a series of common processes, considered good practices, which allow achieving the outlined goals