Tool Support for Architectural Decisions

Jansen, Anton; Ven, J. van der; Avgeriou, Paris; Hammer, D.K.

doi:10.1109/wicsa.2007.47

Cited by 97 publications

(70 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…If we consider a system's architecture as a set of architectural decisions, the most significant ones concern the satisfaction of quality attributes (Jansen et al, 2007). The process of architectural design has been characterized as making a series of decisions that have system wide impact.…”

Section: Patterns From Nuggetsmentioning

confidence: 99%

Decision Based Development of Productline: A Quintessence Usability Approach

Balan¹,

Punithavalli²

2011

Journal of Computer Science

View full text Add to dashboard Cite

Problem statement:A well designed user interface is comprehensible and controllable, helping users to complete their work successfully and efficiently and to feel competent and satisfied. To improve the usability of a software system, usability patterns can be applied. However, there are short comes shows that the software architecture of a system restricts certain usability patterns from being modified after implementation. Several of these usability patterns are "architecture sensitive", such modifications are costly to implement due through their structural impact on the system. So we practice the pattern oriented usability design with considering the dependencies between the design decisions relevant to the product line business objects which has its impact on the usability criterion. Dependencies between the rationale decisions for the architecture sensitive usability patterns can be maintained for future reference. Approach: While going for the usability patterns, the decisions behind the pattern selection should be specified. We address the issues by analyzing the quality based models that determines the design rationale and their dependencies. We use QDK methodology to preserve the specifications of decisions and all their inter dependencies along with the knowledge rule. Results: Preserving the specifications of decisions and all their inter dependencies with knowledge rules will support the evolution and maintenance of such productline systems. Explicit evaluation of usability during architectural design prevents part of the high costs incurred by adaptive maintenance activities once the system has been implemented. Conclusion: Capturing knowledge by this means provides the basis for justification, learning and re-uses of the knowledge rules for further design decisions.

show abstract

Section: Patterns From Nuggetsmentioning

confidence: 99%

Decision Based Development of Productline: A Quintessence Usability Approach

Balan¹,

Punithavalli²

2011

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…In response to the increasing realization of the importance of providing suitable tooling support for capturing and sharing Architectural Knowledge, several researchers have developed various tools [6,8,11,19] for managing architectural knowledge and others have identified requirements with the intention of providing such tools [10]. One of the earliest tools for managing architectural knowledge is Archium, which models design decisions and their relationships with resulting components [4].…”

Section: Related Workmentioning

confidence: 99%

Tool support for automating architectural knowledge extraction

Aman-ul-haq

Babar

2009

2009 ICSE Workshop on Sharing and Reusing Architectural Knowledge

View full text Add to dashboard Cite

Development of large projects is a knowledge intensive task. Applying knowledge management techniques to project activities can enhance productivity and reduce risks of failures. However, it has been observed that knowledge management activities suffer from problems such as unavailability of structured information and lack of incentives to put extra efforts for these activities. In this paper, we present a tool that captures architectural knowledge from documents and emails and stores it in more structured manner in knowledge repositories with minimum user intervention, thus minimizing the required amount of effort.

show abstract

“…For forward engineering purposes, we have developed another approach called Archium (Jansen and Bosch, 2005;Jansen et al, 2007). The architectural decision model of Archium is very similar to the one presented in this paper (see Fig.…”

Section: Software Architecturementioning

confidence: 99%