Proseminar Sichere Softwareentwicklung


  • The list of topic is now final (with one minor exception)
  • Process for application: write an e-mail to Prof. Jan Jürjens with a short application in written form, your course credits so far and a prioritized list of desired topics.
    Deadline: 1.3.2017 15.03.2017
  • The kickoff meeting will take place 18.04.2017 16:15 in room B015.
  • Attending this seminar is possible in English as well as in German
  • The seminar will be held as a block seminar in the form of two/three whole day sessions at the end of the summer term 2017


  • TBA


The participants will get to understand the requirements on security-critical systems and its types of threats. They will get an overview of the existing techniques to avoid security risks and to repel threats. They will get to know of the special features of the management of security-related software projects, the benefit of security expenses and the relevant standards and regulations. Finally, they will have concentrated on model-based techniques for developing security-critical systems as well as analyzing and re-engineering of existing software, being able to evaluate gained practical experience and to get an overview of existing tools and its performance.

Guiding themes

The development and maintenance of trustworthy and security-critical systems are big challenges. There are many software-intense systems designed, implemented and in use that have serious security issues. We know from experience as well as from headlines about spectacular malfunction of systems or about successful attacks on them. The reasons are manyfold. Sometimes the developers' required security awareness is missing, often the required knowledge for development processes, methods, techniques and tools is missing or they are not used as one supposes not to be able to afford a high time and cost expenditure with the current competitive pressure. In relation to the engineering or re-engineering of security-critical software systems the following questions need to be answered:


  • Which methods do exist for a comprehensive risk management with which experts are able to perform a complete analysis of the security risks of business processes and workflows and to derive proposals for appropriate treatments?
  • Which methods do exist for the engineering or re-engineering of security-critical software systems for the selection of suitable development processes and suitable tools as well as quality assurance?
  • Which tools do exist to automatically analyze e.g. business processes, UML specifications, source code and configuration files towards security?
  • Is it possible to intuitively specify security requirements with UML or CASE tools for example, such as AutoFocus? Do tools exist for simulation, consistency checking, code generation, verification and testing of security aspects?
  • Are the created models usable as documentation for certification against relevant standards?


How to participate

As soon as the final list of topics is announced, send an e-mail to Prof. Dr. Jan Jürjens explaining why you want do participate in the seminar an to what extent you are a good choice for the topics. (See above).


This seminar will take place as a two- or three-day block seminar at the end of the term.


The grade will be put together from the following parts:

  • a written manuscript of about 15 pages length referring to the main part
  • a presentation of about 35 minutes plus discussion (limits: 30-40 minutes)
  • active participation during the presentation of other participants
  • compliance with formal guidelines (in particular the timely and complete submission)
  • you will obtain further information during the first meeting

The grade you receive will built as follows:

  • presentation (40%)
  • written composition (40%)
  • reviews (10%)
  • discussion after the presentations (10%)

Furthermore, compliance to the formal guidelines is vital (degradation of marks in case of non-compliance). Failing one part automatically leads to failing the whole seminar, and plagiarism in one part immediately leads to failing the seminar and will be reported to the audit committee.


We are really interested in accompanying feedback to directly respond to change requests. Please express your comments subsequent to a lecture via e-mail or the anonymous contact form of our research group (in the latter case please mention the lecure the comment refers to). Many thanks!