Year: 2012
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
Complementing User Stories
User stories are well established in agile software development processes, but they should not be seen as detailed requirements specifications. It is accepted that the end users do not know all the requirements at once. Therefore, user stories only give hints about the expectations of an end user. A computer supported strategy is proposed to […]
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
How to Split User Stories
George Dinwiddie proposes a list of material that should help you in the task of splitting user stories used to manage requirements in Agile approaches. In his own handout, he explains the difference between stories in the backlog that are often called features or epics and stories selected for development that should generally be small […]
Read More
Managing Agile Requirements
People often believe that Agile software development requires not documentation. Even if the Agile Manifesto values “Working Software over Comprehensive Documentation”, you should note the word “over” in this statement. The Manifesto is not recommending no documentation, but stating a preference for working software over documentation.
Read More