Ananth Krishna Kunal Jiwarajka

1

• Ananth Krishna Kunal Jiwarajka
• Johnathan Anastacio Lilia Gutnik
• Jonathan Yorde Nathan Burkhart
• Kathy Kwon Noe Lozano

2
BLACK LIGHTNING

• Lecture note taking service
• 30 employees
• 25 courses offered per semester
• 35 lectures per course
• Notes for a total of 300 courses archived
• 1000 current subscribers

3
CURRENT SYSTEM

• Difficult-to-use web-based database
• information on courses and lectures
• Excel spreadsheets
• Hard copy forms
• receiving/editing lectures
• Microsoft Outlook
• lecture backup copies, contact information
• Filing cabinet
• hard copy lecture notes and handouts from class

4
BENEFITS FROM DATABASE

• More efficient review of lecture submissions
• Forecasting of popular courses made possible
• Consistency of information
• Tabs on employee performance
• Ratings
• Professors, employees, courses, etc.
• More efficient data entry

5
PROJECT SUMMARY

1. Black Lightning notes are organized by series.
   Each series has a unique name and course control
   number it is broken up into a specific lecture
   which is identified by its unique number as well
   as the semester, year, date, and location it was
   taught. We keep track of the subscriptions made
   for each lecture series and the payment method
   and amount for each subscription.

6
PROJECT SUMMARY

• 2. Comments/complaints made about the lecture
  series, who took and edited the notes for the
  lecture/series and when, and the professor and/or
  GSI who teaches the course are also all stored.
  Each person has a unique number, a name, contact
  information, among others.

7
PROJECT SUMMARY

• 3. There are four different types of employees
  senior editor, manager, editor, and note taker.
  Each employee type is identified by a unique
  number, a name, and contact information. We also
  keep track of the hours each employee has worked
  and which lecture(s) they took notes for.

8
DATABASE REQUIREMENTS

• Person
• Subscriber
• Speaker
• Professor / GSI
• Employee
• Senior editor, Manager, Editor, Note taker

• Series
• Lecture
• Transaction
• Subscription

9
EER DIAGRAM
10
PERSON

• Subscriber
• Speaker
• Employee

11
LECTURE

• Series
• Relation-ship to Persons

12
TRANSACTION

• Relationship to
• Subscriber
• Relationship to
• Lectures/Series

13
EER DIAGRAM
14
SCHEDULE

• DP Review 2 Nov.18 Noe, John A., Ananth
• Revised EER diagram
• Relational Design schema
• Queries (5) English
• DP Review 3 Nov.21 Lilia, Nathan, Kathy
• Executive Summary
• Relational Design in Access
• Queries (5) English Algebra/SQL
• Final Presentation Dec.9 Kunal, Jon Y., Noe
• Summary of Presentations 1-3
• Normalization analysis
• Final Report Dec.12 John A., Lilia, Ananth
• Final Executive Summary and Access Designs
• Full normalization analysis

15
(No Transcript)