04 Idd PR CG 01

PROJECT
1.1 Implementing Database Design

Implementing Database Design 1.2
INSTRUCTOR NOTES
The following are the inputs for the faculty for project allocation and evaluation:
The project should be allocated to individual students by the end of the
Retrieving and Maintaining Data submodule.
The student can start the project earliest after the Experiment session of
Managing Databases is over.
During allocation, explain the students the scope of the project by referring to
the topic Project Activities and Project Timelines.
Ask the students to refer to the sample case study and its solution given in the
sample project documentation.
Ask the students to refer to the topic Project Standards and Guidelines before
starting the project documentation.
Before project evaluation day, ask the students to verify their projects according
to the standards and guidelines given in the topic Project Standards and
Guidelines.
Evaluate the students according to the guidelines given in the topic Project
Evaluation Guidelines.

CASE STUDY 1: SHOP HERE
Background
Shop Here is a leading departmental store in New York. The store is known for quality
products, affordable price range, timely services, and home delivery facility. The store
has customers from all sections of the society and procures goods from various
countries.
Existing System
Shop Here maintains an optimum inventory of various categories of items. The details
of the various categories are stored in the Categories file. This file contains data
about the item category numbers and the corresponding categories. The details of the
items are stored in a file named Items. The Items file contains records such as item
number, item description, item category number, serial number of the item, unit price
of each item, and reorder level of each item.
The store has several regular suppliers for the various items. The suppliers are spread
over various geographical locations. A detailed record is maintained for each supplier.
The supplier record consists of supplier code, supplier’s name, address, phone
number, country of origin, and shipment mode number and shipment mode for
outstation suppliers. All records are maintained in the Suppliers file.
Whenever the employee of a store places a purchase order, a purchase order form
needs to be filled out. The format of a purchase order form is as follows:
PURCHASE ORDER FORM
Purchase Order ID: Supplier ID:
Employee ID: Order Date:
Shipment Date: Quantity:
Shipment Method ID: Freight Charge:
A complete transaction takes place when the purchase is made and the payment is
done.
Envisioned System
Shop Here requires a computerized system that provides an effective method of
storing transaction details. The inventory-in-charge, Chris Symonds, realizes that with
growth in business, it becomes difficult to manually maintain the inventory. Shop Here

also wants to include the information about employees who place purchase orders with
the suppliers. Therefore, the management of the store has decided to computerize the
inventory management of the store. To fulfill this need, the store management has
contacted RedSky IT Systems to develop the computerized system. Don Allen, a
project manager of RedSky IT Systems, has been deputed to manage the assignment.
Don and his project team have:
1. Identified the various entities involved.
2. Identified the attributes of the various entities. The attributes should
completely define the entities.
3. Drawn an E/R diagram to demonstrate the relationship between the various
entities.
4. Mapped the E/R diagram to tables.
5. Normalized the tables to 3 NF. The normalized tables should have:
a. Table names
b. Field names, datatypes, and size of fields
c. Primary and foreign key identification and integrity
6. Drawn a diagram to show the relationships between various tables.
The final relationship diagram created by the project team is as follows:

Relationship Diagram For the Shop Here Database Management System

INSTRUCTOR NOTES
The various steps involved in creation of the relationship diagram are as follows:
Identifying Entities
The entities for the Shop Here database management system are:
1. Employees
2. Items
3. Purchase Orders
4. Suppliers
5. Categories
Identifying Attributes
The attributes of the entities listed above are as follows:
1. Employees: Employee ID, First Name, Last Name, Title, Phone
2. Items: Item ID, Item Name, Item Description, Category ID, Unit Price,
Reorder Level, Quantity On Hand
3. Purchase Orders: Purchase Order ID, Supplier ID, Employee ID, Order Date,
Shipping Date, Shipping Method, Freight Charge
4. Suppliers: Supplier ID, First Name, Last Name, Address, City, State, Zip,
Country, Phone
5. Categories: Category ID, Category Description

Drawing the E-R Diagram
1 m m m
EMPLOYEES PLACE PURCHASE ORDERS FOR ITEMS
m m
MADE HAS
FROM
1 1
SUPPLIERS CATEGORIES
Normalizing tables
The tables that will be created in the database are as follows:
Employees Items Purchase Orders
Employee Item ID Purchase Order

ID ID
First Name Item Name Supplier ID
Last Name Item Employee ID

Description
Title Category ID Order Date
Phone Unit Price Shipping Date
Reorder Level Shipping Method

ID
Quantity On Shipping Method

Hand (QOH)
Freight Charge

Suppliers Categories Inventory
Transactions
Supplier ID Category ID Transaction ID
First Name Category Purchase Order ID

Description
Last Name Item ID
Address Transaction
Description
City Transaction Date
State Quantity Ordered
Country Quantity Received
Zip Total Amount
Phone
Normalizing tables to 1NF

The tables are already in 1NF.

All the attributes of the tables are dependant on the whole key and not just part of the
key. Hence, the tables are in 2NF.

In the Purchase Orders table, the attribute Shipping Method depends on Shipping
Method ID and not on the Purchase Order ID. Therefore, for the tables to be in 3 NF,
we need to create another table, Shipment Methods.

Employees Items Purchase Orders
Employee Item ID Purchase Order ID

ID
First Name Item Name Supplier ID
Last Name Item Description Employee ID
Title Category ID Order Date
Phone Unit Price Shipping Date
Reorder Level Shipping Method ID
Quantity On Hand Freight Charge

(QOH)
Suppliers Categories Inventory

Transactions
Supplier ID Category ID Transaction ID
First Name Category Purchase Order ID

Description
Last Name Item ID
Address Transaction
Description
City Transaction Date
State Quantity Ordered
Country Quantity Received
Zip Total Amount
Phone

