Marina Filipovic
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Marina Filipovic has a total of 1 co-authors. Here are the top co-authors by number of shared publications:
- Fabian Gilson
University of Canterbury, Christchurch, New Zealand
2 shared publications
Latest Publications
- Open Access
- 11 January 2025
- Published by Springer Nature
- p. 141-149
Towards Improving Behavior-Driven Development and Acceptance Testing-Driven Development Teaching in a University Project Course
Behavior-Driven Development (BDD) improves the collaboration between developers and stakeholders following agile software development practices. Acceptance Test-Driven Development (ATDD) is an extension of BDD where requirements are accompanied by automated acceptance tests, translating functional acceptance criteria linked to requirements. While BDD and ATDD have been successfully applied in industry, few universities report on teaching BDD and ATDD principles as part of their curriculum. However, there is a need for education providers to teach industry-relevant practices so that junior developers’ skills are better aligned to industry’s expectations. Therefore, we report on how BDD and ATDD techniques have been taught in a two-semester software engineering project, including (i) the lack of observed evidence on the implications of applying BDD and ATDD on the functional suitability of software products, (ii) the lack of engagement with BDD and ATDD from students, and (ii) recommendations to educators to improve students’ engagement with these practices.
- 11 January 2025
- Published by Springer Nature
- p. 141-149
Open AccessTowards Improving Behavior-Driven Development and Acceptance Testing-Driven Development Teaching in a University Project Course
Behavior-Driven Development (BDD) improves the collaboration between developers and stakeholders following agile software development practices. Acceptance Test-Driven Development (ATDD) is an extension of BDD where requirements are accompanied by automated acceptance tests, translating functional acceptance criteria linked to requirements. While BDD and ATDD have been successfully applied in industry, few universities report on teaching BDD and ATDD principles as part of their curriculum. However, there is a need for education providers to teach industry-relevant practices so that junior developers’ skills are better aligned to industry’s expectations. Therefore, we report on how BDD and ATDD techniques have been taught in a two-semester software engineering project, including (i) the lack of observed evidence on the implications of applying BDD and ATDD on the functional suitability of software products, (ii) the lack of engagement with BDD and ATDD from students, and (ii) recommendations to educators to improve students’ engagement with these practices.
- Open Access
Which Combination of Test Metrics Can Predict Success of a Software Project? A Case Study in a Year-Long Project Course
Testing plays an important role in securing the success of a software development project. Prior studies have demonstrated beneficial effects of applying acceptance testing within a Behavioural-Driven Development method. In this research, we investigate whether we can quantify the effects various types of testing have on functional suitability, i.e. the software conformance to users' functional expectations. We explore which combination of software testing (automated and manual, including acceptance testing) should be applied to ensure the expected functional requirements are met, as well as whether the lack of testing during a development iteration causes a significant increase of effort spent fixing the project later on. To answer those questions, we collected and analysed data from a year-long software engineering project course. We combined manual observations and statistical methods, namely Linear Mixed-Effects Modelling, to evaluate the effects of coverage metrics as well as time effort on passed stories over 5 Scrum sprints. The results suggest that a combination of a high code coverage for all of automated unit, acceptance, and manual testing has a significant impact on functional suitability. Similarly, but to a lower extent, front-end unit testing and manual testing can predict the success of a software delivery when taken independently. We observed a close-to-significant effect between low back-end testing and deferral (i.e. postponement) of user stories.
Open AccessWhich Combination of Test Metrics Can Predict Success of a Software Project? A Case Study in a Year-Long Project Course
Testing plays an important role in securing the success of a software development project. Prior studies have demonstrated beneficial effects of applying acceptance testing within a Behavioural-Driven Development method. In this research, we investigate whether we can quantify the effects various types of testing have on functional suitability, i.e. the software conformance to users' functional expectations. We explore which combination of software testing (automated and manual, including acceptance testing) should be applied to ensure the expected functional requirements are met, as well as whether the lack of testing during a development iteration causes a significant increase of effort spent fixing the project later on. To answer those questions, we collected and analysed data from a year-long software engineering project course. We combined manual observations and statistical methods, namely Linear Mixed-Effects Modelling, to evaluate the effects of coverage metrics as well as time effort on passed stories over 5 Scrum sprints. The results suggest that a combination of a high code coverage for all of automated unit, acceptance, and manual testing has a significant impact on functional suitability. Similarly, but to a lower extent, front-end unit testing and manual testing can predict the success of a software delivery when taken independently. We observed a close-to-significant effect between low back-end testing and deferral (i.e. postponement) of user stories.