Analysis of transaction problems using the problem frames approach

A large number of analysis methods are used to analyse and document software problems. Among these, Michael Jackson's problem frames is an approach to identifying and describing recurring software problems. Data and business transactions are a recurrent software problem pattern in business and commerce systems. This paper demonstrates that problem frames can effectively capture and describe transactional problems. An extended version of the workpiece frame is proposed for this purpose. We found that problem frames can accommodate the critical transactional properties on diagrams and identify the difficulties associated with solving it.

[1]  George Coulouris,et al.  Distributed systems - concepts and design , 1988 .

[2]  Keith Phalp,et al.  B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process , 2006, Inf. Softw. Technol..

[3]  P. Radha Krishna,et al.  An E-check Framework for Electronic Payment Systems in the Web Based Environment , 2001, EC-Web.

[4]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[5]  David William Brown.  An introduction to object-oriented analysis : objects and UML in plain English , 2002 .

[6]  Andreas Reuter,et al.  Transaction Processing: Concepts and Techniques , 1992 .

[7]  Kendall Scott,et al.  Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example , 2001 .

[8]  Andrew S. Tanenbaum,et al.  Distributed systems: Principles and Paradigms , 2001 .

[9]  Matt Stephens,et al.  Use Case Driven Object Modeling with UMLTheory and Practice , 2008 .

[10]  Keith Phalp,et al.  Requirements engineering for e-business advantage , 2005, Requirements Engineering.

[11]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[12]  Keith Phalp,et al.  Deriving requirements from process models via the problem frames approach , 2005, Inf. Softw. Technol..

[13]  L'ubor Sesera,et al.  Analysis Patterns , 2000, SOFSEM.

[14]  Andrew Haigh.  Object-Oriented Analysis and Design , 2001 .

[15]  Bashar Nuseibeh,et al.  Relating software requirements and architectures using problem frames , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[16]  Stephen J. Mellor,et al.  Object lifecycles: modeling the world in states , 1992 .

[17]  Karl Cox,et al.  The Simulator; Another, Elementary Problem Frame? , 2003 .

[18]  Ian K. Bray,et al.  An Introduction to Requirements Engineering , 2002 .

[19]  Karl Cox,et al.  Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams , 2006, J. Syst. Softw..

[20]  Sasan Rahmatian.  Transaction Processing Systems , 2002, Encyclopedia of Information Systems.

[21]  George Coulouris,et al.  Distributed systems (3rd ed.): concepts and design , 2000 .

[22]  Philip A. Bernstein,et al.  Principles of transaction processing: for the systems professional , 1996 .