magic final

99
PROJECT REPORT ON Restaurant Management System SUBMITED BY BY AASHISH K. DHIVAR Under the Guidance of Prof. Sumathi Rajkumar SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR QUALIFYING EXAMINATION (B.Sc. INFORMATION TECHNOLOGY, SEMESTER-VI EXAMINATION) Seat no: BATCH 2011 - 2012 UNIVERSITY OF MUMBAI Nirmala Memorial Foundation College of Commerce and Science 90 Feet Road,Thakur Complex,Kandivali(E),Mumbai-400 101

Upload: aashish-dhivar

Post on 21-Apr-2015

113 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Magic Final

PROJECT REPORT

ON

Restaurant Management System

SUBMITED BY

BY

AASHISH K. DHIVAR

Under the Guidance of

Prof. Sumathi Rajkumar

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR QUALIFYING EXAMINATION (B.Sc. INFORMATION TECHNOLOGY,

SEMESTER-VI EXAMINATION)

Seat no:

BATCH 2011 - 2012

UNIVERSITY OF MUMBAI

Nirmala Memorial Foundation College of Commerce and Science 90 Feet Road,Thakur Complex,Kandivali(E),Mumbai-400 101

Page 2: Magic Final

4 | P a g e

Restaurant Management System

PREFACE

Computer systems have become the heart of daily activities and a major factor in various

aspects of our life. Just as knowledge of computers and computer programming has become a basic necessity in today’s information oriented society, so has the design of automated business systems.

This is a report for first stage of our project. This stage was aimed at meeting all the preliminary requirements of the Restaurant, “RESTAURANT MANAGEMENT SYSTEM”.

The material provided in this report is the framework for the system, which includes PERT chart, Use case Diagram and flow chart. It includes introductory material and related topics.

The Material provided in this report is the frame work for the system, which includes There is no Restaurant with the name ‘Magic’. This name has been used only for the purpose of project work.

Any suggestions and constructive comments that will help the project to improve are heartily welcome.

AASHISH K. DHIVAR

Page 3: Magic Final

5 | P a g e

Restaurant Management System

ACKNOWLEDGEMENT

Success of an individual is possible only when others are supporting him or her. The

completion of this study would not have been possible without the help of teachers, well-

wishers and others.

First of all, we praise and thank the Lord Almighty for his abundant grace and

blessings he had showered throughout the study and our life.

With great pleasure we express our deep sense of gratitude to Dr. T. P. Mathu Nair,

Principal Nirmala Memorial Foundation College of Commerce and Science, Ms.Manasvi

Shah, Bsc (I.T) coordinator for the valuable guidance, suggestions and support for

completing the project work.

I would like to extend our sincere thanks to our beloved guide Prof. Sumathi Rajkumar

for providing facilities, valuable suggestions and constant supervision for the successful

completion of the project.

Last but not least, we extend our sincere thanks to all other faculty members of IT &

COMPUTER SCIENCE DEPARTMENT and our friends for their support and

encouragement.

AASHISH K. DHIVAR

Page 4: Magic Final

6 | P a g e

Restaurant Management System

INDEX

Sr. No. Topic Page No. 1. Preliminary Investigation 1.1 Organizational Overview 7 1.2 Description of System 8 1.3 Limitation of present System 8 1.4 Proposed System & Advantages 9 1.5 Feasibility Study 10 1.5 Technology and Tools 11 1.6 SDLC 20 1.7 Stakeholders 23 1.8 Gantt Chart 24 2. System Analysis 2.1 Fact Finding Technique 26 2.2 Event Table 27 2.3 Use Case Diagram 29 2.4 Entity Relationship Diagram 31 2.5 Activity Diagram 33 2.6 Class Diagram 36 2.7 Object Diagram 38 2.8 Sequence Diagram 40 2.9 Collaboration Diagram 43 2.10 State Diagram 48 3. System Design 3.1 Converting ERD to Tables 54 3.2 Design Class Diagram(with UI & Persistent Classes) 57 3.3 Component Diagram 59 3.4 Package Diagram 61 3.5 Deployment Diagram 63 3.6 Program Flow Charts & System Flow Charts 65-68 3.7 Structure Charts 69 4. System Coding 4.1 Menu Tree 73 4.2 List Of Tables with Attributes 74 4.3 Program Description 78 4.4 Validation 85 4.5 Test Cases, Test Data and Test Results 81 4.6 Screen Layouts & Report Layouts 83 5. Future Enhancements 107 6. Reference and Bibliography 109 7. Conclusion 111

Page 5: Magic Final

7 | P a g e

Restaurant Management System

PRELIMINARY

INVESTIGATION

Page 6: Magic Final

8 | P a g e

Restaurant Management System

Preliminary Investigation

Organization Overview

