UNIVERSITI TEKNOLOGI MARA

(TERENGGANU)

KAMPUS DUNGUN

(PROJECT ASSESSMENT)

AIS 220 :

PRINCIPLES OF DATABASE SYSTEMS

(MICROSOFT ACCESS)

SYSTEM ACCEPTANCE OF GOODS

REPORT BY: MUHAMMAD NUR I’ZWAN BIN ABU BAKAR

2011680232

PROGRAM/GROUP :

DIPLOMA IN ACCOUNTING INFORMATION SYSTEM (AC120 / 3C)

SESSION : JUNE - OCTOBER 2012

REPORT FOR : MISS SHAHZWEEN BINTI CHE SHALIFULLIZAM

CONTENT

COMPANY BACKGROUND 1

ACKNOWLEDGEMENT 1

PROBLEMS 2

DATABASE INITIAL STUDY 2

ENTITY RELATIONSHIP (ER) MODEL 3

BUSINESS RULES 4

DATABASE IMPLIMENTATIONS 4

DATA DICTIONARY 7

COMPANY BACKGROUND

Hyper telecommunication is the business that sell the gadget, that is handphones.

This business start from 2007. Based at Dungun Terengganu. Our business collect

the product from various supplier such as Samsung, sony ericsson, apple, nokia

and others. Our business gain profit around RM40 000 per year. As a good

company that supply this gadget to people. We provide an offer each year like 30%

discount. To achieve one of our goal that we will provide the newest product to

customer. We always make an advertisement. So, we can gain our profit to

improve our business background.

ACKNOWLEDGEMENT

A big thankful to Allah that give me a power to settle this report. Event many thing

to be settle, still focus whit this report until finish. Not forgotten to miss shahzween

binti che shahlifullizam, that give a lot of help in this course from start until at the

end of this semester. Besides that, to my friends that give ideas how to improve my

project. All in all, thank you very much to those help me in this project.

PROBLEMS

Hyper telecommunication have some problem in the receiving goods, before this

company used manual record to record the goods from the supplier. This make

many problem, such as failing old data, hard to read staff handwriting, and hard to

measure the stock balance. So, the company required to create one database system

to easier the staff record the received goods and also improve the efficiency.

Objective of this database

- To improve the data storage systems.

- To easier the staff to record the goods received.

- To reduce the cost for receive goods department.

DATABASE INITIAL STUDY

First of all, before create this database system, we analyze the company situation,

analyze about the company objective, operations and structure. Then define the

problems that need to be settle in the receive goods department. So, the

requirement for this department is some data of vendor, staff and the product. To

get complete information of the goods listed is the data that need in this database

system for hyper telecommunications.

- Vendor who supply the goods.

- About the product receive.

- Staff who receive the goods from vendor.

ENTITY RELATIONSHIP (ER) MODEL

In this database we have three entities that is vendor entity, product entity and staff

entity. All of this entity have their own attributes. The first entity is the vendor that

have two attribute (vend_id) and (vend_name). (vend_id) as a primary key for

vendor entity. In this system, we hold the data of vendor to easier employee key-in

the new value of stocks.

The second entity is the staff, also have two attributes that is (staff_is) and

(staff_name), (staff_id) as primary key. This table is to record and save the data

who receive the product from vendor. And who will be responsible with the

acceptance of goods from supplier.

The last entity in the product, primary key is (prod_model), foreign key is

(vend_id) and (staff_id). The other attribute as (prod_brand) and (prod_quantity).

This is the main entity of the system acceptance of goods. So, all data are to be

shown on this table. As shown in figure 1, tell how the relationships for each

entity.

Figure 1 : relationship of three entity in crow’s foot model.

BUSINESS RULES

This database have their own rule. The rules are explained in the figure 2 below.

figure 2 : business rule for receive department.

DATABASE IMPLEMENTATIONS

Before the database are implemented we usually make testing of the new systems.

As figure shown below are the interface of this system. Along time taken for this

implement system we always look for maintenance. This maintenance will check

and look for error or changes in system. the maintenance activities is:

- Make the correction when the database have an error.

- When the company make the changes in the business rules.

- Enhance the systems.

The interface for this system we have home, staff authorized, stocks available and

vendor. Home page, we have three command button as show on figure 3.

Figure 3: home page.

So, based on the home page. We have three command button. First we go

through the ‘view stock’ button. When the user click the button, the system

will open the total stocks available. Figure 4 are the image of the form

appear when command button view stock clicked. In this form, we have

seven command buttons, like home, new stocks, remove stocks, save,

previews record, undo and report. All the data related to the product in

stocks are recorded.

Figure 4 : form of the available stocks.

Next, the second button that have on home page is staff button. Staff button

is to show the form of staff data. Figure 5, tell about the staff form.

Figure 5 : staff authorised

for receive goods.

On this form, we have five command button overall. Home button, new staff,

remove staff, save and report. All listed name is the persons who responsibles

for receiving the goods.

And the last is vendor command button. In vendor command button we have

the list of vendor that we have. Figure 6, show all list of the vendor.

figure 6 : vendor form.

DATA DICTIONARY

Table Name Attribute Name Contents Type Required PK

Or

FK

FK

Referenc

ed Table

vendor Vend_id Vendor id Varchar Y PK

Vend_name Vendor name char Y

product Prod_brand Product brand Varchar Y

Prod_model Product model Char Y PK

Prod_quantity Product quantity Integer Y

Vend_id Vendor id Varchar FK Vendor

Staff_id Staff id Varchar FK Staff

staff Staff_id Staff id Varchar Y PK

Staff_name Staff name Char Y

Figure 7: data dictionary for this systems.