SMT.

SUSHILADEVI DESHMUKH COLLEGE OF ARTS,

SCIENCE AND COMMERCE Airoli, Sector 4, Navi Mumbai-400 708

“Project Name”
A Project Report

Submitted in partial fulfilment of the

Requirement for the award of the Degree of

BACHELOR OF SCIENCE ( COMPUTER SCIENCE )

By

Your Name

( BACHELOR OF COMPUTER SCIENCE )

5TH SEM

Under the Guidance of

PROF.PRAKASH NAIK
Department Of Computer Science
SMT. SUSHILADEVI DESHMUKH COLLEGE OF ARTS,SCIENCE & COMMERCE

AIROLI, NAVI MUMBAI 400 708

MAHARASHTRA

YEAR 2024-25

(Affiliated to University of Mumbai)

 (TYB.Sc.CS)-Semester-V, Examination 2018-19
University of Mumbai

SMT. SUSHILADEVI DESHMUKH COLLEGE OF

ARTS, SCIENCE AND COMMERCE Airoli, Sector 4, Navi Mumbai-400708

Date : _________________

Certificate

This is to certify that the Project entitled Online Cake Shop Management Undertaken at the
Smt. Sushiladevi Deshmukh College of Arts, Science And Commerce by Mr. Piyush
Pradeep Chaudhary Seat no : _____________ in partial fulfillment of BSc Computer Science
Degree (Semester V) Examination had not been submitted for any other examination and does
not form part of any other course undergone by the candidate. It is further certified that they
have completed all required phases of the project.

Signature of Internal Guide Signature of HOD

Signature of External Principal

College Seal

PREFACE
Z
It is great opportunity for me to present this project on a topic – “Google assistant
by using Raspberry Pi” as the Final Year Project.

This report consists of all the basic knowledge needed for software development
along with various diagrams and charts.

I have taken complete care to include almost all modules related to the topic and
put it up in an interesting and an attractive format.

This system provides features of low rate of data inconsistency.

We involved in this project have worked with commitment right from the
Initialization of the project and continuing all the way till its completion.

Review of the project is an unending process; it may contain errors, as there is

always scope for improvements.

The content of the project is true and verified and aims to give a simple and clear
understanding of the design and implementation of the software.
 ACKNOWLEDGEMENT

I would like to acknowledge and extend my heartfelt gratitude to the following

people who have made the completion of my project possible.

I extend my heartfelt gratitude and thanks to Prof. Dnyaneshwar Deore and for
providing me excellent guidance to work on this project and for their
understanding and assistance for providing all the necessary information needed
for completing the project.

I would also like to acknowledge all the staffs for providing a helping hand to us in
times of queries & problems. The Project is a result of the efforts of all the people
who are associated with the Project directly or indirectly, who helped me to
successfully complete the Project within the specified time frame.

Thanks to our Head of Department Dr. Prakash Naik and Prof. Soni Yadav for
being a part of the project in numerous ways and for the help and inspiration they
extended to me and for providing the needed motivation.

I would like to thank our Lab Assistant Mr. Vijay Singh for providing a helping
hand.

I would like to thank our Principal Mrs. Shalini Vermani for keeping my Spirits
High and Motivated.

With all Respects & Gratitude, I would like to Thanks to all the people, who have
helped in the Development of the Project.
 By

Pratik Balu Raut

Sr.No CONTENT Page No.

1.0 PRELIMINARY INVESTIGATION 1

1.1 Organizational Overview 2

1.2 Description of System 3

1.3 Limitations of Present System 4

1.4 Scope of the Project 5

1.5 Proposed System 6

1.6 Advantages of Proposed System 7

1.7 Feasibility Study 8

1.8 Stake Holders 10

1.9 Gantt Chart 11

2.0 Operating Environment 12

3.0 System Analysis 14

3.1 Fact Finding Techniques 15

3.2 ER Diagram 17

3.3 Class Diagram 23

3.4 Object Diagram 24

3.5 Event Table 25

3.6 Usecase Diagram 26

3.7 Sequence Diagram 28

3.8 Activity Diagram 30

4.0 System Design 32

4.1 Converting ERD to Table 33

