Online Transaction Processing (OLTP) System for Dir Maidan Palace (Saeed BS project)

ONLINE TRANSACTION PROCESSING (OLTP) SYSTEM
FOR DIR MAIDAN PALACE
SUBMITTED BY
IJAZ ULLAH
SAEED ULLAH
Supervised By
FATIMA-TUZ-ZUHRA
BCS
Session 2009-2013
DEPARTMENT OF COPMUTER SCIENCE
UNIVERSITY OF PESHAWAR

I
In the name of ALLAH, the most Beneficent, the Most Merciful

II
DEDICATION
Our beloved parents and friends, whose Prayers and encouragement
boosted us to complete our project successfully and
We dedicate this Effort, to our teachers, whose blessings, guidance and
encouragement helped us succeed in our goals.
IJAZ ULLAH
SAEED ULLAH

III
PROJECT APPROVAL
The committe certifies that this thesis forwarded by Ijaz Ullah and Saeed Ullah is up to
standard and we here by approve it for its acceptance as a partial fulfillment for the
award of four years degree of BCS(Bachelor of Computer Science) from the department
of Computer science, University of Peshawar Khyber Pakhtunkhwa.
External Examiner _______________________________
Remarks: _______________________________
Internal Examiner _______________________________
Remarks: _______________________________
Chairman ________________________________
Remarks: ________________________________

IV
PROJECT IN BRIEF
Online Transaction Processing (OLTP)
System for Dir Maidan Palace
Developed By: Ijaz Ullah
Saeed Ullah
Internal Supervisor: Madam Fatima-tuz-Zuhra
Department of Computer Science
University of Peshawar
Starting Date: 14 / 03/ 2013__
Completion Date: 10/ 02/ 2014__
Development Tools Used: Oracle Developer Suite 10g For interface design
ERWin for ERD
MS Word for Documentation
Operating System Used: Windows 7

V
ABSTRACT
OLTP System for Dir Maidan Palace
Dir Maidan Palace is residential building in which flats, shop and rooms are available.
Clients can book it any time through paying rent.
For every organization the data of their interest is important and in Dir Maidan Palace up
to current time there is no use of computer technology or software and all the data is
stored manually which is time consuming as well as there is a lot of chances to loss
important data. Client records are stored in many registers which causes data
redundancy.
So for the consideration of the given problems to solve we conducted over whelming
requirement analysis and presented a computerized model solution which fulfill all the
organizational needs of Dir Maidan Palace.
The basic motive, on the basis of which an organization may decide to install a
computerized system that helps to reduce cost, errors, redundancies, additional resources
and above all it increases accuracy to a great extent. Any sort of the data may be
searched, manipulated and reported on time.

VI
TABLE OF CONTENTS
CHAPTER 1 INTRODUCTION ......................................................................1
1.1 PROJECT INTRODUCTION..........................................................................2
1.2 PROJECT AT A GLANCE.............................................................................2
1.2.1 The Organization..............................................................................................................................3
1.2.2 DBMS Used........................................................................................................................................3
1.2.3 Front End Tool..................................................................................................................................4
1.2.4 Reports...............................................................................................................................................4
CHAPTER 2 THE PROPOSED SYSTEM ....................................................5
2.1 THE PRESENT SYSTEM ..............................................................................6
2.2 INTRODUCTION TO THE PROPOSED SYSTEM.........................................6
2.3 OBJECTIVES OF THE PROPOSED SYSTEM .............................................7
2.4 FEATURES OF THE PROPOSED SYSTEM.................................................8
2.4.1 Database Design ..............................................................................................................................8
2.4.2 User Interface....................................................................................................................................8
2.4.3 Simple to Use....................................................................................................................................8
2.4.4 Data Validation .................................................................................................................................9
2.4.5 Quick Search.....................................................................................................................................9
2.4.6 Storage of Data.................................................................................................................................9
2.4.7 Reports Generation.........................................................................................................................9
CHAPTER 3 DATA MODELING ...................................................................10
3.1 INTRODUCTION..........................................................................................11

VII
3.2 DATA MODEL............................................................................................. 11
3.3 ENTITY RELATIONSHIP MODEL............................................................... 11
3.4 ENTITY RELATIONSHIP MODELING (ERM)............................................. 11
3.4.1 Entity.................................................................................................................................................12
3.4.2 Attributes .........................................................................................................................................12
3.4.3 Relationship ....................................................................................................................................12
3.5 IDENTIFIED ENTITIES AND THEIR ATTRIBUTES.................................... 13
3.5.1 CLIENT..............................................................................................................................................13
3.5.2 FLAT..................................................................................................................................................13
3.5.3 SHOP.................................................................................................................................................14
3.5.4 ROOM................................................................................................................................................14
3.5.5 RESERVATION ...............................................................................................................................15
3.5.6 EMPLOYEE......................................................................................................................................15
3.5.7 EMP_SAL_DETAIL.........................................................................................................................16
3.5.8 PAYMENT ........................................................................................................................................16
3.5.9 OWNER.............................................................................................................................................17
3.5.10 EXPENSES ....................................................................................................................................17
3.5.11 RENT...............................................................................................................................................18
3.5.12 LEAVING ........................................................................................................................................18
3.6 ENTITY RELATIONSHIP DIAGRAM (ERD)................................................ 19
3.6.1 Identified Entity Relationship Diagram (ERD) ........................................................................19
CHAPTER 4 DATA DICTIONARY ................................................................. 20
4.1 DESCRIPTION ............................................................................................ 21
CLIENT.............................................................................................................. 21
FLAT.................................................................................................................. 22

VIII
SHOP.................................................................................................................22
ROOM................................................................................................................23
RESERVATION .................................................................................................24
EMPLOYEE .......................................................................................................25
EMP_SAL_DETAIL ...........................................................................................25
PAYMENT..........................................................................................................26
OWNER .............................................................................................................26
EXPENSES........................................................................................................27
RENT .................................................................................................................28
LEAVING ...........................................................................................................28
CHAPTER 5 NORMALIZATION ...................................................................29
5.1 INTRODUCTION..........................................................................................30
5.2 MAIN GOALS OF NORMALIZATION .........................................................30
5.3 NORMALIZATION AVOIDS ........................................................................30
5.4 STEPS IN NORMALIZATION......................................................................31
5.4.1 Normal Form ...................................................................................................................................31
5.5 NORMALIZATION IN OLTP SYSTEM FOR DIR MAIDAN PALACE..........33
5.5.1 CLIENT_TRANSACTION...............................................................................................................33
CHAPTER 6 INTERFACE DESIGN .................................................................35
6.1 INTRODUCTION..........................................................................................36
6.2 SNAPSHOTS OF THE FORMS...................................................................36

