D. Parnas, and P. Clements. IEEE Transactions on Software Engineering, 12 (2):
251-257(1986)
Abstract
A perfectly rational person is one who always has a good reason for what he does. Each step taken can be shown to be the best way to get to a well defined goal. Most of us like to think of ourselves as rational professionals. However, to many observers, the usual process of designing software appears quite irrational. Programmers start without a clear statement of desired behavior and implementation constraints. They make a long sequence of design decisions with no clear statement of why they do things the way they do. Their
rationale is rarely explained.
%0 Journal Article
%1 376637
%A Parnas, David Lorge
%A Clements, Paul C.
%C Piscataway, NJ, USA
%D 1986
%I IEEE Press
%J IEEE Transactions on Software Engineering
%K design fake how ieee paper process rational read:2008 why
%N 2
%P 251-257
%T A rational design process: How and why to fake it
%U http://portal.acm.org/citation.cfm?id=9800
%V 12
%X A perfectly rational person is one who always has a good reason for what he does. Each step taken can be shown to be the best way to get to a well defined goal. Most of us like to think of ourselves as rational professionals. However, to many observers, the usual process of designing software appears quite irrational. Programmers start without a clear statement of desired behavior and implementation constraints. They make a long sequence of design decisions with no clear statement of why they do things the way they do. Their
rationale is rarely explained.
@article{376637,
abstract = {A perfectly rational person is one who always has a good reason for what he does. Each step taken can be shown to be the best way to get to a well defined goal. Most of us like to think of ourselves as rational professionals. However, to many observers, the usual process of designing software appears quite irrational. Programmers start without a clear statement of desired behavior and implementation constraints. They make a long sequence of design decisions with no clear statement of why they do things the way they do. Their
rationale is rarely explained. },
added-at = {2008-07-01T15:32:11.000+0200},
address = {Piscataway, NJ, USA},
author = {Parnas, David Lorge and Clements, Paul C.},
biburl = {https://www.bibsonomy.org/bibtex/2e503584bdf5c7bdb0e8b57478a18225a/cschenk},
interhash = {07e3c942d8bc06cdcd8cb5ac3590258e},
intrahash = {e503584bdf5c7bdb0e8b57478a18225a},
journal = {IEEE Transactions on Software Engineering},
keywords = {design fake how ieee paper process rational read:2008 why},
number = 2,
pages = {251-257},
publisher = {IEEE Press},
timestamp = {2008-07-01T15:32:32.000+0200},
title = {A rational design process: How and why to fake it},
url = {http://portal.acm.org/citation.cfm?id=9800},
volume = 12,
year = 1986
}