This system is your system. This system is my system.
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
Automated Quality Assurance of Software Requirements. The following contribution deals with the automated assurance of software requirements quality.
Eliciting security requirements needs a different process
How to capture the functional size of an application in early project phases and how to create a reliable cost estimate
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
Endeavours to improve the situation are finally rewarded
What does OpenAI’s ChatGPT say about RE?
What do we learn from Gender Studies for Requirements Engineering
Analysis, results, and recommendations
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
Using verbs’ valency to improve requirements’ quality
Effective specifications to select off-the-shelf software
An Intelligent Assistant for Improving Requirement Authoring
Insights for 13 crucial challenges
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
The True Measure of Requirements Quality.
Readable requirements are not a matter of course – or are they?
An Approach for the Inspection of the Completeness of individual Software Requirements Specifications by Semantic Analysis of the Argument Structures
A study concerning the question of whether domain knowledge is rather conducive, or rather hindering, for a requirements engineer
An experience report from the IREB Academy Program in Africa
Goals are intended, Requirements are imposed
When shall does not need to be must
Strategies for building manageable requirements hierarchies in complex problem domains
Reverse Modeling and Up-To-Date Evolution of Functional Requirements in Alignment with Tests
From Requirements to Code
No Double Dutch! [An article of the Inside IREB series]
Preliminary Results from an Ongoing Study
Improving requirements quality by effort estimates
How Product Owners (POs), Business Analysts and Requirements Engineers Use Agile Requirements Engineering (RE) to optimize the work of the team and maximize the value delivered to stakeholders.