FG Praktische Informatik / Softwaresystemtechnik
Refine
Year of publication
- 2014 (2)
Document Type
Language
- English (2)
Keywords
- Capture (2) (remove)
Institute
More than thirty years of research on the topic of design rationale (DR) have passed. However, as of today there are just some exceptional cases where DR are applied in industrial practise. Researchers analysed them for its nature, its structure, its quality, and for analyses to be performed on them. The results showed that DR have the potential to sustainably contribute to the product life cycle in terms of product design, product re-design, product testing, maintenance, and product quality. Hence, this paper presents a proposal to tackle the lack DR usage in documenting software architectures. We strive to promote the use of DR for designing software architectures. Therefore, as a complement to the numerous approaches to formalise the representation of DR, this paper is proposing to pay more attention on research how to capture rationale. In short, within this paper we introduce the topic of DR, related research and elaborate on the intended research on the topic of DR capture.
Over the last thirty years many research has been conducted to capture the ”how” and ”why” behind design decisions. This information is known as design rationales (DR). Approaches to capture, store, preserve, and use DR have emerged from research activities. However, as of today they only found exceptional application within industrial practice. Rationales have been analysed in respect to its nature, its structure, and its quality. Additionally, some researchers performed analyses on them. They found out that DR have the potential to sustainably contribute to design, re-design, testing, maintenance, and improving product quality over the whole product-life cycle. Within this paper a research proposal is presented striving to tackle the exceptional use of DR in software documentation. We want to promote the capture of DR by paying more attention on the questions ”What information has to be captured by rationales?”, ”How detailed should the captured information be?”, and ”How should rationale capture be integrated into the development process?”. It is the goal to promote the use of DR within the whole software development process. In short, within this paper we introduce the topic of DR, related research and elaborate on the intended research on the topic of DR capture.