Home > Research > Publications & Outputs > Driving and managing architectural decisions wi...
View graph of relations

Driving and managing architectural decisions with aspects

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Published

Standard

Driving and managing architectural decisions with aspects. / Garcia, Alessandro; Batista, Thais; Rashid, Awais et al.
In: Software Engineering Notes, Vol. 31, No. 5, 6, 09.2006.

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Harvard

Garcia, A, Batista, T, Rashid, A & Sant'Anna, C 2006, 'Driving and managing architectural decisions with aspects', Software Engineering Notes, vol. 31, no. 5, 6. <http://dl.acm.org/citation.cfm?id=1163514.1178646>

APA

Garcia, A., Batista, T., Rashid, A., & Sant'Anna, C. (2006). Driving and managing architectural decisions with aspects. Software Engineering Notes, 31(5), Article 6. http://dl.acm.org/citation.cfm?id=1163514.1178646

Vancouver

Garcia A, Batista T, Rashid A, Sant'Anna C. Driving and managing architectural decisions with aspects. Software Engineering Notes. 2006 Sept;31(5):6.

Author

Garcia, Alessandro ; Batista, Thais ; Rashid, Awais et al. / Driving and managing architectural decisions with aspects. In: Software Engineering Notes. 2006 ; Vol. 31, No. 5.

Bibtex

@article{74e80974939c41b99029350f986f901f,
title = "Driving and managing architectural decisions with aspects",
abstract = "Software architects face decisions every day which have a broadly-scoped impact on the software architecture. These decisions are the core of the architecting process as they typically have implications in a multitude of architectural elements and views. Without an explicit representation and management of those crucial choices, architects cannot properly communicate and reason about them and their crosscutting effects. The result is a number of architectural breakdowns, such as decreased evolvability, time-consuming trade-off analysis, and unmanageable traceability. Aspects are a natural way to capture widely-scoped architectural decisions and promote software architectures with superior modularity.",
author = "Alessandro Garcia and Thais Batista and Awais Rashid and Claudio Sant'Anna",
year = "2006",
month = sep,
language = "English",
volume = "31",
journal = "Software Engineering Notes",
number = "5",

}

RIS

TY - JOUR

T1 - Driving and managing architectural decisions with aspects

AU - Garcia, Alessandro

AU - Batista, Thais

AU - Rashid, Awais

AU - Sant'Anna, Claudio

PY - 2006/9

Y1 - 2006/9

N2 - Software architects face decisions every day which have a broadly-scoped impact on the software architecture. These decisions are the core of the architecting process as they typically have implications in a multitude of architectural elements and views. Without an explicit representation and management of those crucial choices, architects cannot properly communicate and reason about them and their crosscutting effects. The result is a number of architectural breakdowns, such as decreased evolvability, time-consuming trade-off analysis, and unmanageable traceability. Aspects are a natural way to capture widely-scoped architectural decisions and promote software architectures with superior modularity.

AB - Software architects face decisions every day which have a broadly-scoped impact on the software architecture. These decisions are the core of the architecting process as they typically have implications in a multitude of architectural elements and views. Without an explicit representation and management of those crucial choices, architects cannot properly communicate and reason about them and their crosscutting effects. The result is a number of architectural breakdowns, such as decreased evolvability, time-consuming trade-off analysis, and unmanageable traceability. Aspects are a natural way to capture widely-scoped architectural decisions and promote software architectures with superior modularity.

M3 - Journal article

VL - 31

JO - Software Engineering Notes

JF - Software Engineering Notes

IS - 5

M1 - 6

ER -