Shipment Methods
Shipment Method ID
Shipment Method Description
To create a computerized transaction system for Shop Here using SQL Server 2000,
the project team needs to perform the following tasks:
1. Create a database, ShopHere.
2. Create the tables as per the relationship diagram ensuring minimum disk
space utilization.
3. The validations to be performed on the tables are as follows:
Table: Items
a. Item ID must be unique.
b. Item ID must be auto generated.
c. Item name should not be left blank.
d. Item description should not be left blank.
e. The record should not be inserted or modified if QOH is 0.
f. Unit Price should be greater than 0.
g. ROQ should be greater than 0.
Table: Categories
a. Category ID must be unique.
b. Category ID must be auto generated.
c. Category description should not be left blank.
Table: ShippingMethods
a. Shipping Method ID must be unique.
b. Shipping Method ID must be auto generated.
c. Method description should not be left blank.
Table: Suppliers
a. Supplier ID must be unique.
b. Supplier ID must be auto generated.
c. First Name, Last Name, City, and Phone should not be left blank.
d. The Phone number must be in the following format:
‘[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]’
Example: 4356-555-555

Table: Employees
a. Employee ID must be unique.
b. Employee ID must be auto generated.
c. Employee First Name, Last Name, Phone should not be left blank.
d. The Phone number must be in the following format:
‘[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]’
e. The Title value must be any one of the following: ‘Trainee’, ’Floor
Manager’, ’Senior Manager’, ’Floor In Charge’ , ‘Executive’, ‘Senior
Executive’.
Table: PurchaseOrders
a. Purchase Order ID must be unique.
b. The purchase order id must be in the following format:
P[0-9][0-9][0-9]
Example: P001
c. The Order date should not be greater than the current date.
d. The Shipment date should not be less than the order date.
e. If the order date is not entered, the current date should be taken as the
default date.
f. The Freight Charge should be greater than 0.
Table: InventoryTransactions
a. Transaction ID should uniquely identify each record in the table.
b. Transaction ID should be auto generated.
c. The Transaction date should not be greater than the current date.
d. The Transaction date should be the current date if not entered.
e. The Transaction date should be greater than the order date.
f. Quantity Ordered, Quantity Received, and Unit Price should be greater
than 0.
g. The Quantity Received cannot be greater than the quantity ordered.
h. Total Amount should be automatically calculated using the formula
((Quantity Received*Unit Price of Item) + Freight Charge)
and be stored in the Total Amount field.
i. The Shipment date should be updated to two days after the transaction
date after the transaction is successfully completed.
j. The Quantity received should be added to the QOH in the Items table.
k. When a record is inserted into the table, the QOH in the Items table
should be updated automatically.
4. Create appropriate relationships between the tables.
5. The Transaction details need to be stored in a text file on a day-to-day basis.
Make use of the required tools to perform the data transfer.

6. You need to ensure that a supplier record is deleted from the Suppliers table
only after all the records from the dependant tables are deleted.
7. The users of the database need to perform the following queries frequently:
a. Extracting the transaction details for all the purchase orders in the current
month.
b. Extracting the details of all purchase orders handled by a particular
employee.
c. Extracting the details of all the orders placed more than two years back.
d. Displaying the details for all the employees based on the title of the
employees.
Based on the above queries, create the appropriate indexes to speed up the
execution of queries and joins.
8. The entire database should be created using SQL scripts. This will help to
ensure that the database and its objects can be recreated in minimum possible
time in event of a database crash.

CASE STUDY 2: SHOWMAN HOUSE
Background
Showman House is a large event management company of New York. The company
organizes various types of events throughout the year. The events types include
fashion shows, celebrity shows, chat shows, musical extravaganza, exhibitions, fairs,
and charity shows.
Existing System
Showman House organizes events of different types. The details of the various event
types are stored in the Event Types file. This file contains data about the event type
codes and the corresponding event types. Any attendee who wishes to organize an
event needs to provide details about the nature of the event he wants to organize.
Along with providing event details, he also makes the payment for the event. The
payment for an event is made in instalments, according to the fee plan, which is
stored in the Fee Schedules file. The Fee Schedules file maintains details such as fee
schedule id, event id, fee description, and fee amount. An attendee needs to pay all
the instalments of the payment, on or before the start date of the event.
All details related to an event such as event code, event name, event type code,
location of the event, start date, end date, event description, number of people, and
the staffing required for the event are stored in the Events file. The payment details
that include payment amount, payment date, payment method id, and payment
method description are also stored in the Events file. The details of an attendee such
as attendee id, attendee name, and address are stored in the Attendees file.
Any event at Showman House is managed by an employee. The employee details such
as employee id, first name, last name, title, and phone are stored in the Employees
file.
Envisioned System
The management of Showman House realize that it is difficult to maintain so much
data manually. Therefore, they have decided to computerize the entire system of
event management.
Blue Moon Computers have been assigned the task to computerize the system. The
project team of Blue Moon have:
entities.

a. Table names
Relationship Diagram for the Showman House Database Management System

INSTRUCTOR NOTES
The entities for the Showman House database management system are:
1. Attendees
2. Events
3. Fee Schedules
4. Employees
5. Event Types
1. Attendees: Attendee ID, First Name, Last Name, Address, City, State, Zip,
Country, Phone
2. Events: Event ID, Event Name, Event Type ID, Event Description, Location,
Start Date, End Date, Staffing Required, Employee ID, Attendee ID, No Of
People, Payment Date, Payment Amount, Payment Method ID, Payment
Method, Credit Card No, Card Holder Name, Expiry Date, Fee Schedule ID
3. Fee Schedules: Fee Schedule ID, Event ID, Fee Description, Fee
4. Employees: Employee ID, First Name, Last Name, Title, Phone
5. Event Types: Event Type ID, Event Type Description

1
HAS EVENT TYPES
m
1 PAY m 1 1
ATTENDEES EVENTS HAS FEE SCHEDULES
FOR
1
MANAGED
BY
1
EMPLOYEES
Normalizing Tables

Attendees Events Fee Schedules
Attendee ID Event ID Purchase Order ID
First Name Event Name Supplier ID
Last Name Event Description Employee ID
Address Event Type ID Order Date
City Location
State Start Date
Country End Date
Zip Staffing Required
Phone Employee ID
Attendee ID
No Of People
Payment Date
Payment Amount
Payment Method ID
Payment Method
Credit Card No
Card Holder Name
Expiry Date
Fee Schedule ID

