AST21401 Database and its applications / Project Specifications / P.1





AST21401 Database and its Applications
(2020/21 Sem B)

Group Project Specifications


AST21401 Database and its applications / Project Specifications / P.2
Introduction
In this project, students need to form group to handle a scenario that related to a small
wedding planning company. Each group need to analyze the requirements of the users,
propose a solution, and implement the solution with Microsoft Access database to enable the
wedding planning company to work effectively.


Objectives of the Project
By completing this project, students are expected to:
 generate an appropriate solution that make use of database for the effective running of an
organization; and
 implement database application to solve the business problems.


Grouping Instructions
This project requires students to form group with no more than 6 students. You may go solo
but project requirements will not be lessened. The suggested group size would be a group of 4
to 5 students so that loadings and efforts can be properly balanced among different members
in a group. Students can form group that across different tutorial sessions.

Students need to submit your grouping preference online in Moodle. The submission deadline
is by 30th April, 2021 23:55. Each group only needs to submit once.


Details of the Case Scenario
WeddingEasy is a wedding planning company in Hong Kong. It helps the bride and groom to
plan for their wedding. In WeddingEasy, couples are identified by the names of bride and
groom. When a pair of couple comes to WeddingEasy, a sales representative will create a
wedding plan for them. Depends on the need of the customers, the plan is unique to the
couple. The staff will also mark down the special request(s) that the couple requested to follow
up. After the staff confirmed the booking, an invoice will be sent to the customer by mail.

WeddingEasy helps the couples to arrange the wedding banquets. This includes the location,
date, time, and the number of participants. The location of the banquet can be of various
AST21401 Database and its applications / Project Specifications / P.3
types, including hotels, restaurants, public parks, etc. The location is identified by a name. Each
location has an address, maximum capacity, and minimum charges. During the banquet,
WeddingEasy may also arrange a lawyer to testify the ceremony. Different lawyers have
different prices for their services.

Before and during the banquet, couples may need photo taking services. WeddingEasy helps to
book the photographers for different events on different dates including pre-wedding and
banquet. The type of the photographer including master, snapshot, and assistant.
Photographers are identified by their names. Different photographers have different prices for
their services. For the photo taking services before the banquet, the couples can choose
locations that outside Hong Kong. If that is the case, WeddingEasy will help to book the air
tickets, hotels, and local transportations in overseas for the couples as well as the necessary
personnel including photographers, makeup stylists, and hair stylists.

If necessary, WeddingEasy can also help the couples to book the stylists for different events on
different dates including photo shooting (local and overseas) and banquet. The type of the
stylist including makeup and hair. Stylists are identified by their names. Different stylists have
different prices for their services.

As a solution provider, your group needs to analyze the data requirements of the WeddingEasy
and propose a solution for them. In addition, your group needs to implement your proposed
solution in Microsoft Access.


AST21401 Database and its applications / Project Specifications / P.4
Project Deliverables

A. Report

1. Conceptual Schema
The conceptual schema of proposed solution in terms of entity relationship (ER)
diagram. The notation used in the ER diagram should follow the Crow’s feet style that
taught in the lecture. You can include the assumptions that you made during the
analysis and drawing of ER diagram.

2. Data Normalization
The data normalization from un-normalized form (UNF) to third normal form (3NF). You
need to show the detail transformation (including the partial and transitive
dependencies) from UNF to 1NF; from first normal form (1NF) to second normal form
(2NF); and from 2NF to 3NF.

3. Data Description
A detail description for all attributes in each table that resulted in 3NF. The suggested
format as follows.

Table Name: Student

Field Name Description Data Type Size Notes
Student ID Student number of student Number 8 Primary Key
Gender Gender of student Short Text 1 “M” or “F”, Not Null


4. User Guide
A simple user guide that help users to understand how to use the database (with
sample data provided that enable user to use without error). Screen Captures of all the
Forms and Reports should be included in the report.

AST21401 Database and its applications / Project Specifications / P.5
Database

1. Data Structure & Data
Implement the tables that resulted in 3NF with all the configurations as mentioned in
A3. Each table should have at least 15 records of data. The relationship between tables
should be properly implemented in the “Relationship” of Microsoft Access.

2. Data Input Forms
Forms and sub-forms assisting user to manipulate the data. All the data should be
editable by form (not by table).

3. Data Reports
Reports that allow user to read the data. There is no limit on the maximum number of
reports but there should be at least 3 reports. The first one is for individual couples to
see their bookings. The second one is the invoice that to be sent to the customer by
mail. The last one is for manager to see the monthly sales summary.

