An Example of Use-Case-driven Conceptual Design of Relational Database

In this paper we present an approach to the use-case-driven conceptual design of the relational database completely based on the Unified Modeling Language (UML). We base the initial conceptual model on the standard UML business profile. In the first phase, business use cases are identified and described by macroactivity diagrams. After that, detailed business activity diagrams are designed by populating macroactivity diagrams with used business objects, object flows and worker's responsibilities. Based on detailed business activity diagrams, related business class diagrams are designed, and finally integrated into a single business class diagram that describes the static structure of the entire business system. In the last phase, that integral business class diagram is mapped into a system class diagram that represents the initial conceptual model of the target relational database. Therefore, some transformations of the initial conceptual model are proposed and illustrated. Thanks to the unified notation and integrated treatment of business modeling and database design, the proposed approach unifies and accelerates the implementation of the information system. This approach is illustrated by taking a visa issuing system as an example.

[1]  D. Brdjanin,et al.  UML-business profile-based Business Modeling in Iterative-Incremental Software Development , 2005, EUROCON 2005 - The International Conference on "Computer as a Tool".

[2]  Charles W. Bachman,et al.  The Role Concept in Data Models , 1977, VLDB.

[3]  Thomas A. Bruce,et al.  Designing Quality Databases With IDEF1X Information Models , 1991 .

[4]  C. Ellis Workflow Technology , 1999 .

[5]  Douglas Herrmann,et al.  A Taxonomy of Part-Whole Relations , 1987, Cogn. Sci..

[6]  H. A. Proper,et al.  Conceptual Schema Optimisation - Database Optimisation before sliding down the Waterfall , 2021, ArXiv.

[7]  Andreas Rausch,et al.  Structuring and refinement of class diagrams , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[8]  Ian G. MacDonald,et al.  Information Engineering , 2019, Information Systems Design Methodologies: Improving the Practice.

[9]  Yongzhen Ou,et al.  On Mapping Between UML and Entity-Relationship Model , 1997, UML Workshop.

[10]  R. Chaffin,et al.  The similarity and diversity of semantic relations , 1984, Memory & cognition.

[11]  António Rito Silva,et al.  Using roles and business objects to model and understand business processes , 2005, SAC '05.

[12]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[13]  Friedrich Steimann,et al.  On the representation of roles in object-oriented and conceptual modelling , 2000, Data Knowl. Eng..

[14]  Peretz Shoval,et al.  Entity-Relationship and Object-Oriented Data Modeling-an Experimental Comparison of Design Quality , 1997, Data Knowl. Eng..

[15]  Veda C. Storey,et al.  Understanding semantic relationships , 1993, The VLDB Journal.

[16]  Ivar Jacobson,et al.  The object advantage - business process reengineering with object technology , 1994 .

[17]  Jonás A. Montilva Calderón,et al.  BMM: A Business Modeling Method For Information Systems Development , 2018, CLEI Electron. J..

[18]  Ramez Elmasri,et al.  Fundamentals of Database Systems , 1989 .

[19]  Sven Hartmann,et al.  Higher-order entity relationship modelling with UML , 2005, Fifth International Conference on Quality Software (QSIC'05).

[20]  Friedrich Steimann,et al.  Role = Interface: A Merger of Concepts , 2001 .

[21]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .