Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In part #2 we'll create the library of smaller stories that make up parts of the higher level stories that are in #3. For example, look at the Story of Retail Company:

Story of Online Retail Company

There are a lot of high level steps in that story that describe general business activities. These are assembled in a way that makes sense for a retail company, but many of the individual activities are just as applicable in different parts of the high level stories for other types of organizations.

...

The idea of using stories (aka "narratives") like this is a common one. Part of the reason for writing them specifically in the way I've described here is to make them a good starting point for business process oriented use cases, that can then have system interactions added to them (making them system interaction use cases) in order to drive further UI and system design efforts. For those interested, this is based on a lot of research I've done over the years while trying to work more effectively with clients, and I'm working on a book on that topic called "HEMP: Enterprise Software Analysis and Design", HEMP stands for "Holistic Enterprise Mechanization Process". On a side note, a better word for "mechanization" is "automation", but I thought HEMP would make a more colourful and interesting title than "HEAP". (wink)

The book for the lightweight version of this process, HEMP light, is now available on http://www.dejc.com/home/HEMP.html

A Special Note on Testing

...