IX
6.2.1 Login Page ......................................................................................................................................37
6.2.2 Main Page ........................................................................................................................................38
6.2.3 Entry Section ..................................................................................................................................39
6.2.4 Client Reservation.........................................................................................................................40
6.2.4.1 Rent Form.....................................................................................................................................41
6.2.4.2 Leaving Form...............................................................................................................................42
6.2.5 Property Details Entry ..................................................................................................................43
6.2.5.1 Room Entry Form .......................................................................................................................43
6.2.5.2 Flat Entry Form ...........................................................................................................................44
6.2.5.3 Shop Entry Form ........................................................................................................................45
6.2.6 Employee Detail .............................................................................................................................46
6.2.6.1 Employee Salary.........................................................................................................................46
6.2.6.2 Employee Expenses Details ....................................................................................................47
6.2.7 Owner Detail....................................................................................................................................48
6.2.7.1 Owner Payment...........................................................................................................................48
6.2.7.2 Owner Expenses.........................................................................................................................49
6.2.8 Search Section ...............................................................................................................................50
6.2.8.1 Client Search ...............................................................................................................................50
6.2.8.2 Room Search...............................................................................................................................51
6.2.8.3 Rent of Client Search ................................................................................................................52
6.2.8.4 Shop Detail Search ....................................................................................................................53
6.2.8.5 Leaving Detail Search ...............................................................................................................54
6.2.9 Over All Reports of Dir Maidan Palace.....................................................................................55
6.3 ALERTS ...................................................................................................... 56
6.3.1 Delete Alert......................................................................................................................................56
6.3.2 Exit Alert ..........................................................................................................................................56

X
CHAPTER 7 REPORTS ...................................................................................57
7.1 REPORTS....................................................................................................58
7.2 CLIENT REPORT ........................................................................................58
7.3 FLAT REPORT ............................................................................................59
7.4 MONTHLY RENT REPORT.........................................................................60
7.5 EXPENSES REPORT..................................................................................61
7.6 EMPLOYEE SALARY REPORT..................................................................62
7.7 OWNER PAYMENT REPORT .....................................................................63
7.8 SHOP RESERVATION REPORT ................................................................64
7.9 FLAT RESERVATION REPORT .................................................................65
7.10 EMPTY FLATS REPORT ..........................................................................66
7.11 EMPTY SHOPS REPORT .........................................................................67
7.12 EMPTY ROOMS REPORT ........................................................................68
CHAPTER 8 TESTING AND IMPLEMENTATION ...........................................69
 Testing................................................................................................................................................69
 Testing Strategies ..............................................................................................................................69
 Implementation .................................................................................................................................69
8.1 TESTING......................................................................................................70
8.1.1 To Improve Quality ........................................................................................................................71
8.1.2 For Verification And Validation (V&V) ......................................................................................71
8.1.3 For Reliability Estimation ............................................................................................................72

XI
8.2 TESTING STRATEGIES ............................................................................. 73
8.2.1 Black-box Testing..........................................................................................................................73
8.2.2 White-box Testing .....................................................................................................................73
8.2.3 Performance Testing................................................................................................................74
8.2.4 Reliability Testing......................................................................................................................74
8.2.5 Security Testing.........................................................................................................................75
8.3 IMPLEMENTATION..................................................................................... 75
CHAPTER 9 CONCLUSIONS AND FUTURE DIRECTIONS ……………….. 76
 All Conclusions and Problems of the Project .................................................................................76
 Future Direction and Suggestions....................................................................................................76
9.1 INTRODUCTION ......................................................................................... 77
9.2 CONCLUSION............................................................................................. 77
9.3 FUTURE DIRECTIONS ............................................................................... 78
9.3.1 Implementation...............................................................................................................................78
9.3.2 Future Incrementation..................................................................................................................78

Chapter 1 Introduction
OLTP System for Dir Maidan Palace Page 1
CHAPTER 1
INTRODUCTION
 Project Introduction
 Project at a Glance

1.1 Project Introduction
This project is to develop an information management system for Dir Miadan Palace, in
which the rooms, shops and flats are given to clients for rent. And information about
clients is gathered which is in the interest of the organization and then stored in the
system.
The major parts of the project are:
To develop a database which keeps all the information regarding clients, employees,
expanses, owners, booking, rent, shops, flats and rooms etc
To develop a user-friendly interface to store, manipulate and retrieve data to and from the
database.
Generate detailed reports of Clients, Owners, Employees, Flats, Rooms, Shops, Owner
Payment, Rent, Flat Reservation, Room Reservation and Shop Reservation.
1.2 Project at a Glance
Project Name: OLTP System for Dir Maidan Palace
Description: Implementation of Database at Dir Maidan Palace
Organization: Dir Maidan Palace
Components: A database, User Interface, Reports
DBMS Used: Oracle 10g Enterprise Edition, SQL Developer
Front-end Tool: Oracle Developer 10g
Reports: Oracle Reports 10g

1.2.1 The Organization
Dir Maidan Palace is a residential building associated in Gul Berg#1 Saddar, Peshawar
which consists of shops, rooms and flats. Rooms and shops are for individual person and
flats are for families. The building is the property of two partners sharing the monthly
profit. The building has a staff of employees. Manager manages all the accounts and
clients information.
The clients have to register themselves by booking shop, room or flat along with
submitting appropriate refundable security fee to the manager. The client pays monthly
rent and bills.
The manger collects the securities and per month rents as the total income.
The building has two owners. The profit is divided as the share of each owner.
The building has many types of expanses such as income tax and property tax per year,
amount in the management of the building, bills of the unallocated rooms, refunded
securities and employee salaries etc which is paid by the manager from the income of the
building in that particular month.
1.2.2 DBMS Used
Oracle 10g Enterprise edition is used as Database Management System to develop this
project.
In today’s businesses, nearly all data is stored in some type of database and Oracle is
considered is the best one for any of large database system. Oracle is considered to be the
server of choice of many of them. With its built-in data replication capabilities, large data
storage and internet access, Oracle is an excellent choice for most enterprises.