4.2 Component Diagram 41

4.3 Development Diagram 42

5.0 System Coding and Implementation 43

5.1 Form Design 44

5.2 Coding 83

5.3 Validation 134

5.4 Test Case, Test Data and Test Results 134

6.0 Future Enhancements for Project Report 138

7.0 Bibliography 139

.
 Chapter 1
Preliminary Investigation
 Organizational Overview

An intelligent and effective use of available resource the key to any successfully
adventure. In this complex and competitive business world planning the
organization and well coordination of this resource matter the most.

One of the major finding of research was, the realization that a systematic
approach to their requirement information was lacking in this organization due to
variety of constraints. It was therefore felt that a professional approach to address
this problem would provide some relief of these organizations.

The” Cake Ordering System (COS)”activity is based on ordering and selling the
cake for each customer. Each customer will be given unique order number. As
soon as this the customer’s name and contact details are added for reference. Next
the cake is selected and stuffing type is also added if required. The user should
enter the date of delivery and also the quantity. A separate bill is produced for the
confirmation and the customer can do any advance payment. During the day of
delivery, the customer will be producing the bill of order. According to it, again a
bill is generated for selling purpose and the customer is supposed to pay the
balance amount. All the data’s are being stored in the database.
Admin has the authority to add cake details, flavour details and rate. And
he also has the right to edit and delete those details to/from the list. Admin
provides username and password for each user. At the end of the day report is
generated to calculate the payment for each user in each day.

Chapter 2
System Analysis
 Description of System

Existing System:-

 In present non-computerized system all jobs are performed manually. All records of
Employees, Customers, and Sales & Purchase are written and stored in paper format in a
file.

 Prop writer maintains separate files for each new information. So managing them is very
complex and has become an impossible task to be performed manually systematic way.

 As the job is done manually, it has its own limitations and lot’s of paperwork.

 Preparation of records on yearly basis becomes a tedious and time-consuming job still its
authenticity is always debatable and can’t be verified easily.

 The yearly records, which are done manually, are not easy to maintain in files, which can
be destroyed anytime by any person.
 Time required for searching records of particular item is also difficult. Maintaining the
records of each and every minute detail of every item is also very difficult.

 Any manual error can lead to wrong result. This system is unable to provide timely report
information.

Limitation of Existing System:-

 In present system each and every record is maintained in files, so there will be lot of
redundancy in maintaining ‘suppliers or distributor’ records.

 Also there is no security as all records are maintained in files.

 Modification of one record causes changes to other records related to that record, so
work becomes very critical, there are chances of data loss

 Storage of information is costly.

 Require knowledge about the system

 Searching any old record requires more time due to critical system of register

 Present system is very time consuming.

 A lot of paperwork is maintain

  Difficult in maintaining records

 It is difficult to keep through registers for many years or months safely.

 There are many chances of mistakes as all the data is handled manually.

 Bill calculation there are chances of errors which results in wrong billing data.

 Maintenance of registry is difficult because any register is lost then there will be big
loss of data.

The Proposed System:-

 The proposed system is computerized and has been developed using advance language
therefore it gives more facilities than present system.

 It provides quick access to any data.

 Features of project include aspects such as to make my software user friendly i.e. to make
it so easy to use that the user will not dream of switching back to the original System.

 By user friendly we mean to make records available to the user at just the hit of a
keystroke.

 To maintain the list of Orders, to maintain records of Suppliers and Distributors, to

maintain records of bill, to maintain the order details. To add/update/search them from
the database-all these features have been considered for the management of the system.

 Besides maintaining the data in the database the system also has the provision for printing
various reports.
 The system helps reduce the paper work and provide an efficient environment that is user
friendly to work in.

Advantages of Proposed System:-

 The system is platform independent as it is developed in C# Windows Application.

 It facilitates quick processing of data.

 Data present in database is highly secured.

 Searching of data is done very easily & more efficiently.

 There is no fear of loss of data or data corruption.

 Maintaining of data is very proper & accurate.

 Information of any Item can be retrieved any time.

 It provides facility to modify records.

  Information of each item with its record can be maintained in computer & user will not
