INTRODUCTION

A pizzeria specialized in custom made pizzas is currently taking orders

by phone. The current system where the customer calls the pizzeria
takes time of employees to answer the phone and is more work
consuming than necessary. They want to allow customers to customize
and order their pizzas online. The pizzeria also aims to increase the
sales, due to the easy to use order online website. The system will give
the employees more time to “work” rather then to accept orders by
phone, also the potential increase in customers are enough reason for the
pizzeria to accept the change (website where customers can order their
customized pizzas).

Goal
Our goal is to deliver a database with a user interface (website) where
customers can select various ingredients for their own pizza and place their
order. The order will be sent to the “kitchen” where the pizza will be
made. The focus is to create an “easy to use” website, which will allow a
first time customer to complete their order with ease.

Existing solutions
There are many different web based ordering systems. Those systems do
not offer all the functionality that is needed for a pizzeria. Ordering
systems usually allow people to add products and separate them in
different categories and subcategories. Pizzeria sells pizzas, and most of
them also offer clients to customize their own pizzas by picking their
own ingredients. At the same time they offer other products that do not
need customization like the side orders. That does not fit into the general
category-subcategory differentiation.

Our solution
Our solution is to make an ordering system that separates ordering pizzas
from ordering the side dishes (non-pizza products) in an intuitive way.
The ordering system provides the user with three tabs: one for
customizing pizzas, one for side orders, and one for delivery details.
Customers can switch to any tab any time. Hence the system will
decrease workload of the employees and benefit the pizzeria due to the
database / information system. Information will be stored in the system
and can be viewed at any time. The system will be able to guide a user
through the website and make then complete their pizza order. When
they are done with filling in all information regarding their order they
can complete the order to send it to the pizzeria.

Technical constraints

The constraints of this case are the network connectivity which is

required and a website located on the internet. Customers will have to be
able to customize their pizzas. However there is a limit to the
customization of the pizza, technical constraints, functions of the
database and user interface. The system should make use of open-source
software, since the pizzeria does not want an expensive system.
Ordering

The first use case is ordering. To order, a potential customer must first
know what he can choose from (“What’s on the menu?”). For ordering
custom pizzas a customer will have to know the ingredients he can
choose from and how choosing ingredients will influence the total price.
Customers pick ingredients for their pizza and sometimes they want a
double portion of specific ingredients. When a customer is done
choosing his pizza, he may want to order several pizzas of the same
configuration. A customer may also want to order non-pizza side orders,
such as drinks and salads. Also the customer will have to provide his
name, address and telephone number. A customer can also pick another
delivery date and time if they wish for the order to be delivered on a
later date and time. Customers can order up to two weeks in advance.

Order processing

When an order has been confirmed by a customer order processing

begins. Throughout the order processing the order status will be updated
and the customer will be notified. New orders will show up in a list for
the employees in the kitchen. They need to state which products are
ordered and which ingredients are chosen for the custom pizzas. The
kitchen employees have to look at the order and decide if they can
prepare the order or not. When the decision is made, the order status will
change and the customer will be notified. After preparing the order the
order status will be updated and the delivery employees will take over.
They will look up the name and address, and deliver the order. The
customer will also be notified when the order is prepared and ready to be
delivered. When delivery has been completed or failed, the order status
will be changed once more.

Administration

Custom pizzas are made by selecting several ingredients, the list of

available ingredients and their prices are administrated by an employee,
for instance the manager. Administration includes added, editing and
deleting ingredients. Besides the administration of ingredients, the non-
pizza side orders must also be administrated. Administrators also need to
have logs of previous orders.

1.3 System specification

Functionality specification

The functionality specification is closely related to the use cases. The

