Rationale-based software engineering

Janet E. Burge, John Carroll, Raymond McCall, Ivan Mistrik

Research output: Book/ReportBook

55 Citations (Scopus)

Abstract

Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. Burge, Carroll, McCall, and Mistrík describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the first comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.

Original languageEnglish (US)
PublisherSpringer Berlin Heidelberg
Number of pages316
ISBN (Print)9783540775829
DOIs
StatePublished - Jan 1 2008

Fingerprint

Software engineering
Decision making
Terminology
Testing

All Science Journal Classification (ASJC) codes

  • Computer Science(all)

Cite this

Burge, J. E., Carroll, J., McCall, R., & Mistrik, I. (2008). Rationale-based software engineering. Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-540-77583-6
Burge, Janet E. ; Carroll, John ; McCall, Raymond ; Mistrik, Ivan. / Rationale-based software engineering. Springer Berlin Heidelberg, 2008. 316 p.
@book{9c05eb5513c0419392616452142afcc7,
title = "Rationale-based software engineering",
abstract = "Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. Burge, Carroll, McCall, and Mistr{\'i}k describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the first comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.",
author = "Burge, {Janet E.} and John Carroll and Raymond McCall and Ivan Mistrik",
year = "2008",
month = "1",
day = "1",
doi = "10.1007/978-3-540-77583-6",
language = "English (US)",
isbn = "9783540775829",
publisher = "Springer Berlin Heidelberg",

}

Burge, JE, Carroll, J, McCall, R & Mistrik, I 2008, Rationale-based software engineering. Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-540-77583-6

Rationale-based software engineering. / Burge, Janet E.; Carroll, John; McCall, Raymond; Mistrik, Ivan.

Springer Berlin Heidelberg, 2008. 316 p.

Research output: Book/ReportBook

TY - BOOK

T1 - Rationale-based software engineering

AU - Burge, Janet E.

AU - Carroll, John

AU - McCall, Raymond

AU - Mistrik, Ivan

PY - 2008/1/1

Y1 - 2008/1/1

N2 - Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. Burge, Carroll, McCall, and Mistrík describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the first comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.

AB - Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. Burge, Carroll, McCall, and Mistrík describe in detail the capture and use of design rationale in software engineering to improve the quality of software. Their book is the first comprehensive and unified treatment of rationale usage in software engineering. It provides a consistent conceptual framework and a unified terminology for comparing, contrasting and combining the myriad approaches to rationale in software engineering. It is both an excellent introductory text for those new to the field and a uniquely valuable reference for experienced rationale researchers. The book covers the use of rationale for decision making throughout the software lifecycle, starting from the first decisions in a project and continuing through requirements definition, design, implementation, testing, maintenance, redesign and reuse.

UR - http://www.scopus.com/inward/record.url?scp=84889788824&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84889788824&partnerID=8YFLogxK

U2 - 10.1007/978-3-540-77583-6

DO - 10.1007/978-3-540-77583-6

M3 - Book

AN - SCOPUS:84889788824

SN - 9783540775829

BT - Rationale-based software engineering

PB - Springer Berlin Heidelberg

ER -

Burge JE, Carroll J, McCall R, Mistrik I. Rationale-based software engineering. Springer Berlin Heidelberg, 2008. 316 p. https://doi.org/10.1007/978-3-540-77583-6