Home  About us  Contact
 

Architecture Practice (architecture + practice)

Distribution by Scientific Domains
Information Science and Computing100%

Selected Abstracts

Information Architecture Practice: An Interview with Gayle Curtis, Modem Media

BULLETIN OF THE AMERICAN SOCIETY FOR INFORMATION SCIENCE & TECHNOLOGY (ELECTRONIC), Issue 6 2000
Irene L. Travis Editor
No abstract is available for this article. [source]

Information Architecture Practice: An Interview with Seth Gordon, ZEFER

BULLETIN OF THE AMERICAN SOCIETY FOR INFORMATION SCIENCE & TECHNOLOGY (ELECTRONIC), Issue 6 2000
Irene L. Travis Editor
No abstract is available for this article. [source]

Information Architecture Practice: An Interview with Steven Ritchey, Sapient

BULLETIN OF THE AMERICAN SOCIETY FOR INFORMATION SCIENCE & TECHNOLOGY (ELECTRONIC), Issue 6 2000
Irene L. Travis Editor
No abstract is available for this article. [source]

Viability for codifying and documenting architectural design decisions with tool support

JOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 2 2010
Rafael Capilla
Abstract Current software architecture practices have been focused on modeling and documenting the architecture of a software system by means of several architectural views. In practice, the standard architecture documentation lacks explicit description of the decisions made and their underlying rationale, which often leads to knowledge loss. This fact strongly affects the maintenance activities as we need to spend additional effort to replay the decisions made as well as to understand the changes performed in the design. Hence, codifying this architectural knowledge is a challenging task that requires adequate tool support. In this research, we test the capabilities of Architecture Design Decision Support System (ADDSS), a web-based tool for supporting the creation, maintenance, use, and documentation of architectural design decisions (ADD) with their architectures. We used ADDSS to codify architectural knowledge and to maintain those trace links between the design decisions and other software artefacts that would help in the maintenance operations. We illustrate the usage of the tool through four different experiences and discuss the potential benefits of using this architectural knowledge and its impact on the maintenance and evolution activities. Copyright © 2009 John Wiley & Sons, Ltd. [source]