Abstract
The central activity in software development is the creation and use of descriptions.We make descriptions to capture our understanding of requirements, to describe the properties of the problem domain, to design the behaviour and structure of the software we are building, and for many other purposes too.
To work effectively we must make our descriptions as exact as possible, and this is one goal of the designers of formal notations. But we must also be clear-headed about the purpose and subject matter of each description. As John von Neumann observed: “There is no point in using exact methods where there is no clarity in the concepts and issues to which they are to be applied”. Without a clear understanding of the purpose and subject matter of each description we can easily lose much of the benefit of effective notations.
This talk presents a view of software development based on the notion of problem frames. Each problem frame is associated with a class of simple problems, and with a set of concerns that arise in the solution of problems of the class. Making and using descriptions are seen as activities aimed at addressing those concerns.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Jackson, M. (2002). Descriptions in Software Development. In: Jézéquel, JM., Hussmann, H., Cook, S. (eds) ≪UML≫ 2002 — The Unified Modeling Language. UML 2002. Lecture Notes in Computer Science, vol 2460. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-45800-X_1
Download citation
DOI: https://doi.org/10.1007/3-540-45800-X_1
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-44254-7
Online ISBN: 978-3-540-45800-5
eBook Packages: Springer Book Archive