Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Design Rules: The Power of Modularity Volume 1
Design Rules: The Power of Modularity Volume 1
Modularisation and composition of aspectual requirements
Proceedings of the 2nd international conference on Aspect-oriented software development
Theme: An Approach for Aspect-Oriented Analysis and Design
Proceedings of the 26th International Conference on Software Engineering
ASAAM: Aspectual Software Architecture Analysis Method
WICSA '04 Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture
An analysis of modularity in aspect oriented design
Proceedings of the 4th international conference on Aspect-oriented software development
IEEE Software
Modules for crosscutting models
Ada-Europe'03 Proceedings of the 8th Ada-Europe international conference on Reliable software technologies
Identifying, Assigning, and Quantifying Crosscutting Concerns
ACoM '07 Proceedings of the First International Workshop on Assessment of Contemporary Modularization Techniques
Requirements traceability in model-driven development: Applying model and transformation conformance
Information Systems Frontiers
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
Mapping connection templates to spring aspects to integrate business rules
Proceedings of the 2011 international workshop on Early aspects
| Hi-index | 0.00 |
Traceability of requirements and concerns enhances the quality of software development. We use trace relations to define crosscutting. As starting point, we set up a dependency matrix to capture the relationship between elements at two levels, e.g. concerns and representations of concerns. The definition of crosscutting is formalized in terms of linear algebra, and represented with matrices and matrix operations. In this way, crosscutting can be clearly distinguished from scattering and tangling. We apply this approach to the identification of crosscutting across early phases in the software life cycle, based on the transitivity of trace relations. We describe an illustrative case study to demonstrate the applicability of the analysis.