1.2.3 Front End Tool
For Front-end interface development Oracle Developer Suite is used in this project.
Oracle Developer Suite is the most complete and Integrated Development Environment
(IDE). This IDE allows the programmer to create, run and debug high quality programs
involving Web Services. This IDE allows a programmer to create working programs in
short time that it would take a lot of time to code such programs without using IDE. The
languages used by Oracle Developer are SQL (Structure Query Language) and PLSQL
(Procedural Language), providing powerful features such as graphical user interface,
error handling, object oriented features, event handling, structured programming and
much more.
1.2.4 Reports
Oracle Reports 10g is used to create output reports in this project. It is a part of Oracle
Developer Suite. Oracle Reports has the capacity to handle larger data sets much more
quickly. Oracle Reports is a high fidelity enterprise reporting tool that enables to give
immediate access to information to all levels within and outside of the organization in a
scalable and secure environment. Enhancements to calculations for formulas and
summaries provide faster processing of records returned from the database. Formulas can
be created in a very easy way. The report designer interface offers much better control
over the positioning of reports objects with the ability to align, move, resize, copy and
paste multiple objects and new alignment and ruler options.
File export is provided for better preservation of formatting, which support the following
formats
RTF (Rich Text Format)
PDF (Portable Document Format)
HTML (Hyper Text Markup Language)
XML (Extensible Markup Language)
Microsoft Excel

Chapter 2: The Proposed System
CHAPTER 2
THE PROPOSED SYSTEM
 The Present System
 Objectives of the Proposed System
 Features of the Proposed System

2.1 The Present System
The present system for the management of Dir Maidan Palace is a file approach
managed by the manger, which is simple but has the following drawbacks:
The records are not safe which can be accessed by unauthorized person and can
be easily modified.
The search for the previous records is not efficient.
More calculations are involved and there is more risk of errors.
There is redundancy of records.
Reports generated via the present system are faulty, Untimely and improper.
2.2 Introduction to the Proposed System
As computer is one of the leading technologies today, so we proposed a computer based
system which full-fills the requirements of the Dir Maidan Palace easily. The proposed
system computerizes the present manual system to minimize the drawbacks of the
current system.

2.3 Objectives of the Proposed System
The proposed system suggests software which has a database for the records storage and
a user friendly interface for the data entries. Before designing any computer based
system, it is necessary to establish the objectives that proposed system should satisfy.
The proposed system has the following benefits which minimized the drawbacks of the
present system:
The proposed system will be more efficient and useful than the existing system.
The interface of the proposed system will restrict the unauthorized user to access
the data.
The search in proposed system will be fast and much efficient.
The data redundancy in proposed system will be eliminated.
The proposed system will saves a lot of time for data access, calculations and
report generation.
The system should be flexible enough to cope with the future requirements.
The Performance of the proposed system will not be slow.
The new system should have capacity to store and manipulate data entered to it.
The new system will be error free and provide accurate information.
The new system will be simple so that its structure, operation and procedure
should be maintained easily.

2.4 Features of the Proposed System
Following are the features of the proposed system.
To develop a user friendly system
To make simple the process of data entry, data manipulation and retrieval
To remove the possibility of data redundancy
To generate error free reports
2.4.1 Database Design
A database is designed, keeping in mind that no data redundancy may occur. The
database stores different types of information in different tables that are related to each
other using foreign keys.
2.4.2 User Interface
For better user interaction whether operator or executive, the interactive input screens is
well designed. They would make data entry simple and easy for the user and data will be
accepted in the same manner as it is done manually but in a much attractive and secure
way.
2.4.3 Simple to Use
The software requires no special training for its operation because it is user friendly and
communication with user in simple English and in simple symbolic representations. Thus
any person who has some knowledge of computer and English language can use it.

2.4.4 Data Validation
Various checks are implemented before data entry in the database to ensure data validity
and integrity of the database. All fields are checked for valid range of values and error
messages are generated accordingly.
2.4.5 Quick Search
The software provides a fast searching mechanism, which saves time and returns
accurate results.
This software provides various types of searching techniques through which the user can
find a specific record more easily.
2.4.6 Storage of Data
The software can store as much data as computer memory allows. The more the
computer memory increases, the more the data can be stored.
2.4.7 Reports Generation
The major purpose of establishing a database is to retrieve information quickly and
efficiently.
The proposed system will generate reports, which will be helpful to the client and top
management for decision making.

Chapter 3: Data Modeling
CHAPTER 3
DATA MODELING
 Data Modeling
 Entity Relationship Model
 Entity Relationship Modeling
 Entity Relationship Diagram

3.1 Introduction
Main purpose of data modeling is to assist the understanding of the meaning of the data
and to facilitate communication about the information requirements, Building a data
model requires answering questions about entities, relationship and attributes. We model
data to ensure that we understand each user’s perspective of data. The nature of data
itself is independent of its physical representation
3.2 Data Model
A data model is a representation of reality. It’s used to define the storage and
manipulation of a data base.
3.3 Entity Relationship Model
The entity–relationship (E-R) model is a detailed, logical representation of the data for an
organization or for a business area. It is based on a perception of a real world that
consists of a collection of basic objects called entities, and of relationships (or
associations) among those entities, and the attributes (or properties) of both the entities
and their relationships.
3.4 Entity Relationship Modeling(ERM)
A technique used to analyze and model the data in an organization using an
Entity Relationship (E-R) diagram. ER Modeling is a top-down approach to data base
design that begins by identifying the important data called entities and relationship
between the data that must be represented in the model. We then add more details such as
the information we want to hold about the entities and relationships called attributes and
any constraints on the entities relationships and attributes.

3.4.1 Entity
An entity is a person, place, object, event, or concept in the user environment about
which the organization wish to maintain the data. Entities are represented by labeled
rectangles.
3.4.2 Attributes
An attribute is a property or characteristics of an entity or relationship that is of interest
to the organization. Attribute may be associated with relationship. Attributes are
properties used to describe an entity. Attributes are represented by ellipse symbol.
3.4.3 Relationship
Relationships are meaningful associations among entity types. Relationship is an
association between two or more entities that is of particular interest. A relationship is an
object that associates entities. A relationship connects two or more entity sets.
A relationship instance is an association among entity instances. The degree of the
relationship is the number of entity types that participate in the relationship.
Relationships are indicated with labeled line connection entities. In some variations of
ERD relationships are represented by special diamond symbol.

3.5 Identified Entities and their Attributes
Entities and their attributes are the following
3.5.1 CLIENT
Information of client along with its attributes is shown in figure 3.1
Figure 3.1: Client and their attributes
3.5.2 FLAT
Information of flat along with its attributes is shown in figure 3.2
Figure 3.2: Flat with attributes
CLIENT
Phone_No
NIC
C_ID
Name
Father_NameAddress
FLAT
Flat_ID
Flat_No
Floor Flat_Status
No_of_Rooms
No_of_Kitchens
Occupation

