In this paper we present Software Archinaut-a tool used to help identify technical debt hotspots in an architecture, and manage the evolution of the architecture once these hotspots are discovered. Archinaut is a platform that integrates analyses from different tools. It supports three main usage scenarios: 1) understanding the architecture, 2) identifying technical debt hotspots, and 3) monitoring and controlling the evolution of the architecture. We illustrate these scenarios by using Apache Kafka as an example.

Attribute Driven Design (ADD)--a method for designing software architectures--was originally developed by the Software Engineering Institute in 2000.ADD 2.0, was published in 2006. Recently we have made some significant changes to ADD to make it easier to enact, to make it better aligned with the way that software is developed today, and hence to improve its adoption by the software architecture practitioner community.In this tutorial we will introduce ADD 3.0 and explain the key changes that we made to its previous versions. We will also present a detailed real-world case study, in the domain of big data, and walk the participants through a few iterations of the method showing how the steps are performed in practice. Then the participants will have the opportunity to enact several iterations of the method on their own. We will place particular emphasis on the design decisions that are made in the different design iterations: how different concepts are used in different iterations, and how these decisions are made more confidently through the use of a reusable catalog of design concepts, how these are documented, and how these can be analyzed within the design process.

This paper presents an approach to describe dynamic sensor-based applications using a declarative language called WADL. Dynamic sensor-based applications are characterized by the fact that measurement producers (sensors) and consumers are introduced or removed from an execution environment at run-time. Supporting this degree of dynamism is usually done programmatically, and the WADL intends to simplify this task and to provide developers with an explicit view of the system architecture, while supporting its dynamic evolution. The paper describes the WADL, its implementation on top of the OSGi WireAdmin Service, and some experimentation results.

The open services gateway initiative (OSGi) defines and promotes open specifications for the delivery of managed services into networked environments. A key element of this initiative is the OSGi framework, which is a lightweight framework for deploying and executing service-oriented applications. This paper focuses on the OSGi framework by first discussing some implementation details of an open source implementation of the OSGi framework, called Oscar. The paper then presents issues that arose or whose importance was magnified through implementing and/or using the OSGi framework.

This paper describes a project, called Gravity, that defines a component model, where components provide and require services (i.e., functionality) and all component interaction occurs via services. This approach introduces service-oriented concepts into a component model and execution environment. The goal is to support the construction and execution of component-based applications that are capable of autonomously adapting at run time due to the dynamic availability of the services provided by constituent components. In this component model the execution environment manages an application that is described as an abstract composition that can adapt and evolve at run time depending on available functionality. The motivation of Gravity is to simplify the construction of applications where dynamic availability arises, ranging from modern extensible systems to novel computing approaches, such as context-aware applications.

This paper describes a project, called Gravity, that is providing support for building client-side applications out of dynamically available building blocks. The purpose behind this work is not only to deal with real-world issues already facing developers and end-users, but to also work toward a grander vision. In this vision, applications are built using context-aware architectures, meaning that context (e.g., location, environment, user task) is used as a filter to determine which building blocks are relevant to the application at any given time. The main concept underlying this vision is dynamically available building blocks, i.e., building blocks that can appear or disappear at any time. The Gravity technology described in this paper is a starting point for such research.