Security Requirements as Code: Example from VeriDevOps Project

Khaled Ismaeel, Alexandr Naumchev, Andrey Sadovykh, Dragos Truscan, Eduard Paul Enoiu, Cristina Seceleanu

Research output: Chapter in Book/Conference proceedingConference contributionScientificpeer-review

1 Citation (Scopus)
41 Downloads (Pure)


This position paper presents and illustrates the concept of security requirements as code - a novel approach to security requirements specification. The aspiration to minimize code duplication and maximize its reuse has always been driving the evolution of software development approaches. Object-Oriented programming (OOP) takes these approaches to the state in which the resulting code conceptually maps to the problem that the code is supposed to solve. People nowadays start learning to program in the primary school. On the other hand, requirements engineers still heavily rely on natural language based techniques to specify requirements. The key idea of this paper is: artifacts produced by the requirements process should be treated as input to the regular object-oriented analysis. Therefore, the contribution of this paper is the presentation of the major concepts for the security requirements as the code method that is illustrated with a real industry example from the VeriDevOps project.

Original languageEnglish
Title of host publicationProceedings - 29th IEEE International Requirements Engineering Conference Workshops, REW 2021
EditorsTao Yue, Mehdi Mirakhorli
Number of pages7
ISBN (Electronic)978-1-6654-1898-0
ISBN (Print)978-1-6654-1899-7
Publication statusPublished - 2021
MoE publication typeA4 Article in a conference publication
EventIEEE International Requirements Engineering Conference Workshops -
Duration: 20 Sept 202124 Sept 2021


ConferenceIEEE International Requirements Engineering Conference Workshops
Abbreviated titleREW


  • development
  • requirements as code
  • seamless
  • security
  • software


Dive into the research topics of 'Security Requirements as Code: Example from VeriDevOps Project'. Together they form a unique fingerprint.

Cite this