Search results
Results from the WOW.Com Content Network
An architectural decision captures the result of a conscious, often collaborative option selection process and provides design rationale for the decision making outcome, e.g., by referencing one or more of the quality attributes addressed by the architectural decision and answering "why" questions about the design and option selection ...
An alternative architectural theory based on scientific laws, as for example A Theory of Architecture is now competing with purely aesthetic theories most common in architectural academia. This entire body of work can be seen as balancing and often questioning design movements that rely primarily upon aesthetics and novelty.
Choice architecture is the design of different ways in which choices can be presented to decision makers, and the impact of that presentation on decision-making. For example, each of the following: the number of choices presented [1] the manner in which attributes are described [2] the presence of a "default" [3] [4] can influence consumer choice.
A set of architectural design decisions: software architecture should not be considered merely a set of models or structures, but should include the decisions that lead to these particular structures, and the rationale behind them. [10] This insight has led to substantial research into software architecture knowledge management. [11]
Decisions of when and how to engage in an intervention are critical to the ultimate conservation-restoration of cultural heritage. Ultimately, the decision is value based: a combination of artistic, contextual, and informational values is normally considered. In some cases, a decision to not intervene may be the most appropriate choice.
A design rationale is the explicit listing of decisions made during a design process, and the reasons why those decisions were made. [2] Its primary goal is to support designers by providing a means to record and communicate the argumentation and reasoning behind the design process. [3] It should therefore include: [4] the reasons behind a ...
Architecturally significant requirements are used in software design to drive and justify architectural decisions; if not satisfied properly, they contribute to the accumulation of technical debt. For instance, failure to meet security and compliance requirements complicates the system and process assurance audits and increases the risk of ...
These scenarios are then used in conjunction with architectural approaches and architectural decisions to create an analysis of trade-offs, sensitivity points, and risks (or non-risks). This analysis can be converted to risk themes and their impacts whereupon the process can be repeated.