three main functions are ordering, order processing and administration.
A description of each of the functionality will follow. It includes the
output of the system and the input it expects from the users.
Ordering involves customizing pizzas, selecting products and entering
customer information. The system will have to provide the user with data
about the ingredients and the non-pizza products such as name and price.
Users will provide an order which consists of custom pizzas by selecting
ingredients, non-pizza products, and customer information like name,
address and telephone number. For every custom pizza and non-pizza
product users can also specify an amount if they wish to order more than
one of them.
Order processing is involved in preparing and delivering orders. The
system needs to provide the kitchen employees with a list of pending
orders. Of each order the ordered products and pizzas must be shown,
together with the amount of each product. For each custom pizza the
selected ingredients must also be shown. The kitchen employees will
first view the order and decide if they are going to process the order or
not. The decision will be entered by changing the status of the order to
the respective status. An e-mail will be sent to customer to keep him
informed of the ordering status. After the order is prepared, the order
will be passed to the delivery employees who will use the system to
retrieve the customer details.. The status of the order will change to
“being delivered” and an new e-mail will be sent to the customer. When
the order is delivered, the delivery employee can mark the order as
“delivered”, or in case he failed to deliver it he will make it as “failed to
deliver”.
Administration includes adding, editing and deleting available
ingredients, non-pizza products and employees and viewing previous
orders. The system will be able to show a list of ingredients and a list of
products. For each ingredient and non-pizza product a name, price and
picture can be specified. The system also needs a function to show
previous orders.

Technical specification

The system is made up of three layers. At the top there is the GUI
(Graphical User Interface) layer, the middle layer is the storage and query
manager, the bottom layer is the underlying database.

GUI layer

The GUI layer allows users to access the system. All the functionalities of
the system must be available through the GUI. There are two separate
GUI’s. One is for the customers to create orders and one is for employees
for processing orders and administration purposes. With scripts, user
input will be used to invoke queries from the storage and query manager
layer to provide the user with various pages. The GUI should prevent
input errors and in case of errors that could not be prevented, provide
clear error messages.
Nowadays people have usernames and passwords for a lot of websites
and services. It is not practical to have users to remember information
for a pizzeria. It is much easier for customers to type in their name and
address than to have to remember the username and password.
Therefore, customers do not have accounts to log on to. However
customer information will be stored into the system to allow employees
view previous orders by customers.
The GUI for employees is on a separate URL. Users need a username
and a password to gain access to the system. The administrator has
access to add users to the system to give them access.

Storage and query manager layer

The storage and query manager layer is responsible for information

storage, retrieval, authorizations and error checking. This layer allows
selecting, adding, updating, deleting entities and relations in the database
by using different queries. Some instructions are limited to users with
authorization, such as deleting data from the database which should only
be allowed by the administrator.

Database layer
The database layer contains all the data of entities and their relationships.

1.4 Requirements

This section describes different types of users of the system in 3.3.1. In

the following paragraph 3.3.2, the functional requirements for each type
of user are listed. 3.3.3 Lists the non-functional requirements of the
system.

Users

Three types of users should be able to use the system: customer,

employee and administrator. Customers are users who visit the website
and can create orders by customizing pizzas, selecting products and
entering customer details. Employees are the group of users that work
with the ordering system on a daily basis. Employees will have their own
accounts to log on to. They are the ones responsible for processing
orders. Since Customer users do not need a log in, employees who
process telephone orders can use the system as a Customer and enter the
telephone order directly into the system as they take the order from the
calling customer.
The administrator, or super user, has the ultimate control of the system, he
can add, change or delete ingredients and products, as well as add, change,
or delete employee accounts.
Functional requirements

Customers

1.1 The user must be able to create a new order.

1.2 The user must be able to customize a pizza by:
1.2.1 The user must be able to view a list of available ingredients.
1.2.2 The user must be able to add an ingredient to a custom pizza
1.2.3 The user must be able to remove an ingredient from a custom pizza
1.2.4 The user must be able to get graphical feedback from
selecting ingredients. A photo of a pizza will contain the
newly selected ingredient combined with previous selected
ingredients.
1.3 The user must be able to add a custom pizza to an order.
1.4 The user must be able to view a list of available non-pizza products.
1.5 The user must be able to add non-pizza products to an order.
1.6 The user must be able to see a list of custom pizzas and non-pizza
products that are added to the order.
1.7 The user must be able to change the amount of a custom pizza.
1.8 The user must be able to change the amount of a non-pizza product.
1.9 The user must be able to delete a custom pizza from an order.
1.10 The user must be able to delete a non-pizza product from an order.
1.11 The user must be able to see the total price of an order.
1.12 The user must be able to choose a delivery date and time that is up to
two weeks ahead.
1.13 The user must be able to add the name and address of the customer.
1.14 The user must be able to clear the current order to start a new one.
1.15 The user must be able to confirm the order.

Employees

 The employee must be able to log in and out.

 The employee must be able to view a list of available orders and their
custom pizzas.
 The employee must be able to mark orders as “prepared”.
 The employee must be able to mark order as “delivered”
 The employee must be able to mark order as “failure to
