Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Regulatory Requirements Engineering in Large Enterprises: An Interview Study on the European Accessibility Act
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering. fortiss GmbH, Germany.ORCID iD: 0000-0002-9971-1130
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-4118-0952
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0003-0619-6027
Netlight Consulting GmbH, Germany.
2025 (English)In: Product-Focused Software Process Improvement / [ed] Dietmar Pfahl, Javier Gonzalez Huerta, Jil Klünder, Hina Anwar, Springer Science+Business Media B.V., 2025, Vol. 15452, p. 204-220Conference paper, Published paper (Refereed)
Abstract [en]

Context: Regulations, such as the European Accessibility Act (EAA), impact the engineering of software products and services. Managing that impact while providing meaningful inputs to development teams is one of the emerging requirements engineering (RE) challenges.

Problem: Enterprises conduct Regulatory Impact Analysis (RIA) to consider the effects of regulations on software products offered and formulate requirements at an enterprise level. Despite its practical relevance, we are unaware of any studies on this large-scale regulatory RE process.

Methodology: We conducted an exploratory interview study of RIA in three large enterprises. We focused on how they conduct RIA, emphasizing cross-functional interactions, and using the EAA as an example.

Results: RIA, as a regulatory RE process, is conducted to address the needs of executive management and central functions. It involves coordination between different functions and levels of enterprise hierarchy. Enterprises use artifacts to support interpretation and communication of the results of RIA. Challenges to RIA are mainly related to the execution of such coordination and managing the knowledge involved.

Conclusion: RIA in large enterprises demands close coordination of multiple stakeholders and roles. Applying interpretation and compliance artifacts is one approach to support such coordination. However, there are no established practices for creating and managing such artifacts. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2025. Vol. 15452, p. 204-220
Series
Lecture Notes in Computer Science (LNCS), ISSN 0302-9743, E-ISSN 1611-3349 ; 15452
Keywords [en]
Compliance requirements, Enterprise requirements engineering, Impact Analysis, Large-scale agile, Requirements engineering, Software regulatory compliance, Human resource management, Compliance requirement, Enterprise requirement engineering, Enterprise requirements, Large-scales, Regulatory impact analysis, Requirement engineering
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-27325DOI: 10.1007/978-3-031-78386-9_14ISI: 001423664600014Scopus ID: 2-s2.0-85211892202ISBN: 9783031783852 (print)OAI: oai:DiVA.org:bth-27325DiVA, id: diva2:1923730
Conference
25th International Conference on Product-Focused Software Process Improvement, PROFES 2024, Tartu, Dec 2-4, 2024
Note

Available from: 2024-12-30 Created: 2024-12-30 Last updated: 2025-09-30Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records

Kosenkov, OleksandrUnterkalmsteiner, MichaelMendez, Daniel

Search in DiVA

By author/editor
Kosenkov, OleksandrUnterkalmsteiner, MichaelMendez, Daniel
By organisation
Department of Software Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 116 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf