Difference between revisions of "ORM"

From Pearl Language
Jump to navigation Jump to search
(Agile Modelling)
(Writing User Stories)
Line 21: Line 21:
*http://www.agilemodeling.com/artifacts/ormDiagram.htm
*http://www.agilemodeling.com/artifacts/ormDiagram.htm
*http://www.flexiblesoftwaresolutions.co.uk/content/capturing-software-requirements-user-stories-user-interface-and-entities-agile-approach
*http://www.flexiblesoftwaresolutions.co.uk/content/capturing-software-requirements-user-stories-user-interface-and-entities-agile-approach
==User Stories==
User Story
*must comply with zero or more business rules
*list [[must comply with::business rule]]
*ask business rules to show synopsis in US (a bit like in Logo?)
Business Rule or Policy
*is implemented by one or more User Stories
*ask compliant user stories to list their title
===Writing User Stories===
#Define Product Vision
#Define and describe Roles
#Write scenarios for roles (a day in the life of, ''kruip in de huid van'')
#Highlight all nouns (== entities or objects in ORM) and verbs (actions users perform on objects).
#Distill user stories, each user story has one or more objects and at least one verb. Stories with two objects denote relationships.

Revision as of 14:22, 17 March 2012

Sources

Terry Halpin is very active on the topic of ORM and NIAM.

Agile Modelling

User Stories

User Story

  • must comply with zero or more business rules
  • list business rule
  • ask business rules to show synopsis in US (a bit like in Logo?)

Business Rule or Policy

  • is implemented by one or more User Stories
  • ask compliant user stories to list their title

Writing User Stories

  1. Define Product Vision
  2. Define and describe Roles
  3. Write scenarios for roles (a day in the life of, kruip in de huid van)
  4. Highlight all nouns (== entities or objects in ORM) and verbs (actions users perform on objects).
  5. Distill user stories, each user story has one or more objects and at least one verb. Stories with two objects denote relationships.