Many architectural languages have been proposed in the last 15 years, each one with the chief aim of becoming the ideal language for specifying software architectures. What is evident nowadays, instead, is that architectural languages are defined by stakeholder concerns. Capturing all such concerns within a single, narrowly focused notation is difficult. At the same time it is also impractical to define and use a universal notation, such as UML. As a drawback, a proliferation of languages exists, each one with its own application domain, analysis type, or modeling environment. This thesis...