A

Mini Project Report

On
E-POST OFFICE
Submitted to Jawaharlal Nehru Technological University for the Partial Fulfillment of the requirement
for the Award of Degree in
BACHELOR OF TECHNOLOGY
In
COMPUTER SCIENCE & ENGINEERING
Submitted by

V. Shiva Sagar Rao (15QK1A0541)

V. Priyatha (15QK1A0528)
B. Sai Tharun (15QK1A0538)
P. Sai Ram (15QK1A0531)

Under the Esteemed Guidance of

Mr. GUIDE NAME
Assistant Professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

JYOTHISHMATHI INSTITUTE OF TECHNOLOGICAL SCIENCES
(Approved by AICTE, New Delhi, Affiliated to JNTU, HYDERABAD)
Ramakrishna Colony, Karimnagar- 505481.
TELANGANA, INDIA
(2018-2019)
 DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
JYOTHISHMATHI INSTITUTE OF TECHNOLOGICAL SCIENCES
(Approved by AICTE, New Delhi, Affiliated to JNTU, HYDERABAD)

Ramakrishna Colony, Karimnagar, Telangana – 505481

CERTIFICATE

This is to certify that the Mini Project Report entitled “E-POST OFFICE” is being
submitted by V. Shiva Sagar Rao (15QK1A0541), V. Priyatha (15QK1A0528), B. Sai
Tharun (15QK1A0538), P. Sai Ram (15QK1A0531) in partial fulfillment of the requirements
for the award of the Degree of Bachelor of Technology in Computer Science & Engineering,
to the JYOTHISHMATHI INSTITUTE OF TECHNOLOGICAL SCIENCES, Karimnagar,
during academic year 2018-2019, is a bonafide work carried out by them under my guidance and
supervision.
The results presented in this Project Work have been verified and are found to be
satisfactory. The results embodied in this Project Work have not been submitted to any other
University for the award of any other degree or diploma.

Project Guide Head of the Department

GUIDE NAME, A. Manjula,
Assistant Professor, Associate Professor,
Dept. of CSE Dept. of CSE
 ACKNOWLEDGEMENT

We would like to express our sincere gratitude to our advisor, GUIDE NAME, Assistant
Professor, CSE Dept., whose knowledge and guidance has motivated us to achieve goals we
never thought possible. The time we have spent working under GUIDE NAME supervision has
truly been a pleasure.

The experience from this kind of work is great and will be useful to us in the future. We
thank Dr.A. Manjula, Associate Professor & HOD, CSE Department, for encouraging us to do
such research work and for providing all the facilities to carry out this project work.

It is a great pleasure to convey our thanks to our principal Dr. P. K. Vaishali, Principal,
JYOTHISHMATHI INSTITUTE OF TECHNOLOGICAL SCIENCES and the College
Management for permitting us to undertake this project and providing excellent facilities to carry
out our project work.

We thank all the Faculty members of the Department of Computer Science &
Engineering for sharing their valuable knowledge with us. We extend our thanks to the
Technical Staff of the department for their valuable suggestion to technical problems.

V. Shiva Sagar Rao (15QK1A0541)

V. Priyatha (15QK1A0528)
B. Sai Tharun (15QK1A0538)
P. Sai Ram (15QK1A0531)
 DECLARATION

We hereby declare that the work which is being presented in this dissertation entitled,
“E-POST OFFICE”, submitted towards the partial fulfillment of the requirements for the award
of the degree of Bachelor of Technology in Computer Science & Engineering,
JYOTHISHMATHI INSTITUTE OF TECHNOLOGICAL SCIENCES, Karimnagar is an
authentic record of our own work carried out under the supervision of GUIDE NAME,
Assistant Professor, Department of CSE, JYOTHISHMATHI INSTITUTE OF
TECHNOLOGICAL SCIENCES, Karimnagar.

To the best of our knowledge and belief, this project bears no resemblance with any
report submitted to JNTUH or any other University for the award of any degree or diploma.

V. Shiva Sagar Rao (15QK1A0541)

V. Priyatha (15QK1A0528)
B. Sai Tharun (15QK1A0538)
P. Sai Ram (15QK1A0531)

