21.01.2014 Views

A Rationale-based Model for Architecture Design Reasoning

A Rationale-based Model for Architecture Design Reasoning

A Rationale-based Model for Architecture Design Reasoning

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

viewpoints are functional requirements, non-functional requirements, in<strong>for</strong>mation<br />

system environment, business environment and technical environment.<br />

Users may select all of the viewpoints or selected viewpoints. The AREL tool<br />

would retrieve only those elements which viewpoints have been included.<br />

The trace actions dictate whether the traceability is to be <strong>for</strong>ward tracing, backward<br />

tracing or both. In <strong>for</strong>ward tracing, only those AEs and ARs which are downwards<br />

from the specified AE element are retrieved. In the backward tracing, only those<br />

AEs and ARs which are upwards from the specified AE are retrieved. When Both<br />

are specified, then all upwards and downwards AEs and ARs are retrieved.<br />

On completion of the trace the following screen is displayed (Figure 7).<br />

Figure 7 – message screen after tracing is complete<br />

The result of the tracing is to create an UML graph which is stored in the same<br />

EAP repository as the AREL model. The trace results are located in the Use Case<br />

Package under Use Case <strong>Model</strong> with the name of Traceability Graph.<br />

Figure 8 – An example of an AREL model<br />

If Figure 8 is the original AREL model, a downward trace of AE2 would result in a<br />

graph such as the one in Figure 9. An upward trace of AE2 would result in a graph<br />

such as the one in Figure 10. Traceability of both directions would result in a graph<br />

such as the one in Figure 11.<br />

233

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!