1. DESIGN AND IMPLEMENTATION DATA MODELING TOOLS Indah Puspa Sari (26407063) Advisor : Adi Wibowo, M.T. Andreas Handojo, M.MT.

2. Background

3. Problems

4. Objectives Database reverse engineering Database forward engineering

5. Scopes Database reverse engineering Database forward engineering Application development using Microsoft Visual Basic.Net 2005 Database engine : SQL Server 2005, MySQL and Oracle 10g

6. Scopes  Input :  Database, username, password and server name  Process :  Entity type : strong and weak entity  Attribute type : Simple attribute, multivalued attribute and stored attribute. Composite and derived attribute can’t be processed.  Relationship degree : unary, binary, ternary and n-ary.  Subtype / supertype relation can be processed.

7. Scopes  Process (cont’d):  Relation name is a combination of entities names that have that relation.  Attribute in the relation will be considered as entity attribute except in M-N relation  Cardinality : 1-1, 1-M, M-N  Process analysis of the participation done by looking at the table contents, if the table is empty it will be given default values.  Output : ERD using Chen notation

8. Scopes  Input : ERD using Chen notation  Process:  Entity : strong and weak entity  Attribute type : Simple attribute, multivalued attribute, stored attribute, composite attribute and derived attribute.  Relationship degree : unary, binary, ternary and n-ary.  Subtype / supertype relation can be processed.  Cardinality : 1-1, 1-M, M-N  Participation : total and partial  Normalization process is not performed  Output: SQL dump file

9. THEORY

10. Chen Notation

11. Mapping Regular Entity – Create a relation R that includes all the simple attributes of E. – Choose one of the key attributes of E as the primary key. Composite Attribute – Include all simple attribute of composite attribute into entity attribute of composite atribute Multivalued Attribute – Create a new relation that will include an attribute corresponding to the multi-valued attribute, plus the primary key attribute of the relation that has the multi-valued attribute, K.

12. Mapping – The primary key attribute of the relation is the foreign key representing the relationship between the entity and the multi- valued relation. – The primary key of R is the combination of A and K. Weak Entity – For each weak entity type W with owner entity type E, create a relation R and include all attributes of the weak entity as attributes of the new relation R. – Then, include the primary key of the owner entity as foreign key attributes of R. – The primary key of R is the combination of the primary key(s) of the owner(s) and the partial key of the weak entity type W, if any.

13. Mapping Binary relationship – 1-1 Include as foreign key in S the primary key of the other relation which is on the side of partial participation. – 1-M Include as foreign key in S the primary key of the relation which is on the 1 side of the relationship. Include any simple attributes of the relation as attributes of S. – M-N Create a new relation S and include as foreign key attributes in S the primary keys of the entities on each side of the relationship; the two primary keys will form the primary key of S. Include any simple attributes of relationship as attributes of S.

14. Mapping Ternary, n-ary relationship – Create a new relation S and include as foreign key and primary key attributes in S the primary keys of the participating entities. – Include any simple attributes of the n-ary relationship type as attributes of S. Specialization / generalization – Create a relation for the super class, including the super class attributes. – Create a relation for each subclass, which includes the primary key of the super class (which acts as the foreign key) and the attributes of the subclass specialization.

15. Database Reverse Engineering Flowchart

16. Database Forward Engineering Flowchart

17. TESTING

18. Strong entity Weak entity Key attribute Simple attribute Multivalued attribute Composite attribute Derived attribute Binary relationship Unary relationship

19. “INPUT”

20. “OUTPUT DATABASE FORWARD ENGINEERING”

21. “OUTPUT DATABASE REVERSE ENGINEERING”

22. Ternary relationship

23. “INPUT”

24. “OUTPUT DATABASE FORWARD ENGINEERING”

25. “OUTPUT DATABASE REVERSE ENGINEERING”

26. Generalization / specialization relation

27. “INPUT”

28. “OUTPUT DATABASE FORWARD ENGINEERING”

29. “OUTPUT DATABASE REVERSE ENGINEERING”

30. CONCLUSION AND SUGGESTION

31. Conclusion Database reverse engineeringDatabase forward engineering Strong entity√√ Weak entity√#√# √ Simple attribute√√ Multivalued attribute √+√+ √ Key attribute√√ Composite attributeSimple attribute of composite that can be detected √ Derived attributeDetected as simple attributeSQL Server 2005 -> computed column MySQL, Oracle 10g -> simple column

32. Conclusion(cont’d) Database reverse engineeringDatabase forward engineering Cardinality√*√*√ Participation√*√ Unary relationship√√ Binary relationship√√ Ternary relationship√√ N-ary relationship√√ Subtype / supertype√√

33. Conclusion(cont’d) # : Weak entity with 1 key attribute without any attribute will be detected as multivalued attribute in database reverse engineering. + : Multivalued attribute which is also composite attribute will be detected as weak entity in database reverse engineering. * : Cardinality and participation type can be detected correctly if the table is not empty Attribute in relation will be detected as entity attribute except in M-N relation in database reverse engineering.

34. Suggestion The number of database engine may be added, such as PostgreSQL

35. THANK YOU