Usability-Oriented Software Development Process

Usability is the capability of the software product to be understood, learned, used and attractive to the user, when used under specified conditions. Many studies demonstrate the benefits of usability, yet to this day software products continue to exhibit consistently low levels of this quality attribute. Furthermore, poor usability in software systems contributes largely to software failing in actual use. One of the main disciplines involved in usability is that of Human-Computer Interaction (HCI). Over the past two decades the HCI community has proposed specific features that should be present in applications to improve their usability, yet incorporating them into software continues to be far from trivial for software developers. These difficulties are due to multiple factors, including the high level of abstraction at which these HCI recommendations are made and how far removed they are from actual software implementation. In order to bridge this gap, the Software Engineering community has long proposed software design solutions to help developers include usability features into software, however, the problem remains an open research question. This doctoral thesis addresses the problem of helping software developers include specific usability features into their applications by providing them with a structured and tangible guidance in the form of a process, which we have termed the Usability-Oriented Software Development Process. This process is supported by a set of Software Usability Guidelines that help developers to incorporate a set of eleven usability features with high impact on software design. After developing the Usability-oriented Software Development Process and the Software Usability Guidelines, they have been validated across multiple academic projects and proven to help software developers to include such usability features into their software applications. In doing so, their use significantly reduced development time and improved the quality of the resulting designs of these projects. Furthermore, in this work we propose a software tool to automate the application of the proposed process. In sum, this work contributes to the integration of the Software Engineering and HCI disciplines providing a framework that helps software developers to create usable applications in an efficient way.

Tailoring the Scrum Development Process to Address Agile Product Line Engineering

Software Product Line Engineering (SPLE) is becoming widely used due to the improvement it means when developing software products of the same family. However, SPLE demands long-term investment on a product-line platform that might not be profitable due to rapid changing business settings. Since Agile Software Development (ASD) approaches are being successfully applied in volatile markets, several companies have suggested the idea of integrating SPLE and ASD when a family product has to be developed. Agile Product Line Engineering (APLE) advocates the integration of SPLE and ASD to address their lacks when they are individually applied to software development. A previous literature re-view of experiences and practices on APLE revealed important challenges about how to fully put APLE into practice. Our contribution address several of these challenges by tailoring the agile method Scrum by means of three concepts that we have defined: plastic partial components, working PL-architectures, and reactive reuse.

Introducing usability in a conceptual modeling-based software development process.

Usability plays an important role to satisfy users? needs. There are many recommendations in the HCI literature on how to improve software usability. Our research focuses on such recommendations that affect the system architecture rather than just the interface. However, improving software usability in aspects that affect architecture increases the analyst?s workload and development complexity. This paper proposes a solution based on model-driven development. We propose representing functional usability mechanisms abstractly by means of conceptual primitives. The analyst will use these primitives to incorporate functional usability features at the early stages of the development process. Following the model-driven development paradigm, these features are then automatically transformed into subsequent steps of development, a practice that is hidden from the analyst.

A systematic mapping study on the open source software development process.

Abstract?Background: There is no globally accepted open source software development process to define how open source software is developed in practice. A process description is important for coordinating all the software development activities involving both people and technology. Aim: The research question that this study sets out to answer is: What activities do open source software process models contain? The activity groups on which it focuses are Concept Exploration, Software Requirements, Design, Maintenance and Evaluation. Method: We conduct a systematic mapping study (SMS). A SMS is a form of systematic literature review that aims to identify and classify available research papers concerning a particular issue. Results: We located a total of 29 primary studies, which we categorized by the open source software project that they examine and by activity types (Concept Exploration, Software Requirements, Design, Maintenance and Evaluation). The activities present in most of the open source software development processes were Execute Tests and Conduct Reviews, which belong to the Evaluation activities group. Maintenance is the only group that has primary studies addressing all the activities that it contains. Conclusions: The primary studies located by the SMS are the starting point for analyzing the open source software development process and proposing a process model for this community. The papers in our paper pool that describe a specific open source software project provide more regarding our research question than the papers that talk about open source software development without referring to a specific open source software project.

Guidance for the development of accessibility evaluation tools following the Unified Software Development Process

