Project Report On

Online Ice-Cream Parlour

Submitted By,

Mr. SIDDHI SUNIL CHAVAN

Year 2017-2018
Under the Guidance of

Prof. Mrs. SNEHAL BORLE

Submitted in Partial Fulfilment of

Requirement For Qualifying

B.Sc.(Information Technology) (Semester-VI)

Examination

University of Mumbai

College:
T.Z.A.S.P.M.’S
PRAGATI COLLEGE OF ARTS & COMMERCE, DOMBIVLI

Page | 1
 .

Sid’s
®
Ice-Cream Parlour

Page | 2
 Certificate
Class : TYBSC(IT) Year : 2017 - 2018

__________ ___________ ___________

Head of the External Internal Examiner

Department Examiner Subject Teacher

Date : / / 2018 Department of

Page | 3
 INDEX

Serial Topic
No.
1. Abstract
2. Introduction
3. Objective And Scope of the Project
4. Theoretical Background
5. Definition of Problem
6. System Analysis and Design
7. System Planning Pert Chart
8. Detailed life cycle
ER Diagram
DFD Diagram
Use case Diagram
9. Output Screen
10. Coding
11. Process involved
12. System Implementation
13. Hardware and Software requirement
14. System Maintenance and Evaluation
15. Cost and Benefits Analysis
16. Methodology used for testing
17. User manual and Security Policy
18. Data Dictionary
19. Conclusion
20. References
21. Acknowledgement

Page | 4
Abstract

Page | 5
 Ice-cream Parlour is a very important feature used in e-commerce to assist
people making purchases online, similar to the US English term „ordering cart‟.
The business-to-consumer aspect of electronic commerce (e-commerce) is the most
visible business use of the World Wide Web. The objective of Online Ice-cream
Parlour is to develop a general purpose e-commerce store where any ice-cream
(such as Chocolate, Vanilla etc.) can be bought from the comfort of home. In order
to facilitate online purchase a orderingcart is provided to the user. Private customer
and business customers can order the selected products of theice-cream Parlour
Service online quickly and comfortably. These include 3-tier architecture, server
and client side scripting techniques, implementation technologies such as
ASP.NET, programming language (such as C#), relational databases (such as SQL
server).

The Ice-CreamParlour is a virtual store on the Internet where customers

can browse the catalogue and select products of interest. The selected items may be
collected in a ordering cart. At checkout time, the items in the ordering cart will be
presented as an order. At that time, more information will be needed to complete
the transaction. Usually, the customer will be asked to fill or select a billing
address, a shipping address, a shipping option, and payment information such as
Cash on Delivery and then bill is displayed to the user.

The objective of Online Ice-CreamParlour is to develop a general purpose

e-commerce store where any ice-cream (such as Chocolate, Vanilla etc.) can be
bought from the comfort of home.It provides the user with a catalogue of different
types of ice-creams available for purchase in the store. In order to facilitate online
purchase a ordering cart is provided to the user. This project has been developed to
allow business grows larger and faster. This site will let customers to view and

Page | 6
order products online from any part of the world. Under this website many
products can be ordered.

Users of the system: Customer is the user of the system. An administrator of the
website is the super user. When the user types in the URL of the website, a
Welcome page is shown which has a menu on the left hand side, a banner at the
top and any related links to other sites. This site contains an ice-cream catalogue
for the user. User has to login to Welcome Page before ordering anything. Login
functionality should check the authenticity of the user from the database.

Functional components of the project: Following is a list of functionality of the

system:

 Registration Screen: If the user is not registered, then registration screen

should be available
 Products Order: This screen will show all the types of different product
with their values and minimum quantity that should be ordered. If possible,
provide the image of each of the product. On selecting any one of the
product, user is shown the columns for the quantity to be entered. After
entering the quantity, price is automatically set by the system based on the
product price data. On adding to catalogue, kindly check the inventory and
take appropriate action.
 Catalogue Information: This screen contains the information about the
orders for the user. It gives total value of the order together with individual
items ordered. On ordering, the validation about user‟s credit is made. Credit
information can be kept in the database for the sake of simplicity. Once the

Page | 7
 order is accepted, inventory is updated and shipment entry is made in the
database. Once the shipment is done, shipment status is updated.
 Contact Information – Contact information regarding the office addresses
with phones and e-mail are provided on this screen
In order to develop an e-commerce website, a number of Technologies must be
studied and understood. These include multi-tiered architecture, server and
client side scripting techniques, implementation technologies such as ASP.NET,
programming language (such as C#), relational databases (such as MySQL,
Access).

Page | 8
Introduction

Page | 9
 E-commerce is fast gaining ground as an accepted and used business
paradigm. More and more business houses are implementing web sites providing
functionality for performing commercial transactions over the web. It is reasonable
to say that the process of ordering on the web is becoming common place. The
objective of this project is to develop a general purpose e-commerce store where
any product (such as Amul, Natural etc.) can be bought from the comfort of home
through the Internet. However, for implementation purposes, this paper will deal
with an online Ice-Cream Parlour.

The Ice-Cream Parlour is a virtual store on the Internet where customers

can browse the catalogue and select products of interest. The selected items may be
collected in a ordering cart. At checkout time, the items in the ordering cart will be
presented as an order. At that time, more information will be needed to complete
the transaction. Usually, the customer will be asked to fill or select a billing
address, a shipping address, a shipping option, and payment information such as
Cash on Delivery and then bill is displayed to the user. The Ice-Cream Parlouris
expanded permanently through new products and services in order to offer a
product portfolio corresponding to the market. Private customer and business
customers can order the selected products of the Ice-Cream Parlour service online
quickly and comfortably.

Target groups of customer of the Ice-Cream Parlour are huge. The customers
can have a payment option through Cash on Delivery only. In order to use the load
writing procedure, the customer registers itself and receives a login for its
purchases name. It is an Internet application. Electronic Commerce (e-commerce)
applications support the interaction between different parties participating in a
commerce transaction via the network, as well as the management of the data
involved in the process.

Page | 10
Purpose of the project

The online Ice-Cream Parlour needs to sell different types of products to

customer living in any part of the world. The website will show all products in
categorized manner. Customer can browse any product for its price and other
details and can order the product. Orders needs to accompany with shipping &
billing details. Customer has to pay order amount. Products can be managed by
operators from admin panel. Operator can be created by admin. Admin can keep
track of orders through admin panel.

The main purpose of the system is to enable customers to browse and order
from any part of the world and hence increasing business scope.

Page | 11
Problem in existing system

 The existing system is manual system. Needs to be converted into automated system.
 Risk of mismanagement of data.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users - Friendly.
 Accuracy not guaranteed.
 Not in reach of distant users.

Solution of these problems

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.

1. User friendliness is provided in the application with various controls.

2. The system makes the overall project management much easier and flexible.
3. There is no risk of data mismanagement at any level while the project
development is under process.
4. It provides high level of security with different level of authentication.
5. Users from any part of the world can make use of the system.
6. New system will be much better in performance as compared to existing one.

Page | 12
Objective &
Scope of the
Project

Page | 13
 Objective
The Online Ice-Cream Parlouris a user-friendly sitewhich has the purpose
of providing the site visitorwith the information ‟What you can get on this site?‟
This site has been purely built for the purpose of knowledge & to provide
convenience for ordering the products just sitting at home. The site provides the
visitor with much information along with images.

The objective of this project is to develop a general purpose e-commerce

store where any product (such as Chocolate,Pista ice-cream, etc.) can be bought
from the comfort of home through the Internet. The site provides the visitor with
proper links, which will make accessing more efficient or rather to making effort
to be more efficient. As its dawn of this new things aren‟t sound & perfect but I
have tried my level best & promise to keep the same in the near future.

I made it easy for the user to access all the information at a click. Along with
this the site provides the user with better acknowledging service. It can be a system
to assist the customer in purchasing a particular handset by the means of
information retrieval. Storing information of members, products, storing latest
information about the products to the members. This project allows administrator
to store and retrieve data with an instant.

Page | 14
 Scope of the Project
