Chapter 1: Introduction

The website “Online Frankie Shop” is designed for people. In this project administrators set product,
product prize, employee information, employee salary, transaction, purchase, sell all of these data.
Administrator can register the user id and their password, which is necessary for user. Administrator gives
order to supplier for raw materials.
Customer easily handles the website & gets their product. In administrator side the work of administrator is
easy than manual work. All data are saved in digital format. Administrator can store number of more data in
system. She/he can easily find out employee details, their salary, and customer information. As compare to
manual work, my project can save time & energy. Administrator can easily generate reports that are used in
audit. So as compare to manual work this website perform better & fast.

BACKGROUND OF THE PROJECT

Our project will basically provide a user – friendly interface. The project includes the data entries including
customer details, Employee details, Supplier details, Orders Details etc. It will generate the bills, and makes
the data search easy and faster. What all things those we were taking days together to complete will be
done with few hours.

Page 1
 OBJECTIVES
Following are the objectives of online frankie shop:-
1. To improve customer relations.
2. Improve speed and efficiency of frankie making.
3. Improve efficiency and speed of delivery.
4. Lower the cost of frankie.
5. As most of the things will be done online, it will reduce the paper work.
6. This system will provide customer all the details of his order before making the order.

Purpose
This website has been developed for user to
Order Online Frankie
Search for frankie shops available in certain area.
View their menu.

Scope
The scope of the project to provide a frankie ordering service using an online. The website shows the list of
different frankie shops available at a certain place,the list of frankies available and also provides an option
to buy.

Page 2
 Chapter 2: System Analysis

Existing System
Still customer using the system which is totally depending on manual data management
for performing various activities related to the ordering frankie.
In existing system the activity which are perform by the user/supplier manually that are
providing delivary ordering frankie customer details etc.
So this all activities done manually that’s why existing system is time consuming and it’s create
difficulties to handle various task related to the online frankie ordering delivary.
The reports and register related to the delivering frankie to the customer are maintained
manually that is in paper format.
So there is a chance of data loosing related to ordering and delivering frankie records.
In existing system to order frankie customer has to visit particular restaurant, shop, hotel etc.
Problem in existing system
1) Time consuming.
2) All transaction is done manually with paper and pen.
3) Abdation is not allowed.
4) In manual system there is no accuracy reports and bill generation.
5) Lack of better facilities.
6) In existing system if customer wants to get inquiry of particular parcel and if that parcel is not available
then it is difficult to remember about it.

Limitations of present system:

There are certain limitations in system, which are as follows:-

1. To maintain records of every task like record of Employee, bill, payment, Stock, etc. manually is
unaffordable.

2. To Search the records of Employee, payment, customer, customer- order, bill, salary from
registers is critical process.

3. Retrieval of information and searching any old record is critical process.

4. In the current system, time is wasted for searching any old records of student, staff.

Most chances of losing information in the manual files and it requires lot of manpower

Page 3
Fact-Finding Techniques
Fact-finding technique is one of the parts of the system analysis. At the time of analysis of the system or
before starting actual work, system analysts collect the information. For gathering information system
analyst prefers any fact-finding technique such as:
1] Interview.
2] Questionnaire.
3] Record review.
4] Observation.
While developing this system we have done this part by using interview & record-review
techniques.
1] Interview: -
The whole system investigation part has done by taking interview of the concerned people, user &
staff. By asking them manual process of each work, by pointing hints regarding the work, by discussing
their problems deeply, by asking them their requirements, by taking their valuable suggestion guidance
regarding system study.
After taking their interviews regarding the systems study noting down the points regarding the
system. This work of taking interview-asking difficulties to concern person till all the points of the system
understood. This interview technique proved beneficial outcome for system analysis.

2] Questionnaire:-
In this method we actually provide a list of questions to the user. According to the list the user
answers the questions, taking his own time without stress to answer quickly. In this method the results
Obtained are rather accurate and thoughtfully given. Questionnaires can be an effective method for
gathering facts.
E.g. how your system actually works?

3] Record review:-
Review of record is good but a tedious way to retrieve information from an organization. This refers
to a personal viewing of records.

