A Classification and Comparison Framework for Software Architecture Description Languages

By Nenad Medvidovic, Richard N. Taylor. IEEE Trans. Software Eng., 2000

2,335 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/3cf945bfbc69107fd636de6fdfe751d3b06e4a58

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Computer Networks and Communications

In Information Systems

Citations in the corpus

Software Architecture Reconstruction: A Process-Oriented Taxonomy (2009, background): “Architecture Description Languages (ADLs) have been proposed both to formally define architectures and support architecture-centric development activities [103].”
Software Architecture as a Set of Architectural Design Decisions (2005, methodology): “Architectural Description Languages (ADLs) [16] describe software architectures in a formal language, which support first class architectural concepts.”
What Industry Needs from Architectural Languages: A Survey (2013, methodology): “They reviewed a number of software technologies, they found that it typically takes 15-20 years for a technology to be ready for popularization, and they identified six phases: (a) Basic research; (b) Concept formulation; (c) Development and extension; (d) Internal Enhancement and exploration; (e) E”
Towards a taxonomy of software connectors (2000, background): “Such level of understanding is necessary in order to fully meet the challenge posed to software architecture researchers of giving connectors “a first-class status” [20,35].”
Modeling software architectures in the Unified Modeling Language (2002, methodology): “The requirements are as follows: UML should be well suited to model the structural concerns (i.e., the con.guration or topology [Medvidovic and Taylor 2000]) of a system.”
Engineering Automotive Software (2007, methodology): “Architecture description languages (ADLs) [78] have long been used to describe design and deployment architectures of software systems.”
Component-Based Software Engineering (2005, methodology): “There are numerous definitions of software architecture, such as [2,4, 29 ,37].”
Software Component Models (2006, methodology): “The abstract model can be used to explain the semantics and syntax of components and their composition, at an abstract level, independent of any specific model.”
An Open Component Model and Its Support in Java (2004, background): “Component models. The Fractal model occupies an original position in the vast amount of work dealing with component-based programming and software architecture [22, 14 ,12], because of its combination of features: hierarchical components with sharing, support for arbitrary binding semantics between ”
The Palladio component model for model-driven performance prediction (2009, background): “They are related to architectural description languages (ADL) [44].”
A taxonomy of variability realization techniques (2005, methodology): “Koala [24], XVCL [28], or any of the ADL’s mentioned in Reference [29]).”
Staged configuration through specialization and multilevel configuration of feature models (2005, background): “The latter is the domain of architecture description languages (ADLs) (e.g., Medvidovic and Taylor, 2000) rather than feature modeling.”
A Classification Framework for Software Component Models (2011, methodology): “The observations and analysis included the study of a number of component models and the literature related to the general principles of CBSE [2], [3], [4], [6], [7], [8], [9], and related classifications [5], [10], [11], [12].”
A survey of self-management in dynamic software architecture specifications (2004, background): “Related work to our survey includes several papers that have surveyed Architecture Description Languages (ADLs) and provided broad comparisons [6, 18].”
Behavior Protocols for Software Components (2002, background): “In F, an interface can be instantiated as a providesinterface or a requires-interface (this concept is typical for most ADLs, e.g., [ 13 ]).”
ArchJava: connecting software architecture to implementation (2002, background): “Describing architecture in a formal architecture description language (ADL) [ MT00 ] can aid in the specification and analysis of high-level designs.”