Catering Management System Project Report

Catering Management
INDEX
Section Description Page No
1 Introduction 5-8
2 Software Requirement Analysis And 9-17

Specification
3 Design 18-44
4 Testing 45-75
5 User Manual 76-87
6 Conclusion 88
7 Scope for Future Enhancement 89
8 Bibliography 90
www.studentprojectguide.com
Catering Management
TABLE OF CONTENTS
Section Description
INTRODUCTION
1.
1.1 Project Performa...................................................................06
1.2 Company Profile....................................................................07
1.3 Project Details..................................................................07-08
SOFTWARE REQUIREMENTS ANALYSIS AND SPECIFICATION

2.
2.1Introduction.........................................................................10
2.1.1 Purpose........................................................................10
2.1.2 Scope............................................................................10
2.1.3 Definitions, Acronyms and Abbreviation..............10-11
2.1.4 References....................................................................11
2.1.5 Overview......................................................................11
2.2 Overall Description..............................................................11

2.2.1 Product Perspective.................................................11-12
2.2.2 Product Features........................................................12
2.2.3 User classes and Characteristics...............................12
2.2.4 Design constraints......................................................12
2.2.5 Assumption and dependencies...................................12
2.3 Specific Requirements.........................................................13

2.3.1 External Interface Requirements.............................13
2.3.1.1 User Interfaces..............................................13
2.3.1.2 Hardware Interfaces.....................................13
2.3.1.3 Software Interfaces......................................13
2.3.1.4 Communication Interfaces...........................13
2.3.2 Functional Requirements........................................13
2.3.2.1 Input Requirements....................................13
2.3.2.1.1 Purchase Details..........................13-14
2.3.2.1.2 Inventory.....................................14
2.3.2.1.3 Employee Transaction..................14
2.3.2.1.4 Food Sales Information.................
2.3.2.1.5 Receipts Information...................
2.3.2.1.6 Reports Information....................
2.3.3 Document Conventions...........................................
2.3.4 Intended User and Reading suggestions................
2.3.5 User Documentation................................................
2.4 Other Non-functional Requirements...............................
2.4.1 Performance Requirements............................................
Catering Management
2.4.2 Safety Requirements......................................................

2.4.3 Security Requirements..................................................
2.4.4 Software Quality Attributes........................................
2.5 Other Requirements.............................................................
3. DESIGN
3.1 Data Flow Diagram...............................................................

3.2 Entity Relationship Diagram...............................................
3.3 Table Relationship Diagram.................................................
3.4 Schema Description...............................................................
3.5 Detailed Design.....................................................................
4. TESTING................................................................
5. USER MANUAL.......................................................
6. CONCLUSION.........................................................
7. SCOPE FOR FURTHER ENHANCEMENT......................
BIBLIOGRAPHY.........................................................................
8.
Catering Management
INTRODUCTION
1.3 Project details

Title of the project
Catering Management
Objectives
Catering Management
The main objective of the Catering Management is to develop a software

system for hotel which maintains the accounts which includes the Bills,
Inventory, Receipts, and Expenditures, Employee details, Supplier payments,
Reports and Monthly sales of the company as well as the employee payroll.
Project Category
Stand-alone Application
Software Requirements
Front End: Visual Basic.net
Vb.net is the improved version and contains improved features such as

inheritance, interface and over loading these features make it powerful object-
oriented programming language. As a basic developer, we can now create
multi threaded, scalable application using explicit multithreading. Other new
features include structured exception handling, customer interoperability;
simplified deployment enhanced security and improved versioning support.
Visual Basic.net is composed of three primary entities:

Assemblies : The primary unit of deployment of a NET application.
Modules : The individual fields that make up an assembly.
Back End: SQL (Structured Query Language)

Microsoft SQL Server is an application used to create computer databases for
the Microsoft Windows family of server operating systems. Microsoft SQL
Server provides an environment used to generate databases that can be
accessed from workstations, the Internet, or other media such as a personal
digital assistant (PDA).
Microsoft SQL Server is a relational database server, developed by Microsoft:

It is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or
those running on another computer across a network (including the Internet).
There are at least a dozen different editions of Microsoft SQL Server aimed at
different audiences and for different workloads (ranging from small
Catering Management
applications that store and retrieve data on the same computer, to millions of
users and computers that access huge amounts of data from the Internet at the
same time).
Hardware Requirements
Operating System:Windows Xp or above

Processor : Intel Dual core or above
RAM : 512 MB or above
Hard Disk : 50 GB or above
Future scope of the project:

 Online web application.
 Online Orders.
Software Requirement
Specification
Catering Management
2. Software Requirement Specification
2.1 Introduction
SRS – is a complete description of the behaviour of a system to be developed. It

deals with the requirements of the proposed system. It describes what the
proposed System should do without describing how the System will do it. An
SRS provides a reference for the validation of the final product i.e.; the SRS
helps the client to determine if the System meets the requirements.
2.1.1 Purpose
This document is meant to serve as a guide to the developer on one hand

and a software validation document for the client on the other. The
purpose of this document is to specify all the information required to
design, develop and test the software. This is to ensure that the person
reading the document understands what he or she is looking at. It
provides the visibility in the design and provides information needed for
software support.8147935613
2.1.2 Scope
This SRS describes the requirement of the system. It’s meant for use by
the developer and will be the basis for validating the final delivered
system; any changes made to the requirement in the future will have to
Catering Management
go through the formal change approval process. This document contains

a complete description of the functioning of the Catering Management.
2.1.3 Definitions, Acronyms, Abbreviations
SRS - Software Requirements specifications

SQL - Structured Query Language
RAM - Random Access Memory
OS - Operating System
VB.Net -Visual Basic.Net
2.1.4 References
Text Books:
 Software Engineering - Ian Summerville
 Pankaj Jalote, Integrated Approach to Software
Engineering, Third Edition,Narosa Publications
2.1.5 Overview
The SRS is organized into two main sections. The first is the Overall
Description and the second is the Specific Requirements. The Overall
Description will describe the requirements from a general high level
perspective. The Specific Requirements section will describe in detail
the requirements of the system. The primary purpose of this
application is to implement the above stated functionality. It will be
having user friendly GUIs that will guide the user to easily achieve the
same. The application shall also have some features like reports
displaying in the same window.

2.2 Overall description
This section of the SRS describes all general factors of the product and its
requirements.
Catering Management
2.2.1Product Perspective
This section aims to describe both the existing and the proposed
systems, with respect to why the proposed system is needed.
After understanding the existing system, the need for developing new
system includes different people involved in the related activities have
been consulted. The data needed for the study has been collected from
company records.
2.2.2Product Features
The major features of the Catering Management are organised

according to its main components. The features of the Catering
Management are as follows:
 Keeps the track of the transactions done in the Industry and
Produce Bills, Receipts.
 Up-to-date Reports are generated.
 Sales details are maintained.
 Employee Payroll is maintained.
 Reduces manual work and time consumption
 Provides Data security
 No Data loss and Misuse of data is avoided.
2.2.3 User classes and Characteristics
 General users with basic computer skill can use this software.
 Administrator can use the application.
2.2.4Design constraints
// None
Catering Management
2.2.5 Assumption and dependencies

The product must have an interface which is simple enough to
understand to the end users. The system has to create at least one user
by default else the system can’t be used.
2.3Specific Requirements
2.3.1External Interface Requirements
2.3.1.1 User Interface
The System is a GUI (Graphical User Interface). It consists of

buttons and menus which assist the user for the proper working
of the system.
2.3.1.2 Hardware Interface
 Printer
2.3.1.3 Software Interface
Software requirements are:
Operating System : Windows XP/2000/vista/7

Front-end : VB.NET
Back-end : SQL Sever
2.3.1.4Communication Interface
//None
2.3.2 Functional Requirements:
2.3.2.1 Input Requirements
Catering Management
2.3.2.1.1 Purchase Details
Introduction: Stores supplier information

Input: Entering the personal details of the Suppliers
Processing: Supplier details will be stored
Output: Proper data will be stored as well as can be
retrieved.
Here the purchase details like Groceries, purchase,
other Expenditures are
Maintained. Monthly purchase reports are generated.
Purchase influences income of the caterers.
2.3.2.1.2 Inventory
Introduction: Stores stock information

Input: Entering the Item name, Quantity and
Amount
Processing: Stock details will be stored
retrieved.
Here daily stock details are maintained. User can
view the stock items.
2.3.2.1.3 Employee Transaction
Introduction: Stores employee information

Input: Entering the personal details, basic pay of the
employee
Processing: Employee details will be stored
retrieved.
Catering Management
Monthly salary will be calculated for the employees.

Every employee has
The Basic salary, Allowance are added to the Basic
salary and PF, ESI are
Deducted from Basic salary.
Hence the total salary will be calculated for all the
employees.
2.3.2.1.4Food Sales Information
Introduction: Stores sales details of the industry.

Input: Entering the day wise sales details like
employee details, coupon amount etc
Processing: Day wise sales details are stored.
Output: Sales reports are generated.
In food sales daily sales of the foods are maintained.
Depending on the coupon collected they
differentiated according to the food type
Like lunch, breakfast, dinner etc. At the end of the
month the food bills are
Calculated and reports are generated.
2.3.2.1.5 Receipts information
Introduction: Stores food Bill payment details.

Input: Entering the food Bill payment details done
by the MRPL.
Processing: Receipts are generated and stored.
Output: Outstanding amount will be retrieved and
reports will be produced.
Depending on the food bill, the payment details
done by the customers are
Catering Management
Maintained and the final reports will be sent to

customers.
2.3.2.1.6 Reports information
Expenditure, Food bill reports, Receipts, Employee

payroll receipts will be generated.
2.3.3 Document conventions.

The format of this SRS is simple. Bold face and indentation is used on general
topics and or specific points of interest. The remainder of the
document will be written using the standard font, New Times Roman.
2.3.4 Intended User and Reading suggestions

This document is intended for software developers, documentation
writers and for general discussions on the implementation decisions
regarding the Software.
2.3.5 User Documentation

The “help” button placed in the main screen of this software will give the
simple explanation about how the software can be used, so that the
user can easily understand and operate with this software quickly.
2.4 Other Non-functional Requirements
2.4.1Performance Requirements
The system is supposed to be having good memory space and a

Bigger RAM above 512 MB preferably. The sound card and
graphics card will have to be of good quality and capacity.
2.4.2Safety Requirements
Catering Management
To avoid data loss backups can be done regularly.

There should be an Antivirus to protect the software
2.4.3 Security Requirements
Authenticated users are able to access the system.
2.4.4 Software Quality Attributes
 Reliability
Specify the factors required to establish the required reliability
of the software system at time of delivery.
 Availability
The system shall be available during normal operating hours of
company.
 Security
Administrators will be able to log in to the Catering
Management System. Administrator will provide the
permissions to Access the Sub Functions for the Users.
 Maintainability
The Catering Management is being developed in VB.Net.
 Portability
The Catering Management shall run in any Microsoft Windows
environment that contains VB.Net platform and the Microsoft
Sql Server 2008 database.
2.5 Other Requirements:
// None
Catering Management
System Design
Catering Management
3. Design
System Design
The purpose of the design phase is to plan a solution of the problem specified by
the requirement of the document. This is the phase in moving from problem
domain to solution domain. The design process is a set of iterative steps that
enable the designer to describe all aspects of the software to be built. Design is
essentially the bridge between the requirement specification and final solution for
satisfying the requirement. The design of the system is essentially a blueprint
orplan for asolution for the system. The two levels of designprocess are system
design anddetailed design.
In System design, the focus is on deciding which modules are needed for the
system, the specification of these modules, and how the modules should be
interconnected. It is also called Top-level design. The system design controls the
major structural characteristics of the system. It has a major impact on the
testability and modifiability of a system, and it impacts its efficiency. At the end
of the system design, all the major data structures, file formats and the major
modules in the system and their specifications are decided.
3.1 Data Flow Diagram
CONTEXT FLOW DIAGRAMS
A context diagram is a dataflow diagram with only massive central process that
subsumes everything inside the scope of the system. It shows how the system
will receive and send data flows to the external entities involved.
Context diagram is a dataflow diagram showing data flows between a

generalized application within the domain and other entities and abstraction with
which it communicates. One thing that differentiate the use of data flow
diagrams in domain analysis from other typical uses is that the variability of the
data flows across the domain boundary must be accounted for which either a set
of diagrams or text describing the differences.
Catering Management
In this context diagram, the information provided to and received from the
movement control domain is identified. The arrows represent the information
received or generated by the movement control domain. The closes boxes
represent the set of sources and sinks of information.
A context flow diagram confines project scope to an agreed limit by obtaining

agreement from the customer on the data flows that are included in the scope of
the project. The context diagram focuses on relationships with external entities
and identifies the information that is exchanged between these external entities
and the business system under review. The external entities themselves are
outside the scope of the project but the data flows between the entities and the
business system are within the project scope.
DATA FLOW DIAGRAMS
SYMBOLS DESCRIPTION
Represents the Database
Represents the external entity
Represents the data flows
Represents the process that transforms incoming

data flows into outgoing data flows
* Represents the AND symbol
+ Represents the OR symbol
Catering Management
The DFD was first developed by Larry Constantine as a way of expressing system
requirements in a graphical form; this leads a module design. A DFD also known as
bubble chart has the purpose of clarifying system requirements and identifying major
transformations that will become programs in system design. So it is the starting point
of the design phase that functionally decomposes the requirement specification down
to the lowest level of details. The DFD consist of a series of bubbles joined by lines.
Data flow diagrams are used to describe how the system transforms information. They
define how information is processed and stored and also identify how the information
flows through the processes. It differs from flow chat as it shows the data flow instead
of the control flow of the program. A data flow diagram can also be used for the
visualization of data processing (structured design)
CONSTRUCTING A DFD
 Processes should be named and numbered for easy reference. Each

name should be representative of the process.
 The direction of the flow is from top to bottom and from left to
right. Data traditionally flows from the source to the destination,
although they may flow back to a source. One way to indicate this
is to draw a long flow line back to a source. An alternative way is
to repeat the source symbol as destination. Since it is used more
than once in the DFD, it is marked with a short diagonal in the
lower right corner.
 When a process is exploded into lower level details, they are
numbered.
 The names of data stores, sources and destination are written in
capital letters.
 Process and data flow names have the first letter of each word
capitalized.
Catering Management
CONTEXT FLOW DIAGRAM:
LEVEL 0:
Sup_ID, Punch_No, Food_Type, Amt,

Expenditure_type
0.0
User Catering
Management
Final_Bill_Amt, Payed_Amt, Reports
DATAFLOW DIAGRAM:
LEVEL 1:
Top Level Diagram
Catering Management
purchase_no, purchase amount, date,

1.0
sup_id, name, contact
Purchase tbl_Purchase
Details
Emp_Id, name, basic, esi,

2.0 allowance,pf
Employee tbl_Employee
Transaction
date, no_of_coupons,
date, no_of_coupons,
User coupon_type,amt 3.0 coupon_type,amt
Food
tbl_Food sales
Sales
Details
4.0
reciept_no, amt_paid, date
Generation
tbl_Reciepts
Of
Reciepts
LEVEL 2:
Purchase Details
purchase_no, purchase_amt, 1.1 purchase_no, purchase_amt,

date, sup_id, name, contact Update date, sup_id, name, contact
User
Purchase tbl_Supplier
Details
Purchase_no,Sup_id,purchase_Amt
1.2
Supplier
Payments
name, Id
1.3
Date,Amt
Reports
tbl_Supplier
Payments
LEVEL 2:
Catering Management
Employee Transaction
emp_id, name, basic, esi,

2.1
allowance, pf
User Updating
Employee
Details
tbl_Employee
2.2
Salary
Generation employee_details
month, year, emp_id,

total_salary_amt
tbl_Salary
Report
LEVEL 2:
Food Sales Details
date, coupon no, coupon 3.1 date, coupon no, coupon

