1.1 Purpose: Online Integrated Shopping Management Portal

Online Integrated Shopping Management Portal
CHAPTER 1
INTRODUCTION
1.1 Purpose
Mobile e-mail client is an application software which stores the messages in a file that
are located on the local Mobile. Like all other common e-mail client, it also provides the
basic functions like e-mail reading, creation and sending of new mails, Forwarding of
mails etc. It also helps in offline e-mail reading which is made possible by storing the
new mails whenever the user opens the application and connects to the internet.
1.2 Scope
 Importance of e-mail communication
 PDA market covers almost 60% of total mobile market.
 The most famous and common OS used for PDA is symbian.
 No device is more mobile and user friendly than PDA.
 Consumes less power.
 Accessing e-mails from PDA will be more convenient since they are
always on.
 Simple interface compared to a computer
 Just the basic knowledge about e-mail is required. Not required to know
 the operation of a computer
1.2 Definitions, Acronyms and Abbreviations

 PDA: A personal digital assistant (PDA), also known as a palmtop computer,
it is a mobile device that functions as a personal information manager. Current
PDAs often have the ability to connect to the Internet
 J2ME: Java Platform, Micro Edition, or Java ME, is a Java platform designed
for embedded systems (mobile devices are one kind of such systems.

Department of Computer Science, SOE 1
1.3 References
 IEEE SRS Format
1.4 Technologies to be used

 Programming languages:
 J2ME: Java Enterprise Edition is a programming platform part of the Java

Platform-for developing and running distributed multi-tier architecture Java
applications, based largely on modular software components running on a
server.
 HTML: Hyper Text Markup Language and Extensible markup Language are
the predominant markup languages for web pages. It provides a means to
describe the structure of text-based information in a document and to
supplement that text with interactive forms, embedded images, and other
objects.
 SMTP: Simple Mail Transfer Protocol (SMTP) is an Internet standard for

electronic mail (e-mail) transmission across Internet Protocol (IP) networks..
Tools & Development Environment
 Qt: Qt is a cross-platform application and UI framework. Using Qt, you can

write web-enabled applications once and deploy them across desktop, mobile
and embedded operating systems without rewriting the source code.
 NetBeans: NetBeans refers to both a platform framework for Java desktop

applications, and an integrated development environment (IDE) for
developing with Java, JavaScript, PHP, Python, Ruby, Groovy, C, C++, Scala,
Clojure, and others.
 Symbian OS: It is one of Nokia's mobile operating systems for mobile devices and
smartphones, with associated libraries, user interface, frameworks and reference
implementations of common tools, originally developed by Symbian Ltd.[

CHAPTER 02
SYSTEM ENVIRONMENT
2.1 System Requirement
To be used efficiently, all computer software needs certain hardware components or

other software resources to be present on a computer. These pre-requisites are known as
(computer) system requirements and are often used as a guideline as opposed to an
absolute rule. Most software defines two sets of system requirements: minimum and
recommended. With increasing demand for higher processing power and resources in
newer versions of software, system requirements tend to increase over time. Industry
analysts suggest that this trend plays a bigger part in driving upgrades to existing
computer systems than technological advancements.
2.1.1 Software requirement
Operating system - Linux/Windows
-Symbian S60
Softwares -Qt
-Net beans

2.1.2 Hardware requirement
The table shown gives the details of all the hardware requirements for this software
to be run successfully. It consists of processor, memory, hard disk, floppy disk, monitor,
mouse, CD drive, operating system, etc. The table shown in the next page shows the all
details of above mentioned hardware.
Minimum and Recommended Hardware requirement are depicted in the table given in the
next page.
TABLE 2.1 HARDWARE REQUIREMENTS FOR PC
ITEM MINIMUM IDEALLY

REQUIREMENTS RECOMMENDED H/W
CONFIGURATION
1 Processor Pentium II Pentium IV 866MHz
2 Memory 64 MB 128 MB
3 Hard Disk 4GB 40 GB
4 Monitor SVGA-Mono SVGA-Color
5 Mouse Ps-2, 2-Button Ps-2, 3-Buttonscroll mouse
6 CD ROM Drive Optional 52X
7 Operating system Windows Xp Windows Xp
8 UPS Optional (1 KVA-Online) 1 KVA-Online

TABLE 2.1 HARDWARE REQUIREMENTS FOR PDA
ITEM MINIMUM IDEALLY

REQUIREMENTS RECOMMENDED H/W
CONFIGURATION
1 Processor ARM(356 MHZ) Pentium IV 866MHz
2 Device Nokia E series Nokia E series
3 SIM card 2G sim 3G sim
4 Internet connection 25-40kbps(gprs) 384kbps-2mbps(3G)

CHAPTER 03
SYSTEM ANALYSIS
3.1 Existing System
Many e-mail clients are designed for symbian based phones. Most of them
were designed by manufactures them self offering less functionalities. These are
insufficient in providing functions like group mails. Different applications are required
for performing different functions on e-mail.
3.2 Proposed system
Proposed system is designed to works in symbian platform; it provides all basic functions
like, e-mail reading, composing new mails, reply, forwarding, deletion. And it includes
some special functions like offline mail reading, scheduling, group Mail.
3.3 System Functions
 User: End user(client)
 Functions: client is the only user related with this software, he uses this
application to view and download mails from the mail server.
3.3 Constraints
 Reliability in net connection. An un-interrupted connection is required while
storing the e-mails to the local device.
 No defined database for storing and indexing mails.
 Successive file accessing is complex for PDA.

CHAPTER 4
SYSTEM DESIGN
4.1 Input Design
Fig 4.1 Home

Make UR Own Website
Fig 4.2 Account Creation

Shop Keeper Login (First time)
Fig 4.3 Shop Keeper Login (First time)

Fig 4.4 Themes & Menu

Fig 4.5 Header & Menu Customization

Fig 4.6 Shop Keeper Interface

Fig 4.7 Add Product

Fig 4.8 Transaction & Stock

Fig 4.9 Product & Gallery

Fig 4.10 User Sign Up

Fig 4.11 Customer Interface

4.2 FUNCTIONALITIES AND DESCRIPTION
4.2.1 DATA FLOW DIAGRAM
The data flow diagram reviews the current physical system, prepares input and
output specification, specifies the implementation plan etc. Four basic symbols are used
to construct data flow diagram. They are symbols that represent data source data flow and
data transformation and data storage. The points at which data are transformed are
represented by enclosed figures, usually circles, which are called nodes. Basic data flow
diagram symbols are:
Data Flow Diagram Symbols
1.
= Function
2.
=Files/Databases
3. = Input/Output
4. = Data flow

Level 0 DFD of the system
Fig 4.3 Level 0 DFD
Level 1 DFD of the online module
Fig 4.3 Level 1 DFD for online module

Level 1 DFD for sending mails
Fig 4.4 Level 1 for sending
Level 1 DFD for offline Module
Fig 4.4 Level 1 DFD for offline module.

4.2.2 Modular Structure

The whole system has been modularized broadly into four modules namely the
Design module, the Mail handling module, Online module, and the Offline module. Each
of the modules functionalities have been described briefly in the paragraphs below.
Mobile E-Mail client
Design Mail handling Online Offline

Module
Module Module Module
Fig 4.7 Modular Structure
4.2.2.1 Design Module

The ‘Design Module’ deals with creation of the interface for the program. All other
modules will be integrated into the design once they are completed. The interface for the
offline and online activities share almost the same interface. Design module will
concentrate on designing interface for online activity. Minor differences of the offline
interface will be added later on.
Apart from designing of the interface this module also covers user verification,
checking connectivity, error reporting etc...
4.2.2.2 MAIL HANDELING MODULE

This module deals with the basic mail handling functions like e-mail creation,
mail forwarding, sending replays, and group mails.
Mail handling module will be an integral part of both online and offline modules.

4.2.2.3 ONLINE MODULE

This third module handles all the online activities. Once the connection is
established this module contacts the server. The first function is to check for new mails. It
also displays a snapshot of your e-mail account. This will include new mails, already read
mails. One of the most important functions in this module is mail sending. Apart from
sending new mails, it should also be able to send scheduled mails at the specified time.
This module comprises of almost 70% work of the total project. All the remaining
modules will directly inherit its properties.
Once the client establishes connection with the server, online module checks for
new mails. It also provides the user to back up the newly arrived mails to his local drives
so that he can use them even when he is offline through ‘offline module’.
4.2.2.4 OFFLINE MODULE

‘Offline module’ is a characteristic module in this project. This module makes
this e-mail client more reliable and friendly. This module inherits most of the
functionalities from online module. This includes sending new mails, composing new
mails etc.
The offline functionalities are explicitly activated when the device fails to
establish a connection with the server. At this point the client displays snapshot of mails
which were saved to the local drive (back up).
Just like the online module this module also provide facility for deleting messages
only this time the deleted messages are removed from the local drive.
All the activities performed on the back up messages are logged in to a ‘log file’.
This log file is critical in avoiding errors. Offline module also provides facilities for
offline mail scheduling. These scheduled messages will be mailed at the specified time
and date. If the client happens to be offline during the scheduled time, the messages will
be rescheduled and send whenever a connection is established with the server.

4. 3. DATABASE DESIGN
The data handled by the different modules includes user details like username, e-
mail id, and password, the mails received form server while online, backup copies of
mails and so on.. Including a database server (like MYSQL, DB2 every place etc) will
require installation of these third party soft wares on the device. This will be very
inconvenient for the user, moreover some of the DBMS management software like DB2
every place are not free of cost. Thus for the sake of simplicity the respective data will be
stored in files which are accessible directly by the software.
Critical user data like user name, password, e-mail id etc… will be stored in a file
called user.txt. The access to this file will be limited to this software alone by setting
attributes which prevents outside access.
The back up of mail involves basically of two different classes of files.
The first one is a log file which stores the details of transfer of mails from server
to device. After each successful transfer details like total mails stored, time of updating
the log, total mails currently present in the directory etc… are included. When a file is
deleted the process is repeated and the number of deleted files is subtracted from the total
mails and log is updated. In case of failures the current transfer is aborted and the file is
updated with id stored till the last one successful update.
Each new mail is stored in a new file including time of receiving, sender name
and address and content of the message. Each file is given a unique index which is used
to identify the message. The index will be made according to the time of receiving of the
message.
A user-mail file is used to map e-mail id to file id. This indexing allows user to
see mails in the order of senders. This file is randomly updated after addition of new
mails or after deletion.

Figure: User file used to store user details

Figure: Log file
Figure: index file
Figure: file storing mails

1.1 Purpose: Online Integrated Shopping Management Portal

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1.1 Purpose: Online Integrated Shopping Management Portal

Uploaded by

Copyright:

Available Formats

Online Integrated Shopping Management Portal

1.2 Definitions, Acronyms and Abbreviations

1.4 Technologies to be used

 J2ME: Java Enterprise Edition is a programming platform part of the Java

 SMTP: Simple Mail Transfer Protocol (SMTP) is an Internet standard for

Tools & Development Environment

 Qt: Qt is a cross-platform application and UI framework. Using Qt, you can

 NetBeans: NetBeans refers to both a platform framework for Java desktop

Department of Computer Science, SOE 2

2.1 System Requirement

To be used efficiently, all computer software needs certain hardware components or

2.1.1 Software requirement

Operating system - Linux/Windows

Department of Computer Science, SOE 3

2.1.2 Hardware requirement

TABLE 2.1 HARDWARE REQUIREMENTS FOR PC

ITEM MINIMUM IDEALLY

3 Hard Disk 4GB 40 GB

4 Monitor SVGA-Mono SVGA-Color

5 Mouse Ps-2, 2-Button Ps-2, 3-Buttonscroll mouse

6 CD ROM Drive Optional 52X

7 Operating system Windows Xp Windows Xp

8 UPS Optional (1 KVA-Online) 1 KVA-Online

Department of Computer Science, SOE 4

TABLE 2.1 HARDWARE REQUIREMENTS FOR PDA

ITEM MINIMUM IDEALLY

2 Device Nokia E series Nokia E series

3 SIM card 2G sim 3G sim

4 Internet connection 25-40kbps(gprs) 384kbps-2mbps(3G)

Department of Computer Science, SOE 5

3.1 Existing System

3.2 Proposed system

3.3 System Functions

 User: End user(client)

 No defined database for storing and indexing mails.

 Successive file accessing is complex for PDA.

Department of Computer Science, SOE 6

Fig 4.1 Home

Department of Computer Science, SOE 7

Make UR Own Website

Fig 4.2 Account Creation

Department of Computer Science, SOE 8

Shop Keeper Login (First time)

Fig 4.3 Shop Keeper Login (First time)

Department of Computer Science, SOE 9

Fig 4.4 Themes & Menu

Department of Computer Science, SOE 10

Fig 4.5 Header & Menu Customization

Department of Computer Science, SOE 11

Fig 4.6 Shop Keeper Interface

Department of Computer Science, SOE 12

Fig 4.7 Add Product

Department of Computer Science, SOE 13

Fig 4.8 Transaction & Stock

Department of Computer Science, SOE 14

Fig 4.9 Product & Gallery

Department of Computer Science, SOE 15

Fig 4.10 User Sign Up

Department of Computer Science, SOE 16

Fig 4.11 Customer Interface

Department of Computer Science, SOE 17

4.2 FUNCTIONALITIES AND DESCRIPTION