The workshop focussed on three major topics leading to split attendees in three groups. After a short report of the outcomes, the remaining of the chapter is devoted to the thirteen selected position papers. Formalisms should have characteristics such as to be understandable by practitioners, to contain abstraction techniques, to be open so that they can be refined with subformalisms, and to be computable to be integrated in a tool. Moreover, systems have to support the coexistence and the interaction of formalized parts with non-formalized parts. The notion of extended interfaces can roughly be seen as interfaces annotated with extra behavioural information.
Temporal formalisms are necessary to describe architectures and their evolution.
Graph grammars allow us to reason about the evolution of dependencies captured by graphs. The category theory seems like a noble formalism to capture architectures, because they can be seen as code abstractions, and categories have an overwhelming suite of abstraction mechanisms over graph-like structures. System, subsystem, module, class and method. Repeatability of empirical validation case studies and theoretical validation are certainly two ways to proceed. The identified issues adressed by this group are the distinction between structure, architecture and architectural style, software generality versus flexibility, the progression from requirements to architectures, domain modelling to inform architecture, methods for evaluating and assessing architecture, and the architecting process.