Date:

Place:
 ABSTRACT

The e-Post Office is the shopping portal of the world-renowned postal service on the Internet
and an additional distribution channel. It sells Stamps, Postcards, Packets, and Cartons and has
services like courier, registering for electricity vendors, selling mobile cards, etc. Under this
website many products and services can be ordered, that are also available in a "normal" branch.
The product prices are identical with the prices of their normal branches.

The e-Post Office is 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 postal service online quickly and comfortably. Besides
this, the e-Services offer new flexibility through e-Packet, the PICKUP order for packages over
the Internet as well as the online forwarding order and storage order. For the case of the absence
or the move, one can let delegate here the after shipment of the postal service at another address
or store the letter shipments. The customers can register themselves and can be served
individually.

Target groups of a customer of the e-Post Office are predominantly little and middle-class
business. The customers can have a payment alternative through credit card. In order to use the
load writing procedure, the customer registers itself in the e-Post Office and receives a login for
its purchases name. You have to develop this website, which captures the above functionality. It
is an Internet application.

The Post Office needs to sell Stamps, Postcards & Envelopes 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.
 CONTENTS

PAGE No.
List of Figures i
List of Tables iii

CHAPTER 1 – INTRODUCTION

1.1 Motivation 1
1.2 Problem Statement 2
1.3 Existing System 3
1.4 Proposed System 3

CHAPTER 2 - LITERATURE SURVEY & PROBLEM IDENTIFICATION

2.1 Literature Survey 4

2.2 Software And Hardware Requirements
2.2.1 Hardware Requirements 5
2.2.2 Software Requirements 5

CHAPTER 3 – METHODOLOGY & DESIGN ANALYSIS

3.1 3.1 Architecture of Proposed System

6
3.2 System Design
3.2.1 UML Diagrams 8
3.2.2 Dataflow Diagrams 17
3.2.3 Data Dictionary 20
3.2.4 E-R Diagram 25

CHAPTER 4 – IMPLEMENTATION

4.1 Coding/ Code Templates 27

4.2 Testing
4.2.1 Types of Testing 32

CHAPTER 5 – RESULT ANALYSIS

1
2
3
4
5

5.1 Output- Screen Shots 36

CHAPTER 6 – CONCLUSION & FUTURE ENHANCEMENTS 42

BIBLIOGRAPHY / REFERENCES 43
 LIST OF FIGURES

Figure No. Description Page No.

Figure 3.1 Architecture of MVC 6

Figure 3.2 Easy Wear Web Portal 9

Figure 3.3 Category Management 9

Figure 3.4 Customer Management 10

Figure 3.5 Content Management 10

Figure 3.6 Catalog Management 11

Figure 3.7 Searching Categories 12

Figure 3.8 Searching Products List 13

Figure 3.9 User Registration 14

Figure 3.10 Product Purchase Process 15

Figure 3.11 Order Management 16

Figure 3.12 Data Flow 19

Figure3.13 E-R diagram 26

Figure4.1 Strategic Approach To Software Testing 33

Figure5.1 Home Page 36

Figure5.2 Admin 37

Figure5.3 Category 37

Figure5.4 Login 38

Figure5.5 Products 38

i
Figure 5.6 User Registration 39

Figure5.7 Manage Users 39

Figure5.8 Orders 40

Figure 5.9 Epayment 40

Figure 5.10 Feedback 41

Figure 5.11 ContactUs 41

ii
 LIST OF TABLES

Table No. Description Page No.

Table 3.1 tblAddress 20

Table 3.2 tblAdminMenu1 21

Table 3.3 tblAdminMenu2 21

Table 3.4 tblAttributes 22

Table 3.5 tblBrands 22

Table 3.6 tblCategories 23

Table 3.7 tblCity 23

Table 3.8 tblCountry 24

Table 3.9 tblCustomer 24

Table 3.10 tblFeaturedProducts 25

iii
 CHAPTER 1
INTRODUCTION

1.1. MOTIVATION

