INFO275

Database ManagementTerm Project

Overview• Your project will be to define, design and build a functioning database, to

support an application that you choose. • Minimum of 10 to 12 relations, with at least 2 being ‘event’ types.• Work will be done in teams of 2 or 3• Value: 20% of course grade• The project will involve providing the following:

• Deliverable 1: (Due Nov 19th) (50%)• A summary of your application – what is its purpose? What kinds of user transactions

does it support.• Logical Design

• Deliverable 2: (Due Nov 29th) (50%)• Physical design• Functional database, populated with sample data• A set of queries, and results of queries• Application Screen ‘mock ups’

Deliverable 1 – November 19 in class• Word Document

• Summary of your application – why are you building the database• A list of user transactions that will be supported – see the cases in

appendix B in your text for examples.• Design:

• Entity descriptions (assignment 1)• Relationship descriptions (assignment 1)• Attribute and domain descriptions (assignment 1)• ER Diagram (assignment 2) in Visio Remember: minimum of 10 – 12 relations.

• Relations, attributes, PK and FKs, relationships• Referential integrity for Delete of Parent (assignment 2)

Deliverable 2 – Nov 28 in class• Word Document

• Physical design (next page)• Database structure (DDL)• Sample data listing – tabular (spreadsheet) format • A set of at least 10 useful queries. You will include the DML statement

AND the result of each query. At least 6 queries must be multi-table. • At least 5 data input screen mockups (examples to be provided) – Visio.• On a separate page – provide Account details (User Name and Password)

where database exists.• Implemented, functioning database – Oracle

• Populated with sample data – at least 5 rows in each table. • I WILL TEST YOUR DATABASE WITH YOUR QUERIES

Physical Design• For each table, create the following:

Column Name

Description Data Type NULL or NOT NULL

DEFAULT DELETE REF. INT. Constraint

Name of column

Brief description of meaning

Valid Oracle type

Indicate if NULLS allowed

Specify default value, if you feel there should be one

List the DELETE constraints for EACH PARENT (foreign Key)

• Note: You DO NOT need to implement your RI constraints in your DDL. You DO need to implement your NULL and DEFAULT constraints.

Document Format• Each deliverable document must have:

• Title Page• Document Introduction• Page numbers• Introduction to each section. For example, in deliverable 1,

explain what entity descriptions, relationship descriptions and attribute / domain descriptions are before you present them.

• Use: 11 point Arial font and 1 inch margins. Singe spaced.

Process• Form teams of 2 – 3 SOON• Think about what application you want to build

• NOTHING GENERIC ‘Order processing’ or ‘Inventory Control’• Choose something that interests you• Be as specific as you can

• “Build a database to manage St FX societies application for funding from the students union”

• “Build a database to support a fantasy football league including defining league participants, fantasy teams, collection of stats, reports of results"

• You must schedule a meeting with me to discuss your database on or by November 5th. You cannot proceed without my approval.