deliver” 2.6 Only users with respective rights (employee)
must be able to use all these “Employees” features.

3 Administrators

3.1 The administrator must be able to log in and out.

3.2 The administrator must be able to add/delete/edit orders.
3.3 The administrator must be able to add/delete/edit ingredients.
3.4 The administrator must be able to add/delete/edit non-pizza products.
3.5 The administrator must be able to add/delete/edit other users.
3.6 The administrator must be able to view an order log.
3.7 Only users with respective rights (administrators) must be able to use all
these “Administrators” features.

Non-functional requirements

As an operational requirement, the system will run as a database with a

website as user interface. As performance requirement the system must
be accessible 24 hours a day, seven days a week. Due to the nature of
the system as an ordering website, the system must have a low response
time, preferably shorter than second, with a maximum of five seconds.
The exception is viewing order logs which could have a higher response
time (of seconds) as the log increases in size over time. Due to the low
complexity of the system, no problems with response time are expected.
Customers who visit the website to order will get a session ID for their
visit, which is used to identify them while using the system. For every
action they take, a timestamp is stored. From time to time a service on
the server will scan session ID’s and timestamps. Session ID’s which
have not been active for more than three hours will be deleted along
with the corresponding ordering information.
Architecture

Information Architecture

This paragraph describes the information architecture for the

database system. The data model consists of an Entity Relationship
Diagram (ERD) and relational schemas

ERD
We chose for a separate Non-Pizza and Pizza table, because it is far more
clear to program. If we would combine both the tables, we would get
confusing situations, because Pizza records are being created by the
customers, and non-pizza records are being created by the administrators.
The attributes might be very similar but a pizza record is always connected
to a bunch of ingredient records, where this is not the case for the non-pizza
records. The price of a pizza is based on the individual ingredient prices.
Upon completing the pizza, the price is being inserted in the Pizza table.

Diagram 1 shows the Entity-Relationship Diagram (ERD). In this paragraph

every relation between entities is described.

Customer --- Places --- Order

A customer can place several orders; the customer entity holds attributes
describing properties concerning the customer. The order entity holds
attributes such as
OrderStatus to track the status of the order (new/prepared/delivered/failed to
deliver).

Employee --- finalizes --- Order

An employee is responsible for the multiple or one order. By tracking

this, it is possible to look up which employee finalized which order.

Employee --- Adds New --- Non-Pizza

Through this relationship it is possible to track which non-pizza product

has been added to the database by which employee.

Employee --- Adds New --- Ingredients

Through this relationship we track which ingredient has been added by

which employee.

Pizza --- Pizza Ingredients --- Ingredients

This relation describes which ingredients belong to the pizza creations
(created by customers during their shopping process). A pizza can have 1
or multiple ingredients. It is impossible for a pizza to have zero
ingredients.

Order --- OrderNonPizza --- Non-Pizza

This tracks which non-Pizza products have been selected by the customer
during the shopping process. An Order can have 1, multiple or none Non-Pizza
products.

Order --- Has --- Pizza

This relation tracks the pizza’s which belong to an order created by a customer.
TESTING TEMPLATES:

Ingredient Management

Add and Change Ingredient

Steps Actions
1. Add ingredient
2. Logout
3. Login Different user
4. Change Ingredient
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R The change here means the add or change of any ingredient
V = Validation Point;R = Remarks

Delete Ingredients

Steps Actions
1. Delete ingredient
2. Logout
3. Login Different user
4. Delete other Ingredient
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R The change here means deletion of any ingredient.

V = Validation Point;R = Remarks

Modify Ingredients
Steps Actions
1. Modify ingredient
2. Logout
3. Login Different user
4. Modify other Ingredient
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R The change here means modification to the ingredient.

V = Validation Point;R = Remarks

Non-pizza Management

View Non-Pizza Product

Steps Actions
1. View Non-Pizza Product
2. Logout
3. Login Different user
4. View other Non-Pizza Product
V Are the changes being processed correctly, and does the new
record show non-pizza products? YES
R The non-pizza product which was viewed remains the same

V = Validation Point;R = Remarks

Add Non-Pizza Product

Steps Actions
1. Add Non-Pizza Product
2. Logout
3. Login Different user
4. Add other Non-Pizza Product
V Are the changes being processed correctly, and does the new
record show the other or new non-pizza products? YES
R