The name of the project is online Ice-cream-shop. The software provides the
customer various facilities. Ice-cream-shop automation System automates Ice-
cream making and their selling. In this project we can easily maintain ice-cream
sales details.

It gives complete information‟s of ice-cream, its name, price and category

etc. We can see the ice-cream detail before Purchasing the particular ice-cream
and view for our requirement satisfying item detail.

The Ice-Cream Parlour automation system provides ability to view any ice-
cream of different category available in the shop. Admin can perform Login by
entering Username and Password allotted to him and can view the feedback
submitted by the Users. Here we are trying to develop such type of system which
provides the automation on any type of Ice-Cream Parlour. That means a she
which has the system which provides the facility to the customer of the shop to
purchase the ice-cream from the shop without any difficulty and complexity.

For example any customer wants to purchase any ice-cream from the shop
than first customer has to login in the website and then just choose the category of
the ice-cream than he/she can see the more than one type of ice-cream there and
then he/she can choose the specific ice-cream from there.

Page | 15
The software provides the following facilities to the customers:

 Facilities easy ordering online anywhere.

 Provides information about ice-creams in Categories.
 Can avail the facility of Online purchasing of Ice-Cream.
 Customer are provided with up to date information on the ice-creams
available.

AIM

 The main aim of this project is that the process involved in managing and
selling of the ice-creams can be automated.
 With this it is easy to maintain the records related with the buying of the ice-
creams.
 The records can be updated and have easy and fast access.
 All information can be kept securely and viewed rapidly.
 Generation and authentication procedure is provided for the security
purpose.
 Easy data retrieval due to dynamic search option.

Page | 16
Theoretical
Background

Page | 17
System study

The most important thing is to study a system thoroughly. Here we are studying
both the existing and the proposed system so that the advantages and disadvantages
both understand.
The first task was to identifying how the system is to be computerized. Some
analysis and projection was done regarding changes to be made to the existing
system.
The new developed system “online Ice-Cream Parlour” is simple without any
complexities.

Existing System
This process is done manually. The existing system is time consuming and it is
very costly, because it involves a lot of paperwork. To manually handle such a
system was very difficult task.
But now-a-days because of computerization this job is becoming easier.
The following are the reasons why the existing should be computerized
 To increase efficiency with reduced cost.
 To reduce the burden of paper work.
 To save time of management for recording details of each and every
transaction.
 To check that particular product requested is available.

Page | 18
Limitation of Existing System

 Time Consumption
As the records are to be manually it consumes a lot of time.

 Paper work
Lot of paper work is involved as the records are maintained in the files and
registers.

 Storage requirement
As files and registers are used the storage requirement is increased.

 Less Reliable
Use of paper for storing valuable data is not at all reliable.

 Accuracy
As the system is in manual, there are not many chances of human error.
These cause error in calculating mechanism or maintaining product and
supplier data in register.

 Difficulty in keeping new records

It is difficult for keeping all the new entries of the products, their updates,
reviews, feedback etc.

Page | 19
Proposed system
To reduce the inconvenience that were found in the current system, it has been
automated so as to provide a user friendly GUI that will help data entry.
This also includes Member registration and Comment.
 Creating a database for containing the information present with them on the paper
in the existing system.
 The developed system will be a Time saving application for the user.
 User or visitor can get a broad view about the handset which they requires.

Advantages of Proposed System

Time saving since all the detail information is stored in this system, it enables in
significance reduction in the number of man-hours taken up for the storage and the
retrieval of the information, as it removes the large registers from the scene.
 Accuracy and Reliability
 User-friendly , robust
 Security of data and Integration of all functions in to one system
 Remove redundancy and in-consistency
 Through proper validation, data inconsistency is reduced
 The proposed system would reduce the man-power, because a single trained
person (Administrator) can handle whole database

Page | 20
Definition of
Problem

Page | 21
Purpose of the project

The E-Ice-Cream Parlour needs to sell different types of products to

customer living in any part of the world. The website will show all products in
categorized manner. Customer can browse any product for its price and other
details and can order the product. Orders needs to accompany with shipping &
billing details. Customer has to pay order amount online through credit cards.
Products can be managed by operators from admin panel. Operator can be created
by admin. Admin can keep track of orders through admin panel.

The main purpose of the system is to enable customers to browse and order
from any part of the world and hence increasing business scope.

Problem in existing system

 The existing system is manual system. Needs to be converted into automated

system.
 Risk of mismanagement of data.
 Less security.
 No proper coordination between different applications and users.
 Fewer users - friendly.
 Accuracy not guaranteed..

Solution of these problems

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.

Page | 22
  User friendliness is provided in the application with various controls.
 The system makes the overall project management much easier and
flexible.
 There is no risk of data mismanagement at any level while the project
development is under process.
 It provides high level of security with different level of authentication.
 Users from any part of the world can make use of the system.
 New system will process accurate results.
 New system will be much better in performance as compared to existing
one.

Feasibility Analysis

A feasibility study is undertaken to determine the possibility of either improving

the existing system or developing a complete new system. It helps to obtain an
overview of the problem and to get rough assessment of whether a feasibility
solution exits.

Need For Feasibility Study:

o Answer the question whether a new system is to be installed or not.

o Determine the potential of existing system.
o Improve the existing system.
o Know what should be embedded in the new system.
o Define the problem and objectives involved in the project.
o Avoid costly repairs at larger stage when the system in implemented.

Page | 23
Preliminary investigation examine project feasibility, the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test
the Technical and Operation feasibility for adding new modules and debugging old
running system.

When the developer building any system, he/she make sure that the system he/she
is going to build is feasible. Feasibility study mainly comprises of three kinds of
feasibility.

 Technical Feasibility
 Economical Feasibility
 Operational Feasibility

Technical Feasibility:

Technical Feasibility is concerned with the availability and capability of hardware,

software and people.

Hardware:

A computer should be available that is powerful enough to handle the proposed

system. DBMS systems usually consume more computer power because of its data
structure, security, rule and index pointers to the records. These take more
machines processing time. Now almost any system is technically feasible.

Software:

Page | 24
According to convenience of the system, the system developer should decide
which computer language or software he/she is going to use for the proposed
project. The developer should keep in mind that the software or languages he/she is
going to use should be easily available, efficient and portable and the database
languages which he uses should be preferably Relational Database Language
(RDBMS).

People:

The developers of the system should be ready to learn a new set of skill if
necessary. It will be beneficial if he is thorough with the Operating System and
Software Development Life Cycle.

Economical Feasibility:

Higher level of automation most often requires more funds. Hence based on the
hardware and software specification a desirable alternative costs and benefits to see
if the investment made in creating / developing a new system is costlier or more
beneficial.

A system can be developed technically and that will be used if installed must still
be a good investment for the organization. In the economical feasibility, the
development cost in creating the system is evaluated against the ultimate benefit
derived from the new systems. Financial benefits must equal or exceed the costs.

Page | 25
Usefulness of the project is to be based on the cost benefit analysis from this
perspective a project that costs greater than the benefits is only in feasible in the
sense that it is not profitable to undertaken such project.

First, the cost and benefit ratio should be estimated and then the project should be
undertaken. The present software developed to be economical beneficial.

Operational Feasibility:

The operational feasibility is obtained by consulting the system user whether it

satisfies the user‟s requirements. A system with an easy interface will always help
the user to use the system.

As the system provides a user friendly simple GUI it is operationally feasible to

implement it in the Corporate. This automation will save time as well as reduce
errors.

The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.

A system is technically feasible and is implemental. Management has actively

supported us to implement the system.

Page | 26
Systems Analysis
and Design

Page | 27
 System Development Life Cycles (SDLC) describes the data design and
applications design. SDLS is an interactive rather than a sequential process. Thus
SDLS might help to refine Feasibility study to the user requirements.

Planning

Analysis

Detailed Systems Design

Implementation

Maintenance

Fig. System Development Life Cycles (SDLC)

Page | 28
Planning:

SDLS planning yields a general overview of the company and its objectives. An initial
assessment of the information of the flow and intents requirement must be made during
this discovery portions of SDLS.