Name of Company: MAGIC RESTAURANT Name of Proprietor: Mr xyz Address: abc History: The Restaurant was established in the year 1993. Contact No. : 0222xxxxxx \

Page 7: Magic Final

9 | P a g e

Restaurant Management System

Description of the System

LIMITATION OF PRESENT SYSTEM

The present System of “MAGIC RESTAURANT” possesses lots of limitations in their system.

The Orders placed by the customer and the delivery details for delivery is accepted manually

due to which details can be misplaced or misinterpreted.

There is no security anyone can access the database and view records and Customer’s details

Since the records are saved manually it is difficult to arrange those for a longer time

The present System is a lot time consuming.

There is no provision for report generation which help to maintain company’s record monthly.

Since the system is manual risk of losing or misplacement of order is possible.

The Current System is not at all user friendly. Since he has to search for records and items and their estimated prices for developing bills which should be automated.

Page 8: Magic Final

10 | P a g e

Restaurant Management System

Proposed System

The proposed System is user Friendly and does not require much knowledge of Computers.

Various Validations are included for determining of correct information’s.

Annual reports and bill generation are implemented.

The calculations for generating bills and other services of adding automated rates various

products including the V.A.T are available.

The System will be developed taking user’s time; effort as well as user authorization to security is implemented.

Advantages of Proposed System

It is more efficient and accurate in compare to the current System. The Calculations of bills will be more accurate and error-free. No un-authorized access to the system would be allowed. Validations would led to the correctness of information’s.

The system would be more users friendly and easy to operate on.

Page 9: Magic Final

11 | P a g e

Restaurant Management System

Feasibility Study

Feasibility Study is the measure and the study of how beneficial the developed system would be to the organization. The project feasibility is concern with expected benefits .An important outcome of the preliminary investigation is the destination that the proposed system is feasible. The feasibility study of the system includes:

Schedule Feasibility Economical Feasibility Operational Feasibility Technical Feasibility

Schedule Feasibility:- The likelihood of a project being completed within its scheduled time frame is schedule feasibility. According to mine discussion and calculation with client the total time required for complication of project would be 4-5 months. This include time required for coding, designing, debugging and testing, etc. for completion of project, I have decided to work on project for around 2-3 hours a day. The time period can be extended as per requirement. Economical Feasibility:- Economical feasibility is analysis of a project’s cost and revenues in an effort to determine whether or not it is logical and possible to complete. The organization will benefits from this system in terms of money and time. The development cost would include travelling cost, communication cost and the operational cost would include the license for the Visual Studio.Net 2008 IDE and MS SQL Server 2005. Operational Feasibility:- Operational Feasibility is a measure of how well a proposed system solves the problem, and takes advantages of the opportunities during scope definition and how it satisfies the requirements identified in the requirements analysis phase. As the current system is manual, it needs to be upgraded. The new system will therefore be used in the organization as a substitute for the manual one. Based on the type of users he/she will be provided with some write’s operation in the system. Technical Feasibility:- It is based on computer hardware and networking software which would be available or the proposed system. Additional peripheral device are required which are available with the unit. The requirements for the proposed system can be easily made available by the user within the estimated cost which is minimal and of better usage.

Page 10: Magic Final

12 | P a g e

Restaurant Management System

The Software used for the development of proposed system is: Front End: - Visual Studio 2008 Using VB.Net. Back End: - SQL Server 2005.

The Hardware requirements are: Operating System:-windows 2000/xp/vista/7 Processor:-Pentium 4,Dual Core,i3,i5,i7 RAM:1GB Hard Disk:- 1GB

Page 11: Magic Final

13 | P a g e

Restaurant Management System

TECHNOLOGIES AND TOOLS

Page 12: Magic Final

14 | P a g e

Restaurant Management System

MICROSOFT VISUAL STUDIO 2005 or 2008

Microsoft Visual Studio 2008 Standard Edition

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silver light.

Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designer, and database schema designer. It accepts plug-ins that enhance the functionality at almost every level—including adding support for source-control systems (like Subversion and Visual SourceSafe) and adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer).

Visual Studio supports different programming languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-specific service exists. Built-in languages include C/C++ (via Visual C++), VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010). Support for other languages such as M, Python, and Ruby among others is available via language

Page 13: Magic Final

15 | P a g e

Restaurant Management System

services installed separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Individual language-specific versions of Visual Studio also exist which provide more limited language services to the user: Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++.

Microsoft provides "Express" editions of its Visual Studio 2010 components Visual Basic, Visual C#, Visual C++, and Visual Web Developer at no cost. Visual Studio 2010, 2008 and 2005 Professional Editions, along with language-specific versions (Visual Basic, C++, C#, J#) of Visual Studio Express 2010 are available for free to students as downloads via Microsoft's Dream Spark program.

Page 14: Magic Final

16 | P a g e

Restaurant Management System

SQL SERVER

Microsoft Sql Server 2005 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 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).

