Documenting software architectures: views and beyond

By P. Clements, David Garlan, Reed Little, R. Nord, J. Stafford. 25th International Conference on Software Engineering, 2003. Proceedings., 2002

1,696 citations recorded by the source corpus.

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

View Paper: https://www.semanticscholar.org/paper/a28effe7b4b72af5575f3fcdb32300bc86726a43

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

Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity (2008, background): “Researchers have proposed standard graphical representations of software architectures that capture different technical aspects of a software system [12].”
Software Architecture as a Set of Architectural Design Decisions (2005, background): “Although the term " architectural design decision " is often used [7] [10] [4], a precise definition is hard to find.”
The Blockchain as a Software Connector (2016, background): “For example, middleware can be viewed as a connector between the components that use the middleware [6].”
Building Up and Reasoning About Architectural Knowledge (2006, background): “Architectural design, even well documented according to all the good recipes [5, 12, 14], is only one small part of the Architectural Knowledge that is required to design a system, or that is needed to guide a possibly multisite development team, or that can be exploited out of a system to build the”
Digital twins in smart farming (2021, background): “It is usually not drawn in one diagram but separated in multiple so-called architecture views each of which describes an architecture according to specific stakeholders ’ concerns (Clements et al., 2010).”
Rainbow: architecture-based self-adaptation with reusable infrastructure (2004, background): “4 Such an architecture-based self-adaptation approach offers many beneﬁts.”
A survey on engineering approaches for self-adaptive systems (2015, methodology): “A software architecture is a set of software elements (or components), the relations between them, as well as the properties of both [75] and denotes the high level structure of software [76].”
Architecture for Blockchain Applications (2019, methodology): “The software architecture of a software-based system is the high-level structure of relationships between software elements (components and connectors) in the system (Clements et al. 2003; Bass et al. 2012).”
On Architecture Specification (2018, background): “When looking at software families and product lines, architecture becomes even more signi ﬁ cant, because it determines the possibilities and options of variability and reusability (see [8]).”
What Industry Needs from Architectural Languages: A Survey (2013, background): “Index Terms—Software Architecture, Architecture Description Languages, ADL, Survey, Empirical Study”
An Ontology of Architectural Design Decisions in Software-Intensive Systems (2004, methodology): “Representations of software architecture were centered on views, (Clements et al., 2002; Hofmeister, Nord, & Soni, 2000; Kruchten, 1995), as captured by the IEEE 1471 standard (IEEE, 2000), or usage of an architecture description language.”