Wayne,
>Payne, J. W., Bettman, J. R., & Johnson, E. J. (1993). The adaptive
>decision maker. New York: Cambridge University Press.
This is the book that kicked off this discussion.
>Third -- our work can be considered as emphasizing bottom-up
>considerations. There are top-down considerations as well. These would be
>all of the "good programming practices" that are taught in the books or
>acquired thru years of painful experience ("sure this is easier now, but
>if I ever have to change this then . . ."). These may be considered as
>affecting the value of P in the PG-C equation or they may simply (?)
>introduce a meta-layer into the choice of programming strategies.
I think bottom up considerations are used so often by developers that writers
of guidelines have got to get away from their top down approach.
I think guidelines introduce other considerations. They have a multitude
of potential effects:
o they introduce a new weighting factor (if a weighted decision strategy is
being used),
o they may be triggered as a commonly used rule (if a developer does
use them often enough) and an availability heuristic is being used,
o they introduce a third party. As Payne et al point out, people can
adjust decision strategies if they know their decisions need to be justified.
If guidelines are being automatically enforced what the developer does, or
does not do, could cause a noncompliance flag to be raised.
derek
--
Derek M Jones tel: +44 (0) 1252
520 667
Knowledge Software Ltd mailto:[EMAIL PROTECTED]
Applications Standards Conformance Testing http://www.knosof.co.uk
- Automatic footer for [EMAIL PROTECTED] ----------------------------------
To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss
To join the announcements list, mail [EMAIL PROTECTED] subscribe announce
To receive a help file, mail [EMAIL PROTECTED] help
This list is archived at http://www.mail-archive.com/discuss%40ppig.org/
If you have any problems or questions, please mail [EMAIL PROTECTED]