Employees Event Types
Employee ID Event Type ID
First Name Event Type Description
Last Name
Address
City
State
Country
Zip
Phone

These tables are already in 1NF.
For 2 NF, the tables Attendees, Employees, Event Types, and Fee Schedules will not
change as they are already in 2 NF. In the Events table, Event ID, Attendee ID, and
Fee Schedule ID comprise the composite key. The attributes Payment Date, Payment
Amount, and Payment Method ID, Payment Method, Credit Card No, Card Holder
Name, and Expiry Date depend only on Event ID and Fee Schedule ID and not the
Attendee ID. Therefore, we need to create another table, Payments. Now, the tables
are as follows:

Attendee ID Event ID Fee Schedule ID
First Name Event Name Event ID
Last Name Event Description Fee Description
Address Event Type ID Fee
City Location
State Start Date
Country End Date
Phone Employee ID
Attendee ID
No Of People

Employees Event Types Payments
Employee ID Event Type ID Payment ID
First Name Event Type Description Payment Date
Last Name Payment Amount
Address Payment Method ID
City Payment Method
State Credit Card No
Country Card Holder Name
Zip Expiry Date
Phone Fee Schedule ID
Event ID

In the Payments table, the attribute Payment Method depends on Payment Method ID
and not on the Payment ID. Therefore, for the tables to be in 3 NF, we need to create
another table, Payment Methods.

Attendee ID Event ID Fee Schedule ID
First Name Event Name Event ID
Last Name Event Description Fee Description
Address Event Type ID Fee
City Location
State Start Date
Country End Date
Phone Employee ID
Attendee ID
No Of People

Employees Event Types Payments
Employee ID Event Type ID Payment ID
First Name Event Type Description Payment Date
Last Name Payment Amount
Address Payment Method ID
City Payment Method
State Credit Card No
Country Card Holder Name
Zip Expiry Date
Phone Fee Schedule ID
Event ID
Payment Methods
Payment Method ID
Payment Method Description
To create the computerized event management system for Showman House, the
project team at Blue Moon Computers needs to perform the following tasks:
1. Create a database, ShowmanHouse.
2. Create the table designs as per the relationship diagram ensuring minimum
disk space utilization.
Table: Employees
a. Employee ID should be unique.
b. The FirstName, LastName, City, and Phone should not be left blank.

c. The Title of the employees should be any one of the following: ‘Executive’,
’Senior Executive’, ‘Management Trainee’, ‘Event Manager’, ‘Senior Event
Manager’.
d. The Phone number should be in the following format:
‘[0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]’
Example: 11-111-111
Table: Events
a. Event ID should be unique.
b. Event ID should be auto generated.
c. Event Name, Start Date, End Date, Location, NoOfPeople, and
StaffingRequired should not be left blank.
d. NoOfPeople and StaffingRequired should be greater than 0.
e. The Start Date should be less than the End Date.
f. The Start Date and End Date should be greater than the current date.
Table: Payments
a. Payment ID must be unique.
b. Payment ID should be in the following format:
‘PA[0-9][0-9][0-9][0-9]’
Example: PA0001
c. Payment Date should be less than or equal to the start date of the event.
d. Payment Date cannot be less than the current date.
e. If the payment method is ‘Credit Card’, then it needs to be ensured that
the credit card details are entered for a new record being inserted into the
table. If the payment is not being done using a credit card, it must be
ensured that the credit card details are blank.
f. The Expiry date for the credit card should be greater than the current
date.
g. The Payment Amount must be compared with the fee given in the Fee
Schedule table for a given fee schedule ID and event ID. If the two values
match, the transaction is successful, else it needs to be rejected.
h. The Payment Amount must be greater than 0.
Table: Attendees
a. Attendee ID must be unique.
b. Attendee ID must be auto generated.
c. FirstName, LastName, Address, City, State, Phone should not be left
blank.
d. The Phone should be in the following format:
‘[0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]’
Example: 21-123-122
Table: FeeSchedules
a. Fee Schedule ID must be unique.

b. Fee Schedule ID must be auto generated.
c. Fee Schedule Description should not be left blank.
d. Fee Amount should be greater than 0.
Table: EventTypes
a. Event Type ID must be unique.
b. Event Type ID must be auto generated.
c. Description should not be left blank.
5. You need to ensure that an event record is deleted from the Events table only
after all the records from the dependant tables are deleted.
6. The details of all the employees who have managed an event in the current
month need to be stored in a text file. This information will be displayed on
the organization’s website. Make use of the required tools to perform the data
transfer.
a. Extracting the attendee details for an event organized on a particular date.
b. Displaying the fee schedule details for all events organized by the
organization.
c. Extracting event details for all the events where the payment is pending.
d. Displaying the details of all the events where the staffing required is
greater than 25.
Based on the above queries, create the appropriate indexes to speed up
the execution of queries and joins.

CASE STUDY 3: NEW PROJECT LTD
Background
New Project Ltd is a company that provides staff on contract for various project
assignments. The company is known for providing qualified and skilled staff that can
fulfill the project requirements efficiently. New Project employs professionals from
various fields that match the requirement of clients.
Existing System
New Project has a system of time cards. Time cards are issued to its employees for
working at the client site until the completion of the project. The employees use their
time cards for all work processes and expenses during the contract period. The time
card data enables New Project to prepare the final billing that needs to be submitted
to the clients for release of payment in lieu of work.
When a work agreement is signed, a project form needs to be filled out. The format of
this form is as follows:
PROJECT FORM
CLIENT SECTION
Client code: Company Name:
Address: Country:
Contact Person: Phone:
PROJECT SECTION
Project code: Project Name:
Project Description: Estimate Bill:
Start Date: End Date:
EMPLOYEE SECTION
Employee code: Employee Name:
Address: Country:
Work Phone: Billing Rate:

