Subtopic Deep Dive
Requirements Engineering
Research Guide
What is Requirements Engineering?
Requirements Engineering is the disciplined approach to eliciting, modeling, analyzing, validating, and managing software requirements throughout the development lifecycle.
This subtopic encompasses techniques for handling functional and non-functional requirements, including goal-oriented modeling and traceability. Key works include Nuseibeh and Easterbrook (2000, 1792 citations) providing a roadmap and Kotonya and Sommerville (1998, 1710 citations) detailing processes. Chung and Leite (2009, 2240 citations) focus on non-functional requirements.
Why It Matters
Effective requirements engineering cuts software project failure rates by aligning systems with stakeholder needs, as shown in Jacobson (1992, 2943 citations) use case-driven methods reducing rework. In agile contexts, it supports requirements evolution, per Kruchten (1998, 2606 citations) iterative processes. Nuseibeh and Easterbrook (2000) highlight traceability impacts on maintenance costs in large-scale systems.
Key Research Challenges
Eliciting Non-Functional Requirements
Capturing vague qualities like performance and security from stakeholders remains difficult. Chung and Leite (2009) outline formal modeling gaps. Conflicts arise in prioritization without structured methods.
Traceability in Agile Environments
Maintaining links between requirements and code in iterative development challenges change management. Kotonya and Sommerville (1998) note tool limitations. Nuseibeh and Easterbrook (2000) discuss evolution tracking issues.
Requirements Validation Scalability
Verifying complex requirements sets grows computationally expensive. Petersen et al. (2008, 3043 citations) map systematic review needs. Jacobson (1992) use cases reveal validation bottlenecks in large projects.
Essential Papers
Software Product Lines: Practices and Patterns
Paul Clements, Linda Northrop · 2001 · 3.2K citations
Foreword. Preface. Acknowledgements. Dedication. Reader's Guide. I. SOFTWARE PRODUCT LINE FUNDAMENTALS. 1. Basic Ideas and Terms. What Is a Software Product Line? What Software Product Lines Are No...
Systematic Mapping Studies in Software Engineering
Kai Petersen, Robert Feldt, Shahid Mujtaba et al. · 2008 · Electronic workshops in computing · 3.0K citations
BACKGROUND: A software engineering systematic map is a defined method to build a classification scheme and structure a software engineering field of interest. The analysis of results focuses on fre...
Object Oriented Software Engineering: A Use Case Driven Approach
Ivar Jacobson · 1992 · 2.9K citations
Part 1. Introduction 1. System development as an industrial process Introduction A useful analogy System development characteristics Summary 2. The system life cycle Introduction System development...
Groupware: some issues and experiences
Clarence A. Ellis, Simon Gibbs, Gail L. Rein · 1991 · Communications of the ACM · 2.7K citations
article Free Access Share on Groupware: some issues and experiences Authors: Clarence A. Ellis MCC, Austin, TX MCC, Austin, TXView Profile , Simon J. Gibbs View Profile , Gail Rein View Profile Aut...
The Rational Unified Process: An Introduction
Philippe Kruchten · 1998 · 2.6K citations
(NOTE: Each chapter concludes with a summary.) Preface. I. THE PROCESS. 1. Software Development Best Practices. The Value of Software. Symptoms and Root Causes of Software Development Problems. Sof...
Generative Programming: Methods, Tools, and Applications
Krzysztof Czarnecki, Ulrich W. Eisenecker · 2000 · 2.5K citations
1. What Is This Book About? From Handcrafting to Automated Assembly Lines. Generative Programming. Benefits and Applicability. I. ANALYSIS AND DESIGN METHODS AND TECHNIQUES. 2. Domain Engineering. ...
On Non-Functional Requirements in Software Engineering
Lawrence Chung, Julio César Sampaio do Prado Leite · 2009 · Lecture notes in computer science · 2.2K citations
Reading Guide
Foundational Papers
Start with Nuseibeh and Easterbrook (2000) for roadmap overview, then Kotonya and Sommerville (1998) for processes, and Jacobson (1992) for use case foundations.
Recent Advances
Chung and Leite (2009) on non-functionals; Petersen et al. (2008) mapping studies for field structure.
Core Methods
Goal-oriented (Nuseibeh 2000), use case-driven (Jacobson 1992), iterative unification (Kruchten 1998), systematic mapping (Petersen 2008).
How PapersFlow Helps You Research Requirements Engineering
Discover & Search
Research Agent uses searchPapers and citationGraph to map Requirements Engineering literature, starting from Nuseibeh and Easterbrook (2000), revealing 1792 citing works on validation techniques. exaSearch finds goal-oriented papers; findSimilarPapers clusters non-functional requirements studies like Chung and Leite (2009).
Analyze & Verify
Analysis Agent applies readPaperContent to extract elicitation processes from Kotonya and Sommerville (1998), then verifyResponse with CoVe checks claims against Jacobson (1992) use cases. runPythonAnalysis computes citation trends via pandas on 250M+ OpenAlex data; GRADE grades evidence strength for non-functional modeling claims.
Synthesize & Write
Synthesis Agent detects gaps in agile traceability via contradiction flagging across Kruchten (1998) and Nuseibeh (2000). Writing Agent uses latexEditText, latexSyncCitations for requirements diagrams, and latexCompile for report export; exportMermaid visualizes goal hierarchies.
Use Cases
"Analyze citation networks for non-functional requirements evolution papers post-2000."
Research Agent → citationGraph on Chung and Leite (2009) → runPythonAnalysis (networkx for centrality) → CSV export of top influencers.
"Draft LaTeX section on use case driven requirements with synced citations."
Synthesis Agent → gap detection → Writing Agent → latexEditText + latexSyncCitations (Jacobson 1992, Kotonya 1998) → latexCompile PDF.
"Find GitHub repos implementing goal-oriented requirements tools from papers."
Research Agent → paperExtractUrls → Code Discovery → paperFindGithubRepo → githubRepoInspect for traceability prototypes.
Automated Workflows
Deep Research workflow conducts systematic mapping like Petersen et al. (2008): searchPapers → 50+ papers → structured report with GRADE. DeepScan analyzes Nuseibeh (2000) via 7-step CoVe checkpoints for validation techniques. Theorizer generates evolution models from Clements (2001) product line practices.
Frequently Asked Questions
What is Requirements Engineering?
Requirements Engineering systematically elicits, models, validates, and evolves software needs (Nuseibeh and Easterbrook, 2000).
What are key methods in Requirements Engineering?
Methods include use case modeling (Jacobson, 1992) and non-functional formalization (Chung and Leite, 2009); processes from Kotonya and Sommerville (1998).
What are seminal papers?
Nuseibeh and Easterbrook (2000, 1792 citations) roadmap; Kotonya and Sommerville (1998, 1710 citations) techniques; Jacobson (1992, 2943 citations) use cases.
What open problems exist?
Scalable validation in agile (Kruchten, 1998); non-functional elicitation gaps (Chung and Leite, 2009); traceability automation (Nuseibeh and Easterbrook, 2000).
Research Advanced Software Engineering Methodologies with AI
PapersFlow provides specialized AI tools for Computer Science researchers. Here are the most relevant for this topic:
AI Literature Review
Automate paper discovery and synthesis across 474M+ papers
Code & Data Discovery
Find datasets, code repositories, and computational tools
Deep Research Reports
Multi-source evidence synthesis with counter-evidence
AI Academic Writing
Write research papers with AI assistance and LaTeX support
See how researchers in Computer Science & AI use PapersFlow
Field-specific workflows, example queries, and use cases.
Start Researching Requirements Engineering with AI
Search 474M+ papers, run AI-powered literature reviews, and write with integrated citations — all in one workspace.
See how PapersFlow works for Computer Science researchers