3.5.3 SHOP
Information of shop along with its attributes is shown in figure 3.3
Figure 3.3: Shop and their attributes
3.5.4 ROOM
Information of room along with its attributes is shown in figure 3.4
Figure 3.4: Room and their attributes
SHOP
Shop_No Shop_StatusShop_ID
ROOM
Room_ID
Room_No Room_Status Floor
Number_Of_Seats

3.5.5 RESERVATION
Information of reservation along with its attributes is shown in figure 3.5
Figure 3.5: Reservation and their attributes
3.5.6 EMPLOYEE
Information of employee along with its attributes is shown in figure 3.6
Figure 3.6: Employee and their attributes
RESERVATION
Booking_ID
Security Res_Status
Reservation_Date
EMPLOYEE
Employee_ID
NameAddressJob_Title
Emp_ID
NIC
Emp_ID
Phone_Number
Salary

3.5.7 EMP_SAL_DETAIL
Information of emp_sal_detail along with its attributes is shown in figure 3.7
Figure 3.7: Emp_Sal_Detail and their attributes
3.5.8 PAYMENT
Information of payment along with its attributes is shown in figure 3.8
Figure 3.8: Payment and their attributes
PAYMENT
Received_ID Received_TypeAmount Received_Date
Payment_Month
EMP_SAL_DETAIL
Amount_Taken
Sal_Date
Sal_Transaction_ID
Sal_Month

3.5.9 OWNER
Information of owner along with its attributes is shown in figure 3.9
Figure 3.9: Owner and their attributes
3.5.10 EXPENSES
Information of expenses along with its attributes is shown in figure 3.10
Figure 3.10: Expenses and their attributes
OWNER
Owner_IDNICName
EXPENSES
Exp_ID
Exp_Type
Exp_Date
Amount
Phone_No
Address

3.5.11 RENT
Information of rent along with its attributes is shown in figure 3.11
Figure 3.11: Rent and their attributes
3.5.12 LEAVING
Information of leaving along with its attributes is shown in figure 3.12
Figure 3.12: Leaving and their attributes
RENT
AmountRent_Type
Rent_ID
Rent_Month
Rent_Date
Remaining_Balance
LEAVING
Leaving_ID Security_ReturnedLeaving_Date

3.6 Entity Relationship Diagram (ERD)
An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an
information system. Entity Relationship Diagrams (ERDs) illustrate the logical structure
of databases.
3.6.1 Identified Entity Relationship Diagram (ERD)
Identified ERD is shown in figure 3.13
Figure 3.13 Complete Entity Relationship Diagram of Dir Maidan Palace
CLIENT
C_ID: INTEGER
Name: VARCHAR(20)
Address: VARCHAR(40)
Father_Name: VARCHAR(20)
NIC: VARCHAR(15)
Phone_No: NUMBER(11)
Occupation: VARCHAR(20)
FLAT
Flat_ID: VARCHAR(20)
Flat_No: VARCHAR(20)
Floor: VARCHAR(20)
Flat_Status: VARCHAR(20)
No_of_Rooms: INTEGER
No_of_Kitchens: INTEGER
ROOM
Room_ID: VARCHAR(20)
Room_No: VARCHAR(20)
Room_Status: VARCHAR(20)
No_Of_Seats: INTEGER
Floor: VARCHAR(20)
SHOP
Shop_ID: VARCHAR(20)
Shop_No: VARCHAR(20)
Shop_Status: VARCHAR(20)
RESERVATION
Booking_ID: VARCHAR(20)
Room_ID: VARCHAR(20) (FK)
Flat_ID: VARCHAR(20) (FK)
Shop_ID: VARCHAR(20) (FK)
Leaving_ID: VARCHAR(20) (FK)
C_ID: VARCHAR(20) (FK)
Security: INTEGER
Reservation_Date: DATE
Res_Status: VARCHAR(20)RENT
Rent_ID: INTEGER
C_ID: INTEGER (FK)
Amount: INTEGER
Remaining_Balance: INTEGER
Rent_Month: DATE
Rent_Type: VARCHAR(20)
Rent_Date: DATE
OWNER
Owner_ID: VARCHAR(20)
Name: VARCHAR(20)
NIC: VARCHAR(15)
Phone_No: NUMBER
PAYMENT
Received_ID: INTEGER
Owner_ID: VARCHAR(20) (FK)
Amount: INTEGER
Received_Date: DATE
Received_Type: VARCHAR(20)
Payment_Month: DATE
EXPENSES
Exp_ID: VARCHAR(20)
Owner_ID: VARCHAR(20) (FK)
Employee_ID: VARCHAR(20) (FK)
Booking_ID: VARCHAR(20) (FK)
Room_ID: VARCHAR(20) (FK)
Flat_ID: VARCHAR(20) (FK)
Shop_ID: VARCHAR(20) (FK)
Leaving_ID: VARCHAR(20) (FK)
C_ID: VARCHAR(20) (FK)
Exp_DATE: DATE
Amount: VARCHAR(20)
Exp_Type: VARCHAR(20)
EMPLOYEE
Employee_ID: VARCHAR(20)
Name: VARCHAR(20)
Job_Title: VARCHAR(20)
Phone_Number: INTEGER
Salary: INTEGER
NIC: VARCHAR(20)
LEAVING
Leaving_ID: VARCHAR(20)
Leaving_Date: DATE
Security_Returned: INTEGER
EMP_SAL_DETAIL
Sal_Transaction_ID: INTEGER
Employee_ID: VARCHAR(20) (FK)
Amount_Taken: INTEGER
Sal_Date: DATE
Sal_Month: DATE

Chapter 4: Data Dictionary
CHAPTER 4
DATA DICTIONARY
 Description

4.1 Description
Description of all the entities and their attributes are described below
CLIENT
Attributes, data types and description of Client is shown in table 4.1
Entity Name: Client
Description: Represents the client which is the main entity of the whole system and his
Identification to the system.
Attribute Name Data Type Description Null
C_ID Number Unique ID of a client i.e Primary key of client No
Name Varchar(20) Name of the client No
Father_Name Varchar(20) Father name of the client Yes
NIC Varchar(15) NIC of the client Yes
Address Varchar(40) Home address of the client No
Phone_No Number(11) Phone number of the client Yes
Occupation Varchar(20) Work description of the client Yes
Table 4.1: Description of Client