type, amt Food type, amt tbl_Coupon
User
Coupon
Updation
3.2
On Cash
date, amt
Food Supply tbl_Cash
Details
3.3
Food
Bill date, type of food
Generation
month, year
Sales
tbl_Bill
month bill
3.4
Reports
Sales
Final Sales
LEVEL 2:
Catering Management
For Generation of Receipts
4.1 billno
Payed amt, date Updating
User tbl_Bill
Of
Reciepts amt
tbl_Reciepts
4.2
month, year
Budget
Income report Estimation
Report
final bill amt
total
month, year
expenses
tbl__Purchase
3.2 Entity-Relationship Diagram
The basic object that the E-R model represents is an entity which is a “thing in
real world with an independent existence. An entity may be an object with a
physical existence (person, car, house etc.) Or it may be an object with a
conceptual existence (company, job, university, course etc). Each entity has
attributes particular properties that describes it. Further each entity will have a
value for each of its attributes. Each key attributes has its name underlined.
Whenever an attribute of one entity type refers to another entity some
relationship exists. The degree of a relationship type is the number of
participating entity types. The cardinality ratio for binary relationship specifies a
number of relationship existences that an entity can participate in.
Hence we include that an E-R Diagram represents the relationship between the
entities.
ENTITY: It may be an object with physical existence or conceptual existence.
Catering Management
Entity name
ATTRIBUTE: The properties of entity can be described as an attribute.
Attribute name
RELATIONSHIP: Whenever an attribute of one entity type refers to another entity

type, some relationship exists.
Relation
MULTIVALUED ATTRIBUTE: Attributes that have different number of values for

a particular attribute.
Multi-valued
attribute
WEAK ENTITY TYPE: Entity that has no key attribute of their own are called
weak entity types.
Weak Entity
RATIO: It specifies the maximum number of relationship instances that an entity can
participate in. There are four cardinality ratios.
Catering Management
1) 1:1
2) 1:N
3) N:1
4) M:N
1 1
Rel
EntityE11 D Entity
E2
Entity-Relationship Diagram
Catering Management
quantity
coupon_
N
address Gives Cash date
PhoneNo WORKS
Custname
For Sales_date
coupon_ coupon_
MobileNo
type type
Email ID Company 1 N N Updates 1 dailySales N_coupons

Gives Coupon
Employee
Recieves
coupon_
1 food_Cost
1 type Customer
1 name
Recieves generate Custname
1
total_amt
1
foodblls
billdate
billNo
month year
generate
1 reciept_tNo
1
Reciepts
reciept_date
amtpaid
billno
3.3 Table Relationship
Catering Management
Table Design
3.4 Schema Description
Catering Management
Introduction
Schema Description is the process of producing a detailed data model of a

database. This data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in a data
definition language, which can then be used to create a database.
Normalization
Normalization is the process of efficiently organizing data in a database. There

are two goals of the normalization process: eliminating redundant data (for
example, storing the same data in more than one table) and ensuring data
dependencies make sense (only storing related data in a table). Both of these
are worthy goals as they reduce the amount of space a database consumes and
ensures that data is logically stored. Normalization usually involves dividing
large, badly- formed tables into smaller, well-formed tables and defining
relationships between them. The objective is to isolate data so that additions,
deletions, and modifications of a field can be made in just one table and then
propagated through the rest of the database via the defined relationships. The
database community has developed a series of guidelines for ensuring that
database is normalized. These are referred to as normal forms and are
numbered from 1NF, 2NF, 3NF and so on.
Normal Form (1NF): Each field in a table contains different information. First normal form
(1NF) sets the very basic rules for an organized database:
 Eliminate duplicative columns from the same table.

 Create separate tables for each group of related data and identify each row with a unique
column or set of columns (the primary key).
Second Normal Form (2NF): Each field in a table that is not a determiner of the contents of
another field must itself be a function of the other fields in the table. Second normal form
(2NF) further addresses the concept of removing duplicative data:
 Meet all the requirements of the first normal form.
 Remove subsets of data that apply to multiple rows of a table and place them in separate
tables.
Catering Management
 Create relationships between these new tables and their predecessors through the use of
foreign keys.
Third Normal Form (3NF):Third normal form (3NF) goes one large step further. No
duplicate information is permitted.
 Meet all the requirement of the second normal form.

 Remove columns that are not dependent upon the primary key.
Schema Description
Customer table
Field name Data type Constraints Description
Customer _Name Varchar(50) Primary key Name of the
Customer
Address Varchar(MAX) Not null Address of the
Customer
Phone Number Numeric(18,0) Not null Phone number Of the
Customer
Mobile Number Numeric(18,0) Not null Mobile Number of
the Customer
Email ID Varchar(50) Not null Email ID of the
Customer
Coupon Table
Food Type Date Not null Type of Food
Food Cost Money Not null Cost of the food
Cash Table
Coupon Date Date Not null Coupon date
Food Type Varchar(50) Not null Type of the Food
Quantity Numeric(18,0) Not null Quantity of the Food
Food Bills table

Bill_no Numeric(18,0) Primary key Bill Number
Month Varchar(50) Not null Month
Year Numeric(18,0) Not null Year
Bill Date Date Not null Bill Date
Total Amount Money Not null Total Amount
Customer Name Varchar(50) Not null Name of the Customer
Reciepts table
Catering Management

Receipt No Numeric(18,0) Primary key Receipt No
Receipt Date Date Not null Receipt Date
Bill Number Numeric(18,0) Not null Bill Number
Amount Paid Money Not null Amount Paid by the
Customer
Daily Sales Table

Supplier Date Date Not null Supplier Date
Food Type Varchar(50) Not null Type of the Food
Number of the Coupons Numeric(18,0) Not null Number of the
Coupons
Customer Name Varchar(50) Not null Name of the Customer
Employee Table
Employee Name Varchar(50) Not null Name of the Employee
Nature of Work Varchar(50) Not null Nature of work
Phone Number Numeric(18,0) Primary Key Phone Number of the
Employee
Address Varchar(MAX) Not null Address of the Employee
Contact Number Numeric(18,0) Not null Mobile Number of the
Employee
Date Of Join Date Not null Date of Join of the
Employee
Salary Table
Month Varchar(20) Not null Month
Year Numeric(18,0) Not null Year
Phone Number Numeric(18,0) Not null Phone Number of the
Employee
Number of Days Numeric(18,0) Not null Number of Days
worked by Employee
SRK Allowance Money Not Null SRK Allowance given
to Employee
OT Money Not Null Over Time
Total Gross Money Not Null Total Gross
Deduction Money Not Null Deduction from
Employee Salary
Wage Paid Money Not Null Wage Paid to
Employee
3.5 Detailed Design
Catering Management
The purpose of the design phase is to plan a solution of the problem specified by
the requirements document. The design of the system is perhaps the most critical
factor affecting the quality of the software. This phase is the first step in moving
from the problem domain the solution domain.
LOGIN PAGE:
Fields Type Description

