Abstract
How can the application domain and the requirements be better understood using object-oriented (OO) modeling? How do scenarios / use cases fit together with functional requirements? How can a domain model be used for a model-based transition to a design model?
This tutorial addresses these questions in the following manner. It shows how each requirement given in natural language can be viewed itself as an object and modeled as such. This approach facilitates both a hierarchical organization (by grouping requirements instances into classes and subclasses) and explicit association (by relating requirements through OO associations). While scenarios / use cases can somehow illustrate the overall functionality, additionally functional requirements for the system to be built should be formulated and related to them appropriately. All kinds of requirements make statements about the application domain, which should be first represented in a domain model of conceptual classes, in order to make the requirements better understandable. This tutorial explains a seamless transition to a high-level design model, where design classes are abstractions of implementation classes. This transition from requirements to software design is also investigated in model-driven terms, whether it is a transformation or just a mapping. In addition, the influence of non-functional requirements for selecting an architecture is explained.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Kaindl, H.: How to Identify Binary Relations for Domain Models. In: Proceedings of the Eighteenth International Conference on Software Engineering (ICSE-18), pp. 28–36. IEEE Computer Society Press, Los Alamitos (1996)
Kaindl, H.: A Practical Approach to Combining Requirements Definition and Object-Oriented Analysis. Annals of Software Engineering 3, 319–343 (1997)
Kaindl, H.: Difficulties in the transition from OO analysis to design. IEEE Software, 94–102 (September/October 1999)
Kaindl, H.: A Design Process Based on a Model Combining Scenarios with Goals and Functions. IEEE Transactions on Systems, Man, and Cybernetics (SMC) Part A 30(5), 537–551 (2000)
Kaindl, H.: Adoption of Requirements Engineering: Conditions for Success. In: Fifth IEEE International Symposium on Requirements Engineering (RE 2001), Toronto, Canada (August 2001)
Kaindl, H.: Is object-oriented requirements engineering of interest? Requirements Engineering 10, 81–84 (2005)
Kaindl, H.: A Scenario-Based Approach for Requirements Engineering: Experience in a Telecommunication Software Development Project. Systems Engineering 8, 197–210 (2005)
Kaindl, H., Falb, J.: Can We Transform Requirements into Architecture? In: Proceedings of the Third International Conference on Software Engineering Advances (ICSEA 2008), pp. 91–96. IEEE (2008)
Kaindl, H., Kramer, S., Kacsich, R.: A Case Study of Decomposing Functional Requirements. In: Proc. Third International Conference on Requirements Engineering (ICRE 1998), pp. 156–163. IEEE (April 1998)
Kaindl, H., Svetinovic, D.: On confusion between requirements and their representations. Requirements Engineering 15, 307–311 (2010)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Kaindl, H. (2013). Model-Based Transition from Requirements to High-Level Software Design. In: Heidrich, J., Oivo, M., Jedlitschka, A., Baldassarre, M.T. (eds) Product-Focused Software Process Improvement. PROFES 2013. Lecture Notes in Computer Science, vol 7983. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-39259-7_36
Download citation
DOI: https://doi.org/10.1007/978-3-642-39259-7_36
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-39258-0
Online ISBN: 978-3-642-39259-7
eBook Packages: Computer ScienceComputer Science (R0)