Automated and semi-automated accessibility evaluation tools are key to streamline the process of accessibility assessment, and ultimately ensure that software products, contents, and services meet accessibility requirements. Different evaluation tools may better fit different needs and concerns, accounting for a variety of corporate and external policies, content types, invocation methods, deployment contexts, exploitation models, intended audiences and goals; and the specific overall process where they are introduced. This has led to the proliferation of many evaluation tools tailored to specific contexts. However, tool creators, who may be not familiar with the realm of accessibility and may be part of a larger project, lack any systematic guidance when facing the implementation of accessibility evaluation functionalities. Herein we present a systematic approach to the development of accessibility evaluation tools, leveraging the different artifacts and activities of a standardized development process model (the Unified Software Development Process), and providing templates of these artifacts tailored to accessibility evaluation tools. The work presented specially considers the work in progress in this area by the W3C/WAI Evaluation and Report Working Group (ERT WG)

Evaluation of Development Projects: a Process-Centered Approach in the Outskirts of Lima, Peru.

Development cooperation projects work with people involved in processes of change and social transformation. While the main objective of the intervention is the development process itself, the project?s quality will be determined by the way of implementing it. Its success lies in the sustainability of the generated processes and the connection with them by the involved actors. The evaluation analyses both aspects. This article examines the evaluation, under a process approach, of a project on urban agriculture in Lima (Peru). The results show that the use of this approach, which combines different evaluation tools, allows the identification and analysis of the processes with the involved members, providing a better understanding of the real sustainability of the results.

Social involvement for community development in rural areas of Cuenca, Spain

Community development must be accompanied by a social involvement process which creates functional groups of citizens capable of taking responsibility for their own development. It is important that this process promotes the structuring of all population groups and provides the appropriate institutional and technical support. The present paper addresses these issues based on over 25 years of experience by the Association Instituto de Desarrollo Comunitario de Cuenca in revitalizing rural areas of the Spanish province of Cuenca. This paper analyses the social involvement process encouraged by this association, the relationships between public institutions and local associations, the role of these associations and the difficulties encountered in the rural areas. The long-term perspective of this experience provides some keys which can be used to successfully support the process of social involvement ―such as information on its characteristics and methodological tools―, establish local associations and create sustainable partnerships that foster the growth of leadership within the community development process.

Information as a Key Tool for Rural Development. 25 Years of Experience in Spain

The lack of useful information has become a major obstacle that hinders the participation of the members of the community in the development process because they can not accurately perceive how their individual and/or collective action can influence their environment, and because of the lack of elements that support the decision-making processes. This article addresses these issues from the work carried out by the Association Instituto de Desarrollo Comunitario de Cuenca (IDC Cuenca) in the rural areas of this province of Spain for 25 years. The results show how the application of methodologies for the transmission of information tailored to each group of recipients in some aspects, enhances the participation of individuals.

Including functional usability features in a Model-Driven Development Method

The Software Engineering (SE) community has historically focused on working with models to represent functionality and persistence, pushing interaction modelling into the background, which has been covered by the Human Computer Interaction (HCI) community. Recently, adequately modelling interaction, and specifically usability, is being considered as a key factor for success in user acceptance, making the integration of the SE and HCI communities more necessary. If we focus on the Model-Driven Development (MDD) paradigm, we notice that there is a lack of proposals to deal with usability features from the very first steps of software development process. In general, usability features are manually implemented once the code has been generated from models. This contradicts the MDD paradigm, which claims that all the analysts? effort must be focused on building models, and the code generation is relegated to model to code transformations. Moreover, usability features related to functionality may involve important changes in the system architecture if they are not considered from the early steps. We state that these usability features related to functionality can be represented abstractly in a conceptual model, and their implementation can be carried out automatically.

Communication Project for development: 25 years of experience in andean rural communities in Ecuador

IThis paper analyses communication for development from a new perspective: the project in its broader and most genuine sense, as an instrument for changing current reality. This is examined from both its theoretical and practical implementation side. Knowledge/action binomial as a two-way relationship is one of the basis of the project cycle. It allows for better knowing the reality that the project itself (what constitutes the action) is intended to improve. Besides that, this knowledge/action binomial also offers new knowledge that nourishes future actions (projects). From a project based communication perspective, the project nourishes the knowledge, which leads to a transformative action. Reflecting about the action is a new knowledge source whose adoption by the community is eased by the communication process. Radio Mensaje project among the indigenous Andean communities in Cayambe (Ecuador) was born and also developed within this approach, supporting the collaborative participation in project management. This leads to the development process which is described in this case study.