V = Validation Point;R = Remarks

Modify Non-Pizza Product

Steps Actions
1. Modify Non-Pizza Product
2. Logout
3. Login Different user
4. modify other Non-Pizza Product
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R The modification here can be the adjustment in the price

V = Validation Point;R = Remarks

Order Management

View Order

Step Actions
s
1. View Order
2. Logout
3. Login Different user
4. View another Order
V Are the changes being processed correctly, and does the new
record show the order as employee who changed it? YES
R
V = Validation Point;R = Remarks

Removal Management
Delete Pizza

Steps Actions
1. Delete Pizza
2. Logout
3. Login Different user
4. Delete other Pizza
V Are the changes being processed correctly, and does the new
record show the updated pizza list? YES
R The deleted item should not be in the system anymore

V = Validation Point;R = Remarks

Delete Non-Pizza

Steps Actions
1. Delete Non-Pizza
2. Logout
3. Login Different user
4. Delete another Non-Pizza
V Are the changes being processed correctly, and does the new
record show the updated non nonpizza list? YES
R The deleted item should not be in the system anymore

V = Validation Point;R = Remarks

Information Management

Delivery Date

Steps Actions
1. Check Delivery Date
2. Logout
3. Login Different user
4. Check the Delivery Date of another Order
V Are the changes being processed correctly, and does the new
record show the different Delivery Date of the new order/another
order? YES
R

V = Validation Point;R = Remarks

Add Customer info

Steps Actions
1. Add Customer Info
2. Logout
3. Login Different user
4. Add other Customer info
V Are the changes being processed correctly, and does the new
record show the different user as the correct customer
information? YES
R A new user will have a clean form to fill in (always)

V = Validation Point;R = Remarks

Clear Order

Steps Actions
1. Clear Order
2. Logout
3. Login Different user
4. Clear another Order
V Are the changes being processed correctly, and does the new
login show a clean order? YES
R

V = Validation Point;R = Remarks

Ordering

Add Custom Pizza

Step Actions
s
1. Select Ingredient
2. Check if Photo is updated, check if Price changes correctly
3. Select another Ingredient
4. Type a name
5. Select another Ingredient
6. Remove one of the previously selected ingredients
7. Press Add to Order
8. Check if the ingredients are listed correctly in the order
9. Select another Ingredient
10. Press Add to Order
11. Check if the new pizza was added correctly
V Are the changes being processed correctly, and does the new
record show the? YES
R

V = Validation Point;R = Remarks

Add Non-pizza

Steps Actions
1. Click on Side Order
2. Click on the shopping cart next to a non-pizza product
3. Click on the shopping cart next to another non-pizza product
4. Click on the shopping cart next to the in step 2 chosen non-pizza
product
5. Check if the first product has amount “2” and the other product
amount “1”
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R

V = Validation Point;R = Remarks

Current Order

Steps Actions
1. Select Ingredient
2. Press Add to Order
3. Press on the – under the pizza to remove it from the order list
4. Select Ingredient
5. Press Add to Order
6. Press on the + under the pizza to increase the amount by 1
7. Press on the + under the pizza to increase the amount by 1
8. Check if Price and Total Price are updated correctly
9. Press on the - under the pizza to decrease the amount by 1
10. Click on the red X to remove the pizza from the order list
V Are the changes being processed correctly, and does the new
record show the different user as employee who changed it? YES
R

V = Validation Point;R = Remarks

Delivery Information

Steps Actions
1. Click on Delivery Info
2. Type in Customer Information and pick a different delivery date
and time
3. Select another tab
4. Go back to Delivery Info
5. Check if data remains the same
V Are the changes being processed correctly, and does the new
record correct delivery date and other info? YES

Confirm Order

Steps Actions
1. Click on Confirm Order
2. Check the error message
3. Select an ingredient
4. Add to Order
5. Click on Confirm Order
6. Check if Delivery Info is shown
7. Fill in Delivery Info
8. Click on Confirm Order
9. See if confirmation page is shown
10. Click on Cancel
11. Click on Confirm Order
12. Click on OK
V Are the changes being processed correctly, and does the new
record show the order that is confirmed? YES
R

V = Validation Point;R = Remarks

Chapter 2: Approach

Our solution to make the pizzeria more efficient will be a website to