4. Data Search Forms
The data search should be done in the format of forms. Students are required to
produce forms that allow dynamic search with different criteria. There is no limit on the
number of forms but at least there are 3 search forms. The first one is for staff to input
bride name and or groom name to search for related wedding plan. The second one is
for staff to input the date range to search for the related wedding plans. The last one is
for manager to search for the bookings done by a particular sales representative.

AST21401 Database and its applications / Project Specifications / P.6
Submission Requirements & Schedule

A. Report
Template Please use the provided report template to produce the report

Number of Pages: No restriction

Due Date: Before 30th April, 2021 23:55

Softcopy filename: AST21401-ProjGpXX.docx
(XX need to be replaced by your group number that will be
announced by teacher later)

Softcopy format: MS Word (*.doc / *.docx)

Softcopy Submission: To Moodle by Group Leader

Hardcopy Submission: Not accepted


B. Database
Due Date: Before 30th April, 2021 23:55

Softcopy filename: AST21401-ProjGpXX.accdb
(XX need to be replaced by your group number that will be
announced by teacher later)

Softcopy format: MS Access Database (*.accdb)

Softcopy Submission: To Moodle by Group Leader


Penalty
If plagiarism is found in any submissions, all the students in the related groups (including
those who give their works for others’ to copy) might subject to a fail grade in this course plus
other disciplinary actions.
The late penalty is 10% of the overall marks in this project per calendar day of late submission,
including both softcopies.

AST21401 Database and its applications / Project Specifications / P.7
Marking Rubrics
This project contributes to 20% of the marks in the whole course. In particular, the marks
distribution as follow:
Items \ Criteria % Grade A Grade B Grade C Grade D Grade F Result
(A1)
Conceptual
Schema
15
No logical
mistake in the
ERD and no
error in ERD
notations.
Most of the
entities in the
ERD and
notations are
correct.
Over half of
the entities in
the ERD and
notations are
correct.
Less than half
of the entities
in the ERD and
notations are
correct.
The ERD is
lacking of logic
and not follow
the notation at
all.

(A2)
Data
Normalization
15
The process
from UNF to
3NF are done
without error.
A few errors
found during
the process
from UNF to
3NF.
The process
from UNF to
3NF suffers
certain amount
of errors .
The process
from UNF to
3NF contains
large amount
of errors.
No sign of
normalization
at all.
(A3)
Data
Descriptions
10
Data can
completely
fulfill the users’
req. with
correct
datatype &
constraints.
A few missing
data that
cannot fulfill
the req. with
few error s in
datatype &
constraints.
Most of the
core data are
present with
datatype &
constraints for
major fields
correct.
Part of the
important data
are missing
with errors
found in
datatype &
constraints.
Core data are
missing with
large number
of errors
found in
datatype &
constraints.

(A4)
Documentation 10
A clear user
guide is
provided with
all the stated
operations can
be followed in
the database.
A user guide is
provided with
most of the
operations can
be followed in
the database.
A vague user
guide is
provided with
some of the
operations can
be followed in
the database.
A poor user
guide is
provided with
many stated
operations
cannot done in
the database.
A badly written
user guide with
most of the
operations
cannot be
followed in the
database.

(B1)
Data Structure
& Data
5
All the tables
are properly
configured in
MS Access with
more than 15
sample rows in
each table.
Relationship is
properly given
without error.
Most tables
are properly
configured in
MS Access with
more than 15
sample rows in
each table.
Relationship is
given with
minor errors.
More than half
tables are
properly
configured in
MS Access with
15 sample
rows in each.
Relationship is
given with
errors.
Less than half
tables are
properly
configured in
MS Access with
15 sample
rows in each.
Relationship is
given with
many errors.
Only a few
tables are
properly
configured in
MS Access
with not much
sample rows.
Relationship is
not present at
all.

(B2)
Data Input
Forms
10
All the tables
can be edited
by forms with
high degree of
user friendly
design
Most of the
tables can be
edited by
forms with
certain level of
user friendly
Over half of
the table can
be edited by
forms with
middle level of
user friendly
Less than half
of the table
can be edited
by forms with
low level of
user friendly
There is almost
no form to edit
the data and
no sign of user
friendly at all.

(B3)
Data Reports 15
All 3 required
reports can be
generated with
professional
style. Extra
practical
reports are
provided.
All 3 required
reports can be
generated with
acceptable
style and
without errors.
At least 2
required
reports can be
generated with
some style and
without errors.
At least 1
required
report can be
generated
without errors.
No reports can
be generated
without errors.

(B4)
Data Search
Forms
20
All 3 required
search
functions are
completed
without errors.
Extra practical
search are
provided.
All 3 required
search
functions are
completed
with minor
errors.
At least 2
required
search
functions are
completed
with errors.
At least 1
required
search function
is completed
with errors.
The search
functions are
not working at
all.















































































































































































































































































































































































































































































学霸联盟