Requirements Engineering is one of the most vital activities in the entire Software
Development Life Cycle. The success of the software is largely dependent on how well the …

Context In large software development projects a huge number of unstructured text
documents from various stakeholders becomes available and needs to be analyzed and …

User stories are a widely adopted requirements notation in agile development. Yet, user
stories are too often poorly written in practice and exhibit inherent quality defects. Triggered …

User stories are a widely used notation for formulating requirements in agile development
projects. Despite their popularity in industry, little to no academic work is available on …

Extracting conceptual models from natural language requirements can help identify
dependencies, redundancies, and conflicts between requirements via a holistic and easy-to …

Natural language (NL) is still the predominant notation that practitioners use to represent
software requirements. Albeit easy to read, NL does not readily highlight key concepts and …

In the architecture, engineering, and construction (AEC) industry, manual compliance
checking is labor-intensive, time-consuming, expensive, and error-prone. Automated …

Improving the quality of software demands quality controls since the very beginning of the
development process, ie, requirements capture and writing. Automating quality metrics may …

A glossary is an important part of any software requirements document. By making explicit
the technical terms in a domain and providing definitions for them, a glossary helps mitigate …

Interviews are the most common and effective means to perform requirements elicitation and
support knowledge transfer between a customer and a requirements analyst. Ambiguity in …