ISY103 Database Management for Business
1.A completed copy of the AIH Assignment Coversheet.
2.An appropriate title page that includes an acknowledgement of all students you have spoken to about the assignment.
3.A table of contents and automatically generated page numbers.
4.An entity relation diagram that models the solution which includes:
a.all entities, relationships (including names) and attributes;
b.primary (underlined) and foreign (italic) keys identified;
c.cardinality and participation (optional / mandatory) symbols; and
d.assumptions you have made, e.g. how you arrived at the cardinality / participation for those not mentioned or clear in the business description, etc. The E-R should be completed using the standards of this course (crow’s feet or UML).
5.Relational data structures (shown in Standard Notation Format) that translates your E-R diagram which includes:
a.relation names;
b.attribute names;
c.primary and foreign keys identified; and
d.for each relation the level of Normalisation achieved, and for any not to Third Normal Form, explain why. The data structures should be shown using the standards of this course (crow’s feet or UML).
Answer:
ER Diagram
(CS Odessa Corp. 2016)
Relational Database
CLIENT(FCompanyName, FWebsite, FPhone, FFax, FEmail)
CLIENTCONTACTS(FContactID, FCompanyName, FFirstName, FLastName, FPhone, FFax)
CLIENTADDRESS(FAddressID, FCompanyName, FStreet, FCity, FState, FPostcode, FAddressType)
MAGAZINEISSUE(FMagazineIssueID, FPublicationName, FIssueMonthYear)
PAYMENTTYPE(FPaymentType)
STAFFTYPE(FStaffType)
STAFF(FStaffID, FStaffName, FStaffType, FAddress, FPhone, FTFN, FSalary)
STAFFEMAIL(FStaffID, FEmail)
USERS(FStaffID, FFirstName, FLastName, FLoginName, FPassword, FEmail, FLevel)
ORDER(FOrderID, FOrderDate, FONumber, FStaffID, FSpInstruction, FCopyNotes, FInvoiceDate, FCost, FPageSize, FShape, FColour, FPosition, FProdNotes, FMagazineIssueID, FCompanyName)
PAYMENT(FPaymentID, FAmount, FPaymentDate, FPaymentType, FOrderID)
CREDITCARDPAYMENT(FPaymentID, FCreditCardType, FCreditCardNumber, FCreditCardName, FCreditCardExpiryMonthYear)
CHEQUEPAYMENT(FPaymentID, FChequeNumber)
ADVERTISINGAGENCY(FAgencyBusinessName, FContactName, FStreet, FCity, FState,
FPostcode, FMobile, FBusinessPhone, FFax, FOther)
CLIENTAGENCY(FCompanyName, FAgencyBusinessName, FCommission)
SUPPLIER(FSuppCompanyName, FContactName, FTitle, FStreet, FCity, FState, FPostcode, FPhone, FWebsite, FEmail, FComment)
Assumptions
These are the assumptions that are made in the database designing-
- Types of Staff are saved into a separate table.
- Complete client detail is saved into separate tables e.g. Contacts in separate table, Emails in separate table etc.
- A client can hire an agency but it is not mandatory. Therefore the clients with agency detail are stored in separate table.
Relational Schema
Table Name |
Field |
Type |
Description |
SUPPLIER_TABLE |
FSuppCompanyName |
text(50) |
PRIMARY KEY |
|
FContactName |
text(50) |
|
|
FTitle |
text(10) |
|
|
FStreet |
text(50) |
|
|
FCity |
text(20) |
|
|
FState |
text(20) |
|
|
FPostcode |
text(5) |
|
|
FPhone |
text(20) |
|
|
FWebsite |
text(50) |
|
|
FEmail |
text(50) |
|
|
FComment |
text(50) |
|
ADVERTISINGAGENCY_TABLE |
FAgencyBusinessName |
text(50) |
PRIMARY KEY |
|
FContactName |
text(50) |
|
|
FStreet |
text(50) |
|
|
FCity |
text(20) |
|
|
FState |
text(20) |
|
|
FPostcode |
text(5) |
|
|
FMobile |
text(20) |
|
|
FBusinessPhone |
text(20) |
|
|
FFax |
text(20) |
|
|
FOther |
text(20) |
|
CLIENT_TABLE |
FCompanyName |
text(50) |
PRIMARY KEY |
|
FWebsite |
text(50) |
|
|
FPhone |
text(20) |
|
|
FFax |
text(20) |
|
|
FEmail |
text(50) |
|
CLIENTAGENCY_TABLE |
FCompanyName |
text(50) |
PRIMARY KEY; foreign key reference to Client. FCompanyName |
|
FAgencyBusinessName |
text(50) |
foreign key reference to AdvertisingAgency. FAgencyBusinessName |
|
FCommission |
Double(6,2) |
|
CLIENTCONTACTS_TABLE |
FContactID |
integer |
PRIMARY KEY |
|
FCompanyName |
|
Foreign key reference to Client.FCompanyName |
|
FFirstName |
text(50) |
|
|
FLastName |
text(50) |
|
|
FPhone |
text(20) |
|
|
FFax |
text(20) |
|
CLIENTADDRESS_TABLE |
FContactID |
integer |
PRIMARY KEY |
|
FCompanyName |
|
Foreign key reference to Client.FCompanyName |
|
FStreet |
text(50) |
|
|
FCity |
text(20) |
|
|
FState |
text(20) |
|
|
FPostcode |
text(5) |
|
|
FAddressType |
text(20) |
|
MAGAZINEISSUE_TABLE |
FMagazineIssueID |
integer |
PRIMARY KEY |
|
FPublicationName |
text(50) |
|
|
FIssueMonthYear |
text(20) |
|
PAYMENTTYPE_TABLE |
FPaymentType |
text(20) |
PRIMARY KEY |
STAFFTYPE_TABLE |
FStaffType |
text(20) |
PRIMARY KEY |
STAFF_TABLE |
FStaffID |
integer |
PRIMARY KEY |
|
FStaffName |
text(50) |
|
|
FStaffType |
text(20) |
foreign key reference to StaffType.FStaffType |
|
FAddress |
text(50) |
|
|
FPhone |
text(20) |
|
|
FTFN |
text(20) |
|
|
FSalary |
Double(6,2) |
|
STAFFEMAIL_TABLE |
FStaffID |
integer |
PRIMARY KEY; foreign key reference to Staff.FStaffID |
|
FEmail |
text(50) |
PRIMARY KEY |
USERS_TABLE
|
FStaffID |
integer |
PRIMARY KEY; foreign key reference to Staff.FStaffID |
|
FFirstName |
text(20) |
|
|
FLastName |
text(20) |
|
|
FLoginName |
text(20) |
|
|
FPassword |
text(20) |
|
|
FEmail |
text(50) |
|
|
FLevel |
text(20) |
|
ORDER_TABLE |
FOrderID |
integer |
PRIMARY KEY |
|
FOrderDate |
date |
|
|
FPONumber |
integer |
|
|
FStaffID |
integer |
foreign key reference to Staff. FStaffID |
|
FSpInstruction |
text(50) |
|
|
FCopyNotes |
text(50) |
|
|
FInvoiceDate |
date |
|
|
FCost |
Double(6,2) |
|
|
FPageSize |
text(10) |
|
|
FShape |
text(10) |
|
|
FColour |
text(20) |
|
|
FPosition |
text(20) |
|
|
FProdNotes |
text(50) |
|
|
FMagazineIssueID |
integer |
foreign key reference to MagazineIssue. FMagazineIssueID |
|
FCompanyName |
text(50) |
foreign key reference to Client. FCompanyName |
PAYMENT_TABLE |
FPaymentID |
integer |
PRIMARY KEY |
|
FAmount |
double(6,2) |
|
|
FPaymentDate |
date |
|
|
FPaymentType |
text(20) |
foreign key reference to PaymentType. FPaymentType |
|
FOrderID |
integer |
foreign key reference to Order. FOrderID |
CREDITCARDPAYMENT_TABLE |
FPaymentID |
integer |
PRIMARY KEY; foreign key reference to Payment. FPaymentID |
|
FCreditCardType |
text(20) |
|
|
FCreditCardNumber |
text(20) |
|
|
FCreditCardName |
text(20) |
|
|
FCreditCardExpiryMonthYear |
text(20) |
|
CHEQUEPAYMENT_TABLE |
FPaymentID |
integer |
PRIMARY KEY; foreign key reference to Payment. FPaymentID |
|
FChequeNumber |
text(20) |
|
(Janalta Interactive Inc. 2015)
(Refsnes Data. 2015)
(Adrienne Watt. n.d.)
Database Designing Experience/Strength
There are so many learning experiencing while database designing in this assignment as follows-
- Got knowledge about database normalization.
- Got knowledge about different data types.
- Got knowledge about database relations in between the tables.
- Got knowledge about ER Diagram representation
References
Janalta Interactive Inc. (2015). Functional Dependency [online]. Available from: https://www.techopedia.com/definition/19504/functional-dependency [Accessed 1 May 2018].
Adrienne Watt. (n.d.). Chapter 11 Functional Dependencies [online]. Available from: https://opentextbc.ca/dbdesign/chapter/chapter-11-functional-dependencies/ [Accessed: 1-Mayl-2018].
Refsnes Data. (2015). SQL Server Data Types for various DBs [online]. Available from: https://www.w3schools.com/sql/sql_datatypes.asp [Accessed: 1-May-2018]
CS Odessa Corp. (2016). Design elements – ERD (crow’s foot notation) [online]. Available from: https://www.conceptdraw.com/examples/crowfoot-notation [Accessed: 1-May-2018]
Buy ISY103 Database Management for Business Answers Online
Talk to our expert to get the help with ISY103 Database Management for Business Answers to complete your assessment on time and boost your grades now
The main aim/motive of the management assignment help services is to get connect with a greater number of students, and effectively help, and support them in getting completing their assignments the students also get find this a wonderful opportunity where they could effectively learn more about their topics, as the experts also have the best team members with them in which all the members effectively support each other to get complete their diploma assignments. They complete the assessments of the students in an appropriate manner and deliver them back to the students before the due date of the assignment so that the students could timely submit this, and can score higher marks. The experts of the assignment help services at urgenthomework.com are so much skilled, capable, talented, and experienced in their field of programming homework help writing assignments, so, for this, they can effectively write the best economics assignment help services.