11,515 research outputs found
Recommended from our members
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
Designing and evaluating the usability of a machine learning API for rapid prototyping music technology
To better support creative software developers and music technologists' needs, and to empower them as machine learning users and innovators, the usability of and developer experience with machine learning tools must be considered and better understood. We review background research on the design and evaluation of application programming interfaces (APIs), with a focus on the domain of machine learning for music technology software development. We present the design rationale for the RAPID-MIX API, an easy-to-use API for rapid prototyping with interactive machine learning, and a usability evaluation study with software developers of music technology. A cognitive dimensions questionnaire was designed and delivered to a group of 12 participants who used the RAPID-MIX API in their software projects, including people who developed systems for personal use and professionals developing software products for music and creative technology companies. The results from the questionnaire indicate that participants found the RAPID-MIX API a machine learning API which is easy to learn and use, fun, and good for rapid prototyping with interactive machine learning. Based on these findings, we present an analysis and characterization of the RAPID-MIX API based on the cognitive dimensions framework, and discuss its design trade-offs and usability issues. We use these insights and our design experience to provide design recommendations for ML APIs for rapid prototyping of music technology. We conclude with a summary of the main insights, a discussion of the merits and challenges of the application of the CDs framework to the evaluation of machine learning APIs, and directions to future work which our research deems valuable
Identifying Agile Requirements Engineering Patterns in Industry
Agile Software Development (ASD) is gaining in popularity in today´s business world. Industry is adopting agile methodologies both to accelerate value delivery and to enhance the ability to deal with changing requirements. However, ASD has a great impact on how Requirements Engineering (RE) is carried out in agile environments. The integration of Human-Centered Design (HCD) plays an important role due to the focus on user and stakeholder involvement. To this end, we aim to introduce agile RE patterns as main objective of this paper. On the one hand, we will describe our pattern mining process based on empirical research in literature and industry. On the other hand, we will discuss our results and provide two examples of agile RE patterns. In sum, the pattern mining process identifies 41 agile RE patterns. The accumulated knowledge will be shared by means of a web application.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2-RMinisterio de Economía y Competitividad TIN2015-71938-RED
Decision-focussed resource modelling for design decision support
Resource management including resource allocation, levelling, configuration and monitoring has been recognised as critical to design decision making. It has received increasing research interests in recent years. Different definitions, models and systems have been developed and published in literature. One common issue with existing research is that the resource modelling has focussed on the information view of resources. A few acknowledged the importance of resource capability to design management, but none has addressed the evaluation analysis of resource fitness to effectively support design decisions. This paper proposes a decision-focused resource model framework that addresses the combination of resource evaluation with resource information from multiple perspectives. A resource management system constructed on the resource model framework can provide functions for design engineers to efficiently search and retrieve the best fit resources (based on the evaluation results) to meet decision requirements. Thus, the system has the potential to provide improved decision making performance compared with existing resource management systems
State of the Practice in Application Programming Interfaces (APIs): A Case Study
Application Programming Interfaces (APIs) have become prevalent in today’s software systems and services. APIs are basically a technical means to realize the co-operation between software systems or services. While there are several guidelines for API development, the actually applied practices and challenges are less clear. To better understand the state of the practice of API development and management in the industry, we conducted a descriptive case study in four Finnish software companies: two consultancy companies developing software for their customers, and two companies developing their software products. As a result, we identified five different usage scenarios for APIs and emphasize that diversity of usage should be taken into account more explicitly especially in research. API development and technical management are well supported by the existing tools and technologies especially available from the cloud technology. This leaves as the main challenge the selection of the right technology from the existing technology stack. Documentation and usability are practical issues to be considered and often less rigorously addressed. However, understanding what kind of API management model to apply for the business context appears as the major challenge. We also suggest considering APIs more clearly a separate concern in the product management with specific practices, such as API roadmapping.Peer reviewe
Infectious diseases management framework for Saudi Arabia (SAIF)
A Thesis Submitted to the University of Bedfordshire in partial fulfilment of the requirements for the degree of Doctor of PhilosopyInfectious disease management system area is considered as an emerging field of modern healthcare in the Gulf region. Significant technical and clinical progress and advanced technologies can be utilized to enhance the performance and ubiquity of such systems. Effective infectious disease management (IDM) can be achieved by analysing the disease management issues from the perspectives of healthcare personnel and patients. Hence, it is necessary to identify the needs and requirements of both healthcare personnel and patients for managing the infectious disease. The basic idea behind the proposed mobile IDM system in this thesis is to improve the healthcare processes in managing infectious diseases more effectively. For this purpose, internet and mobile technologies are integrated with social networking, mapping and IDM applications to improve the processes efficiency. Hence, the patients submit their health related data through their devices remotely using our application to our system database (so-called SAIF).
The main objective of this PhD project was the design and development of a novel web based architecture of next-generation infectious disease management system embedding the concept of social networking tailored for Saudi patients. Following a detailed literature review which identifies the current status and potential impact of using infectious diseases management system in KSA, this thesis conducts a feasibility user perspective study for identifying the needs and the requirements of healthcare personnel and the patients for managing infectious diseases. Moreover, this thesis proposes a design and development of a novel architecture of next-generation web based infectious disease management system tailored for Saudi patients (i.e., called SAIF – infectious diseases management framework for Saudi Arabia). Further, this thesis introduces a usability study for the SAIF system to validate the acceptability of using mobile technologies amongst infected patient in KSA and Gulf region. The preliminary results of the study indicated general acceptance of the patients in using the system with higher usability rating in high affected patients. In general, the study concluded that the concept of SAIF system is considered acceptable tool in particularly with infected patients
Neuroimaging study designs, computational analyses and data provenance using the LONI pipeline.
Modern computational neuroscience employs diverse software tools and multidisciplinary expertise to analyze heterogeneous brain data. The classical problems of gathering meaningful data, fitting specific models, and discovering appropriate analysis and visualization tools give way to a new class of computational challenges--management of large and incongruous data, integration and interoperability of computational resources, and data provenance. We designed, implemented and validated a new paradigm for addressing these challenges in the neuroimaging field. Our solution is based on the LONI Pipeline environment [3], [4], a graphical workflow environment for constructing and executing complex data processing protocols. We developed study-design, database and visual language programming functionalities within the LONI Pipeline that enable the construction of complete, elaborate and robust graphical workflows for analyzing neuroimaging and other data. These workflows facilitate open sharing and communication of data and metadata, concrete processing protocols, result validation, and study replication among different investigators and research groups. The LONI Pipeline features include distributed grid-enabled infrastructure, virtualized execution environment, efficient integration, data provenance, validation and distribution of new computational tools, automated data format conversion, and an intuitive graphical user interface. We demonstrate the new LONI Pipeline features using large scale neuroimaging studies based on data from the International Consortium for Brain Mapping [5] and the Alzheimer's Disease Neuroimaging Initiative [6]. User guides, forums, instructions and downloads of the LONI Pipeline environment are available at http://pipeline.loni.ucla.edu
Requirements of API Documentation: A Case Study into Computer Vision Services
Using cloud-based computer vision services is gaining traction, where
developers access AI-powered components through familiar RESTful APIs, not
needing to orchestrate large training and inference infrastructures or
curate/label training datasets. However, while these APIs seem familiar to use,
their non-deterministic run-time behaviour and evolution is not adequately
communicated to developers. Therefore, improving these services' API
documentation is paramount-more extensive documentation facilitates the
development process of intelligent software. In a prior study, we extracted 34
API documentation artefacts from 21 seminal works, devising a taxonomy of five
key requirements to produce quality API documentation. We extend this study in
two ways. Firstly, by surveying 104 developers of varying experience to
understand what API documentation artefacts are of most value to practitioners.
Secondly, identifying which of these highly-valued artefacts are or are not
well-documented through a case study in the emerging computer vision service
domain. We identify: (i) several gaps in the software engineering literature,
where aspects of API documentation understanding is/is not extensively
investigated; and (ii) where industry vendors (in contrast) document artefacts
to better serve their end-developers. We provide a set of recommendations to
enhance intelligent software documentation for both vendors and the wider
research community.Comment: Early Access preprint for an upcoming issue of the IEEE Transactions
on Software Engineerin
Usability Heuristics for Domain-Specific Languages (DSLs)
[Abstract] The usability of Domain-Specific Languages (DSLs) has been attracting considerable interest from researchers lately. In particular, our literature review found many usability studies that make use of subjective and empirical methods. However, we noted a lack of heuristic methods in the literature. In comparison, there exist several usability studies of Application Programming Interfaces (APIs) that have used heuristics with success, so we argue that this approach would be also useful for DSLs. Therefore, this paper proposes a set of usability heuristics for DSLs and illustrates the approach with a case study. We show how our heuristics helped us identify many actual usability problems, even for a simple DSL.Xunta de Galicia; GRC2014/035Xunta de Galicia; ED431G/0
- …