The client details are stored in the Clients file, the project details are stored in the
Projects file, and the employee details are stored in the Employees file. The next
form that needs to be filled out is the Time Card Details form. The format of the form
is as follows:
TIME CARD DETAILS
Time Card code: Employee code:
EXPENSES DETAILS
Time Card Expense code: Expense Description:
Expense code ID: Expense code:
Expense Date: Expense amount:
WORK DETAILS
Work code ID: Work code:
Work Description: Work date:
Project code:
BILL SECTION
Billed Hours: Billing Rate:
All employees fill the time card details on a daily basis. These details include Time
Card ID, Employee ID, Date Issued, Date Worked, Project ID, Work Description,
Billable Hours, and Work Code ID. The staffing-in-charge of New Project stores these
details in the Time Cards file. The work code Id defines the category of the task
performed by the employee in the project. The details related to the work codes are
stored in the Work Codes file which includes details such as work code id and work
code description.
During the project life cycle, employees might also incur expenses due to conveyance,
food etc. The details of the expenses incurred by an employee in a project are stored
in the Time Card Expenses file. These details include time card expense id, time
card id, expense date, expense amount, expense description, project id, expense code
id, and expense code. After every project, the company calculates its payment due
from the client and raises an invoice. On realization of the payment, all related data is
stored in the Payments file. This file contains data about payment code, payment
mode ID, payment mode name, corresponding project code, payment amount,
payment date, and credit card details if the client pays through credit card. Credit card
details consist of card number, cardholder’s name, and expiry date of the credit card.

Envisioned System
The management decided that manually maintaining such records was a cumbersome
process. It also gave rise to data redundancy and record duplication. Therefore, to
streamline the entire process, the best solution was to create databases and convert
the manual process to computerized process.
An in-house development team has been created to work on the project of
computerizing the staffing process of New Project Ltd. The development team has:
entities.
a. Table names

Relationship Diagram for the New Project Database Management System
INSTRUCTOR NOTES
The entities for the New Project database management system are:
1. Employees
2. Projects
3. Clients

4. Time Cards
5. Work Codes
6. Time Card Expenses
7. Payments
1. Employees: Employee ID, First Name, Last Name, Title, Phone, Billing Rate
2. Projects: Project ID, Project Name, Project Description, Client ID, Billing
Estimate, Employee ID, Start Date, End Date
3. Clients: Client ID, Company Name, Address, City, State, Zip, Country, Contact
Person, Phone
4. Time Cards: Time Card ID, Employee ID, Date Issued, Date Worked, Project
ID, Work Description, Billable Hours, Work Code ID
5. Work Codes: Work Code ID, Work Code Description
6. Expenses: Time Card Expense ID, Time Card ID, Expense Date, Project ID,
Expense Description, Expense Amount, Expense Code ID, Expense Code
7. Payments: Payment ID, Project ID, Payment Amount, Payment Date, Credit
Card No, Card Holder Name, Expiry Date, Payment Method ID, Payment
Method

PAYMENTS
EMPLOYEES
1 m
1
WORKS
ON
MADE
FILLS FOR
m 1
1
m 1
TIME CARDS PROJECTS GIVES CLIENTS
1 1
m m
RECORDED EXPENSES FOR
IN
Normalizing tables
Employees Projects Clients
Employee ID Project ID Client ID
First Name Project Name Company Name
Last Name Project Description Address
Title Client ID City
Phone Billing Estimate State
Billing Rate Start Date Country
End Date Zip
Employee ID Contact Person
Phone

Time Cards Work Codes Time Card Expenses
Time Card ID Work Code ID Time Card Expense

ID
Employee ID Work Code Description Time Card ID
Date Issued Expense Date
Date Worked Expense Amount
Project ID Expense Code ID
Work Description Expense Code
Billable Hours Project ID
Work Code ID Expense Description
Total Cost
Payments
Payment ID
Payment Date
Payment Amount
Project ID
Credit Card No
Card Holder Name
Expiry Date
Payment Method ID
Payment Method

The tables are already in 1NF.

For 2 NF, the tables Employees, Clients, Projects, Work Codes, Expenses, and
Payments will not change as they are already in 2 NF. In the Time Cards table, Time
Card ID, Employee ID, and Project ID comprise a composite key. The Date Worked,
Billable Hours, Work Description, Work Code ID depend only on Project ID and Time
Card ID and not the Employee ID. Therefore, we need to create another table, Time
Card Hours. Now, the tables are as follows:
End Date Zip
Phone
Time Card ID Work Code ID Time Card Expense ID
Expense Amount
Expense Code ID
Expense Code
Project ID
Expense Description

Payments Time Card Hours
Payment ID Time Card Detail ID
Payment Date Time Card ID
Payment Amount Project ID
Project ID Date Worked
Credit Card No Work Description
Card Holder Name Work Code ID
Expiry Date Billable Hours
Payment Method ID Total Cost
Payment Method

In the Payments table, the attribute Payment Method depends on Payment Method ID
and not on the Payment ID. Similarly, in the Time Card Expenses table, the attribute
Expense Code depends on the Expense Code ID and not on the Time Card Expense ID.
Therefore, for the tables to be in 3 NF, we need to create two more tables, Payment
Methods and Expense Codes.

End Date Zip
Phone
Time Card ID Work Code ID Time Card Expense ID
Expense Amount
Expense Code ID
Expense Code
Project ID
Expense Description
Payment ID Time Card Detail ID

Payment Date Time Card ID
Payment Amount Project ID
Project ID Date Worked
Credit Card No Work Description
Card Holder Name Work Code ID
Expiry Date Billable Hours
Payment Method ID Total Cost
Payment Method
Payment Methods Expense Codes
Payment Method ID Expense Code ID
Payment Method Description Expense Code Description
To create the computerized time card management system for New Project Ltd., the
development team needs to perform the following tasks:
1. Create a database, TimeCard.
Table: Clients
a. Client-ID must be auto generated.
b. Client-ID must be unique.
c. CompanyName, Contact Person, Address, City, and Phone should be
mandatory.
d. The phone number must be in the following format, (000)-(000)-(0000).
Table: Employees
a. Employee ID must be auto generated.
b. Employee ID must be unique.

c. Title must be any one of the following, ‘Trainee’, ‘Team Member’, ‘Team
Leader’, ‘Project Manager’, ‘Senior Project Manager’.
d. Billing Rate should be greater than 0.
e. First Name and Phone should not be left blank.
f. The phone number must be in the following format, (000)-(000)-(0000).
Table: Projects
a. Project ID should be unique.
b. Project ID should be in the format ‘P[0-9][0-9][0-9]’.
c. Project Name, Start Date, and End Date should not be left blank.
d. The Billing Estimate should be greater than 1000.
e. The start date should be less than the end date.
Table: PaymentMethods
a. The Payment Method ID should be in the format ,’PM [0-9][0-9][0-9]’
b. The Payment Description cannot be blank.
c. The Payment Method Id should be unique.
Table: Payments
a. The Payment Id should be auto generated.
b. The payment id should be unique.
c. The payment amount should be greater than 0.
d. The payment date should be greater than the end date of the project.
e. If the payment method is not ‘Credit Card’, the credit card details should
be null.
f. If the payment method is ‘Credit Card’, the Expiry date of the card should
be greater than the payment date.
g. If the payment method is ‘Credit Card’, ensure that the credit card details
are not blank.
Table: WorkCodes
a. The Work Code Id should be auto generated and unique.
b. The Description cannot be left blank.
Table: ExpenseCodes
a. The Expense Code ID should be auto generated and unique.
b. The Description should not be blank.
Table: TimeCards
a. The Time Card ID should be unique.
b. The Time Card ID should be auto generated.
c. The Date of issue of the time card should be greater than the current date
and the project start date to which the employee is assigned.
Table: TimeCardHours
a. The Date worked should be greater than the project start date.
b. The Date worked cannot be left blank.
c. The Time card detail id should be unique and auto generated.

d. The Total Cost should be automatically calculated using the formula
(Billable Hours * Billing Rate for the employee to whom the time card is
issued.)
e. Billable hours should be greater than 0.
Table: TimeCardExpenses
a. The Time Card Expense Id should be auto generated and unique.
b. The Expense date should be less than the project end date.
c. The Expense amount should be greater than 0.
d. The Expense date cannot be left blank.
5. The payment details of each client need to be documented and saved in a text
file.
a. Extracting the time card details for a employee based on employee names.
b. Extracting the expense details for all employees with time card ids in a
given range.
c. Displaying the name of an employee with the list of all projects that he is
working on.
d. Extracting a list of all projects that need to be completed in the current
month.
Based on the above queries, create the appropriate indexes to speed up the
execution of queries and joins.
7. You need to create a report displaying the projects and the details of the
employee assigned to a project in the following format:
Project ID: …………

Project Name: …………
Employee Name: …………
Employee Title: …………

PROJECT EXECUTION
This book contains three case studies. These case studies will be allocated to
individual students.
Phases in Project Execution

The project will be carried out in the following phases:
System Analysis: System analysis refers to an in-depth study of the existing
system to depict the functionality of the system. The analysis phase is the most
crucial phase in a project because it helps developers to identify the processes in
the system and functioning of each process. The project teams will analyze their
respective case studies before moving on to the development phase.
Development: This phase involves developing the project based on the
specifications.
Testing and debugging: This phase involves testing the project before
submitting it to the coordinator.
Documentation: Documentation is one of the most important aspects of
computer programming. The project documentation should be submitted to the
coordinator in the formats given in this book before the project walkthrough.
The blank report following the case studies is to be filled up, detached from the
book, and submitted on the given date.
Project Evaluation Guidelines

The project is to be evaluated based on the following parameters:
Quality: Conformance to requirements of the case study – 20 marks
x The solution maps to the requirements specified along with the case study
Timeliness - 20 marks
x Timely completion of the project
Quality of documentation - 40 marks
x Completion of all formats
x Adherence to standards and processes
Query handling during project walkthrough - 20 marks

Project Standards and Guidelines
The following standards and guidelines should be followed while creating the project.
Following these standards and guidelines is one of the evaluation criteria for the
project:
A consistent naming convention should be used for all database objects.
Fields in a table should not have a “.” character.
Project Activities
The students will get 16 hours to complete the project. The activities to be performed
during this period are:
a. Analyze the case study to identify the system processes.
b. Create the design of the database objects.
c. Test the tables with three or four records.
d. Debug the tables, stored procedures, triggers, and transactions in case of
any errors.
e. Document the project by using the formats given in the later section.
f. Submit the documentation to the faculty.
g. After submitting the documentation, the student will present the project to
the faculty. The faculty will assign marks to the student based on the
evaluation criterions specified in this section.
Project Timelines
The students should follow the given timelines to complete the project on time:
Session Task to be Performed

#
1 Analyze the case study and create the table design

with appropriate fields and their datatypes.
2 Create and execute the database creation script.

Refer to the sample script ‘CreatePayJunctionDB.sql’
for help.
Create the tables by applying the appropriate
constraints.
3 Create the table creation scripts.
4 Create the script which is used to enter sample

records into the database.
5 According to the validations, create the appropriate

Session Task to be Performed
#
stored procedures, triggers, and transactions.
6 Test the stored procedures, triggers, and

transactions as per the requirements of the project.
7 Create the appropriate indexes for the tables as per

the queries defined in the requirements.
8 Perform final validations and document the project.

SAMPLE CASE STUDY 4: PAY JUNCTION
Background
Pay Junction is a company that performs order processing and manages payment
realizations for other organizations.
Existing System
Pay junction maintains separate files for storing customer details and order details.
The Customer Details file consists of records such as customer code, customer
name, company name, address, country, phone number, and billing address.
When an order is processed, various parameters that affect the order are filled in a
form and then analyzed. The format of the Order Processing form is shown below:
ORDER PROCESSING
Order code: Order Details Code:
Customer code: Order Date:
Employee Code: Product code:
Product Name: Quantity:
Discount:
SHIPMENT DETAILS
Shipment Name: Shipping Address:
Shipping Country: Contact Phone:
Shipping Date: Shipping Method ID:
Shipping Method: Freight Charges:
Tax:
Total Amount:
The data related to the order and shipment is transferred from the Order Processing
form to the Orders file. The data related to the products ordered is stored in the
Products file.

