- Methods
- Practice
By search term
By topic
By tag
- Testing (9)
- Agile (29)
- Approaches (42)
- Attributes (4)
- Business Analysis (21)
- Elicitation (27)
- Estimation (5)
- Prioritization (7)
- Team (17)
- User Story (11)
- Template (3)
- Framework (10)
- Goals (8)
- Reuse (2)
- Software Engineering (9)
- Traceability (9)
- Perception (10)
- Management (14)
- Verification (6)
- Study (15)
- Development (12)
- CPRE (5)
- Automation (6)
- Documentation (20)
- Software Quality (10)
- ReqIF (1)
- Standards (6)
- Analysis (19)
- Business Value (10)
- Metrics (5)
- Validation (10)
- Modeling (14)
- Security (3)
- SysML (3)
- Stakeholder (12)
- Big Data (4)
- Opinion (15)
- Literature (4)
By author
- 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)
Articles
Showing 32 articles tagged with Documentation, Template, User Story or Verification [max. 4 tags]
Delegation of requirement verification. A key technique for more mature requirements management.
- Methods
Verification and Validation of System Requirements by Animation and Automated Formal Analysis.
- Practice
- Methods
When requirements and the product are elaborated concurrently
- Practice
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
- Methods
Automated Quality Assurance of Software Requirements. The following contribution deals with the automated assurance of software requirements quality.
- Practice
Eliciting security requirements needs a different process
- Methods
- Opinions
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
- Methods
- Skills
Endeavours to improve the situation are finally rewarded
- Cross-discipline
- Practice
What does OpenAI’s ChatGPT say about RE?
- Studies and Research
Analysis, results, and recommendations
- Methods
- Practice
An agile and collaborative prioritization technique
- Methods
- Practice
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
- Practice
- Opinions
When every new iteration can violate previously satisfied requirements
- Methods
Using verbs’ valency to improve requirements’ quality
- Methods
- Practice
Effective specifications to select off-the-shelf software
- Methods
An approach for iterative and requirements-based quality assurance in DevOps
- Studies and Research
An Intelligent Assistant for Improving Requirement Authoring
- Practice
- Opinions
Insights for 13 crucial challenges
- Practice
- Cross-discipline
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
- Methods
- Practice
An Example from the Automation Industry
- Practice
- Methods
Why Testers should have a closer look into Requirements Engineering
- Practice
- Methods
Readable requirements are not a matter of course – or are they?
- Methods
- Cross-discipline
An Approach for the Inspection of the Completeness of individual Software Requirements Specifications by Semantic Analysis of the Argument Structures
- Methods
A new approach for requirements validation and rigorous verification.
- Opinions
Goals are intended, Requirements are imposed
- Opinions
When shall does not need to be must
- Methods
- Practice
Strategies for building manageable requirements hierarchies in complex problem domains
- Methods
- Skills
How to create awareness for some of the difficulties requirements engineers face
- Practice
- Methods
It seems evident to test designs or prototypes of software with end-users. But what about requirements?
- Methods
From Requirements to Code
- Studies and Research
- Practice
Preliminary Results from an Ongoing Study
- Practice
- Studies and Research
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.