Burger Shop

BURGER SHOP
Mini Project Report submitted to Bharathiar University in partial fulfillment of the requirement
for the Award of the Post Graduate Degree of
MASTER OF COMPUTER APPLCATION
By
DHEERAJ DHARMAPALAN
REGISTER NO: 16P38M0045
Project Guide
Mr. M.R. RAJESH
Senior Software Architect of Teams Global Village Academy
Thalikode , Thrissur, Kerala

December 2018
CENTRE FOR PARTICIPATORY PROGRAMME
Bharathiar University,
Coimbatore 641 046

MINI PROJECT 2018 Page |2
Mini Project Report submitted to Bharathiar University in partial fulfillment of the requirement
for the Award of the Post Graduate Degree of
MASTER OF COMPUTER APPLCATION
By
DHEERAJ DHARMAPALAN
REGISTER NO: 16P38M0045
Project Guide
Mr. M.R. RAJESH
Senior Software Architect of Teams Global Village Academy
Thalikode , Thrissur, Kerala

December 2018
CENTRE FOR PARTICIPATORY PROGRAMME
Bharathiar University,
Coimbatore 641 046
BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

DECLARATION
I hereby declare that this project work titled BURGER

SHOP submitted to the Bharathiar University is a record of original work done by DHEERAJ
DHARMAPALAN under the supervision and guidance of Rajesh M R and that this project
work has not formed the basis for the award of any Degree / Diploma / Associate ship /
Fellowship or similar title to any candidate of any University.
Signature
Name : DHEERAJ DHARMAPALAN
Register No : 16P38M0045
Course : Master of Computer Applications
CPP Centre : TEAMS GLOBAL VILLAGE ACADEMY
Place :
Date :
Countersigned by
Signature of the Guide Countersigned by the Co-ordinator
(With seal) (With Seal)

CERTIFICATE
This is to certify that the project work titled BURGER

SHOP submitted to Bharathiar University in partial fulfillment of the requirements for the
award of the Degree of Master of Computer Applications is a record of the original work done
by DHEERAJ DHARMAPALAN under my supervision and guidance and that this project
work has not formed the basis for the award of any Applications in Degree / Diploma /Associate
ship / Fellowship or similar title to any candidate of any University.
(Seal)
Signature of the Guide

Name and Designation
Forwarded by,
Director
Bharthiar University
Coimbatore – 46
Submitted for University Examination held on __________________________
Internal Examiner External Examiner

TABLE OF CONTENTS
I. Acknowledgement 7
II. Synopsis 8
1. Introduction 9
1.1. System Overview 11
2. System Study and Analysis 12
2.1. Problem Statement 13
3. Existing System 14
3.1. Drawbacks 14
4. Proposed System 15
4.1. Proposed System and Advantage 16
4.1.1 Advantage 16
4.2. Feasibility Analysis 17
4.2.1. Technical Feasibility 17
4.2.2. Economic Feasibility 18
4.2.3. Operational Feasibility 18
4.2.4. Cost Estimation and Scheduling 19
5. Development Environment 20
5.1 Hardware Requirement 21
5.2 Software Requirement 21
6. Programming Environment 22
6.1. About Visual Studio .Net 23
6.2. About Microsoft SQL Server 27
7. System Design and Development 28
7.1. Element of Design 29
7.1.1. Process Design 29
7.1.2. Concept Design 29
7.1.3. Logical Design 30
7.1.4. Physical Design 36
7.1.5. Input Design 36

7.1.6. Database Design 38

7.1.7. Table Structure 39
7.1.8. Output Design 42
8. Screen Shots 43
9. System Testing and Implementation 51
9.1. System Testing 52
9.1.1. Unit Testing 53
9.1.2. Integration Testing 53
9.1.3. User Acceptance Testing 54
9.1.4. Validation Testing 54
9.2. System Security 55
9.3. System Enhancement 55
10. System Implementation and Maintenance 56
10.1. System Maintenance 57
11. Conclusion and Further Enhancement 59
11.1. Conclusion 60
12. Bibliography and References 61
12.1. References 62

ACKNOWLEDGEMENT
I express my sincere thanks to Controller of Examination, Bharathiar University,

Coimbatore who has given me the opportunity to pursue my MCA.
I would like to thank my guide RAJESH .M .R for his encouragement and guidance,
which helped me in completing the project.
I also thank the staff of TEAMS GLOBAL VILLAGE ACADEMY, TRICHUR, for
extending their support as & when required for completing the project.
Finally I would like to thank my colleagues and friends who helped me in completing
the project successfully.
DHEERAJ DHARMAPALAN

SYNOPSIS

