A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
6.2. <strong>Architecture</strong> <strong>Rationale</strong> and Elements Linkage (AREL)<br />
as an architecture element, to show its influence on a decision. This is similar to a goal in<br />
DRL.<br />
A decision creates and is justified by the architecture design rationale, similar to the<br />
argument in REMAP. The architecture rationale encapsulates the details of the justification.<br />
It contains a description of the issues addressed by the decision, the arguments<br />
<strong>for</strong> and against an option, and the alternative options that have been considered. Once<br />
a decision is made, the result of a decision is a design outcome or solution. A design<br />
outcome should be explicitly represented in the architecture design as an architecture<br />
element. Although this conceptual model has similarities, such as the representation of<br />
design rationale and design issues, to other design rationale models, it is unique because<br />
it simplifies the argumentation aspect and strengthens the linkage between motivational<br />
reasons, design rationale and design elements. This subject is further discussed in Section<br />
6.2.<br />
6.2 <strong>Architecture</strong> <strong>Rationale</strong> and Elements Linkage (AREL)<br />
The AREL model is an implementation of the conceptual model using the UML notation<br />
[118, 113]. AREL is an acyclic graph which relates architecture elements AEs to architecture<br />
rationale ARs using directional links ARtrace. An AE is an architecture element<br />
that participates in a decision as an input (i.e. motivational reason) or an outcome (i.e.<br />
design outcome). They are stereotyped by ≪AE≫. An AR encapsulates the architecture<br />
design justification of a decision. ARs are stereotyped by ≪AR≫. Since AR has a oneto-one<br />
relationship to justify a decision, AR can there<strong>for</strong>e represent a decision point in<br />
AREL modelling. The relationships between an AE and an AR are connected by a directional<br />
association stereotyped ≪ARtrace≫. It is also referred to as a links in the AREL<br />
definition below. The ≪ARtrace≫ stereotype is used to represent the causal relationships<br />
between AEs and ARs. A causal relationship is a relationship between two entities where<br />
AE is a cause and AR is the effect. For instance, a motivational reason causes a decision<br />
to be made. Alternatively, AR is a cause and AE is an effect. For instance, a decision<br />
causes a design object to be created as an effect.<br />
Definition 1 An <strong>Architecture</strong> <strong>Rationale</strong> and Element Linkage (AREL) model is a tuple<br />
(AE, AR, P L), where AE is a set of nodes representing architecture elements, AR is a set<br />
of nodes representing architecture rationales, and P L ⊆ (AE × AR) ∪ (AR × AE) is a set<br />
of directed links between the nodes, such that<br />
1. all rationale nodes must be associated by links with at least one cause and one effect:<br />
84