Data modeling and functional modeling: Examining the preferred order of using UML class diagrams and use cases

Innovations in Information Systems Modeling: Methods and Best Practices

Volumn , Issue , 2009, Pages 122-142

  Shoval, Peretz ^a   Last, Mark ^a   Yampolsky, Avihai ^a  

^a BEN GURION UNIVERSITY OF THE NEGEV   (Israel)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84900210731     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-60566-278-7.ch007     Document Type: Chapter

References (40)

1. Alabiso, B. (1988). Transformation of data flow analysis models to object-oriented design. Proceeding of OOPSLA '88 Conference, San Diego, CA, 335-353.
2. th International Conference on Software Engineering and Knowledge Engineering (SEKE '02), Ischia, Italy, 127-134.
3. Bailin, S. (1989). An object-oriented requirements specification method. Communication of the ACM, 32(5), 608-623.
4. Batra, D. (1993). A framework for studying human error behavior in conceptual database modeling. Information & Management, 24, 121-131.
5. Batra, D., Hoffer, J., & Bostrom, R. (1990). Comparing representations with the Relational and Extended Entity Relationship model. Communications of the ACM, 33, 126-139.
6. nd Edition): Wiley.
7. Coad, O., & Yourdon, E. (1991). Object-Oriented Design. Englewood Cliffs, NJ: Prentice Hall.
8. Cockburn, A. (2001). Writing Effective Use Cases. Addison-Wesley.
9. DeMarco, T. (1978). Structured Analysis and System Specifications: Yourdon Press.
10. Dobing, B., & Parsons, J. (2000). Understanding the role of use cases in UML: A review and research agenda. Journal of Database Management, 11(4), 28-36.
11. D'Souza, D., & Wills, A. (1998). Objects, Components, and Frameworks with UML: The Catalysis Approach. Addison-Wesley.
12. Hofreiter, B., Huemer, C., Liegl, P., Schuster, R., & Zapletal, M. (2006). UN/CEFACT'S modeling methodology (UMM): A UML profile for B2B e-commerce. Retrieved March, 2008, from http://dme.researchstudio.at/publications/2006/
13. Insfran, E., Pastor, O., & Wieringa, R. (2002). Requirements engineering-based conceptual modeling. Requirements Engineering, 7, 61-72.
14. Jacobson, I., Booch, G., & Rumbaugh, L. (1999). The Unified Software Development Process. Addison-Wesley.
15. Jacobson, I., Christerson, M., Jonsson, P., & Overgaard, G. (1992). Object-Oriented Software Engineering: A Use Case Driven Approach. Addison Wesley.
16. Jenkins, A. (1982). MIS Decision Variables and Decision Making Performance. Ann Arbor, MI: UMI Research Press.
17. Kim, Y., & March, S. (1995). Comparing data modeling formalisms. Communications of the ACM, 38(6), 103-115.
18. nd Edition). Prentice Hall.
19. nd Edition: Addison-Wesley.
20. Mathiassen, L., Munk-Madsen, A., Nielsen, P., & Stage, J. (2000). Object Oriented Analysis and Design. Marko Publishing, Alborg, Denmark.
21. Meyer, B. (1998). Object Oriented Software Construction. Prentice Hall.
22. nd Edition). Wiley.
23. Pastor, O., Gomez, J., Insfran, E., & Pelechano, V. (2001). The OO-Method approach for information systems modeling: From object-oriented conceptual models to automated programming. Information Systems, 26(7), 507-534.
24. Rockwell, S., & Bajaj, A. (2005). COGEVAL: Applying cognitive theories to evaluate conceptual models. In K. Siau (Ed.), Advanced Topics in Databases Research. Idea Group, Hershey, PA, 255-282.
25. Rosenberg, D., & Kendall, S. (2001). Applied Use Case-Driven Object Modeling. AddisonWesley.
26. Rubin, K., & Goldberg, A. (1992). Object Behavior Analysis. Communications of the ACM, 35(9), 48-62.
27. Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., & Lorensen, W. (1991). Object Oriented Modeling and Design. Englewood Cliffs, NJ: Prentice Hall.
28. RUP - Rational Unified Process. Retrieved March, 2008 from http://www.e-learningcenter.com/rup.htm
29. Shlaer, S., & Mellor, S. (1992). Object Lifecycles: Modeling the World in States: Prentice Hall.
30. Shneiderman, B. (1978). Improving the human factor aspects of database interactions. ACM Transactions on Database Systems, 3(4), 417-439.
31. Shoval, P., & Kabeli, J. (2001). FOOM: functionaland object-oriented analysis and design of information systems: An integrated methodology. Journal of Database Management, 12(1), 15-25.
32. Shoval, P., & Kabeli, J. (2005). Data modeling or functional analysis: which comes next? - an experimental comparison using FOOM methodology. Communications of the AIS, 16, 827-843.
33. Shoval, P., & Shiran, S. (1997). Entity-relationship and object-oriented data modeling - an experimental comparison of design quality. Data & Knowledge Engineering, 21, 297-315.
34. Siau, K., & Lee, L. (2004). Are use case and class diagrams complementary in requirements analysis? an experimental study on use case and class diagrams in UML. Requirements Engineering, 9, 229-237.
35. Sjøberg, D., Hannay, J., Hansen, O., Kampenes, V., Karahasanovi, A., Liborg, N., & Rekdal, A. (2005). A survey of controlled experiments in software engineering. IEEE Transactions on Software Engineering, 31(9), 733-753.
36. Song, I., Yano, K., Trujillo, J., & Lujan-Mora, S. (2005). A taxonomic class modeling methodology for object-oriented analysis. In K. Siau (Ed.), Advanced Topics in Database Research, 4. 216-240. Hershey: Idea Group.
37. Topi, H., & Ramesh, V. (2002). Human factors research on data modeling: a review of prior research, an extended framework and future research directions. Journal of Database Management, 13(2), 188-217.
38. Wand, Y., & Weber, R. (1995). On the deep structure of information systems. Journal of Information Systems, 5, 203-223.
39. Weber, R. (2003). Conceptual modeling and ontology: possibilities and pitfalls. Journal of Database management, 14(3), 1-20.
40. Yourdon, E. (1989). Modern Structured Analysis: Prentice Hall.