2007
DOI: 10.1016/j.aei.2006.11.002
|View full text |Cite
|
Sign up to set email alerts
|

Classifying architectural constraints as a basis for software quality assessment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2009
2009
2020
2020

Publication Types

Select...
3
3

Relationship

2
4

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 15 publications
0
3
0
Order By: Relevance
“…The use of styles in architecture design implies certain properties of software systems, as these styles are abstractions of successfully implemented systems that are usually easy to understand, to manage, or to maintain [12,13]. Non-functional quality aspects ranging from availability, performance, and maintainability guarantees to costs are equally important functional aspects of components and need to be captured explicitly to clearly state the quality requirements.…”
Section: Quality-driven Architecturementioning
confidence: 99%
See 1 more Smart Citation
“…The use of styles in architecture design implies certain properties of software systems, as these styles are abstractions of successfully implemented systems that are usually easy to understand, to manage, or to maintain [12,13]. Non-functional quality aspects ranging from availability, performance, and maintainability guarantees to costs are equally important functional aspects of components and need to be captured explicitly to clearly state the quality requirements.…”
Section: Quality-driven Architecturementioning
confidence: 99%
“…The architecture influences a broad variety of properties such as the maintainability, dependability or the performance of a system [10]. While architecture description languages (ADLs) exist [22], these are not always suitable to support rich conceptual modelling of architectures [12]. Only a few, such as ACME [10], support the abstraction of architectures into styles or patterns.…”
Section: Introductionmentioning
confidence: 99%
“…In this paper, we will use the terms "design patterns" for lower-level artifacts, and "architectural styles" for higher-level artifacts, except when explicitly discussing differences between both concepts. A taxonomy of these concepts and other types of architectural constraints is presented in [23]. Figure 1 shows an overview of our view of the relationship of architectural styles to other concepts of software architecture, which applies to all the usages we identified.…”
Section: Architectural Styles Patterns and Their Usagementioning
confidence: 99%