Loading [MathJax]/extensions/tex2jax.js

Rationale as a by-product

Research output: Chapter in book/report/conference proceeding › Contribution to book/anthology › Research › peer review

Authors

Research Organisations

Details

Original languageEnglish
Title of host publicationRationale Management in Software Engineering
Pages91-109
Number of pages19
Publication statusPublished - 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.

Keywords

    by-product, capturing rationale, FOCUS, task-specific path

ASJC Scopus subject areas

Cite this

Rationale as a by-product. / Schneider, Kurt.
Rationale Management in Software Engineering. 2006. p. 91-109.

Research output: Chapter in book/report/conference proceeding › Contribution to book/anthology › Research › peer review

Schneider, K 2006, Rationale as a by-product. in Rationale Management in Software Engineering. pp. 91-109. https://doi.org/10.1007/978-3-540-30998-7_4
Schneider, K. (2006). Rationale as a by-product. In Rationale Management in Software Engineering (pp. 91-109) https://doi.org/10.1007/978-3-540-30998-7_4
Schneider K. Rationale as a by-product. In Rationale Management in Software Engineering. 2006. p. 91-109 doi: 10.1007/978-3-540-30998-7_4
Schneider, Kurt. / Rationale as a by-product. Rationale Management in Software Engineering. 2006. pp. 91-109
Download
@inbook{ed3e994f44c44c0faef5f12bcfc249cb,
title = "Rationale as a by-product",
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.",
keywords = "by-product, capturing rationale, FOCUS, task-specific path",
author = "Kurt Schneider",
year = "2006",
doi = "10.1007/978-3-540-30998-7_4",
language = "English",
isbn = "3540309977",
pages = "91--109",
booktitle = "Rationale Management in Software Engineering",

}

Download

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 -

By the same author(s)