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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4.2. The chosen research and validation methods<br />

Table 4.2: Case Study Verification<br />

Research Questions<br />

Evidence Collected<br />

1. Is design rationale important Statistical Results<br />

in architecture development?<br />

2. Is design rationale important<br />

in system maintenance?<br />

3. What is the current state of practice of<br />

design rationale in the software industry?<br />

4. How to improve the representation Evaluation Results<br />

of design rationale in architecture development?<br />

Expert Opinion<br />

5. How to implement traceability between requirements, Demonstration / Implementation<br />

architecture design elements and design rationale?<br />

6. How to estimate change impacts using Demonstration / Implementation<br />

architecture design elements and design rationale?<br />

ture design. The resulting method characterises the relationship between design elements<br />

and design rationales. A proof-of-concept tool set has been developed to accompany the<br />

method and it overcomes the usability issues identified in Table 3.1. Using an empirical<br />

study, this new method is compared with using the traditional design specifications to<br />

examine their effectiveness in design reasoning. Domain experts are asked to evaluate<br />

the two methods to determine whether design rationale could help them understand and<br />

reason with the system design. The case study used in this research is an Electronic Fund<br />

Transfer System (EFT) which processes inter-bank fund transfers <strong>for</strong> The People’s Bank<br />

of China in Guangzhou (PBC-GZ). The system was in production between 1998 and May<br />

2006. It was originally designed by the author who led a team of architects and designers<br />

using traditional waterfall software development methodology. A rationale-<strong>based</strong> model is<br />

reconstructed <strong>for</strong> the EFT system to capture the missing design rationale. Its validation<br />

is reported in Chapter 7.<br />

For questions 5 and 6, we resolve the problems using traceability and Bayesian Belief<br />

Networks methods. Based on the case study examples, we demonstrate the applications<br />

in both research questions.<br />

The architecture design rationale models presented in this thesis are early conceptual<br />

models to integrate design rationale into architecture development. As such, the research<br />

settings are to test the feasibility of the research concepts, characterise the design rationale<br />

problem and then propose methods to address the issues. The validity of the conceptual<br />

models is there<strong>for</strong>e limited to demonstrating that such an approach is feasible and likely to<br />

be useful. Like most software engineering research projects, the real success of this work<br />

can only be tested and validated through its continuous applications and improvements<br />

in industrial projects, which is beyond the scope of this thesis.<br />

50

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

Saved successfully!

Ooh no, something went wrong!