Page 69 -

54 BERENTE AND LYYTINEN
developers and others involved in a design are necessarily iterative, but this can mean different
things depending on whether the rationalistic tradition or the situated action perspective of human
cognition is adopted. In addition, cognitive iterations involve iterative engagement with represen-
tations acting as both extensions to cognition and mediation between individuals.
We identify two primary forms of representation: the descriptive documents associated with
analysis and design activity, and the executable code itself. Although many representational
artifacts for both types are prescribed by advocates of particular methodologies, the empirical
literature is limited solely to examining iterations over the software code as evolutionary proto-
typing. Furthermore, recent “iterative development” identifies entirely with the centrality of the
iterations associated with the code itself. In this chapter we provide a starting point for unpack-
ing the notion of iteration to expand the discussion beyond iterating code to other artifacts and
associated cognitive processes.

REFERENCES

Alavi, M. 1984. An assessment of the prototyping approach to information systems development. Commu-
nications of the ACM, 27, 6, 556–563.
Anton, A.I. 1996. Goal-based requirements analysis. In Proceedings of the Second International Conference
on Requirements Engineering. Colorado Springs: IEEE Computer Society Press, 136–144.
Auer, K.; Meade, E.; and Reeves, G. 2003. The rules of the game. In F. Maurer and D. Wells (eds.), Extreme
Programming and Agile Methods—XP/Agile Universe 2002, Lecture Notes in Computer Science 2753.
Berlin-Heidelberg: Springer, 35–42.
Barrett, B.; Berry, M.; Chan, T.F.; Demmel, J.; Dongrra, J.; Eijkhout, V.; Pozo, R.; Romine, C.; and Van der
Vorst, H. 1994. Templates for the Solution of Linear Systems—Building Blocks for Iterative Methods.
Philadelphia, PA: SIAM. Available at www.netlib.org/templates/Templates.html (accessed on August
31, 2007).
Basili, V.R., and Turner, A.J. 1975. Iterative enhancement: a practical technique for software development.
IEEE Transactions on Software Engineering, 1, 4, 390–396.
Baskerville, R., and Pries-Heje, J. 2004. Short cycle time systems development. Information Systems Journal,
14, 3, 237–264.
Baskerville, R.L., and Stage, J. 1996. Controlling prototype development through risk analysis. MIS Quar-
terly, 20, 4, 481–504.
Beck, K. 2002. Extreme Programming Explained: Embrace Change. Boston: Addison-Wesley.
Bergman, M.; King, J.L.; and Lyytinen, K. 2002. Large scale requirements analysis as heterogeneous engi-
neering. Scandinavian Journal of Information Systems, 14, 1, 37–55.
Beynon-Davies, P.; Mackay, H.; and Tudhope, D. 2000. “It’s lots of bits of paper and ticks and post-it notes
and things . . .”: a case study of a rapid application development project. Journal of Information Systems,
10, 3, 195–216.
Beynon-Davies, P.; Tudhope, D.; and Mackay, H. 1999. Information systems prototyping in practice. Journal
of Information Technology, 14, 1, 107–120.
Beynon-Davies, P.; Carne, C.; Mackay, H.; and Tudhope, D. 1999. Rapid application development: an em-
pirical review. European Journal of Information Systems, 8, 2, 211–223.
Blair, D.C. 2005. Wittgenstein, Language, and Information: Back to the Rough Ground. Berlin-Heidelberg:
Springer.
Boehm, B. 1981. Software Engineering Economics. Upper Saddle River, NJ: Prentice Hall.
———. 1988. The spiral model of software development and enhancement. Computer, 21, 5, 14–24.
———. 2002. Get ready for agile methods, with care. IEEE Computer, 35, 1, 64–69.
Boehm, B.; Gray, T.E.; and Seewaldt, T. 1984. Prototyping vs. specification: a multi-project experiment.
IEEE Transactions on Software Engineering, 10, 3, 290–303.
Boland, R.J. 1978. The process and product of system design. Management Science, 24, 9, 887–898.
Boland, R.J., and Day, W.F. 1989. The experience of system design: a hermeneutic of organizational action.
Scandinavian Journal of Management, 5, 2, 87–104.