UserType Textfield Used to enter Usertype
UserName Textfield Used to enter Username
Password Textfield Used to enter User Password
Login Button Redirects to welcome user form
MASTER PAGE:

Purchase Details Menu Supplier_details/Payments are maintained
Inventory Menu Stocks are maintained
Catering Management
Customer Menu Customer Details are maintained

Food Sales Menu Keeps Track of Daily Food_sales
Employee Menu Employee Details/Payroll are maintained
Accounts Menu Monthly Food_Bills/Reciepts/Expenditure are maintained
Configuration Menu Current Year Settings/User_creation are Maintained
Help Menu Helps how to use the project
Exit Menu Exits the whole Master Page
SUPPLIER DETAILS:

Supplier_ID Textfield Used to enter Supplier_id
Supplier_Name Textfield Used to enter Supplier_name
Address Textfield Used to enter Supplier Address
Contact_no Textfield Used to enter contact_no
Remarks Textfield Used to enter the remarks
ADD Button Redirects to add supplier details
VIEW Button Redirects to view supplier details
RESET Button Redirects to reset supplier details
SUPPLIER BILL PAGE:
Catering Management

Supplier_Name Combo Used to selectSupplier_Name
Bill_Number Textfield Used to enter Bill_Number
Bill_Date DateTimePicker Used to selectBill_Date
Total_Amount Textfield Used to enter Bill Amount
Add_Bill Button Redirects to add Supplier_bills
Reset Button Redirects to reset Supplier_bills
VIEW SUPPLIER BILLS:

Search By Combo Used to select Suppliers
SUPPLIER PAYMENTS:
Catering Management

Supplier_Name Combo Used to select Supplier_Name
Bill_No Combo Used to select Bill_No
Total_Amount Textfield Used to enter Total_Amount
Amount_Paid Textfield Used to enter Amount_Paid
Balance Textfield Redirects the Balance Amount
ADD Button Redirects to add Supplier_Payments
Reset Button Redirects to reset Supplier_Payments
ADD STOCK:

Date DateTimePicker Used to select the Date
Item_Name Textfield Used to enter Item_Names
Quantity Textfield Used to enter Item Quantity
Amount Textfield Used to enter Item Amount
Submit Button Redirects to Submit the Stocks
View Button Redirects to View the Stocks
Reset Button Redirects to Reset the Stocks
VIEW STOCK:
Catering Management

Month Combo Used to select Month
Year Combo Used to select Year
Print Button Redirects to print the stocks
UPDATE STOCK:

Date DateTimePicker Used to select Date
Items_Name Combo Used to select Items
Used_Quantity Textfield Used to enter the quantity used
Update Button Redirects to Update the stocks
CUSTOMER DETAILS:
Catering Management

Customer_Name Textfield Used to enter the Customer_Name
Address Textfield Used to enter the Customer_Address
Phone_Number Textfield Used to enter the Phone_Number
Mobile_ Number Textfield Used to enter the Mobile_ Number
Email_ID Textfield Used to enter the Email_ID
Update Button Redirects to Update Customer Details
Reset Button Redirects to Reset Customer Details
ADDING NEW ITEM:

Menu_Name Textfield Used to enter the menu_name
Cost Textfield Used to enter the cost
Submit Button Redirects to Submit the Menu
View Button Redirects to View the Menu
Reset Button Redirects to Reset the Menu
VIEW MENU:
Catering Management

Delete Button Redirects to delete the menu
FOOD COUPONS:

Coupon_Type Textfield Used to enter Coupon_Type
Food_Cost Textfield Used to enter the Food_Cost
Save Button Redirects to Save the Coupon
Reset Button Redirects to Reset the Coupon
DAILY SALES:
Catering Management

Update Button Redirects to Update Daily_sales
ADDING EMPLOYEE:

Employee_Name Textfield Used to enter the Employee_Name
Catering Management
Nature_of_Work Combo Used to select Nature_of_Work

PunchCard_No Textfield Used to enterPunchCard_No
Address Textfield Used to enterAddress
Contact_no Textfield Used to enterContact_no
Date_of_Join DateTimePicker Used to select the Date
ADD Button Redirects to ADD the Employee
Reset Button Redirects to Reset the Employee
EMPLOYEE PAYMENTS:

Year Combo Used to select Year
Generate_Payroll Button Redirects to Generate_Payroll
ADD Button Redirects to ADD Employee_Payments
Print_All Button Redirects to Print all Employee_Payments
Print Button Redirects to Print selected Employee
MONTHLY FOOD BILLS:
Catering Management

Bill_No Textfield Used to enter the Bill_No
Bill_Date DateTimePicker Used to select the Date
Month Combo Used to select the Month
Year Textfield Used to select the Year
Generate Button Redirects to Generate Food_Bills
ADD Button Redirects to ADD Food_Bills
Print Button Redirects to Print Food_Bills
RECIEPT:
Catering Management

