SESSION 3
(NOTE: Students must have completed the MS Access exercise in Chapter 11 before doing this PBL)
System Design
The following week, Encik Rashdan started to design the database. He found that the following
documents are required for the sales order processing system:
CUSTOMER REGISTRATION FORM
Customer Number:
Customer Name:
Street Address:
Postal Code:
Outstanding Balance:
@@@
Telephone (Office)
Telephone (Mobile)
City:
State:
Credit Limit:
SALES REPRESENTATIVE REGISTRATION FORM
Sales Rep. ID:
Sales Rep. Name:
IC Number:
Date Joined:
Telephone (Mobile):
Commission Rate:
PRODUCT REGISTRATION FORM
Product Code:
Product Name:
Category:
Description:
Supplier Name:
Unit Price:
Quantity on Hand:
Picture:
SALES ORDER FORM
Customer Number:
Customer Address:
Telephone:
Product Code
xxxxxxxx
xxxxxxxx
xxxxxxxx
Product Name
xxxxxxxxxxx
xxxxxxxxxxx
@@@
Sales Order Number
Date:
Sales Rep. ID:
Sales Rep. Name:
Quantity Sold
GRAND TOTAL:
Unit Price
xxxxxx
xxxxxx
xxxxxxxxx
Total (RM)
xxxxxxxxx
xxxxxxxxx
xxxxxxxxx
On top of that, Encik Rashdan was also furnished with the following additional information concerning
orders:
i.
ii.
iii.
A customer can place many orders (i.e. in different sales order form) but each sales order form
is only for single customer.
A sales representative can take many orders from customers (i.e.sales rep. can prepare many
sales order forms) but each sales order form can only be prepared by one sales representative.
An order may contain several line items (i.e. customer may order several products within a
sales order form) but each line item may only include a single product. For example, Product X
cannot appear on multiple lines within the same order.
Required:
a)
b)
c)
d)
Identify and list the entities and the attributes of those entities.
Define primary key, secondary key and concatenated key. Give an example each from the
information provided above. Identify the primary key for each of the entity.
Specify the relationship among these entities. Is there any many-to-many relationship? How do we
implement many-to-many relationship in Microsoft Access?
Draw the entity relationship diagram (ERD) depicting the relationship between these entities.
System Construction
e)
Using Microsoft Access, create a database for Sales Order Processing system. Your database should
include the followings:
i.
Tables for each entity that you have identified in your ERD plus any other appropriate
tables. You may add other attributes to suit your business or product. Since you are not
doing a complete system, data for fields marked with @@@ are not necessarily being
automatically updated every time you create sales transaction.
ii.
Forms for new customer registration, sales rep. registration, product registration and sales
order form. Use your creativity to design these forms. Remember that good paperless input
design should minimize keystrokes, so use dropdown menu, checkbox etc. where
appropriate. To minimize errors, the fields marked with XXX in the sales order form must be
auto-completed.
iii.
Queries for your products, customers and sales reps such as:
a. Specific product (user can view picture and description of the product)
b. Product by category (make, size, colour etc.)
c. Product by price range
d. Other relevant queries
iv.
Reports for your products, customers and sales reps such as:
a. Sales by product category
b. Sales by sales representative
c. List of all available products
v.
vi.
vii.
d. List of all customers
e. Other relevant reports
A main menu with buttons linking to the forms, queries and reports. You need to help the
users to navigate through the database. Create this page using form in form design.
A start page with your company logo, name of the system and two buttons (one linking to
the main menu and labelled with “ENTER” and the other for user to quit the application and
labelled with “EXIT”). Use similar steps as for creating the main menu. You must set this
page to appear when user first enters into the system.
Dummy data to test your database. You are required to create at least 10 customers, 5 sales
representatives and 20 sales transactions.
END OF PBL SESSION