Seamless Object-Oriented Requirements

Naumchev, Alexandr

doi:10.1109/sibircon48586.2019.8958211

Cited by 8 publications

(3 citation statements)

References 19 publications

(32 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Seamless approaches, such as SOOR [58], use an identical programming language to combine requirements with other software tasks, including design and development. This technique can achieve the seamless integration of requirements, design, and development, but it lacks support for verification, and further research is still necessary to determine its effectiveness.…”

Section: B Representation Of Safety/security Requirementsmentioning

confidence: 99%

Contradictions Identification of Safety and Security Requirements for Industrial Cyber–Physical Systems

Sun,

Ding,

Pei

et al. 2024

IEEE Internet Things J.

View full text Add to dashboard Cite

Section: B Representation Of Safety/security Requirementsmentioning

confidence: 99%

Contradictions Identification of Safety and Security Requirements for Industrial Cyber–Physical Systems

Sun,

Ding,

Pei

et al. 2024

IEEE Internet Things J.

View full text Add to dashboard Cite

“…The requirements traceability improvements proposed by RQCODE have to be analyzed regarding [19], [20]. Finally, the work at [21] set the basis for our work.…”

Section: Related Workmentioning

confidence: 99%

RQCODE – Towards Object-Oriented Requirements in the Software Security Domain

Nigmatullin

Sadovykh

Messe³

et al. 2022

2022 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

For the last 20 years, the number of vulnerabilities has increased near 20 times, according to NIST statistics. Vulnerabilities expose companies to risks that may seriously threaten their operations. Therefore, for a long time, it has been suggested to apply security engineering -the process of accumulating multiple techniques and practices to ensure a sufficient level of security and to prevent vulnerabilities in the early stages of software development, including establishing security requirements and proper security testing. The informal nature of security requirements makes it uneasy to maintain system security, eliminate redundancy and trace requirements down to verification artifacts such as test cases. To deal with this problem, Seamless Object-Oriented Requirements (SOORs) promote incorporating formal requirements representations and verification means together into requirements classes.This article is a position paper that discusses opportunities to implement the Requirements as Code (RQCODE) concepts, SOORs in Java, applied to the Software Security domain. We argue that this concept has an elegance and the potential to raise the attention of developers since it combines a lightweight formalization of requirements through security tests with seamless integration with off-the-shelf development environments, including modern Continuous Integration/Delivery platforms. The benefits of this approach are yet to be demonstrated in further studies in the VeriDevOps project.

show abstract

“…Seamless Object-Oriented Requirements (SOORs) [9] is a requirements engineering approach that focuses on requirements verifiability and reusability. In SOORs, requirements are written as classes.…”

Section: B Seamless Object-oriented Requirementsmentioning

confidence: 99%

Security Requirements as Code: Example from VeriDevOps Project

Ismaeel

Naumchev

Sadovykh

et al. 2021

2021 IEEE 29th International Requirements Engineering Conference Workshops (REW)

Self Cite

View full text Add to dashboard Cite

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. Objectoriented 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.

show abstract

Seamless Object-Oriented Requirements

Cited by 8 publications

References 19 publications

Contradictions Identification of Safety and Security Requirements for Industrial Cyber–Physical Systems

Contradictions Identification of Safety and Security Requirements for Industrial Cyber–Physical Systems

RQCODE – Towards Object-Oriented Requirements in the Software Security Domain

Security Requirements as Code: Example from VeriDevOps Project

Contact Info

Product

Resources

About