Attribute-Driven Design (ADD), Version 2.0

Wojcik, Rob; Bachmann, Felix; Bass, Len; Clements, Paul; Merson, Paulo; Nord, Robert L.; Wood, Bill

doi:10.21236/ada460414

Cited by 97 publications

(94 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A practical example applying ADD is presented in [39]. [38] In the following, we give a brief explanation of each ADD step based on [38] (see Figure 1). In the first step, a list of stable and prioritized requirements including functional, constraints and quality attributes have to be available to start ADD.…”

Section: Attribute Driven Design (Add) Methodsmentioning

confidence: 99%

“…Team Workload Division and Assignment: The ADD method does not explicitly focus on giving guidelines on how a team of architects divide their workload [38]. This can be emphasized on the first iteration.…”

Section: Add Issues Faced By Subjectsmentioning

confidence: 99%

“…The Software Engineering Institute (SEI) defines a quality attribute as "a property of a work product or goods by which its quality will be judged by some stakeholder or stakeholders" [33]. They are important properties that a system must exhibit such as scalability, modifiability or availability [38].…”

Section: Introductionmentioning

confidence: 99%

“…A method for designing software architecture based on quality attributes is the one defined by the SEI called the Attribute Driven Design (ADD) method [3], [38]. The ADD method is based on an iterative process for designing software architecture based on applying architectural tactics and patterns which satisfy quality attributes.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Exploring How the Attribute Driven Design Method Is Perceived

Alí

Solís²

2014

Relating System Quality and Software Architecture

View full text Add to dashboard Cite

Abstract.A method for designing software architecture based on achieving quality attributes is the Attribute Driven Design (ADD) method. This method has not been explored in terms of users' perception on its usefulness and easiness of use. Our goal is to study the perceptions that software engineers with no or little experience industrially in designing software architecture using the ADD. In this paper, we describe an empirical study that we conducted on master students to measure their perceptions of the ADD after using it. We performed two experiments; one with students enrolled in the Software Architecture module in 2010 and repeated it with the students of the same module in 2011. Our main findings are that the subjects perceive ADD method as useful, and that there is a relationship between its usefulness and willingness of use. However, the subjects' opinion was that they did not agree that the ADD method is easy to be used. We also discuss several problems that the subjects faced when using ADD.

show abstract

Section: Attribute Driven Design (Add) Methodsmentioning

confidence: 99%

Section: Add Issues Faced By Subjectsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Exploring How the Attribute Driven Design Method Is Perceived

Alí

Solís²

2014

Relating System Quality and Software Architecture

View full text Add to dashboard Cite

show abstract

“…The tactics will be used in determining architectural models. The approach is based on the classic software architecture development process proposed by Software Engineering Institute [3] [4]. In the literature different solutions are proposed in the field.…”

Section: Introductionmentioning

confidence: 99%

A Quality Attributes Approach to Defining Reactive Systems Solution Applied to Cloud of Sensors

Skowronski¹,

Werewka

2015

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Reactive systems have been investigated and used for a long time. Due to new methods and new technology development, the reactive systems needs their redefinition. These systems are currently an interesting topic for IT (Information Technology) solution providers. In this paper the authors try to define a new view of the architecture of reactive systems, because reactive systems are evolving and there is no clear definition of them. The starting point of the investigation was the reactive manifesto which defines reactive systems by four main features (quality attributes): responsiveness, resilience, elasticity and message driven interoperability. The mentioned quality attributes are the basis for developing a system solution. For each of the quality attributes, a set of tactics are proposed to maintain attribute required behavior. The suitability of the proposed tactics was investigated for Reactive Sensor Middleware which is part of a CoS (Cloud of Sensors) in the PaaS (Platform as a Service) layer. A cloud of sensors for pollution monitoring in urban areas was used as an example. Verification of the tactics has confirmed that some of the proposed tactics are suitable for the selected CoS subsystem.

show abstract