CAR-2-X Communication SDK - A Software Toolkit for Rapid Application Development and Experimentations

Context: From the past few years, Application Programming Interface (API) is widely used for mobile- and web-based application developments. Software developers can integrate third-party services into their projects to achieve their development goals efficiently using APIs; however, with the rapid increase in the number of APIs, the manual selection of Mashup-oriented API is becoming more difficult for the developer. Objective: In the COVID-19 pandemic, everyone wants an update about the latest Standard Operating Procedures (SOPs) and the latest information on COVID-19. Additionally, a software developer wants to develop an application that provides the SOPs and latest information of COVID-19; a developer can add these functionalities into an application using COVID-19-based APIs. Moreover, the current work aims at proposing a COVID-19-based API recommendation system for the developers. Method: In this study, we propose a COVID-19-based API recommendation system for developers. The recommendation system takes a developer query as input and recommends top-3 APIs and supported features, which help the developer during software development. Furthermore, the proposed COVID-19-based API recommendation system ensures the maximum participation of the developers by validating the recommended APIs and recommendation system from the expert developers using research questionnaires. Results: Additionally, the proposed COVID-19-based API recommendation system’s output is validated by expert developers and evaluated on 120 expert developers’ queries. In addition, experiment results show that single value decomposition achieves better prediction. Conclusion: We conclude that it is significantly important to recommend APIs along with supported features to the developer for project development, and future work is needed to take more developer’s queries also to build Integrated Development Environment for the developers.

Efforts were made to integrate emerging Vehicular Ad-hoc Network (VANETs) with the mobile internet architecture through Road Side Unit (RSU) to enhance its operational capabilities for safety and non safety applications. Transmission Control Protocol (TCP) is one of the prominent protocol that contributes a considerable amount of internet traffic as the vast majority of internet applications such as file transfer, messaging service, mail services, etc. was based on TCP. However, TCP performs poorly under vehicular wireless environment due to its high mobility and wireless errors such as fading and interferences that lead to unpredicted packet drop. In this paper the behavioral aspects of existing standard TCP variants such as Vegas, Compound, Westwood, New Reno, BIC and CUBIC were rigorously tested and analyzed under vehicular environment for variable speed and traffic. This analysis forms a foundation work in designing TCP exclusively for vehicular environment.

APIs (application programming interfaces) play a key role in software development. Virtually, all programmers are potential users of third-party APIs. From the perspective of the theory of Semiotic Engineering, we may characterize an API as an artifact mediating the communication between two types of developers: the API designers and its users. During the construction of an API, the designers should establish proper dialogues with the users. These dialogues will enable the conversation of these actors at the interaction time. In this way, we define a conversational API as an API capable of offering effective dialogues to its users. In this paper, we introduce Colloquy, a method for supporting the design of conversational APIs. Colloquy results from the lessons learnt during an action research conducted for redesigning a real and complex API. The set of Colloquy resources allow API designers to go beyond conventional concerns with usability. We also report in this paper a case study in which Colloquy was used for redesigning a refactoring API. The study findings indicate the method helped the designer creating empathy with the API users, as well as better reflecting and depicting the requirements and the conversations that the API should attend to the different user profiles.

The paper present exploratory research on application programming interface (API), management of accounting information system, security of transaction processing system, general ledger and financial reporting system. An application programming interface, or API, enables businesses to make the data and functionality of their applications available to external third-party developers, commercial partners, and internal departments inside their own organizations. Using a defined interface enables services and products to interact with one another and benefit from each other's information and features. The interface is used by developers to interact with other software and services; they are not required to understand how an API is developed, and neither are the software’s end-users. In short, an API is a contract between pieces of applications serving the main software once integrated into the source code of the main application. These pieces of applications communicate with each other in the language they both understand and over a network if needed. As the name implies, APIs serve as interfaces between programs. The interface is usually between a software developer and software developer’s application. Basically, the API allows one software to access some functionalities of another software. In its development, information systems develop and run well using a web-base so that it can be reached via an online computer network. Web applications have become complex and important for many companies, especially when combined with areas such as AIS. All AIS transaction data will be stored in the database management system and will be used if there is a query data request. Based on the IFRS (International Financial Reporting Standard) document, a proper accounting system must at least include the following aspects (IFRS Standard Requirements): Financial position statement, cash flows statement. Web-based AIS application for recording, grouping, processing

