Month: March 2012
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
Entity Relationship Modeling
The video lecture discusses the concepts associated with the Requirements Stage in the process of developing a database system. Specifically with the creation of the ERD or Entity Relationship Diagram based on a business case study.
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
Better Document Management
Document management is a important part of requirements and specification management with topics like taxonomies, focusonomies among others. A “taxonomy” is a grouping mechanism. A “focusonomy” is a tagging mechanism that allows to recognize document that focus on the same topic.
Read More