Requirements Elicitation

Towards Reducing Communication Gaps in Multicultural and Global Requirements Elicitation

“…Functional requirements are related to specific business functions, tasks, or behaviors that a system under development is expected to support [3]; hence they aim to capture the intended behavior of the system to be developed. Use cases have become a widespread practice for capturing functional requirements.…”

“…For example, the General Data Protection Regulation (GDPR), a regulation in EU law, places a legal obligation for all systems to adhere to integrity and confidentiality (security) [4]. Non-functional requirements are considered problematic as users often state them in terms that are overly vague [3]. They are basically constraints placed on various attributes of business functions or tasks, and they arise from the operating environment, the user(s), and competitive products [3].…”

“…Non-functional requirements are considered problematic as users often state them in terms that are overly vague [3]. They are basically constraints placed on various attributes of business functions or tasks, and they arise from the operating environment, the user(s), and competitive products [3]. Domain requirements refer to domain concepts or specialized domain terminology.…”

“…Linguistic ambiguity due to terminological discrepancies may occur between stakeholders that belong to different technical domains [5]. Since domain requirements are very specialized and requirements engineers find it difficult to understand how they are related to other system requirements, domain experts may leave information out of requirements simply because it is so obvious to them [3].…”