INFO6002: Database数据库详说

Posted 2021-09-04 0zcm01ql

Page 1 of 5
INFO6002: Database Management 2
Trimester 2, 2021 – Callaghan & Online
Assignment 1 – Requirements Analysis & Conceptual Design
Due: 10pm, Friday 4
th June 2021
WORTH 15% of final course mark.
This is an INDIVIDUAL Assignment.
Assignment Background
You are asked to develop a conceptual database design using Enhanced Entity Relationship
modelling for a database for Office Wizard.
Tasty’n’Yummy Pizzas is a pizza outlet at Charlestown. After years of managing the records
manually, Tasty’n’Yummy Pizzas has decided to computerise its records. You are tasked to
design the conceptual database design for Tasty’n’Yummy Pizzas’ database. The initial
business requirements are provided in this document and you can get further clarification by
inquiring from the client.
Your lecturer will act as your client, whom you can query for any further information and
clarifications. This can be done via the Blackboard Discussion Forum detailed below.
Business Requirements
Order Processing
Tasty’n’Yummy Pizzas takes orders via phone, online (via an app and website) as well as
through walk-in customers. Tasty’n’Yummy Pizzas provide both delivery and pickup services.
When a customer orders via the phone, the customer’s phone number is entered to the system
along with the id of the employee taking the order. If the customer has previously ordered by
phone, the name and address appears on the screen. The customer is then asked for his name
and address and then takes the order. If the customer has not ordered before or if the name
and address given does not correspond with that in the computer, a new customer record is
created and the order is taken. For a walk-in customer, the customer’s name is recorded to
identify the order. If the customer is using the app or website, the customer can login using
his/her email or phone number and password. Alternatively, the customer can order as a guest.
Page 2 of 5
Each order contains date and time of order, one or more items, quantity of each item, price of
each item, subtotal, discount amount (if any), discount or promotion code (if any), tax, total
amount due, payment method, status, type (phone/walk-in/online) and description. If the
payment is via card, a payment approval number is recorded. If the order is a delivery order,
the driver who delivered the order is recorded. It is possible to pre-order for the order to be
fulfilled at a later date/time.
Menu Items, Ingredients and Suppliers
Each item in the menu has an item code (unique), name, size, a current selling price and
category (traditional pizzas, value pizzas, etc.). An item in the menu can be made up of a
number of ingredients. The ingredients and quantities used for the item are recorded in the
database.
Each ingredient has a code (unique), name, type, description, stock level at stock take, date
last stock take was taken, suggested current stock level, reorder level and a list of suppliers
who supply the ingredients. A supplier can supply many ingredients.
A stock take is taken each week, where the actual levels of ingredients in store are recorded.
This is then compared with suggested levels (based on orders for the week). This report is used
by the store manager to order ingredients for the following week. Information about supplier
orders needs to be maintained in the database.
Discounts and Promotions
There are different types of discount programs offered by Tasty’n’Yummy Pizzas. All discount
programs are recorded in the database. A discount program has a discount code, description,
start date of discount program, end date of discount program, requirements for discount,
discount percentage (e.g. 5%), a description and a category of menu items the discount is
applied.
A promotion is when a number of menu items categories are grouped together at a fixed price.
For example, 2 traditional large pizzas and a large drink for $19.99/- pickup. A promotion has
a promotion code, description, start date and end date of promotion and a price, quantity of
categories of items and a delivery method (store-pickup or delivery).
Employees
Employees who work at Tasty’n’Yummy are paid an hourly rate. Drivers get an extra service
fee added to their pay for each delivery. For each employee, there is an employee number,
firstname, lastname, postal address, contact number, tax file number, bank details (bank code,
bank name, account number), a payment rate, status, and a description. Drivers also have a
driver’s license number. Hours are not regular and a record is kept for each time an employee
works – a shift (start date, start time, end date, end time). The orders a driver delivers during a
shift is kept on record.
Employee are paid bi-weekly for all the shifts for the 2 week period to the employee’s bank
account at the end of each pay period. Payslips for each employee are maintained in the
database.
Reference: Requirements modified from case study at
http://programmingou2k9.blogs...
Page 3 of 5
In addition to the above information, you may wish to ask additional question of your client to
further understand the business requirements. This can be done using Blackboard / Discussion
Forums / Assignment 1: Interview your client. Your lecturer will act as the client and answer any
questions that you post.
Assignment Requirements
Part 1: Requirements Document (2 marks)
The requirements document must capture all requirements that lead to your conceptual
database design. Your requirements document will include:
• Data Requirements – outlining the major data items
• Transaction Requirements – outlining the data manipulation and queries
• Business Rules
Note: Sample requirements documents are available in Appendices A and B of your main text
(Databases Systems – A Practical Approach to Design, Implementation, and Management –
6
th Edition by Connolly and Begg 2015). Additionally a sample is available at Blackboard /
Assignment 1 / Assignment 1 Sample Requirements
Part 2A&B: Documented EER Model (13 marks)
The documented EER model includes:
• Part 2A: EER model. The EER Model must be shown in UML notation. It is preferable to
use Visio to document your model, however other applications are acceptable so long as
they are in UML format and can depict all aspects of the model.
• Part 2B Data Dictionary. The Data Dictionary describes the entities, relationships and
attributes of your EER Model. The sample format for documenting the Data Dictionary is
provided below.
Entities
Entity Name Description
Item Resources made available to staff and students
Staff An employee of the library
Relationships
Entity
name
Multiplicity Relationship Multiplicity Entity name Description
Item 1.. CategorisedTo 1.. ItemType An item is categorised to
many different item types
Staff 0..1 Delivers 0..* Order An order is delivered by a
single staff member
Page 4 of 5
Attributes
Entity Attributes Attribute
Description
Data
Type &
Length
Nulls Multivalued
Derived Default
Book bookId Uniquely
identifies a
copy of a
book
char (10) N N N
title the name of
the book
char (30) N N N
Note: Sample Data Dictionary formats are available in Chapter 16 of your main text (Databases
Systems – A Practical Approach to Design, Implementation, and Management – 6
th Edition by
Connolly and Begg 2015). Additionally, a sample is available at Blackboard / Assignment 1 /
Assignment 1 Data Dictionary
Submission Requirements
All of these components are due by 10pm, Friday 4
th June, 2021
Component Submission Method
Part 1: Requirements
Document
Submit to Turnitin using the following link:
Assessments / ASSIGNMENT1 / Assignment 1 Part 1
Requirements Submission
Submit your MS Word or PDF format document containing the
Requirements. This document will include sections for Data
Requirements, Transaction Requirements & Business Rules.
This should NOT be put into .zip file
Part 2A&B:
Documented EER
Model
Submit to Blackboard using the following link:
Assessments / ASSIGNMENT 1 / Assignment 1 Part 2
Documented EER Model Submission
Submit a .zip file containing:

• Your EER model in Visio format, or PDF format

• Your Data Dictionary in MS Word or PDF format
  Page 5 of 5
  The assessment RUBRIC is given below:
  Excellent Satisfactory Fail
  Requirements
  Document
  (2)
  (2) (1) (0)
  All requirements documented in
  clear and complete manner. The
  document includes data
  requirements, transaction
  requirements and business rules.
  Many requirements outlined.
  Some requirements
  missing/incorrect.
  No requirements document.
  Excellent Good Satisfactory Poor Fail
  EER Model
  (10)
  (9-10) (7-8) (4-6) (2-3) (0-1)
  EER model is
  complete
  with/without any
  minor corrections.
  EER model has
  most constructs
  correctly
  represented.
  EER model has
  some constructs
  correct with major
  errors.
  Most constructs
  have errors. Poor
  EER design with
  major flaws in
  modelling
  requirements.
  EER model not in
  UML notation.
  None or few EER
  constructs shown.
  Excellent Satisfactory Fail
  Data Dictionary
  (3)
  (3) (1-2) (0)
  All constructs in the EER model are
  defined and documented in a clear,
  unambiguous manner.
  Data dictionary has most
  documentation but with some
  errors.
  No data dictionary.

  WX：codehelp