Loading...
Please wait, while we are loading the content...
Similar Documents
Sharing and reusing architectural knowledge- architecture, rationale, and design intent.
| Content Provider | CiteSeerX |
|---|---|
| Author | Avgeriou, Paris Lago, Patricia Grisham, Paul Perry, Dewayne |
| Abstract | The shift of the software architecture community towards architectural knowledge has brought along some promising research directions. In this workshop we discuss the issues that lead to the application of architectural knowledge in research and industrial practice as well as presenting ongoing research and new ideas to advance the field. We expect to examine the state of the art and practice and gauge future challenges and trends. This year’s workshop has a strong emphasis on documenting, sharing, and reusing architectural rationale and design intent. 1. Theme and goals Software architecture plays an important role in managing the complex interactions and dependencies between stakeholders and providing a central artifact that can be used for reference. Current research trends in software architecture focus on the treatment of architectural decisions as first-class entities and their explicit representation in architectural documentation. From this point of view, a software system’s architecture is no longer perceived as interacting components and connectors only, but also as a set of architectural decisions that convey the architectural principles underlying a particular design [1] [3]. This new paradigm is a response to current design practices that fail to document design decisions and their underlying rationale. The consequences of the lack of architectural decisions are well known in the software industry: expensive system evolution; poor stakeholder communication; limited reusability of architectural assets; and poor traceability between requirements, architecture and implementation. The focus of this workshop is on current software engineering approaches that attempt to tackle this |
| File Format | |
| Access Restriction | Open |
| Subject Keyword | Design Intent Architectural Decision Architectural Knowledge Architecture Architectural Knowledge Important Role Explicit Representation Current Design Practice Architectural Documentation Interacting Component Current Software Engineering Approach Limited Reusability Software Architecture Focus Current Research Trend Gauge Future Challenge Particular Design Poor Stakeholder Communication Complex Interaction New Paradigm Central Artifact Poor Traceability Software System Architecture Underlying Rationale New Idea Architectural Principle Expensive System Evolution Software Industry Strong Emphasis Year Workshop Design Decision Industrial Practice First-class Entity Goal Software Architecture Promising Research Direction Architectural Asset Architectural Rationale Software Architecture Community |
| Content Type | Text |