Analysis:

Problems defined during the planning phase are examined in great details during analysis
phase. Analysis phase of the SDLS is an effect, a though AUDIT of the users
requirements.

Detailed system Design:

In this phase, the designer complete the design of the systems processes. This include all
the necessary technical specification for the screens and reports.

Implementations:

In this phase hardware, DBMS software and the applications programs are installed and
the database designs is being implementations .

Maintenance:

As soon as the system is operable, end users being to request in it. Those changes
generates systems maintenance activities, which can be grouped into three type:

 Adoptive maintenance due to changes in business environment

 Correctives maintenance in response to systems.
 Perfective maintenance to enhance the system.

Page | 29
System Design

Software design sits at the technical kernel of the software engineering

process and is applied regardless of the development paradigm and area of
application. Design is the first step in the development phase for any engineered
product or system. The designer‟s goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been
specified and analyzed, system design is the first of the three technical activities -
design, code and test that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the
place where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way that
we can accurately translate a customer‟s view into a finished software product or
system. Software design serves as a foundation for all the software engineering
steps that follow. Without a strong design we risk building an unstable system –
one that will be difficult to test, one whose quality cannot be assessed until the last
stage.

During design, progressive refinement of data structure, program structure,

and procedural details are developed reviewed and documented. System design can
be viewed from either technical or project management perspective. From the
technical point of view, design is comprised of four activities – architectural
design, data structure design, interface design and procedural design.

Page | 30
System Planning
PERT Chart

Page | 31
 A PERT chart is a project management tool used to schedule, organize and
co-ordinate tasks within a project.
PERT stands for Program Evaluation Review Technique.

 A PERT chart presents a graphic illustration of a project as a network

diagram consisting of numbered nodes(either circles or rectangles)
representing events or milestones in the project linked by labeled vectors
(directional lines) representing tasks in the project.

 The direction of the arrows on the lines includes the sequence of the tasks. In
the diagram, the tasks which must be completed in sequence are called
Dependent or Serial tasks.

 Tasks that must be completed in sequence but that don‟t require resource or
completion time are considered to have event dependency.
These are represented by dotted lines with arrows and are called dummy
activities.

 Number on the opposite sides of the vectors indicates the time allocated for
the task.

Page | 32
 Task Start Finish Duration

Analysis and
11/01/2018 17/01/2018 6 days
requirements

Designing Tables 18/01/2018 22/01/2018 4 days

Designing Forms 23/01/2018 31/01/2018 8 days

System Coding 31/01/2018 16/02/2018 16 days

Initial Testing 26/02/2018 04/03/2018 6days

Initial
05/03/2018 13/03/2018 8 days
Implementation

Final Testing 13/03/2018 18/03/2018 5 days

Final
18/03/2018 22/03/2018 4days
Implementation

Page | 33
Pert Chart

Analysis & System Designing Tables

Requirements
Start Date: End Date: Start Date: End Date:

11/01/2018 17/01/2018 18/01/2018 22/01/2018

System Coding Designing Forms

Start Date: End Date: Start Date: End Date:
31/01/2018 16/02/2018 23/01/2018 31/01/2018

Initial Testing Initial Implementation

Start Date: End Date: Start Date: End Date:
26/02/2018 04/03/2018 05/03/2018 13/03/2018

Final Implementation Final Testing

Start Date: End Date: Start Date: End Date:
18/03/2018 22/03/2018 13/03/2018 18/03/2018

Page | 34
Gantt Chart

Page | 35
 Gantt Chart
Gantt chart are useful in planning, how long project should take and helping to
sequence the events by laying them but in order in which the tasks needs to be
completed.

Typically tasks are shown in vertical axis and the project time span represented on
the horizontal axis. Each task has a corresponding bar that shows the time span
required for that basic task. The bar can be filled into show the time span required
for that task.

Page | 36
E-R Diagram

Page | 37
Symbols used in this E-R Diagram:

Entity: Entity is a “thing” in the real world with an independent existence. An

entity may be an object with a physical existence such as person, car or employee.
Entity symbol is as follows

Attribute: Attribute is a particular property that describes the entity. Attribute

symbol is

Relationship: Relationship will be several implicit relationships among various

entity types whenever an attribute of one entity refers to another entity type some
relationship exits. Relationship symbol is:

Page | 38
 Key attributes: An entity type usually has an attribute whose values are distinct
for each individual entity in the collection. Such an attribute is called key attribute.
Key attribute symbol is as follows

Table

Field

Relationship

Primary Key

Link

Page | 39
 Online Ice
Cream
Parlour

Manages Visits

Customer
Admin

Makes

Add to
Add Payment

Modifies Is for

Has Cart
Product

Has Category

Page | 40
Data Flow
Diagram

Page | 41
 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. 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 top-
level diagram is often called context diagram. 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.

Larry Constantine first developed the DFD as a way of expressing system

requirements in a graphical from, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying

system requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design to the lowest
level of detail. A DFD consists of a series of bubbles joined by data flows in the
system.

Page | 42
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

CONSTRUCTING A DFD:

Several rules of thumb are used in drawing DFD‟S:

1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. When a process is exploded into lower level details, they are
numbered.
3. The names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized
A DFD typically shows the minimum contents of data store. Each data store
should contain all the data elements that flow in and out.

Page | 43
SAILENT FEATURES OF DFD’S

1. The DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the
dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

Page | 44
Symbol Meaning Example

An entity.

A source of data
or a destination
for data.

A process or
task that is
performed by the
system.

A data store, a
place where data
is held between
processes.

A data flow.

Page | 45
Context Level(0th Level)Diagram:

Login:

Admin Details Data Flow:

Page | 46
1ST Level DFD Diagram:

2nd Level DFD For Manage Product:

Page | 47
2nd Level DFD For Manage Orders:

User Activities DFD:

Page | 48
DFD for new user registration:

Page | 49
Use Case
Diagram

Page | 50
USE CASE DESING:

Page | 51
Page | 52
CLASS DIAGRAM:

Page | 53
Activity
Diagram

Page | 54
Activity diagram are graphical representation of workflow of stepwise activities
and action with support for choice , iterations and concurrency. In the Unified
Modified Language(UML), activity diagram are intended to model both
computational and organizational processes(i.e workflow). Activity diagram show
the overall flow of control.

Activity diagram are constructed from a limited number of shapes, connected with
arrows. The most important shapes types:

 Rounded rectangle represent Action

 Diamonds represent Decisions
 Bar represent the start(spilt) or end(join) of concurrent activities
 Black circle represent the start(initial state) of the workflow
 Encircled black circle represent the end(final state)

Page | 55
Activity Diagram:

Login Activity:

Page | 56
Registration Activity Diagram:

Page | 57
Admin Activity Diagram:

Page | 58
User Activity Diagram:

Page | 59
Output Screen

Page | 60
Login.aspx

Amul.aspx

Page | 61
Chocolate.aspx

Mycart.aspx

Page | 62
 Bill.aspx

Payment.aspx

Page | 63
 Payok.aspx

Addminaddproduct.aspx

Page | 64
 Adminviewuser.aspx

Adminorderdetails.aspx

Page | 65
Aboutus.aspx

Contactus.aspx

Page | 66
Coding

Page | 67
 Login.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;

