- Practice
- Studies and Research
By search term
By topic
By tag
- Testing (10)
- Agile (33)
- Approaches (49)
- Attributes (4)
- Business Analysis (28)
- Elicitation (32)
- Estimation (5)
- Prioritization (8)
- Team (20)
- User Story (14)
- Template (4)
- Framework (12)
- Goals (10)
- Reuse (2)
- Software Engineering (14)
- Traceability (10)
- Perception (10)
- Management (18)
- Verification (6)
- Development (16)
- CPRE (5)
- Study (15)
- Automation (7)
- Documentation (24)
- Software Quality (13)
- ReqIF (1)
- Standards (10)
- Analysis (21)
- Business Value (14)
- Metrics (6)
- Validation (14)
- Modeling (14)
- Security (5)
- SysML (3)
- Stakeholder (14)
- Big Data (4)
- Opinion (18)
- Literature (4)
- AI (6)
- Digital Design (3)
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)
- 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)
- Michael Jastram (3)
Articles
Showing 32 articles tagged with Modeling, Prioritization, ReqIF or User Story [max. 4 tags]
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.
- Methods
Reverse Modeling and Up-To-Date Evolution of Functional Requirements in Alignment with Tests
- Methods
- Skills
How to create awareness for some of the difficulties requirements engineers face
- Methods
- Practice
Strategies for building manageable requirements hierarchies in complex problem domains
- Opinions
When shall does not need to be must
- Practice
- Methods
Integrating explainability and privacy as a first step towards a stakeholder needs taxonomy
- Methods
- Practice
Classifying product techniques by requirements type
- Practice
- Methods
Why Testers should have a closer look into Requirements Engineering
- Practice
How the ReqIF Standard for Requirements Exchange Disrupts the Tool Market.
- Methods
How modeling can be useful to better define and trace requirements
- Methods
- Practice
Smart use of constraints leads to cleaner requirements that are easy to test
- Methods
- Practice
An Example from the Automation Industry
- Practice
- Cross-discipline
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
- Practice
- Methods
‘A large elephant is in the room but we are not able or brave or willing enough to point at it’
- Methods
An approach for iterative and requirements-based quality assurance in DevOps
- Practice
- Opinions
When every new iteration can violate previously satisfied requirements
- Opinions
Views of a real RE pioneer
- Cross-discipline
- Methods
How you can use the natural partitioning of business events to flexibly synchronise your agile development.
- Methods
- Practice
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
- Methods
- Practice
An agile and collaborative prioritization technique
- Methods
- Cross-discipline
The Future How Viewpoint.
- Methods
- Practice
A Structural Analysis of Prioritization Pitfalls in Agile Hierarchies
- Methods
An application of the IREB Handbook of Requirements Modeling
- Methods
- Skills
Evaluating Business Analysts‘ role in the Data Driven Economy
- Cross-discipline
- Practice
What does OpenAI’s ChatGPT say about RE?
- Methods
- Skills
Endeavours to improve the situation are finally rewarded
- Methods
- Opinions
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
- Practice
- Methods
When requirements and the product are elaborated concurrently
- Practice
- Cross-discipline
Implementation and Future Trends
- Practice
- Cross-discipline
Introduction and Concepts
- Opinions
- Cross-discipline
This system is your system. This system is my system.
- Methods
How can the standard UML FSM be improved to better serve the requirements engineer?