Search

Copyright of CISTI (Iberian Conference on Information Systems & Technologies / Conferência Ibérica de Sistemas e Tecnologias de Informação) Proceedings is the property of Conferencia Iberica de Sistemas Tecnologia de Informacao and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

As organizations move to the cloud, they realize that simply migrating existing legacy applications has not achieved the anticipated efficiencies and cost savings. The result is an increased focus on the design and deployment of truly cloud-native applications. This shift must take place within information systems curricula to remain relevant in this space, but this requires rethinking the structure, focus, and approach of these courses. This paper describes the redesign of an undergraduate cloud infrastructure course where students create and deploy APIs using cloud-native technologies. [ABSTRACT FROM AUTHOR]

Digital ecosystems are usually conceptualized around a focal platform orchestrating the contribution of third parties. Such theorizations cannot adequately account for the dynamic and emergent nature of ecosystems, resulting from intricate and transient interconnections. To this aim, we propose opening the black-box of interfaces and outlining their role in infrastructuring digital ecosystems and configuring relationships of value creation. We present the results of an empirical research exploring the role of Application Programming Interfaces (APIs) in the fluid and emergent dynamics of the online travel ecosystem. We reveal how the ongoing and manifold processes of interfacing result, over time, in the changing position of actors and emergence of new ones, and of their multiple and relative roles within the ecosystem. We contribute to the IS literature on digital innovation by showing how value creation and innovation in ecosystems is much more fluid, dynamic and multifarious than a platform-centric approach would suggest. [ABSTRACT FROM AUTHOR]

Copyright of CISTI (Iberian Conference on Information Systems & Technologies / Conferência Ibérica de Sistemas e Tecnologias de Informação) Proceedings is the property of Conferencia Iberica de Sistemas Tecnologia de Informacao and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Copyright of Congreso Internacional de Investigacion Academia Journals is the property of PDHTech, LLC and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Software engineering activities often produce large amounts of unstructured data. Useful information can be extracted from such data to facilitate software development activities, such as bug reports management and documentation provision. Online forums, in particular, contain extensive valuable information that can aid in software development. However, no work has been done to extract problematic API features from online forums. In this paper, we investigate ways to extract problematic API features that are discussed as a source of difficulty in each thread, using natural language processing and sentiment analysis techniques. Based on a preliminary manual analysis of the content of a discussion thread and a categorization of the role of each sentence therein, we decide to focus on a negative sentiment sentence and its close neighbors as a unit for extracting API features. We evaluate a set of candidate solutions by comparing tool-extracted problematic API design features with manually produced golden test data. Our best solution yields a precision of 89%. We have also investigated three potential applications for our feature extraction solution: (i) highlighting the negative sentence and its neighbors to help illustrate the main API feature; (ii) searching helpful online information using the extracted API feature as a query; (iii) summarizing the problematic features to reveal the “hot topics” in a forum. [ABSTRACT FROM PUBLISHER]

Today, when constructing a new software system, many developers build their systems on top of frameworks. Eclipse framework is one such popular and widely adopted framework that has been evolving for over a decade. Like many other evolving software systems, the Eclipse SDK framework has both stable and supported APIs (good interfaces) and unstable, discouraged and unsupported non-APIs (bad interfaces). However, despite being discouraged by Eclipse, in our experience, the usage of bad interfaces is not uncommon. In this thesis, by means of a series of empirical studies, we quantify/qualify some the challenges faced by Eclipse third-party plug-in developers in using the interfaces provided by the Eclipse SDK framework. Furthermore, we propose solutions to the identified challenges, like changes in development strategy to both interface providers and interface users. In particular, the lessons learned from this study can provide valuable information in particular to the interface providers, i.e., Eclipse SDK developers, and the interface uses, i.e., ETP developers, in co-evolving the Eclipse framework. In general, the lessons learned can be transferable to other framework ecosystem. [ABSTRACT FROM PUBLISHER]

Eclipse guidelines distinguish between two types of interfaces provided to third-party developers, i.e., APIs and non-APIs. APIs are stable and supported, while non-APIs are unstable, unsupported and discouraged as they are subject to arbitrary change or removal without notice. In our previous work, we found that despite the discouragement of Eclipse, the use of non-APIs in Eclipse third-party plug-ins (ETPs) is not uncommon. Furthermore, we found that these non-APIs are the main cause of ETP incompatibilities in forthcoming releases of the Eclipse. In the current work we conducted a survey aiming at understanding why do the ETP developers use non-APIs. We have observed that developers with a level of education of up to master degree have a tendency not to read product manuals/guidelines. Furthermore, while for less experienced developers instability of the non-APIs overshadows their benefits, more experienced developers prefer to enjoy the benefits of non-APIs despite the instability problem. Finally, we have observed that there are no significant differences between Open Source and commercial Eclipse products in terms of awareness of Eclipse guidelines and interfaces, Eclipse product size and updating of Eclipse product in the new SDK releases. [ABSTRACT FROM PUBLISHER]

Massive use of wireless networks and the high rate penetration of mobile deviceshave raised severalchallenges to developers. One of the research problems of the data wireless networks is the so-calledvertical handoff, and a great number of vertical handoff algorithms (VHA) thathave been proposed. Most of these algorithms have been tested in simulated environments using simulation tools (e.g. NS-2, OMNeT++, NCTUNs), but only a few algorithms have been tested in a real environment. This paper presents a VHA controlled from a mobile phone and a software prototype for Android platform. One of the goals of our research was to validate the potential of Android's platforms as a tool for research in the topic of controlled vertical handoff from mobile device (MCVHO). [ABSTRACT FROM PUBLISHER]

Web mashups are a new generation of applications created by composing contents and functions available through Web services and APIs. A central activity in mashup development is the retrieval and selection of components to be included in the composition. The adoption of recommender systems can alleviate some of the difficulties arising in this activity. Based on the results of an empirical study, this paper tries to shed light on the application of recommender systems to the mashup composition domain, and discusses the performance of different recommendation systems when applied to a very large collection of mashups and mashup components. [ABSTRACT FROM PUBLISHER]

Learning to use a software framework and its API (Application Programming Interfaces) can be a major endeavor for novices. To help, we have built a critic to advise the use of an API based on the formal semantics of the API. Specifically, the critic offers advice when the symbolic state of the API client code triggers any API usage rules. To assess to what extent our critic can help solve practical API usage problems and what kinds of API usage rules can be formulated, we manually analyzed 150 discussion threads from the Java Swing forum. We categorize the discussion threads according to how they can be helped by the critic. We find that API problems of the same nature appear repeatedly in the forum, and that API problems of the same nature can be addressed by implementing a new API usage rule for the critic. We characterize the set of discovered API usage rules as a whole. Unlike past empirical studies that focus on answering why frameworks and APIs are hard to learn, ours is the first designed to produce systematic data that have been directly used to build an API support tool. [ABSTRACT FROM PUBLISHER]

For more than five years, researchers at Carnegie Mellon University have been collaborating with several SAP teams to improve the usability of SAP's developer tools and programming APIs. Much research has shown that HCI techniques can improve the tools that developers use to write software. In a recent project, we applied HCI techniques to a SAP developer tool for the SAP NetWeaver Gateway product. The SAP team building this tool uses agile software development processes, which allowed them to quickly improve the tool's usability based upon the evaluations. [ABSTRACT FROM PUBLISHER]