public partial class login : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void Login_btn_Click(object sender, EventArgs e)
{
SqlConnection cn = new
SqlConnection(ConfigurationManager.ConnectionStrings["apparelsConnectionStri
ng"].ToString());
cn.Open();

SqlCommand cmd = new SqlCommand("select custid,custnme,pass FROM

CustDetails WHERE username='" + Login_username_txt.Text + "' and pass='" +
Login_password_txt.Text + "'", cn);
cmd.Connection = cn;

SqlDataReader dr = cmd.ExecuteReader();
if (dr.HasRows)
{
dr.Read();
Session["cid"] = Convert.ToInt32(dr.GetValue(0));
Session["custname"] = dr.GetValue(1).ToString();
Response.Redirect("Default.aspx");
//temp = 1;

Page | 68
 }
else
{
Login_error_lbl.Text = "Invalid username or password";
//this.Login_error_lbl.ForeColor
}
dr.Dispose();
cn.Close();
cmd.Dispose();
if (Login_username_txt.Text == "Admin" && Login_password_txt.Text ==
"admin")
{
Response.Redirect("AdminHome.aspx");
}

}
}

Page | 69
 mycart.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Data;
using System.Collections.Specialized;

publicpartialclassmycart : System.Web.UI.Page
{
protectedvoid Page_Load(object sender, EventArgs e)
{
con.Open();
String pid = Request.QueryString["prdid"];
if (Session["cid"] == null)
{
Response.Redirect("~/login.aspx");
}
String cid=Session["cid"].ToString();
SqlCommand cmd2 = newSqlCommand("select custid from CartDetails where
productid='"+pid+"'and custid='"+cid+"' ", con);
SqlDataReader dr = cmd2.ExecuteReader();
dr.Read();

dr.Close();
}

SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["onlineicecreamCon
nectionString"].ToString());

publicstaticIOrderedDictionary GetValues(GridViewRow row)

{

Page | 70
IOrderedDictionary values = newOrderedDictionary();
foreach (DataControlFieldCell cell in row.Cells)
{
if (cell.Visible)
{
cell.ContainingField.ExtractValuesFromCell(values, cell, row.RowState,
true);

}
}
return values;
}

protectedvoid btn_update_Click1(object sender, EventArgs e)

{
String pid = Request.QueryString["prdid"];
for (int i = 0; i < GV_My_Cart.Rows.Count; i++)
{
IOrderedDictionary rowValues = newOrderedDictionary();
rowValues = GetValues(GV_My_Cart.Rows[i]);
String ProductId = Convert.ToString(rowValues[1]);
TextBox t1 = newTextBox();
t1 = (TextBox)GV_My_Cart.Rows[i].FindControl("txt_Quantity");
String PurchaseQuantity = t1.Text;
CheckBox chb_Remove = newCheckBox();
chb_Remove =
(CheckBox)GV_My_Cart.Rows[i].FindControl("chb_Remove");
if (con.State == ConnectionState.Closed)
con.Open();
if (chb_Remove.Checked)
{
SqlCommand cmd = newSqlCommand("Delete from CartDetails where custid='" +
Session["cid"] + "' AND productid='" + ProductId + "'", con);
cmd.ExecuteNonQuery();
}

else
{

Page | 71
SqlCommand cmd = newSqlCommand("Update CartDetails SET quanordered='" +
PurchaseQuantity + "' WHERE custid='" + Session["cid"] + "' AND productid='" +
ProductId + "' and cartstatus='In Process'", con);
cmd.ExecuteNonQuery();
}
}
GV_My_Cart.DataBind();
GridView1.DataBind();
}

protectedvoid btn_placeorder_Click(object sender, EventArgs e)

{
con.Close();
con.Open()
SqlCommand cmd3 = newSqlCommand("select max(orderid) from OrderMaster",
con);
SqlDataReader dr1 = cmd3.ExecuteReader();
dr1.Read();
int oid1 =Convert.ToInt16(dr1.GetValue(0).ToString());
int oid = oid1 + 1;
DateTime tdate = DateTime.Now.Date;
DateTime ddate = DateTime.Now.AddDays(5);
con.Close();
con.Open();
SqlCommand cmd4 = newSqlCommand("select sum(rate) from CartDetails where
custid='"+Session["cid"]+"'", con);
SqlDataReader dr2= cmd4.ExecuteReader();
dr2.Read();
String tamount = dr2.GetValue(0).ToString();
con.Close();
con.Open();
SqlCommand cmd5 = newSqlCommand("insert into OrderMaster values('" + oid +
"','" + Session["cid"] + "','" + tdate + "','" + tamount + "')", con);
cmd5.ExecuteNonQuery();

Response.Redirect("~/bill.aspx?oid="+oid+"&tamount="+tamount+"");
}
Page | 72
protectedvoid btn_continue_Click(object sender, EventArgs e)
{
Response.Redirect("Default.aspx");
}
}

Page | 73
 register.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;

publicpartialclassregister : System.Web.UI.Page
{
SqlConnection cn =
newSqlConnection(ConfigurationManager.ConnectionStrings["onlineicecreamCon
nectionString"].ToString());
SqlCommand cmd;
string id;
int Count;
protectedvoid Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
autogenerateid();
}
}
publicvoid autogenerateid()
{
cn.Open();
id = "Select Count(*) from CustDetails";
cmd = newSqlCommand(id, cn);
Count = Convert.ToInt16(cmd.ExecuteScalar()) + 1;
txtcid.Text = Count.ToString();
txtcid.Enabled = false;
cn.Close();
}
protectedvoid Unnamed1_Click(object sender, EventArgs e)
{
cn.Open();

Page | 74
 cmd = newSqlCommand("insert into CustDetails values('" +
txtcid.Text.ToString() + "','" + txtnme.Text + "','" + txtgen.Text + "','" +
txtadd.Text + "','" + txtcon.Text + "','" + txtst.Text + "','" + txtcit.Text + "','" +
txtpin.Text.ToString() + "','" + txtcnct.Text.ToString() + "','" + txtusr.Text + "','" +
txtpass.Text + "','" + txtcpass.Text + "','" + txtmail.Text + "')", cn);
cmd.ExecuteNonQuery();
cn.Close();
Response.Redirect("~/Login.aspx");
}
}

Page | 75
 Bill.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

publicpartialclassbill : System.Web.UI.Page
{
protectedvoid Page_Load(object sender, EventArgs e)
{
String oid = Request.QueryString["oid"].ToString();
String tamt = Request.QueryString["tamount"].ToString();
txtid.Text = oid;
txtcid.Text = Session["cid"].ToString();
txtamount.Text = tamt;
}
protectedvoid btnsubmit_Click(object sender, EventArgs e)
{
string card_type, bank_name;
if (cc.Checked == true)
{
card_type = "Credit Card";
bank_name = RadioButtonList1.SelectedItem.ToString();
}
else
{
card_type = "Debit Card";
bank_name = RadioButtonList2.SelectedItem.ToString();
}
Response.Redirect("~/Payment.aspx?bid=" + txtid.Text + "&cid=" +
txtcid.Text +"&amount=" + txtamount.Text +"&qs_card_type=" + card_type
+"&qs_bank_name="+bank_name+"");
}
protectedvoid cc_CheckedChanged(object sender, EventArgs e)
{
creditcard.Visible = true;

Page | 76
 PlaceHolder1.Visible = false;
}
protectedvoid dc_CheckedChanged(object sender, EventArgs e)
{
creditcard.Visible = false;
PlaceHolder1.Visible = true;
}
}

cmd.Parameters.AddWithValue("User_Name",DropDownList1.SelectedValue);
cmd.Parameters.AddWithValue("Comment",Comment_txt.Text);

if (cn.State == ConnectionState.Open)
{
cn.Close();
}
cn.Open();
cmd.ExecuteNonQuery();
cmd.Dispose();
cn.Close();
Response.Redirect("Feedback.aspx");
}
}

Page | 77
 Feedback.aspx.cs:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;

publicpartialclassfeedback : System.Web.UI.Page
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["onlineicecreamCon
nectionString"].ToString());
SqlDataReader dr;

String Feedback_Name, Feedback_Email_id, Feedback_Comment,

Feedback_Date;
protectedvoid Page_Load(object sender, EventArgs e)
{

}
protectedvoid Feedback_submit_btn_Click(object sender, EventArgs e)
{
SqlCommand cmd = newSqlCommand("insert into Feedback
values(@Feedback_Name, @Feedback_Email_id, @Feedback_Comment,
@Feedback_Date)");
cmd.Connection = con;
cmd.Parameters.AddWithValue("Feedback_Name",
Feedback_name_txt.Text);
cmd.Parameters.AddWithValue("Feedback_Email_id",
Feedback_email_txt.Text);
cmd.Parameters.AddWithValue("Feedback_Comment",
Feedback_comment_txt.Text);

Page | 78
 cmd.Parameters.AddWithValue("Feedback_Date", Feedback_date_txt.Text);

con.Open();
cmd.ExecuteNonQuery();
cmd.Dispose();
con.Close();

Feedback_name_txt.Text = "";
Feedback_email_txt.Text = "";
Feedback_comment_txt.Text = "";
Feedback_date_txt.Text = "";

Response.Redirect("login.aspx");

}
}

Page | 79
 Adminorderdetails.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Data;

publicpartialclassadminorderdetails : System.Web.UI.Page
{
protectedvoid Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{

SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["onlineicecreamCon
nectionString"].ToString());
SqlCommand cmd;
string strQuery = @"SELECT
CustDetails.custnme as name,
CustDetails.emailid as email,
CustDetails.contact as cntct,
'~/product_image/'+image as image,
ProductDetails.productid as pid,
quanordered qorder,
rate as ratee,
cartstatus as cstatus
FROM
dbo.CartDetails
INNER JOIN ProductDetails ON CartDetails.productid =
ProductDetails.productid

Page | 80
 INNER JOIN CustDetails ON CartDetails.[custid] =
CustDetails.[custid]";

cmd = newSqlCommand(strQuery, con);

SqlDataAdapter da = newSqlDataAdapter(cmd);
DataSet ds = newDataSet();
da.Fill(ds);
if (ds.Tables == null&& ds.Tables.Count == 0)
{
return;
}
if (ds.Tables[0].Rows == null&& ds.Tables[0].Rows.Count == 0)
{
return;
}

GV_My_Cart.DataSource = ds;
GV_My_Cart.DataMember = ds.Tables[0].TableName;
GV_My_Cart.DataBind();
}

}
}

Page | 81
 Amul.aspx.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Data;

public partial class women_women : System.Web.UI.Page

{
SqlConnection cn = new
SqlConnection(ConfigurationManager.ConnectionStrings["appare
lsConnectionString"].ToString());
protected void Page_Load(object sender, EventArgs e)
{
if (Session["cid"] != null)
{
Hyperlogin.NavigateUrl = "~/logout.aspx";
Hyperlogin.Text = "logout";
SqlCommand cmd_retrive = new SqlCommand("SELECT
count(*) from CartDetails WHERE custid='" +
Session["cid"].ToString() + "' and cartstatus='In Process'",
cn);
SqlDataReader dr;
if (cn.State == ConnectionState.Open)
{
cn.Close();
}
cn.Open();
dr = cmd_retrive.ExecuteReader();
if (dr.HasRows)
{
dr.Read();

Page | 82
 lbl_cart_items.Text = "(" +
dr.GetValue(0).ToString() + ")";
dr.Dispose();
cmd_retrive.Dispose();
cn.Close();
dr.Dispose();
}
}
}
protected void LV_Products_SelectedIndexChanged(object
sender, EventArgs e)
{

}
}

Page | 83
 Chocolate.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;
using System.Configuration;
public partial class women_jacketsncoatsbm : System.Web.UI.Page
{
SqlConnection cn = new
SqlConnection(ConfigurationManager.ConnectionStrings["apparelsConnectionStri
ng"].ToString());
protected void Page_Load(object sender, EventArgs e)
{
if (Session["cid"] != null)
{
Hyperlogin.NavigateUrl = "~/logout.aspx";
Hyperlogin.Text = "logout";
SqlCommand cmd_retrive = new SqlCommand("SELECT count(*) from
CartDetails WHERE custid='" + Session["cid"].ToString() + "'", cn);
SqlDataReader dr;
if (cn.State == ConnectionState.Open)
{
cn.Close();
}
cn.Open();
dr = cmd_retrive.ExecuteReader();
if (dr.HasRows)
{
dr.Read();
lbl_cart_items.Text = "(" + dr.GetValue(0).ToString() + ")";
dr.Dispose();
cmd_retrive.Dispose();
cn.Close();
dr.Dispose();

Page | 84
 }
}
}
}

Page | 85
 Payok.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;

public partial class PayOk : System.Web.UI.Page

{
SqlConnection cn = new
SqlConnection(ConfigurationManager.ConnectionStrings["apparelsConnectionStri
ng"].ToString());
protected void Page_Load(object sender, EventArgs e)
{
String cartstatus = "paid";
cn.Close();
cn.Open();
SqlCommand cmd = new SqlCommand("update CartDetails set
cartstatus='"+cartstatus+"' where cartid='"+Session["cartid"]+"'and
custid='"+Session["cid"]+"'", cn);
cmd.ExecuteNonQuery();
cn.Close();

}
}

Page | 86
 Payment.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Net.Mail;

public partial class Payment : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
string var_card_type, var_bank_name;
lblamount.Text = Request.QueryString["tamount"];
String amount = Request.QueryString["amount"];
String bid = Request.QueryString["bid"];
String cid = Request.QueryString["cid"];
// String radio = Request.QueryString[3];
lblamount.Text = Request.QueryString["amount"];

// msg.Text = radio;
if (!IsPostBack)
{
var_card_type = Request.QueryString["qs_card_type"].ToString();
var_bank_name = Request.QueryString["qs_bank_name"].ToString();

if (Request.QueryString["qs_bank_name"] == "AmericanExpress")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{4}";
}
if (Request.QueryString["qs_bank_name"] == "Master")
{

Page | 87
 REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{4}";
}
if (Request.QueryString["qs_bank_name"] == "Visa")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{4}";
}
if (Request.QueryString["qs_bank_name"] == "Union bank Of India")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{3}";
}
if (Request.QueryString["qs_bank_name"] == "Yes Bank")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{3}";
}
if (Request.QueryString["qs_bank_name"] == "Union bank Of India")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{3}";
}
if (Request.QueryString["qs_bank_name"] == "State Bank Of India")
{
REV_For_All.ValidationExpression = @"\d{4}\-\d{4}\-\d{4}\-\d{4}";
REV_cre.ValidationExpression = @"\d{3}";
}
}
}
protected void btnpayment_Click(object sender, EventArgs e)
{

try
{
DataSet ds = new DataSet();
DataSet ds1 = new DataSet();
SqlConnection cn = new SqlConnection("Data Source=.;Initial
Catalog=apparels;User ID=sa;Password=abcd1234");
cn.Open();
Page | 88
 SqlCommand cmd1 = new SqlCommand("SELECT emailid from
CustDetails WHERE custid ='" + Session["cid"] + "'", cn);
SqlDataAdapter da1= new SqlDataAdapter(cmd1 );
da1.Fill(ds1);
SqlCommand cmd = new SqlCommand("SELECT totalamt FROM
OrderMaster Where custid = '" + Session["cid"] + "'", cn);
SqlDataAdapter da = new SqlDataAdapter(cmd);
da.Fill(ds);
cn.Close();
if (ds1.Tables[0].Rows.Count > 0)
{
MailMessage Msg = new MailMessage();
// Sender e-mail address.
Msg.From = new MailAddress("saideepcomplex@gmail.com");
// Recipient e-mail address.
Msg.To.Add(Convert.ToString(ds1.Tables[0].Rows[0]["emailid"]));
Msg.Subject = "Your Bill Details";
Msg.Body = "Hi, <br/>Your order has been placed
successfully!!!!<br/><br/>Your Bill Amount is : "+
Convert.ToString(ds.Tables[0].Rows[0]["totalamt"]) + "<br/><br/>";
Msg.IsBodyHtml = true;
// your remote SMTP server IP.
SmtpClient smtp = new SmtpClient();
smtp.Host = "smtp.gmail.com";
smtp.Port = 587;
smtp.Credentials = new
System.Net.NetworkCredential("saideepcomplex@gmail.com", "saideep2015");
smtp.EnableSsl = true;
smtp.Send(Msg);
//Msg = null;

lblMessage.Text = "Your bill Details Sent to your Registered mail";

// Clear the textbox valuess

}
else
{

Page | 89
 }
catch (Exception ex)
{
Console.WriteLine("{0} Exception caught.", ex);
}
Response.Redirect("~/PayOk.aspx");
}
protected void btncancel_Click(object sender, EventArgs e)
{
Response.Redirect("~/paycancel.aspx");
}
}

Page | 90
 Adminaddproduct.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Configuration;
using System.Data;

public partial class adminaddproduct : System.Web.UI.Page

{
SqlConnection cn = new
SqlConnection(ConfigurationManager.ConnectionStrings["apparelsConnectionStri
ng"].ToString());
protected void Page_Load(object sender, EventArgs e)
{

protected void btnUpload_Click(object sender, EventArgs e)

{
if (FileUpload1.HasFile)
{
FileUpload1.SaveAs(Server.MapPath("~/ProjectImage/") +
FileUpload1.FileName);
imgViewFile.ImageUrl = "~/ProjectImage/" + FileUpload1.FileName;
txt_image.Text = FileUpload1.FileName;
}
}
protected void btnsaveProduct_Click(object sender, EventArgs e)
{
SqlCommand cmd = new SqlCommand("insert into ProductDetails
values(@productid, @productnme, @price, @typeid, @image, @brandid,
@catid)", cn);
cmd.Connection = cn;
cmd.Parameters.AddWithValue("productid", txt_product_id.Text);

Page | 91
 cmd.Parameters.AddWithValue("productnme", txt_product_name.Text);
cmd.Parameters.AddWithValue("price", txt_product_price.Text);
cmd.Parameters.AddWithValue("typeid", dropdown_type.SelectedValue);
cmd.Parameters.AddWithValue("image", txt_image.Text);
cmd.Parameters.AddWithValue("brandid", dropdown_brand.SelectedValue);
cmd.Parameters.AddWithValue("catid", dropdown_category.SelectedValue);

lblAddingNewItem.Text = "ITEM ADDED";

if (cn.State == ConnectionState.Open)
{
cn.Close();
}
cn.Open();
cmd.ExecuteNonQuery();
cmd.Dispose();
cn.Close();

txt_product_name.Text = "";
txt_product_price.Text = "";
}
}

Page | 92
 Adminviewuser.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class adminviewuser : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void DetailsView1_ItemUpdated(object sender,
DetailsViewUpdatedEventArgs e)
{
this.GridView1.DataBind();
}
protected void GridView1_SelectedIndexChanged(object sender, EventArgs e)
{

}
}

Page | 93
 Aboutus.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class aboutus : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{

}
}

Page | 94
 Contactus.aspx.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;

public partial class contactus : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{

}
}

Page | 95
 Process
Involved

Page | 96
Analysis Model

Software Development Life Cycle or SDLC is a model of a detailed plan on

how to create, develop, implement and eventually fold the software. It‟s a complete
plan outlining how the software will be born, raised and eventually be retired from
its function.

Page | 97
Waterfall Model

This is also known as Classic Life Cycle Model (or) Linear Sequential Model (or)
System Development Life Cycle Model. This model has the following activities.

1. System/Information Engineering and Modeling

As software is always of a large system (or business), work begins by establishing

the requirements for all system elements and then allocating some subset of these
requirements to software. This system view is essential when the software must
interface with other elements such as hardware, people and other resources. System
is the basic and very critical requirement for the existence of software in any entity.
So if the system is not in place, the system should be engineered and put in place.
In some cases, to extract the maximum output, the system should be re-engineered
and spruced up. Once the ideal system is engineered or tuned, the development
team studies the software requirement for the system.

2. Software Requirement Analysis

The requirements gathering process is intensified and focused specifically on

software. To understand the nature of the program to build, the software engineer
must understand the information domain for the software as well as required
function, behavior, performance, and interface. Requirement for both the system
and the software are documented and reviewed with the customer.

Page | 98
 3. System Analysis and Design

In this phase, the software development process, the software's overall structure
and its nuances are defined. A software development model is thus created.
Analysis and Design are very crucial in the whole development cycle. Much care is
taken during this phase. The logical system of the product is developed in this
phase.

4. Code Generation

The design must be translated into a machine-readable form. The code generation
step performs this task. If designed is performed in a detailed manner, code
generation can be accomplished mechanistically.

5. Testing

Once code has been generated, program testing begins. The testing process focuses
on the logical internals of the software, ensuring that all statements have been
tested, and on the functional externals; that is, conducting tests to uncover errors
and ensure that defined input will produce actual results that agree with required
results.

6. Maintenance
Page | 99
 The software will definitely undergo change once it is delivered to the
customer. There can be many reasons for this change to occur. Change could
happen because of some unexpected input values into the system. In addition, the
changes in the system could directly affect the software operations. The software
should be developed to accommodate changes that could happen during the post
implementation period.

Page | 100
 WATERFALL MODEL

Requirement

Analysis

Design

Coding

Testing

Maintenance

Page | 101
 System
Implementation

Page | 102
 This is the phase in the software life cycle where the actual software is
implemented. The result of this phase consists of source code, together with
documentation to make the code reliable. Implementation is the action that must
follow any preliminary in order for something to actually happen. It encompasses
all the processes involved in getting new software and hardware operating properly
in its environment, including installation, configuration, running, testing and
making necessary changes.

The word deployment is sometimes used to mean the same thing.

Implementation refers to post sales process of guiding a client from purchase to use
of the software or hardware that was purchased.

This includes Requirement Analysis, Scope Analysis, Customizations,

System Integrations, User Policies, User Training and Delivery. These steps are
often overseen by a Project Management Methodologies set forth in the Project
Management Body of Knowledge. Software Implementations involve several
professionals that are relatively new to the knowledge based economy such as
business Analysts, Technical Analysts, Solution Architect and Project Managers.

Page | 103
There are 6 Stages in Software Implementation:

1) verification and validation

 Purpose:

Verify that a system confirms that to its specification and validate that the
systems is what the customer wanted.

 Activities:
o Inspections and reviews.
o Testing: Unit Testing, Integration Testing, System Testing, Acceptance
Testing, etc.

2) Integration

 Purpose:
Assemble the system from subsystems.

 Approaches
Incremental integration or big-bang?

 Problems:
o Interface mismatches or misunderstanding.
o Resources Conflicts: Memory, Control, Physical
o Communication Problems.
o Integration with COTS.
3) Installation

Page | 104
  Purpose:
System is installed in the environment and made for ready for use.
 Problems
o Unexpected issues such as too little space, power, heat, etc.
o Configuration problems and tuning.
o Training

4) Software Evolution and Maintenance

 Purpose

Change the system while it is first in use to handle changing requirements.

 Covers:
o Trouble fixing (Corrective maintenance).
o Adaptation to new platform/technology(Adaptive Maintenance).
o New requirements (Perfective Maintenance).

 Activities:
o Assess existing software.
o Propose change, Modify System.
5) System De-commissioning

 Purpose:
o Take the system out of use at the end of its life-time.
o Should be carefully planned for large systems.

Page | 105
 Issues:
o Safety or security considerations
o Reuse of software or data.

6) Project Management

 Planning

Approaches, Resources, Schedule, Increments or Deliveries and Budget and

Managing all these.

 Cost Estimation

HW, SW, Organization

Page | 106
Hardware and
Software
Requirement

Page | 107
Hardware:

 Processor: Pentium 1GHz or higher

 RAM : 2GB
 Hard disk space : 2-3 GB

Software:

 Tool: Microsoft Visual Studio 2010

 User Interface :ASP.NET
 Database: SQL server 2008/2012
 Operating System: Windows 2007/2010
 Web browser : Google Chrome

Page | 108
About ASP.NET as front End

.Net-What is it?

• Software platform
• Language neutral
• In other words:
.NET is not a language (Runtime and a library for writing and
executing written programs in any compliant language)

What is .NET?

• .NET is a new framework for developing web-based and windows-

based applications within the Microsoft environment.
• The framework offers a fundamental shift in Microsoft strategy:
It moves application development from client-centric to server-centric.

Page | 109
.NET Framework services

• Common Language Runtime

• Windows Forms
• ASP.NET
-Web Forms
-Web Services
• ADO.NET, evolution of ADO
• Visual Studio .NET

Common Language Runtime (CLR)

• CLR works like a virtual machine in executing all languages.
• All .NET languages must obey the rules and standards imposed by
CLR.
Examples:
- Object declaration, creation and use
- Data types, language libraries
- Error and exception handling
- Interactive Development Environment (IDE)

Page | 110
SQL 2008 as Back-End
SQL server is scalable database system whose primary purpose is
to serve as a back-end database for client program, such as your Web
browser, an accounting program like online Ice-Cream Parlour–anything
that makes use of the data. In the most common usage scenario, a client
program connects to SQL server and requests some information,
whereupon SQL server processes the requests and returns results. The
client must then interpret and display these results- eg. Displaying list of
Users in alphabetical order. SQL server can structured information. Eg.
You can instantly search through millions of records and view the results
of the search in many different formats.

You can combine different data into one set; you can transform
some formats into others; you can set security rules to be enforced by
SQL server; and so on.

Page | 111
FEATURES OF SQL SERVER 2008:

 Information representation

 Unique definition of rows

 Systematic treatment of Null values

 Guaranteed access

 High level Update, Insert, and Delete

 Retrieving information from the database.

 Accepting query language statements.

 Enforcing security specifications.

 Enforcing data integrity specifications

 Enforcing transaction consistency

 Managing data sharing

 Optimizing queries

Page | 112
 System
Maintenance
And Evaluation

Page | 113
 Maintenance is not a part of software development, but is an extremely
important activity in the life of a software product. Maintenance includes all the
activities after installation of the software that is performed to keep the system
operational. Maintenance activities related to fixing of errors modifications that
may occur due to changes in the requirements is called „Adaptive Maintenance‟. It
may happen that the application may fail after development. A software product
wears out due to age. In software, failures occur due to bugs or errors that get
introduced during the design and development process. Software may fail after
operating correctly for some time. It is necessary to check that the vendor‟s
computer system is having the requirements specified that too in full version and
not trial period version. If the requirements are met then check for the bugs and
errors do possible modifications. These bugs should be removed. So as not to
encounter such problems in the future it its necessary to visit the organization
frequently to check whether the system is maintained properly and is error free. In
most software organizations, the budget for software maintenance is much larger
than for software development.

The Maintenance can be classified as Corrective, Adaptive, Perfective and

Prevention.

Page | 114
 Corrective Maintenance:

Corrective Maintenance changes the software to correct defects. Means

repairing, processing or Performance failures or making alteration because of
previously ill-defined problems.

Adaptive Maintenance:

Adaptive maintenance results in modification to the software to accommodate

changes to its external environment.

Perfective or Enhancement Maintenance:

Enhancing the performance or modifying the programs according to the user‟s

additional or changing needs. Perfective maintenance extends the software beyond
its original functional requirements.

Prevention Maintenance:

Computer Software deteriorates due to change, and because of this, preventive

maintenance must be conducted to enable the software to serve the needs of its end
users. In essence, preventive maintenance makes changes to computer programs so
that they can be more easily corrected, adapted and enhanced.

Page | 115
Cost and Benefit
Analysis

Page | 116
Why cost & benefit analysis…??
Why should you do a cost-benefit analysis for your project? IT projects frequently
over promise and under deliver. Executive managers have become aware of this
performance issue and the cost-benefit analysis is their guarantee that the project
team has carefully evaluated the project before commencement, studying the whole
life cycle costs and the expected benefits.

The most common way to carrying out an economic assessment of a proposed

information system, or other development, is by comparing the expected cost of
development and operation of the system with the benefits of having it in place.
Assessment is based upon the question of whether the estimated costs are exceeded
by the estimated income and other benefits. Additionally, it is manually necessary
to ask whether or not the project under consideration is the best of number of
options.

Identifying and estimating all of the costs and benefits of carrying out the project:
This includes development costs of the system, the operating costs and the benefits
that are expected to accrue from the operation of the system. Where the proposed
system is replacing an existing one, these estimates should reflect the cost and
benefits due to the new system. A sales order processing system, for example,
could not claim to benefit an organization by the total value of sales – only by the
increase due to the use of new system.

Expressing these costs and benefits in common units:- We must the net benefit,
which is the difference between the total benefit and total cost. To do this, we must
express each cost and benefit in memory terms,
Page | 117
Most costs are relatively easy to identify and quantify in approximate monetary
terms. It is helpful to categorize costs according to where they originate in the life
of the project.

Setup costs:- Include the costs of putting the system into place. These consist
mainly of the any new hardware and ancillary equipment but will also include cost
of file conversion, recruitment and staff training.

Operational costs: - consists of the costs of operating the system once it has been
installed.

Direct benefits:- these accure directly from the operation of the proposed system.
These could, for example, include the reduction in salary bills though the
introduction of a new, computerized system.

Cost Analysis

The cost can be calculated with respect to amount of hours spent while doing the
project. It is the cost which is calculated with the respect to the amount of work
done by each person on the project and also the number of days taken for
completing each form and each module. It also takes the time required for
designing each form and validating them. Also the time spent in testing each
module with all its forms. The amount of hours spent can be calculated with
respect to the number of forms and modules created during this curses
It also corresponds to the amount of consumption of electricity, printout, telephone
bills travelling expenses, internet, stationary etc.

Page | 118
Cost Estimation
For a given set of requirements it is desirable to know how much it will cost to
develop the software to satisfy a given requirements, and how much time
development will take. The cost of a project is a function of many parameters.
Foremost among them is the size of the project. Other factors that affect the cost
are programmer ability, experience of the developers in the area, complexity of the
project, and reliability requirements. It is also due to the requirements of software,
hardware and human resources.

Cost required for the project is to install Microsoft Visual Studio software. SQL
express comes inbuilt into it.

Benefit analysis

There are many benefits the company will have by using our software
1. System will helping in reducing the file work.
2. System will make the job easier than other system
3. It will save time
4. Job of searching records and its information will be much easier, hence time
for retrieving particular record will be less.
5. Records can be saved which solves the problem of misplacing.

Because lack of accuracy & information in improper format the existing system is
computerized to reduce the manual record keeping work to improve timelessness
during implementation of an organization employee details.

Cost and benefits Analysis is a three step Process-

Page | 119
1st step:

Estimate the anticipate development and operational cost

 Development cost:

Cost occurred during the development of the system.

 Operational Cost:

Cost that will occur after the installing of the system.

2nd step:

Estimate the anticipate financial benefits.

 Financial Benefits:

They are expected annual saving or increase in revenue derived from the
installation of the new system.

3rd step:

The cost and benefit analysis is calculated based on detailed estimate cost and
benefits.

Page | 120
Methodology
Used
For Testing

Page | 121
 Introduction

Testing is the process of running a system with the intention of

finding errors. Testing enhances the integrity of a system by detecting
deviations in design and errors in the system. Testing aims at detecting
error-prone areas. This helps in the prevention of errors in a system.
Testing also adds value to the product by conforming to the user
requirements.

The main purpose of testing is to detect errors and error-prone areas

in a system. Testing must be thorough and well-planned. A partially tested
system is as bad as an untested system. And the price of an untested and
under-tested system is high.

Software Testing is a process of executing the program with objective finding

an error. Software testing is successful only if all error from software are removed.
Good testing techniques are available which find maximum uncovered error but no
techniques is available which will find all error so we have to used set of setting
technique to find errors.

Page | 122
Objectives of Testing:

The objectives of testing are:

 Testing is a process of executing a program with the intent of finding

errors.
 A Successful test case is one that uncovers an as- yet-undiscovered
error.

1) White Box Testing (WBT)

White Box Testing is related with a structure or internal logic. Various

test cases designed which takes care of the following:
i. Every statement in a program must be executed at least once.
ii. Every path in program must be executed at least once which is called
as path analysis.
iii. Every logical decision must be executed on their true or false sides.
iv. Executed all loops their boundaries and within operational boundaries

Static analyzers is one of the tool used for WBT which is used to check
function calls, and initialized variables, variables defines but not used etc.

Advantages of WBT

1) As all statement or logic is verified it is possible to give guarantees of

error free software.
2) WBT is helpful for improving the quality of system in terms if increasing
executions speed by selecting proper logic, minimizing memory space by
removing unnecessary statement etc.

