A web-based tool for managing architectural design decisions
ACM SIGSOFT Software Engineering Notes
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Software architecting without requirements knowledge and experience: What are the repercussions?
Journal of Systems and Software
Extending Software Architecting Processes with Decision-Making Activities
Balancing Agility and Formalism in Software Engineering
On the Role of Architectural Design Decisions in Software Product Line Engineering
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
A comparative study of architecture knowledge management tools
Journal of Systems and Software
Viability for codifying and documenting architectural design decisions with tool support
Journal of Software Maintenance and Evolution: Research and Practice
Architectural knowledge: getting to the core
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
An exploratory study of architectural effects on requirements decisions
Journal of Systems and Software
Impediments to requirements-compliance
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Towards decision centric repository of architectural knowledge
CEE-SET'09 Proceedings of the 4th IFIP TC 2 Central and East European conference on Advances in Software Engineering Techniques
Processes for creating and exploiting architectural design decisions with tool support
ECSA'07 Proceedings of the First European conference on Software Architecture
| Hi-index | 0.00 |
The architecture of a software system is a key asset for a software business. While there are several architecting and evaluation methods, literature and practice are devoid of architecture-centric concernanalysis (ACCA) methods analogous to causal analysis methods for software defects. A concern is any aspect of an architecture considered undesirable. This paper describes an ACCA method which uses at its core a Concern Traceability map (CT-map) that captures architectural design decisions starting from software requirements and links them to identified architectural concerns. The CT-map essentially forms a net of design decisions, sandwiched between requirements and architectural concerns. Analysis of the root causes of a concern is then conducted on the CT-map. The ACCA method is empirically validated through a case study on a sizeable architecture of a banking application.