FLAT
Attributes, data types and description of Flat is shown in table 4.2
Entity Name: Flat
Description: Represents the complete details of the flat.
Flat_ID Varchar(20) Unique ID of a flat i.e Primary key of flat No
Flat_No Varchar(20) Every flat is numbered in dirmaidan palace No
Floor Varchar(20) The specific flat is in which floor Yes
Flat_Status Varchar(20) The specific flat is empty or occupied No
No_of_Rooms Number Total number of rooms in a specific flat Yes
No_of_Kitchens Number Total number of kitchens in a specific flat Yes
Table 4.2: Description of Flat
SHOP
Attributes, data types and description of Shop is shown in table 4.3
Entity Name: Shop
Description: Represent the whole details of the shops.
Shop_ID Varchar(20) Unique ID of a shop i.e Primary key of shop No
Shop_No Varchar(20) Every shop is numbered in dirmaidan plaza No
Shop_Status Varchar(20) The specific shop is empty or occupied No
Table 4.3: Description of Shop

ROOM
Attributes, data types and description of Room is shown in table 4.4
Entity Name: Room
Description: Represents the room details.
Room_ID Varchar(20) Unique ID of a room. i.e Primary key of room No
Room_No Varchar(20) Every room is numbered in dirmaidan palace No
Room_Status Varchar(20) The specific room is empty or occupied No
Floor Varchar(20) The specific room is in which floor No
No_Of_Seats Number Number of available seats in a room Yes
Table 4.4: Description of Room

RESERVATION
Attributes, data types and description of Reservation is shown in table 4.5
Entity Name: Reservation
Description: Represents the Reservation. Which room, flat or shop is reserved by which
Client and on which date and by how many amount.
Booking_ID Varchar(20) Unique ID of reservation i.e Primary key of reservation No
Reservation_Date Date Date of reservation No
Reservation_Status Varchar(20) Room, shop or flat is reserved or leaved by client Yes
Security Number How many amount has taken from the client as security Yes
C_ID Varchar(20) Represents which client has done reservation No
Room_ID Varchar(20) Represents which room is reserved Yes
Flat_ID Varchar(20) Represents which flat is reserved Yes
Shop_ID Varchar(20) Represents which shop is reserved Yes
Leaving_ID Varchar(20) Represents which client has left the palace Yes
Table 4.5: Description of Reservation

EMPLOYEE
Attributes, data types and description of Employee is shown in table 4.6
Entity Name: Employee
Description: Represents all the details of Employee.
Employee_ID Varchar(20) Unique ID of employee. i.e primary key of
employee
No
NIC Varchar(20) NIC of employee No
Name Varchar(20) Name of employee No
Address Varchar(40) Address of employee Yes
Job_Title Varchar(20) Job title of employee Yes
Phone_Number Number Phone number of employee Yes
Salary Number Salary of employee No
Table 4.6: Description of Employee
EMP_SAL_DETAIL
Attributes, data types and description of emp_sal_detail is shown in table 4.7
Entity Name: Emp_sal_detail
Description: Represents all salary transactions of employees.
Sal_Transaction_ID Number Unique ID of emp_sal_detail. i.e Primary key No
Amount_Taken Number How many amount (salary) is taken by an
employee
No
Sal_Month Date Represents month of the salary No
Sal_Date Date On which date the salary is taken No
Employee_ID Varchar(20) Represents the employee who has taken the salary No
Table 4.7: Description of Emp_Sal_Detail

PAYMENT
Attributes, data types and description of Payment is shown in table 4.8
Entity Name: Payment
Description: Represents payment which is done to owner and all details of payment.
Received_ID Number Unique ID of payment. i.e primary key of
payment
No
Amount Number How many amount is received No
Received_Type Varchar(20) Amount reception type Yes
Received_Date Date Date of reception No
Payment_Month Date Represents payment of month No
Owner_ID Varchar(20) Represents the owner No
Table 4.8: Description of Payment
OWNER
Attributes, data types and description of Owner is shown in table 4.9
Entity Name: Owner
Description: Represents the Owner.
Owner_ID Varchar(20) Unique ID of owner i.e Primary key of owner No
NIC Varchar(15) NIC of owner No
Name Varchar(20) Name of owner No
Address Varchar(40) Represents address of the owner Yes
Phone_No Number Represents phone number of the owner Yes
Table 4.9: Description of Owner

EXPENSES
Attributes, data types and description of Expenses is shown in table 4.10
Entity Name: Expenses
Description: Represent all types of expenses.
Exp_ID Varchar(20) Unique ID of Expenses i.e Primary key of
expenses
No
Amount Varchar(20) How many amount spent No
Exp_Type Varchar(20) The type of expense Yes
Exp_Date Date Date on which a specific amount is spent No
Booking_ID Varchar(20) Represents all details of reservation Yes
Emp_ID Varchar(20) Represent employee who has done expanses Yes
Owner_ID Varchar(20) Represent owner which is responsible for
expanses
Yes
Table 4.10: Description of Expenses

RENT
Attributes, data types and description of Expenses is shown in table 4.11
Entity Name: Rent
Description: Represents all the details of rent. The rent is taken from the clients after
specific time from some clients it is taken monthly and from some clients it is taken yearly.
Rent_ID Number Unique ID of rent i.e Primary key of rent No
Amount Number How many rent has submitted No
Remaining_Balance Number Represents remaining amount to a client No
Rent_Type Varchar(20) Type of rent Yes
Rent_Month Date Show month of rent No
Rent_Date Date Date on which rent is submitted No
C_ID Number Represent the client who has submitted the rent No
Table 4.11: Description of Rent
LEAVING
Attributes, data types and description of leaving is shown in table 4.12
Entity Name: Leaving
Description: Represents the Leaving details of a client.
Leaving_ID Varchar(20) Unique ID of Leaving i.e Primary key of Leaving No
Leaving_Date Date Date on which a client has left the palace No
Security_Returned Number Represents the returned security to the client No
Table 4.12: Description of Leaving

Chapter 5: Normalization
CHAPTER 5
NORMALIZATION
 Normalization
 Main Goals of Normalization
 Normalization Avoids
 Steps in Normalization

