Formal Methods for an Agile Scrum Software Development Methodology
DOI:
https://doi.org/10.58190/icat.2023.35Keywords:
Agile Software Development Methodology, Formal Methods (FMs), Formal Specification, Proof Obligation (PO), Scrum, ZAbstract
Efficient, high-quality software systems embodying dependable methods are in high demand, which has led to a wide range of competitive market solutions. One effective technique that arguably has excelled above others is the Agile Software Development Methodology (ASDM). Agile approaches’ capacity to produce software in a way that is flexible to changes is the main factor that makes them preferable. Scrum, a recommended Agile methodology, prioritises feature coverage and project structure. Because iterative methodologies encourage engagement from cross-functional teams, including consumers, Agile provides flexibility in responding to change. However, achieving methodological efficiency is insufficient while developing software; high-quality software should be achieved with equal consideration. Formal Methods (FMs), which are mathematically based techniques, can offer highly dependable software but suffer from a steep learning curve in mastering the underlying discrete mathematics and logic. This research investigates the extent to which FMs may be embedded in traditional Agile as embodied by Scrum. Future work in this area would be the development of a framework for embedding FMs in Scrum, followed by a survey among software practitioners to establish the feasibility of our technique.