Acme: architectural description of component-based systems

By David Garlan, Robert T. Monroe, D. Wile. 2000

676 citations recorded by the source corpus.

How researchers see this paper

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

Design Techniques and Applications of Cyberphysical Systems: A Survey (2015, methodology): “methodology for facilitating design and evaluation of alternative architectures for CPSs, using Acme architectural description language [274], which extends existing architectural”
A generic component model for building systems software (2008, background): “architecture description language (specifically, ACME [Garlan et al. 2000]) and are compiled to generate CF-specific constraint policing code [Joolia et al.”
Software Component Models (2006, methodology): “Examples are Acme [36] and UML2.”
Component-Based Software Engineering (2005, background): “They must interact with each other in a system architecture [36,4,29, 12 ,40,33].”
Rainbow: architecture-based self-adaptation with reusable infrastructure (2004, methodology): “An architectural model represents the system architecture as a graph of interacting components, as illustrated in Figure 2.1 This is the core architectural representation scheme adopted by a number of architecture description languages (ADLs), including Acme [ 12 ], xADL [7], and SADL [22].”
What Industry Needs from Architectural Languages: A Survey (2013, unknown): “, [16], [28], [29]).”
Software Architecture (2008, unknown): “Acme: Archi- tectural Description of Component-Based Systems.”