- Testing (9)
- Agile (28)
- Approaches (41)
- Attributes (4)
- Business Analysis (19)
- Elicitation (25)
- Estimation (5)
- Prioritization (6)
- Team (17)
- User Story (11)
- Template (3)
- Framework (9)
- Goals (8)
- Reuse (2)
- Software Engineering (9)
- Traceability (9)
- Perception (10)
- Management (13)
- Verification (6)
- Study (15)
- Development (12)
- CPRE (5)
- Automation (6)
- Documentation (20)
- Software Quality (10)
- ReqIF (1)
- Standards (6)
- Analysis (18)
- Business Value (10)
- Metrics (5)
- Validation (9)
- Modeling (14)
- Security (3)
- SysML (3)
- Stakeholder (11)
- Big Data (4)
- Opinion (15)
- Literature (4)
- Howard Podeswa (3)
- Rainer Grau (2)
- Erik van Veenendaal (1)
- Cristina Palomares (1)
- Carme Quer (1)
- Xavier Franch (2)
- Mats Wessberg (1)
- Kim Lauenroth (2)
- Joseph Aracic (1)
- IREB (1)
- Jens Schirpenbach (1)
- Alexander Rachmann (1)
- Jesko Schneider (1)
- Frank Engel (1)
- Dr. Ralph R. Young (2)
- Maria-Therese Teichmann (1)
- Eva Gebetsroither (1)
- Corinna Unterfurtner (1)
- Alexandra Kreuzeder (1)
- Harry Sneed (2)
Has RE adapted itself to the challenges of Agile methods?
Insights for 13 crucial challenges
Do you know what acceptance criteria are?
Goals are intended, Requirements are imposed
Building the bridge between experience and research: The future Research Section of the RE Magazine
Views of a real RE pioneer
Why Testers should have a closer look into Requirements Engineering
When shall does not need to be must
The Future How Viewpoint.
How you can use the natural partitioning of business events to flexibly synchronise your agile development.
How bias will affect even the simplest of specifications
Using Hypothesis Testing and Metrics to Drive Requirements Elicitation
What do we learn from Gender Studies for Requirements Engineering
Part 2: The Art of Assigning Software Development
How to create awareness for some of the difficulties requirements engineers face
Preliminary Results from an Ongoing Study
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
The True Measure of Requirements Quality.
It seems evident to test designs or prototypes of software with end-users. But what about requirements?
Transitioning successfully from the IT side to business – and 5 questions you should ask yourself before moving from the tech side to Business Analysis
Using verbs’ valency to improve requirements’ quality
Results of research project announced in a previous issue.
Preliminary Results of a Questionnaire
Eliciting security requirements needs a different process
Who works in RE and what competences do they need, particularly soft skills?
Lessons learned from a European Framework Project
Readable requirements are not a matter of course – or are they?
An approach for iterative and requirements-based quality assurance in DevOps
Effective product management is the critical success factor to make a product successful – across its life-cycle and across markets.
A statistical analysis and trends from 2009 to 2015
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
An Intelligent Assistant for Improving Requirement Authoring
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.
How can the standard UML FSM be improved to better serve the requirements engineer?
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
Evaluating Business Analysts‘ role in the Data Driven Economy
Reverse Modeling and Up-To-Date Evolution of Functional Requirements in Alignment with Tests
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
What does OpenAI’s ChatGPT say about RE?
Automated Quality Assurance of Software Requirements. The following contribution deals with the automated assurance of software requirements quality.
Driving innovation with crowd-based techniques
An Approach for the Inspection of the Completeness of individual Software Requirements Specifications by Semantic Analysis of the Argument Structures
Strategies for building manageable requirements hierarchies in complex problem domains
Endeavours to improve the situation are finally rewarded
From Requirements to Code
Analysis, results, and recommendations
Effective specifications to select off-the-shelf software
A study concerning the question of whether domain knowledge is rather conducive, or rather hindering, for a requirements engineer