Towards auto-completion on software requirements statements
Carlos Alberto dos Santos, Fabio Petrillo
TL;DR
This paper explores how auto-completion can enhance the quality of software requirements documentation by addressing issues of ambiguity and incompleteness, emphasizing human factors in modern software development.
Contribution
It proposes an approach to implement auto-completion for software requirements statements to improve clarity and completeness, filling a gap in existing tools.
Findings
Auto-completion can reduce ambiguity in requirements.
Improves completeness of requirements documentation.
Enhances human participation in requirements elicitation.
Abstract
As software systems become more complex, modern software development requires more attention to human perspectives, and active participation of development teams in requirements elicitation tasks. In this context, incomplete or ambiguous requirements descriptions do not guide the development of good software products. We hypothesize that the text auto-completion feature improves the quality of the software requirements artifacts. We present the motivation for this study, related works, our approach and future research efforts.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Research · Advanced Software Engineering Methodologies · Software Engineering Techniques and Practices