Abstract
Software engineers are invariably confronted with the question of which development methods to use in order to produce good software. If we ask how exactly software development is to be organized, we come up against a wide variety of different concepts. But there is not only an abundance of concepts, there is even greater diversity in the terms used to describe them. What one software engineer chooses to call “process model” is termed by another “project strategy”; and there are “system requirements”, “requirements analyses”, “user needs analyses” and “software models”. How we can make practical use of the proposed concepts remains a mystery. At any rate, it would seem impossible to draw any sort of comparison between them.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 1992 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Budde, R., Kautz, K., Kuhlenkamp, K., Züllighoven, H. (1992). Introduction. In: Prototyping. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-76820-0_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-76820-0_1
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-76822-4
Online ISBN: 978-3-642-76820-0
eBook Packages: Springer Book Archive