Application programming interfaces (APIs) have a central role in software development, as programmers have to deal with a number of routines and services that range from operating system libraries to large application frameworks. In order to effectively use APIs, programmers should have good comprehension of these software artifacts, making sense of the underlying abstractions and concepts by developing an interpretation that is compatible with the designer's intent. Due to the complexity of today's systems and programming environments, learning and using an API properly can be non-trivial task to many programmers. Traditionally, studies on API design have been developed from a usability standpoint. These studies have provided evidence that bad APIs may affect programmer's productivity and software quality, offering valuable insights to improve the design of new and existing APIs. This thesis proposes a novel approach to investigate and discuss API design, based on a communication perspective under the theoretical guidance of Semiotic Engineering. From this perspective, an API can be viewed as a communication process that takes place between designer and programmer, in which the former encodes a message to the latter about how to communicate back with the system and use the artifact's features, according to its design vision. This approach provides an account of API design space that highlights the pragmatic and cognitive aspects of human communication mediated by this type of software artifact. By means of the collection and qualitative analysis of empirical data from bug repositories and other sources, this research work contributes to a deeper comprehension of the subject, providing an epistemic framework that intends to support the analysis, discussion and evaluation of API design.

Application Programming Interface (API) merupakan antarmuka yang dibangun
\noleh pengembang sistem supaya sebagian atau keseluruhan fungsi sistem dapat
\ndiakses secara programmatis. Sementara Representational State Transfer (REST)
\nmerupakan salah satu gaya arsitektur dari pengembangan API yang menggunakan
\nHypertext Transfer Protocol (HTTP) dalam melakukan komunikasi data. Penelitian
\nini mengimplementasikan gaya arsitektur REST dalam pengembangan API sebagai
\nback-end sistem informasi administrasi pasien klinik perawatan kulit. API yang
\ndikembangkan menggunakan Javascript Object Notation (JSON) sebagai standar
\nformat dalam komunikasi data serta JSON Web Token (JWT) sebagai kode
\notentikasi pengguna pengguna. Penelitian ini menunjukkan bahwa pengembangan
\nAPI berhasil dilakukan pada administrasi pasien klinik perawatan kulit dan REST
\nyang diterapkan mempermudah pengembangan struktur API. Penelitian ini
\nmenghasilkan back-end sistem informasi administrasi pasien klinik perawatan kulit
\nberbasis REST API. API diuji dalam tiga tahap yakni pengujian JWT pada backend
\nserver berjumlah banyak, pengujian API dengan metode Equivalence
\nPartitioning dan pengujian fungsional sistem.
\nKata kunci: application programming interface (api), representational state
\ntransfer (rest), hypertext transfer protocol (http), javascript object
\nnotation (json), json web token (jwt).
\n
\n
\nABSTRACT
\n
\nApplication Programming Interface (API) is an interface built by system developer
\nso some or entire functions of the system can programmatically be accessed.
\nRepresentational State Transfer (REST) is one of API development architectural
\nstyle that uses Hypertext Transfer Protocol (HTTP) for data communication. This
\nresearch implemented REST in developing API as the back-end of the skincare
\nclinic patient information system. API was developed using Javascript Object
\nNotation (JSON) as the standard format for data communication and JSON Web
\nToken (JWT) as user authentication code. This research indicates that the
\ndevelopment of API successfully performed on the patient administration of skin
\ncare clinic and implementation of REST makes it easy to develop API structures.
\nThis research produced REST API-based back-end for the patient administration
\ninformation system of skin care clinic. API was tested in three stages: JWT testing
\non multiple back-end servers, API testing with Equivalence Partitioning and system
\nfunctional testing.
\nKeywords : application programming interface (api), representational state transfer
\n(rest), hypertext transfer protocol (http), javascript object notation
\n(json), json web token (jwt).

Impact of Developer Choices on Energy Consumption of Software on Servers

While Application Programming Interface (API) enables an easy and flexible software development process, selecting a best-fit API is often non-straightforward in practice due to misunderstanding on the API specification or a complex programming context etc.. Consequently, the API selection has always been time-consuming and error-prone. In recent years, API recommendation systems have been introduced to help developers choose an API automatically, e.g., Eclipse and IntelliJ can generate an internal or user-defined API on the fly. Other research leveraged language models to capture the regularity in API usage and further guide the completion of APIs. While existing approaches provided a general support for API usage, they suffer from the lack of semantic awareness (e.g., Eclipse) and code relevance (e.g., language model based methods). To overcome these limitations, we proposed Crmac in this paper. The key insight of Crmac is a combination of a cache language model which learns code regularity from both open-source projects and local projects, as well as a relevance mining engine that identifies similar code to enable a weighted language model training. In our empirical evaluation, Crmac overwhelmed n-gram approaches, with an improvement of 5.28% in terms of top 10 accuracy. Moreover, over 79% APIs were correctly predicted in the top 10 guesses of Crmac.