5.1 Introduction
The process of decomposing relations with anomalies to produce smaller and well-
structured Relations.
5.2 Main Goals of Normalization
Main goals of Normalization are as:
◦ Minimize data redundancy
◦ Simplify the enforcement of referential integrity constraints
◦ Make it easier to maintain data (insert, update, and delete)
◦ It is a process of efficiently organizing data in a database
◦ Normal Form reduces the amount of space a database consumes.
5.3 Normalization Avoids
◦ Duplication of Data – The same data is listed in multiple lines of the database
◦ Insert Anomaly – A record about an entity cannot be inserted into the table
without first inserting information about another entity
◦ Delete Anomaly – A record cannot be deleted without deleting a record about a
related entity. Cannot delete a reservation record without deleting all of the client
information.
◦ Update Anomaly – Cannot update information without changing information in
many places.

5.4 STEPS IN NORMALIZATION
Normalization can be accomplished and understood in stages, each of which corresponds
to a normal form.
5.4.1 Normal Form
A state of a relation that results from applying simple rules regarding functional
dependencies (or relationships between attributes) to that relation.
There are different normal forms
5.4.1.1 First Normal Form: (Any multi valued attributes have been removed)
5.4.1.2 Second Normal Form: (having no partial functional dependencies)
5.4.1.3 Third Normal: (Any transitive dependencies have been removed)
5.4.1.4 Boyce-Codd Normal Form: (Any remaining anomalies that result from
functional dependencies have been removed).
5.4.1.5 Fourth Normal Form: (Multi-valued Dependencies have been removed).
5.4.1.6 Fifth Normal Form: (Any remaining anomalies have been removed)

Figure 5.1: Normal forms in Normalization

5.5 Normalization in OLTP System for Dir Maidan Palace
There is one large table for storing complete transactions of the whole system.
Table 3.1: All transactions of a client
5.5.1 CLIENT_TRANSACTION
As the Client_Transaction table shows that the attributes of Client_Transaction should be
repeated for each instance. So this table is decomposed into six small tables.
i) CLIENT
ii) RENT
iii) RESERVATION
iv) FLAT
v) SHOP
vi) ROOM
Transaction_ID Client_Name Client_Address Client_NIC Booking_Type Floor Security Rent T_Date
B123 Ahmad Mardan 16101-
0423676-3
Flat 1st
30000 9000 9/19/2013

Now the decomposed tables show that every instance is uniquely identified and there is
no chance of repeating rows.
5.5.1.1 CLIENT:
C_ID Name Address Phone_No Occupation Father_Name NIC
5.5.1.2 RESERVATION:
Booking_ID Flat_ID Shop_ID Room_ID Security Booking_Date Reservation_Type C_ID
5.5.1.3 FLAT:
Flat_ID Flat_No No_of_Rooms No_of_Kitchens Flat_Status
5.5.1.4 ROOM:
Room_ID Room_No Room_Status No_of_Seats
5.5.1.5 SHOP:
Shop_ID Shop_No Shop_Status
5.5.1.6 RENT:
Rent_ID C_ID Amount Rent_Type Rent_Month Rent_Date Remaining_Balance

Chapter 6: Interface Design
CHAPTER 6
INTERFACE DESIGN
 Interface Design Introduction
 Snapshots of the Forms

6.1 Introduction
The interface design describes how the software communicates with system that inter-
operates with it and with user who use it. An interface implies a flow of information and
a specific type of behavior.
The interface design creates an effective communication medium between a human and a
computer, following is a set of design principle. The design identifies interface objects,
actions and then creates screen layout that forms the basis for a user interface prototype.
After the logical design phase, Interface Design is performed.
6.2 Snapshots of The Forms
Snapshots of the user interface forms of Dir Maidan palace are shown on the
subsequent pages

6.2.1 Login Page
Login page is the first page which appears when we run the application through which
we can enter to database.
The login page accepts the user name and password so that only authorized user can
login to the program for data entry, updating and modification.
Figure 6.1: Login Page

6.2.2 Main Page
When user login to the system the main page appears in which there are three main
sections Entry section, Search section and Reports section.
Figure 6.2: Main Page

6.2.3 Entry Section
In Entry section user can enter the actual data to the database in which entity represent a
specific form according to the organizational need. In entry section there are different
modules used which are explained on subsequent pages.
Figure 6.3: Entry Section

6.2.4 Client Reservation
One of the most important Form in the entry section is client in which the new client will
be registered through this form and all the related information of the client will be stored
in the data base through this Form.
Figure 6.4: Client Reservation

6.2.4.1 Rent Form
In this form all of the rent information submitted by a client is stored.
Figure 6.5: Rent Form

6.2.4.2 Leaving Form
In Leaving Form all of those client records are stored who have left Dir Maidan Palace
after reservation.
Figure 6.6: Leaving Form

6.2.5 Property Details Entry
In Entry Section when the Property Details button is clicked then it leads the user to
Room, Flat and Shop details which is the main entities in Dir maidan palace. If on the
room entry button is clicked the user will lead to room form.
6.2.5.1 Room Entry Form
In this form all of the room’s information is entered and stored.
Figure 6.7: Room Entry Form

6.2.5.2 Flat Entry Form
When the Flat button is pressed by the user, It leads the user to the Flat form in which
user can enter all the details related to the flat and stored.
Figure 6.8: Flat Entry Form

6.2.5.3 Shop Entry Form
When the shop button is pressed by the user, it leads the user to the shop form in which
the details of shops are stored.
Figure 6.9 Shop Entry Form

6.2.6 Employee Detail
In the entry section when the user press the employee Details button. It leads user to the
employee Form, where user can easily add new record of employees and also the salary
given to employees per month will also be entered here.
6.2.6.1 Employee Salary Form
In this form all of the salary information received by a specific employee is stored.
Figure 6.10: Employee Salary Form

6.2.6.2 Employee Expenses Details
In this form all of those expenses details are stored which a specific employee has done.
Figure 6.11 Employee Expenses Details

6.2.7 Owner Detail
In Entry Section when the user press the Owner Details button, then it leads the user to
the owner form in which all of the owner information is stored.
6.2.7.1 Owner Payment
In this form the income details received by the owners are stored.
Figure 6.12: Owner Payment Information

6.2.7.2 Owner Expenses
In this form all of those expenses details are stored which a specific owner has done.
Figure 6.13: Owner Expenses Information

6.2.8 Search Section
Searching is one of the most important and widely used technique in any software. By
using search option user can easily find his desired object from large number of data. We
have put the search criteria in separate section.
6.2.8.1 Client Search
In the Client Search form we can search a client by name and by address.
Figure 6.14: Client Search Section

6.2.8.2 Room Search
In room search form we can search a room by room number and by name of the client
reserved the room.
Figure 6.15 Room Search Section

6.2.8.3 Rent of Client Search
In Rent of Client search form we can search by Client ID and by Rent ID of the client.
Figure 6.16: Rent of Client Search Section

