Specifying model changes with UMLchange to support security verification of potential evolution

  • Authors:
  • S. Wenzel;D. Poggenpohl;J. Jürjens;M. Ochoa

  • Affiliations:
  • Fraunhofer ISST, Emil-Figge-Str. 91, D-44227 Dortmund, Germany;Fraunhofer ISST, Emil-Figge-Str. 91, D-44227 Dortmund, Germany;TU Dortmund, D-44221 Dortmund, Germany and Fraunhofer ISST, Emil-Figge-Str. 91, D-44227 Dortmund, Germany;Technical University of Munich, Software Engineering, Boltzmannstr. 3, 85748, Garching, Germany

  • Venue:
  • Computer Standards & Interfaces
  • Year:
  • 2014

Quantified Score

Hi-index 0.00

Visualization

Abstract

In model-based development, quality properties such as consistency of security requirements are often verified prior to code generation. Changed models have to be re-verified before re-generation. If several alternative evolutions of a model are possible, each alternative has to be modeled and verified to find the best model for further development. We present a verification strategy to analyze whether evolution preserves given security properties. The UMLchange profile is used for specifying potential evolutions of a given model simultaneously. We present a tool that reads these annotations and computes a delta containing all possible evolution paths. The paths can be verified wrt. security properties, and for each successfully verified path a new model version is generated automatically.