Early Foundations and Practical Adjustments (2005-2008)
The mid-2000s saw Requirements Engineering (RE) solidifying its foundational concepts while also grappling with its practical application in the rapidly evolving tech landscape. In 2005, the focus was on core techniques, exemplified by an article discussing "goal-modeling techniques," indicating an early emphasis on structured approaches.
By 2006, the conversation shifted towards more tangible aspects: how to "Improve Your Requirements: Quantify Them" and the emerging relevance of new technologies, as seen in "Take your mobile device out from behind the requirements desk." This suggests a move from theoretical underpinnings to measurable outcomes and adapting to new platforms. The years 2007 and 2008 continued this trend by acknowledging the inherent complexity and context-dependency of requirements ("My Requirements? Well, That Depends," "From the Horse's Mouth"). There was also a notable reflection on the discipline's longevity with "Requirements 25 Years On," alongside a clear distinction between "User Requirements and System Requirements," highlighting a growing understanding of different stakeholder perspectives.
Navigating Complexity and Human Elements (2009-2012)
This period reveals a deepening appreciation for the nuanced and often challenging human and organizational aspects of requirements work. In 2009, titles like "How to Use Web Services in Your Requirements Process" and "Card Sorts to Acquire Requirements" point to the adoption of new technical tools and practical elicitation techniques. However, there's also a burgeoning recognition of the analyst's role and its inherent difficulties, as hinted by "Oi, Analyst You're Barred!" and the need for "Handling Context."
The year 2010 introduced the crucial discussion around Agile methodologies with "Agile Requirements Can We Have Our Cake and Eat It Too?", signaling the start of a long-standing debate on integrating agile practices within RE. The human dimension continued to be explored with "Trust Me, I'm an Analyst" and new visualization methods like "Storyboarding Requirements." By 2011, the field began to look ahead ("Requirements Analysis: The Next Generation") and consider more abstract qualities such as "Requirements and Aesthetics," alongside the personal challenges faced by practitioners ("The Inhibited Analyst"). This trend culminated in 2012, where titles like "Politics Are Inescapable" and "Spocks and Kirks in the Requirements Universe" underscore the acknowledgment of interpersonal dynamics and inherent ambiguities ("Cherishing Ambiguity") in requirements work, moving beyond purely technical considerations to embrace the 'soft skills' and learning aspects ("Framing Requirements Work as Learning").
Architectural Depth and Value-Driven Approaches (2013-2015)
The mid-2010s marked a significant focus on strategic aspects of requirements, particularly their connection to system architecture and the drive for business value. In 2013, a strong theme emerged around "Architecturally Significant Requirements" (ASRs), with titles like "Thinking about Quoins: Strategic Traceability of Architecturally Significant Requirements" and "Meet Elaine: A Persona-Driven Approach to Exploring Architecturally Significant Requirements." This period also featured a meta-analysis of the discipline itself with "Are Requirements Alive and Kicking?" and "So, What Is Requirements Work?", alongside a growing interest in continuous oversight ("Monitoring Our Requirements").
By 2014, the scope broadened to consider requirements in a "Global World" and the challenges of managing difficult stakeholders ("How Well Do You Know Your Personae Non Gratae?"). A significant shift toward achieving quality goals through rigorous understanding ("Beyond Anecdotal Thinking") and avoiding project pitfalls ("Don't Fire the Architect! Where Were the Requirements?") became prominent. The year 2015 solidified this value-driven perspective. Titles like "From Raw Project Data to Business Intelligence" and "Mining Domain Knowledge [Requirements]" highlight a move towards data-informed decision-making. The emphasis on "Injecting Value-Thinking into Prioritization Decisions" and fostering "Meaningful Industrial--Academic Partnerships" clearly indicates a push for RE to directly contribute to business outcomes and bridge the gap between research and practice.
Self-Assessment, Ubiquity, and Societal Impact (2017-2019)
The late 2010s represented a period of deep introspection for the Requirements Engineering community, coupled with a broadening of its perceived societal and practical reach. In 2017, the field critically examined its own maturity with "RE@40: Midlife Crisis or Graceful Maturity?", alongside reflections on the practical realities faced by practitioners in industry ("The Unplanned Journey of a Requirements Engineer").
By 2018, the conversation became even more granular concerning practical application, exploring the elusive concept of "How Common Is Common Enough in Requirements-Engineering Practice?" and offering "Heuristics for Common-Enough Requirements Practice," indicating a move towards pragmatic, experience-based guidance. The year 2019 marked a significant expansion and self-evaluation. There was a clear push to review the discipline's progress ("Is Requirements-Engineering Research Delivering What It Promised?") and question existing metrics ("The Quest for Meaningful Metrics: Time for a Change?"). Crucially, the scope of RE expanded dramatically to include a societal dimension ("Requirements Engineering (RE) for Social Good: RE Cares") and a pervasive presence across various contexts ("Ubiquitous Requirements Engineering: A Paradigm Shift That Affects Everyone"). Challenges in "Large-Scale Agile System Development" also came to the forefront, highlighting the ongoing integration complexities.
Emerging Technologies and Inclusive Quality (2020)
The most recent year in the dataset showcases Requirements Engineering directly confronting the impact of cutting-edge technologies and embracing new dimensions of quality. The pervasive influence of Artificial Intelligence is evident in "Requirements Engineering in the Days of Artificial Intelligence," and blockchain technology enters the RE discourse with "RE_BBC: Requirements Engineering in a Blockchain-Based Cloud." This highlights a rapid adaptation to and engagement with transformative digital trends.
Perhaps the most significant new theme is the explicit consideration of social factors as a quality requirement. "Gender Inclusivity as a Quality Requirement: Practices and Pitfalls" marks a notable expansion of what constitutes 'quality' in software and systems, moving beyond traditional functional and non-functional aspects to incorporate ethical and social considerations. The continued evolution of Agile practices is also observed, with "Shu-Ha-Ri for RE? An Agile Approach to Requirements Engineering Practitioner Maturity" indicating a deeper exploration of professional development within agile contexts. This year underscores RE's role not just in technical systems, but also in shaping their social and ethical implications.
