Wednesday, June 9, 2010

Tutorial: Agile Use Cases

Instructor: Rebecca Wirfs-Brock

Rebecca is the inventor of the two column use case. She has been doing use cases since 1992. It was in a Smalltalk magazine that she published a use case with two columns. The side-by-side use case was born... no, No, NO.

Agile core values
  • Design simplicity (use case application: simple writing leads to simple coding)
  • Interpersonal communication
  • High degree of trust
  • Satisfying stakeholders
  • Constant learning
What makes a project Agile?
  • Decision making spread across project duration
  • Information when needed ... just in time (often through conversations and additional tests)
Use case
  • Functionality from a particular point of view
  • ... describes a chunk of the system
  • Can be a various levels: In the clouds (scope) and at sea level (code)
  • Agile use cases are not so detailed
Use cases describe functionality from an external perspective - an actor.
Actor = a user or another system

Use case body forms
  1. Narritive form
  2. Step-by-step form
  3. Side-by-side form (Conversational)
Agile: write just enough requirements and just enough design to implement.

User stories are a similar to use cases.

From wikipedia: "A user story is a software system requirement formulated as one or more sentences in the everyday or business language of the user. User stories are used with Agile software development methodologies for the specification of requirements (together with acceptance tests). Each user story is limited, so it fits on a small paper note card—usually a 3×5 inches card—to ensure that it does not grow too large. The user stories should be written by the customers for a software project and are their main instrument to influence the development of the software."

No comments:

Post a Comment