Reciept_No Textfield Used to enter the
Reciept_No
Reciept_Date DateTimePicker Used to select the Date
Month Combo Used to select the Month
Year Textfield Used to select the Year
ADD Button Redirects to ADD Reciept
Print Button Redirects to Print Reciept
EXPENDITURE:

Date DateTimePicker Used to select the Date
Transportation Textfield Used to enter Transportation charges
Repair/Servicing Textfield Used to enter the Repair charges
Infrastructure Textfield Used to enter the Infrastructurecharges
Calculate Button Redirects to Calculate Expenditure
Submit Button Redirects to SubmitExpenditure
Catering Management
Reset Button Redirects to ResetExpenditure
MONTHLY BILLS:

Month Combo Used to select the Date
Year Textfield Used to enter year
Generate Button Redirects to generate bills
Print Button Redirects to print the bill
CURRENT YEAR SETTINGS:

Year Textfield Used to enter the Year
Nature_of _Work Combo Used to select Nature_of _Work
Minimum_Wage Textfield Used to enter Minimum_Wage
Allowance Textfield Used to enter Allowance
Catering Management
Bonus/day Textfield Used to enter Bonus/day

Leave with Wage/day Textfield Used to enter Leave with Wage/day
Washing Allowance Textfield Used to enter Washing Allowance
SRK Allowance Textfield Used to enter SRK Allowance
PF Textfield Used to enter the PF
ESI Textfield Used to enter the ESI
SUBMIT Button Redirects to SubmitCurrent_Year_Settings
RESET Button Redirects to ResetCurrent_Year_Settings
REGISTRATION PAGE:

Name Textfield Used to enter the Name
Sex RadioButton Used to select Gender
Date_of_Birth DateTimePicker Used to select the Date
E-mail Textfield Used to enter E-mail
Address Textfield Used to enter the Address
User_Type Combo Used to select User_Type
User_Name Textfield Used to enter User_Name
Password Textfield Used to enter Password
Confirm_Password Textfield Used to enter Confirm_Password
SUBMIT Button Redirects to SUBMIT Registration Form
RESET Button Redirects to RESET Registration Form
DELETE Button Redirects to DELETE Registration Form
4. TESTING
LOGIN PAGE:
Catering Management
SI.NO User Action Expected Result Observed Test Result

Output
1. User does not Login Failed Login Failed PASS
enter any value
and clicks login.
2. User enters Login Failed Login Failed PASS
username but
not password
and clicks login
password but
not username
and cliks login
wrong
username or
wrong password
5. On Successful The user’s The user’s PASS
Login welcome page welcome page
loads. loads.
6. Unsuccessful The control The control PASS
Login stays on the stays on the
login page itself login page itself
REGISTRATION PAGE:
Catering Management
Catering Management

Output
1. User doesn’t Messagebox Messagebox PASS
enter the value appears asking appears asking
in one or more user to enter user to enter
fields. the details. the details.
2. User doesn’t Messagebox Messagebox PASS
enter a name, appears asking appears asking
date of birth, user to enter user to enter
address the details. the details.
3. User enters Messagebox Messagebox PASS
different appears asking appears asking
password and user to enter user to enter
confirm the correct the correct
password Password. password.
4. User enters all The Welcome The Welcome PASS
the fields and Page loads Page loads
clicks submit
MASTER PAGE:
Catering Management

Output
1. User clicks on The The PASS
Purchase Details corresponding corresponding
page loads page loads
Inventory corresponding corresponding
Customer corresponding corresponding
Food sales corresponding corresponding
Employee corresponding corresponding
Accounts corresponding corresponding
Configuration corresponding corresponding
Exit corresponding corresponding
Catering Management
SUPPLIER DETAILS PAGE:
SI.NO User Action Expected Result Obseved Result Test Result

1. User doesn’t Message box Message box PASS
enter any appears asking appears asking
Catering Management
content the user to the user to

enter particuler enter particuler
details details
2. User enters all Message box Message box PASS
the fields and will be displayed will be displayed
clicks add
VIEW SUPPLIER:

1. User selects Message box Message box PASS
delete appears asking appears asking
do you want do you want
delete delete
TO VIEW BILLS:
Catering Management

1. User clicks on All Displays Displays PASS
Suppliers Suppliers
Information Information
2. User clicks on Message box Message box PASS

billlno enters displays stock not displays stock
wrong number found not found
delete displays do you displays do you
want to delete want to delete
Catering Management
ADD BILLS:

details details
2. User enter all Message box Message box PASS
the fields will be displayed will be displayed
3. User clicks on The data is The data is PASS
reset button cleared cleared
add bill appears bill appears bill
already exist already exist
Catering Management
SUPPLIER PAYMENTS PAGE:

Catering Management

details details
3. User clicks on All the fields are The data is PASS
reset button cleared erased
4. Clicks on Total Total PASS
outstanding oustanding will oustanding will
form be displayed be displayed
STOCK PAGE:
Catering Management

details details
submit will be displayed will be displayed
4. User clicks on All the fields are The data is PASS
reset button cleared erased
Catering Management

details details
2. User enter the Report will be Report will be PASS
month and year generated generated
Catering Management
DAILY STOCK UPDATION:

Catering Management

details details
2. User enters Message box Message box PASS
same item name item already item already
exist exist
the fields and stock updated stock updated
clicks on update
4. If user enters Message box Message box PASS
more than stock stock not found stock not found
item
VIEW STOCK:
Catering Management

print appears asking appears asking
the user to the user to
enter month enter month
2. User clicks on Message box do Message box do PASS
delete you want to you want to
delete delete
CUSTOMER DETAILS PAGE:
Catering Management

details details
the fields customer details customer details
updated updated
successfully successfully
3. User clicks on All the fields are All the fields are PASS
FOOD MENU:
Catering Management