4] Observation: -
This technique proves useful in finding the facts of the system. In this technique has done by
observing ledger, registers, document, files that are prepared manually. By observing such record a view of
the database file, reports, screen designing, required input output of the system, database designing of the
system, and logical designing of the system.
Thus by doing their techniques of the fact finding method different facts of the system gathered.

Page 4
Proposed system

1. It is manual and time consuming.

2. It utilizes a large amount of space for customer and supplier transaction information in paper files .

3. Sometime manual calculation may be incorrect thus, leading to the incorrect information

4. A large amount of data cannot be viewed at a glance .

5. No reminder for customer and Purchaser.

6. Sometime the calculation has to be done manually so it requires a lot of work.

7. Updating is not performed that efficiently and may lead complications.

8. No security as data can be misplaced or damaged.

9. Lastly, it was not offers a user friendly work environment

Page 5
Feasibility study

The feasibility study proposes one or more conceptual solutions to the problem set for project. The
conceptual solution gives an idea of how the system looks like. The following three things should be done
to establish feasibility

1] Technical feasibility: -
Technical feasibility study determines whether the organization has technology and the skills
necessary to carry out the project. If not then it determines how they should be obtained. In this proposed
system, the existing technology satisfies the need for the system that is available. Therefore the system is
feasible.
Technical feasibility study determines whether the organization has the technology & the skills necessary to
carry out the project. If not then it determines how they should be.
2] Operational Feasibility: -
Operational feasibility study determines if the proposed system satisfies the user’s objectives & can be
fitted into the current system operation. Our proposed system will certainly satisfy the user’s objective & it
will enhance their capability. The proposed system can be best fitted instead of the current system
operation. Therefore, the system is operationally feasible.
3] Economic Feasibility:-
Economic feasibility study determines whether the project goals can be achieved within the limits allocated
to it. It must also determine that the benefits obtained from the new system are not worth the cost.

Page 6
System Requirements

Hardware and Software Requirements:

 RAM
Minimum 2 GB RAM required to run the system.

 Hard Disk
Minimum 20 GB HDD is necessary to deploy the system.

 Processor
Pentium IV and above.

 Operating System
Windows NT, 2000, Window’s 7, Vista etc.

 Platform
Microsoft Visual Studio .NET 2012.

 Backend
Sqlserver

Page 7
 Justification of selection of technology

In the world of web and application development, there are many framework and languages that
developers can choose from. Each framework has features and benefits that make them different.
But I have selected asp.net with c# for the development of my project. There are plenty of good
reasons to used asp.net and developing a website or an application:-high speed low cost and vast
language support are among the most significant benefits.it gives you full control of your
development and can easily be used on any project, big or small and Abdation can be done using
this language.

Page 8
Gantt chart

Page 9
 Phase Sub phase Expected Date Actual Date of Remarks
of Completion Completion

1.Preliminary Investigation

1.Organizational
Overview

2.System
Description

3.Feasibility Study

2.System Analysis

1.Collection of
System
Requirements

2.Modelling Events

3.Modelling
classes/objects

4.Identifying
Activities &
Sequences

3.System Designing

1.Designing
Database Tables

2.Components,
Package &
Deployment
considerations

4.System Coding

1.Program Coding

2.Testing &
Validations

3.System
Integration

5.System Implementation

6.Project Review by Guide Page 10

7.Feedback for Improving, correcting &

Modifying the Project
 Chapter 3: System Design

Module division
Online frankie shop consist of following module

1)administrator

2)customer

3)supplier

4)employee

Administrator
administrator has a facility to manage and control all the task which are perform by other
customer,supplier,employee.it is manly used to verify the details of user and to provide authentication for
delivery or odereing of frankie.

Customer\user
The user is provided with a list of frankie shop available in a cerain area as per his request.upon
selection,the user is given a choice to view either the veg or nonveg menu.the user is provided with list of
frankie along with their prices as per the veg or nonveg option selected.the user can also place an order and
collect it based on the token number provided.

Supplier
The role of supplier is to deliver the frankie to the authenticate user within time.