Page | 123
Disadvantages of WBT

1) Only experts persons able to do WBT because understanding of the code

is necessary.
2) Each and every statement and path is checked this requires lot of time for
testing.
3) Cost of testing is high because we have to pay expert persons.

2) Black Box Testing

Black Box Testing is related with input and output only and not
related with internal structure of the program. In BBT it is checked some input is
produce by the program or not various set of input test cases are prepared and
applied on the program and corresponding output is verified. BBT is used to find
the error in data structure, performances errors etc.

Methods for BBT

1. Partioning

In this input domain of the program is divided into different categorized from
which test cases can be derived same as input portioning. Output portioning is
also done for output domain.

2. Error Guessing
Possible error are listed and inputs conditions can based on this are
constructed.

3. Boundary value Analysis

Page | 124
 Test cases should be design in such way that input conditions are either just
above or just below of the actual value.

4. Random Testing
Program is tested by randomly selecting some subset of the possible input
values test data may be chosen randomly or by sampling process.

Page | 125
Advantage of BBT

1) Expert persons are not requiring for testing because internal logic or
statement are not verified
2) Cost of BBT may be less as expert persons are not required.

Disadvantages of BBT

1) It is not possible to give guarantee of error free software because possibility

of the error still remains logic is not checked.
2) Requires large test data even after we have applied large test data we can‟t
says that this is sufficient.