The e-Post Office is the shopping portal of the world-renowned postal service on the
Internet and an additional distribution channel. It sells Stamps, Postcards, Packets, and
Cartons and has services like courier, registering for electricity vendors, selling mobile
cards, etc. Under this website many products and services can be ordered, that are also
available in a "normal" branch. The product prices are identical with the prices of their
normal branches.

The e-Post Office is 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 postal service online quickly and comfortably. Besides
this, the e-Services offer new flexibility through e-Packet, the PICKUP order for packages over
the Internet as well as the online forwarding order and storage order. For the case of the absence
or the move, one can let delegate here the after shipment of the postal service at another address
or store the letter shipments. The customers can register themselves and can be served
individually.

Target groups of a customer of the e-Post Office are predominantly little and middle-
class business. The customers can have a payment alternative through credit card. In
order to use the load writing procedure, the customer registers itself in the e-Post Office
and receives a login for its purchases name. You have to develop this website, which
captures the above functionality. It is an Internet application.

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

 Registration Screen: If the user is not registered, then the registration screen should be
available
 Stamps and Bulk Stamps Order: This screen will show all the types of Stamps with
their values and minimum quantity that should be ordered. If possible, provide the image

1
 of each of the stamp types. On selecting any one of the Stamp types, the user is shown the
columns for the quantity to be entered. After entering the quantity, the price is
automatically set by the system based on the product price data. On adding to catalog,
kindly check the inventory and take appropriate action.
 Letter Order: This Screen will show different types of letter, which can be ordered,
online. Provide an image for each type of letter. On selecting any one of the Letter types,
the user is shown the columns for the quantity to be entered. After entering the quantity,
the price is automatically set by the system based on the product price data. On adding to
catalog, kindly check the inventory and take appropriate action.
 Catalog Information: This screen contains the information about the orders for the user.
It gives the total value of the order together with individual items ordered. On order, the
validation about user’s credit is made. Credit information can be kept in the database for
the sake of simplicity. Once the order is accepted, inventory is updated and shipment
entry is made in the database. Once the shipment is done, shipment status is updated.
 Terms and Conditions – A Brief text on the website explaining terms and conditions
and a printable copy of it.

 Contact Information – Contact information regarding the office addresses with phones
and faxes are provided on this screen

1.2. PROBLEM STATEMENT

We want our website to be bug-free, reliable and flexible user interaction.

Today many people are facing trouble to obtain various Post Office services like
Courier, Post Cards, Stamps etc because of the formation of long queues and lack of time.
We have too many release failures that result in too many rollback failures. If we
ignore this problem; resources will need to increase to handle the cascading problems,
and we may miss critical customer deadlines which could result in lost revenue, SLA
penalties, lost business, and further damage to our quality reputation. (Issue Statement)
We will use our Kaizen Blitz methodology in evaluating the last release to help us
improve our processes. (Method)

1.3. EXISTING SYSTEM

2
  The existing system is a manual system. Needs to be converted into an 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.

1.4. PROPOSED SYSTEM

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.

 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 a high level of security with different level of authentication.
 Users from any part of the world can make use of the system.
 The new system will process accurate results.
 The new system will be much better in performance as compared to the existing one.

CHAPTER 2
LITERATURE SURVEY& PROBLEM IDENTIFICATION

2.1 LITERATURE SURVEY

3
 1. Customers Attitude towards postal services
AUTHOR: G.Thangapandi
The post office provides numerous services to the public. These services can be
broadly classified into public. The services can be broadly classified into postal and non-
postal services. The postal services include registration of letters and parcels, booking of
value payable letters and parcels, booking of money orders.

2. Relative Prices and electronic substitution

AUTHORS: Seung-Hyun Hong, Frank A Wolak

This paper quantifies the extent to which the shift in the aggregate household demand
for postal delivery services can be attributed to the appearance of alternative modes of
communication versus the concomitant rise in the postal prices. We find that both recent
postal prices. We find that both recent postal price increases and the penetration of
personal computer technology among US households led to similar reductions in postal
expenditure. We further find that a 5% postal price increase, such as the one introduced
in January 2006 reduces revenue collected from US households.

2.2. SOFTWARE AND HARDWARE REQUIREMENTS

