Requirements specification for developers in agile projects: Evaluation by two industrial case studies

Medeiros, Juliana; Vasconcelos, Alexandre Marcos Lins de; Silva, Carla T. L. L.; Goulão, Miguel

doi:10.1016/j.infsof.2019.106194

Cited by 22 publications

(13 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As Davies [46] describes the behaviour of waterfall developers: "When requirements come from someone else and someone else tests my work, I don't need to know the environment that my software will be running in ". On the other hand, agile does not make any differences between the kind of requirements (FRs and QRs) and defines both as user stories (the most used documentation technique as in [47] ). Agile developers are expected to collect the needed requirement, elaborate them further in face-to-face communication sessions and implement them just in time.…”

Section: Moving To Agile With a Waterfall Mind-setmentioning

confidence: 99%

Quality requirements challenges in the context of large-scale distributed agile: An empirical study

Alsaqaf

Daneva

Wieringa

2019

Information and Software Technology

View full text Add to dashboard Cite

Section: Moving To Agile With a Waterfall Mind-setmentioning

confidence: 99%

Quality requirements challenges in the context of large-scale distributed agile: An empirical study

Alsaqaf

Daneva

Wieringa

2019

Information and Software Technology

View full text Add to dashboard Cite

“…The Requirements Specification for Developers (RSD) approach [14] proposes to create Software Requirements Specifications (SRS) that provide necessary information for developers. This approach does not include a mechanism for identifying and describing dependencies that may exist between requirements, sometimes hindering the readability of requirements descriptions.…”

Section: Discussionmentioning

confidence: 99%

Specifying Requirements for Modern Software Development: A Test-Oriented Methodology

Esperón¹,

Pérez²,

Berná-Martínez³

et al. 2023

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

Most modern computer systems operate in distributed environments. To develop and test such applications, services, and systems, it is necessary to consider the physical devices, architectures, communication, security and deployment mechanisms involved. However, the requirements’ specification process still replicates that of traditional applications: details remain implicit and are hidden in the description. As a result, specifications are difficult to identify and, ultimately, tests are designed in the traditional way: they overlook constraints and fail to achieve the desired effects. Our objective is to design a methodology for specifying requirements in both traditional software and applications deployed in distributed environments. We present an iterative and incremental requirements specification methodology. This methodology allows us to describe functional requirements and incorporate non-functional or quality constraints, which is the main contribution of this proposal. To ensure that quality requirements are specified during the design phase, the methodology proposes a series of phases, stages and artefacts that ensure the discovery and consideration of these requirements. In order to find out the strengths and weaknesses of our methodology, we have carried out a comparative study with other similar proposals in the literature. To this end, evaluation criteria were defined by considering standards and good practices in Requirements Engineering. The results of the comparative study show that our methodology constitutes a solid procedure for a detailed requirements specification from the beginning of the software development cycle. This represents an advance over the rest of the proposals studied. Our methodology contributes to the simplification of the design and execution phases of software testing, enabling traceability between the specified requirements and the designed test cases.

show abstract

“…Neglect of non-functional requirements (NFRs) is common in agile software development (ASD) (Behutiye et al, 2020;Cao and Ramesh, 2008;Inayat et al, 2015;Ramesh et al, 2010;Medeirosa et al, 2020). According to Behutiye et al (2020), the primary challenge is the limited ability of ASD methods to handle NFRs because of insufficiencies related to eliciting, analyzing, modeling, documenting, and managing NFRs.…”

Section: Agile Scalability Requirements Engineeringmentioning

confidence: 99%

“…Time to elicit scalability requirements is scarce, mainly because the industry embraces agile methods intended to be lightweight. Moreover, the agile literature offers little advice on eliciting scalability requirements (Medeirosa et al, 2020). In our previous work, we introduced a set of scalability concepts Brataas and Faegri, 2017) and the first agile method for scalability engineering, the ScrumScale method (Brataas et al, 2020).…”

Section: Introductionmentioning

confidence: 99%

Agile elicitation of scalability requirements for open systems: A case study

Brataas

Martini

Hanssen

et al. 2021

Journal of Systems and Software

View full text Add to dashboard Cite

Requirements specification for developers in agile projects: Evaluation by two industrial case studies

Cited by 22 publications

References 10 publications

Quality requirements challenges in the context of large-scale distributed agile: An empirical study

Quality requirements challenges in the context of large-scale distributed agile: An empirical study

Specifying Requirements for Modern Software Development: A Test-Oriented Methodology

Agile elicitation of scalability requirements for open systems: A case study

Contact Info

Product

Resources

About