create orders online, which should be come with a good user interface.
Also it should be “fast” as in the customer will be able to order his pizza
in a matter of minutes. We stress the importance of “easy to use” user
interface here because some customers will leave if the website is too
complicated. In the case of a website where a user goes to for personal
interest a less user friendly interface is not a big problem since he will
try and try to get the information due to his interest in the site.

To create the website we will first analyze the current processes of the
pizzeria. This will be recorded in the use cases. From the use cases we
derive the system specification which describes what the system should
be able to do. It will contain the needed functionalities and the technical
specification. Then we will analyze the different users and list their
functional requirements and non-functional requirements for the system
in detail.
With all the specification and requirements we will create an
information model using an E-R diagram to describe the entities and the
relations between the entities. From the E-R diagram we will derive a
relational schema which will be used for the final database design. The
E-R diagram will be made in Visio.

GUI prototypes will follow using screen mockups in the form of images.
These mockups will be created using Photoshop.
To support implementation, a list of functions will be created describing
what actions these functions need to perform. The list will also include the
SQL statements that are needed to perform these actions.
During implementation, test scripts will be created. After implementation is
complete, the test scripts will be run by a few people to detect implementation
errors. The project will end when the implementation errors are fixed.
3 Scope Of The Project

It may help collecting perfect management in details. In a very short time,

the collection will be obvious, simple and sensible. It will help a person to
know the management of passed year perfectly and vividly. It also helps in
current all works relative to Inventory. It will be also reduced the cost of
collecting the management & collection procedure will go on smoothly.

The present project has been developed to meet the aspirations indicated in
the modern age. An attempt has been made through this project to do all
work ease & fast. It provide current add, Update, Move Next, Move
Previous , Move Last, Find & Delete all facilities to accomplish the desired
objectives. The facility Include in this project and the suggested activities
have been organized to impart knowledge & develop skill & attitude in the
Service official works.

(i) System Design (Introduction):

The systems objectives outlined during the feasibility study serve as

the basic from which the work of system design is initiated. Much of the
activities involved at this stage is of technical nature requiring a certain
degree of experience in designing systems, sound knowledge of computer
related technology and through understanding of computers available in the
market and the various facilities provided by the vendors. Nevertheless, a
system cannot be designed in isolation without the active involvement of the
user. The user has a vital role to play at this stage too. As we know that data
collected during feasibility study wills we utilized systematically during the
system design. It should, however be kept in mind that detailed study of the
existing system is not necessarily over with the completion of the feasibility
study. Depending on the plan of feasibility study, the level of detailed study
will vary and the system design stage will also vary in the amount of
investigation that still needs to be done. This investigation is generally an
urgent activity during the system. Sometimes, but rarely, this investigation
may form a separate stage between feasibility study and computer system
design. Designing a new system is a creative process, which calls for logical
as well as lateral thinking. The logical approach involves systematic moves
towards the end product keeping in mind the capabilities of the personnel
and the equipment at each decision making step. Lateral thought implies
encompassing of ideas

Beyond the usual functions and equipment. This is to ensure that no efforts
are being made to fit previous solutions into new situations.

ii) Considerations: System Design

The system design process is not a step-by-step adherence of clear

procedures and guidelines. Though, certain clear procedures and guidelines
have emerged in recent days , But still much of design work depends on
knowledge and experience of the designer. When designer starts working on
system design, he will face different type of problems. Many of these will be
due to constraints imposed by the user or limitations of the hardware and
software available in the market. Sometimes, it is difficult to enumerate the
complexity of the problems and solutions thereof since the variety of likely
problems is so great and no solutions are exactly similar.
iii)Design Objectives:

The primary objective of the design of course, is to deliver the requirements

as specified in the feasibility reports. In general the following design
objectives should be kept in mind.

Practicality

The system must be stable and can be operated by people with average.

Efficiency

This involves accuracy, timeliness and comprehensiveness to the system

output.

Cost

It is desirable to aim for a system with a minimum cost subject to the

condition that it must satisfy all the requirements.

Flexibility

The system should be modifiable depending on the changing needs of the

user. Such modifications should not entail extensive reconstructing or
recreation of software. It should also be portable to different computer
systems.

Security

This is very important aspect of the design and should cover areas of
hardware reliability, fall back procedures, physical security of data and
provision for detection of fraud and abuse.
System design involves first logical design and then physical construction of
the system. The logical design describes the structure and characteristics of
features, like the outputs, inputs, files, database and procedures. The
physical construction, which follows the logical design, produces actual
program software, files and a working system.