2.2.1. Hardware Requirements:

 PIV 2.8 GHz Processor and Above

 RAM 512MB and Above
 HDD 20 GB Hard Disk Space and Above

4
 2.2.2. Software Requirements:

 WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

 Visual Studio .Net 2005 Enterprise Edition
 Internet Information Server 5.0 (IIS)
 Visual Studio .Net Framework (Minimal for Deployment)
 SQL Server 2000 Enterprise Edition

CHAPTER 3
METHODOLOGY & DESIGN ANALYSIS

3.1. ARCHITECTURE OF PROPOSED SYSTEM

MVC Architecture:

Introduction:

5
 Model-view-controller (MVC) is an architectural pattern used in software
engineering. In complex computer applications that present lots of data to the user, one
often wishes to separate data (model) and user interface (view) concerns, so that changes
to the user interface do not impact the data handling, and that the data can be reorganized
without changing the user interface. The model-view-controller solves this problem by
decoupling data access and business logic from data presentation and user interaction, by
introducing an intermediate component: the controller.

Fig. 3.1: Architecture of MVC

It is common to split an application into separate layers: presentation (UI), domain,

and data access. In MVC the presentation layer is further separated into View and
Controller. MVC encompasses more of the architecture of an application than is typical
for a design pattern.

Model :

6
 The domain-specific representation of the information on which the application
operates. It is a common misconception that the model is another name for the domain
layer. Domain logic adds meaning to raw data (e.g., calculating if today is the user's
birthday, or the totals, taxes and shipping charges for shopping cart items).Many
applications use a persistent storage mechanism (such as a database) to store data. MVC
does not specifically mention the data access layer because it is understood to be
underneath or encapsulated by the Model.

View :

Renders the model into a form suitable for interaction, typically a user interfaces
element. MVC is often seen in web applications, where the view is the HTML page and
the code which gathers dynamic data for the page.

Controller :

Processes and response to events, typically user actions, and may invoke changes on
the model. Though MVC comes in different flavours, control flow generally works as
follows:

 The user interacts with the user interface in some way (e.g., the user presses a button)
 A controller handles the input event from the user interface, often via a registered handler
or callback.
 The controller accesses the model, possibly updating it in a way appropriate to the user's
