Behavior-driven development benefits and challenges

Pereira, Lauriane; Sharp, Helen; Souza, Cleidson de; Oliveira, Gabriel; Marczak, Sabrina; Bastos, Ricardo Melo

doi:10.1145/3234152.3234167

Cited by 16 publications

(4 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This approach enables integration with testing tools, allowing the adoption of BDD to monitor system requirements and evaluate its behavior, ensuring that it is validated as ready at the end of each iteration. BDD has been widely recognized by the academic community and industry, demonstrating significant benefits, such as more effective communication, reduced release delivery time, and greater accuracy in requirements elicitation [14].…”

Section: Behavior-driven Development (Bdd)mentioning

confidence: 99%

“…From this point on, the features begin to be written, implemented, and validated, seeking to maintain the behavior expected by the requirements elicited in each release in order to deliver what is being expected by the system. In addition to helping with communication and collaboration between the parts involved [16], as it is written in English, the BDD also helps with the dynamic documentation of the system [14,15,17]. Dynamic documentation, or living documentation, refers to the agility required for updates to process documentation.…”

Section: Behavior-driven Development (Bdd)mentioning

confidence: 99%

See 1 more Smart Citation

Using Behavior-Driven Development (BDD) for Non-functional Requirements

Santos,

Pimentel,

Rocha

et al. 2024

Preprint

View full text Add to dashboard Cite

Context: In Software Engineering, there must be clarity in communication among interested parts to elicit the requirements aimed at software development through frameworks to achieve the behaviors expected by the software. Problem: Lack of clarity in the requirements elicitation stage can impact subsequent stages of software development. Solution: We proposed a case study to achieve the proposed goal focusing on the performance efficiency characteristic expressed in the ISO/IEC/IEEE 25010 Standard using Behavior-Driven Development (BDD). Method: The case study was performed with professionals who use BDD to elicit the non-functional requirements of a company that develops software. Summary of Results: The results obtained were aspects related to the elicitation of non-functional requirements aimed at the performance efficiency characteristic of the ISO/IEC/IEEE 25010 Standard using BDD through the point of view of industry professionals. Contributions and impact: The article’s main contribution is to demonstrate the effectiveness of using BDD to elicit non-functional requirements about the performance efficiency characteristic of the ISO/IEC/IEEE 25010 Standard.

show abstract

Section: Behavior-driven Development (Bdd)mentioning

confidence: 99%

Section: Behavior-driven Development (Bdd)mentioning

confidence: 99%

Using Behavior-Driven Development (BDD) for Non-functional Requirements

Santos,

Pimentel,

Rocha

et al. 2024

Preprint

View full text Add to dashboard Cite

show abstract

“…When trying to resolve technical problems such as model features and interfaces, we need effective communication; miscommunication during the specification is one of the major factors lowering project productivity Kortum et al (2016). Behavior-driven development Pereira et al (2018); Scandaroli et al (2019) is recognized to be a solution to this issue. Communication based on documents generated by the CI system and its source code works as form of behavior-driven development,…”

Section: Lessons From the History Of Software Developmentmentioning

confidence: 99%

Agile Stock Assessment

Hayashi¹,

Ichinokawa²,

Kinoshita³

et al. 2020

Preprint

View full text Add to dashboard Cite

Stock assessment determines the status of fishery stock to support manage- ment decision making. Considering the iterations between exploratory cal- culations and the need to compare outputs to elicit better model settings, we should focus on not only the accuracy of abundance estimation and the toler- ance of uncertainty but also the efficiency of the project workflow. Although in Japan, a stock assessment model was introduced written in the R language in 2012, the workflow did not sufficiently adjust, creating problems because the current workflow is contrary to the principles of effective value creation. To make our project sustainable, we propose adopting the agile methodol- ogy, an iterative development method used by software developers, for stock assessment. Therefore, we wrote an example report as a package document in the R language. Developed under a continuous integration environment, the report remains up to date, with every modification on component files. This method enabled our work to be efficient and transparent by allowing and documenting scenario branching, error corrections, and annual updates. We show that the iterative development cycle benefit us by allowing us to focus on the essential business problem of the assessment project.

show abstract

“…The relatively unconstrained format of such specifications, however, gives rise to most of the problems typically found in natural language requirements specifications such as verbosity, incompleteness, and ambiguity [5], which often make them difficult to understand and assess [6]. Furthermore, poorly-written BDD scenarios has been reported in the literature as one of the key hindrances to achieve the benefits of the approach [7].…”

Section: Introductionmentioning

confidence: 99%

Towards a Domain-Specific Language for Behaviour-Driven Development

Silva

2023

2023 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

View full text Add to dashboard Cite

This paper introduces a high-level domain-specific language (DSL) and its rich editing environment to allow the specification of consistent and testable Behaviour-Driven Development (BDD) scenarios as user requirements at different levels of abstraction. We preliminary evaluated our approach by looking at its potential to support the writing of BDD scenarios in five open-source projects on GitHub. Results have shown the language was able to fully support, with minor adaptations, the specification of consistent user requirements, allowing also a complete mapping between domain and interactive behaviours through BDD scenarios.

show abstract

Behavior-driven development benefits and challenges

Cited by 16 publications

References 3 publications

Using Behavior-Driven Development (BDD) for Non-functional Requirements

Using Behavior-Driven Development (BDD) for Non-functional Requirements

Agile Stock Assessment

Towards a Domain-Specific Language for Behaviour-Driven Development

Contact Info

Product

Resources

About