Logo des Repositoriums

Auflistung nach Autor:in "Ruhroth, Thomas"

1 - 5 von 5
  • Konferenzbeitrag
    1st collaborative workshop on Evolution and Maintenance of Long-Living Systems (EMLS'14)
    (Software Engineering 2014, 2014) Heinrich, Robert; Jung, Reiner; Konersmann, Marco; Ruhroth, Thomas; Schmieders, Eric
  • Konferenzbeitrag
    5. Workshop „Design For Future - Langlebige Softwaresysteme“
    (Software Engineering 2013, 2013) Sauer, Stefan; Klatt, Benjamin; Ruhroth, Thomas
  • Workshopbeitrag
    A Framework for Semi-Automated Co-Evolution of Security Knowledge and System Models (Summary)
    (Software Engineering and Software Management 2019, 2019) Bürger, Jens; Strüber, Daniel; Gärtner, Stefan; Ruhroth, Thomas; Jürjens, Jan; Schneider, Kurt
  • Konferenzbeitrag
    Towards maintaining long-living information systems by incorporating security knowledge
    (Software-engineering and management 2015, 2015) Gärtner, Stefan; Ruhroth, Thomas; Bürger, Jens; Schneider, Kurt; Jürjens, Jan
    Modern information systems are increasingly complex and need to operate in evolving environments. As a consequence, systems must co-evolve to keep up-todate with their environments. This is especially important for security properties, since changes and patches tend to compromise them. We propose a security assessment approach for natural language requirements for systematic co-evolution. Our evaluation and tool implementation show security benefits for maintaining long-living systems.
  • Zeitschriftenartikel
    Versioning and Evolution Requirements for Model-Based System Development
    (Softwaretechnik-Trends Band 34, Heft 2, 2014) Ruhroth, Thomas; Gärtner, Stefan; Bürger, Jens; Jürjens, Jan; Schneider, Kurt
    Long-living software systems “ages” not by wearing out, but by failing to keep up-to-date with its requirements. Moreover, security is an increasingly important quality facet in modern information systems and needs to be retained properly. In model-based system development, this leads to a continuously changing information system model accordingly. The problem is that software engineers cannot simply overview changes of the system model and their impact on the applied security model. To overcome this problem, a semantic representation of model changes is needed which is determined from fine-grained edit operations. Based on the semantic representation of system model changes, software engineers are supported to choose an evolution strategy of the associated security model. In this paper, we discuss challenges and problems that arise from the granularity of the change operations as well as the selection of different evolution strategies which can be performed interleaved.