Abstract
Design decisions are based on several criteria affecting each other. The architect is responsible for ensuring that the decisions fit the system requirements. This validation process is time-consuming work which has to be repeated if the requirements change. The use of various documentation forms complicates this work. In this chapter, we describe an approach for supporting the architect in validating the architecture against the requirements. It allows an automation of the validation process and offers support for the impact analysis. It can be applied in an early as well as in an advanced project phase. For documentation, we apply the Unified Modeling Language wherever possible and reasonable in order to achieve consistent system documentation.
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
Notes
- 1.
Guillemets are the french quote signs.
- 2.
The presentation of the UML profile is due to the used modeling tool Enterprise architect [16]. It is not UML compliant.
- 3.
In this example the model contains only one diagram.
References
Robertson S, Robertson J (2006) Mastering the requirements process. Addison-Wesley Longman, Amsterdam
Young R (2003) The Requirements Engineering Handbook, Artech House Inc., London
Sommerville I (2007) Software Engineering, Pearson Studium, Germany
Homepage of the Object Management Group (OMG) (2010) http://www.omg.org. Accessed 28 August 2010
Wiegers K (2003) Software requirements, Microsoft Press, Sydney
Pohl K (2010) Software Engineering, dpunkt Verlag, Heidelberg
Home of the UML profile MARTE (2010) http://www.omgwiki.org/marte/. Accessed on 28 August 2010
The MADES project (2010) http://mades-project.ning.com/. Accessed 28 August 2010
Börger E, Stärk R (2003) Abstract state machines, Springer, Berlin
CoFluent Studio (2010) http://www.cofluentdesign.com/. Accessed 28 August 2010
Home of the UML profile SysML (2010) http://www.sysml.org/.Accessed May 2010
Balcer M, Mellor S (2002) Executable UML: a foundation for model-driven architecture, Addison-Wesley, Massachusetts
Object Management Group (2010) The UML Infrastructure Specification 2.3. http://www.omg.org/spec/UML/2.3/Infrastructure/. Accessed May 2010
Object Management Group (2010) The UML Superstructure Specification 2.3. http://www.omg.org/spec/UML/2.3/Superstructure/. Accessed May 2010
Homepage of the Eclipse Modeling Framework (EMF) (2010) http://www.eclipse.org/emf/. Accessed 28 August 2010
Homepage of Sparx Systems (2010) http://www.sparxsystem.de. Accessed 28 August 2010
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer Science+Business Media New York
About this paper
Cite this paper
Pflueger, A., Golubski, W., Queins, S. (2013). Validation of System Architectures Against Requirements. In: Sobh, T., Elleithy, K. (eds) Emerging Trends in Computing, Informatics, Systems Sciences, and Engineering. Lecture Notes in Electrical Engineering, vol 151. Springer, New York, NY. https://doi.org/10.1007/978-1-4614-3558-7_35
Download citation
DOI: https://doi.org/10.1007/978-1-4614-3558-7_35
Published:
Publisher Name: Springer, New York, NY
Print ISBN: 978-1-4614-3557-0
Online ISBN: 978-1-4614-3558-7
eBook Packages: EngineeringEngineering (R0)