Author: Requirements Management
Successful Feature Injection
Feature injection is a business analysis approach that focuses on business value, an approach similar to Behavior Driven Development (BDD). It transfers knowledge to the team about how the project can deliver value and what are the features needed to deliver that value. Examples are used to transfer this information to the team in the […]
Read More
User Stories Walking Exercise
In this blog post, Dhaval Panchal proposes a technique that help slicing agile user stories. He uses it for stories ‘not-done’ at the end of sprint or team that have problems to split stories horizontally across components. The idea is linked to the experience of taking your dog to a park for a walk. The […]
Read More
Templates for Software Requirements
What do you document and how much should you document? This question is often present in software development projects and even more now with Agile approaches. This article presents a template for managing software requirements and software problems. This templates have been validated within the industry in various parts of the world.
Read More
Comprehensive User Stories
A user story is a high-level requirement of a feature provided from the perspective of a stakeholder. A comprehensive user story has acceptance criteria that cover all possible functional scenarios or conditions needed to satisfy the user requirements. In development and testing terms, this means defining positive and negative scenarios. This article defines what differs […]
Read More
Representing Domain Requirements and Domain Architecture in Software Product Line
Software Product Line (SPL) core assets development is an effective approach in software reuse in which core assets can be shared among the members of the product line with an explicit treatment of variability. This article propose an approach for transitioning requirements models to architecture levels to overcome the issue of variability at the requirements […]
Read More
Visual Models for Software Requirements
Software requirements are often thought to be textual material that can take the form of free “system shall…” statements, user stories, or “give when then” of behavior driven development. This blog post explore the usage of visual models to capture software requirements. It explains that models are not requirements, but they help us find and […]
Read More