Employee
The role of employee is to fulfill the order of user as per his requirement and make the bill.

Page 11
Data dictionary
A tool for recording and processing information (metadata) about the data that and organisation uses

Customer
Field Name Data Type Size Description
Customer Id Varchar (MAX) Customer ID
Name Varchar (MAX) Customer Name
Gender Radio Button Customer Gender
Address Varchar (MAX) Customer Address
Contact No Varchar (MAX) Customer Contact No
Email ID Varchar (MAX) Customer Email ID
Shipping order Varchar (MAX) Customer Shipping order
Address address
Payment Mode Varchar (MAX) Customer Payment Mode
Amount Varchar (MAX) Customer Product
type Amount

Employee
Fields Name Data Type Size Description
ID Varchar (MAX) Employee Id
Name Varchar (MAX) Employee Name
Contact Varchar (MAX) Employee Contact
Address Varchar (MAX) Employee Address
Date of Birth Varchar (MAX) Employee Birth Date
Date of Joining Varchar (MAX) Employee Joining Date
Salary Varchar (MAX) Employee Salary

Page 12
 Product
Field Name Data Type Size Description
Id Varchar (MAX) Product ID
Name Varchar (MAX) Product Name
Company Varchar (MAX) Product Company
Total Quality Varchar (MAX) Product Quality
Quality Per Price Varchar (MAX) Product Quality Per Price
Total Price Varchar (MAX) Product Total Price

Customer Bills
Field Name Data Type Size Description
Customer id Varchar (MAX) Customer ID
Customer Name Varchar (MAX) Name Of customer
Product name Varchar (MAX) Product Name
Date of Bill Varchar (MAX) Date Of customer Bill
Amount Mode Varchar (MAX) Customer Payment Mode
Amount Varchar (MAX) Customer total Amount

Page 13
 Product Type
Field Name Data Type Size Description
ID Varchar (MAX) Product Type ID
Name Varchar (MAX) Product Type Name
Price Varchar (MAX) Product Type
Amount

Page 14
 Supplier

Field Name Data Type Size Description

Supplier Id Varchar (MAX) Id of Supplier

Name Varchar (MAX) First name of Supplier

Date Of Birth Varchar (MAX) Supplier Date Of Birth

Gender Varchar (MAX) Supplier Gender

Address Varchar (MAX) Address of Supplier

Contact No Varchar (MAX) Contact No of Supplier

Email-Id Varchar (MAX) Email-Id of Supplier

43

Page 15
 2
Use case diagram:
1. Use case for Frankie shop:-

Manage
Customer
record

Manage Employee
record

Manage Supplier
record

Manage Items
record

Manage Purchase
Record

Manage sale
record

Admin

Manage Report

16
 2. Use Case for Customer:-

Enquiry about
Product

Selecting the
Product

Login Account

Ordering the
Product

CUSTOMER Fill up information

about delivery

Get Bill

Pay Bill

17
 3.Use case for Employee:-

Provide
Information

Provide Information
about the Product

EMPLOYEE Delivery of
Product

18
 4) Use case for Supplier:

Get Order

Supply
Product

Supplier
Get
Payment

Prepare Bill

19
 Entity Relationship Diagram

Address
Id
EMP DOB Address
Name
Gender Name
Contact No
Contact

Employee
Customer Gender
E-mail

ID

Online pizza shop

Work

For Product

Supplier Type
E-mail

Name Salary Name

Price
Company
Contact
Address ID

20
 Data Flow Diagram

Order management

Pizza management Delivery

management
Online
pizza
ordering
system
System user
Order management
management

Login management

Zero Level DFD-online pizza ordering system

21
Pizza management Generate pizza report

Pizza cart Generate pizza cart

management report

Order management Generate order

report

Delivery Address Online Generate delivery

Management pizza address report
ordering
system
Login Management Check user login
details

System user Generate system user

Management report

First Level DFD-online pizza ordering system

Login to Check
Admin role of
system
Access Manage Pizza Details 22
 Manage Pizza
coupan details
Forgot Check Manage
password credentials modules Manage order
Details

