Sitemap

• issues
• 2014-01 Learning to Fly
• Five Questions
• Innovation Arena
• Think Like a Scientist
• Requirements Reuse
• What does it mean?
• RE for Testers
• 2014-02 Gathering speed
• Toward Better RE
• Product Owner in Scrum
• Opportunities & Approaches
• Gender Studies
• A key technique
• Building the bridge
• 2014-03 Gaining height
• Project Value Delivered
• Automated Quality Assurance
• Open Up
• How agile can Requirements Engineers really be?
• Rigorous Verification
• Product Management
• 2014-04 Steady flight
• Advance
• Poor requirements?
• TORE
• Readable requirements
• Customized Agile RE Process
• Translating Exam Questions
• 2015-01 Ruling complexity
• Catching the worm
• Agile Product Ownership
• The Recover Approach
• Agility and Obligation
• Bridging communication gaps with a Feature Tree
• Requirements Engineering and Agile
• 2015-02 Bridging the impossible
• Mobile RE
• Building in security instead of testing it in
• Agility and Obligation
• RE in Agile Projects: a Survey
• Modeling Requirements with SysML
• LELIE
• 2015-03 Thinking without limits
• Applying IREB RE practices in an agile environment
• A Finite State Machine Model for Requirements Engineering
• The Business Analysis Center of Excellence
• Is requirements engineering still needed in agile development approaches?
• Requirements Elicitation (ReqElic) in My Company
• Requirements under construction
• 2015-04 Building the extreme
• Cyber Security Requirements Engineering
• IT Requirements when Buying, not Making
• Survival Kit for the RE Guy
• An “agile” lifecycle for requirements
• Stable? Fragile? Agile! Attractive but reasonable
• Requirements Engineering Workshop in Mozambique
• 2016-01 Seeking new perspectives
• The Genius Toddler Challenge
• Requirements Engineering in Research Projects: Food for Thought
• What makes Women Better BAs
• Evolving and Improving the Requirements Approach to Big Data Projects
• NLP for Requirements Engineers, Part 1
• RE in Agile Projects: Survey Results
• 2016-02 Take the broader view
• How Requirements Engineering can benefit from crowds
• Modeling Requirements and Context as a means for Automated Requirements Validation
• Leveraging Creativity Techniques in Requirements Elicitation
• NLP for Requirements Engineers, Part 2
• Managing the Invisible
• Sharing My Doubts on Acceptance Criteria
• 2016-03 An eye for detail
• Requirements Engineering in German Job Advertisements
• Modeling Requirements with Constraints
• KCycle: Knowledge-Based & Agile Software Quality Assurance
• The Context-Canvas
• Improving the Use of English in Requirements
• Sharing My Doubts on Shall / Should / Will etc.
• 2017-01 All lights on green
• Functional Requirements and their levels of granularity
• The Business Case for Agile Business Analysis
• Biased Toddlers
• Making “agiLE” Work
• Tracing Change Requests
• Sharing My Doubts on Goals and Requirements
• 2017-02 Staying on the right path
• The goal is to solve the problem
• What is a Useful Perspective in Considering Requirements Engineering Relative to Systems Engineering?
• To Brainstorm or Not to Brainstorm
• REQM guidance matrix
• Sharing My Doubts on the Focus of Requirements
• Integrating Program Management and Systems Engineering
• Design in Tech Report
• Contributions to the Development of Personal Rapid Transit
• Information
• About IREB
• About the RE Magazine
• Contact
• Advertise with us
• How to advertise
• Advertising Rates
• Become a Sponsor
• Contribute
• Become an author
• Ways to contribute
• Give Feedback
• Home
• Meta
• Sitemap
• Imprint
• Privacy
• Conditions of Use