<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-22T21:25:27Z</responseDate>
  <request identifier="860" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:860</identifier>
        <datestamp>2024-03-06T11:07:03Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>A Taxonomy of Aspects in Terms of Crosscutting Concerns</dc:title>
          <dc:creator>Fox, Jorge</dc:creator>
          <dc:subject>Aspect-orientation</dc:subject>
          <dc:subject>Software Engineering</dc:subject>
          <dc:subject>Taxonomy</dc:subject>
          <dc:description>Aspect-orientation provides support for " Separation of Concerns"&#13;
by means of techniques that first isolate and then weave concerns.&#13;
Most work in aspect-orientation has achieved such goals at the programming&#13;
level, even also at the modeling level. Though, in some cases the&#13;
application of these techniques is independent of the problem itself. In&#13;
other words, the techniques for weaving either code or models are in&#13;
principle applicable to a number of problems without a clear criterion&#13;
to answer questions like: in what software processes we may actually&#13;
discuss aspect-orientation? This also brings other questions: what do we&#13;
consider an aspect?, how do we deal with it?, are aspects crosscutting&#13;
concerns? The first notions of aspect-orientation relate to crosscutting in&#13;
code. We consider this a bottom-up approach. We believe though, that&#13;
aspect-orientation can be better understood from an architectural perspective.&#13;
We call this a top-down approach. We explore the question of&#13;
''what makes an aspect an aspect" and '' when do aspects arise" from&#13;
a top-down perspective. This work relates to a definition of aspects in&#13;
terms of requirements traceability, proposes a classification, and altogether&#13;
a taxonomy.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Jorge Fox</dc:contributor>
          <dc:date>2007</dc:date>
          <dc:relation>Is Part Of Dagstuhl Seminar Proceedings, Volume 6351, Methods for Modelling Software Systems (MMOSS) (2007)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/DagSemProc.06351.5</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-8603</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.06351.5</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
