Towards Viewpoint-centric Artifact-based Regulatory Requirements Engineering for Compliance by Design
Oleksandr Kosenkov

TL;DR
This paper introduces an artefact model for regulatory requirements engineering aimed at integrating compliance by design into software development, addressing industry challenges of complexity and cross-functional coordination.
Contribution
It proposes the AM4RRE artefact model to systematically support regulatory requirements engineering and facilitate compliance by design in software engineering.
Findings
Initial artefact model synthesis presented
Highlights the need for systematic regulatory RE approaches
Calls for empirical evaluation and industry feedback
Abstract
Processing regulations and resulting requirements to achieve regulatory compliance in software engineering (SE) is a developing challenge due to the continuously growing amount, complexity, and expanding scope of regulations. Despite the growing amount of newly suggested regulatory requirements engineering (RE) approaches by the research community, industry remains under pressure to assure their integration into their RE and overall software development life cycle (SDLC) practices to facilitate a seamless and legally valid compliance by design. As of today, we still have limited empirical understanding of how this can be achieved. Such integration should avoid additional burdens and address the demands of legal knowledge intensity, cross-functional communication and consistency between different involved viewpoints. Intermediary results of this doctoral study showed that regulatory RE…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSafety Systems Engineering in Autonomy · Software Engineering Techniques and Practices · Information and Cyber Security
