ECSY505 DATABASE DESIGN & PRACTICE I

Coursework 2

Module Leader: Mr.Saman hettiarachchi

By: R.A.Thushara Kasun Ranawaka Student ID: 2010066 Group B

Coursework 2

Contents
Acknowledgment ................................................................................................................................................................. 1 Introduction ......................................................................................................................................................................... 1 What are ER diagrams? ................................................................................................................................................... 1 Q & A.................................................................................................................................................................................... 2 Identify the main entity types of SonicLive. Explain and justify the decisions you make in written section of no more than 200 words. ................................................................................................... Error! Bookmark not defined. Identify the main relationships types between entity types of SonicLive. Explain and justify the decisions you make in written section of no more than 300 words. ................................................... Error! Bookmark not defined. Determine the multiplicity constrain for each relationship type. Explain how you determine these multiplicities in a written section of no more than 300 words. .............................................................. Error! Bookmark not defined. Identify the attributes and association them with the entity or relationship types. Also identify the primary keys for all entity types. Explain and justify the decisions you make in a written section of no more than 200 words. ....................................................................................................................................... Error! Bookmark not defined. Produce a complete entity relationship diagram for SonicLive. This need to include all entity types, relationship types, multiplicity constrains, attributes and primary keys that you have previously identified. ..... Error! Bookmark not defined. Conclusion ........................................................................................................................................................................... 4 The problems I had face .................................................................................................................................................. 4 How I manage them ........................................................................................................................................................ 4 Attachments ........................................................................................................................................................................ 5 References ........................................................................................................................................................................... 5

0|Page

Coursework 2

Acknowledgment.
Thank you very much everyone who help me to deliver this program

Introduction
SonicLive is a UK company that is specialised in hiring out audio equipment to recording artists to be used for the recording, mixing and mastering of music projects such as music tracks and albums. The company is based on 12 recording studios located all over the UK, including 4 in London. SoniLive offers a real wide range of studio equipment to their customers such as analogue and digital recorders, mixing desk, audio interfaces, microphones, studio monitors, digital convertors, controllers and other miscellaneous studio accessories. I have been hired by SonicLive as a consultant to undertake a database project for the organization. My goal in this exercise is to produce a high quality conceptual data model to fulfill all the data needs of the company i.e. to conceptually represent how the key business data needs to be recorded and organize in a way that is meaningful to the company and this with a view to design a database later.

What are ER diagrams?

In software engineering, an entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs. 1|Page

Coursework 2
What logical relational data model?
Logical data models represent the abstract structure of some domain of information. They are often diagrammatic in nature and are most typically used in business processes that seek to capture things of importance to an organization and how they relate to one another. Once validated and approved, the logical data model can become the basis of a physical data model and inform the design of a database. Logical data models should be based on the structures identified in a preceding conceptual data model, since this describes the semantics of the information context, which the logical model should also reflect. Even so, since the logical data model anticipates implementation on a specific computing system, the content of the logical data model is adjusted to achieve certain efficiencies. The term 'Logical Data Model' is sometimes used as a synonym of 'Domain Model' or as an alternative to the domain model. While the two concepts are closely related, and have overlapping goals, a domain model is more focused on capturing the concepts in the problem domain rather than the structure of the data associated with that domain.

Q&A
Driver 0..1 IsAllocated 0..1 Van

Driver +licenNo{PK} +bloodGroup +transportBouns +regNo{FK} IsAllocated 0..1 0..1 Van +regNo{PK} +maxSpeed

2|Page

Coursework 2
MemberOfStaff +idNumber{pk} +name +salary

{Optional,or}

Manager +bonus

SoundEngineer +repairingFee +ranking

Driver +vanRegNo +transportBonus +maxSpeed +licenNo

StaffMember +staffID{PK} +fName +lName +salary 1

1 CanBe 0..1

CanBe

0..1 Driver +staffID{PK}{FK} +licenNo{PK} +bloodGroup +transportBouns +regNo{FK}

CanBe

0..1 Manager +staffID{PK}{FK} +bouns SoundEngineer +staffID{PK}{FK} +repairingFee

3|Page

Coursework 2
Rents Engineer +staffID{PK}{FK} +repairingFee Examine 1..* 0..* +staffID{PK}{FK} +serviceNumber{PK}{FK} +regNumber{PK}{FK} +rentStartDate +rentEndDate +fixedRentCost 0..* Uses 1 Customer +regNumber{PK} +custName +custAddress 0..1 IsGiven 1 Fixed_Equipmt +serviceNumber{PK} +serviceDate

Conclusion

The problems I had face

1) Identify the entity types 2) Identify the relationship types 3) Identify the multiplicity constrains 4) Identify the attributes 5) Identify the primary key of the related entity

How I manage them

1) I read the case study line by line several times and try to understand the exact meaning of it. Then I short note the description into my own words.
4|Page

Coursework 2
2) I browse the internet to find out more about relationship types of entity diagrams. Then I started connecting one by one. 3) I read the notes again do this part kind an easily. 4) For this I read the paragraph word by word to pick all the attributes in the case study. 5) I ask it from my friend, and he explains me how to identify or define the primary key.

Attachments

References
Entity-relationship model - Wikipedia, the free encyclopedia. 2011. Entity-relationship model - Wikipedia, the free encyclopedia. [ONLINE] Available at:http://en.wikipedia.org/wiki/Entity-relationship_model. [Accessed 04 November 2011].

Logical data model - Wikipedia, the free encyclopedia. 2011. Logical data model - Wikipedia, the free encyclopedia. [ONLINE] Available at:http://en.wikipedia.org/wiki/Logical_data_model. [Accessed 24 November 2011].

5|Page

Coursework 2
Data Modeling 101 . 2011. Data Modeling 101 . [ONLINE] Available at:http://www.agiledata.org/essays/dataModeling101.html. [Accessed 24 November 2011].

. 2011. . [ONLINE] Available at: http://jackzheng.net/teaching/cis3730/files/1.4-db-design.pdf. [Accessed 24 November 2011].

The End

6|Page