Unified modeling language (UML) topics: The past, the problems, and the prospects

Journal of Database Management

Volumn 19, Issue 1, 2008, Pages

  Batra, Dinesh ^a  

^a FLORIDA INTERNATIONAL UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 50549084311     PISSN: 10638016     EISSN: 15338010     Source Type: Journal    
DOI: None     Document Type: Editorial

References (48)

1. Agarwal, R. & Sinha, A. P. (2003). Object-oriented modeling with UML: A study of developers' perceptions. Communications of the ACM, 46(9), 248-256.
2. Ambler, S.W. (2004). The object primer: Agile model-driven development UML 2.0 (3rd ed.). Cambridge, UK: Cambridge University Press.
3. Barra, D. & Satzinger, J. W. (2006). Contemporary approaches and techniques for the systems analyst. Journal of Information Systems Education, 17, 257-266.
4. Bell, A. E. (2004). Death by UML fever. Queue, 2, 72-80.
5. Cant, S. N., Jeffery, D. R., & Henderson-Sellers, B. (1995).A conceptual model of cognitive complexity of elements of the programming process. Information and Software Technology, 37(7), 351.
6. Card, S. K., Moran, T. P., & Newell, A. (1983). The psychology of human-computer interaction. Hillsdale, NJ: Lawrence Erlbaum Associates.
7. Conallen, J. (1999). Modeling web application architectures with UML. Communications of the ACM, 42(10), 63-70.
8. Dahanayake, A., Sol, H., & Stojanovic, Z. (2003). Methodology evaluation framework for component-based system development. Journal of Database Management, 14(l), 1-26.
9. Davis, F.D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319-340.
10. Dobing, B., & Parsons, J. (2002). The role of use cases in the UML: A review and research agenda. In K. Siau (Ed.), Advanced topics in database research (pp. 367-382). Hershey, PA: IGI Publishing.
11. Dobing, B., & Parsons, J. (2008). Dimensions of UML diagram use: A survey of practitioners. Journal of Database Management, 19(l), 1-18.
12. Dori, D. (2001). Object-Process Methodology applied to modeling credit card transactions. Journal of Database Management, 12(l), 4-14.
13. Dori, D. (2002). Why significant UML change is unlikely. Communications of the ACM, 45(11), 82-85.
14. Evermann, J., & Wand, Y. (2006). Ontological modeling rules for UML:An empirical assessment. Journal of Computer Information Systems, 47(l).
15. George, J.F., Batra, D., Valacich, J.S., & Hoffer, J.A. (2007). Object-oriented systems analysis and design (2nd Ed.). Upper Saddle River, NJ: Prentice Hall.
16. Halpin, T. (2001). Supplementing UML with concepts from ORM. In K. Siau & T. Halpin (Eds.), Unified modeling language: Systems analysis, design and development issues (pp. 61-74). Hershey, PA: Idea Group Publishing.
17. Halpin, T. (2002). Information analysis in UML and ORM: A comparison. In K. Siau (Ed.), Advanced topics in database research (pp. 307-323). Hershey, PA: Idea Group Publishing.
18. Hesse, W. (2001). RUP:A process model for working with UML. In K. Siau & T. Halpin (Eds.), Unified modeling language: Systems analysis, design and development issues (pp. 61-74). Hershey, PA: Idea Group Publishing.
19. Kleppe, A.G., Warmer, J.B., & Bast, W. (2003). MDA explained - the model driven architecture: Practice and promise. Boston, MA: Addison-Wesley.
20. Kobryn, C. (1999). UML 2001: A standardization odyssey. Communications of the ACM, 42(10), 29-37.
21. Kobryn, C. (2002). Will UML 2.0 be agile or awkward? Communications of the ACM, 45(l), 107-110.
22. Kobryn, C. (2004). UML 3.0 and the future of modeling. Software & Systems Modeling, 3(1), 4-8.
23. Kruchten, P. (2003). The rational unfied process: An introduction (3rd ed.). Boston, MA: Addison-Wesley Professional.
24. Loucopoulos, P., & Kadir, W. (2008). BROOD: Business rules-driven object oriented design. Journal of Database Management, 19(1), 41-73.
25. Miller, J. (2002). What UML should be. Communications of the ACM, 45(11), 67-69.
26. OMG. (2005). Introduction to OMG's unified modeling language (UML). Retrieved August 2007.
27. Peleg, M., & Dori, D. (2000). The model multiplicity problem: Experimenting with real-time specification methods. IEEE Transactions of Software Engineering, 26(8), 742-759.
28. Pender, T. (2003). UML bible. Indianapolis, IN: Wiley Publishing.
29. Price, R., Trfona, N., & Jensen, C.S. (2002). Extending UML for space- and time-dependent applications. In K.Siau (Ed.), Advanced topics in database research (pp. 342-366). Hershey, PA: Idea Group Publishing.
30. Reeves, W.W. (1999). Learner-centered design: A cognitive view of managing complexity in product, information, and environmental design. Thousand Oaks, CA: Sage Publications.
31. Reinhartz-Berger, I., & Sturm, A. (2008). Enhancing UML models: A domain analysis approach. Journal of Database Management, 19(1), 74-94.
32. Rosenberg, D., & Scott, K. (2001). Applying use case driven ohject modeling with UML: An anotated e-commerce example. Addison-Wesley, Boston.
33. Rossi, M., & Brinkkemper, S. (1996). Complexity metrics for systems development methods and techniques. Information Systems, 21(2), 209-227.
34. Rosson, M.B., & Alpert, S. R. (1990). The cognitive consequences of object-oriented design. Human-Computer Interaction, 5(4), 345-379.
35. Selic, B., Ramackers, G., & Kobryn, C. (2002). Evolution, not revolution. Communications of the ACM, 45(11), 70-72.
36. Selonen, P., Koskimies, K., & Sakkinen, M. (2003). Transformations between UML diagrams. Journal of Database Management, 14(3), 37-55.
37. Shoval, P., & Kabelli, J. FOOM: Functional- and object-oriented analysis & design of information systems: An integrated methodology. Journal of Database Management, 12(1), 15-25.
38. Siau, K., & Cao, Q. (2001). Unified modeling language (UML) - A complexity analysis. Journal of Database Management, 12(1), 26-34.
39. Siau, K., Erickson, J., & Lee, L. Y. (2005). Theoretical vs. practical complexity: The case of UML. Journal of Database Management, 16(3), 40-57.
40. Siau, K., & Loo, P.-P. (2006). Identifying difficulties in learning UML. Information Systems Management, 32(3), 43-51.
41. Siau, K., & Tian, Y. (2001). The complexity of unified modeling language: A GOMS analysis. In the Proceedings of International Conference on Information Systems, New Orleans, LA.
42. Sin, T., & Batra, D. (2007, May 12-13). Improving usability of analysis sequence diagram in transaction-oriented applications. Symposium on Systems Analysis and Design. Tulsa, Oklahoma.
43. Smolander, K., & Rossi, M. (2008). Conflicts, compromises, and political decisions - Methodological challenges of enterprise-wide e-business architecture creation. Journal of Database Management, 19(1), 19-40.
44. Soloway, E., & Pryor, A. (1996). The next generation in human-computer interaction. Communications of the ACM, 39(4), 16-18.
45. Tilley, S., & Huang, S. (2003). A qualitative assessment of the efficacy of UML diagrams as a form of graphical documentation in aiding program understanding. Paper presented at the 21st Annual International Conference on Documentation. San Francisco, CA.
46. Trujillo, J., Lujan-Mora, S., & Song, I. (2004). Applying UML and XML for designing and interchanging information for data warehouses and OLAP warehouses. Journal of Database Management, 15(1), 41-72.
47. Warmer, J., & Kleppe, A. (2003). The object constraint language: Getting your models ready for MDA. The Addison-Wesley Object Technology Series. Addison-Wesley, 2nd edition, August 2003.
48. Zendler, A., Pfeiffer, T., Eicks, M., & Lehner, F. (2001). Experimental comparison of coarse-grained concepts in UML, OML, and TOS. Journal of Systems and Software, 57(1), 21-30.