4. System Configuration

i) HARDWARE CONFIGURATION:

CPU TYPE : Dual Core

CPU CLOCK MEMORY : 2.66 GHz Extend
RAM DDR II : 2 GB
Disk drive : DVD Writer
Keyboard : Any
Display type : LCD monitor
Printer type : laser print
Speed : 1.1 GHz
Hard Disk : 500 GB
Mouse : optical

ii) SOFTWARE CONFIGURATION:

Operating System : Windows 7

Front End : .net
Back End : Ms Access
5 .Software Selection

OPERATING SYSTEM

Operating system software is a class of program which manages the

resources of the computer processing command and control program execution
as the translation of all computer operations. It is most complex program
executed on the complex yet must also be the most reliable. An operating
system irrespective of whether it is being used on a microcomputer,
minicomputer or mainframe computer. An operating system plays three basic
roles as a manager, as a command processor and as a controller. An operating
system can be a single user, a multiuser, a multitasking in this project we have
used Window 7 and MS Dos as operating system.

M.S.WORD
Microsoft word was first released in 1983 under the name multi-tool
word for system versions were later written for several other platforms. It
became part of the suite, in which it is referred to as Microsoft office word,
although it is still also sold as a standalone product or bundled with a full
featured word processing program for windows and the Macintosh from
Microsoft, it is sophisticated program with rudimentary desktop publishing
capabilities that has become the most widely used word processing applications
on the market the first various of word come out under dos and provided both
graphics-based and text-based interfaces for working with a document.

WINDOW 7
The difference being that the server Versions are designed to be dedicated
servers. The clients versions of windows may also share data over the network
and can be configured to grant access to all are specific files only. Windows
PC’s are used to access a verify of servers on the networks, including windows
servers, UNIX, Linux and network servers and mainframes. The most widely
used operating system for desktop and Laptop computer developed by the
Microsoft window primarily runs on the x 86-based CPU windows provide a
graphical user interface and desktop environment in application displayed in
resizable movable windows on screen. Window comes in both client and server
various, all of which support networking Windows 95 was the first 32-bit
windows operating system and a major upgrade from windows 3.1 it used an
entirely different user interface that incorporated the now common start menu
and taskbar. It was also the first time the computer booted directly into
windows, rather than being loaded after booting up in dos. Windows 98 was an
upgrade to Windows 95 that tightly integrated the internet explorer, web
browser with the O/S. In 1999 windows 98 second edition fixed numerous bugs
and upgraded its applications.

MS-DOS

Ms-dos (for micro soft disk operating system) is a commercialized by

Microsoft. It was the most widely used member of the family of operating
system and was the dominant .The operating system for during the 1980’s it has
gradually been replaced on customer desktop computers with various
generation of the operating system.dos commonly refers to the family of
closely related a single user operating system from Microsoft for the PC. It was
the first O/S for windows 3.1, 95, 98 , Window NT 2000, XP and 7 emulate dos
in order to support existing dos application.
VB.Net2010
Visual Basic.NET is the next generation of Microsoft's popular Visual
Basic programming languages. Some programmers refer to the new
incarnation as VB.net, but this is incorrect. VB.net is actually not
backwards-compatible with VB6, meaning that code written in the old
version will not compile under VB.net. In fact, the languages are sufficiently
different that many programmers consider them independent. As a language,
VB.net has the following traits:

Object-Oriented:-

VB.NET included limited support for object-oriented design.

Encapsulation was supported with Public and Private Data types in Classes, as
well as special accessory /matador Pairs called Properties (a feature unique to
Visual Basic). Polymorphism received crude Support through the Implements
keyword, which would require that one class implement all of the methods in
another, skeleton class. Inheritance was neglected completely. As of VB.NET,
all of this has changed. As with all 2013 languages, concepts, VB.NET includes
full-Blown support for object-oriented

Including simple inheritance. Unlike most other OOP languages, everything in

VB.net is an object, including all of the primitives (Short, Integer, Long, String,
Boolean, etc.) as well as types, events, and even assemblies. Everything inherits
from the Object base class.

Event-Driven:-

All previous versions of Visual Basic.net were event-driven, but this feature is
heavily enhanced under the vb.net framework. Events are no longer recognized
because they use certain naming convention (Object Name Event Name), but
now are declared with a Handles Object Name. Event Name clause. Event
handlers can also be declared at runtime using the Add Handler command.

