Applying learner-centered design principles to UML sequence diagrams

Journal of Database Management

Volumn 20, Issue 1, 2009, Pages 25-47

  VanderMeer, Debra ^a   Dutta, Kaushik ^a  

^a FLORIDA INTERNATIONAL UNIVERSITY   (United States)

Author keywords

Cognitive complexity; Learner centered design; Sequence diagrams; Systems analysis and design, Unified modeling language (UML)

Indexed keywords

COGNITIVE SYSTEMS; GRAPHIC METHODS; LEARNING SYSTEMS; MODELING LANGUAGES; SYSTEMS ANALYSIS;

COGNITIVE COMPLEXITY; LEARNER CENTERED DESIGN; PROCESS OF LEARNING; SEQUENCE DIAGRAMS; SYSTEMS ANALYSIS AND DESIGN; UML SEQUENCE DIAGRAMS;

UNIFIED MODELING LANGUAGE;

EID: 59849101411     PISSN: 10638016     EISSN: 15338010     Source Type: Journal    
DOI: 10.4018/jdm.2009010102     Document Type: Article

References (32)

1. Agarwal, R., & Sinha, A. (2003). Object-oriented modeling with UML: A study of developers' perceptions. Communications of the ACM, 49(9), 248-256.
2. Beck, K., & Cunningham, W. (1989). A laboratory for teaching object oriented thinking. Proceedings of the 1989 ACM OOPSLA Conference on Object-Oriented Programming, (pp. 1-6).
3. Blaha, M., & Rumbaugh, J. (2005). Object-oriented modeling and design with UML, Second Edition. Pearson Prentice Hall.
4. Bolloju, N., & Leung, F. S. (2006). Assisting the novice analyst in developing quality conceptual models with UML. Communications of the ACM, 49(7), 108-112.
5. Booch, G. (1986). Object-oriented development. IEEE Transactions on Software Engineering, 12(2), 211-221.
6. Brewer, J., & Lorenz, L. (2003). Using UML and agile development methodologies to teach object-oriented analysis and design tools and techniques. Proceedings of the 4th Conference on Information Technology Education, (pp. 54-57).
7. Burton, P., & Bruhn, R. (2004). Using UML to facilitate the teaching of object-oriented systems analysis and design. Journal of Computing Sciences in Colleges, 19(3), 278-290.
8. Dobing, B., & Parsons, J. (2006). How UML is used. Communications of the ACM, 49(5), 109-113.
9. Dobing, B., & Parsons, J. (2008). Dimensions of UML diagram use: A survey of practitioners. Journal of Database Management, 19(1), 1-18.
10. Dori, D. (2002). Why significant UML change is unlikely. Communications of the ACM, 45(11), 82-85.
11. Fowler, M. (1997). Analysis patterns: Reusable object models. Addison-Wesley Pearson Education.
12. Fowler, M. (2004). UML distilled third edition: A brief guide to the standard object modeling language. Addison-Wesley Pearson Education.
13. France, R., Kim, D.-K., Ghosh, S., & Song, E. (2004). A UML-based Pattern Specification Technique. IEEE Transactions on Software Engineering, 30(3), 193-206.
14. George, J. F., Batra, D., Valacich, J. S., & Hoffer, J. A. (2006). Object-oriented systems analysis and design, second edition. Prentice Hall.
15. International Organization for Standardization. (2005, April). ISO/ IEC 19501:2004 - Unified Modeling Language (UML). Retrieved from http://www.iso.org.
16. Johnson, R. E., & Fotte, B. (1988). Designing reusable classes. Journal of Object-Oriented Programming, 1(2), 22-35.
17. Lindland, O., Sindre, G., & Solvberg, A. (1994). Understanding quality in conceptual modeling. IEEE Software, 11(2), 42-49.
18. Micallef, J. (1988). Encapsulation, reusability, and extensibility in object-oriented programming languages. Journal of Object-Oriented Programming, 1(1), 12-36.
19. Miller, G. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. The Psychological Review, 63(2), 209-227.
20. Reeves, W. (1999). Learner-centered design: A cognitive view of managing complexity in product, information, and envirommental design. Sage Publications.
21. Rosson, M. B., & Alpert, S. R. (1990). The cognitive consequences of object-oriented design. Human-Computer Interaction, 5(4), 345-379.
22. Rumbaugh, J., Blaha, M., Premerlani, W., & Lorensen, W. (1991). Object-oriented modeling and design. Englewood Cliffs, NJ: Prentice Hall.
23. Sheetz, S. (2002). Identifying the difficulties of object-oriented development. Journal of Systems and Software, 64(1), 23-36.
24. Siau, K., & Cao, Q. (2001). Unified Modeling Language (UML) - A complextiy analysis. Journal of Database Management, 12(1), 26-34.
25. Siau, K., & Loo, P.-P. (2006). Identifying difficulties in learning UML. Information Systems Management, 23(3), 43-51.
26. Siau, K., Erickson, J., & Lee, L. (2005). Theoretical vs. practical complexity: The case of UML. Journal of Database Management, 16(3), 40-57.
27. Stumpf, R., & Teague, L. (2005). Object-oriented systems analysis and design with UML. Pearson Prentice Hall.
28. Tabrizi, M., Collins, C., Ozan, E., & Li, K. (2004). Implementation of object-orientation using UML in entry level software development courses. Proceedings of the 5th Conference on Information Technology Education, (pp. 128-131).
29. Visual Paradigm International. (2006). Retrieved from Visual Paradigm for UML: http://www.visual-paradigm.com
30. Wei, F., Moritz, S., Parvez, S., & Blank, G. (2005). A student model for object-oriented design and programming. Journal of Computing Sciences in Colleges, 20(5), 260-273.
31. Wiedenbeck, S., Fix, V., & Scholtz, J. (1993). Characteristics of the mental representations of novice and expert programmers: An empirical study. International Journal of Man-Machine Studies, 39(5), 793-812.
32. Wiedenbeck, S., Ramalingam, V., Sarasamma, S., & Corritore, C. (1999). A comparison of the comprehension of object-oriented and procedural programs by novice programmers. Interacting with Computers, 11(3), 255-282.