have to maintain file/paperwork.

 It will save user time.

 User can get several responses at a place.

 User can get information about several items at a place.

 Report will be generated automatically.

Feasibility Study
Feasibility study tells whether the system would be beneficial for the organization with respect to
the requirements of the organization. Feasibility study is divided into the following phases:

(1) Operational Feasibility:

Operational feasibility is dependent on the human resources available for the project
and involves projecting whether the system will operate and used once it is install. It is
mainly concerned with the availability of human resources for the project. In the Cake
Ordering System, different departments and members are assigned according to their jobs.

(2) Technological feasibility:

Technical feasibility is a measurement of the practicality of a specific technical
solution and the availability of technical resources and expertise. In the Cake Ordering
System we use two specific languages i.e. C# as Front End and SQL Server as Back End. To
use this languages we use respected software i.e. C# and SQL Server 2008 respectively. The
whole management managed in windows 7 operating system. In hardware specification, we
use Processor of 2 GHz, RAM (1GB) and free Hard Disk Space.
(3) Economical and financial feasibility:
Economical feasibility is the measurement of the cost effectiveness of the project proposed
system. Costs are practically impossible to estimate at that stage because the end user
requirement and alternative technical solutions have not identified.
In Cake Ordering System, economical feasibility consists of cost of menus, salary of
all employee and overhead. However, as soon as a specific requirement has been identify.
The analyst can Weight the cost and benefit of each alternate solution.

Hence, in economical feasibility we see what cost is required to implement the new system. This
system includes maintenance of the system.

Stakeholders
Stakeholders are anyone who has an interest in the project. Project stakeholders are individuals
and organization 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 stakeholder,
determine their requirement and expectations and to the extent possible, manage their influence
in relation to the requirement to ensure a successful project.

The following are examples of project stakeholders:

1. Project developers:

A project developer is one who develops software for customer. In my project I am the
stakeholder i.e. project developer.

2. Project customer:

A project customer is one who pays for the developed software.

3. Project user group:

 Project user group are those people who use the software on daily basis for the project
customer.

4. Project tester:

Project testers are those who test the software. In my project myself, my project guide
and technical department are the fourth stakeholders i.e. project tester.

Visual Studio 2008

Developing our project in vb.net was our first choice. Vb.net is an ideal programming
language for developing sophisticated application. It makes use of “GUI” for creating robust
and powerful application. The design environment provided by visual studio 2008 is easy to
use; since we can success all the development tools that we need for, one screen vb.net
feature such easier comprehensive, and many other aspects make vb.net an interesting tool to
work.

Microsoft Sql Server 2008

Microsoft SQL Server 2008 is a database software package. A database is an organized

collection of records. Telephones and address books are examples of paper database. With
SQL you can create a computerized database .for example; you can use access to organize a
student who attend a school, the courses they take and the instructors who teach them. After
you create an SQL database, you can search it manipulate it, and extract information from it
this lesson introduces you to access windows and teach you how to create database.

Software Specification :-

 Front End : C#.NET

 Back End : SQL Server 2008
  Operating System : Windows 7
 For Documentation : Microsoft Office 2007

Hardware Specification :-

 Processor :- Pentium IV onwards

 RAM :- 512 MB onwards
 Free Hard Disk Space :- 2 GB or more

GANTT CHART

Oct(2016) Oct(2016)- Nov(2016)- Dec(2017)- Jan(2017)

Month Nov(2016) Dec(2016) Jan(2017) Feb(2017)

Weeks Weeks Weeks Weeks Weeks

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Planning

Requirement
gathering

Analysis
 Design

Coding

Testing

Implementatio
n

Chapter 3
System Design
 Fact Finding Technique
To study any system the analyst needs to do collect facts and all relevant information. The facts
when expressed in quantitative form are termed as data .accurate information can be collected
with the help of certain methods or techniques. These specific methods for finding information is
called fact finding techniques

The analyst may use more than one technique for investigation.

Interview:

This method is used to collect the information from groups or individuals. Analyst selects the
people who are related with the system for an interview. In this method the analyst site face to
face with the people and records their responses.

Questionnaires:

It is technique used to extract information from number of people. This is cheapest source of fact
finding. It consists of series of questions framed together in logical manner. The questions are
simple, clear and to the point.
 Record view:

The information related to system is published in sources like journals, documents etc. This
record review helps the analyst to get valuable information about the system.

Observation:

Analyst himself visits the organization and observes and understand flow of documents, working
of the existing system, the user of system etc Analyst may observed unwanted things as well and
simply cause delay development of new system

Event Table

SR.NO EVENTS TRIGGER SOURCE ACTIVITY RESPONCE DESTINATION

1. OWNER ADD NEW OWNER CREATE NEW PRODUCT OWNER

PRODUCTS PRODUCT PRODUCT CONFIRMATION

DETAILS DETAILS DETAILS

2. OWNER REQUESTIN OWNER MODIFY PRODUCT OWNER

MODIFIES G FOR PRODUCT DETAILS

PRODUCT MODIFYING DETAILS MODIFICATION

DETAILS PRODUCT CONFIRMATION

DETAILS
3. OWNER REQUESTIN OWNER DELETING PRODUCT OWNER

DELETE G FOR PRODUCT DETAILS DELETE

PRODUCT DELETING DETAILS CONFIRMATION

DETAILS PRODUCT

DETAILS

4. OWNER PRODUCT OWNER LOOK-UP PRODUCT OWNER

SEARCH DETAILS PRODUCT DETAILS

PRODUCT ENQUIRY AVAILABILITY

CONFIRMATION

5. OWNER ADD NEW OWNER CREATE ADD CUSTOMER OWNER

CUSTOMER CUSTOMER CUSTOMER DETAILS

DETAILS DETAILS DETAILS CONFIRMATION

6. OWNER REQUESTIN OWNER LOOK-UP CUSTOMER OWNER

SEARCH G FOR CUSTOMER RECORD

CUSTOMER ENQUIRY RECORD AVAILABILITY

RECORD OF

CUSTOMER

RECORD

Page 17 of 131
7. OWNER REQUESTIN OWNER UPDATE CUSTOMER OWNER
UPDATE G FOR CUSTOMER DETAILS
 CUSTOMER UPDATE DETAILS UPDATE
DETAILS CUSTOMER CONFIRMATION
DETAILS
8. OWNER ENQUIRY OWNER LOOK-UP CUSTOMER OWNER
SEARCH FOR CUSTOMER DETAILS
CUSTOMER CUSTOMER AVAILABILITY
DETAILS DETAILS CONFIRMATION
9. CUSTOMER ITEM CUSTOMER LOOK-UP FOR ITEM DETAILS OWNER
MAKES ENQUIRY ITEM
ENQUIRY AVAILABLE
ABOUT ITEM
10. CUSTOMER ORDER CUSTOMER CREATE ORDER DETAILS OWNER &
PLACE ORDER PLACEMENT CUSTOMER CUSTOMER
RECORD &
CREATE
ORDER
11. CUSTOMER REQUEST OWNER UPDATE ORDER OWNER &
UPDATE FOR ORDER & UPDATED CUSTOMER
ORDER UPDATE ITEM DETAILS
ORDER
12. CUSTOMER REQUEST OWNER CANCEL CANCELATION OWNER
CANCEL THE TO CANCEL ORDER RECEIPT &
ORDER THE ORDER REFUND
13. CUSTOMER REQUEST CUSTOMER GENERATE BILL CUSTOMER
DEMAND FOR FOR BILL BILL GENERATED
BILL
14. OWNER PLACE PURCHASE OWNER CREATE NEW LIST OF ALL OWNER
ORDER TO ORDER PURCHASE ITEM TO BE
SUPPLIER ORDER & PURCHASED
ITEM DETAILS FROM THE
SUPPLIER
 Use Case Diagram

Use Case Diagram

Figure 2.1
ENTITY RELATION DIAGRAM
CAKE SUPPLIER CAKE PRODUCT

ENTITY RELATION DIAGRAM

Figure 2.2

Activity Diagram
Activities between supplier and distributers

Activity Diagram:
Figure 2.3
 Activities between Customer and distributor