The payments for orders are accepted through cash or credit card. When the customer
makes the payment, the Payments file is updated with the data about payment code,
order code, payment amount, payment date, payment mode ID, payment mode, and
credit card details if the customer pays through a credit card. The credit card details
consist of card number, cardholder’s name, and card expiry date.
Envisioned System
Pay Junction has decided to stop manual data storage and start computerized
database management and order processing. It would also enable the company to
have quicker communication with the clients.
A small group of database designers have been deployed by Pay Junction to develop a
computerized system of order processing and database management. Pay Junction
also wants to include the information about an employee who processes an order. This
information will include the employee code, name, title, and phone number.
The development team has:
entities.
a. Table names

Relationship Diagram for the Pay Junction Database Management System
To create the computerized system, the team needs to perform the following tasks:
1. Create a database, PayJunction.
Table: Customers
a. Cust_Id must be unique.
b. Cust_Id must be auto generated.
c. The FirstName, LastName, Address, City, State, and Phone should not be
left blank.
d. The phone number should be entered in the format, 0000-000-000.
Table: Employees
a. Emp_Id must be unique.

b. Auto generation on the Emp_Id column.
c. The phone number should be in the format, 0000-000-000.
d. The Title must be in the list, ‘Executive’, ’Senior Executive’, ‘Manager’,
’Chairman’.
e. The FirstName and LastName fields should not be left blank.
Table: Products
a. Product_Id must be unique.
b. The product id must be of the format, ‘P[0-9][0-9][0-9]’
c. The Unit Price should be greater than 0.
d. The Product name, description and price should not be left blank.
Table: PaymentMethods
a. PaymentMethod_Id must be unique.
b. The payment method id must be of the format, ‘PM[0-9][0-9][0-9]’
c. The description should not be left blank.
Table: ShipmentMethods
a. ShipmentMethod_Id must be unique.
b. The shipment method id must be of the format, ‘SH[0-9][0-9][0-9]’
c. The description should not be left blank.
Table: Orders
a. Order_Id must be unique.
b. The order id must be of the format, ‘O[0-9][0-9][0-9]’
c. The shipment name, shipment address, shipment city, shipment state,
shipment phone, shipment country, shipment date, freight charge, and tax
should not be left blank.
d. The shipment phone should be in the format, ‘[0-9][0-9][0-9][0-9]-[0-
9][0-9][0-9]-[0-9][0-9][0-9]’
e. The Order date should not greater than the current date.
f. If the order date is not entered, the current date should be taken as the
default order date.
g. Freight charge must be greater than 0.
h. Tax should be greater than 0.
i. When an insertion is made into the Orders table, an insertion should be
made into the OrderDetails table. The insertion should take place only
after all the values in the Orders table have been validated.
j. The Shipment Date cannot be greater than the order date.
Table: OrderDetails
a. OrderDetail_Id must be unique.
b. Auto generation of OrderDetail_Id.
c. The quantity and discount should not be left blank.
d. The Total cost should be calculated automatically and added to the total
cost field.
e. The Quantity should be greater than 0.

Table: Payments
a. Payment_Id must be unique.
b. Auto generation of Payment_Id.
c. The payment amount should be greater than 0.
d. The payment amount should be equal to the sum of the total costs for a
given order id in the OrderDetails table. If the amounts do not match, the
transaction should be rejected and a user-friendly message should be
displayed to the user.
e. The shipment date should be updated to two days after the payment date
if the transaction is successful.
f. The payment date should be greater than the order date.
g. The Credit card number must be in the following format, ‘[0-9][0-9][0-9]-
[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9]’.
h. The payment amount and payment date fields should not be left blank.
i. If the payment method is ‘Credit Card’, ensure that the credit card details
are not blank.
j. If the payment method is not ‘Credit Card’, ensure that the credit card
details are blank.
k. The Expiry date for the credit card should be greater than the current
date.
5. A yearly sales report needs to be sent to each customer displaying their order
details in the current year. Make use of the required tools to perform the data
transfer.
6. The order details for a given customer id need to be stored in a text file. Make
use of the required tools to perform the data transfer.
a. Extracting order details of the orders placed on a particular date along
with the product details.
b. Extracting for all orders whose payments are pending.
c. Displaying the customer details for all customers living in a particular city.
d. Displaying the customer details for all customers with a given first name
and last name.

SOLUTION TO CASE STUDY 4 – PAY
JUNCTION
To create the PayJunction database and its objects, you need to make use of the SQL
Scripts provided in the TIRM CD.
1. CreatePayJunctionDatabase.sql: The script contains the code for creating a
database. It removes the database if it already exists in SQL Server.
2. CreatePayJunctionObjects.sql: The script contains the statements required
to create the tables of the database. It also contains statements used to insert
sample records into the tables.
3. CreatePayJunctionConstraints.sql: The script contains the SQL statements
used for creation of constraints, rules, and defaults as per the validations
required.
4. CreatePayJunctionProcedures.sql: The script contains the batch
statements that create the generic procedures and triggers in the database.
5. CreatePayJunctionIndexes.sql: The script contains the SQL statements
used to create indexes to speed up the execution of the frequently used
queries.
6. CreatePayJunctionForBCPandDTS.sql: The script contains the SQL queries
used to retrieve the data to be transferred to external applications using BCP
and DTS.
7. ErrorDetectionForProceduresandTriggers.sql: The script contains
statements which test the database objects for validity.

SAMPLE PROJECT DOCUMENTATION: PAY
JUNCTION
PROJECT ON
Pay Junction Database Management System
Developed by
Name: Debbie Howe
Reg. No.: 4701-10-258