INTRODUCTION

MINI PROJECT 2018 P a g e | 10
INTRODUCTION
This Software is mainly implemented for Burger Shop only

that is it is made for business use. This software will help to store details of Burger and other
items and also can calculate the Profit and Loss per month and also provide the facility
to show the details of total purchase and total sales.
Though which the user can understand the shop is in profit
or not or can understand the flow of business is proper or not. They also get record of the Burger
details of total purchase and total sales. Because of that case the user will try to make the proper
flow of business to get more profit.
In this way this software will help to improve the Burger
Shop process and also help to save time for calculating Profit and Loss per month. In same way
user can also save money too.

1.1 SYSTEM OVERVIEW
This section describes the system in narrative form using non-technical terms. It should
provide a high-level system architecture diagram showing a subsystem breakout of the system, if
applicable. The high-level system architecture or subsystem diagrams should, if applicable,
show interfaces to external systems. Supply a high-level context diagram for the system and
subsystems, if applicable. Refer to the Requirements Traceability Matrix (RTM) in the
Functional Requirements Document (FRD), to identify the allocation of the functional
requirements into this design document.

SYSTEM STUDY AND ANALYSIS

2.1 PROBLEM STATEMENT
 This activity requires a precise definition of the problem in user terms.

 A clear statement of the problem is crucial to the success of the software.
 It helps not only the developers but also the user to understand the problem better.
 Keeping recording for every transaction in the registers takes
 More time & is a tedious job.
 To search for details of any particulars has to refer many Registers.
 Lacks reliability & no guarantee of sure end results.
 Calculations are done manually which may lead to errors.
 For all these reasons computerized.

EXISTING SYSTEM
The existing system is manual system. The administrator has the option to add, modify or delete
any records from the system. The new system will operate feasible and will contain an automated
database for storage. The administrator has the authority to changes the rights of the staffs.
The drawback of existing system are:
 More consumption of time
 Problem in storing bulk of information
 No security
 More manual work required
3.1 DRAWBACKS
 Maintenances of records are difficult.

 Time consuming.
 Updating is a tedious task.
 Data processing is difficult.
 Debugging is difficult.
 Data retrieval is difficult.
 More consumption of time.
 Problem in storing bulk of information in ledger and notebooks.
 Security and reliability of the data stored.
 Data redundancy.
 More manual work required.
 Errors occur frequently.

PROPOSED SYSTEM

4.1 PROPOSED SYSTEM AND ADVANTAGES
The system will provide the user, the option to look at the details of the existing List
of products and rates. It also allows the user to modify the record. The administrator can alter the
system data.
The main objective of developing a computerized system are:
 To maintain the records of Bills
 User friendly
4.1.1 ADVANTAGES
 High portability.
 User friendly
 It facilitates timely updating process whenever initiates.
 Effective’s data retrieved.
 Support managerial decision.
 It enables the user to get information at any time by a single keystroke.
 High security to the system.
 Easy to access stored information.
 Structured programming and so debugging is easy

4.2 FEASIBILITY ANALYSIS
Having drawn the rough specifications the next step is to check where it is feasible to
implement the system. If the benefits from the computerization, the efforts is not justified. A
feasibility study in this case is the portion of the SDLC that determines three types of feasibility
to implement the system.
4.2.1 Technical Feasibility
4.2.2 Economic Feasibility
4.2.3 Operational Feasibility
4.2.4 Cost Estimation and Scheduling
4.2.1 TECHNICAL FEASIBILITY
This tells whether the appropriate hardware, software and the supplication tools will be
available when required. The proposed system is developed under Windows 8 platform on dual
core based machine using Visual Basic 2008 and SQL Server 2005 keeping in view the
availability of software and hardware therefore, no extra effort is required to implement the
software .In short:
 To determine availability of hardware and software for the system.
 Includes analysis of capabilities and resources existing.
 Whether the above have to be purchased?
 Whether training required?

4.2.3 ECONOMICAL FEASIBILITY
The application module has since been by us as trainees here, therefore it is difficult to
quantify the cost of this package in monetary terms, however considering the hardware and
system software already available. The benefits as already covered in objective shall outweigh
the cost aspect of this application and therefore it is found to be practically feasible. In short:
 Cost study factors are out-of-pocket costs for software hardware and
programming(not fully under management control)
 Cost saving by establishing standard(before software installed)
 Cost saving by not installing a quarry language(unless sufficient data exists)
 Hidden costs associated with system implementation(mentioned by the project team)
 To conduct a cost-benefits study of proposed system(expected time to achieve

benefits ,data sharing by user departments feasible, risk involved if database system
is implemented, type of risks, application types and type of benefits from each of the
application, competition existing and expected, method in which the system will aid
in fulfilling corporate long range plans).
4.2.3 OPERATIONAL FEASIBILITY

