It's the Activities, Stupid! A New Perspective on RE Quality

Femmer, Henning; Mund, Jakob; Fernández, Daniel Méndez

doi:10.1109/ret.2015.11

Cited by 22 publications

(56 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For each content element, we classify whether it is a mandatory or optional content element. To achieve is, we follow the idea of activity-based quality models [14] and consider development activities that take performance requirements as input, such as defining a performance test case. We identify necessary and important content elements that a performance requirement must contain to complete these development activities efficiently and effectively.…”

Section: Methodsmentioning

confidence: 99%

“…Following the idea of an activity-based definition of quality attributes (see [14], [16]), we created a notion of completeness based on development activities that stakeholders conduct with performance requirements. We identified necessary content elements that a performance requirement must contain to complete these development activities efficiently and effectively.…”

Section: Notion Of Completeness For Performance Requirementsmentioning

confidence: 99%

“…Activity-based quality models (e.g., [14], [16]) provide frameworks to define and operationalize quality attributes such as completeness. In our study, we derived a content model for performance requirements based on the question which content is necessary to perform specific activities.…”

Section: A Implications For Academiamentioning

confidence: 99%

“…A less strict content model, that defines less mandatory content elements, would result in more requirements that are considered complete. From our point of view, a "good" definition of the content model should be derived from the activities that need to be performed based on the requirements (see [14]). We tried to justify all mandatory content elements in our content model by considering development activities that are not or hardly possible without this content.…”

Section: Limitations and Threatsmentioning

confidence: 99%

See 3 more Smart Citations

Challenging Incompleteness of Performance Requirements by Sentence Patterns

Eckhardt

Vogelsang

Femmer

et al. 2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

Self Cite

View full text Add to dashboard Cite

Section: Methodsmentioning

confidence: 99%

Section: Notion Of Completeness For Performance Requirementsmentioning

confidence: 99%

Section: A Implications For Academiamentioning

confidence: 99%

Section: Limitations and Threatsmentioning

confidence: 99%

See 2 more Smart Citations

Challenging Incompleteness of Performance Requirements by Sentence Patterns

Eckhardt

Vogelsang

Femmer

et al. 2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

Self Cite

View full text Add to dashboard Cite

“…Example of such studies are, [41] that address the issue of alignment with a model for defining and validating RE quality in a precise and systematic way, and [42] presenting a tool to model NFRs to support alignment.…”

Section: Focus Of Research (Rq2)mentioning

confidence: 99%

What Do We Know about Alignment of Requirements Engineering and Software Testing?

Karhapää

Haghighatkhah

Oivo

2017

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Context:The alignment of different software engineering activities for coordinated functioning and optimized product development is of great importance, particularly in industrialscale development. The link between intermediate activities has been researched extensively, but the link between requirements engineering (RE) and software testing (ST) is a relatively less explored area. Objective: The objective of this study is to aggregate, structure, and classify all existing research regarding alignment of RE and ST published by the end of 2015. Method: We conducted a systematic mapping study (SMS) and aggregated all studies relevant to our scope. The primary studies are analyzed in terms of publication trend, focus area, i.e., how alignment is supported, the application domain and benefits and challenges, methodological data, and scientific rigor and industrial relevance. Results: There is a growing interest towards the topic. Several different techniques have been identified to improve RE and ST alignment. Test generation from requirements specification has received most attention. Alignment of RE and ST is particularly important for large safety-critical domains. While many challenges have been reported, the supporting evidence for benefits is scarce. Frameworks/methods/techniques is the most frequent contribution type. Solution proposal and evaluation research were the most frequently applied research type. Case study research was the most frequently applied research method, however, almost half of the studies did not clearly report any research method. Conclusion: Despite the numerous approaches that are proposed, it is not clear what approach is suitable in what context and why. To support industry in RE and ST alignment, guidelines and tool support are needed. The supporting evidence for claimed benefits is very limited. Overall, the research area is in its early stages and an increase in both the number and rigor of empirical studies are required.

show abstract

Crossing Disciplinary Borders to Improve Requirements Communication

Hess

2022

Ernst Denert Award for Software Engineering 2020

View full text Add to dashboard Cite

Software requirements specifications (SRS) serve as an important source of information for a variety of roles involved in software engineering (SE) projects. This situation poses a challenge to requirements engineers: Different information needs have to be addressed, which are strongly dependent on the particular role(s) that SRS stakeholders have within a project. This chapter summarizes the contributions of a thesis that aimed to address and reduce role-specific defects in SRS that negatively influence the efficient usage and acceptance of these documents. To achieve this goal, we collected empirical data about role-specific information needs in a series of empirical studies that served as a baseline for a secondary analysis toward the definition of role-specific views. Moreover, we realized a proof-of-concept implementation that is capable of generating role-specific views on SRS. The results of a case study revealed that role-specific views have the potential to efficiently support SRS consumers during the analysis of a given SRS. Besides conducting further empirical studies in industry, future work aims to foster cross-disciplinary collaboration and requirements communication, especially in agile teams. Thereby, we are exploring synergy potential with best practices from non-SE disciplines.

show abstract

It's the Activities, Stupid! A New Perspective on RE Quality

Cited by 22 publications

References 10 publications

Challenging Incompleteness of Performance Requirements by Sentence Patterns

Challenging Incompleteness of Performance Requirements by Sentence Patterns

What Do We Know about Alignment of Requirements Engineering and Software Testing?

Crossing Disciplinary Borders to Improve Requirements Communication

Contact Info

Product

Resources

About