Capturing business transaction requirements in use case models

A significant portion of our modern economy is dependent on the reliability and usability of enterprise applications (EAs) of which business transactions and concurrency management are central concepts. The correct orchestration of subordinate system transactions forming a business transaction, as well as proper concurrency conflict resolution strategies are crucial factors. In this paper we argue that modeling business transactions and concurrency management are a domain activity and as such, are to be analyzed and documented during the requirements phase. Failing to do so can have a significant negative effect on the usability of an application. Driven by our own experiences in writing use cases for EAs, we demonstrate how business transactions can be modeled within use case specifications. Concrete examples and usage guidelines are offered as well as a demonstration of how our approach helps contribute to the difficult task of requirements elicitation.

[1]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[2]  Vasantha Banagala.  Analysis of transaction problems using the problem frames approach , 2006, IWAAPF '06.

[3]  Raghu Ramakrishnan,et al.  Database Management Systems , 1976 .

[4]  Avraham Leff,et al.  A Distributed Object Oriented Framework to Offer Transactional Support for Long Running Business Processes , 2000, Middleware.

[5]  David Budgen,et al.  The application of use cases in systems analysis and design specification , 2003, Inf. Softw. Technol..

[6]  Michael J. Butler,et al.  Precise Modelling of Compensating Business Transactions and its Application to BPEL , 2005, J. Univers. Comput. Sci..

[7]  Ferhat Khendek,et al.  Consistency between Task Models and Use Cases , 2007, EHCI/DS-VIS.

[8]  Craig Larman,et al.  Applying UML and patterns , 1997 .

[9]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[10]  Ferhat Khendek,et al.  Towards a Common Semantic Foundation for Use Cases and Task Models , 2007, FMIS@ICFEM.

[11]  Martin Fowler,et al.  Patterns of Enterprise Application Architecture , 2002 .

[12]  Peter Dolog,et al.  Transactions Concurrency Control in Web Service Environment , 2006, 2006 European Conference on Web Services (ECOWS'06).

[13]  Cláudia Maria Lima Werner,et al.  Precise specification and validation of transactional business software , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[14]  Neil A. M. Maiden,et al.  Guiding use case authoring: results of an empirical study , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[15]  Keith Phalp,et al.  Improving the quality of use case descriptions: empirical assessment of writing guidelines , 2007, Software Quality Journal.

[16]  Fredrik Törner,et al.  An Empirical Quality Assessment of Automotive Use Cases , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).