What Industry Needs from Architectural Languages: A Survey

Malavolta, Ivano; Lago, Patricia; Muccini, Henry; Pelliccione, Patrizio; Tang, Antony

doi:10.1109/tse.2012.74

Cited by 233 publications

(212 citation statements)

References 40 publications

Supporting

Mentioning

206

Contrasting

Order By: Relevance

“…Understanding the way architectural information in SAD of OSS projects is documented can help researchers and practitioners to identify mainstream architectural languages for OSS projects as well as their needs [31].…”

Section: Rq2 What Architectural Languages Are Used In Sad Of Oss Promentioning

confidence: 99%

“…Diagram and UML are often used to decribe model and system elements since these two architectural languages are graphical representations suitable for representing the structural aspect of an architecture (i.e., model and system elements). They can represent and facilitate interaction with non-technical stakeholders [31], e.g., UML can be used to describe and communicate the static structure of an architecture [35]. However, diagram and UML are not used to describe mission and environment elements.…”

Section: Relationship Between Architectural Languages Andmentioning

confidence: 99%

See 1 more Smart Citation

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

Self Cite

View full text Add to dashboard Cite

Abstract-Software architecture (SA) documentation provides a blueprint of a software-intensive system for the communication between stakeholders about the high-level design of the system. In open source software (OSS) development, a lack of SA documentation may hinder the use and further development of OSS, but how much "architecture" documentation is enough and appropriate is largely dependent on the contextual factors of development. In order to understand the state of the practice of SA documentation in OSS projects, we conducted a documentation-based survey to explore how SA is documented in OSS projects. Out of 2,000 OSS projects from four major OSS sources, we found that 108 projects have some SA documentation, which shows that the SA documentation is scarce in OSS development. We analyzed these 108 projects to understand what SA information has been documented and how they have been described. We have found that frequentlydocumented architectural information is model, system, and mission; natural language is the most frequently-used architectural language for specifying architectural information in OSS SA documents. The results also show that the likelihood that an OSS project will document SA is increased when more developers are involved in the project, and industry and research OSS projects are more likely to create SA documents than freelance projects.

show abstract

Section: Rq2 What Architectural Languages Are Used In Sad Of Oss Promentioning

confidence: 99%

Section: Relationship Between Architectural Languages Andmentioning

confidence: 99%

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

Self Cite

View full text Add to dashboard Cite

show abstract

“…This is one of the major reasons that often hinders the adoption of formal-based techniques in software industry, as revealed in a recent survey in this context [15]. Therefore, providing affordable, efficient approaches for rigorously verifying properties in dynamic software architectures is a major challenge.…”

Section: Introductionmentioning

confidence: 99%

Statistical Model Checking of Dynamic Software Architectures

Cavalcante

Quilbeuf

Traonouez

et al. 2016

Software Architecture

View full text Add to dashboard Cite

Abstract. The critical nature of many complex software-intensive systems calls for formal, rigorous architecture descriptions as means of supporting automated verification and enforcement of architectural properties and constraints. Model checking has been one of the most used techniques to automatically analyze software architectures with respect to the satisfaction of architectural properties. However, such a technique leads to an exhaustive exploration of all possible states of the system under verification, a problem that becomes more severe when verifying dynamic software systems due to their typical non-deterministic runtime behavior and unpredictable operation conditions. To tackle these issues, we propose using statistical model checking (SMC) to support the analysis of dynamic software architectures while aiming at reducing effort, computational resources, and time required for this task. In this paper, we introduce a novel notation to formally express architectural properties as well as an SMC-based toolchain for verifying dynamic software architectures described in π-ADL, a formal architecture description language. We use a flood monitoring system to show how to express relevant properties to be verified, as well as we report the results of some computational experiments performed to assess the efficiency of our approach.

show abstract

“…A survey we recently conducted on the industrial needs from architectural languages [4] revealed that 85% of the 48 interviewed practitioners use multiple views when architecting a software system, with a total of nine different views and a predominant use of structural, behavioral, and physical views reported. One consequence of the tenet of using multiple views is a growing body of viewpoints that have become available (such as [1], [5], [6]) and supported by Architecture Description Languages (ADLs).…”

Section: Introductionmentioning

confidence: 99%

“…Thus, (i) it is difficult to re-use viewpoints when defining new frameworks to be used in different organizations or domains; and (ii) it is difficult to define consistency rules among viewpoints once and forever, since such rules are not re-usable as first-class artefacts. Based on our survey [4], although automated consistency checking between views is advocated as an important feature for future ADLs, about 50% of the respondents check view consistency manually (i.e., with no formalized method). Moreover, (iii) current ADLs do not provide systematic mechanisms for adding new views (about 48% of the respondents to our survey had to extend their ADLs for adding new views).…”

Section: Introductionmentioning

confidence: 99%

On the Composition and Reuse of Viewpoints across Architecture Frameworks

Hilliard

Malavolta

Muccini

2012

2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture

Self Cite

View full text Add to dashboard Cite

Abstract-A central aspect of architecting is architecture description. Architecture descriptions take many forms and serve many purposes throughout the life cycle of development, operation and maintenance activities. The use of multiple views -diverse representations for distinct audiences and uses -has been a major tenet of architecture description since the earliest work in software architecture. This tenet has been codified in various ways. Most practising software architects must operate within the confines of a prescribed architecture framework (AF) or architecture description language (ADL) as dictated by their organization or client. Current AFs and ADLs are defined with varying degrees of rigour and offer varying levels of tool support; furthermore, these resources are often closed, making it difficult for the architect to tailor a representational solution to the specific challenges of the project at hand.In this paper we propose an automated infrastructure to support the architecture description-related activities of the architect. This infrastructure facilitates customization, composition and reuse of the architect's representational resources (AFs, ADLs and their constituents) to meet project-, domainand organization-specific needs. The proposed approach builds upon the conceptual foundations of ISO/IEC/IEEE 42010 for architecture description. The approach has been evaluated in the context of a complex, real-world, public transportation system.

show abstract

What Industry Needs from Architectural Languages: A Survey

Cited by 233 publications

References 40 publications

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Statistical Model Checking of Dynamic Software Architectures

On the Composition and Reuse of Viewpoints across Architecture Frameworks

Contact Info

Product

Resources

About