Articles
Collaborative Requirements Definition
There are different popular models for collaborative software requirements definition. In this article, Gojko Adzic, the author of Specification by Example, discusses some of them. Big specification workshops, like Product Backlog Refinement (PBR) workshops, with the entire team allows building a shared understanding and produce a set of examples that illustrate a feature. Smaller workshops […]
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
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
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
User Stories Acceptance Criteria
In Scrum user stories are the starting point of a conversation. This articles discusses the challenge for the Product Owner to provide acceptance criteria to help the Scrum team understand user stories. The author explains that acceptance criteria need not constitute an exhaustive list, but they should be sufficient to move forward. Acceptance criteria are […]
Read More