Compliance of agilized (software) development processes with safety standards

Gallina, Barbara; Muram, Faiz Ul; Ardila, Julieth Patricia Castellanos

doi:10.1145/3234152.3234175

Cited by 8 publications

(3 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Compliance or conformance checking is the verification of whether a process used to develop a specific software application adheres to a determined set of normative requirements (i.e., standards, policies, or regulations). 14 The expression conformance checking is also used to determine whether a software process instance conforms to its process definition. 15 Compliance can be shown when processes comply with all requirements or when organizations perform tailoring † within the boundaries of the norm, which determine allowed actions and the resulting conditions.…”

Section: Compliance Checking Of Software Processesmentioning

confidence: 99%

“…Compliance of agilized (software) development processes with safety standards: A vision 14 Conference S30 Formalizing ISO/IEC 15504-5 and SEI CMMI v1.3-Enabling automatic inference of maturity and capability levels 100 Journal…”

Section: S29mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Compliance checking of software processes: A systematic literature review

Ardila

Gallina

Muram

2022

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

The processes used to develop software need to comply with normative requirements (e.g., standards and regulations) to align with the market and the law. Manual compliance checking is challenging because there are numerous requirements with changing nature and different purposes. Despite the importance of automated techniques, there is not any systematic study in this field. This lack may hinder organizations from moving toward automated compliance checking practices. In this paper, we characterize the methods for automatic compliance checking of software processes, including used techniques, potential impacts, and challenges. For this, we undertake a systematic literature review (SLR) of studies reporting methods in this field. As a result, we identify solutions that use different techniques (e.g., anthologies and metamodels) to represent processes and their artifacts (e.g., tasks and roles). Various languages, which have diverse capabilities for managing competing and changing norms, and agile strategies, are also used to represent normative requirements. Most solutions require tool‐support concretization and enhanced capabilities to handle processes and normative diversity. Our findings outline compelling areas for future research. In particular, there is a need to select suitable languages for consolidating a generic and normative‐agnostic solution, increase automation levels, tool support, and boost the application in practice by improving usability aspects.

show abstract

Section: Compliance Checking Of Software Processesmentioning

confidence: 99%

Section: S29mentioning

confidence: 99%