Application of user-centered design in the development of an atomated/assisted testing system for self-service devices

Automated Teller Machines (ATMs) are sensitive self-service systems that require important investments in security and testing. ATM certifications are testing processes for machines that integrate software components from different vendors and are performed before their deployment for public use. This project was originated from the need of optimization of the certification process in an ATM manufacturing company. The process identifies compatibility problems between software components through testing. It is composed by a huge number of manual user tasks that makes the process very expensive and error-prone. Moreover, it is not possible to fully automate the process as it requires human intervention for manipulating ATM peripherals. This project presented important challenges for the development team. First, this is a critical process, as all the ATM operations rely on the software under test. Second, the context of use of ATMs applications is vastly different from ordinary software. Third, ATMs’ useful lifetime is beyond 15 years and both new and old models need to be supported. Fourth, the know-how for efficient testing depends on each specialist and it is not explicitly documented. Fifth, the huge number of tests and their importance implies the need for user efficiency and accuracy. All these factors led us conclude that besides the technical challenges, the usability of the intended software solution was critical for the project success. This business context is the motivation of this Master Thesis project. Our proposal focused in the development process applied. By combining user-centered design (UCD) with agile development we ensured both the high priority of usability and the early mitigation of software development risks caused by all the technology constraints. We performed 23 development iterations and finally we were able to provide a working solution on time according to users’ expectations. The evaluation of the project was carried out through usability tests, where 4 real users participated in different tests in the real context of use. The results were positive, according to different metrics: error rate, efficiency, effectiveness, and user satisfaction. We discuss the problems found, the benefits and the lessons learned in the process. Finally, we measured the expected project benefits by comparing the effort required by the current and the new process (once the new software tool is adopted). The savings corresponded to 40% less effort (man-hours) per certification. Future work includes additional evaluation of product usability in a real scenario (with customers) and the measuring of benefits in terms of quality improvement.

La Práctica del Desarrollo Local: Veinticinco Años de Experiencia del Instituto de Desarrollo Comunitario de Cuenca en Territorios Rurales

La investigación tiene como objetivo principal analizar la experiencia de la Asociación Instituto de Desarrollo Comunitario de Cuenca, en la práctica del desarrollo local en los territorios rurales de esta provincia. La necesidad de estimular a la población para que ésta forme parte de su propio desarrollo, pone de manifiesto la existencia de determinadas instituciones externas que a través de procesos como la facilitación, movilizan y crean capacidades en las personas y las empujan hacia la participación. Este es el caso del IDC de Cuenca que nace en 1985 como entidad privada —declarada de utilidad pública y sin ánimo de lucro—, con la voluntad de sus fundadores de trabajar en el desarrollo local de las zonas deprimidas de Cuenca. La labor desarrollada en estos más de 25 años tiene como centro la promoción de la persona como ser individual y como parte de su comunidad. Para la elaboración de la Tesis, se ha utilizado la metodología del caso de estudio centrado en el análisis de la experiencia del IDC respecto de las cuatro investigaciones realizadas centradas en el proceso de facilitación, las herramientas de formación e información, y la dinamización del tejido asociativo como resultado del proceso. La labor del IDC en la provincia de Cuenca se ha desarrollado a través de la ejecución de proyectos. Éstos se han llevado a cabo por medio de procesos de facilitación donde la creación de grupos de trabajo ha permitido mejorar la estructuración social de las zonas rurales. Los grupos de trabajo son creados y apoyados por el IDC a través de la utilización de las herramientas de información y formación, que deben estar adaptadas a las necesidades de los individuos y en este caso cuentan con una metodología de aplicación propia. La creación de diferentes entidades —asociaciones, cooperativas, clubes, etc.—, ha sido uno de los resultados del trabajo desarrollado por el IDC a través de los procesos de facilitación que han mejorado la estructuración de la sociedad rural. Pese a la complejidad tanto de los procesos de desarrollo como de la evaluación final de dichos procesos, la creación de grupos capaces de alcanzar determinados objetivos propuestos en su comunidad potenciando sus propios recursos, son el ejemplo de la dinamización social que se lleva produciendo en la provincia de Cuenca desde hace más de 25 años. The research's main objective is to analyze the experience of the Asociación Instituto de Desarrollo Comunitario de Cuenca, in the practice of local development in rural areas of this province. The need to encourage more people to take part of their own development, reveals the existence of certain external institutions which through processes such as facilitation, mobilize and create capacities in people to foster their participation. This is the case of the IDC of Cuenca that was born in 1985 as a private entity —declared of public utility and as non profit entity— with the intention, as stated by its founders, of working in the local development of the disadvantaged areas of Cuenca. The work carried out in these more than 25 years focused on promoting the person as an individual and as part of their community. In this research, the methodology of the case study has been used in the analysis of the experience of the IDC in four investigations carried out regarding the process of facilitation, training and information tools, and the improvement of social involvement as a result of the development process. The work of the IDC in the province of Cuenca has been developed through the implementation of projects. They have been carried out through processes of facilitation, where the creation of working groups has improved the social structuring of rural areas. The working groups are created and supported by the IDC through the use of tools of information and training, which must be adapted to the individual needs in each case, and even count with their own implementation methodology. The creation of different entities —associations, cooperatives, clubs, etc.— has been one of the results of the work carried out by the IDC through processes of facilitation which have improved the structure of rural society. Despite the complexity of development processes and the final assessment of these processes, the creation of groups able to reach certain objectives proposed in their community promoting its own resources, is an example of the social involvement that has been taking place in the province of Cuenca for more than 25 years.

Essentials in Ontology Engineering: Methodologies, Languages, and Tools

In the beginning of the 90s, ontology development was similar to an art: ontology developers did not have clear guidelines on how to build ontologies but only some design criteria to be followed. Work on principles, methods and methodologies, together with supporting technologies and languages, made ontology development become an engineering discipline, the so-called Ontology Engineering. Ontology Engineering refers to the set of activities that concern the ontology development process and the ontology life cycle, the methods and methodologies for building ontologies, and the tool suites and languages that support them. Thanks to the work done in the Ontology Engineering field, the development of ontologies within and between teams has increased and improved, as well as the possibility of reusing ontologies in other developments and in final applications. Currently, ontologies are widely used in (a) Knowledge Engineering, Artificial Intelligence and Computer Science, (b) applications related to knowledge management, natural language processing, e-commerce, intelligent information integration, information retrieval, database design and integration, bio-informatics, education, and (c) the Semantic Web, the Semantic Grid, and the Linked Data initiative. In this paper, we provide an overview of Ontology Engineering, mentioning the most outstanding and used methodologies, languages, and tools for building ontologies. In addition, we include some words on how all these elements can be used in the Linked Data initiative.

An extended approach for service innovation study: an empirical research

Initially, service sector was defined as complementary to manufacturing sector. This situation has changed in recent times; services growth has resulted in a dominance of employment and economic activity in most developed nations and is becoming a key process for the competitiveness of their industrial sectors. New services related to commodities have become a strategy to differentiate their value proposition (Robinson et al., 2002). The service sector's importance is evident when evaluating its share in the gross domestic product. According to the World Bank (2011), in 2009, 74.8% of GDP in the euro area and 77.5% in United States were attributed to services. Globalization and use of information and communication technology has accelerated dissemination of knowledge and increasing customer expectations about services available worldwide. Innovation becomes essential to ensure that service organizations respond with appropriate products and services for each market segment. Customized and placed on time-tomarket new services require a more developed innovation process. Service innovation and new service development process are cited as one of the priorities for academic research in the following years (Karniouchina et al., 2005) This paper has the following objectives: -To present a model for the analysis of innovation process through the service value network, -To verify its applicability through an empirical research, and -To identify the path and mode of innovation for a group of studied organizations and to compare it with previous studies.

Agile Construction and Evolution of Product-Line Architectures