Figure 2.4
r
 CLASS DIAGRAM

Cake Supplier Employees

+ID
+ID
+Name
+Name *
1 Distributor 1 * +qualification
+Address
+Salary
+Contact +id +contact
+compny name +name +Address
+Email id +contact
+email ID +insert
+insert
+update
+update +cancel +delete
+delete +reset

1 1 1

*
Cake Products

+id
1 +name *
+stock
* 1
+type Customer
Order
+price
+id
+Date
+insert +name
+Order no
+update +Address
+Customer ID
+delete +contact
+NO. of items Purchased
+company name
+Amount Bill
+Email Id
+update
1 1 +insert
+update
+delete

CLASS DIAGRAM
Figure 2.5
 OBJECT DIAGRAM

Cake Supplier Employees

+MDE12
+Ms1
+Kiran
+Vinod *
1 Distributor +Bcom
+Airoli 1 *
+4000
+9702244635 +MD11 +987839330
+KD +Anil +Vashi
[email protected] +98384939483
[email protected] +insert
+insert
+update
+update +cancel +delete
+delete +reset

1 1
1

*
Cake Products

+Mdp1
1 +WArna *
+290 1
*
+Cow Customer
Order
+18
+MDC1
+7/12/2012
+insert +Suraj
+MDO1
+update +KK
+MDC1
+delete +8293849506
+12
+Kirana
+512
[email protected]
+update 1 1 +insert
+update
+delete

OBJECT DIAGRAM

Figure 2.6
 SEQUENCE DIAGRAM

SUPPLIER DISTIBUTOR CUSTOMER

1 : Enquiry about Cake()

2 : Getting details()
3 : Supplier registration()
4 : Place an order()

5 : Order fulfilment()

6 : Check order()
7 : Paying Bill ()

8 : Getting receipt()
9 : Enquiry about Cake()

10 : Getting details about product()

11 : Customer registration()

12 : Place an order()

13 : Order confirmed()
14 : Store order details()

15 : Check order status()

16 : Order fulfilment()

17 : Check order()

18 : Paying bill()
 SEQUENCE DIAGRAM
Figure 2.7
STATE DIAGRAM

ENQUIRY
IDLE
REGISTRATION

Asking for product

GIVING DETAILS

Place order

ORDER CONFORM

Check order status

ORDER FULFILMENT

Check order

PAYING BILL

Reciept Generation

GETTING RECIEPT
 STATE DIAGRAM
Figure 2.8

CONVERTING ERD TO TABLES

1) CUSTOMER DETAILS

1) custid

2) custname

3) address

4) mobile

5)Email

2) SUPPLIER DETAILS

1) s_id

2) s_name

3) cname

4) address

5) mobile no

3) Product Details

1) p_id

2) pname

3)ptype
 4) qty

5) price

6)color1

4) CUSTOMER _ORDER

1) Order_id

2) Custname

3) cmobile

4) productname

5) ptype

6) weight

7) qty

8) price

9)Orderdatel

10)Totalamt

5) Supplier_ORDER

1) Orderid

2) suppliername

3) smobile

4) email

5) productname

6) ptype
7) weight

8) qty

9)price

10)orderdate

11)totalamt

DESIGN CLASS DIAGRAM [WITH UI CLASSES]

Cake Supplier Employees

+ID
+ID
+Name
+Name *
1 Distributor 1 * +qualification
+Address
+Salary
+Contact +id +contact
+compny name +name +Address
+Email id +contact
+email ID +insert
+insert
+update
+update +cancel +delete
+delete +reset

1 1 1

*
Cake Products

+id
1 +name *
+stock
* 1
+type Customer
Order
+price
+id
+Date
+insert +name
+Order no
+update +Address
+Customer ID
+delete +contact
+NO. of items Purchased
+comapny name
+Amount Bill
+Email Id
+update
1 1 +insert
+update
+delete

DESIGN CLASS DIAGRAM [WITH UI CLASSES]

Figure 3.1
Component Diagram
Cake Ordering
System

Component Diagram

Figure 3.2

PACKAGE DIAGRAM
 LOG MANAGEMENT
SYSTEM