details details
the fields New items New items
added added
succesfully succesfully
the menu which menu already menu already
is already exist exist
present
4. If User clicks on Message box Message box PASS
SL.no or other Record deleted Record deleted
field
Catering Management
FOOD COUPON:
Catering Management

details details
the fields Coupon rates Coupon rates
saved saved
delete you really want you really want
to delete to delete
DAILY SALES:
Catering Management

month month
the fields Daily sales Daily sales
updated updated
EMPLOYEE DETAILS PAGE:
Catering Management
Catering Management

details details
the fields Employee Employee
record added record added
the employee Employee Employee
which is already already exist already exist
present
5. User clicks on All Employee All Employee PASS
View Information wil Information wil
be displayed be displayed
Delete you really want you really want
to delete to delete
EMPLOYEE PAYROLL:
Catering Management
Catering Management
Catering Management
PRINTING EMPLOYEE PAYROLL:

content the Please select the Please select
the month the month
2. User enters all Employee Employee PASS
the fields payroll payroll
generatyed generatyed
3. User clicks on Employee salary Employee salary PASS
print button report report
generated generated
MONTHLY FOOD BILLS:
Catering Management
Catering Management

content the Please select the Please select
the month the month
2. User click on Message box Message box PASS
add displays are you displays are you
sure add the bill sure add the bill
3. User change the Message box No Message box No PASS
month and click sales found sales found
add
4. User change the Message box No Message box No PASS
month and click sales found sales found
add
RECEIPT PAGE:
Catering Management

add appears no appears no
record found record found
2. User select the Message box Message box PASS
month and click receipts added receipts added
add
3. User select the Message box Message box PASS
month and click receipts already receipts already
add added added
EXPENDITURE PAGE:
Catering Management

details details
2. User enters data Message box Message box PASS
appears appears
expenditure expenditure
details added details added
3. User click on All data cleared All data cleared PASS
reset
MONTHLY SALES:
Catering Management

1. User clicks on Message box no Message box no PASS
print records records
2. User selects the Data is shown Data is shown PASS
month and click
generate
generate please select please select
the month the month
CONFIGURATION PAGE:
Catering Management

details details
the fields Current year Current year
settings are settings are
updated updated
5. USER MANUAL
Catering Management
LOGIN
This is the login page for all the users using this system. This page is used by the users to
log into his/her account. Each user has his/her own User Name and Password to login into
Master page. It contains a text box and a password field for entering the username and
password of the user. Only if the user enters the username and the password correctly and
then clicks the login button he/she is redirected to Master page of Catering Management.
MASTER PAGE
This is master page, here we have purchase details which redirects to Supplier forms,
Inventory which redirects to stock forms, customer which redirects to customer form, food
sales which redirects to coupon and food sales, employee which redirects to new employee
and employee payroll, accounts which redirects to monthly and yearly and other forms,
Catering Management
configuration which redirects to current year settings and user creation forms, help which
redirects to word file, and exit will close the application.
REGISTRATION PAGE
Registration page is to login the new staff or manager.Registration page contains textbox and
buttons which as to be filled by different users who are operating the application. At right
side data grid view displays the exixsting users.
SUPPLIER DETAILS PAGE
This page is used to enter any new suppliers, And also used to view the existing suppliers by
clicking view button. It is also possible to reset the Supplier details which is already entered.
Catering Management
Here, Add button is used to add the existing suppliers. The supplier details is added and
stored in the database. View button is used to view the existing Suppliers.Reset button is used
to clear the bill details entered.
VIEW SUPPLIER
This page is used to view the suppliers details. Here, the supplier details are viewed in grid
format. Delete button is used to delete the existing supplier details from the list .
VIEW BILLS
This page is used to view the Supplier bills. Here the Supplier Bills are used to display by
using Search By Option. The Bills are Viewed by selecting the bill_no, Supplier_name and
bill_date.
Catering Management
ADD BILLS
This page is used to add the supplier bills. The Supplier_name, Bill_no, Bill_date, Total
amount are entered. Add_bill button is used to add the supplier _bills. Reset button is used to
clear the entered bill details.
SUPPLIER PAYMENT
This page is used to keep track of supplier payments. Here supplier_name, bill_no,
Total_amount, Amount paid is entered to calculate the supplier_payments. Balance is
calculated automatically. Add button is used in adding the supplier_payments. Reset button is
used to clear the entered supplier_payments details.
STOCK PAGE
Catering Management
This page is used to enter the new food items. Here the date, items_name, quanity, measure
and amount is entered and the items are submitted. View button is used to view the items.
Reset button is used to clear the entered stock details.
DAILY STOCK UPDATION
This page is used to update daily stocks. Here date, items name, used_quantity , measure are
entered and updated. This is updated daily.
VIEW STOCK
Catering Management
This page is used to view the stock. Here the month and year is selected to display the stocks.
The stocks are displayed in grid manner. The print button is used for printing the stock page.
Delete option is required for deleting a particular item.
CUSTOMER PAGE
This page is used to enter the details of present customer. Customer_name, address,
phone_no, mobile_no, email_id are ented and updated. Here the customer details are
maintained. For present MRPL is the only customer. Reset button is used to clear the entered
customer details.
FOOD MENU
This page is used to enter the food items. Here the menu name, cost of the food is entered and
submitted using submit button. Reset button is used to clear the entered food details.
Catering Management
VIEW MENU
This page is used to view the new items. The food items are displayed in grid manner. Here
the menu name and its cost are displayed. Delete button is used to delete a particular food
menu.
COUPON DETAILS
Catering Management
This page is used to enter the different coupon type and food cost and it also displays the
different coupon types. Here the coupon type and food cost is entered and saved. The saved
details will be displayed in the data grid view. Reset button is used to clear the entered
coupon details. The coupon type and cost can be deleted by delete link in the grid view itself.
DAILY SALES
This page is used to update the daily sales. Here the month is selected to display the daily
sales and it is also updated. Daily sales details is viewed in the data grid view. Here the date,
dinner, lunch, mini dinner,snacks, Sunday special and amount are displayed.
Catering Management
EMPLOYEE DETAILS
This page is used to enter the employee details. Here employee name, nature of work, punch
card number, address, contact number, date of join are entered and are added. Reset button is
used to clear the entered employee details.
VIEW EMPLOYEES
This page is used to view the employees. The employee details are viewed in this page with
grid view. Here employee name, punch card number, nature of work are viewed. Thre is also
delete option in the grid view, which is used to delete the selected employee detail.
EMPLOYEE PAYMENT
Catering Management
This page is used to generate the employee payroll. The payments of the employees are
generated. Here the month and year must be selected to generate the payroll. Generate payroll
button is used to generate the employee payroll. Add button is used in adding the employee
payment. Print button is used for printing the payment.
EMPLOYEE PAYMENT REPORT
Catering Management
This page is used to print the report. To print this page a printer is must. Here the employee
payment report is generated for particular month and year.
MONTHLYFOODBILLS
This page is used generate the monthly food bills. Here bill_no, bill_date, month and year are
entered to generate monthly food bills. Generate button is used to generate food bills. Add
button is used to add food bills. Print button is used in printing food bills.
RECEIPT
Catering Management
This page is used to enter the receipt information.Here the receipt_no, receipt_date, month
and year are entered to display the receipt information. Add button is used to add the receipt.
Print button is used in printing the receipts.
MONTHLY SALES
This page is used to generate the monthly food bills. Here month and year are selected to
generate the monthly sales. Generate button is used to generate the monthly food sales,
expenditure and total budget.
CONFIGURATION PAGE
This page is used to set the salary. Here the year, nature of work, minimum wage, Allowance,
Bonus, leave with wage, washing allowance, SRK allowance, PF, ESI are setted before and
submitted. Reset button is used to clear the entered year settings.
Catering Management
CONCLUSION
The Project “Catering Management” was successfully tested and
implemented under windows XP or above. This software has been
developed to satisfy the needs of the company.
The system developed is a lot user friendly and interactive. The
system is found to be really beneficial for the concerned aspects. The
performance of the software is provided efficiently. This software has
been tested with all possible sample data and was found to function
efficiently.
Thus the new software eliminates the drawbacks of the existing
process. The application developed is futuristic of secure. The user
may add any modules in future without affecting the current project.
Catering Management
SCOPE FOR FUTURE