Pay Junction Database Management
System
(Project Title)
Batch Code : B010101

Start Date : June 1, 2003
End Date : June 10, 2003
Name of the Coordinator : Alex Norton
Name of Developer : Debbie Howe
Date of Submission : June 11, 2003

CERTIFICATE
This is to certify that this report titled Pay Junction Database

Management System embodies the original work done by Debbie
Howe in partial fulfillment of their course requirement at NIIT.
Coordinator:
Alex Norton

ACKNOWLEDGEMENT
We have benefited a lot from the feedback and suggestions given

to us by Mr. Alex Norton and other faculty members.

SYSTEM ANALYSIS
System Summary: Pay Junction is a consultancy firm that manages

order processing and payment realizations for any organization.
The company has decided to stop manual data entry. Instead, it has
decided to make use of a computerized database management for
processing orders and payment realizations. This would enable the
company to have quicker communication with the clients.

DATABASE DESIGN
Database Name: PayJunction
Number of tables: 8
Table Names:
1. Customers
2. Employees
3. Products
4. PaymentMethods
5. ShipmentMethods
6. Orders
7. OrderDetails
8. Payments

SCHEMATIC DIAGRAM OF DATABASE
Schematic diagram of the database depicting the primary and
foreign key relationships.

TABLE DESIGN

Customers
Field Name Data type Width Description
Cust_Id int Customer Number
First Name varchar 30 Customer First

Name
Last Name varchar 30 Customer Last

Name
Address varchar 50 Customer Address
City varchar 30 Customer City
State varchar 30 Customer State
Zip char 10 Zip Code
Country varchar 20 Customer Country
Phone char 20 Phone Number

Employees
Field Data type Width Description

Name
Emp_Id int Employee Number
First Name varchar 30 Employee First

Name
Last Name varchar 30 Employee Last

Name
Title varchar 30 Employee

Designation
Phone char 20 Phone Number
PaymentMethods
Field Name Data Width Description

type
PaymentMethod_Id char 5 Payment Method

Number
PaymentMethodDesc varchar 30 Payment Method

Description

ShipmentMethods

type
ShipmentMethod_Id char 5 Shipment

Method
Number
ShipmentMethodDesc varchar 30 Shipment

Method
Description
Products
Product_Id char 4 Product Number
Prod_Name varchar 30 Name of the

product
Prod_Desc varchar 50 Description of

product
UnitPrice money Cost of the

product

OrderDetails

type
OrderDetail_Id int Order Detail Number
Order_Id char 4 Order Number
Product_Id char 4 Product Number
Quantity int Quantity of the

product bought
Discount smallint Discount on the

payment amount
TotalCost money (Quantity * Unit Price)

+ Tax * (Quantity *
Unit Price) + Freight
Charge – Discount *
(Quantity * Unit Price)

Payments
Payment_Id int Payment

Number
Order_Id char 4 Order

Number
Payment Amount money Amount

paid for
the order
Payment Date datetime Date of

payment
PaymentMethod_Id char 5 Payment

Method
Number
CreditCardNo char 20 Credit

Card
Number
CardHolderName varchar 30 Credit card

holder’s
name
ExpiryDate datetime Expiry

Date of the
credit card

Orders

type
Order_Id char 4 Order Number
Cust_Id int Customer

Number
Emp_Id int Employee

Number
ShipmentMethod_Id char 5 Shipment

Method Number
OrderDate datetime Date when the

order was
placed
ShipName varchar 30 Name of the

parcel to be
shipped
ShipAddress varchar 30 Place for

shipment
ShipCity varchar 30 Shipment City
ShipState varchar 30 Shipment State
ShipCountry varchar 20 Shipment

Country
ShipPhone char 20 Shipment Phone
ShipDate datetime Date of the

shipment
Freight Charge money Shipping

charges
Tax smallint Tax applied on

the payment

VALIDATIONS PERFORMED
Customers
Validation Required Method Used For Validation
Cust_Id must be unique. Primary key constraint
Cust_Id must be auto generated. Stored Procedure and batch

programming
The FirstName, LastName, NOT NULL clause in the CREATE

Address, City, State, and Phone TABLE statement
should not be left blank.
The phone number should be CHECK constraint

entered in the format, 0000-000-
000.
Employees
Emp_Id must be unique. Primary key constraint
Auto generation on the Emp_Id Stored Procedure and batch

column. programming
The phone number should be in CHECK constraint

the format, 0000-000-000.
The Title must be in the list, CHECK constraint

‘Executive’, ’Senior Executive’,
‘Manager’, ’Chairman’.
The FirstName, LastName, Title, NOT NULL clause in the CREATE

and Phone fields should not be TABLE statement
left blank.

Products
Product_Id must be unique. Primary Key constraint
The product id must be of the CHECK constraint

format, ‘P[0-9][0-9][0-9]’
The Unit Price should be greater Rule

than 0.
The Product name, description NOT NULL clause in the CREATE

and price should not be left TABLE statement
blank.
PaymentMethods
PaymentMethod_Id must be Primary Key constraint

unique.
The payment method id must be Rule

of the format, ‘PM[0-9][0-9][0-9]’
The description should not be left NOT NULL clause in the CREATE
blank. TABLE statement

ShipmentMethods
ShipmentMethod_Id must be Primary Key constraint

unique.
The shipment method id must be Rule

of the format, ‘SH[0-9][0-9][0-
9]’
The description should not be left NOT NULL clause in the CREATE
blank. TABLE statement
Orders
Order_Id must be unique. Primary Key constraint
The order id must be of the CHECK constraint

format, ‘O[0-9][0-9][0-9]’
The shipment name, shipment NOT NULL clause in the CREATE

address, shipment city, shipment TABLE statement
state, shipment phone, shipment
country, shipment date, freight
charge, and tax should not be left
blank.
The shipment phone should be in Rule

the format, ‘[0-9][0-9][0-9][0-9]-
[0-9][0-9][0-9]-[0-9][0-9][0-9]’
The Order date should not be Trigger

