Abstract

Identification of non-functional requirements in an early phase of software development process is crucial for creating a proper software design. These requirements are often neglected or given in too general forms. However, interviews and other sources of requirements often include important references also to non-functional requirements which are embedded in a bigger textual context. The non-functional requirements have to be extracted from these contexts and should be presented in a formulated and standardized way to support software design. The set of requirements extracted from their textual context have to be classified to formalize them. This task is to be accomplished manually but it can be very demanding and error-prone. Several attempts have been made to support identification and classification tasks using supervised and semi-supervised learning processes. These efforts have achieved remarkable results. Researchers were mainly focused on the performance of classification measured by precision and recall. However, creating a tool which can support business analysts with their requirements elicitation tasks, execution time is also an important factor which has to be taken into account. Knowing the performance and the results of benchmarks can help business analysts to choose a proper method for their classification tasks. Our study presented in this article focuses on both the comparison of performances of the classification processes and their execution time to support the choice among the methods.

Highlights

  • Non-functional requirements (NFRs) are crucial factors for software design [1].The lack of a well structured set of non-functional requirements can lead to an inappropriate software design and the failure of the specific project

  • Many NFRs are out of the analysis and even those which are included in specifications are poorly engineered

  • Experiments were conducted to identify appropriate machine learning methods can be used for requirement classification task to support business analysts in their elicitation process

Read more

Summary

Introduction

Non-functional requirements (NFRs) are crucial factors for software design [1]. The lack of a well structured set of non-functional requirements can lead to an inappropriate software design and the failure of the specific project. Security aspects are a critical part of the software design process which is one of the emphasized concern of the software development these days. These aspects cannot be reviewed completely without security related non-functional requirements. The source of requirements are memos of different interviews and regulations, laws and standards. These documents contain texts written in natural languages.

Methods
Results
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call