Over the last decade, machine learning methods have revolutionized a large number of domains and provided solutions to many problems that people could hardly solve in past. The availability amounts data, powerful processing architectures, easy-to-use software frameworks made popular, readily available, affordable option different contexts. However, development maintenance production-level syste...

Natural Language Processing for Requirements Engineering (NLP4RE) is an area of research and development that seeks to apply natural language processing (NLP) techniques, tools, resources the requirements engineering (RE) process, support human analysts carry out various linguistic analysis tasks on textual documents, such as detecting issues, identifying key domain concepts, establishing trace...

Traditional approaches to requirements elicitation stress systematic and rational analysis and representation of organizational context and system requirements. This paper argues that the introduction of any computer-based system to an organization transforms the organization and changes the work patterns of the system’s users in the organization. These changes interact with the users’ values a...

There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the cancellation of system development, or else the ...

This paper examines the use of Bayesian Networks to tackle one of the tougher problems in requirements engineering, translating user requirements into system requirements. The approach taken is to model domain knowledge as Bayesian Network fragments that are glued together to form a complete view of the domain specific system requirements. User requirements are introduced as evidence and the pr...

Software requirements are defined in many industries using informal software requirements specifications that are based on standards such as IEEE 830. Also, in teams of small to medium-sized projects there are often no experienced requirements engineers. These two factors leave product development efforts in a tar pit of ambiguities and misunderstandings that is risking product success. We inve...

Many managers and others who are not professional requirements engineers tend to greatly oversimplify requirements engineering (RE). Based on their observations that requirements specifications primarily contain narrative English textual statements of individual requirements and that all members of the engineering team are reasonably literate, there is a common myth that practically anyone with...

Inconsistency is a major challenge in requirements engineering. Traditionally, software requirements specifications (SRSs) are expected to be consistent, with the underlying assumption that this consistency is always achievable. However, with the growing complexity of software systems it has become clear that this assumption is not always realistic. This has led to new paradigms for inconsisten...

Recently, a lot of research efforts in software engineering have focused on integrating business modeling as a key piece in requirements engineering. In these research works, the business models are proposed as the source of the software requirements specification process. However, the majority of these works focus only on the definition of notations that permit the representation of the semant...