An active dialogue between all the members of a university community is a vital part of the education process. A campus wide communications system, which allows lecturers and students to communicate through multiple communications protocols, which intelligently chooses how and when to deliver a message, will greatly improve students’ ability to learn and lecturers’ ability to teach. This thesis describes the design and implementation of such a system, the Intelligent Messaging System (IMeS). Further by creating a service which is modular both in the communications protocols that are supported and the way the information is presented to the user, the IMeS is able to adapt and respond to changes in the way people, in particular young people who make up the majority of the student body, use technology to communicate. By rapidly supporting new communications protocols and technologies, the IMeS will stay relevant to the way its users communicate as new technologies for communication emerge. Much of this flexibility is provided by leveraging the Java Agent DEvelopment (JADE) framework, which allows the development of asynchronous agent-based systems. Initially this thesis describes the implementation of the IMeS with access via a web site, Short Message Service (SMS) and email, and provides a roadmap of integrating other communications protocols as additional services. The IMeS provides a Simple Object Access Protocol (SOAP) Application Programming Interface (API), which allows the expansion of how users can interact with the system, in particular allowing dedicated applications to be created for mobile devices. The web site is built on this API, proving it is both functionally operational and fit for purpose.

Vehicular ad hoc networks (VANETS) are simply a collection of onboard units (OBUs) and roadside units (RSUs) that communicate using dedicated short-range communications (DSRC) utilizing 75 Mhz in 5.9 GHz frequency band for wireless access in vehicular environment (WAVE). The frequency channel layout of WAVE has been divided into seven channels, with one channel for service safety applications and the remaining for service non-safety applications. The nature of the VANET environment being dynamic, it is most likely that packet forwarding over varied time intervals may be disconnected, causing network delays. In such a case the message containing information needs to be with the current vehicle until a new intelligent node becomes active. Extensive studies have been conducted on the propagation of messages in vehicular networks. Although conventional methods are mainly focused on similar traffic, in this only high, low-density traffic is considered. The intelligent mobile node structure in NS-3 has been designed in such a way as to support 802.11 MAC with a single channel. However, this intelligent mobile node is not appropriate for WAVE multi-channel operation.

The application programming interface (API) as a means of communication to establish a connection with the cloud, which allows storing the vast amounts of heterogeneous data. Data has been steadily growing over the past several years. Software developers can use different data from cloud as convenient ecosystems for developing, deploying, testing and maintaining their software. API provides the archival solution and storing the data in the cloud. This platform also plays an essential role in managing them effectively with improved transfer rates. API is becoming increasingly dynamic and complex day by day. One of the significant challenges faced by us is to develop appropriate individual API and extensible mechanisms for managing and storing the data in the cloud. The objective of this paper is to utilize the storage efficiently based on API capability and analysis of (extreme amounts of) raw heterogeneous data.

Communication networks, protocols, and application programming interfaces (APIs) are crucial factors for the performance of parallel and distributed computations. This topic of Euro-Par 2003 is therefore devoted to all aspects of communication in on-chip interconnects, parallel computers, networks of workstations, and more widely distributed systems such as grids. Papers were solicited that examine the design and implementation of interconnection networks and communication protocols, advances in system area and storage area networks, routing and communication algorithms, and the communication costs of parallel and distributed algorithms. On-chip and power-e.cient interconnects, I/O architectures and storage area networks, switch architectures as well as multimedia and QoS-aware communication were new topics introduced in this year’s Call for Papers (CfP).

With the recent developments of communication technologies surrounding vehicles, we will be witnessing the simultaneous availability of multiple on-board communication interfaces on vehicles. While most of the current interfaces already include Bluetooth, WiFi, and LTE, they will be augmented further by IEEE 802.11p and the 5G interfaces, which will serve for safety, maintenance, and infotainment applications. However, dynamic management of interfaces depending on application needs will become a significant issue that can be best addressed by Software Defined Networking (SDN) technology. While SDN-based vehicular networks have been promoted previously, none of these works dealt with their practical challenges. In this paper, we propose and develop a practical framework that will realize SDN-based vehicular networks for a wide range of applications. Through this framework, we demonstrate a platoon example which demonstrates the use of SDN for quick and efficient multi-hop messaging. The route from source vehicle to destination is computed with the help of the SDN Controller to transmit the Beacon Safety Messages through Road Side Units (RSUs) at the MAC layer without relying on IP for proper platooning operations. The results show the efficiency of the SDN-based approach compared to the traditional routing approaches.