action (e.g., the controller updates user's shopping cart).
 A view uses the model to generate an appropriate user interface (e.g., view produces a
screen listing the shopping cart contents). The view gets its own data from the model.
The model has no direct knowledge of the view. (However, the observer pattern can be
used to allow the model to indirectly notify interested parties – potentially including
views – of a change.)
 The user interface waits for further user interactions, which begins the cycle a new.
Functioning:

7
 In GUIs, views and controllers often work very closely together. For example, a
controller is responsible for updating a particular parameter in the model which is then
displayed by a view. Each controller-view pair is associated with only one model;
however, a particular model can have many view-controller pairs.

Briefly, the model contains a pointer to view the object(s). when a manipulator
method is called for the model, the model automatically broadcasts a “notify” message to
all the associated views. This alerts the views that something has changed in the model
and causes them to re-draw themselves, first obtaining the new data from the model with
an “update” method.

3.3. SYSTEM DESIGN

3.3.1. UML Diagrams

Every complexsystem is best approached through asmall set of nearly independent
views of a model; no single viewer is sufficient. Every model may be expressed at
different levels of fidelity. The best models are connected to reality. The UML defines nine
graphical diagrams.
1. Class diagram
2. Object diagram
3. Use-case diagram
4. Behavior diagram
5. Interaction diagram
6. Sequence diagram
7. Collaboration diagram

8
Use Case Design:

Admin

Fig. 3.2: Easy Wear Web Portal

Category Management

Customer Admin

Fig. 3.3: Category Management

9
 Customer Management

Customer Admin

Fig. 3.4: Customer Management

Content Management

Customer Admin

Fig. 3.5: Content Management

10
 Catalog Management

Manage Country

<<extend>>

ViewCountry AddCountry UpdateCountry

Manage State

<<extend>>

ViewState AddState UpdateState

Manage City

<<extend>>

ViewCity AddCity UpdateCity

Fig. 3.6: Catalog Management

11
 Use Case Sequence Diagrams

CUSTOMER CATEGORY MANAGER CATEGORIES

View Categories Request

Search Categories

Categories List

Result

Fig. 3.7: Searching Categories

12
CUSTOMER PRODUCT MANAGER PRODUCTS

View Products Request

Search Products

Products List

Result

Fig. 3.8: Searching Products List

13
USER CUSTOMER MANAGER CUSTOMERS

Personal, Address & credential details

Register User

Customer Registration Status

Result

Fig. 3.9: User Registration

14
Customer Login Product manager Shopping Cart Orders
Payment Gateway
Products

Click on Login
Button

Click on
Product Link

Search for
Product

Click on Add to
Cart

Click on Billing

Select the Check the

Payment Mode Status of Order

Return to
Customer Home
Page

Fig. 3.10: Product Purchase Process

15
 Login Screen
Admin Order Manager Orders

Login Details

Order Details
Manage Orders

Status

Result

Result

Fig. 3.11: Order Management

16
3.3.2 Data Flow Diagrams

A data flow diagram is a graphical tool used to describe and analyze the movement of
data through a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output, through
processed, may be described logically and independently of physical components
associated with the system. These are known as the logical data flow diagrams. The
physical data flow diagrams show the actual implements and movement of data between
people, departments and workstations. A full description of a system actually consists of
a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson
notation develops the data flow diagrams. Each component in a DFD is labelled with a
descriptive name. The process is further identified with a number that will be used for
identification purpose. The development of DFD’S is done at 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 a context diagram. It consists of a single
process bit, which plays a vital role in studying the current system. The process in the
context level diagram is exploded into another 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 the
further explosion is necessary and an adequate amount of detail is described for the
analyst to understand the process.

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

requirements in a graphical form, 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.

DFD Symbols:

In the DFD, there are four symbols

17
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

The process that transforms data flow.

Source or Destination of data

Data flow

Data Store

18
 1

Brow se
C atalogue Item D etails
*

Product Info

2
Product ID C ustom er
R egister
C ustom er
Profile
D etails
Public *
Product Q ty
D 1 Product Inventory
D 2 C ustom ers
9 U sernam e and
Passw ord
U sernam e+passw - Login
ord
*

C ustom ers
Product-ID

3
Product ID
Add product
to
C art
*

C art Item
C art Item ID
5
Shopping C ustom er
D3 C art Item s C heck-out C ustom er O rder D4
C art O rders
O rder
*
C art Item
N ew C redit C ard C ustom er O rder
4 C redit C ard
C redit C ard
C redit C ard
View /Am end D etails 8
C art
Issue O rder
* C redit
D5 to Shipping
C ards
Agent
C redit C ard *
Status 7
Issue Shipping
C redit C C for C opyO fC ustom ers R equest
C ard Validation
Co *

C redit C ard Shipping

Agent

Fig. 3.12: Data Flow Diagram

19
3.3.3 Data Dictionary

After carefully understanding the requirements of the client then entire data storage
requirements are divided into tables. The below tables are normalized to avoid any
anomalies during the course of data entry.

Table 3.1: tblAddress

20
Table 3.2: tblAdminMenu1

Table 3.3: tblAdminMenu2

21
Table 3.4: tblAttributes

Table 3.5: tblBrands

22
Table 3.6: tblCategories

Table 3.7: tblCity

23
Table 3.8: tblCountry

Table 3.9: tblCustomer

24
 Table 3.10: tblFeaturedProducts

3.3.4. ER Diagrams

 The relation upon the system is structured through a conceptual ER-Diagram, which not
only specifies the existential entities but also the standard relations through which the
system exists and the cardinalities that are necessary for the system state to continue.

 The Entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modelling activity the
attributes of each data object noted is the ERD can be described resign a data object
descriptions.
 The set of primary components that are identified by the ERD are
Data object Relationships
Attributes Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

25
Fig 3.13: E-R Diagram

26
 CHAPTER 4
Implementation

4.1 Coding/Code Templates

Default.aspx:

<%@ Page Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true"

CodeFile="Default.aspx.cs" Inherits="_Default" Title="E-Postal Services Network" %>

<%@ Register Src="Browse/Controls/ucFeaturedProducts.ascx"

TagName="ucFeaturedProducts"
TagPrefix="uc2" %>
<%@ Register Src="Browse/Controls/ucNewProducts.ascx" TagName="ucNewProducts"
TagPrefix="uc3" %>

<%@ Register Src="Browse/Controls/ucHotSellingProducts.ascx"

TagName="ucHotSellingProducts"
TagPrefix="uc1" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<table style="width:95%">
<tr>
<td style="width:95%" align="center" valign="top">
<uc1:ucHotSellingProducts ID="UcHotSellingProducts1" runat="server" />
</td>
</tr>
<tr>
<td style="width:95%" align="left" valign="top">
<uc2:ucFeaturedProducts ID="UcFeaturedProducts1" runat="server" />
</td>
</tr>
<tr>
<td style="width:95%" align="left" valign="top">

27
<uc3:ucNewProducts ID="UcNewProducts1" runat="server" />

</td>
</tr>
</table>
</asp:Content>

Web.config:

<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<appSettings>
<add key="CONSTR" value="Data Source=DELL-PC;Initial
Catalog=EPostOfficeNew;Integrated Security=true"/>
<!--<add key="EasyWearConnectionString" value="Server=localhost;Data Source=SYS\
SQLEXPRESS;Initial Catalog=EPostOfficeNew;Integrated Security=true"/>-->
</appSettings>
<connectionStrings>
<add name="EasyWearConnectionString" connectionString="Data Source=DELL-PC;Initial
Catalog=EPostOfficeNew;Integrated Security=true" providerName="System.Data.SqlClient"/>
</connectionStrings>
<system.web>

<!--

28
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="System.Design, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=B03F5F7F11D50A3A"/></assemblies></compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Forms">
<forms loginUrl="Registration/frmLogin.aspx" name="AuthCookie" timeout="60" path="/">
</forms>
</authentication>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/>

29
</system.web>
</configuration>

MasterPage.master:

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs"

Inherits="MasterPage" %>
<%@ Register Src="Skins/Default/Controls/ucAdAccenture.ascx" TagName="ucAdAccenture"
TagPrefix="uc5" %>
<link href="StyleSheet.css" rel="stylesheet" type="text/css" />
<%@ Register Src="Skins/Default/Controls/ucMasterLeft.ascx" TagName="ucMasterLeft"
TagPrefix="uc4" %>
<%@ Register Src="Browse/Controls/ucPopularCategories.ascx"
TagName="ucPopularCategories"
TagPrefix="uc3" %>
<%@ Register Src="Skins/Default/Controls/ucMasterHeader.ascx"
TagName="ucMasterHeader"
TagPrefix="uc1" %>
<%@ Register Src="Skins/Default/Controls/ucMasterFooter.ascx" TagName="ucMasterFooter"
TagPrefix="uc2" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head runat="server">
<title>E-Postal Services Network</title>
<link href="StyleSheet.css" rel="stylesheet" type="text/css" />
</head>
<body>
<form id="form1" runat="server" style="margin-top:0; margin-bottom:0; width:100%;">

30
<div style="width:100%">
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td colspan="4" valign="top" style="width:100%" align="left">
<uc1:ucMasterHeader ID="UcMasterHeader1" runat="server" />
</td>
</tr>
<tr>
<td style="width:1%; border-right:1pt; border-right-style:solid; border-right-color:Silver"
align="left">&nbsp;</td>
<td align="left" valign="top" style="width:80%;">
<asp:contentplaceholder id="ContentPlaceHolder1" runat="server">
</asp:contentplaceholder>
</td>
<td align="left" valign="top" style="width:10%;">
&nbsp;</td>
</tr>
<tr>
<td colspan="4" align="left">
<uc2:ucMasterFooter ID="UcMasterFooter1" runat="server" />
</td>
</tr>
</table>
</div>
</form>
</body>
</html>

31
4.2 TESTING

4.2.1. Introduction

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design,and coding. In fact, testing is the one step in the
software engineering process that could be viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design methods into a
well-planned series of steps that result in the successful construction of software. Testing
is the set of activities that can be planned in advance and conducted systematically. The
underlying motivation of program testing is to affirm software quality with methods that
can economically and effectively apply to both strategic to both large and small-scale
systems.

4.2.2. Strategic Approach To Software Testing

The software engineering process can be viewed as a spiral. Initially, system

engineering defines the role of software and leads to software requirement analysis where
the information domain, functions, behaviour, performance, constraints and validation
criteria for software are established. Moving inward along the spiral, we come to design
and finally to coding. To develop computer software we spiral in along streamlines that
decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vertex of the spiral and concentrates on each unit of the software as
implemented in the source code. Testing progress by moving outward along the spiral to
integration testing, where the focus is on the design and the construction of the software
architecture. Talking another turn on outward on the spiral we encounter validation
testing where requirements established as part of the software requirements analysis are
validated against the software that has been constructed. Finally, we arrive at system
testing, where the software and other system elements are tested as a whole.

32
 UNIT TESTING

MODULE TESTING

Component Testing SUB-SYSTEM TESING

SYSTEM TESTING

Integration Testing

ACCEPTANCE TESTING

User Testing

Fig. 4.1: Strategic Approach To Software Testing

4.2.3. Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the
module. The unit testing we have is white box oriented and some modules the steps are
conducted in parallel.

1. White Box Testing

This type of testing ensures that

 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.

33
 To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check
their validity. All loops are executed on their boundaries.

2. Basic Path Testing

The established technique of flow graph with Cyclomatic complexity was used to
derive test cases for all the functions.
Determine the Cyclomatic complexity of the resultant flow graph, using the formula:

V(G)=E-N+2 or

V(G)=P+1 or

V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of a set of linearly independent paths.

3. Conditional Testing

In this part of the testing, each of the conditions were tested to both true and false
aspects. And all the resulting paths were tested. So that each path that may be generated
on a particular condition is traced to uncover any possible errors.

4. Data Flow Testing

34
 This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable was declared. The definition-use chain method was used in this type of testing.
These were particularly useful in nested statements.

5. Loop Testing

In this type of testing, all the loops are tested to all the limits possible. The following
exercise was adopted for all loops:

 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For nested loops test the innermost loop first and then work outwards.
 For concatenated loops, the values of dependent loops were set with the help of a
connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and tested as
above.

Each unit has been separately tested by the development team itself and all the input
have been validated.

35
 CHAPTER 5
RESULT ANALYSIS
5.1 OUTPUT –SCREENSHOTS

Fig. 5.1: Home Page

36
 Fig. 5.2: Admin

Fig. 5.3: Category

37
 Fig. 5.4: Login

Fig. 5.5: Products

38
Fig. 5.6: User Registration

Fig. 5.7: Manage Users

39
 Fig. 5.8: Orders

Fig. 5.9: Epayment

40
Fig. 5.10: Feedback

Fig. 5.11: ContactUs

41
 CHAPTER 6
CONCLUSION AND FUTURE ENHANCEMENTS

CONCLUSION:
It has been a great pleasure for me to work on this exciting and challenging project.
This project proved good for me as it provided practical knowledge of not only
programming in ASP.NET and VB.NET web-based application and no some extent
Windows Application and SQL Server, but also about all handling procedure related with
“E-POST OFFICE”. It also provides knowledge about the latest technology used in
developing a 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.

Limitations:

 The size of the database increases day-by-day, increasing the load on the database back
up and data maintenance activity.

 Training for simple computer operations is necessary for the users working on the
system.

FUTURE ENHANCEMENTS:

 This System being web-based and an undertaking of Cyber Security Division needs to be
thoroughly tested to find out any security gaps.

 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.

42
BIBLIOGRAPHY/REFERENCES:

 For .Net Installation

www.support.mircosoft.com

 For Deployment And Packing On Server

www.developer.com

www.15seconds.com

 For SQL

www.msdn.microsoft.com

 For ASP.NET

www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

43