- 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)
Why Testers should have a closer look into Requirements Engineering
Requirements Reuse with the PABRE Framework
Automated Quality Assurance of Software Requirements. The following contribution deals with the automated assurance of software requirements quality.
Effective product management is the critical success factor to make a product successful – across its life-cycle and across markets.
Readable requirements are not a matter of course – or are they?
A Framework for Systematic Requirements Development in Information Systems.
Part 2: The Art of Assigning Software Development
Eliciting security requirements needs a different process
An Intelligent Assistant for Improving Requirement Authoring
How can the standard UML FSM be improved to better serve the requirements engineer?
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
Effective specifications to select off-the-shelf software
Results of research project announced in a previous issue.
How to create awareness for some of the difficulties requirements engineers face
Driving innovation with crowd-based techniques
Analysis, results, and recommendations
When shall does not need to be must
A new approach to accelerate the RE-process!
How bias will affect even the simplest of specifications
Agile in the Large Enterprise
Goals are intended, Requirements are imposed
From Requirements to Code
Some thoughts on problems and goals in the context of requirements engineering
A short and fun elicitation workshop for Agile teams and architects
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
Using verbs’ valency to improve requirements’ quality
An Approach for the Inspection of the Completeness of individual Software Requirements Specifications by Semantic Analysis of the Argument Structures
Insights for 13 crucial challenges
Preliminary Results from an Ongoing Study
The Future How Viewpoint.
Views of a real RE pioneer
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
How you can use the natural partitioning of business events to flexibly synchronise your agile development.
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
Endeavours to improve the situation are finally rewarded
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.
What does OpenAI’s ChatGPT say about RE?
Strategies for building manageable requirements hierarchies in complex problem domains