The XML-based Systems Biology Markup Language (SBML) is the de facto standard file format for the storage and exchange of biochemical network models, and is supported by more than 180 software packages to date. Much of this success is due to SBML's clearly defined specifications and the availability of libSBML, a portable, robust and easy-to-use library.LibSBML provides many methods for manipulating and validating SBML files through its Application Programming Interface (API). Originally written in C and C++, libSBML also provides automatically-generated language bindings for Java, MATLAB, Perl, Python, and many more. However, the platform independence of Java is compromised in libSBML due to the fact that the language binding is a wrapper around the C/C++ core. The real-world experiences of many software developers has been that the deployment of portable libSBML-based Java applications is difficult. Further, the libSBML API and type hierarchy are not sufficiently intuitive from a Java programmer's perspective simply because they were not designed directly for Java.For these reasons, several groups in the SBML community have mounted an open-source effort to develop a pure Java library for SBML. Here we present the JSBML project, whose products are freely available at the website "http://jsbml.sourceforge.net/":http://jsbml.sourceforge.net/. The JSBML project's aim is to provide an SBML parser and programming library that maps all SBML elements to a flexible and extended type hierarchy. Where possible, JSBML strives to attain 100% API compatibility with the libSBML Java API, to facilitate a switch from one library to the other for those who desire it.Currently, JSBML supports all constructs for SBML up to the latest Level 3 Version 1 release candidate specification, including an API to add SBML extensions. There are no plans to re-implement some of the more complex functions of libSBML, since separate community efforts are expected to make them available to JSBML via web services. These more complex functions include model consistency checking, SBML validation, and the conversion between different SBML Levels and Versions.In summary, JSBML is a young, ongoing software project that provides comprehensive and entirely Java-based data structures to read, write, and manipulate SBML files. Its layered architecture allows for the creation of Java web start applications and CellDesigner plug-ins based on stand-alone programs with very little effort. One program, SBMLsqueezer 1.3, has already been re-implemented and released using JSBML, and many others are planned.

Modern software systems are increasingly including machine learning (ML) as an integral component. However, we do not yet understand the difficulties faced by software developers when learning about ML libraries and using them within their systems. To fill that gap this thesis reports on a detailed (manual) examination of 3,243 highly-rated Q&A posts related to ten ML libraries, namely Tensorflow, Keras, scikitlearn, Weka, Caffe, Theano, MLlib, Torch, Mahout, and H2O, on Stack Overflow, a popular online technical Q&A forum. Our findings reveal the urgent need for software engineering (SE) research in this area. The second part of the thesis particularly focuses on understanding the Deep Neural Network (DNN) bug characteristics. We study 2,716 high-quality posts from Stack Overflow and 500 bug fix commits from Github about five popular deep learning libraries Caffe, Keras, Tensorflow, Theano, and Torch to understand the types of bugs, their root causes and impacts, bug-prone stage of deep learning pipeline as well as whether there are some common antipatterns found in this buggy software. While exploring the bug characteristics, our findings imply that repairing software that uses DNNs is one such unmistakable SE need where automated tools could be beneficial; however, we do not fully understand challenges to repairing and patterns that are utilized when manually repairing DNNs. So, the third part of this thesis presents a comprehensive study of bug fix patterns to address these questions. We have studied 415 repairs from Stack Overflow and 555 repairs from Github for five popular deep learning libraries Caffe, Keras, Tensorflow, Theano, and Torch to understand challenges in repairs and bug repair patterns. Our key findings reveal that DNN bug fix patterns are distinctive compared to traditional bug fix patterns and the most common bug fix patterns are fixing data dimension and neural network connectivity. Finally, we propose an automatic technique to detect ML Application Programming Interface (API) misuses. We started with an empirical study to understand ML API misuses. Our study shows that ML API misuse is prevalent and distinct compared to non-ML API misuses. Inspired by these findings, we contributed Amimla (Api Misuse In Machine Learning Apis) an approach and a tool for ML API misuse detection. Amimla relies on several technical innovations. First, we proposed an abstract representation of ML pipelines to use in misuse detection. Second, we proposed an abstract representation of neural networks for deep learning related APIs. Third, we have developed a representation strategy for constraints on ML APIs. Finally, we have developed a misuse detection strategy for both single and multi-APIs. Our experimental evaluation shows that Amimla achieves a high average accuracy of ∼80% on two benchmarks of misuses from Stack Overflow and Github.