Reference Hub1
Process for the Validation of System Architectures against Requirements

Process for the Validation of System Architectures against Requirements

André Pflüger, Wolfgang Golubski, Stefan Queins
ISBN13: 9781466642171|ISBN10: 1466642173|EISBN13: 9781466642188
DOI: 10.4018/978-1-4666-4217-1.ch008
Cite Chapter Cite Chapter

MLA

Pflüger, André, et al. "Process for the Validation of System Architectures against Requirements." Progressions and Innovations in Model-Driven Software Engineering, edited by Vicente García Díaz, et al., IGI Global, 2013, pp. 209-229. https://doi.org/10.4018/978-1-4666-4217-1.ch008

APA

Pflüger, A., Golubski, W., & Queins, S. (2013). Process for the Validation of System Architectures against Requirements. In V. Díaz, J. Lovelle, B. García-Bustelo, & O. Martínez (Eds.), Progressions and Innovations in Model-Driven Software Engineering (pp. 209-229). IGI Global. https://doi.org/10.4018/978-1-4666-4217-1.ch008

Chicago

Pflüger, André, Wolfgang Golubski, and Stefan Queins. "Process for the Validation of System Architectures against Requirements." In Progressions and Innovations in Model-Driven Software Engineering, edited by Vicente García Díaz, et al., 209-229. Hershey, PA: IGI Global, 2013. https://doi.org/10.4018/978-1-4666-4217-1.ch008

Export Reference

Mendeley
Favorite

Abstract

The development of systems consisting of hardware and software is a challenging task for the system architect. On the one hand, he has to consider an increasing number of system requirements, including the dependencies between them for designing the system architecture; on the other hand, he has to deal with a shortened time-to-market period and requirements changes of the customers up to the implementation phase. This chapter presents a process that enables the architect to validate the system architecture against the architecture-relevant requirements. The process is part of the system design phase and can be integrated in the iterative design of the system architecture. In order to keep track of all requirements, including their dependencies, the architect clusters the requirements according to architecture-specific aspects, the so-called validation targets. For each target he defines examinations processes and check criteria to define the validation status. If all targets are valid, i.e., all check criteria are met by the result of the examination processes, the system architecture itself is valid. Instead of formal validation techniques like model checking, the approach prefers simulations for the examination processes. The approach uses model-based documentation based on the Unified Modeling Language (UML). All data required for the simulations is part of an UML model and extracted to configure and run the simulations. Therefore, changes in the model affect the validation result directly. The process supports the architect in building a system architecture that fulfills the architecture-relevant requirements, and it supports the architect in analyzing the impacts after requirements or architecture changes. A tool facilitates the work effort of the architect by partly automating the major process steps.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.