CAKE MANAGEMENT SYSTEM

ADMIN CUSTOMER
MANAGEMENT MANAGEMENT
SYSTEM SYSTEM

REPORT
MANAGEMENT
SYSTEM

SUPPLIER EMPLOYEE
MANAGEMENT MANAGEMENT
SYSTEM SYSTEM

PACKAGE DIAGRAM

Figure 3.3

DEPLOYMENT DIAGRAM
 BILL

CUSTOMER
SUPPLIER

PRODUCT

EMPLOYEE

Cake
Ordering
System

DEPLOYMENT DIAGRAM

Figure 3.4

PROGRAM FLOW CHART

 Start

Check for
Availability of stock

Find product

Get customer details

Received charges

Deliver the
Product

Stop
PROGRAM FLOW CHART

Figure 3.5

Chapter 4
System Coding

MENU TREE
MDI FORM

MASTER

CUSTOMER DETAILS

SUPPLIER DETAILS

EMPLOYEE DETAILS

PRODUCT DETAILS

TRANSACTION

CUSTOMER ORDER

SUPPLIERORDER

SALARY

REPORT SCREEN

CUSTOMER BILL REPORT

CUSTOMER BILL REPORT

UTYLITIES

CALCULATOR

NOTEPAD

WEB ACCESS

PHOTO GALLERY

HELP
 LIST OF TABLES WITH ATTRIBUTES & CONSTRAINTS
TABLE 4.1 :- LOGIN

COLUMN NAME DATA TYPES ALLOW NULL

Username Varchar(10) Not Null
password Varchar(10) Not Null

TABLE 4. 2 :- CUSTOMER_DETAILS

COLUMN NAME DATA TYPES ALLOW NULL

C_ID VARCHAR (50) PRIMARY KEY

C_NAME VARCHAR (50) NOT NULL

ADDRESS VARCHAR (50) NOT NULL

MOBILE VARCHAR (50) NOT NULL

EMAIL VARCHAR (50) NOT NULL

TABLE 4.3 :- Supplier_Details

COLUMN NAME DATA TYPES ALLOW NULL

SID VARCHAR (50) PRIMARY KEY

SNAME VARCHAR (50) NOT NULL

CNAME VARCHAR (50) NOT NULL

ADDRESS VARCHAR (50) NOT NULL

MOBILE VARCHAR (50) NOT NULL

 EMAIL VARCHAR (50) NOT NULL

TABLE 4. 4 :- P RODUCT_DETAILS

COLUMN NAME DATA TYPES ALLOW NULL

P_ID VARCHAR (50) PRIMARY KEY

PNAME VARCHAR (50) NOT NULL

PTYPE VARCHAR (50) NOT NULL

QTY NUMBER NOT NULL

PRICE NUMBER NOT NULL

COLOR1 NUMBER NOT NULL

TABLE 4. 5 :- EMPLOYEE_DETAILS

COLUMN NAME DATA TYPES ALLOW NULL

E_ID VARCHAR (50) PRIMARY KEY

E_NAME VARCHAR (50) NOT NULL

MOBILE VARCHAR (50) NOT NULL

DESIGNATION VARCHAR (50) NOT NULL

GENDER VARCHAR (50) NOT NULL

ADDRESS VARCHAR (50) NOT NULL

JDATE DATETIME NOT NULL

TABLE 4.6 :- CUSTOMER_ORDER

COLUMN NAME DATA TYPES ALLOW NULL

ORDER_ID VARCHAR (50) NOT NULL

CUSTNAME DATETIME NOT NULL

CMOBILE VARCHAR (50) NOT NULL

PRODUCTNAME VARCHAR (50) NOT NULL

PTYPE VARCHAR (50) NOT NULL

WEIGHT VARCHAR (50) NOT NULL

 QTY VARCHAR (50) NOT NULL

PRICE VARCHAR (50) NOT NULL

BILL NUMBER NOT NULL

TABLE 4.7 :- SUPPLIER _ORDER

COLUMN NAME DATA TYPES ALLOW NULL

SID VARCHAR (50) NOT NULL

SNAME DATETIME NOT NULL

CNAME VARCHAR (50) NOT NULL