6.2.8.4 Shop Detail Search
In Shop Detail Search form we can search by shop number.
Figure 6.17: Shop Detail Search Section

6.2.8.5 Leaving Detail Search
In leaving detail search form the details of all clients are displayed who has left
Dir Maidan Palace.
Figure 6.18: Leaving Detail Search Section

6.2.9 Over All Reports of Dir Maidan Palace
This form is used to display all reports of the system.
Figure 6.19: Over All Reports Form

6.3 Alerts
In any software alerts play a vital role. With any sensitive action, we have used alerts to
confirm whether user really want to perform such sensitive action or not. Also alerts are
used when user try to enter wrong data in mistake.
Following are useful alerts that we have used in this project:
6.3.1 Delete Alert
This alert in Figure 6.20 is shown when user press delete button to perform any deletion.
Figure 6.20: Delete Alert
6.3.2 Exit Alert
This alert in Figure 6.21 is shown when user press Exit button.
Figure 6.21: Exit Alert

Chapter 7: Reports
CHAPTER 7
REPORTS
 Reports of the whole system

Chapter 7: Reports
7.1 Reports
Forms are only used for data manipulation purpose. It is used to store records in a
database. But in order to show records of some entity we use Reports.
We have built the reports by using “Oracle Reports Builder 10g”.
Reports are designed in every project according to the need of an organization for which
the software is built. In a database, data is entered through the forms and then we
generate several reports on the basis of these data.
Reports are actually the search of information stored in a database.
7.2 Client Report
This report shows the client’s information.
Figure 7.1: Client Report

Chapter 7: Reports
7.3 Flat Report
This report shows the flat’s information.
Figure 7.2: Flat Report

Chapter 7: Reports
7.4 Monthly Rent Report
This report shows rent information by taking two dates from the user usually used for a
month.
Figure 7.3: Monthly Rent Report

Chapter 7: Reports
7.5 Expenses Report
This report shows all of the expenses information.
Figure 7.4: Expenses Report

Chapter 7: Reports
7.6 Employee Salary Report
This report shows all of the employee’s salaries which employee has taken.
Figure 7.5: Employee Salary Report

Chapter 7: Reports
7.7 Owner Payment Report
This report shows all of the payment taken by the owner.
Figure 7.6: Owner Payment Report

Chapter 7: Reports
7.8 Shop Reservation Report
This report shows all of the reserved shops.
Figure 7.7: Shop Reservation Report

Chapter 7: Reports
7.9 Flat Reservation Report
This report shows all of the reserved flats.
Figure 7.8: Flat Reservation Report

Chapter 7: Reports
7.10 Empty Flats Report
This report shows all of the empty flats in Dir Maidan Palace.
Figure 7.9: Empty Flats Report

Chapter 7: Reports
7.11 Empty Shops Report
This report shows all of the empty shops in Dir Maidan Palace.
Figure 7.10: Empty Shops Report

Chapter 7: Reports
7.12 Empty Rooms Report
This report shows all of the empty rooms in Dir Maidan Palace.
Figure 7.11: Empty Rooms Report

Chapter 7: Reports
CHAPTER 8
TESTING AND IMPLEMENTATION
 Testing
 Testing Strategies
 Implementation

Chapter 7: Reports
8.1 Testing
Software Testing is the process of executing a program or system with the intent of
finding errors. Or, it involves any activity aimed at evaluating an attribute or capability
of a program or system and determining that it meets its required results. Software testing
is an investigation conducted to provide stakeholders with information about the quality
of the product or service under test. Software testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the
risks of software implementation. Test techniques include, but are not limited to, the
process of executing a program or application with the intent of finding software bugs
(errors or other defects).
Software testing can also be stated as the process of validating and verifying that a
software program/application/product:
1. Meets the business and technical requirements that guided its design and
development
2. Works as expected
3. Can be implemented with the same characteristics
Testing is an integral part in software development. It is broadly deployed in every phase
in the software development cycle. Typically, more than 50% percent of the development
time is spent in testing. Testing is usually performed for the following purposes:

Chapter 7: Reports
8.1.1 To Improve Quality
Quality means the conformance to the specified design requirement. Being correct, the
minimum requirement of quality, means performing as required under specified
circumstances. Debugging, a narrow view of software testing, is performed heavily to
find out design defects by the programmer. The imperfection of human nature makes it
almost impossible to make a moderately complex program correct the first time. Finding
the problems and get them fixed, is the purpose of debugging in programming phase.
8.1.2 For Verification And Validation (V&V)
Just as topic Verification and Validation indicated, another important purpose of testing
is verification and validation (V&V). Testing can serve as metrics. It is heavily used as a
tool in the V&V process. Testers can make claims based on interpretations of the testing
results, which either the product works under certain situations, or it does not work. We
can also compare the quality among different products under the same specification,
based on results from the same test. We cannot test quality directly, but we can test
related factors to make quality visible. Quality has three sets of factors -- functionality,
engineering, and adaptability.

Chapter 7: Reports
8.1.3 For Reliability Estimation
Software reliability has important relations with many aspects of software, including the
structure, and the amount of testing it has been subjected to. Based on an operational
profile (an estimate of the relative frequency of use of various inputs to the program),
testing can serve as a statistical sampling method to gain failure data for reliability
estimation.
Software testing is not mature. It still remains an art, because we still cannot make it a
science. We are still using the same testing techniques invented 20-30 years ago, some of
which are crafted methods or heuristics rather than good engineering methods. Software
testing can be costly, but not testing software is even more expensive, especially in
places that human lives are at stake. Solving the software-testing problem is no easier
than solving the Turing halting problem. We can never be sure that a piece of software is
correct. We can never be sure that the specifications are correct. No verification system
can verify every correct program. We can never be certain that a verification system is
correct either.

Chapter 7: Reports
8.2 Testing Strategies
Following are the basic strategies that were used for testing of the software.
 Black-box testing
 White-box testing
 Performance testing
 Reliability testing
 Security testing
