Details
| Originalsprache | Englisch |
|---|---|
| Titel des Sammelwerks | Rationale Management in Software Engineering |
| Seiten | 91-109 |
| Seitenumfang | 19 |
| Publikationsstatus | Veröffentlicht - 2006 |
Abstract
Rationale is an asset in software engineering. Rationale is communicated during several project activities, like design or prototyping. Nevertheless, very little rationale is captured today. There seems a s to be an inherent tension between creating or externalizing rationale, and capturing it successfully. In this chapter, the "Rationale as a By-Product Approach" is defined through seven principles. Those principles were identified while building two applications. In both, tools were tailor-made to support capturing design rationale on the side while working on software project tasks as usual. The approach is best applied to project tasks that create or elicit a lot of rationale.
ASJC Scopus Sachgebiete
Zitieren
- Standard
- Harvard
- Apa
- Vancouver
- BibTex
- RIS
Rationale Management in Software Engineering. 2006. S. 91-109.
Publikation: Beitrag in Buch/Bericht/Sammelwerk/Konferenzband › Beitrag in Buch/Sammelwerk › Forschung › Peer-Review
}
TY - CHAP
T1 - Rationale as a by-product
AU - Schneider, Kurt
PY - 2006
Y1 - 2006
N2 - Rationale is an asset in software engineering. Rationale is communicated during several project activities, like design or prototyping. Nevertheless, very little rationale is captured today. There seems a s to be an inherent tension between creating or externalizing rationale, and capturing it successfully. In this chapter, the "Rationale as a By-Product Approach" is defined through seven principles. Those principles were identified while building two applications. In both, tools were tailor-made to support capturing design rationale on the side while working on software project tasks as usual. The approach is best applied to project tasks that create or elicit a lot of rationale.
AB - Rationale is an asset in software engineering. Rationale is communicated during several project activities, like design or prototyping. Nevertheless, very little rationale is captured today. There seems a s to be an inherent tension between creating or externalizing rationale, and capturing it successfully. In this chapter, the "Rationale as a By-Product Approach" is defined through seven principles. Those principles were identified while building two applications. In both, tools were tailor-made to support capturing design rationale on the side while working on software project tasks as usual. The approach is best applied to project tasks that create or elicit a lot of rationale.
KW - by-product
KW - capturing rationale
KW - FOCUS
KW - task-specific path
UR - http://www.scopus.com/inward/record.url?scp=35148832963&partnerID=8YFLogxK
U2 - 10.1007/978-3-540-30998-7_4
DO - 10.1007/978-3-540-30998-7_4
M3 - Contribution to book/anthology
AN - SCOPUS:35148832963
SN - 3540309977
SN - 9783540309970
SP - 91
EP - 109
BT - Rationale Management in Software Engineering
ER -