Argumentation-based design rationale: what use at what cost?
International Journal of Human-Computer Studies
Correct Architecture Refinement
IEEE Transactions on Software Engineering - Special issue on software architecture
Use case maps for object-oriented systems
Use case maps for object-oriented systems
Design rationale: concepts, techniques, and use
Design rationale: concepts, techniques, and use
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
BCOOPL: Basic concurrent object-oriented programming language
Software—Practice & Experience
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Exploring Alternatives During Requirements Analysis
IEEE Software
An Event-Based Architecture Definition Language
IEEE Transactions on Software Engineering
Documenting and Analyzing a Context-Sensitive Design Space
WICSA 3 Proceedings of the IFIP 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance
Attribute-Based Architecture Styles
WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
Quality management activities for software architecture and software architecture process
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models
Models in Software Engineering
Proceedings of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications
Flexible and expressive composition rules with aspect-oriented use case maps (AoUCM)
Proceedings of the 10th international conference on Early aspects: current challenges and future directions
Using planning techniques to assist quality-driven architectural design exploration
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Structuring agents for adaptation
Adaptive agents and multi-agent systems
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
An exploratory study of architectural effects on requirements decisions
Journal of Systems and Software
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Towards a quality meta-model for information systems
Software Quality Control
Using model transformation techniques for the superimposition of architectural styles
ECSA'11 Proceedings of the 5th European conference on Software architecture
| Hi-index | 0.00 |
This paper discusses an approach for the top-down composition of software architectures. First, an architecture is derived that addresses functional requirements only. This architecture contains a number of variability points which are next filled in to address quality concerns. The quality requirements and associated architectural solution fragments are captured in a so-called feature-solution (FS) graph. The solution fragments captured in this graph are used to iteratively compose an architecture driven by quality requirements. Our versatile composition technique allows for pre- and post-refinements, refinements that involve multiple variability points, and functionality extensions. In addition, the usage of the FS-graph supports aspect-oriented programming at the architecture level.