6. System Analysis

The system analysis part is done by the following six steps

I. Preliminary Investigation
II. Feasibility Study
III. Fact Finding Techniques
IV. Cost Benefit Analysis
V. Entity Relationship Model
VI. Data Flow Diagram
VII. Normalization
i) Preliminary Investigation

   Here in the project Hotel Management System, a detailed study of existing

system is carried along with all the steps in system analysis. An idea for
creating a better project was carried and the next steps were followed. A
detailed study of the process must be made by various techniques like
interviews, questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of
how the system functions. This system is called the existing system. Now
the existing system is subjected to close study and problem areas are
identified. The designer now functions as a problem solver and tries to sort
out the difficulties that the enterprise faces. The solutions are given as
proposals. The proposal is then weighed with the existing system
analytically and the best one is selected. The proposal is presented to the
user for an endorsement by the user. The proposal is reviewed on user
request and suitable changes are made. This is loop that ends as soon as the
user is satisfied with proposal.  Preliminary study is the process of gathering
and interpreting facts, using the information for further studies on the
system. Preliminary study is problem solving activity that requires intensive
communication between the system users and system developers. It does
various feasibility studies. In these studies a rough figure of the system
activities can be obtained, from which the decision about the strategies to be
followed for effective system study and analysis .
ii) Feasibility Study

An important outcome of the preliminary investigation is the

determination the at the system requested is feasible. Feasibility study is
carried out to select the best system that meets the performance
requirements.

Feasibility study is both necessary and prudent to evaluate the feasibility of

the project at the earliest possible time. It involves preliminary investigation
of the project and examines whether the designed system will be useful to
the organization. Months or years of effort, thousand for millions of money
and untold professional embarrassment can be averted if an in-conceived
system is recognized early in the definition phase.

The different types of feasibility are: Technical feasibility, Operational

feasibility, Economical feasibility.

Technical Feasibility

Technical Feasibility deals with the hardware as well as software

requirements. Technology is not a constraint to type system development.
We have to find out whether the necessary technology, the proposed
equipments have the capacity to hold the data, which is used in the project,
should be checked to carry out this technical feasibility.
The technical feasibility issues usually raised during the feasibility
stage of investigation includes these
 This software is running in windows 2000 Operating
System, which can be easily installed.
 The hardware required is Pentium based server.
 The system can be expanded.

Behavioral Feasibility

This feasibility test asks if the system will work when it is developed and
installed Operational feasibility in this project:

 The proposed system offers greater level of user-

The proposed system produces best results and gives
high performance. It can be implemented easily .So this
project is operationally feasible.

Economical feasibility

Economical Feasibility deals about the economical impact faced by the

organization to implement a new system. Financial benefits must equal or
exceed the costs. The cost of conducting a full system, including software
and hardware cost for the class of application being considered should be
evaluated. Economic Feasibility in this project:

The cost to conduct a full system investigation is possible.

iii) Fact Finding Techniques

The various document of the office was studied and after a short interview
the fact finding was finished and certain
questions were arising that:

1. Whether there is any problem of retrieval.

2. Whether there is any extra Guide needed.
3. Whether you want the proposed system of Hardware detailing.
4. Whether the office member is benefited or not.
5. Whether they are ready to accept the changes or not.
And afterwards it was found that:

1. No problem of retrieval.
2. There is no extra Guide is needed.
3. Yes they want the proposed system of Hardware Detailing.
4. Yes office member is benefited.
5. Yes they are ready to accept the changes.

iv) Cost Benefit Analysis

A system is also expected to provide benefits. The first task is to identify

and then assign a monetary value to it for cost / benefit analysis.
The two major benefits are improving performance and minimizing the
cost of processing. The performance category emphasize in the accuracy of
the result or access to information and easier access to the system by
authorized users.
Our software has fulfilled all the benefits very well. Our software are
improving and minimizing the cost of processing. Our software has
controlled error and caused reduction of staff.
Tangible or Intangible cost and benefits:-

An outlay of case for a special file item or activity is referred to as a

