ABSTRACT
In the parlance of computer-aided software engineering (CASE), one designs solutions to problems in a domain by identifying a series of representative use cases. Success depends on choosing a sufficient number of use cases to sample the domain adequately, characterizing the variety of likely applications of the system. By this logic, the design of systems to represent and compute geographic dynamics requires an understanding first of the domain of geographic dynamics, and second of the range of uses to which such representations and computations will be put. In short, to discuss representation and computation of geographic dynamics we must first understand the full range of geographic dynamics, and then ask why such representations and computations are useful.