This informs us whether will aspect the newly developed system. The system being
considered is designed in such a manner. It does not need any extra training to operate it. If any
error occurs during the execution, so no extra training is required to implement this.
Software moreover the reports are generated in same format as they are in the existing
system. In short:
 To determine available expertise and personal needed for the system ,as well as
training needs for users and system personal:

Technical feasibility Feasibility Operational

Study feasibility study
Study
All the above three-feasibility examination conducted and reviewed found favorable and
acceptable to the firm the committee gives approval to go ahead with requirement definition.
4.2.4 COST ESTIMATION AND SCHEDULING
Cost estimation is the approximation of the cost of a program, project or operation. The
cost estimate is the product of the cost estimating process. The coast estimation has a single total
value and may have identifiable component values. A problem with a cost overrun can be
avoided with credible, reliable and accurate cost estimation an estimator is the professional who
prepares cost estimates. There are different types of estimators whose title may be preceded by a
modifier, such as building estimators, or electrical estimator, or chief estimator. Other
professional titles may also prepare estimates or contribute estimates, such as quantity surveyors,
coat engineers etc...

DEVELOPMENT ENVIRONMENT

5.1 HARDWARE SPECIFICATION
 Processor : Intel Pentium 4 (or) Higher
 RAM : 512 MB & Above
 Hard Disk Drive : 500 MB Free Space or Above
 Printer : Ink-Jet Printer
 Pen Drive : 512MB
 Keyboard : 108 keys
 Mouse : A Pair of Mouse Button
5.2 SOFTWARE SPECIFICATION
 Operating System : Microsoft Windows XP and above version

 Front End : VB.Net
 Back End : SQL Server 2005

PROGRAMMING ENVIRONMENT

6.1 ABOUT VISUAL STUDIO.NET
The .NET Framework is a new computing platform that simplifies application development
in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill
the following objectives: To provide a consistent object-oriented programming environment
whether object code is stored and executed locally, executed locally but Internet-distributed, or
executed remotely.
 To provide a code-execution environment that minimizes software deployment and

versioning conflicts.
 To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.