Page | 126
α-β Testing

After software development is complicated is completed during

implementing of the system a proper training is given to the users get early
training before implementing at the developer side. Though proper training
is given to the customer there is the no guarantee that they will handle the
system property. Due to implementing also there are no chances of the
errors in handling the systems. So the methods of α-β testing is applied.

α Testing
A customer conducts this test at the developer side. α test are conducts
in a controls enrollment. Customer operates the software and developer
watches and usages problems.

β testing
This test is conducted at one or more customers sides by the end user of
the software.
During this, developer is not presents so user fields free in handling the
system and records all the systems these problems are then reported to the
developer. Developers solve the problems and makes necessary changes in
software and then modified software is given to all customers.

Page | 127
 User Manual
and
Security Policy

Page | 128
 User manual and Security policy

The website has various users and hence the website is divided
based on the login provided by the user. The access is different for
different users based on their login type. The two types of users
are Customer and Admin.
This is a user manual to describe how website works:
 When customer enters into the website:
When the customer wants to Order any ice-cream, first the needs to
do is login into the website. If the customer does not have the
account then he needs to register himself to the website. Then
he/she can select required category and select specific Ice-Cream
and then add it to cart. After that he/she need to pay the amount
with regards to the ordering done.
The customer can also provide feedback and suggestion. He/she
can also update his/her account and also their password by clicking
the respective links.

 When Admin enters into website:

Administrator has full access to the website. He can Add new ice-
cream, update ice-cream details, update the existing information,
view user details, view feedback and also view order given by the
customers and many more.

Page | 129
 Data
Dictionary

Page | 130
Brand Table

Description: This table gives the detail information of the

brands of the product .
Fields Datatype Constraint

Brandid nvarchar(50) Primary key

Brandnme nvarchar(50)

Cart Detail Table

Description : This is Table gives the detail information of the cart

detail.

Fields Datatype Constraint

Productid nvarchar(50) Primary key

Typeid nvarchar(50)

Quanordered int

Rate int

Cartid int

Custid nvarchar(50)

Cartstatus varchar(50)

Page | 131
 Category_Detail

Description : This is Category table for storing category detail.

Fields Datatype Constraint

Catid nvarchar(50) Primary key

Catnme nvarchar(50)

Customer Detail Table

Description : This is customer table for storing Customer details.

Fields Datatype Constraint

Custid Int Primary key

Custnme nvarchar(50)

Gender nvarchar(50)

Address nvarchar(50)

Country nvarchar(50)

State nvarchar(50)

Pin nvarchar(50)

Contact Nvarchar(50)

Username Nvarchar(50)

Page | 132
 Pass Nvarchar(50)

Confirmpass Nvarchar(50)

