Usability of Analysis Sequence Diagram

The Unified Modeling Language (UML) has become a widely-accepted modeling language for object-oriented software development since it became the industry standard in 1997. Although researchers and practitioners have extensively studied various aspects of UML in the last couple of years, they have not yet explored the usability of the analysis sequence diagram. Drawing analysis sequence diagrams is often found to be very challenging for students in systems analysis and design classes even though basic guidelines are provided in popular textbooks. Given the important role of analysis sequence diagrams in object-oriented systems analysis and design, there is the need for an effective sequence diagram modeling technique that can facilitate novices in developing these diagrams. This paper presents a research framework which is developed based on difficulties students encounter in drawing sequence diagrams, identified in the qualitative exploratory study conducted in an undergraduate systems analysis and design class. The proposed framework will enable the design of a modeling technique and laboratory experiments to evaluate the efficacy of the new technique.

[1]  Dinesh Batra,et al.  A conceptual database design approach based on rules and heuristics , 1994 .

[2]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[3]  Wayne W. Reeves.  Learner-centered design : a cognitive view of managing complexity in product, information, and environmental design , 1999 .

[4]  John W. Satzinger,et al.  Contemporary Approaches and Techniques for the Systems Analyst , 2006, J. Inf. Syst. Educ..

[5]  Keng Siau,et al.  Theoretical vs. Practical Complexity: The Case of UML , 2005, J. Database Manag..

[6]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[7]  Venkataraman Ramesh,et al.  Human Factors Research on Data Modeling: A Review of Prior Research, An Extended Framework and Future Research Directions , 2002, J. Database Manag..

[8]  Narasimha Bolloju,et al.  Assisting novice analysts in developing quality conceptual models with UML , 2006, CACM.

[9]  Alex E. Bell.  Death by UML Fever , 2004, ACM Queue.

[10]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[11]  Colette Rolland,et al.  Guiding the Construction of Textual Use Case Specifications , 1998, Data Knowl. Eng..

[12]  Noushin Ashrafi,et al.  Object-oriented systems analysis and design , 2008 .

[13]  Bonnie Kaplan,et al.  Combining Qualitative and Quantitative Methods in Information Systems Research: A Case Study , 1988, MIS Q..

[14]  Julio Cesar Sampaio do Prado Leite,et al.  A Scenario Construction Process , 2000, Requirements Engineering.

[15]  Matthias Jarke,et al.  Scenario Management: An Interdisciplinary Approach , 1998, Requirements Engineering.

[16]  Robert P. Bostrom,et al.  Comparing representations with relational and EER models , 1990, Commun. ACM.

[17]  Ritu Agarwal,et al.  Object-oriented modeling with UML: a study of developers' perceptions , 2003, CACM.

[18]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

[19]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[20]  Joseph A. Maxwell,et al.  Qualitative Research Design: An Interactive Approach , 1996 .

[21]  Liisa von Hellens,et al.  Qualitative Research in Information Systems , 2007, Australas. J. Inf. Syst..