Theme: an approach for aspect-oriented analysis and design
By E. Baniassad, Siobhán Clarke. Proceedings. 26th International Conference on Software Engineering, 2004
350 citations recorded by the source corpus.
Aspects are behaviours that are tangled and scattered across a system. In requirements documentation, aspects manifest themselves as descriptions of behaviours that are intertwined, and woven throughout. Some aspects may be obvious, as specifications of typical crosscutting behaviour. Others may be more subtle, making them hard to identify. In either case, it is difficult to analyse requirements to locate all points in the system where aspects should be applied. These issues lead to problems achieving traceability of aspects throughout the development lifecycle. To identify aspects early in the software lifecycle, and establish sufficient traceability, developers need support for aspect identification and analysis in requirements documentation. To address this, we have devised the Theme approach for viewing the relationships between behaviours in a requirements document, identifying and isolating aspects in the requirements, and modelling those aspects using a design language. This paper describes the approach, and illustrates it with a case study and analysis.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/3194c8f273ef6021a4c4f4656a820ac440d91fc1
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
In Information Systems
Citations in the corpus
- Research Directions in Requirements Engineering (2007, methodology): “Evaluation Elicitation [42, 39, 94] Negotiation [75] Air traffic control [98, 158] Aspects [12] Viewpoints [53] Security [151] Semantic web ontologies [49] User interfaces [15] Inspection methods [118] RE payoff [38, 54] Requirements evolution [7, 95] Risk management [59] Cost estimation in web app.”
- Model-driven Development of Complex Software: A Research Roadmap (2007, background): “Approaches in the second category (e.g., see [1, 5 , 12, 23, 47]) focus more on providing support for separating concerns at higher levels of abstractions.”