Using weaves for software construction and analysis

A Family of Software Architecture Implementation Frameworks

“…For example, when the style was initially formulated, component communication ports were given an important role, despite the fact that each component always had a fixed number of ports (one on the top and one on the bottom) [32]. The original C2 framework tried to stay true to this vision, but eventually we realized that, unlike other styles such as Weaves [8], ports do not play an active role in a C2-style architecture. Therefore, explicit ports created unnecessary overhead in implementations and were removed in the subsequent frameworks.…”

“…To date, most architectural tools have focused on the simulation and analysis of architectural models to exploit the semantic power of ADLs. With few exceptions (e.g., Weaves [8], GenVoca [1]), insufficient progress has been made on supporting implementations of applications based on styles and ADL models [17].…”

Style-based software architectural compositions as domain-specific models

“…Most such tools tend to be style and notation specific. DRADEL for the C2 architectural style [15] and Weaves and its related toolset [8] are a few examples. ViSAC is style-neutral and aids an architect in defining architectural styles as well as architectures based on these styles.…”

“…Past research has helped establish the utility of architectural styles for designing largescale software systems by providing style-specific environments for architectural design (e.g., DRADEL [15]) and style-based architectural description languages (e.g., Weaves [8]). The creation of such techniques and associated tools is highly expensive, time consuming, and frequently involves reinventing the wheel.…”

“…A prominent reason for the increasing use of styles in the design of software architectures is the observation that a property proven about a style holds true in the architectures based on that style [9]. Further, styles provide analytical models for determining properties of software architectures such as performance and reliability [8,27].…”