Software architecture can be seen as a decision making process; it involves making the right
decisions at the right time. Typically, these design decisions are not explicitly represented in …

Despite recent advancements in software architecture knowledge management and design
rationale modeling, industrial practice is behind in adopting these methods. The lack of …

Abstract Design Rationale (DR), the reasons behind decisions made while designing, offers
a richer view of both the product and the decision-making process by providing the …

For a number of years, members of the Artificial Intelligence (AI) in Design community have
studied Design Rationale (DR), the reasons behind decisions made while designing. DR is …

One goal of design rationale systems is to support designers by providing a means to record
and communicate the argumentation and reasoning behind the design process. However …

Rationale is the justification behind decisions. It is captured and used in many different forms
during software engineering. While it has not achieved widespread use in practice, several …

Many decisions have to be made when developing a software system and a successful
outcome depends on how well thought out these decisions were. One way that the decisions …

Traditionally, software architecture is seen as the result of the software architecture design
process, the solution, usually represented by a set of components and connectors. Recently …

Methods of representing and capturing design rationale have been studied in past years.
Many meta-models, methods and techniques have been proposed. Are these software …

There is growing recognition of the importance of documenting and managing background
knowledge about architecture design decisions. However, there is little guidance on the …