Web development productivity improvement through object-oriented application framework

Most of the commercial and industrial web applications are complex, difficult to implement, risky to maintain and requires deep understanding of the requirements for customization. As today's software market is more competitive, productivity has become a major concern in software development industry. The aim of this research is to design and develop an application framework for accelerating web development productivity through object-oriented technology. It allows customization, design reuse and automatic code generation to support productivity improvement as a breakthrough solution for the given problem. This research employed systematic literature review (SLR) to identify the source of complexity and productivity factors. Agile development methodology was used to design the framework and it was validated by empirical data from two commercial projects. Results showed that object-oriented application framework (OOAF) has significant factors that affect productivity and dramatically improve higher productivity over traditional approach. It has fulfilled the current needs by reducing complexities, development efforts and accelerates web development productivity. This research contributes in the area of software engineering, specifically in the field of software productivity improvement and software customization. These will lead to faster development time for software industries

The business value of agile software development: Results from a systematic literature review

A key promise of agile software development (ASD) is to deliver business value. While research and practice indeed report multiple benefits resulting from the adoption of ASD methodologies, the bandwidth of the achievable business values is not well understood yet. To clarify the concept of ASD business value and provide a systematic perspective on its multidimensional nature, we present the results of a literature review, in which we investigated the attainable benefits when adopting ASD methodologies. The contribution of the paper is twofold. First, we provide a systematic overview of 43 distinct ASD business values, which includes prominent values such as increased productivity and less regarded values, for example improved business IT alignment. Using a conceptual lens based on Chow and Cao (2008), we furthermore relate the identified business values to the factors determining the success of ASD projects, thus proposing a novel model to explain ASD success

A systematic mapping study of API usability evaluation methods

An Application Programming Interface (API) provides a programmatic interface to a software component that is often offered publicly and may be used by programmers who are not the API’s original designers. APIs play a key role in software reuse. By reusing high quality components and services, developers can increase their productivity and avoid costly defects. The usability of an API is a qualitative characteristic that evaluates how easy it is to use an API. Recent years have seen a considerable increase in research efforts aiming at evaluating the usability of APIs. An API usability evaluation can identify problem areas and provide recommendations for improving the API. In this systematic mapping study, we focus on 47 primary studies to identify the aim and the method of the API usability studies. We investigate which API usability factors are evaluated, at which phases of API development is the usability of API evaluated and what are the current limitations and open issues in API usability evaluation. We believe that the results of this literature review would be useful for both researchers and industry practitioners interested in investigating the usability of API and new API usability evaluation methods

Technical Debt Prioritization: State of the Art. A Systematic Literature Review

Background. Software companies need to manage and refactor Technical Debt issues. Therefore, it is necessary to understand if and when refactoring Technical Debt should be prioritized with respect to developing features or fixing bugs. Objective. The goal of this study is to investigate the existing body of knowledge in software engineering to understand what Technical Debt prioritization approaches have been proposed in research and industry. Method. We conducted a Systematic Literature Review among 384 unique papers published until 2018, following a consolidated methodology applied in Software Engineering. We included 38 primary studies. Results. Different approaches have been proposed for Technical Debt prioritization, all having different goals and optimizing on different criteria. The proposed measures capture only a small part of the plethora of factors used to prioritize Technical Debt qualitatively in practice. We report an impact map of such factors. However, there is a lack of empirical and validated set of tools. Conclusion. We observed that technical Debt prioritization research is preliminary and there is no consensus on what are the important factors and how to measure them. Consequently, we cannot consider current research conclusive and in this paper, we outline different directions for necessary future investigations

Software Reuse in Agile Development Organizations - A Conceptual Management Tool

The reuse of knowledge is considered a major factor for increasing productivity and quality. In the software industry knowledge is embodied in software assets such as code components, functional designs and test cases. This kind of knowledge reuse is also referred to as software reuse. Although the benefits can be substantial, software reuse has never reached its full potential. Organizations are not aware of the different levels of reuse or do not know how to address reuse issues. This paper proposes a conceptual management tool for supporting software reuse. Furthermore the paper presents the findings of the application of the management tool in an agile development organization

Synthesizing diverse evidence: the use of primary qualitative data analysis methods and logic models in public health reviews

Objectives: The nature of public health evidence presents challenges for conventional systematic review processes, with increasing recognition of the need to include a broader range of work including observational studies and qualitative research, yet with methods to combine diverse sources remaining underdeveloped. The objective of this paper is to report the application of a new approach for review of evidence in the public health sphere. The method enables a diverse range of evidence types to be synthesized in order to examine potential relationships between a public health environment and outcomes. Study design: The study drew on previous work by the National Institute for Health and Clinical Excellence on conceptual frameworks. It applied and further extended this work to the synthesis of evidence relating to one particular public health area: the enhancement of employee mental well-being in the workplace. Methods: The approach utilized thematic analysis techniques from primary research, together with conceptual modelling, to explore potential relationships between factors and outcomes. Results: The method enabled a logic framework to be built from a diverse document set that illustrates how elements and associations between elements may impact on the well-being of employees. Conclusions: Whilst recognizing potential criticisms of the approach, it is suggested that logic models can be a useful way of examining the complexity of relationships between factors and outcomes in public health, and of highlighting potential areas for interventions and further research. The use of techniques from primary qualitative research may also be helpful in synthesizing diverse document types. (C) 2010 The Royal Society for Public Health. Published by Elsevier Ltd. All rights reserved

Definition of the on-time delivery indicator in rapid software development

Rapid software development (RSD) is an approach for developing software in rapid iterations. One of the critical success factors of an RSD project is to deliver the product releases on time and with the planned features. In this paper, we elaborate an exploratory definition of the On-Time Delivery strategic indicator in RSD based on the literature and interviews with four companies. This indicator supports decision-makers to detect development problems in order to avoid delays and to estimate the additional time needed when requirements, and specifically quality requirements, are considered.Peer ReviewedPostprint (author's final draft