Adoption of the personas technique in the open source software development process

The growth in the number of non-developer open source software (OSS) application users and the escalating use of these applications have led to the need and interest in developing usable OSS. OSS communities do not generally know how to apply usability techniques and are unclear about which techniques to use in each activity of the development process. The aim of our research is to adopt the Personas usability technique in the PSeInt OSS project and determine the feasibility of adapting the technique for application. To do this, we participated as volunteers in the project. We used the case study research method during technique application and participation in the community. As a result, we identified adverse conditions that were an obstacle to technique application and modified the technique to make it applicable. We can conclude from our experience that these changes were helpful for applying the technique, although it was not easy to recruit OSS users to participate in usability technique applicationThis research has been partly funded by several organizations, including the Government of Ecuador’s Secretariat of Higher Education, Science, Technology and Innovation (SENESCYT) through a scholarship and the State Technical University of Quevedo through doctoral training scholarships for university professors. Also this research was funded by the Spanish Ministry of Education, Culture and Sports FLEXOR and “Realizando Experimentos en la Industria del Software: Comprensión del Paso de Laboratorio a la Realidad” projects (TIN2014-52129-R and TIN2014-60490-P, respectively) and the eMadrid-CM “Investi-gación y Desarrollo de Tecnologías Educativas en la Comunidad de Madrid” project (S2013/ICE-2715

<i>Trace++</i>: A Traceability Approach for Agile Software Engineering

Agile methodologies have been introduced as an alternative to traditional software engineering methodologies. However, despite the advantages of using agile methodologies, the transition between traditional and agile methodologies is not an easy task. There are several problems associated with the use of agile methodologies. Examples of these problems are related to (i) lack of metrics to measure the amount of rework that occurs per sprint, (ii) interruption of a project after several iterations, (iii) changes in the requirements, (iv) lack of documentation, and (v) lack of management control. In this paper we present Trace++, a traceability technique that extends traditional traceability relationships with extra information in order to support the transition between traditional and agile software development. The use of Trace++ has been evaluated in two real projects of different software development companies to measure the benefits of using Trace++ to support agile software development

Adapting usability techniques for application in open source Software: A multiple case study

Context: As a result of the growth of non-developer users of OSS applications, usability has over the last ten years begun to attract the interest of the open source software (OSS) community. The OSS community has some special characteristics (such as worldwide geographical distribution of both users and developers and missing resources) which are an obstacle to the direct adoption of many usability techniques as specified in the human-computer interaction (HCI) field. Objective: The aim of this research is to adapt and evaluate the feasibility of applying four usability techniques: user profiles, personas, direct observation and post-test information to four OSS projects from the viewpoint of the development team. Method: The applied research method was a multiple case study of the following OSS projects: Quite Universal Circuit Simulator, PSeInt, FreeMind and OpenOffice Writer. Results: We formalized the application procedure of each of the adapted usability techniques. We found that either there were no procedures for adopting usability techniques in OSS or they were not fully systematized. Additionally, we identified the adverse conditions that are an obstacle to their adoption in OSS and propose the special adaptations required to overcome the obstacles. To avoid some of the adverse conditions, we created web artefacts (online survey, wiki and forum) that are very popular in the OSS field. Conclusion: It is necessary to adapt usability techniques for application in OSS projects considering their idiosyncrasy. Additionally, we found that there are obstacles (for example, number of participant users, biased information provided by developers) to the application of the techniques. Despite these obstacles, it is feasible to apply the adapted techniques in OSS projectsThis research was funded by the Secretariat of Higher Education, Science, Technology and Innovation (SENESCYT) of the Government of Ecuador as part of an academic scholarship granted for postgradu- ate training, and Quevedo State Technical University through doctoral scholarships for university professors. Also this research was funded by the Spanish Ministry of Education, Culture and Sports FLEXOR ( TIN2014-52129-R ) and TIN2014-60490-P projects and the eMadrid- CM project ( S2013/ICE-2715 ). Finally, this research received funding from the University of Atacama “DIUDA 22316 ”projec

ERP implementation methodologies and frameworks: a literature review

Enterprise Resource Planning (ERP) implementation is a complex and vibrant process, one that involves a combination of technological and organizational interactions. Often an ERP implementation project is the single largest IT project that an organization has ever launched and requires a mutual fit of system and organization. Also the concept of an ERP implementation supporting business processes across many different departments is not a generic, rigid and uniform concept and depends on variety of factors. As a result, the issues addressing the ERP implementation process have been one of the major concerns in industry. Therefore ERP implementation receives attention from practitioners and scholars and both, business as well as academic literature is abundant and not always very conclusive or coherent. However, research on ERP systems so far has been mainly focused on diffusion, use and impact issues. Less attention has been given to the methods used during the configuration and the implementation of ERP systems, even though they are commonly used in practice, they still remain largely unexplored and undocumented in Information Systems research. So, the academic relevance of this research is the contribution to the existing body of scientific knowledge. An annotated brief literature review is done in order to evaluate the current state of the existing academic literature. The purpose is to present a systematic overview of relevant ERP implementation methodologies and frameworks as a desire for achieving a better taxonomy of ERP implementation methodologies. This paper is useful to researchers who are interested in ERP implementation methodologies and frameworks. Results will serve as an input for a classification of the existing ERP implementation methodologies and frameworks. Also, this paper aims also at the professional ERP community involved in the process of ERP implementation by promoting a better understanding of ERP implementation methodologies and frameworks, its variety and history

Alter ego, state of the art on user profiling: an overview of the most relevant organisational and behavioural aspects regarding User Profiling.

This report gives an overview of the most relevant organisational and\ud behavioural aspects regarding user profiling. It discusses not only the\ud most important aims of user profiling from both an organisation’s as\ud well as a user’s perspective, it will also discuss organisational motives\ud and barriers for user profiling and the most important conditions for\ud the success of user profiling. Finally recommendations are made and\ud suggestions for further research are given

Tracing the Scenarios in Scenario-Based Product Design: a study to support scenario generation

Scenario-based design originates from the human-computer interaction and\ud software engineering disciplines, and continues to be adapted for product development. Product development differs from software development in the former’s more varied context of use, broader characteristics of users and more tangible solutions. The possible use of scenarios in product design is therefore broader and more challenging. Existing design methods that involve scenarios can be employed in many different stages of the product design process. However, there is no proficient overview that discusses a\ud scenario-based product design process in its full extent. The purposes of creating scenarios and the evolution of scenarios from their original design data are often not obvious, although the results from using scenarios are clearly visible. Therefore, this paper proposes to classify possible scenario uses with their purpose, characteristics and supporting design methods. The classification makes explicit different types of scenarios and their relation to one another. Furthermore, novel scenario uses can be referred or added to the classification to develop it in parallel with the scenario-based design\ud practice. Eventually, a scenario-based product design process could take inspiration for creating scenarios from the classification because it provides detailed characteristics of the scenario

The Practices of Unpaid Third-Party Developers – Implications for API Design

To draw on the innovation capabilities of third-party developers many organizations are currently deploying open application programming interfaces (API’s). While third-party services may offer commercial opportunities for independent software firms, a large portion of existing third-party software are undertaken without any financial compensation. Although unpaid developers offers a potential source for innovation of end-user services, the current literature has largely overlooked how these unpaid actors use and appropriate the technology provided by organizations. To this end, this research pays specific attention to the specific practices of unpaid developers. The data used for analysis were collected through a programming contest – a hackathon – where unpaid developers gather to craft end-user services. Through an ethnographic lens we present a number of recurrent activities and patterns of action employed by developers and from this analysis we present implications for API designers seeking to attract unpaid developers