IFIP/ACM International Conference on Distributed systems platforms
Writing Effective Use Cases
Database Management Systems
Patterns of Enterprise Application Architecture
Patterns of Enterprise Application Architecture
Guiding Use Case Authoring: Results of an Empirical Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
Precise Specification and Validation of Transactional Business Software
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Analysis of transaction problems using the problem frames approach
Proceedings of the 2006 international workshop on Advances and applications of problem frames
An Empirical Quality Assessment of Automotive Use Cases
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Transactions Concurrency Control in Web Service Environment
ECOWS '06 Proceedings of the European Conference on Web Services
Towards a Common Semantic Foundation for Use Cases and Task Models
Electronic Notes in Theoretical Computer Science (ENTCS)
Improving the quality of use case descriptions: empirical assessment of writing guidelines
Software Quality Control
The application of use cases in systems analysis and design specification
Information and Software Technology
Specification of Transactional Requirements for Web Services using Recoverability
International Journal of Information Technology and Web Engineering
| Hi-index | 0.00 |
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.