Abstract

Functional requirements and the involved user interaction are dependent on the chosen concurrency management strategy of the encompassing business transaction. Use cases are the specification technique of choice for functional requirements documentation. Unfortunately, the current state of the art in use case writing does not provide a proper means to express business transaction specifications. In order to overcome this shortcoming we adapt the use case notation to allow business transactions to be defined in terms of its boundaries, affected resources and the chosen concurrency management strategy. The practicality of our extension is illustrated by a comprehensive case study. Lessons learnt from the case study are presented in the form of a set of heuristics and practical guidelines.