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.

Slides:



Advertisements
Similar presentations
ELH 1 ELHs - Part 2, Development Initial identification of events and assignment to functions Construction of event/entity Matrix Drawing entity life histories.
Advertisements

Required System DFM Develop Required DFDs from selected BSO
DFD, LDS, ELH Inter-Relationships
Normalisation.
Manage Transfer Students. C3-TF Manage Transfer Students by School Student Registrar Description: –This function allows the School Student Registrar to;
WJEC Applied ICT Databases – Attributes & Entities Normalisation It is important in Database Design to make sure that the correct attributes are grouped.
Manage Student Deferment. C3-DF Manage Deferment by School Student Registrar Description: –This function allows the School Student Registrar to; Setup.
# 3- Click on Repeat: Free workbooks for previous adoptions # 2- Click on Free Materials Order # 1- Got to Note: Do not order more than your current enrollment.
ENTITY RELATIONSHIP MODELLING
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
Introduction  Jobcentre Plus is introducing a new service called Employer Direct online  You can post and manage your jobs 24 hours a day, 7 days a.
Athabasca University Under Development for COMP 200 Gary Novokowsky
Modeling the Data: Conceptual and Logical Data Modeling
SwE 313 Case Study Registration System.
Patient Visit Arrange Appointment AttendDiagnosisVerdict TreatmentAll Clear PrescriptionClinicHospital -/11/22/3 3/43/53/ Operations List.
1 5 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 5 Database Design: Normalization.
Entity Event Modelling
Further Data Modelling …and the effect of time. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis –Further.
Relational Data Analysis II. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis Feasibility Maintenance.
1 5 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 5 Database Design 1: Normalization.
Database development (MIS 533) MBS in Management Information Systems and Managerial Accounting Systems (2007 / 2008) Fergal Carton Business Information.
SABAL SHRESTHA SHERIF HALAWA SHAMA KHADPEKAR JIANWEI LAI SI TRAN GROUP A Tri-Airport Shuttle System.
Entity-Relationship Design
Chapter 7: The Object-Oriented Approach to Requirements
Reception.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 3 Requirements Models.
Systems Analysis and Design in a Changing World, Fifth Edition
CREATE THE DIFFERENCE Normalisation (special thanks to Janet Francis for this presentation)
CSE 441: Systems Analysis & Design
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
1 CMPT 275 Software Engineering Requirements Gathering Activity Janice Regan,
Assignements. CSC343: Intro. to Databases2 Exercise 1 Superkeys: Candidate keys: Primary key:
Customer Order Order Number Date Cust ID Last Name First Name State Amount Tax Rate Product 1 ID Product 1 Description Product 1 Quantity Product 2 ID.
Faculty of Computer & Information
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant.
1SSPD Jackson System Development From Models to Networks.
Database Beginnings. Scenario so far In our scenario we have people registering for training sessions. –The data about the training sessions was placed.
Section 08 (a)ER Modelling In Practice1 HSQ - DATABASES & SQL And Franchise Colleges 08 (a) ER Modelling In Practice QUICKHIRE Car Company.
Slide #1 Computerised Transit Computer System Training Session Trader Application Users.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Reports and Learning Resources Module 5 1. SLMS Primary Administrator Training Module 5: Reports and Learning Resources 2.
1 A Student Guide to Object- Oriented Development Chapter 6 Identifying Functionality.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
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.
Entity-Relationship (E-R) Diagrams
An Entity Relationship (ER) Diagram is a graphic that shows the interrelationship between entities in a database.
Description and exemplification of entity-relationship modelling.
Childcare And Family Information Service Anne Lalley Choice Adviser.
G045 Lecture 08 DFD Level 1 Diagrams (Data Flow Diagrams Level 1)
Database Design Normalisation. Last Session Looked at: –What databases were –Where they are used –How they are used.
V Slide 1V 1.0Slide 1 School Details School Administrator School JAN 1 Class Subject Update School Details  Basic Information  School Management.
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Information Access Mgt09/12/971 Entity-Relationship Design Information Level Design.
Children’s swimming lessons at the local swimming pool:
Database Training Date: 18/July/2008 Student Service Officers.
USE CASE Pertemuan 7 Matakuliah: Konsep object-oriented Tahun: 2009.
RELATIONAL TABLE NORMALIZATION. Key Concepts Guidelines for Primary Keys Deletion anomaly Update anomaly Insertion anomaly Functional dependency Transitive.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Modeling the Data: Conceptual and Logical Data Modeling.
Normalization. Overview Earliest  formalized database design technique and at one time was the starting point for logical database design. Today  is.
Analysis. This involves investigating what is required from the new system and what facilities are available. It would probably include:
G057 - Lecture 05 From Scenario To Design Mr C Johnston ICT Teacher
Normalisation Worked example for an Order Remember : The data should depend upon the key, the whole key and nothing but the key.
Intro to MIS – MGS351 Relational Database Design
SCC P2P – Collaboration Made Easy Contract Management training
UML Use Case Diagrams.
Start at 17th March 2012 end at 31th March 2012
To the ETS – Encumbrance Online Training Course
To the ETS – Encumbrance Online Training Course
Presentation transcript:

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.

SESSION ARRANGE NEW SESSION MANAGE SESSION USE SESSION DELETE OLD SESSION * BOOK SESSION MAKE TEAM BOOKING MAKE MEMBER BOOKING CANCEL CANCEL TEAM BOOKING CANCEL MEMBER BOOKING MARK AS PLAYED oo ooo o

IO Structure Diagram (I/OSD) BOOK SESSION GET BOOKING DATA ISSUE RESPONSE INDIVIDUAL DATA (input) TEAM DATA (input) oo CONFIRMATION (output) REJECTION (output) oo

A (disjoint) I/OSD Example Loan status Data of copies

Event Entity Matrix (EEM) Example Event

EEM Views Event

The ELH View (for entity “Reader”) Comm. with reader

The ECD View (for event “Lend”)

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

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

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

LDS for “Whack-The-Balls” scenario: TeamSportCourt Price Band Member Session Equipment contains played in hosts assigned to booked for requires use of plays played by tagged to is within made up of component of books booked by books played by plays used by consumed on

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

SET OF SESSION COURT Court # SESSION * TEAM BOOKED BY TEAM o BOOKED BY MEMBER o Member

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?...

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

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

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 Product Name Product Price

Another ELH Example (1) System 1 description: The system should manage boats taking part in a club tournaments. The system should allow boats to be registered and de-registered, as well as editing of their details. Furthermore, the system should allow the allocation and de- allocation of boats to races. Only boats registered in the system can participate in races. Registered boats can have their details and their race allocations edited any number of times. boat register boat de-register boat edit boat details allocate boat to race * oo

Another ELH Example (2) System 2 description: The system describes the movement of a lift to service a call. On receipt of a call and if the lift is idle, the lift will leave the floor at which it is located and proceed to next floor (either up or down). On arrival at a floor, the lift will either stop, if that is where the call originated from, or proceed with its movement. Once the lift stops at a floor, another call will make it leave that floor. lift leave initial floor arrive at floor leave current floor stop at floor- * oo

Interpreting an ELH student Student registration Enrol in module Withdraw from module * oo Amend student det. Premature departure Course completed Student departs o oo 1 year after student dep. Student permanence Student actions Student departure Normal departure