tangible cost. The purchase of hardware or software, personal training and
employees salaries are examples of tangible cost in our software we have
included training and employee salaries approx 300 /- to be paid for
training and we have saved the salary of 3 employees but training cost is
one time cost and hence we have saved 3 x 5000 = 15000 /- per month.
V) Data Flow Diagram
Data flow oriented techniques advocate that the major data items
handled by a system must be first identified and then the processing required
on these data items to produce the desired outputs should be determined.
The DFD (also called as bubble chart) is a simple graphical formalism that
can be used to represent a system in terms of input data to the system,
various processing carried out on these data, and the output generated by the
system. It was introduced by De Macro (1978) , Gane and Sarson
(1979).The primitive symbols used for constructing DFD’s are:
Symbols used in DFD :
A circle represents a process.

A rectangle represents external entity

A square defines a source or destination of the system data.

An arrow identifies dataflow.

Double line with one end closed indicates data store

vi) Normalization

Normalization is a data analysis technique that organizes the data such

that they are grouped to form non-redundant, stable, flexible and adaptive
entities. Normalization is a three stem technique that places the data moved
in 3N forms.
We can easily change the database without rewriting many or the entire
program that used those databases.

We can make our data model as application independent as possible to

encourage the Database structure that can be extended to modify without
impact to current program.

I. Simply stated entity in 1NF if there are no attributes that can have more than
one value for single instance of the entity any attribute that can have multiple
values actually describe a separate entity possibly an entity and relationship.

II. An entity is in 2NF if it is already in 1NF and if the value of all non primary
key attributes that are dependent on only part of primary key should be moved
to any entity where that partial key is actually the full key. That may require
creating a new entity and relationship of model.

III. An entity is in 3NF if it is already in 2NF and if the value of it non primary
key attributes that are not dependent on another non primary key attributes.
Any non primary key attributes that are dependent on other non primary key
attributes must be moved or deleted. Again new entities and relationship may
have to be added to the data model. For our convenience we have not taken the
concept of Normalization in consideration in our project.

7. Implementation

Implementation is the stage of the project when the theoretical design is

turned out into a working system. Thus it can be considered to be the most
critical stage in achieving a successful new system and in giving the user,
confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the
existing system and it’s constraints on implementation, designing of
methods to achieve changeover and evaluation of changeover methods.
Implementation Review:
After the system is implemented and conversion is complete, user usually
conducts a review of the system. User usually conducts a review of the system.
 In this system all Requirements are fulfills.
 The user can easily insert, update and delete the
record in Efficient way.
 This system is user-friendly and easily understands.
 User can view the Purchase Report and Sales Report So,
user can speedily work in this system .
 The performance level of users has improved.
 Data record can be easily stored.

8. DATA DICTIONARY

Field type Appropriate Uses Storage Space

Text Data containing text, a Based on what’s

combination of text and actually stored in
numbers, or numbers that the field; ranges
don’t need to be included from 0 to 255
in calculations. Examples bytes
are name, addresses,
department codes, and
phone numbers.

Memo Long text and numeric Ranges from 0 to

strings Example are notes 65,536 bytes.
and description

Number Data that’s included in 1, 2, 4 or 8

calculation (excluding bytes,depending
money). on the field size
Examples are ages, codes selected (or 16
(such as employee Bytes for
IDs),and payment Replication ID).
methods

Date/Time Dates and times ex. Are 8 bytes

Date ordered ,birth date

Auto number Unique sequential or 4 bytes (16 bytes

random numbers ex. for replication
invoice number and ID).
project number

9.DATABASE –DESIGN

A database is an organized mechanism that has the capability of storing

information through which a user can retrieve stored information in an
effective and efficient manner. The data is the purpose of any database and
must be protected.
The database design is a two level process. In the first step, user
requirements are gathered together and a database is designed which will
meet these requirements as clearly as possible. This step is called
Information Level Design and it is taken independent of any individual
Database Management System (DBMS).

Organization of the data in the database is aimed to achieve. In the

second step, this Information level design is transferred into a design for the
specific DBMS that will be used to implement the system in question. This
step is called Physical Level Design, concerned with the characteristics of
the specific DBMS that will be used. A database design runs parallel with
the system design. The following two major objectives.
 Data Integrity
 Data independence
CONCLUSION

The aim of this project was to save the time, make the processing faster
and accurate and to automate the Hotel management system. Maintaining the
activities of managerial area, which would not only help the employees
related to the services but also the members.

Thus all the objectives that were determined in the beginning were mate.
This system makes the management activities of service faster and accurate.
It increases the efficiency of the management system and changes a
complicated system to a simpler system. Though it has some limitations still
then it works efficiently.