0% found this document useful (0 votes)
58 views9 pages

Logical Database Design

Download as docx, pdf, or txt
0% found this document useful (0 votes)
58 views9 pages

Logical Database Design

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 9

ISYS6198 - DATA AND INFORMATION MANAGEMENT – LA80

Business Information Technology

KELOMPOK :
1. (2301878630) MIRANDA ARDANI
2. (2301913564) MAULANA DZAKY RISWANDI
3. (2301947426) ZHARFAN NASYWA KEMAL
4. (2301911230) LEONARDUS ARIEL KEISA PURBA
5. (2301913343) AJIE PERDANA

BEKASI
14 Oktober 2020
LOGICAL DATABASE DESIGN

2.1
1. Strong Entity Type

The composition of the Staff relation is Staff ( StaffID,


StaffName, StaffPosition, StaffAddress, StaffPhone, StaffDOB).
Primary key StaffID

2. Weak Entity Type

FormMember is a weak entity type, because if the Customer entity is deleted, the FormMember
must also be deleted.
3. One to Many (1..*) binary relationship type

Post StaffID into Warehouse to model 1:* Registers relationship


Staff (StaffID, StaffName, StaffPosition, StaffAddress, StaffPhone, StaffDOB)
Primary Key StaffID
Warehouse (WarehouseID, ProductID, StaffID, WarehouseLocation)
Primary Key WarehouseID
Alternate Key WarehouseLocation
Foreign Key ProductID references Product (ProductID), StaffID references Staff
(StaffID)

4. One-to-one (1:1) binary relationship types (cont..)

Didalam one to one binary relationship types adalah mengenai penentuan parents class dan
child class, dan disini kita menentukan Transaction sebagai parents class dan Payment
sebagai child class.
Transaction : (TransactionID, CustomerID, PromoID, TransactionDate,
TransactionMethod)
Primary key : TransactionID
Payment : (PaymentID, TransactionID, StaffID, PaymentType, TotalPrice, Status)
Primary key : PaymentID

5. One-to-one (1:1) recursive relationships


Dalam kasus disini bahwa staff akan memberikan kartu member kepada customer yang
bersedia menjadi member. Dan kartu hanya memiliki idcard yang berbeda dari yang lain.
Staff : (StaffID, StaffName, StaffPosition, StaffAddress, StaffPhone, StaffBOD)
Primary key : StaffID
MemberCard : (CardID, CustomerID, CustomerName)
Member : (CustomerID, CustomerName, CustomerPhone, CustomerAddress, Password,
Point, Voucher, Stamp, Star)
Primary key : CustomerID

6. Superclass/subclass relationship types

Cashier (StaffID, StaffName, StaffPosition, StaffAddress, StaffPhone, StaffBOD)


Primary Key StaffID
Supervisor (StaffID, StaffName, StaffPosition, StaffAddress, StaffPhone, StaffBOD)
Primary Key StaffID
Courier (StaffID, StaffName, StaffPosition, StaffAddress, StaffPhone, StaffBOD)
Primary Key StaffID
Relationship yang dimiliki antara superclass Staff dengan subclass-subclassnya adalah
Mandatory, Disjoint(OR) karena nilai minimal dari multiplicity dari Staff adalah
mandatory(satu) dan masing-masing staff hanya terbagi antara Cashier, Supervisor, atau Courier.
7. Many-to-many (*:*) binary relationship types

From *:* relationship Transaction has Product, the has relationship mempunyai satu
atribut yaitu Qty. Untuk merepresentasikan relationship tersebut, dapat dibuat sebuah relasi
DetailTransaction untuk merepresentasikan relationship Has :
DetailTransaction (ProductID, TransactionID, Qty)

8. Complex relationship types

staff records products


from suppliers

Record : (StaffID(from Staff Entity), ProductID(from Product Entity), SupplierID(from


Supplier Endity), record date.
Primary Key : StaffID, ProductID
9. Multi-valued attributes

In staff entity, one staff member can handle multiple products, so we create a new relationship
called Products and post the IdStaff into the Products
2.2 Normalisasi
UNF / Unnormalized Form
IdTransaction , IdMember, IdProduct, IdSupplier, IdWarehouse, IdStaff, MemberName,
MemberPhoneNumber, MemberGender, MemberDOB, TransactionDate, PaymentType,
ProductName, ProductCategory, ProductPrice, ProductBrand, ProductStock, ExpiryDateProduct,
SupplierName, SupplierRating, SuppluerCompany, WarehouseName, WarehouseAddress,
StaffName, StaffAddress, StaffPhoneNumber, StaffBOD, StaffGender, StaffSalary,
TransactionBonus, TransactionDiscount.

1NF
IdTransaction(PK), IdMember, IdProduct, IdSupplier, IdWarehouse, IdStaff, MemberName,
MemberPhoneNumber, MemberGender, MemberDOB, TransactionDate, PaymentType,
ProductName, ProductCategory, ProductPrice, ProductBrand, ProductStock, ExpiryDateProduct,
SupplierName, SupplierRating, SuppluerCompany, WarehouseName, WarehouseAddress,
StaffName, StaffAddress, StaffPhoneNumber, StaffBOD, StaffGender, StaffSalary,
TransactionBonus, TransactionDiscount.

2NF
Transaction Header
IdTransaction(PK), IdMember, IdProduct, IdSupplier, IdWarehouse, IdStaff, MemberName,
MemberPhoneNumber, MemberGender, MemberDOB, ProductName, ProductPrice ,
SupplierName, StaffName, StaffAddress, StaffPhoneNumber, StaffBOD, StaffGender,
StaffSalary.

Detail Transaction
IdDetailTransaction(PK), TransactionBonus, TransactionDiscount, TransactionDate,
PaymentType, SupplierRating, SuppluerCompany, WarehouseName, WarehouseAddress.

3NF
Transaction Header
IdTransaction(PK), IdDetailTransaction, IdMember, IdProduct, IdSupplier, IdWarehouse,
IdStaff.
Detail Transaction
IdDetailTransaction(PK), TransactionBonus, TransactionDiscount, TransactionDate,
PaymentType, ,

Member
IdMember(PK), MemberName, MemberPhoneNumber, MemberGender, MemberDOB.

Product
IdProduct(PK), ProductName, ProductPrice ProductBrand, ProductStock, ExpiryDateProduct,
ProductBrand, ProductStock, ExpiryDateProduct

Supplier
IdSupplier(PK), SupplierName, SupplierRating, SuppluerCompany.

Warehouse
IdWarehouse(PK), WarehouseName, WarehouseAddress.

Staff
IdStaff(PK), StaffName, StaffAddress, StaffPhoneNumber, StaffBOD, StaffGender, StaffSalary.
ER Logical

You might also like