A WhackTheBalls session:

1

• A Whack-The-Balls session
• Every Friday the manager of Whack-The-Balls
  arranges the playing sessions for the week
  beginning in 4 weeks time. At the same time, the
  records of playing sessions from 4 weeks ago are
  deleted.
• Each session is booked either by a team or a
  member. The booking may subsequently be
  cancelled, in which case it will become available
  for re-booking. When the team or member arrives
  to play on the booked court the session is marked
  as played.
• The EEM for Whack-The-Balls records the following
  events for the session entity
• - Make team booking (M)
• - Make member booking (M)
• - Cancel booking (M)
• - Play session (M)
• - Arrange sessions (C/D)
• PRODUCE AN ELH FOR A WHACK-THE-BALLS SESSION.

2
SESSION
ARRANGE NEW SESSION
MANAGE SESSION
USESESSION
DELETE OLD SESSION
o
o

MARK AS PLAYED
----------
BOOK SESSION
CANCEL
o
o
o
o
MAKE TEAM BOOKING
MAKE MEMBER BOOKING
CANCEL TEAM BOOKING
CANCEL MEMBER BOOKING
3

• Produce an ECD for the event ARRANGE SESSION
  (could be old or new).

4
Session Number
NEW SESSION
OLD SESSION
SET OF EQUIPMENT BOOKING
EQUIPMENT BOOKING

5

• Produce an I/O structure diagram for the
  following Whack-The-Balls enquiry function
  description.
• When a playing court number is entered into the
  system it should return a list of all the
  sessions for which the court has been booked,
  giving details of the member or team that placed
  each booking.
• Assume the following attribute names are
  required
• Court
• Session
• Session start time
• Session end time
• Member
• Member name
• Team
• Team name

6

• LDS for Whack-The-Balls scenario

7

• Produce an EAP for the Whack-The-Balls court
  number enquiry report (from a previous slide),
  using the LDS from the immediately previous slide.

8
Court
SET OFSESSION
COURT
SESSION

o
o
BOOKED BY TEAM
BOOKED BY MEMBER
TEAM
Member
9

• CONSIDER THE FOLLOWING TABLE
• Customer Order
• Customer Order
• Customer
• Customer Name
• Customer Address
• Customer Tel.
• Depot
• Depot Name
• Product
• Product Name
• Product Qty
• Product Price
• ANY COMMENTS?...

10

• 1NF no repeating groups.
• Customer Order
• Customer
• Customer Name
• Customer Address
• Customer Tel.
• Depot
• Depot Name
• Customer Order
• Product
• Product Name
• Product Qty
• Product Price

11

• 2NF 1NF no non-key attributes which are
  dependent on only part of the primary key.
• Customer Order
• Customer
• Customer Name
• Customer Address
• Customer Tel.
• Depot
• Depot Name
• Customer Order
• Product
• Product Qty
• Product
• Product Name
• Product Price

12

• 3NF 2NF no non-key attributes which are
  dependent on other non-key attributes.
• Customer Order Customer Order
• Customer
• Depot
• Customer Customer Details
• Customer Name
• Customer Address
• Customer Tel.
• Depot Depot ID
• Depot Name
• Customer Order Customer Order Line
• Product
• Product Qty
• Product Product Details