Text
Architectural Design Decision Documentation through Reuse of Design Patterns
Software design patterns are evaluated and recognised architectural solutions for recurring design problems. They are often described in pattern
catalogues that contain known patterns for a certain application domain,
for example, patterns for object-oriented software by Gamma et al. or
patterns for distributed computing by Buschmann et al.. However, design
patterns are still often misunderstood and inappropriately applied. While
design decisions on the application of patterns involve complex trade-offs
between desired functionality and various quality properties, such decisions
are often spontaneous and do not follow a systematic process. Moreover,
documentation of such decisions and trace links to related artefacts is usually insufficient or completely omitted. Finally, even if design decisions
on pattern application are documented, there are often mistakes during the
architectural modelling of design patterns or their implementation in code.
Thus, some design decisions on the application of patterns may be misunderstood or overseen and overridden. Even worse, correction of design
decision mistakes causes costs and overhead. All these factors negatively
influence evolution of software systems.
No copy data
No other version available