Manage Customer
Details

Send Manage Pizza cart

email to Details
user
Manage cash Details

Manage system Manage Roles of Manage User

Manage Report
Admins user permissions

Second level DFD-online pizza ordering system

Activity Diagram
23
 1) Create Customer Record :
Collect Fill Save
Customer Info Customer Info Record

2) Update/Delete Customer Record:

Search Update/Delete Save

Record Record Changes

1) Create Employee Record :

Collect Fill Save

Employee Info. Employee Info. Record

1) Update/Delete Employee Record:

Search Update/Delete Save

Record Record Changes

24
Class Diagram:

Customer Master Supplier Master

Customer Id Supplier Id
Customer Name Supplier Name
Customer Address Supplier Address
Contact No Email-Id
Product buyed Contact No
Date of Birth
add () Gender
update ()
delete () add()
display () update()
search() delete()
Employee Master display()
search()
Employee Id View()
Employee Name Save()
Employee Address Product Master
Email-Id
Contact No. Product Name
Quantity
add() Price
update()
delete() add()
display() update()
search() delete()
view() display()
search()

Customer Bill Order

25
Bill Id Order Id
Bill Date Order Date
Supplier Id
Customer Name
Employee Salary

Employee Id
Salary Date
Employee Name
Employee Gender
Employee Address
Employee Salary

add()
delete()
update()
search()

26
Class Association Diagram:-

1 Gives *
Customer Supplier Products

Take *
*

Gives has
Include
*
1 1
*
Bill Order Report
1has 1

27
Sequence Diagram

:Customer :Employee :Stock :Supplier

1.ProductEnquiry()

LookUpProduct()
2.Available()

3.ProductNotAvailabl
e
PlaceOrder()

4.FullFillOrder()

5.ArrangeOrder()

28
COLLABORATION DIAGRAM

New Customer Entry:

1.1 Collect Information

()1.2 Save Record ()
1. New Record
CH: User : Customer
Interface

Update Customer Entry:

Update Member 1.1 Search Record

Record 1.2 Update Record
CH: User : Customer
Interface

29
Delete Customer Entry:

Delete Member 1.1 Search Record

Record 1.2 Delete Record
CH: User : Customer
Interface

Customer Bill Entry:

: Paid bill

1.2 Receive Bill ()

1.3 Paid Bill ()

1.4 Save Bill ()

CH: User : Customer
Interface

30
COMPONENT DIAGRAM

Manage DB

Access DB Customer

Database

Manage DB

Access DB Employee

Database

Manage DB
Product
Administrator
Type
Access DB
Database

Manage DB
Customer

Bill
Report Access DB
Database

Manage DB
Employee

Salary
Access DB
Database

Manage DB
Remaining

Bill
Access DB
Database
31
Package Diagram

User Report
Interface
Master Customer Bill

Information Employee Report

Transactions Product Type Structure

Reports Add Customer Form

Database
Customer

Employee

Product Type

Bill

Product Information

32
Deployment Diagram:

Database
DB: Database
Server

Printer Printer

System Admin

(Executable)

App. Common App.

Server (Executable)

Manage Res. Manage Project

Desktop Desktop
(Executable) (Executable)
Client Client

(Owner) (Clerk)

33
 Conclusion and
Future Enhancement

34
 Conclusion
This website is developed as simple as possible to use. Being user friendly
software the user does not find any difficulty in using it.

Keeping details, records of each and every Products, and Customers is a very lengthy,
costly and tedious job in manual system. This software overcomes these problems with less
maintenance.

Future Enhancement
To improve the performance of the project we have planned to carry out following
enhancements:
Today “Online Frankie Order” is working manually. We have made this
system Computerized but it is Windows Based.

This system can be enhanced in very attractive manner in future:

We can implement this system as Web Based Application.

By making a Web site we can launch this website worldwide. So that there will be no need to
interact with the administrator each time. The system will manage all applications by its own.

35
 Bibliography

 ASP.Net and c# with programming (Black Book)

 Beginning Visual C# 2012

 Program and design with ASP.Net

 www.sourcecode.com

 Google.com

36