Analysis of crosscutting across software development phases based on traceability

Klaas van den Berg, J.M. Conejero, J. Hernández

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    13 Citations (Scopus)

    Abstract

    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.
    Original languageUndefined
    Title of host publicationEarly Aspects at ICSE2006: Workshop in Aspect-Oriented Requirements Engineering and Architecture Design
    Place of PublicationNew York, NY, USA
    PublisherACM Press
    Pages43-50
    Number of pages8
    ISBN (Print)1-59593-405-7
    DOIs
    Publication statusPublished - 21 May 2006
    EventEarly Aspects at ICSE2006: Workshop in Aspect-Oriented Requirements Engineering and Architecture Design - Shanghai, China
    Duration: 21 May 200621 May 2006

    Publication series

    Name
    PublisherACM Press
    Number06EX1382C

    Workshop

    WorkshopEarly Aspects at ICSE2006: Workshop in Aspect-Oriented Requirements Engineering and Architecture Design
    Period21/05/0621/05/06
    Other21 May 2006

    Keywords

    • traceability
    • EWI-9079
    • IR-63915
    • Cross-cutting Concerns
    • METIS-237912
    • Aspect-Oriented Software Development
    • Scattering
    • Tangling
    • Crosscutting

    Cite this