Year: 2012
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
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
Using Use Cases or User Stories in Scrum
This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. […]
Read More
An Agile Method for Model-Driven Requirements Engineering
This article provides a methodological approach that focuses on requirements engineering within the Model-Driven Development (MDD) context. Our approach is an OpenUP extension in which the requirements discipline is placed in the model-driven context. We believe that the integration of requirements engineering and MDD into one consistent process will provide practitioners with the benefits of […]
Read More
User Stories Key Dimensions
This article discusses the three dimensions of user stories: the backlog order, the complexity (or effort) and the business value. These dimensions are flexible until the sprint commitment, but right before it, you should have estimated the complexity and the business value for the top of the product backlog, which means that the product backlog […]
Read More