SQL Server 2005 (codename Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; Common Language Runtime (CLR) integration was a main feature with this edition, enabling one to write SQL code as Managed Code by the CLR. SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML.

For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and better error recovery systems. Data pages are check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework

Page 15: Magic Final

17 | P a g e

Restaurant Management System

Microsoft Visio

Microsoft Visio

Visio began as a standalone product produced by Shapeware Corporation; version 1.0 shipped in 1992. Just before 1.0 shipped, Shapeware Corporation changed their name to Visio Corporation to take advantage of market recognition and related product equity Microsoft acquired Visio in 2000, re-branding it as a Microsoft Office application, like Microsoft Project; however, it has never been included in any of the Office suites. Microsoft included a Visio for Enterprise Architects edition with some editions of Visual Studio .NET 2003 and Visual Studio 2005.

Along with Microsoft Visio 2002 Professional, Microsoft introduced Visio Enterprise Network Tools and Visio Network Center. Visio Enterprise Network Tools was an add-on product that enabled automated network and directory services diagramming. Visio Network Center was a subscription-based website where users could locate the latest network documentation content and exact-replica network equipment shapes from 500 leading manufacturers. The former has been discontinued, while the latter's shape-finding features are now integrated into the program itself. Visio 2007 was released on November 30, 2006.

Page 16: Magic Final

18 | P a g e

Restaurant Management System

SOFTWARE DEVELOPMENT LIFE CYCLE

Software Development life cycle is an overall process of developing information system through a multi-step process from investigation of initial requirement through analysis, design, implementation and maintenance.

There are different Models

Waterfall Spiral Win win spiral Prototype Incremental

Page 17: Magic Final

19 | P a g e

Restaurant Management System

WATERFALL MODEL The waterfall model is a popular version of the systems development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential.

Waterfall Model

Waterfall development has distinct goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the same with waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back.

Now Let us look at the different phases of Waterfall model

Requirement Analysis and Software Definition This is the first phase of waterfall model which includes a meeting with the customer to understand his requirements. This is the most crucial phase as any misinterpretation at this stage may give rise to validation issues later. The software definition must be detailed and accurate with no ambiguities. It is very important to understand the customer requirements and expectations so that the end product meets his specifications.

System Design The customer requirements are broken down into logical modules for the ease of implementation. Hardware and software requirements for every module are identified and designed accordingly. Also the inter relation between the various logical modules is

Page 18: Magic Final

20 | P a g e

Restaurant Management System

established at this stage. Algorithms and diagrams defining the scope and objective of each logical model are developed. In short, this phase lays a fundamental for actual programming and implementation.

System Implementation This is the software process in which actual coding takes place. A software program is written based upon the algorithm designed in the system design phase. A piece of code is written for every module and checked for the output.

System testing The programmatically implemented software module is tested for the correct output. Bugs, errors are removed at this stage. In the process of software testing, a series of tests and test cases are performed to check the module for bugs, faults and other errors. Erroneous codes are rewritten and tested again until desired output is achieved.

System Deployment and Maintenance This is the final phase of the waterfall model, in which the completed software product is handed over to the client after alpha, beta testing. After the software has been deployed on the client site, it is the duty of the software development team to undertake routine maintenance activities by visiting the client site. If the customer suggests changes or enhancements the software process has to be followed all over again right from the first phase i.e. requirement analysis. This is the biggest shortcoming of the waterfall model. Thus, waterfall model is easy to implement and more often than not produces desired results. The inter-dependence of waterfall model phases may lead to developmental issues, if a systematic approach is not followed at each step. However, in spite of these shortcomings, waterfall model is adopted all across the world. Advantages

It is useful where requirement are fixed It is useful when the work is to proceed to complete in line manner. It is useful for the development of small project It is easy to develop the system using the SDLC. It is disciplined approach and document-driven.

Disadvantages

Delivered product may not meet client’s needs It is often difficult for the customer to state the entire requirement explicitly. The time spend is more to require the final product. This universal model may not be feasible for large scale product.

Page 19: Magic Final

21 | P a g e

Restaurant Management System

Stakeholders Stakeholders are anyone who has an interest in the project. Project stakeholders are individuals and organizations that are actively involved in the project, or whose interests may be affected as a result of project execution or project completion. They may also exert influence over the project’s objectives and outcomes. The project management team must identify the stakeholders, determine their requirements and expectation, and, to the extent possible, manage their influence in relation to the requirements to ensure a successful project. The people involved in the Project development are:

1. Developer:

Here in this project the Developer is Mr. Aashish K. Dhivar i.e. myself who is developing this project.

2. Organization Owner: Is the person to whom the project is to be given and who will be using the `

application?

3. Organization Manager: Here the Employee is the Company Manager who might use the application.

Page 20: Magic Final

22 | P a g e

Restaurant Management System

GANTT CHART

A Gantt chart is a type of bar chart, developed by Henry Gantt, that illustrates a project schedule. Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements comprise the work breakdown structure of the project. Some Gantt charts also show the dependency (i.e., precedence network) relationships between activities. Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical "TODAY" line as shown here.

Although now regarded as a common charting technique, Gantt charts were considered revolutionary when first introduced. In recognition of Henry Gantt's contributions, the Henry Laurence Gantt Medal is awarded for distinguished achievement in management and in community service. This chart is also used in Information Technology to represent data that has been collected.

Gant Chart:-

Page 21: Magic Final

23 | P a g e

Restaurant Management System

PERT CHART PERT is a method to analyze the involved tasks in completing a given project, especially the time needed to complete each task, and to identify the minimum time needed to complete the total project. PERT was developed primarily to simplify the planning and scheduling of large and complex projects. It was developed for the U.S. Navy Special Projects Office in 1957 to support the U.S. Navy's Polaris nuclear submarine project.[2] It was able to incorporate uncertainty by making it possible to schedule a project while not knowing precisely the details and durations of all the activities. It is more of an event-oriented technique rather than start- and completion-oriented, and is used more in projects where time, rather than cost, is the major factor. It is applied to very large-scale, one-time, complex, non-routine infrastructure and Research and Development projects. An example of this was for the 1968 Winter Olympics in Grenoble which applied PERT from 1965 until the opening of the 1968 Games.[3]

This project model was the first of its kind, a revival for scientific management, founded by Frederick Taylor (Taylorism) and later refined by Henry Ford (Fordism). DuPont's critical path method was invented at roughly the same time as PERT.

PERT CHART:-

Page 22: Magic Final

24 | P a g e

Restaurant Management System

SYSTEM ANALYSIS

Page 23: Magic Final

25 | P a g e

Restaurant Management System

Fact Finding Techniques

The Fact Finding methods adopted are as follows: Interview: An interview with the owner Mr. xyz who is the owner of the unit, “Magic Restaurant” was conducted. The Questions related to the unit and the entire procedure of the current system was asked. Some of the related Questions are: What is your system all about? Which software are you currently using? How you are finding it to use? How you are maintaining the Order Details? How you are maintaining the Delivery Details? How you are maintaining the Reports? How the Bill is generated?

Page 24: Magic Final

26 | P a g e

Restaurant Management System

EVENT TABLE

Page 25: Magic Final

27 | P a g e

Restaurant Management System

Event Table No. Event Trigger Source Activity Response Destination

1. Login Enter Login Details & click Ok

Admin Verifying Login details

Login Successfully

Admin

2. Change Password

New Password

Admin Enter New Password

Password Changed

Admin

3. Logout Logout Admin Logging out of the System

Logout Successfully

Admin

4. Add Stock Enter Stock Details

Admin Entering Stock

Details

Data Entered Admin

5. View Stock View Stock Details

Admin Displaying Stock

Details

Stock Details Viewed

Admin

6. Add Order Enter Order Details

Admin Entering Order Details

Order Saved Admin

7. Delivery Enter Delivery details

Admin Entering Delivery Details

Customer Order Saved

Admin

8. Bill Generation

Enter Bill Details

Admin Generating Bill

Bill Generated Admin

9. Stock Report Enter Purchase Report Details

Admin Generating Stock Report

Stock Report Generated

Admin

Page 26: Magic Final

28 | P a g e

Restaurant Management System

USE-CASE DIAGRAM

Page 27: Magic Final

29 | P a g e

Restaurant Management System

UseCase Diagram

Admin

System User

Login

Logout

Change Password

Stock Details

Purchase Stock

Add Stock

View Stock

Details

Enter Employee Details

Enter Order Details

Enter Delivery Details

Reports

Generate Bill Report

Generate Stock Report

Page 28: Magic Final

30 | P a g e

Restaurant Management System

ENTITY RELATIONSHIP DIAGRAM

Page 29: Magic Final

31 | P a g e

Restaurant Management System

Entity Relationship Diagram

M M 1 1 1 1 M M M M M M 1

Customer

Customer Name

Address Phone No

Places an

order Manager

Adds

Stock Price

Name

Id

Category

Size

Checks availability

Stock Details

Search

Stock Details

Buys product

Employee

Id Name Phone No

Address Salary

Purchase

P_Id Price

Quantity

Item Name

Order

Generates Bill

Bill

Total price

Payment

Order Details

Category

Order Details

Grand Total

Bill No

adds

Orders

Page 30: Magic Final

32 | P a g e

Restaurant Management System

ACTIVITY DIAGRAM

Page 31: Magic Final

33 | P a g e

Restaurant Management System

ACTIVITY DIAGRAM

Order:-

Customer Admin System Yes No

Enter Login Details

Login Form

Main Form

Checks availability

View Stock Form

Takes Order Customer Places an

Order

Verifies Order Details

Order Form Accepts the Order

Receives Details

Save Payment Details

Receives Payment

Makes Payment

Receives Bill Dispatches Bill Saves & Generates Bill

Page 32: Magic Final

34 | P a g e

Restaurant Management System

ACTIVITY DIAGRAM

Delivery:-

Customer Admin System

Enter Login Details

Login Form

Main Form

Delivery Form Customer Gives Delivery Details

Receives Details

Save Payment Details

Receives Payment

Makes Payment

Receives Bill Dispatches Bill Saves & Generates Bill

Verifies Order Details

Page 33: Magic Final

35 | P a g e

Restaurant Management System

CLASS DIAGRAM

Page 34: Magic Final

36 | P a g e

Restaurant Management System

CLASS DIAGRAM

Frm_Login -UserName -Password +Login()

Main Form +File +Data Entry +Transaction +Tools +View

View Stock -Search Stock -Stock Details +Add() +Edit() +Delete()

Add Stock -Id -Name -Quantity -Price -Category +Save() +View()

Purchase -Id -Item Name -Quantity -Price +Add() +Update() +Delete()

Employee -Id -Name -Address -Phone No -Salary +Add() +Edit() +Delete()

Order - Category -Order Product -Quantity -Price -Total -Payment -Grand Total +Add() +Delete() +Order()

Delivery -Customer Name -Address -Phone No +Delivery() +Edit() +Delete()

Bill -Bill No -Order Details -Grand Total +Print()

Page 35: Magic Final

37 | P a g e

Restaurant Management System

OBJECT DIAGRAM

Page 36: Magic Final

38 | P a g e

Restaurant Management System

OBJECT DIAGRAM

* * 1 1 * 1 1 * 1 1 1 1 1 * 1 1 1 1 1 *

:Frm_Login

:View Stock

:Purchase :Bill

:Add Stock

:Delivery

:Main Form

:Order

:Employee

Page 37: Magic Final

39 | P a g e

Restaurant Management System

SEQUENCE DIAGRAM

Page 38: Magic Final

40 | P a g e

Restaurant Management System

SEQUENCE DIAGRAM

Admin Login Main Form Stocks Order Delivery Bill Login Details

Validate to access login()

Access to main Access to stock

add() logout() edit() delete() search() Selecting

item

Access to order

Generating bill

Bill () Delivery Order

Access to delivery

delete()

delivery()

add()

edit()

Page 39: Magic Final

41 | P a g e

Restaurant Management System

Admin Login Main Form Purchase Employee

Login Details login ()

Validate to

Logout()

add()

edit()

delete()

add()

edit()

delete()

Page 40: Magic Final

42 | P a g e

Restaurant Management System

COLLABORATION

DIAGRAM

Page 41: Magic Final

43 | P a g e

Restaurant Management System

COLLABORATION DIAGRAM

Login Form Login_Load () btn_loginClick () Add Stock Form Add_Load () Btn_save_click () Btn_View_click ()

Admin

: Login Form

: Login

Admin

: Add Form

: btnSave

: btnView

Page 42: Magic Final

44 | P a g e

Restaurant Management System

View Form View_Load () Btn_Add_Click () Btn_Edit_click () Btn_Delete_Click () Order Form Order_Load () Btn_Add_Click () Btn_Delete_Click () Btn_Order_Click()

Admin

: View Form

: btn_Add

:btn_Edit

:btn_Delete

Admin

: btn_Delete

: btn_Add

: Order Form

: btn_Order

Page 43: Magic Final

45 | P a g e

Restaurant Management System

Delivery Form Delivery_Load () Btn_Delivery_Click () btn_Edit_Click () btn_Delete_Click () Purchase Form Purchase_Load () Btn_Add_Click () Btn_Edit_Click () Btn_Delete_Click ()

: Delivery Form

: btn_Delivery

: btnEdit

: btnDelete

Admin

Admin

: Purchase Form

: btnAdd

: btnEdit

: btnDelete

Page 44: Magic Final

46 | P a g e

Restaurant Management System

Employee Form Employee_Load () Btn_Add_Click () Btn_Edit_Click () Btn_Delete_Click () Bill Form Bill_Load () Btn_Print_Click ()

Admin

: Employee Form

: btnAdd

: btnEdit

: btnDelete

Admin

: Bill

: btnPrint

Page 45: Magic Final

47 | P a g e

Restaurant Management System

STATE DIAGRAM

Page 46: Magic Final

48 | P a g e

Restaurant Management System

STATE DIAGRAM Login Form Login Load btnlogin Add Stock Form AddLoad btnSave btnView

AcceptValues Existing Completion

AcceptValues Existing Completion

View Form

Page 47: Magic Final

49 | P a g e

Restaurant Management System

View Form ViewLoad btnDelete Purchase Form btnAdd btnEdit btnDelete

Accept Values

Existing

Completion

Does Not Exists

Completion

Existing

Accept Values

Does Not Exists

Page 48: Magic Final

50 | P a g e

Restaurant Management System

Employee Form btnAdd btnEdit btnDelete Order Form btnAdd btnOrder btnDelete

Accept Values

Existing

Completion

Does Not Exists

Accept Values

Existing

Completion

Does Not Exists

Page 49: Magic Final

51 | P a g e

Restaurant Management System

Delivery Form btnAdd btnDelivery btnEdit btnDelete Bill Form BillLoad btnPrint

Accept Values

Existing

Completion

Does Not Exists

Accept Values

Existing

Completion

Page 50: Magic Final

52 | P a g e

Restaurant Management System

System Design

Page 51: Magic Final

53 | P a g e

Restaurant Management System

CONVERTING ERD INTO

TABLES

Page 52: Magic Final

54 | P a g e

Restaurant Management System

CONVERTING ERD INTO TABLES

Database Name:-Restaurant

Table Name:-Login

Database Name:-Restaurant Table name:-Foods

Foods_Id Food_Name Price Category 1 Veg Sandwich 25 Sandwich

Database Name:-Restaurant Table Name:-Drinks

Drink_Id Drink_Name Drink_Size Price 1 Mineral Water 100ml 20

Database Name:-Restaurant Table Name:-Meal

Meal_Id Meal_Name Price 1 Gujarati Thali 66

Username Pass Admin 123456

Page 53: Magic Final

55 | P a g e

Restaurant Management System

Database Name:-Restaurant Table Name:- EmpDetails

Id Name Address Phone No Salary 1 Raju Kandivali 80976765xx 3540

Database Name:-Restaurant Table Name:-Purchase

P_Id PName Quantity Price 1 Vegetables 500kg 1200

Database Name:-Restaurant Table Name:-Order1

SrNo Ono ItemName Quantity Price 1 1 PaneerDumRoll 2 180 2 1 PaneerChilly 3 330

Database Name:-Restaurant Table Name:-Delivery

CustNo Customer Name Address PhnNo 1 Ritu Kandivali 98331617xx

Database Name:-Restaurant Table name:-Bill

Bill_No Grand_Total 1 330

Page 54: Magic Final

56 | P a g e

Restaurant Management System

Design Class Diagram

Page 55: Magic Final

57 | P a g e

Restaurant Management System

Design Class Diagram

Reports

Sales Reports

Purchase Reports

Bill Reports

Delivery Reports

Page 56: Magic Final

58 | P a g e

Restaurant Management System

COMPONENT DIAGRAM

Page 57: Magic Final

59 | P a g e

Restaurant Management System

COMPONENT DIAGRAM

Login

SYSTEM USER

Add Stock

View Stock

Order

Delivery

Employee

Bill

Purchase

Page 58: Magic Final

60 | P a g e

Restaurant Management System

PACKAGE DIAGRAM

Page 59: Magic Final

61 | P a g e

Restaurant Management System

PACKAGE DIAGRAM

SYSTEM USER

COURIER

EMPLOYEE

DELIVERY

RETURN

BILL

STATUS

CUSTOMER

LOGIN

Page 60: Magic Final

62 | P a g e

Restaurant Management System

DEPLOYMENT DIAGRAM

Page 61: Magic Final

63 | P a g e

Restaurant Management System

DEPLOYMENT DIAGRAM

System

Printer

SQL Server Database

Page 62: Magic Final

64 | P a g e

Restaurant Management System

Program Chart

Page 63: Magic Final

65 | P a g e

Restaurant Management System

Program Chart

No

Yes

Yes

No

START

Login

if username and password

Correct

STOP

Main Form

Add Stock

Add

Update

Delete

STOP

Purchase

Add Item

Update Item

Delete Items

Employee

Add Details

Update Details

Delete Details

Orders

Add Order

Delete Order

Save Order

Delivery Order Delivery

Details

Bill

Page 64: Magic Final

66 | P a g e

Restaurant Management System

System Flow Diagram

Page 65: Magic Final

67 | P a g e

Restaurant Management System

System Flow Diagram

No

Manager

Receiving Order

Products Products available

Create Bill

Customer

Payment

Page 66: Magic Final

68 | P a g e

Restaurant Management System

Structure Chart

Page 67: Magic Final

69 | P a g e

Restaurant Management System

Structure Chart

Restaurant Management System

Process Order

Details

Process Delivery Details

Process Stock

Details

Process Reports Details

Page 68: Magic Final

70 | P a g e

Restaurant Management System

SYSTEM CODING

Page 69: Magic Final

71 | P a g e

Restaurant Management System

MENU TREE

Page 70: Magic Final

72 | P a g e

Restaurant Management System

MENU TREE

Main Form

File Transaction Report Tools Data Entry View

Change password

Exit Logout

Add Food Add Meal Add Drinks

Order Calculator

Foods Records

Meal Records

Drinks Records

Employee Records

Purchase Records

Sales Reports

Purchase Reports

Bill Delivery

Page 71: Magic Final

73 | P a g e

Restaurant Management System

LIST OF TABLES WITH ATTRIBUTES AND

CONSTRAINTS

Page 72: Magic Final

74 | P a g e

Restaurant Management System

LIST OF TABLES WITH ATTRIBUTES AND CONSTRAINTS

TABLE NAME: Login Table

SrNo Field Name Data Type Field Size Key 1 Username Varchar 10 - 2 Password Varchar 20 -

TABLE NAME: Foods Table

SrNo Field Name Data Type Field Size Key

1 Food_Id Int - Primary key 2 Food_Name Varchar MAX - 3 Price Int - - 4 Category Varchar MAX -

Table Name: Meal Table

SrNo Field Name Data Type Field Size Key 1 Meal_Id Int - Primary key 2 Meal_Name Varchar MAX - 3 Price Int - -

Table Name: Drinks Table

SrNo Field Name Data Type Field Size Key 1 Drink_Id Int - Primary key 2 Drink_Name Varchar MAX - 3 Drink_Size Varchar MAX - 4 Price Int - -

Page 73: Magic Final

75 | P a g e

Restaurant Management System

Table Name: EmpDetails

SrNo Field Name Data Type Field Size Key 1 Id Int - Primary key 2 Name Varchar 50 - 3 Address Varchar MAX - 4 Salary Int - -

Table Name: Purchase Table

SrNo Field Name Data Type Field Size Key 1 P_Id Int - Primary key 2 PName Varchar MAX - 3 Quantity Int MAX - 4 Price Int - -

Table Name: Order1 Table

SrNo Field Name Data Type Field Size Key 1 SrNo Int - - 2 Ono Int - Foreign Key 3 Item Name Varchar 50 - 4 Quantity Int - - 5 Price Int - -

Table Name: Delivery Table

SrNo Field Name Data Type Field Size Key 1 Cust No Int - Primary key 2 Customer Name Varchar MAX - 3 Address Varchar MAX - 4 Phn No Int - -

Table Name: Bill Table

SrNo Field Name Data Type Field Size Key

1 Bill_no Int - Primary key 2 Grand_Total Int - -

Page 74: Magic Final

76 | P a g e

Restaurant Management System

Program Description & Naming Convention

Page 75: Magic Final

77 | P a g e

Restaurant Management System

Program Description & Naming Convention Convention:-

Sr.No Control Convention

1. Lbl Label

2. Txt TextBox

3. Cmb ComboBox

4. Rbtn Radiobutton

5. Chk Checkbox

6. Btn Button

7. DGV DataGridView

8. LV Listview

9. Crp Crystalreportviewer

Program Description:

Sr.

No

Program Description

1. Login It helps to Login into the application.

2. Add Stock Add all the details of the Stock.

3. Purchase Add all the details of the Purchase & Refresh the

form.

4. View Stock Views the stock avalible.

5. Employee Display all the employee records

6. Order It accept all the ordered items from the customer.

7. Main Home page of the Application.

8. SalesSummaryRpt It helps to view the Complete Detail of All the

Sales Also provide Printing Facility for it.

9. PurchaseSummaryRpt It helps to view the Complete Detail of All the

Purchase and Also provide Printing Facility for

it.

10. DeliveryRpt It shows and print the delivery details of the

customer.

11. BillRpt It shows and prints the bill of the customer.

Page 76: Magic Final

78 | P a g e

Restaurant Management System

Test Cases

Page 77: Magic Final

79 | P a g e

Restaurant Management System

TEST CASES PROJECT NAME: RESTAURANT MANAGEMENT SYSTEM

Test Case_Id: MAGIC_01

Test Case Name: Login,Purchase,Add Stock, Employee, Delivery

Description: To verify Username, Item Name, Name, EName, Customer

name.

Sr No. Test Description Test Data Expected

Result Actual Result Log

Pass/Fail 1 Enter 6 alpha

characters and press save

“Aashish” It should accept

It accepts Pass

2 Enter 7 alphanumeric characters and press save

“Aashish 6”

It should not accept

It does not accept

Pass

3 Enter 6 alpha & special character and press save

“Aashish @”

It should not accept

It does not accept

Pass

4 Enter 7 alphanumeric & special character and press save

“Aashish 2$”

It should not accept

It does not accept

Pass

5 Enter 5 special character and press save

“&%$)#” It should not accept

It does not accept

Pass

6 Enter 5 numeric character and press save

“123456” It should not accept

It does not accept

Pass

Page 78: Magic Final

80 | P a g e

Restaurant Management System

PROJECT NAME: RESTAURANT MANAGEMENT SYSTEM

Test Case_Id: MAGIC_02

Test Case Name:Purchase,Add Stock,Employee,Order,Delivery.

DESCRIPTION: To Verify Quantity,Price,Phone No,Salary,Payment.

Sr No. Test Description Test Data Expected Result

Actual Result

Log Pass/Fail

1 Enter 2 alpha characters and press save

“ks” It should not accept

It does not accept

Pass

2 Enter 2 alphanumeric characters and press save

“k6” It should not accept

It does not accept

Pass

3 Enter 2 alpha and special character and press save

“k@” It should not accept

It does not accept

Pass

4 Enter 4 alphanumeric and special character and press save

“kr2$” It should not accept

It does not accept

Pass

5 Enter 5 special character and press save

“&%$)#” It should not accept

It does not accept

Pass

6 Enter 8 -15 numeric character and press save

“8097476569” It should accept

It accepts Pass

7 Enter 4 numeric character and press save

“8097” It should not accept

It does not accept

Pass

Page 79: Magic Final

81 | P a g e

Restaurant Management System

PROJECT NAME: RESTAURANT MANAGEMENT SYSTEM

Test Case_Id: MAGIC_03

Test Case Name: Delivery,Employee.

DESCRIPTION: To verify Address.

Sr No. Test Description Test Data Expected

Result Actual Result

Log Pass/Fail

1 Enter 2 alpha characters and press save

“kr” It should accept

It accepts Pass

2 Enter 2 alphanumeric characters and press save

“S6” It should accept

It accepts Pass

3 Enter 3 alphanumeric character and special symbol and press save

“S/6” It should accept

It accepts Pass

4 Enter 2 alpha and special character and press save

“K@” It should not accept

It does not accepts

Pass

5 Enter 5 special character and press save

“&%$)#” It should not accept

It does not accepts

Pass

6 Enter 3 numeric character and press save

“521” It should accept

It accepts Pass

Page 80: Magic Final

82 | P a g e

Restaurant Management System

Validations

Page 81: Magic Final

83 | P a g e

Restaurant Management System

Validations

Numeric fields are validated, so that will not accept the Characters

Email Textbox are validated, to check if ‘@’ symbol, ‘.’ Dot and no blank spaces are inserted.

Masked Textbox are validated for Mobile No and Contact No to accept only 10 or 11 Digits

Textbox which Details are required are validated, so that no blank spaces are allowed

In New Event Form the Total Cost Textbox is validated such that the Total Cost is automatically calculated and displayed. The Textbox is un-editable(read-only)

Page 82: Magic Final

84 | P a g e

Restaurant Management System

Screen Layouts & Report Layouts

Page 83: Magic Final

85 | P a g e

Restaurant Management System

Screen Layouts

Splash Screen

Login Form

Page 84: Magic Final

86 | P a g e

Restaurant Management System

Main Form

Change Password

Page 85: Magic Final

87 | P a g e

Restaurant Management System

Add_Food

Add_Meal

Page 86: Magic Final

88 | P a g e

Restaurant Management System

Add_Drink

Order Form

Page 87: Magic Final

89 | P a g e

Restaurant Management System

Delivery Form

Bill Form

Page 88: Magic Final

90 | P a g e

Restaurant Management System

Food_Records

Drink_Records

Page 89: Magic Final

91 | P a g e

Restaurant Management System

Meal_Records

Employee Records

Page 90: Magic Final

92 | P a g e

Restaurant Management System

Purchase Form

Page 91: Magic Final

93 | P a g e

Restaurant Management System

Report Layouts

Page 92: Magic Final

94 | P a g e

Restaurant Management System

Purchase Reports

Sales Reports

Page 93: Magic Final

95 | P a g e

Restaurant Management System

Bill Report

Delivery Report

Page 94: Magic Final

96 | P a g e

Restaurant Management System

Future Enhancements

Page 95: Magic Final

97 | P a g e

Restaurant Management System

Future Enhancements

Order Will be Accepted table Wise. Different Payment Facility Can be Added i.e credit card/debit card.

Page 96: Magic Final

98 | P a g e

Restaurant Management System

References & Bibliography

Page 97: Magic Final

99 | P a g e

Restaurant Management System

References & Bibliography

Reference Books/sites:

Books Referred: VB.NET - Black Book VB 6.0 by julia bradley

Website Referred: www.codeproject.com en.wikipedia.com www.w3schools.com www.vb.net-infomation.com

Page 98: Magic Final

100 | P a g e

Restaurant Management System

CONCLUSION

Page 99: Magic Final

101 | P a g e

Restaurant Management System

CONCLUSION

Finally, I can appreciate power of DBMS like Microsoft SQL server in managing the data. I am now confident of handling such real life situation concerning project in Software Management System…