greater than the current date.
If the order date is not entered, Default

the current date should be taken
as the default order date.
Freight charge must be greater CHECK constraint

than 0.

Tax should be greater than 0. CHECK constraint
When an insertion is made into Stored Procedure and batch

the Orders table, an insertion programming
should be made into the
OrderDetails table. The insertion
should take place only after all the
values in the Orders table have
been validated.
The Shipment Date cannot be Trigger

greater than the order date.
OrderDetails
OrderDetail_Id must be unique. Primary Key constraint
Auto generation of OrderDetail_Id. Stored Procedure and batch

programming
The quantity and discount should NOT NULL clause in the CREATE
not be left blank. TABLE statement
The Total cost should be calculated Trigger

automatically and added to the
total cost field.
The Quantity should be greater Rule

than 0.

Payments
Payment_Id must be unique. Primary Key constraint
Auto generation of Payment_Id. Stored Procedure and batch

programming
The payment amount should be greater CHECK constraint

than 0.
The payment amount should be equal to Triggers, Aggregate Functions,

the sum of the total costs for a given and Joins
order id in the OrderDetails table. If the
amounts do not match, the transaction
should be rejected and a user-friendly
message should be displayed to the user.
The shipment date should be updated to Trigger and Update statement

two days after the payment date if the
transaction is successful.
The payment date should be greater than Trigger and batch programming
the order date.
The Credit card number must be in the CHECK constraint

following format, ‘[0-9][0-9][0-9]-[0-
9][0-9][0-9][0-9]-[0-9][0-9][0-9]’.
The payment amount and payment date NOT NULL clause in the CREATE
fields should not be left blank. TABLE statement
If the payment method is ‘Credit Card’, Trigger

ensure that the credit card details are not
blank.
If the payment method is not ‘Credit Trigger

Card’, ensure that the credit card
details are blank.
The Expiry date for the credit card Trigger

should be greater than the current
date.

REPORTS OUTLINE
Report Name Report Type Description Tables/Queries

Used
Customer Text File This report OrderDetails,

Report displays the Orders, and
order details Customers
such as the
Order Detail
Id, Order Id,
Product
Name, Unit
Price, Freight
Charge, Tax,
Discount,
Total Cost,
and Quantity
for a given
customer id.
Yearly Sales Excel Sheet This report OrderDetails,

Report displays the Orders, and
Order_Id and Customers
the
cumulative
cost for the
order for the
customer in
the current
year.

CONFIGURATION
Hardware: PC compatible with a Intel Pentium-III processor, 128-MB

RAM, and 20GB of Hard disk
Operating system: Windows 2003 Server
Software: Microsoft SQL Server 2000 Enterprise Edition
PROJECT FILE DETAILS

S.No File Name Remarks
1 PayJunction.mdf SQL Server database that contains

tables, procedures, triggers,
PayJunction_log.ldf
constraints, and queries.

BLANK DOCUMENTATION FORMATS
PROJECT ON
Developed by
Name:
Reg. No.:

(Project Title)
Batch Code :
Start Date :
End Date :
Name of the Coordinator :
Name of Developer :
Date of Submission :

CERTIFICATE
This is to certify that this report titled __________ embodies the

original work done by ___________ in partial fulfillment of their
course requirement at NIIT.
Coordinator:

ACKNOWLEDGEMENT

SYSTEM ANALYSIS
System Summary:

DATABASE DESIGN
Database Name:
No of Tables:
Name of Tables:

SCHEMATIC DIAGRAM OF DATABASE
Database Name:
Schematic diagram for the database depicting the primary and
foreign key relationships.

TABLE DESIGN
Database Name:
Table Name:

VALIDATIONS PERFORMED

REPORTS OUTLINE
Report Name Report Type Description Tables/Queries

Used

CONFIGURATION
Hardware:
Operating System:
Software:
PROJECT FILE DETAILS

S.No File Name Remarks

04 Idd PR CG 01

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

04 Idd PR CG 01

Încărcat de

Drepturi de autor:

Formate disponibile

PROJECT

1.1 Implementing Database Design

1.3 Implementing Database Design

PURCHASE ORDER FORM

Purchase Order ID: Supplier ID:

Employee ID: Order Date:

Shipment Date: Quantity:

Shipment Method ID: Freight Charge:

Implementing Database Design 1.4

1.5 Implementing Database Design

Implementing Database Design 1.6

1.7 Implementing Database Design

Employees Items Purchase Orders

Employee Item ID Purchase Order

First Name Item Name Supplier ID

Last Name Item Employee ID

Title Category ID Order Date

Phone Unit Price Shipping Date

Reorder Level Shipping Method

Quantity On Shipping Method

Implementing Database Design 1.8

Supplier ID Category ID Transaction ID

First Name Category Purchase Order ID

Last Name Item ID

City Transaction Date

State Quantity Ordered

Country Quantity Received

Zip Total Amount

Normalizing tables to 1NF

Normalizing tables to 2NF

Normalizing tables to 3NF

1.9 Implementing Database Design

Employee Item ID Purchase Order ID

First Name Item Name Supplier ID

Last Name Item Description Employee ID

Title Category ID Order Date

Phone Unit Price Shipping Date

Reorder Level Shipping Method ID

Quantity On Hand Freight Charge

Suppliers Categories Inventory

Supplier ID Category ID Transaction ID

First Name Category Purchase Order ID

Last Name Item ID

City Transaction Date

State Quantity Ordered

Country Quantity Received

Zip Total Amount

Implementing Database Design 1.10

Shipment Method Description

1.11 Implementing Database Design

Implementing Database Design 1.12

1.13 Implementing Database Design

Implementing Database Design 1.14

Relationship Diagram for the Showman House Database Management System

1.15 Implementing Database Design

Implementing Database Design 1.16

1.17 Implementing Database Design

Attendee ID Event ID Purchase Order ID

First Name Event Name Supplier ID

Last Name Event Description Employee ID

Address Event Type ID Order Date

State Start Date