Abstract
Requirements play a pivotal role in software development because they express the needs of the customer. A quality software system can emerge only when the real needs of the client are discovered. However, this is not enough. A typical software development project faces the problem of translating the user needs into a working system. These problems are dealt with by hundreds of books on various aspects of software design and pertaining to the plethora of software development technologies we can choose from. Related activities produce important artefacts that are treated as primary in software development: design models and code. Software design and coding directly contributes to the final system, and thus their results are treated as first-class citizens in the world of software development.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The examples in this chapter use very simplified Java with an imaginary programming framework. Here we want to abstract away from any specific Java technology.
- 2.
- 3.
The idea of requirements modelling started with the Requirements Modelling Language proposed by Greenspan et al. [63, 64]. More recently, Helming et al. proposed the Unified Requirements Modelling Language [16, 68]. Yet another approach was proposed by Beatty and Chen [13].
- 4.
- 5.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2015 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Śmiałek, M., Nowakowski, W. (2015). Introducing Requirements-Driven Modelling. In: From Requirements to Java in a Snap. Springer, Cham. https://doi.org/10.1007/978-3-319-12838-2_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-12838-2_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-12837-5
Online ISBN: 978-3-319-12838-2
eBook Packages: Computer ScienceComputer Science (R0)