Music Boogie Barn A CSci 366 project Gone amok! Megan Bouret, Chazz Fangsrud, David Helm

Music Boogie Barn

A CSci 366 project

Gone amok!

Megan Bouret, Chazz Fangsrud, David Helm

Cash in on the CD sales business

• Music Boogie Barn Benefits: Oracle database backend for great justice

• Automated order placement, stock updates

Java Servlets and JSP frontend for easy access• Customers can search our vast stock

• All employees can use a JSP frontend for point of sale services, and can place orders for extra stock

• Managers can add employees

Schema

• Employee(firstName, lastName, password, employeeNumber, isManager, <useless info>)

• Customer(firstName, lastName, customerNumber, <useless info>)

• Product(UPC, Title, Artist, Genre, Year, Price)• Tracklist(Product, trackNumber, trackTitle)• Stock(Product, quantityInStock, moreOnOrder)• Orders(orderNumber, datePlaced, dateExpected,

quantityOrdered, cost)• ProductSold(Product, quantitySold)

Goals

• To discover how much work creating a working CDDB crossed with a point of sale system actually involves

• To illustrate the subtle complexities of trying to implement an Oracle database using triggers to handle tasks in a way that minimal effort is required on the part of the user to do things like place orders when a product is out of stock

• To remind ourselves that we are but mere mortals

Great Queries

• SELECT title, artist, price FROM PRODUCT; Gives you a view of our vast catalog of CDs to

offer our customer base

• UPDATE stock SET quantityInStock = 0 WHERE upc = (SELECT upc FROM PRODUCT (WHERE ARTIST = ‘Slayer’)) You must really like Slayer. Good thing the

database will automatically order more Slayer for you.