Emailed Nvarchar(50)

Order MasterTable
This is order mastertable for storing order details.

Fields Datatype Constraint

Orederid Numeric(18,0)
Custid nvarchar(50)
Orderdte nvarchar(50)
Totalamt nvarchar(50)

ProductDetail Table
This is ProductDetail table for storing Product details.

Fields Datatype Constraint

Productid Nvarchar(50) Primary key

Productnme nvarchar(50)

Price nvarchar(50)

Typeid nvarchar(50)

Page | 133
Image nvarchar(50)

Brandid nvarchar(50)

Catid nvarchar(50)

Typemaster Table
Description: This is type master table for storing the type of the
product information.

Fields Datatype Constraint

Typeid nvarchar(50) Primary Key

Typenme nvarchar(50)

Feedback Details
Description: This is Feedback table for storing customer feedback.

Fields Datatype Constraint

Emailed nvarchar(50) Not null

Feedbackdte nvarchar(50)

Comment nvarchar(50)

Name nvarchar(50)

Page | 134
Conclusion

Page | 135
 This Website project would allow our customers convenient and easy access
to the site. It would save time and placing orders and doing payment becomes more
simpler and it is very efficient. Hence we have designed the project to provide the
user with easy navigation, retrieval of data and necessary feedback as much as
possible.

A good orderingcart design must be accompanied with user-friendly

orderingcart application logic. It should be convenient for the customer to view the
contents of their cart and to be able to remove or add items to their cart. The E-Ice-
Cream Parlourapplication described in this project provides a number of features
that are designed to make the customer more comfortable.

This project helps in understanding the creation of an interactive web page

and the technologies used to implement it. The design of the project which
includes Data Model and Process Model illustrates how the database is built with
different tables, how the data is accessed and processed from the tables

“Online Ice-Cream Parlour” provides knowledge about the latest

technology used in developing web enabled application and client server
technology that will be great demand in future. This will provide better
opportunities and guidance in future in developing projects independently.

Page | 136
 Future
Enhancement

Page | 137
As for other future developments, the following can be done:

 The Administrator of the web site can be given more functionality, like
looking at a specific customer‟s profile, the books that have to be reordered,
etc.
 Multiple Ordering Carts can be allowed.
 A console for the data centre may be made available to allow the personnel
to monitor on the sites which were cleared for hosting during a particular
period.
 Moreover, it is just a beginning; further the system may be utilized in
various other types of auditing operation viz. Network auditing or similar
process/workflow based applications...

Page | 138
References

Page | 139
Textbook reference:

 Software Engineering, Fifth Edition by Roger S. Pressman, Tata McGraw –

Hill Publication
 SQL Complete Reference Second Edition by James R. Groff and Paul
Weinberg Tata McGraw – Hill Publication

Web Reference:

www.google.com

http://msdn.microsoft.com

www.aspnet101.com

Page | 140
 Acknowledgement

With due to regards I express my sincere thanks to Mr. A.P.Mahajan Sir,

(Principal of Pragati College, Dombivali) and the Management for having
facilitated me with the essential infrastructure resources without which this project
would not have seen light of the day.

I am at the outset on the completions of “Online Ice-Cream Parlour” project,

express our deep regard to those who have offered their invaluable guidance in
hour of needs. I would like to thank Prof. Mrs. Snehal Borle who gave me an
opportunity to developed the Software Projects.

My sincere thanks to all teaching and non-teaching staff members of the

Information Technology Department of Pragati College of the Arts and
Commerce for their encouragement and whole hearted support for this projects.

Finally, I express my whole hearted gratitude towards the entire Computer

Department and my Friends, Relatives and people who are directly or indirectly in
the successful with completion of the projects.

Mr. Siddhi Sunil Chavan

15-TYB.Sc.(I.T.)
Pragati College of Arts & Commerce,
Dombivali (E).

Page | 141
Page | 142