This paper presents the results and experiences of applying a formal tool to writing specifications for software in the spatial domain. We take a specification from a standards organization to demonstrate the properties of this approach, and we compare our result with the semi-formal specification of the standards organization. The expected advantages--formal semantics of specified interfaces, total abstraction from implementation, executable prototype, and extendable algebraic structure--can be verified. However negative experiences are reported also: pure abstract code turns out to appear overloaded and difficult to read (by humans). With this work we contribute to the foundations of standardisation efforts in the spatial domain, preserving an object oriented modeling approach.
No Reference information available - sign in for access.
No Citation information available - sign in for access.
No Supplementary Data.
No Article Media
Document Type: Research Article
Department of Geomatics The University of Melbourne Victoria 3010 Australia, Email: [email protected]
Department of Spatial Information Science and Engineering University of Maine 5711 Boardman Hall Orono ME 04469-5711 USA, Email: [email protected]
Publication date: December 1, 2003
More about this publication?