Microsoft Visual Studio .Net Framework:
Common Language Runtime
Class Libraries
Programming Languages
(C#.NET, VB.NET, VC++.NET, J#.NET)
ASP.NET

Visual Basic .NET (VB.NET) is a multi paradigm, high level programming language,
implemented on the .NET framework. Microsoft launched VB.NET in 2002 as the successor
to its original visual basic language.
Although “.NET” portion dropped in 2005.Microsofts integrated development
environment (IDE) for developing in visual basic .NET language is visual studio. Most of
visual studio editions are commercial; the only exception is visual studio express which is
freeware. In .NET framework SDK includes a freeware command line complier called
vbc.exe. Mono also includes a command line VB.NET complier
 VB.NET is a powerful window based application.
 VB.NET is totally object oriented.
 VB.NET uses xml to transfer data between the various layers in the DNA
Architecture.
 Security is more robust in VB.NET.
ABOUT VB.NET
Visual Basic is Microsoft's high-level object-oriented rapid application development

environment for the Windows platform. The first versions of Visual Basic were intended to
target Windows 3.0 (a version for DOS existed as well), however it was not until version 3.0 for
Windows 3.1 that this programming language gained large-scale acceptance in the shareware and
corporate programming community.
Using drawing tools that resemble those found in hardcopy page layout programs or PhotoShop,
VB programmers make user interfaces by drawing controls and other UI components onto forms.
The programmer then adds code to respond to user interactions with the controls (for example,
clicks, drag and drop, etc) known as events. The code can trigger events in other controls (for
example, by displaying text or an image), execute procedures (run some algorithm based on the
values entered in some control, output data, do business logic, etc), or almost anything else one
might do in code.
Visual Basic can be considered to be an interpreted language like its Basic ancestor, with
appropriate modifications to accommodate object-oriented programming, and has implicit type

conversion. That is, the VB development environment goes to great lengths to format (and aid
the user in formatting) programming code so that it conforms to executable syntax. For example,
VB will appropriately change the case of newly typed variable names to match those that have
been declared previously (if they have been declared at all!). Traditionally, VB is known for
compiling programs into pseudo-code (p-code, similar to Java's byte code) which is interpreted
at runtime, requiring the use of dynamically-linked libraries (for example, VBRUN300.DLL for
version 3 of Visual Basic, circa 1992) but newer versions can compile code into something more
closely resembling the efficient machine code generated by C-like compilers. VB6 can be
compile either into p-code or into native code; in fact VB6 uses the Microsoft C++ compiler to
generate the executable.
For new Windows programmers, VB offers the advantage of being able to access much of the
Windows UI functionality without knowing much about how it works by hiding the technical
details. Although accessing low-level Windows UI functionality is possible, doing so in VB is
as, or more difficult compared to such access using Visual C++ or other lower level
programming languages. Recently VB.NET has gone a long way to fixing some of the
limitations.
Using custom controls provided by Microsoft or third parties, almost any functionality that is
possible in Windows can be added to a VB program by drawing a custom control onto a form in
the project.
Visual Basic traditionally comes in at least entry level and professional versions, with various
designations depending on Microsoft's contemporary marketing strategy. The different versions
are generally differentiated by the number of custom controls included, and the capabilities of
the compiler. Higher priced packages include more functionality.
HISTORY
VB 1.0 was introduced in 1991. The approach for connecting the programming language
to the graphical user interface is derived from a system called Tripod (sometimes also known
as Ruby), originally developed by Alan copper, which was further developed by Cooper and his
associates under contract to Microsoft.

 Visual Basic 1.0 (May 1991) was released for Windows.
 Visual Basic 1.0 for DOS was released in September 1992. The language itself was not quite
compatible with Visual Basic for Windows, as it was actually the next version of Microsoft's
DOS-based BASIC compilers, Microsoft QuickBASIC compiler QuickBASIC and BASIC
Professional Development System. The interface was barely graphical, using extended
ASCII characters to simulate the appearance of a GUI.
 Visual Basic 2.0 was released in November 1992. The programming environment was easier
to use, and its speed was improved.
 Visual Basic 3.0 was released in the summer of 1993 and came in Standard and Professional
versions. VB3 included a database engine that could read and write Access databases.
 Visual Basic 4.0 (August 1995) was the first version that could create 32-bit as well as 16-bit
Windows programs. It also introduced the ability to write classes in Visual Basic.
 With version 5.0 (February 1997), Microsoft released Visual Basic exclusively for 32-bit
versions of Windows. Programmers who preferred to write 16-bit programs were able to
import programs written in Visual Basic 4.0 to Visual Basic 5.0, and Visual Basic 5.0
programs can easily be converted with Visual Basic 4.0. Visual Basic 5.0 also introduced the
ability to create custom user controls, as well as the ability to compile to native Windows
executable code, speeding up runtime code execution.
 Visual Basic 6.0 (Mid 1998) improved in a number of areas, including the ability to create
web-based applications using Internet Explorer. Visual Basic 6 is no longer supported.

6.2 ABOUT MICROSOFT SQL SERVER
SQL SERVER 2005:

SQL Server 2005 supports having a wide range of users access it at the same time.
An instance of SQL Server 2005 includes the file that make up a set of databases and a copy of
the DBMS software. Applications running of separate computers use a SQL Server 2005
communications component to transmit commands over a network to the SDQL Server 2005
instance. When an application connects to an instance of SQL Server 2005,it can reference any
of the databases in that instance that the user is authorized to access. The communication
component also allows communication between an instance of SQL Server 2005 and an
application running on the same computer. You can run multiple instances of SQL Server 2005
on a single computer.
SQL Server 2005 is designed to support the traffic of the largest
Websites or enterprise data processing systems. Instances of SQL Server 2005running on large,
multiprocessor servers are capable of supporting connections to thousands of users at the same
time. The data in SQL Server tables can be partitioned across multiple servers, so that several
multiprocessor computers can cooperate to support the database processing requirements of
extremely large system. These groups of database servers are called federations.
Features of SQL Server 2005:
Microsoft SQL Server 2005 include:

 Internet integration
 Scalability and Availability
 Enterprise-Level Database Features
 Ease of Installation, Deployment and use
 Data warehousing

SYSTEM DESIGN AND DEVELOPMENT

7.1. ELEMENT OF DESIGN

7.1.1 PROCESS DESIGN
Product design is the process of creating a new product to be sold by a business to its
customers. A very broad concept, it is essentially the efficient and effective generation and
development of ideas through a process that leads to new products .In a systematic approach,
product designers conceptualize and evaluate ideas, turning them into tangible inventions and
products. The product designer's role is to combine art, science, and technology to create new
products that people can use. Their evolving role has been facilitated by digital tools that now
allow designers to communicate, visualize, analyze and actually produce tangible ideas in a way
that would have taken greater manpower in the past. Product design is sometimes confused with
(and certainly overlaps with) industrial design, and has recently become a broad term inclusive
of service, software, and physical product design. Industrial design is concerned with bringing
artistic form and usability, usually associated with craft design and ergonomics, together in order
to mass-produce goods. Other aspects of product design include engineering design, particularly
when matters of functionality or utility (e.g. problem-solving) are at issue, though such
boundaries are not always clear
7.1.2 CONCEPT DESIGN
The main idea behind the Conceptual Design is to maximize the probability of a feasible
final product. Hence, a conceptual design should be worked in sufficient detail to allow estimates
of cost, weight, overall dimensions and power consumption. During this first phase of the design
process, decisions should be made about major design features such as primary sub-systems and
major algorithms. The designer should also present the rationale for making these decisions,
supported by relevant experiments. An arbitrary decision, especially early in the design process,
means a wasted opportunity for improving quality and reducing cost. Using an ad-hoc or popular
method without questioning is in fact nothing but making an arbitrary decision. During the
conceptual design phase, one must question the “accepted” or conventional ways of doing things
and look for possible alternatives.

7.1.3 LOGICAL DESIGN

The logical flow of a system and define the boundaries of a system. It includes the
following steps:
 Reviews the current physical system – its data flows, file content, volumes, frequencies
etc.
 Prepares output specifications – that is, determines the format, content and frequency of
reports.
 Prepares input specifications – format, content and most of the input functions.
 Prepares edit, security and control specifications.
 Specifies the implementation plan.
 Prepares a logical design walk through of the information flow, output, input, controls
and implementation plan.
 Reviews benefits, costs, target dates and system constraints.
Data Flow Diagram:
A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, through processed, may be
described logically and independently of physical components associated with the system. These
are known as the logical data flow diagrams. The physical data flow diagrams show the actual
implements and movement of data between people, departments and workstations. A full
description of a system actually consists of a set of data flow diagrams. Using two familiar
notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component
in a DFD is labeled with a descriptive name. Process is further identified with a number that will
be used for identification purpose.

The development of DFD’s is done in several levels. Each process in lower level diagrams can
be broken down into a more detailed DFD in the next level. The lop-level diagram is often
called context diagram. It consist a single process bit, which plays vital role in studying the
current system. The process in the context level diagram is exploded into other process at the
first level DFD.
The idea behind the explosion of a process into more process is that understanding at one level of
detail is exploded into greater detail at the next level. This is done until further explosion is
necessary and an adequate amount of detail is described for analyst to understand the process
DFD Symbols:
In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data
5. Process that transforms data flow.
Process that transforms data flow
Source or Destination of data

Data flow
Data Store
Context Level DFD
Level 0:
USER ID
BUSINESS
ADMIN MANAGER USER
PASSWORD

Level 1:
ADMIN LOGIN
USERNAME
PASSWORD
STORE
PRODUCTS DATA ENTRY FOR PRODUCTS
& RATES ADDING PRODUCTS & RATES STORE & RATES
DATA ENTRY STORE

BILLING BILLS
ADDING FOR BILLING STORE
TOTAL STORE
PURCHASE TOTAL
CALCULATION PURCHASE
& SALES CALCULATING STORE
& SALES
STORE
PROFIT & CALCULATION PROFIT
LOSS CALCULATING STORE & LOSS
RETRIEV
REPORT SHOWING
SHOW PROFIT
AND LOSS
USER LOGIN
USERNAME
PASSWORD
DATA ENTRY STORE

BILLING BILLS
ADDING FOR BILLING STORE
TOTAL STORE
PURCHASE TOTAL
CALCULATING
CALCULATION STORE PURCHASE
& SALES & SALES

Level 2:
ADDING DATA
ABOUT PRODUCTS
AND RATES STORE
ADDING
EDITING DATA STORE

PRODUCTS EDITING STORE PRODUCTS
& RATES ABOUT PRODUCTS
& RATES
AND RATES
RETRIEV
DELETING RETRIEV
DELETING DATA
ABOUT PRODUCTS
AND RATES
ADDING BILLS
STORE
ADDING
DELETING DELETING RETRIEV STORE

BILLING
BILLS BILLS
RETRIEV
DELETING
DELETING ALL
BILLS
CALCULATING
CALCULATING TOTAL PURCHASE
STORE
AND SALES
PROFIT & STORE
LOSS PROFIT
& LOSS
DELETING PROFIT
RETRIEV
DELETING & LOSS

CALCULATING
TOTAL PURCHASE
AND SALES
CALCULATING STORE
STORE
TOTAL DELETING TOTAL TOTAL
PURCHASE DELETING PURSHASE AND
RETRIEV
PURCHASE
& SALES SALES & SALES
DELETING RETRIEV
DELETING ALL
TOTAL PURCHASE
AND SALES
DELETING ALL
PROFIT & LOSS
RETRIEV
DELETING
STORE
REPORT PROFIT &
LOSS
RETRIEV
SHOWING
SHOW PROFIT
& LOSS

7.1.4 PHYSICAL DESIGN
Physical system produces the working systems by define the design specifications that tell
the programmers exactly what the candidate system must do. It includes the following steps.
 Design the physical system.
 Specify input and output media.
 Design the database and specify backup procedures.
 Design physical information flow through the system and a physical design Walk
through.
 Plan system implementation.
 Prepare a conversion schedule and target date.
 Determine training procedures, courses and timetable.
 Devise a test and implementation plan and specify any new hardware/software.
 Update benefits , costs , conversion date and system constraints
7.1.5 INPUT DESIGN
Input design is the process of converting used oriented input into a computer based format.
The goal of the designing input is to make data entry as easy and free from error
In .Net input to the system is entered through forms. A form is “any surface on which
information is to be entered, the nature of which is determined by what is already on that
surface.” If the data going into the system is incorrect, then processing and output will magnify
the errors so designer should ensure that form is accessible and understandable by the user.

The following are the consideration given by the end user for the input design:
1. The screen should be user friendly and easy to operate.

2. Proper validation of input to be provided.
3. The screens should be clear and enough information should be provided to guide the user
to enter correct data.
4. List of valued values for the field should be provided wherever possible.
5. To produce a cost effective method of input.
6. To make the input forms understandable to the user.
7. .Data recording at its source.

7.1.6 DATABASE DESIGN
Table Design
Table design refers to outside the logical data structures are to be physically stored in
the storage device. The design of table includes decision making on the nature and content
of the files such as whether it is to be used for storing master details, transaction details or
reference information. Various factors are considered during the table design phase of
system analysis. Some of them are listed below:
 Purpose of the table
 Availability of the hardware
 File activity
 File size
 Output requirements
 Input requirements
 File organization
Table design also deals with the design of physical database. A key field
determines how the access Is to be implemented. Suitable key fields are identified various
tables and are coded approximately. The type, width and size of the fields are identified.
Techniques of file organization are studied so that the most appropriate storage device can
be selected and n efficient database design can be achieved. Specifying the data between
them identifies the interface between the system databases and other databases. The
designing of the tables in the database is done according to the rules specified for databases
as described above. In the proposed project, 5 tables are used. Insertion and retrieval of
values are easy by designing the database in this way.

TABLE STRUCTURE

TABLE STRUCTURE
tbl_login:
tbl_par:
tbl_billing:

tbl_tpas:
tbl_pal:

7.1.8 OUTPUT DESIGN

One of the most important features of an information system for users is the output is
produces. The output is thee information delivered to user through the information system. Users
generally merit the system solely by its output. Efficient, intelligible output design should
improve the systems relationships with the user and helps in decision making. Hence the system
analysts work closely with user through interactive processes, until the result is considered to be
satisfactory.
The major form of output is a hard copy oriented from the printer. These printouts are designed
to input the exact requirement of the user. The outputs required by the end user are defined
during the logical design stage in terms of:
1. The type of input
2. The content
3. The format
4. The action required
The content of the output are then defined in detail during the physical design of outputs.
Objectives of the output design
 Design output to serve the intended purpose
 Design output to fit the user
 Delivered the appropriate quantity of output
 Provide output on time
 Choose the right output method

SCREEN SHOTS

Login Form:
Staff Form:

Admin Form:
Staff Registration Form:

Products And Rates Form:

Billing Form:

Total Purchases And Sales Form:

Profit And Loss Form:

Report Form:

SYSTEM TESTING AND

IMPLEMENTATION

9.1 SYSTEM TESTING
System testing is the stage of implementation, which is aimed at ensuring that the system
works accurately and efficiently before live operation commences. For any software that is
newly developed, primary importance is given to testing the system. It is the large opportunity
for the developer over to the customers.
Testing is the process by which a developer will generate a set of test data, which gives
maximum probability of finding all type of errors that can occur in the software. Testing is vital
to the success of the system. The candidate system is subject to a variety of tests: online
response, volume, stress, recovery & security and usability tests. A series of testing are
performed for the proposed system before the system is ready for user acceptance testing.
It is the process of exercising or evaluating a system by manual or automatic means to
verify that it satisfies the specified requirements or to identify the difference between expected
and actual results. The testing activities are aimed at convincing the customer through
demonstration and actual use that the software is a solution to the original problem and that both
the product and the process that created it are of high quality.
System testing is the stage of implementation, which is aimed at ensuring that the system
works accurately and efficiently before live operation commences.
Testing is the process of executing the program with the intent of finding errors and
missing operations and also a complete verification to determine whether the objectives are met
and the user requirements are satisfied.
The ultimate aim is equality assurance. Tests are carried out and the results are compared
with the expected document. In the case of erroneous results, debugging is done. System testing
is actually a series of different tests whose primary purpose is to fully exercise the computer-
based system. It begins where testing is completed and finally software is completely assembled
as a package, interfacing errors are uncovered and corrected.

9.1.1 UNIT TESTING
It is the process of taking each program module and run it in isolation from the rest of
the modules, by using prepared inputs and comparing the actual result with results predicated by
the specifications and design of modules. This enables the tester to detect errors in coding and
logic that are contained to within the module alone.
The enables, detect errors in coding and logic that are contained within each module.
This testing includes entering data and ascertaining if the value matches to the type and size
supported by VB. The various controls are tested to ensure that each performs its action as
required .This is known as “Module testing” .This testing is carried out during programming
stages.
Project aspects: Front-end design consists of various forms. They are tested for data
acceptance. Similar the back-end that is database was too tested for successful acceptance and
retrieve l of data.
9.1.2 INTEGRATION TESTING

It is the schematic technique for constructing the program structure while at the same
time conducting tests to see uncovered errors associated with interfacing. It also test to find
discrepancies between the system and its original objectives, current specification and systems
documentation .The primary concern in compatibility of individual modules.
Integration testing is a systematic testing to discover errors associated within the

interface .The objective is to take unit tested modules and build a program structure. All the
modules are combining and tested as a while.
We followed bottom-up integration testing .Bottom up integration testing as its name

implies begins construction and testing with atomic modules. Because components are integrated
from the bottom up, processing required for component subordinate to give level is always
available and the need for stubs is estimated.

9.1.3 USER ACCEPTANCE TESTING
User acceptance of a system is the key factor for the success of any system. The system
under consideration is tested for user acceptance by constantly keeping in touch with the
system users at time of developing and making changes whenever required. This is done with
regard to the following points:
 Inputs screen design
 Output screen design
 Menu drive system
 Format of ad-hoc reports and other outputs
9.1.4 VALIDATION TESTING
Validating testing can be defined in many ways, but a simple definition that validation
succeeds when the software in a manner that is reasonably expected by the customer.
Requirements analysis is validates against the software that has been constructed. Software
validation is achieved through a series of black box that demonstrate conformability with
requirements. After validation test have conducted, once of the two possible conditions exists.
 The function or performance characterized confirm the specification and are accepted.
 Derivation from the specification is found and deficiency list is created.
 The errors, which are uncovered during system integration testing, were also corrected
during this phase.

9.2 SYSTEM SECURITY
System security an (operating) system is responsible for controlling access to system

resources, which will include sensitive data. The system must therefore include a certain amount
protection for such data, and must in turn control access to those parts of the system that
administer this protection. System security is concerned with all aspects of these arrangements
9.3 SYSTEM ENHANCEMENT
Maintenance is a set of software Engineering activities that occur after software

has been delivered to the customer and put into operation. Software configuration
management is a set of tracking and control activities that began when a software project
begins and terminates only when the software is taken out of the operation.
We may define maintenance by describing four activities that are undertaken
after a program is released for use:
 Corrective Maintenance
 Adaptive Maintenance
 Perfective Maintenance or Enhancement
 Preventive Maintenance or reengineering
Only about 20 percent of all maintenance work is spent "fixing mistakes". The remaining 80
percent are spent adapting existing systems to changes in their external environment, making
enhancements requested by users, and reengineering an application for use.

SYSTEM IMPLEMENTATION AND

MAINTANENCE

10.1 SYSTEM MAINTANENCE
The objectives of this maintenance work are to make sure that the system gets into work
all time without any bug. Provision must be for environmental changes which may affect the
computer or software system. This is called the maintenance of the system. Nowadays there is
the rapid change in the software world. Due to this rapid change, the system should be capable of
adapting these changes. In our project the process can be added without affecting other parts of
the system.
Maintenance plays a vital role. The system liable to accept any modification after its
implementation. This system has been designed to favor all new changes. Doing this will not
affect the system’s performance or its accuracy.
The objectives of this maintenance work are to make sure that the system gets into work all
time without any bug. Provision must be for environmental changes which may affect the
computer or software system. This is called the maintenance of the system. Nowadays there is
the rapid change in the software world. Due to this rapid change, the system should be capable of
adapting these changes.
In our project the process can be added without affecting other parts of the system.
Maintenance plays a vital role. The system is liable to accept any modification after its
implementation. This system has been designed to favor all new changes. Doing this will not
affect the system’s performance or its accuracy.
In the project system testing is made as follows:
The procedure level testing is made first. By giving improper inputs, the errors occurred
are noted and eliminated. Then the web form level testing is made. For example storage of data
to the table in the correct manner.
In the form, the zero length username and password are given and checked. Also the
duplicate username is given and checked. The client side validations are made. The dates are
entered in wrong manner and checked. Wrong email-id is given and checked.

This is the final step in system life cycle. Here we implement the tested error-free system
into real-life environment and make necessary changes, which runs in an online fashion. Here
system maintenance is done every months or year based on company policies, and is checked for
errors like runtime errors, long run errors and other maintenances like table verification and
reports.
Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus it can be considered to be the most critical stage in achieving a successful
new system and in giving the user, confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the existing system
and it’s constraints on implementation, designing of methods to achieve changeover and
evaluation of changeover methods.
Implementation is the process of converting a new system design into operation. It is the
phase that focuses on user training, site preparation and file conversion for installing a candidate
system. The important factor that should be considered here is that the conversion should not
disrupt the functioning of the organization.

CONCLUSION AND FURTHER

ENHANCEMENT

CONCLUSION
This software has been developed for the normal functioning of Burger Shop. It
has much scope in the future as it is effective and will be much useful than the existing system,
because it is much more user friendly, ease of access consumes much less time for all the process
in a Burger Shop.
The above project aims at the reduction of a power and great convenience to its
users. I had completed the project within the stipulated time as per the rules and regulations. I am
very glad to express my gratitude to God for the completion of this work. I thank once again all
those who directed and encouraged me.
DHEERAJ DHARMAPALAN

BIBLIOGRAPHY AND REFERENCES

REFERENCES
o VISUAL STUDIO .NET BLACK BOOK : STEVEN HOLZNER
o AN INTRODUCTION TO DATABASE SYSTEM: CJ. DATE
o DATABASE MANAGEMENT SYSTEM : JAMES A SAM
o SOFTWARE ENGINEERING : ROGER S PRESSMAN
o SOFTWARE ENGINEERING CONCEPTS : RICHARD E FARLEY
o SYSTEM ANALYSIS AND DESIGN : JOHN STUBBE
o HTTP://WWW.CODEPROJECT.COM


Burger Shop

Uploaded by

Copyright:

Available Formats

Burger Shop

Uploaded by

Document Information

Original Description:

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

Burger Shop

Uploaded by

Copyright:

Available Formats

BURGER SHOP

MASTER OF COMPUTER APPLCATION

REGISTER NO: 16P38M0045

Mr. M.R. RAJESH

Senior Software Architect of Teams Global Village Academy

Thalikode , Thrissur, Kerala

CENTRE FOR PARTICIPATORY PROGRAMME

Coimbatore 641 046

MASTER OF COMPUTER APPLCATION

REGISTER NO: 16P38M0045

Mr. M.R. RAJESH

Senior Software Architect of Teams Global Village Academy

Thalikode , Thrissur, Kerala

CENTRE FOR PARTICIPATORY PROGRAMME

Coimbatore 641 046

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

I hereby declare that this project work titled BURGER

Course : Master of Computer Applications

CPP Centre : TEAMS GLOBAL VILLAGE ACADEMY

Signature of the Guide Countersigned by the Co-ordinator

(With seal) (With Seal)

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

This is to certify that the project work titled BURGER

Signature of the Guide

Submitted for University Examination held on __________________________

Internal Examiner External Examiner

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

7.1.6. Database Design 38

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

I express my sincere thanks to Controller of Examination, Bharathiar University,

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

This Software is mainly implemented for Burger Shop only

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

1.1 SYSTEM OVERVIEW

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

SYSTEM STUDY AND ANALYSIS

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

2.1 PROBLEM STATEMENT

 This activity requires a precise definition of the problem in user terms.

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

 Maintenances of records are difficult.

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

4.1 PROPOSED SYSTEM AND ADVANTAGES

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY

4.2 FEASIBILITY ANALYSIS

4.2.1 Technical Feasibility

4.2.2 Economic Feasibility

4.2.3 Operational Feasibility

4.2.4 Cost Estimation and Scheduling

4.2.1 TECHNICAL FEASIBILITY

 To determine availability of hardware and software for the system.

 Includes analysis of capabilities and resources existing.

 Whether the above have to be purchased?

 Whether training required?

BURGER SHOP TEAMS GLOBAL VIILAGE ACADEMY