GROUP ASSIGNMENT 
TECHNOLOGY PARK MALAYSIA 

CT042-3-1-IDB 

INTRODUCTION TO DATABASE

GROUP 7 

HAND OUT DATE:  

HAND IN DATE: 

WEIGHTAGE: 50% 

INSTRUCTIONS TO CANDIDATES: 
1 Submit your assignment at the administrative counter. 
2 Students are advised to underpin their answer with the use of references  
   (Cited using the Harvard Name System of Referencing). 
3 Late submissions will be awarded zero (0) unless Extenuating Circumstances
(EC) are upheld. 
4 Cases of plagiarism will be penalized. 
5 The assignment should be bound in an appropriate style (comb bound or
stapled). 
6 Where the assignment should be submitted in both hardcopy and softcopy, the
softcopy of the 
written assignment and source code (where appropriate) should be on a CD in
an envelope 
/ CD cover and attached to the hardcopy. 
7 You must obtain 50% overall to pass this module. 

AICT005-4-1 Database Systems – Workload Matrix – Part 1

Part Compon Student Student Student Student Total

ent 1Name: 2 Name: 3 Name: 4 Name:
Wong Joel Choo Jay
Joe Kit Lopez Jang Kong
Hang Jek
Thian
1 Database 10% 10% 70% 10% 100%
and
Database
Managem
ent
System
1 Business 70% 10% 10% 10% 100%
Rules &
Normaliz
ation
1 Entity 10% 70% 10% 10% 100%
Relations
hip
Diagram

*Ignore student 4 column if there are only 3 members

*Total % of contribution of all members must sum up to 100% (for each row above)

Disadvantages of filed-based system including:

-Data isolation

Data isolation determines if the changes by an operation are visible to other users or
systems because the data is stored in different files. This will make it difficult for
users to combine all the information they need together.

-Poor security

Compared to database systems, file-based systems are less secure. When the file is
stored in shared device, the data can be easily stolen or illegally accessed by peers,
which can lead to financial loss.

-Data redundancy

When using filed-based system, it can cause data redundancy, data redundancy is a
situation that happens in database when a filed has to update in multiple files. It is
unfavorable for some shops such as bookstores because details of the book stored in
different files may cause waste storage space the same data is stored in several files.

-Concurrency access

In a filed-based system, when opened a file, that file which has been opened will be
locked. That means other users are not able to access the file at the same time.
Advantages of database and DBMS

-Security

The DBMS has built-in security features such as encryption, backup, and recovery to
protect users’ data from loss or theft. For example, only authorized users can be able
to access the data. In case of any data loss, DBMS also protects the data by creating
copies of the files.

-Data integration

DBMS access to well managed the information. It enables us data handling faster and
more efficiently, thus improving the integrity and reliability of the information.

-Reduction in data redundancy

DBMS contains the feature to prevent the input of duplicate information in database.
It is to prevent errors and data inconsistencies from occurring and leading to
confusion at work. It is useful for bookstores. For example, if two same books in
different price rows, the duplicate data will be deleted.

-Better data sharing

DBMS with better shareability. This helps to improve the efficiency of the work. For
example, within a company, the DBMS can share information of clients more quickly
to different groups.

-More flexible
Compared with the filed-based system, DBMS are more flexible. The size of database
can become bigger or smaller when the storage staff required are more or lesser.
Without affecting data consistency, the DBMS can also add new tables or delete the
old ones.

Function of DBMS

-Data storage management

This is the man function of the DBMS. With this function, we are able to create a
database to upload our data and manage it. In addition, the storage function of DBMS
also provides performance tuning, it makes users easier when they need to access the
data.

-Data dictionary management

Data dictionary management is a feature of DBMS. The function of this feature is to

store the data user uploaded, allowing the user to create the tables, data constraints
and fields. By this function, users are able to define the structure of data.

-Backup and recovery management

To protect users from data theft or inadvertent deletion, DBMS has backup and
recovery management to protect the information. If users make a backup every time
they upload information, they don’t have to worry about losing their data because they
can restore it at any time and keep it safe.

-Data control

This is a feature that prevents data from being tampered with or deleted. For example,
when uploading information or files, the administrator can choose to grant read-only
access to readers. When the reader loses the right to change the file at will, the file is
in effect secured.

-Data transformation and presentation

The data transformation function provided by DBMS too. It helps programmers settle
and optimize the logic of input. DBMS will store the data in the determined data
structure. This feature more appropriately translates and presents data to different
groups of customers.

List of Business Rules

1. Publisher can provide one or many books. The relationship is one-to-many

relationship.

2. Members can place multiple orders meanwhile each order can only be placed by
one member. The relationship is one-to-many relationship.

3. Members can rate multiple books meanwhile each rate can only be given by one
member. The relationship was represented as one-to-many relationship. “Rate” is
optional to “Member”.

4. Members can review multiple books meanwhile each review can only be given by
one member. The relationship was represented as one-to-many relationship.
“Review” is optional to “Member”.
5. Members can have multiple shopping carts meanwhile each shopping cart can
only be owned by one member. The relationship was represented as one-to-many.

6. Book can be rated by multiple members, but each rate can only rate by one
member. The relationship was many-to-one.

7. Book can be review by multiple members, but each review can only review by
one member. The relationship was many-to-one.

8. Orders can be placed by multiple members; hence each order can only be placed
by one member. The relationship was many-to-one relationship.

9. Order can include multiple books; hence book can be included in multiple orders.
The relationship was many-to-many.

10. Shopping carts can be owned by multiple members while each shopping cart can
only be owned by one member. This relationship can represent as many-to-one
relationship.

11. Shopping cart only can have one order as an order only can have one shopping
cart. This relationship can represent as one-to-one relationship.

12. An order can be related to many books.

13. Address only can relate to one member.

14. A member can have zero, one, many shopping carts.

15. An order only can have one date.

16. An order only can have one ID.

17. A book only can have one ID.

18. A member only can have one ID.

19. A publisher only can have one ID.

20. A publisher only can have one address.

21. A member only can have one address.

UNF

Sales Order

E-Bookstore

Bukit Jalil

Kuala Lumpur 57000

Member ID: M01 Order ID: O01

Member Address: No 10, Jalan 13/1A Order Date: 02/01/2023

Sri Petaling

Member Name: Yee Ming Jun

Book Book Name Quantity Unit Price Total

ID (RM) (RM)
B01 Star Wars 1 40.00 40.00
B02 Hunger Game 1 50.00 50.00
 B03 Harry Potter 1 40.00 40.00

Total Amount 173.00

1NF
Mem Mem Mem Order Order Boo Book Quant Unit
ID name add ID date k name ity price
ID
M01 Yee Ming Sri O01 02/01/2 B01 Star 1 40
Jun Petaling 023 Wars

M01 Yee Ming Sri O01 02/01/2 B02 Hunger 1 50

Jun Petaling 023 Game

M01 Yee Ming Sri O01 02/01/2 B03 Harry 1 40

Jun Petaling 023 Potter

Full dependencies:

Order_ID, Book_ID -> Quantity

Partial dependencies:

Order_ID -> Mem_ID, Mem_name, Mem_add, Order_date

Book_ID -> Book_name, Unit_price

Transitive dependencies:

Mem_ID ->Mem-name, Mem_add

2NF
 Order ID Book ID Quantity

Order ID Mem ID Mem name Mem add Order date

Book ID Book Unit price

name

3NF

Order ID Book ID Quantity

Order ID Mem ID Order date

Mem ID Mem name Mem add

Book ID Book name Unit price

Entity Relationship Diagram