ADDRESS VARCHAR (50) NOT NULL

VARCHAR (50) NOT NULL

MOBILE

EMAIL NUMBER NOT NULL

TABLE 4.8 :- employee_salary

COLUMN NAME

DATA TYPES ALLOW NULL

ID INT NOT NULL

EMPNAME VARCHAR (50) NOT NULL

DESIG VARCHAR (50) NOT NULL

SALDATE VARCHAR (50) NOT NULL

BASIC VARCHAR (50) NOT NULL

PARDAYSAL VARCHAR (50) NOT NULL

ABSENT VARCHAR (50) NOT NULL

 PRESENT VARCHAR (50) NOT NULL

ABSENTDEDUCTION VARCHAR (50) NOT NULL

PRESENTTOTAL VARCHAR (50) NOT NULL

PF VARCHAR (50) NOT NULL

PT VARCHAR (50) NOT NULL

NETSAL VARCHAR (50) NOT NULL

PROGRAM DESCRIPTIO/N WITH NAMING

CONVENTIONS

In the development of the project, naming conventions are followed. The names begin with a
three or four letter prefix, which identifies the object type (such as Label, textboxes, Form etc.)
and the first character prefix has been specialized. All the names are meaning and indicate the
purpose of the object.

Sr. No OBJECT DESCRPTION NAME

1 FORM FORM FRM

2 TEXT BOX INPUT FIELDS TXT

3 MENU BAR MENU BAR MB

4 LABEL LABEL LBL

5 COMBO BOX LIST THE ITEMS CMB

 6 BUTTON PERFORN AN ACTION BTN

7 CRYSTAL REPORTS REPORT GENERATION RPT

8 DATAGRIDVIEWER SHOW DATA FROM TABLE DATAGRIDVIEWE

R

9 GROUPBOX LIST OF CONTROLS AND DETAILS GROUPBOX

10 RADIOBUTTON SELECT ANY ONE OPTION RB

11 PICTUREBOX SHOW PICTURE ONFORM PICTUREBOX

VALIDATIONS

1) Check the eligibility of the Customer.

2) Check whether the Customer has paid all the previous

charges if customer is an existing customer.

3) Check whether the customer has submitted all the necessary

documents.

4) Check if the documents submitted related to personal

information are valid or not.
5) Check the payment details of each Customer.
6) If the Customer is a new then check all the personal details.
 TEST CASES
CUSTOMER_DETAILS

FIELD NAME VALID VALUES INVALID VALUES

C_ID C11 C1.1,C

C_NAME VISHAL @AM,&*N

C_ADD AIROLI ,NAVI MUMBAI NVI,MUMBUI

CONTACT 8355927064 998548

Supplier_Details

FIELD NAME VALID VALUES INVALID VALUES

S_ID S11 S12,6

S_NAME SURESH SU &%M

S_ADD THANE (W) TAH &,NE

CONTACT 8355927064 998@*548

PRODUCT_DETAILS

FIELD NAME VALID VALUES INVALID VALUES

 P_ID P11 P&%12
PRODUCT _NAME WARNA MILK WAR&*5K MILK

PRODUCT _TYPE COW MILK E@G&

STOCK 200 GSGS

SELLING _PRICE 16 KJ78

EMPLOYEE_DETAILS

FIELD NAME VALID VALUES INVALID VALUES

E_ID E11 E21%

E_NAME GAURAV NJA7766

WORKING _AS COMPUTER 7822JJV9

OPERATOR

QUALIFICATION BSC 89988

E_ADD THANE (W) 788JKKK
CONTACT 8895958659 12125
D_O_J 2/2/2013 KAJK&#/121

CUSTOMER _ORDER

FIELD NAME VALID VALUES INVALID VALUES

ORDER_ID O11 O1./2

ORDER_DATE 2/2/2013 KAJK&#/121

C_ID C11 C&%12

C_NAME MANOJ 1245

P_ID P11 JKJ09

P_NAME WARNA MILK BLA&*5K FOREST

NO_ITMS 12 E@G&

PRICE 20 GSGS

BILL 500 KJ78

PURCHASE_AN_ORDER