ENHANCEMENT
BOOKS
PankajJalote, An Integrated Approach To Software Engineering, 4ed,
Publication: Narosa Publishing House.
Catering Management
BIBLIOGRAPHY

Catering Management System Project Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Catering Management System Project Report

Uploaded by

Copyright:

Available Formats

Catering Management

Section Description Page No

2 Software Requirement Analysis And 9-17

5 User Manual 76-87

7 Scope for Future Enhancement 89

SOFTWARE REQUIREMENTS ANALYSIS AND SPECIFICATION

2.2 Overall Description..............................................................11

2.3 Specific Requirements.........................................................13

2.4.2 Safety Requirements......................................................

3.1 Data Flow Diagram...............................................................

7. SCOPE FOR FURTHER ENHANCEMENT......................

1.3 Project details

The main objective of the Catering Management is to develop a software

Front End: Visual Basic.net

Vb.net is the improved version and contains improved features such as

Visual Basic.net is composed of three primary entities:

Back End: SQL (Structured Query Language)

Microsoft SQL Server is a relational database server, developed by Microsoft:

Operating System:Windows Xp or above

Future scope of the project:

2. Software Requirement Specification

SRS – is a complete description of the behaviour of a system to be developed. It

This document is meant to serve as a guide to the developer on one hand

go through the formal change approval process. This document contains

2.1.3 Definitions, Acronyms, Abbreviations

SRS - Software Requirements specifications

The major features of the Catering Management are organised

2.2.3 User classes and Characteristics

2.2.5 Assumption and dependencies

2.3.1External Interface Requirements

2.3.1.1 User Interface

The System is a GUI (Graphical User Interface). It consists of

2.3.1.2 Hardware Interface

2.3.1.3 Software Interface

Software requirements are:

Operating System : Windows XP/2000/vista/7

2.3.2 Functional Requirements:

2.3.2.1 Input Requirements

2.3.2.1.1 Purchase Details

Introduction: Stores supplier information

Introduction: Stores stock information

2.3.2.1.3 Employee Transaction

Introduction: Stores employee information

Monthly salary will be calculated for the employees.

2.3.2.1.4Food Sales Information

Introduction: Stores sales details of the industry.

2.3.2.1.5 Receipts information

Introduction: Stores food Bill payment details.

Maintained and the final reports will be sent to

2.3.2.1.6 Reports information

Expenditure, Food bill reports, Receipts, Employee

2.3.3 Document conventions.

2.3.4 Intended User and Reading suggestions

2.3.5 User Documentation

2.4 Other Non-functional Requirements

The system is supposed to be having good memory space and a

To avoid data loss backups can be done regularly.

2.4.3 Security Requirements

Authenticated users are able to access the system.

2.4.4 Software Quality Attributes

2.5 Other Requirements:

3.1 Data Flow Diagram

CONTEXT FLOW DIAGRAMS

Context diagram is a dataflow diagram showing data flows between a