8.2.1 Black-box Testing
The black-box approach is a testing method in which test data are derived from the
specified functional requirements without regard to the final program structure. It is also
termed data-driven, input/output driven or requirements-based testing. Because only the
functionality of the software module is of concern, black-box testing also mainly refers
to functional testing.
A testing method emphasized on executing the functions and examination of their input
and output data. The tester treats the software under test as a black box. Only the inputs,
outputs and specification are visible, and the functionality is determined by observing the
outputs to corresponding inputs. In testing, various inputs are exercised and the outputs
are compared against specification to validate the correctness. All test cases are derived
from the specification. No implementation details of the code are considered.
8.2.2 White-box Testing
Contrary to black-box testing, software is viewed as a white-box, or glass-box in white-
box testing, as the structure and flow of the software under test are visible to the tester.
Testing plans are made according to the details of the software implementation, such as
programming language, logic, and styles. Test cases are derived from the program
structure. White-box testing is also called glass-box testing, logic-driven testing or
design-based testing.

Chapter 7: Reports
8.2.3 Performance Testing
Not all software systems have specifications on performance explicitly. But every system
will have implicit performance requirements. The software should not take infinite time
or infinite resource to execute. "Performance bugs" sometimes are used to refer to those
design problems in software that cause the system performance to degrade.
Performance has always been a great concern and a driving force of computer evolution.
Performance evaluation of a software system usually includes: resource usage,
throughput, and stimulus-response time and queue lengths detailing the average or
maximum number of tasks waiting to be serviced by selected resources. Typical
resources that need to be considered include network bandwidth requirements, CPU
cycles, disk space, disk access operations, and memory usage. The goal of performance
testing can be performance bottleneck identification, performance comparison and
evaluation, etc. The typical method of doing performance testing is using a benchmark --
a program, workload or trace designed to be representative of the typical system usage.
8.2.4 Reliability Testing
Software reliability refers to the probability of failure-free operation of a system. It is
related to many aspects of software, including the testing process. Directly estimating
software reliability by quantifying its related factors can be difficult. Testing is an
effective sampling method to measure software reliability. Therefore, based on the
estimation, the developers can decide whether to release the software, and the users can
decide whether to adopt and use the software. Robustness testing and stress testing are
variances of reliability testing based on this simple criterion. The robustness of a
software component is the degree to which it can function correctly in the presence of
exceptional inputs or stressful environmental conditions. Robustness testing differs with
correctness testing in the sense that the functional correctness of the software is not of
concern. It only watches for robustness problems such as machine crashes, process hangs
or abnormal termination. The Oracle is relatively simple therefore robustness testing can
be made more portable and scalable than correctness testing.

Chapter 7: Reports
8.2.5 Security Testing
Software quality, reliability and security are tightly coupled. Flaws in software can be
exploited by intruders to open security holes. With the development of the Internet,
software security problems are becoming even more severe.
Many critical software applications and services have integrated security measures
against malicious attacks. The purpose of security testing of these systems include
identifying and removing software flaws that may potentially lead to security violations,
and validating the effectiveness of security measures. Simulated security attacks can be
performed to find vulnerabilities.
8.3 Implementation
After successful testing, the system is installed on the user’s PC. The user starts entering
data into the system and start using the new system parallel with the existing system for a
month or two. Parallel running of old system with new system provides advantages of
checking new system’s results with existing system results. After using both the systems
in parallel, if no error is detected and results produced are according to the requirements
then all the previous data is transferred into the new system and existing system is totally
removed. If the user find some shortcomings in the system or he wants some additions or
changes in the system he note it down and then asked the developer and those
requirements are then fulfilled in the next updated version of the system.

Chapter 9: Conclusions and Future Direction
CHAPTER 9
CONCLUSIONS AND FUTURE DIRECTIONS
 All Conclusions and Problems of the Project
 Future Direction and Suggestions

9.1 Introduction
This chapter describes all the conclusions and problems of the project.
Furthermore it gives future directions which fulfill all the limitations of this project.
During this project, we met many problems but approximately all of them are
solved. The unsolved problems and their cure are given in this chapter. The main
parts of this chapter are “Conclusions” and “Future Directions”.
The following sections discuss them one by one.
9.2 Conclusion
Conclusion is something which summarizes the findings and gives the main
cause of arise problems. As our project is about OLTP database of Dir Maidan
Palace in which records are entered, retrieved, modified and stored offline we
have fully implemented this system for the organization.
We have implemented the whole system practically as well as theoretically. It is
designed according to the requirements of Dir Maidan Palace. All the relations,
integrity constraints and check are properly implemented and the chances of
errors are minimized.

9.3 Future Directions
This section describes the accommodation of changes which may be possible in future.
Changes like ‘data type change’ is easy to adopt because we have to just alter the table
containing the column of which we want to change data type.
Other changes like the addition of a new column can also be managed to an extent but it
may become difficult to handle if that new column has much more relations with other
tables or columns. This is further divided into two subsections which are:
9.3.1 Implementation
In the current Data Base System we have implemented three modules.
i. Client Module
The purpose of this module is to maintain client’s related information.
ii. Employee Module
The purpose of this module is to maintain information about the employee’s related
information.
iii. Property Detail Module
This module is created to store and maintain information about all the property details of
Dir Maidan Palace.
9.3.2 Future Incrementation
In the future, we are going to extend our project by adding new other modules to make
full enterprise resource modules for this organization and going to implement this on web
due to which clients will book their rooms, flats and shops online and give payment
through an online account and also clients will be able to pay their rent online.

REFERENCES
[1] http://www.ece.cmu.edu/~koopman/essays/abstract.html (15/03/2013)
[2] http://www.csc.lsu.edu/~chen/pdf/erd.pdf (Feb 2013 to Oct 2013)
[3] http://www.csc.lsu.edu/~chen/chen.html (20/11/2013)
[4] http://www.oracle.com/us/products/database/overview/index.html (25/11/2013)
[5] http://www.personal.psu.edu/glh10/ist110/topic/topic07/topic07_05.html(10/12/2013)
[6] Jeffrey A. Hoffer, Mary B. Prescott and Fred R. McFadden. Modern Database
Management Seventh Edition (Sep 2013 to Jan 2014)
[7] Roger S Pressman, 2006, 5th
Edition , Software Engineering A Practitioner’s
Approach, Person’s (Oct 2013 to Dec 2013)
[8] http://www.stackoverflow.com (April 2013 to Jan 2014)

Online Transaction Processing (OLTP) System for Dir Maidan Palace (Saeed BS project)

Recommended

Recommended

More Related Content

Similar to Online Transaction Processing (OLTP) System for Dir Maidan Palace (Saeed BS project)

Similar to Online Transaction Processing (OLTP) System for Dir Maidan Palace (Saeed BS project) (20)

More from Saeed Ullah

More from Saeed Ullah (9)

Recently uploaded

Recently uploaded (20)

Online Transaction Processing (OLTP) System for Dir Maidan Palace (Saeed BS project)