FIELD NAME VALID VALUES INVALID VALUES

O_ID O11 O1./2

O_DATE 2/2/2013 KAJK&#/121

S_ID S11 S&%12

P_ID P11 JKJ09

P_NAME WARNA MILK BLA&*5K FOREST

NOITEMS 12 E@G&

PRICE 20 GSGS

BILL 500 KJ78

SCREEN LAYOUTS

SPLASH SCREEN : -
LOGIN FORM : -
MDI FORM : -
SUPPLIER DETAILS : -
PRODUCT DETAILS :

-
EMPLOYEE DETAILS : -
CUSTOMER ORDER : -
SUPPLIER ORDER : -
SALARY : -
 REPORTS LAYOUTS

CUSTOMER BILL REPORT

SUPPLIER ORDER REPORT
EMPLOYEE SALARY REPORT
 Chapter 5
System Testing

TESTING

Testing is a procedure where all the modules are run, their validations are
checked, the Backend compatibility is verified and all the errors called “Bugs”
are eliminated to the best possible extent.

Since my Front End is Microsoft Visual Basic 6.0 the following are types of
Testing done by me.

 Step by Step Execution : -

Here, the code was run and step by stem and the execution flow in case of
Looping and branching constructs for all the possible conditions, including
errors were verified. This was done twice for every Module.

 Breaks on Variables : -
Here, Breaks were put on a particular variable and it was checked that
whether it contains the expected value or not, whenever the variable changes
the value throughout the Module. This procedure was repeated twice for all
the important global variables in a Module.

System Testing :-

System testing is the type of testing to check the behavior of a complete and
fully integrated software product based on the software requirements
specification (SRS) document. The main focus of this testing is to evaluate
Business / Functional / End-user requirements.
Unit Testing :-

Unit testing is a software development process in which the smallest testable

parts of an application, called units, are individually and independently
scrutinized for proper operation. Unit testing is often automated but it can
also be done manually

The same above procedure was implemented for variables global to the whole
system.

Chapter 6
System Review
 1) Formal Technical Review

A method involving a structured encounter in which a group of technical

personnel analyzes or improves the quality of the original work product
as well as the quality of the method.
Reviews reduce rework.
Rework accounts for 44% of dev. cost!
Reqs (1%), Design (12%), Coding (12%), Testing (19%)
Reviews are more productive than testing.
Find more errors in the same amount of time.
Reviews are more effective than testing.
Find errors not possible through testing.
Reviews are training.
Domain, corporate standards, group.

2) Informal Technical Review

Informal reviews are applied many times during the early stages of the life
cycle of the document. A two person team can conduct an informal review. In
later stages these reviews often involve more people and a meeting. The goal
is to keep the author and to improve the quality of the document. The most
important thing to keep in mind about the informal reviews is that they
are not documented.
 Chapter 7
System Implementation & Evolution
 SYSTEM IMPLEMENTATION & UPLOADING
 Computer will be used to maintain the records of the Products, Customer,
Supplier, Order, and Stock in the computer database.

 A Computerized bill in a particular format can be generated.

 Availability of items can be checked.

 Finding Customer, Supplier, Product and Order details is easier.

 The details of the receipt will be recorded in the system

FUTURE ENHANCEMENT
The following are the possible enhancement to the new system,

 The system could be modified suitably to work on a network. This involves, among
other, resolving used conflicts, protecting database integrity and ensuring consistency
of data if it is distributed across multiple locations.

 The system could be modified to add another provision of handling.

  We can add Different module to increase the efficiency of the system.

 Updating of the system is possible.

 New system can also be integrated.

CONCLUSION

 System helps to store all the data about the customer order transaction
in computer and there is no need to do paper work.

 Data is going to be preserved carefully for longer period hence proper

backup is required otherwise there is chance of losing entries or data.

REFERENCES & BIBLIOGRAPHY

During the development of this software I had referred to the following books and reference
material.

 Murach visual basic 2008 – Anne Boehm, Murach

 Mastering visual basic 2008 – Evangelos Petroutsos, Wiley-India Edition

WEBSITES
http://www.google.com

http://www.vb.net information.com