Reengineering the lifecycle of Arrowhead applications: from skeletons to the client library

Traditionally, the development workflow of Arrow-head applications is based on the usage of source code skeletons. This makes it difficult to update applications when the skeletons are changed, for example to fix security vulnerabilities or add new functionality. In fact, to update an application the developer has to either recreate the application on the new skeleton version or recreate the skeleton changes on the previous version of the application. Instead, we propose a client library, which allows the developers to create Arrowhead applications by referring to a library. Not only does this allow the Arrowhead Consortium to update the library without requiring changes to applications, it also eases the creation of new Arrowhead applications, reduces code duplication and increases readability. This paper describes the design and the structure of this client library, provides insights on how to employ the library in applications, and surveys a few sample applications that use the library.