Software Product Line Engineering (SPLE) has proved to have significant advantages in family-based software development, but also implies the up¬front design of a product-line architecture (PLA) from which individual product applications can be engineered. The big upfront design associated with PLAs is in conflict with the current need of "being open to change". However, the turbulence of the current business climate makes change inevitable in order to stay competitive, and requires PLAs to be open to change even late in the development. The trend of "being open to change" is manifested in the Agile Software Development (ASD) paradigm, but it is spreading to the domain of SPLE. To reduce the big upfront design of PLAs as currently practiced in SPLE, new paradigms are being created, one being Agile Product Line Engineering (APLE). APLE aims to make the development of product-lines more flexible and adaptable to changes as promoted in ASD. To put APLE into practice it is necessary to make mechanisms available to assist and guide the agile construction and evolution of PLAs while complying with the "be open to change" agile principle. This thesis defines a process for "the agile construction and evolution of product-line architectures", which we refer to as Agile Product-Line Archi-tecting (APLA). The APLA process provides agile architects with a set of models for describing, documenting and tracing PLAs, as well as an algorithm to analyze change impact. Both the models and the change impact analysis offer the following capabilities: Flexibility & adaptability at the time of defining software architectures, enabling change during the incremental and iterative design of PLAs (anticipated or planned changes) and their evolution (unanticipated or unforeseen changes). Assistance in checking architectural integrity through change impact analysis in terms of architectural concerns, such as dependencies on earlier design decisions, rationale, constraints, and risks, etc.Guidance in the change decision-making process through change im¬pact analysis in terms of architectural components and connections. Therefore, APLA provides the mechanisms required to construct and evolve PLAs that can easily be refined iteration after iteration during the APLE development process. These mechanisms are provided in a modeling frame¬work called FPLA. The contributions of this thesis have been validated through the conduction of a project regarding a metering management system in electrical power networks. This case study took place in an i-smart software factory and was in collaboration with the Technical University of Madrid and Indra Software Labs. La Ingeniería de Líneas de Producto Software (Software Product Line Engi¬neering, SPLE) ha demostrado tener ventajas significativas en el desarrollo de software basado en familias de productos. SPLE es un paradigma que se basa en la reutilización sistemática de un conjunto de características comunes que comparten los productos de un mismo dominio o familia, y la personalización masiva a través de una variabilidad bien definida que diferencia unos productos de otros. Este tipo de desarrollo requiere el diseño inicial de una arquitectura de línea de productos (Product-Line Architecture, PLA) a partir de la cual los productos individuales de la familia son diseñados e implementados. La inversión inicial que hay que realizar en el diseño de PLAs entra en conflicto con la necesidad actual de estar continuamente "abierto al cam¬bio", siendo este cambio cada vez más frecuente y radical en la industria software. Para ser competitivos es inevitable adaptarse al cambio, incluso en las últimas etapas del desarrollo de productos software. Esta tendencia se manifiesta de forma especial en el paradigma de Desarrollo Ágil de Software (Agile Software Development, ASD) y se está extendiendo también al ámbito de SPLE. Con el objetivo de reducir la inversión inicial en el diseño de PLAs en la manera en que se plantea en SPLE, en los último años han surgido nuevos enfoques como la Ingeniera de Líneas de Producto Software Ágiles (Agile Product Line Engineering, APLE). APLE propone el desarrollo de líneas de producto de forma más flexible y adaptable a los cambios, iterativa e incremental. Para ello, es necesario disponer de mecanismos que ayuden y guíen a los arquitectos de líneas de producto en el diseño y evolución ágil de PLAs, mientras se cumple con el principio ágil de estar abierto al cambio. Esta tesis define un proceso para la "construcción y evolución ágil de las arquitecturas de lineas de producto software". A este proceso se le ha denominado Agile Product-Line Architecting (APLA). El proceso APLA proporciona a los arquitectos software un conjunto de modelos para de¬scribir, documentar y trazar PLAs, así como un algoritmo para analizar vel impacto del cambio. Los modelos y el análisis del impacto del cambio ofrecen: Flexibilidad y adaptabilidad a la hora de definir las arquitecturas software, facilitando el cambio durante el diseño incremental e iterativo de PLAs (cambios esperados o previstos) y su evolución (cambios no previstos). Asistencia en la verificación de la integridad arquitectónica mediante el análisis de impacto de los cambios en términos de dependencias entre decisiones de diseño, justificación de las decisiones de diseño, limitaciones, riesgos, etc. Orientación en la toma de decisiones derivadas del cambio mediante el análisis de impacto de los cambios en términos de componentes y conexiones. De esta manera, APLA se presenta como una solución para la construcción y evolución de PLAs de forma que puedan ser fácilmente refinadas iteración tras iteración de un ciclo de vida de líneas de producto ágiles. Dicha solución se ha implementado en una herramienta llamada FPLA (Flexible Product-Line Architecture) y ha sido validada mediante su aplicación en un proyecto de desarrollo de un sistema de gestión de medición en redes de energía eléctrica. Dicho proyecto ha sido desarrollado en una fábrica de software global en colaboración con la Universidad Politécnica de Madrid e Indra Software Labs.