I.

Project Description
And Objective

1
1. Problem Statement

The existing system work manually. The existing system has got lot of intricacies within
itself and need lot of human effort and paper works. All above the data need to be maintained
on ledgers and maintaining this is a tedious and risky process. As the transactions increases,
so the data too. So the task of maintaining them increases exponentially. To view a data may
need lot of paper to be searched.

Some of the negative aspects of the existing system are as follows:

1) Course of action is time consuming. Wherever a need for search arises, the process
evolves search through paper records.

2) Readability of records is constrained. All the records may not be handled or written by
the same person. So the format and style of records differ and hence it is difficult to
understand.

3) Paper records are easily damaged in course of time. The life time of paper record is
unreliable less that it easily gets spoiled.

4) Expenditure is high. Manual system needs added man power.

5) Prone to corruption by unauthorized users. Securing of manual system is not fully
guaranteed. Inaccuracy can be expected. Data can get easily scratched.

6) Techniques used are more complicated. Proper techniques are not exposed, so the
functioning is intricate.

7) To overcome these, the proposed system has been suggested.

2. Background

The proposed system is a computerized one. This has greater accuracy and efficiency. This
takes only limited time for calculation.

The proposed system can be used to maintain efficiently the HR Department schedule of any
type of company. In larger organizations employees are large. At that time also the proposed
system is useful and helpful. HR Management System is not only become a desire of the
company but it become the need of the company.

2
3. Objective of the project

Our objective was to look at online retail from a customers point-of-view and determine
which of the biggest US-based ecommerce sites was providing the best customer experience.
A secondary aim was to zero in on key trends and identify opportunities for high-impact
customer experience improvements.

4. Stakeholders

The following are the stakeholders in this project:

Admin Admin or administrator will be a single or group of person in an organization
that are given access by the company heads to deal with critical data of the organization
and take due action on these issue centric data. Helping General users in getting their issues
resolved. They are given full access to handle any data from the backend.
General Users These are the target and bulk user of the system. System is being
developed for these users only. Other stakeholders are just to support these users. They are
given basic training on how to use this application. Their access level is restricted, mostly
pertaining to their own tasks only.

5. Functionality

The user gets into the system using user name and a unique password. Each user has his
own accessibility permission to accomplish his task flawlessly.

Advantages of the proposed system are

1) Easy access to the data

2) The new system is more user friendly, reliable and flexible.
3) Pop-up menus to carry out transactions for a new user, and for other alert
messages.

4) Timely Report generation.

3
 II.
Software Requirement
&
Specification

4
1. Introduction

An extremely powerful marketing tool, emarts ability to suggestively sell alternate and
complementary products; e.g. if a customer selects the "standard" version of a product, you can
recommend that they also consider the "pro" version or if your customer chooses a pair of
pants, you can suggest that they also consider a belt and socks. Simply specify related product
skus and optional text in a products definition in your Merchant Administrator, and PDG
Shopping Cart will up-sell or recommend related products to your customers automatically

1.1. Purpose

The purpose of this document is to present a detailed description of the Shop Around. It will
explain the purpose and features of the system, the interfaces of the system, what the system
will do, the constraints under which it must operate and how the system will react to external
stimuli. The final product will be having only features/functionalities mentioned in this
document and assumptions for any additional functionality/feature should not be made by any
of the parties involved in developing/testing/implementing/using this product This document
is intended for both the stakeholders and the developers of the system and will be used for
further development of the software as legal agreement.

1.2. Scope of Project

An extremely powerful marketing tool, emarts ability to suggestively sell alternate and
complementary products; e.g. if a customer selects the "standard" version of a product, you can
recommend that they also consider the "pro" version or if your customer chooses a pair of
pants, you can suggest that they also consider a belt and socks. Simply specify related product
skus and optional text in a products definition in your Merchant Administrator, and PDG
Shopping Cart will up-sell or recommend related products to your customers automatically

1.3. Definitions, Acronyms and Abbreviations

User: There are general user uses shop around application for the shopping purpose.
Stakeholders: Administrator, Users, Developer and the intended company for which the Shop
Around is developed have some sort of stake in this web-application software.
Administrator: The person responsible for managing the whole system. In our case he/she is
the head or an appointee in the admin department or IT department of a company. Note that
there can be multiple users (both admin/ normal users).
Developer: The persons who build the software. In the Shop Around, developer is the
company/organization/person who had developed the system.

5
1.4. References

Loginworks Software Online Order Processing System (Shop Around).

IEEE Recommended Practice for Software Requirements Specifications

1.5. Overview

The category screen shows all of the products available for a particular category. The product
screen shows all of the items in a particular product. Product screens right column of the list
shows the price of the item, and includes a link labelled Add to Cart. This link, which also
appears on screen for the corresponding
Item, allows the customer to add the item to the cart without looking at the item details.
The item screen shows detailed information about an individual item for sale .The Add to Cart
link, when clicked, adds an order for the item to the shopping cart, and then shows the shopping
cart contents .The cart screen lists the items currently in the cart, allows the customer to change
the quantity of each item ordered, and shows a title. It also includes a link to remove the item
from the cart, and a link Proceed to Checkout which, when clicked, shows the order information
screen if the user is signed on. If the user is not signed on, the sign on screen is shown instead.
The sign on screen allows an existing customer to sign in as an existing user, and a new
customer to create an account. An existing customer enters a user name and password, and the
application displays the Order Information screen shown in. A new customer enters a user
name and password and clicks the button Create New Account. The application creates a user
with the requested password. If user creation succeeds, the application displays the Account
Information screen.
The account information screen, shown in collects information about a new customer,
including contact information, a credit card, and personal preferences. This is also the screen
displayed whenever the customer clicks the Account link at the top right corner of the screen
(beneath the Search box). Clicking the Update button directs the browser to a page that
summarizes the information entered.
The Order Information screen allows the user to enter billing and shipping address. Default
values for the addresses come from the contact information for the currently signed-in
customer. This information is transmitted to the application when the user clicks Submit. The
application creates a new order, sends it to the order processing centre, and displays the Order
Complete screen.
The Order Complete screen verifies to the user that the order has been placed. The screen
includes the order number.

6
2. Overall Description

2.1. Product Perspective

Product Perspective was to look at online retail from a customers point-of-view and
determine which of the biggest US-based ecommerce sites was providing the best
customer experience. A secondary aim was to zero in on key trends and identify
opportunities for high-impact customer experience improvements.
We examined the entire experience. Unlike some studies that focus only on browsing, we
looked at the entire experience from the first moment on the site through selection,
purchase, shipping and returns.
We combined objective measurement with expert subjective analysis. Metrics have a
strong appeal, but in something that involves as many intangibles as the customer
experience measurement can only take you so far. With this in mind, we split our analysis
between straightforward objective grading and the expert opinions of our panellists. (In
poker terms, think of a good objective score as a table stakes and a good subjective score as
a hand that could win you the game.

1.1.1. System Interface: None.

1.1.2. User Interfaces:

The system is provided with click and goes type of graphical user interface with buttons and
links that can be easily understood by the user so that the errors in the entering the date in
appropriate fields can be reduced.

The system is designed in such a way that a user without any computer knowledge can also use
the system with the aid of help file that is also called as user manual. A menu interface has
been provided to the client that is compatible with Windows environment and is designed to
be user friendly.

The client is provided with an introductory help about the client interface and the user
documentation has been developed through help menu. The system is user-friendly and the
system can be implemented on any software environment.

2.1.3. Hardware Interfaces

Main Processor Pentium IV

Hard-disk Capacity 8 G.B

RAM 256 MB

Clock Speed 2.8 Hz

7
Floppy Drive : 1.44MB

Keyboard 104 Key

Software Requirement

Operating System Window 8

Back-end tool- Oracle 10g
Front-end tool- Java8

2.1.4. Software Interfaces

Database: Oracle 10g
IDE: Eclipse
Language: Java 8
Framework: Servlet, Jsp.

2.1.5. Communications Interfaces None

2.1.6. Memory Constraints:
Hard Disk Space: 8 GB or more.
RAM: 256 MB or more
2.1.7. Operations None
2.1.8. Project Adaptation Requirements
The work-station will have to support the hardware and software interface specified in above
sections.

2.2. Product Functions

The system will allow access only to authorized users with specific roles (Administrator,
Users). Depending upon the users role, he/she will be able to access only specific modules of
the system. A summary of the major functions that the software will perform:
User (Administrator, users) will be able to log into the online application by entering
their credentials on the login page.
User (Administrator, Users) will be able to see a customized homepage according to
their respective roles in the system. User can view his respective all the Items.
Admin will be able to see list of all item/products in the store and can manage these
items from this screen itself.

8
 Admin will be able to see list of all issues raised by several users in the company in a
data-grid and can manage these issues from this screen itself.
Admin will be able to see list of all notices by the in a data-grid and can manage these
notices from this screen itself.

2.3. User Classes and Characteristics

There are various kinds of users for the product. Usually web products are visited by various
users for different reasons. The users include:
Developer: This is not a user of the system in particular is developer of the system who
uses system to check whether the system developed is correct or not.
Administrator: The task of Administrator consists of all tasks of the Shop Around
Application which allows it to manage all products along with other functionality of a
normal user.
Users: Users can access the products from the company through the site, he can browse
according the own choice.
Characteristics
Developer:
1. They have full knowledge about Shop Around application and have complete access
over the software and can make necessary changes to the server-side coding of the web-
application developed.
2. They can make changes to the database internally and can create or drop database at
will.
3. They test system for any error and maintain it accordingly from time to time
Administrator:
1. They have full knowledge about Shop Around application and have complete access
over the software.
2. They cannot make changes to the database internally.
3. They manage all items of the system.
4. They have access to view data of all other products and monitor their activity.
Users:
1. They just deal with specific task related to themselves.
2. These users are present in bulk in the system and are the intended to their own ease to
manage organizational tasks.
3. They cant create a new user for the system.
2.4. Constraints
Users at company will have to implement a security policy to safeguard the status
information from being modified by unauthorized users (by means of gaining access to the
backend database).

9
10
 The product needs no third party product pre-installed on the workstation. But do requires
a standard browser like IE, Firefox, etc. that can effectively handle the web UI of the
application.

2.6. Apportioning of Requirement Not Required.

3. Specific Requirements

This section contains the software requirements to a level of detail sufficient to enable
designers to design the system, and testers to test that system.

3.1. External Interfaces

Since the application is a web-based application and it caters to a company and all its
products, the UI is kept utmost basic so that it is easy to be followed by all users of the
company. The following screens / pages will be provided by the application. Note that the
screen shots given here are just mock ups prepared to give an idea of how the UI will look
to applications user.

Login Page:
This is the page that will be displayed when you type in the employee portals URL on the
address bar. It allows user to access different pages and links based upon the users access-
level (admin or employee).

Default/ Homepage:
This page will be a customized page with customized links according to the role of the
product category. The page will show active notices and open issues in the content area if
the user is not logged in.

Customer Registration Page:

This page will be used to for register of users by editing their details, deleting users profile
from the database and can add a new users when it login through this page itself.

Edit Items Page:

This page is used to edit details of items.

Search Products Keyword:

This search keyword will be used by all items to search product in a categories.

Delete Product:
This page will be delete the item admin want to delete.

11
3.2. Functions

The system will allow access only to authorized users with specific roles (Administrator,
Users). Depending upon the users role, he/she will be able to access only specific modules of
the system. A summary of the major functions that the software will perform

3.3. Performance Requirements

Shopping Cart application must be able to efficiently handle the above stated functional
requirements for a company of a size of about big products.

3.4. Design Constraints

The application must have all the pages accessed from the homepage itself through its links
and menu.

3.5. Logical Database Requirements

The following data will be placed in the database named Shopping Cart under the name of
following tables:

USER_INFO:

S.No Column Name Data Type Description

1 user_id INT(11) Primary Key

2 fist_name Varchar(100)
3 last_name Varchar(100)
4 email Varchar(300)
5 password Varchar(100)
6 mobile Varchar(10)
7 address1 Varchar(300)
8 address2 Varchar(200)

PRODUCTS:

S.No Column Name Data Type Description

1 product_id INT(11) primary key

2 product_cat INT(11)
3 product_brand INT(100)
4 product_title Varchar(300)

12
5 product_price INT(100)
6 product_desc TEXT
7 product_image TEXT
8 product_keywords TEXT

CATEGORIES:

S.No Column Name Data Type Description

1 cat_id INT(11) primary key

2 cat_title TEXT

CART:

S.No Column Name Data Type Description

1 id INT(11) primary key

2 p_id INT(11)
3 user_id INT(11)
4 product_title Varchar(300)
5 product_image TEXT
6 qty INT(100)
7 price INT(100)
8 total_amount INT(100)

BRANDS:

S.No Column Name Data Type Description

1 brand_id INT(11) primary key

2 brand_title TEXT

3.6. Software system attributes

3.6.1. Reliability:

The application is very reliable as there is no duplicity or redundancy of data and database is
managed on MySQL which has its own credentials authenticated based interface which is very
secure.

3.6.2. Availability:

The application will be easily available as it is a web-application that needs a basic browser to
view web pages, any PC without any fancy configuration will do the needful.

13
3.6.3. Security:

The application will be username and password protected. Users will have to enter correct user
name, password to gain authentic user tag to access this web - application. No security breach
is possible by accessing data in session variables through the URL.

3.6.4. Maintainability:

The application will be designed in a maintainable manner. It will be easy to incorporate new
requirements in the individual modules. The workstation that will be used for maintenance in
future, need to have all the development tools used while developing the application like
Sublime Text 3 and MySQL 5.7.14.

3.6.5. Portability:

The application will be easily portable on type of machine as it is a web based application
deployed on a remote server. Server machine must have PHP 7, MySQL 5.7.14 to handle the
database. Client machine just needs a browser to be able to view web-pages with basic html
tags.

14
 III.

Technology Used

15
1. Introduction to PHP

The PHP Hypertext Preprocessor (PHP) is a programming language that allows web
developers to create dynamic content that interacts with databases. PHP is basically used for
developing web based software applications.

History of PHP

PHP was written by Rasmus Lerdorf in 1994. It was a set of CGI binaries in the C
programming language. It was firstly, developed for maintaining a personal homepage. It was
first publicly released on 1995. In 1998 two developer Zeev Suraski and Andi Gutmans wrote
major part of PHP. In 2000 the Zend Engine company re-wrote the core of PHP and in 2004
Zend Engine 2 released new and improved version with better performance and Object
Oriented Programming feature.

PHP Features

Some of the important features of PHP are as follows:

Simplicity

Cross platform to develop

Open Source

Powerful, Robust & Scalable

Designed for the web

Object-Oriented feature

Orientation

Great Documentation

Client Side Interface:

In client side interface we are using:-

JQuery / AJAX for Internet Based Application.

16
JQuery / AJAX are middle-ware technologies which are used in web based projects because
they use:-

Give a Behavior to the webpage.

They are invoked through Browser.

They give output in HTML format.

They need Browser Support.

HTML/CSS:

HTML stands for Hyper Text Markup Language, which is the most widely used language on
Web to develop web pages.

Cascading Style Sheets, is a simple design language intended to simplify the process of
making web pages presentable.

JAVASCRIPT:

JavaScript is a programming language often referred to as scripting language. JavaScript is for

programming language behavior and interactivity.

MYSQL:

MySQL is the most popular Open Source Relational SQL database management system.
MySQL is one of the best RDBMS being used for developing web-based software applications.

WAMPSERVER:

The WAMP stack provides developers with the four key elements of a Web server: an
operating system, database, Web server and Web scripting software.

17
 1. Introduction to MySQL

Mysql 5.7.14 contains all the features of previous version. It also supports some new features
& enhancement to some existing features. Mysql servers provide deficient & effective
solution for the major features.

Large Database & Space Management Control

Mysql supports the largest database potential of hundreds of Giga Bytes in size. To make
efficient use of expensive devices, it allows full control of space usage.

Many Concurrent Database Performances

It supports large no of concurrent users executing a variety of database applications operation

on the same data. It minimizes data connection & guarantees data concurrency.

High Transaction Processing Performance

Mysql maintains the processing features with a high degree of overall system performance.
Database users dont suffer from slow processing performance.

High Availability

Mysql works 24 hours a day with no downtime or limited database throughput. Normal
system operation such as database backup & partial system failure doesnt interrupt database
use.

Controlled Availability

Mysql can selectively control the availability of data at the database level & sub database
level. E.g. an administrator can disallow use of a specific application. Data can be reloaded
without affecting other application.

Industry Accepted Standards

Mysql adheres to industry accepted standards for the data access language operating system,
user interface & network communication protocols.

Manageable Security

To protect against unauthorized database aspects & users, Mysql provides failsafe security
features to limit & monitor the data area. The system makes it easy to manage even the most
completed designs for data assets.

18
 2. Layered Development Architecture

This guide was developed to disseminate proven practices to system developers, project
managers, program/account analysts and system owners/users throughout the DOJ. The
specific objectives expected include the following:

To reduce the risk of project failure

To consider system and data requirements throughout the entire life of the system

To identify technical and management issues early

To disclose all life cycle costs to guide business decisions

To foster realistic expectations of what the systems will and will not provide

To provide information to better balance programmatic, technical, management, and

cost aspects of proposed system development or modification

To encourage periodic evaluations to identify systems that are no longer effective

To measure progress and status for effective corrective action

To support effective resource management and budget planning

19
 IV.

Feasibility Study

20
1. Introduction

A feasibility study is conducted to select the best system that meets performance requirement.
This entails an identification description, an evaluation of candidate system and the selection
of best system for the job. The system required performance is defined by a statement of
constraints, the identification of specific system objective and a description of outputs.

2. Economic feasibility

It looks at the financial aspects of the project. It determines whether the management has
enough resources and budget to invest in the proposed system and the estimated time for the
recovery of cost incurred. It also determines whether it is worthwhile to invest the money in
the proposed project. Economic feasibility is determines by the means of cost benefit analysis.
The proposed system is economically feasible because the cost involved in purchasing the
hardware and the software are within approachable. The personal cost like salaries of
employees hired are also nominal, because working in this system need not required a highly
qualified professional. The operating-environment costs are marginal. The less time involved
also helped in its economic feasibility. It was observed that the organization has already using
computers for other purpose, so that there is no additional cost to be incurred for adding this
system to its computers. The backend required for storing other details is also the same database
that is Sql. The computers in the organization are highly sophisticated and dont needs extra
components to load the software. Hence the organization can implement the new system
without any additional expenditure. Hence, it is economically feasible.

3. Technical feasibility

It is a measure of the practically of a specific technical solution and the availability of technical
resources and expertise. The system will be used if it is developed well then be resistance for
users that undetermined
No major training and new skills are required as it is based on DBMS model.
It will help in the time saving and fast processing and dispersal of user request and
applications.
New product will provide all the benefits of present system with better performance.
Improved information, better management and collection of the reports.
User support.
User involvement in the building of present system is sought to keep in mind the user
specific requirement and needs.
User will have control over their own information. Important information such as pay-
slip can be generated at the click of a button.
Faster and systematic processing of user application approval, allocation of IDs,
payments, etc. used had greater chances of error due to wrong information entered by
mistake.

21
Hardware used in this project are- p4 processor 2.4GHz, 128 MB RAM, 40 GB hard disk,
floppy drive. These hardware were already available on the existing computer system. The
software like MySQL 5.7.14, Wamp Server, Thin Driver, and operating system WINDOWS-
XP used were already installed on the existing computer system. So no additional hardware
and software were required to purchase and it is technically feasible. The technical feasibility
is in employing computers to the organization. The organization is equipped with enough
computers so that it is easier for updating. Hence the organization has not technical difficulty
in adding this system.

4. Legal feasibility

People are inherent to change. In this type of feasibility check, we come to know if the newly
developed system will be taken and accepted by the working force i.e. the people who will use
it.

5. Operational feasibility

The system will be used if it is developed well then be resistance for users that
undetermined

No major training and new skills are required as it is based on DBMS model.
It will help in the time saving and fast processing and dispersal of user request and
applications.
New product will provide all the benefits of present system with better performance.
Improved information, better management and collection of the reports.
User support.
User involvement in the building of present system is sought to keep in mind the user
specific requirement and needs.
User will have control over their own information. Important information such as pay-
slip can be generated at the click of a button.
Faster and systematic processing of user application approval, allocation of IDs,
payments, etc. used had greater chances of error due to wrong information entered by
mistake.

22
 V.

Design of System

23
 1. Use Case Diagram

On line Ordered Processing System

Create Account

Login process

Ordered Process
User 1

Modify/Add
Details

Administrat
or
Delete Detail

View Report User 2

24
2. Use Case Description

2.1. Login

2.1.1. Brief Description:

This use case describes how the user loges into the portal.

2.1.2. Actors:
Admin, General Users.

2.1.3. Basic Flow:

This use case starts when the actor wishes to login to the web site.
(i) System requests that the actor enter his/her name and password.
(ii) The actor enters his/her name & password.
(iii) System validates name & password, and if finds correct allow the actor to logs
into the system.

2.1.4. Alternate Flows:

Invalid name & password - If in the basic flow, the actor enters an invalid name and/or
password, the system displays an error message. The actor can choose to either return
to the beginning of the basic flow or cancel the login, at that point, the use case ends.

2.1.5. Pre-Conditions:
None

2.1.6. Post-Conditions:
If the use case is successful, the actor is logged into the system. If not, the system state
is unchanged.

2.1.7. Special Requirements:

None

2.2. Add New Items

2.2.1. Brief Description:

This use case allows the Admin to add new product with category details.

2.2.2. Actors:
Admin

2.2.3. Basic Flow:

This use case starts when the Admin wishes to add the product/Items details. Admin
can fill the required details and submit it. Then General users can access the all types
of the items.

25
2.2.4. Alternate Flows:
Invalid details - If the details are not in correct format then error message will be shown.

2.2.5. Pre-Conditions:
Actor must be logged in.

2.2.6. Post-conditions:
Database will be updated.

2.2.7. Special Requirements:

None.

2.3. Edit existing Products

2.3.1. Brief Description:

This use case allows the Admin to edit existing employees details or an employee can
edit his own details.

2.3.2. Actors:
Admin/ Employee.

2.3.3. Basic Flow:

This use case when started general user searching the products/item from the site after choosing
the products he/her needs to login the site then he/she can buy the products. And he have need
to enter valid information according to the requirementation.

2.3.4. Alternate Flows:

Invalid details- If the details are not in correct format then error message will be shown.

2.3.5. Pre-Conditions:
Actor must be logged in.

2.3.6. Post-conditions:
Database will be updated.

2.3.7. Special Requirements:

None.

2.4. Search Products

2.4.1. Brief Description:

This use case will allow the user to search the details for products/Item and view them
on some given criterion.

26
2.4.2. Actors:
Admin, General users

2.4.3. Basic flow:

This use case when started general user searching the products/item from the site after choosing
the products he/her needs to login the site then he/she can buy the products. And he have need
to enter valid information according to the requirementation.

2.4.4. Alternate flows:

Invalid details- If the details are not in correct format then error message will be shown.

2.4.5. Pre-Conditions:
Actor must be logged in.

2.4.6. Post-conditions:
List of items and their details will be shown.

2.4.7. Special requirements:

None.

2.5. View Products Details

2.5.1. Brief Description:

This use case will allow the user to view details of a product.
2.5.2. Actors:
Admin, General users

2.5.3. Basic flow:

Actor will click on a products and it will be added to cart and actor can view the details
of any Items

2.5.4. Alternate flows:

Invalid details- If the details are not in correct format then error message will be shown.
2.5.5. Pre-Conditions:
Actor must be logged in.

2.5.6. Post-conditions:
Items details will be shown.
2.5.7. Special requirements:
None

27
3. E-R Diagram

28
4. Data Flow Diagrams

4.1. Context Analysis or Level-0 DFD

Add & update products,

category.
ADMIN

Get Queries.
Check Orders & Check

Browse Products.
Check Order Status
Online.
Get Query Response
CUSTOMER

Add Products to Carts.

Place Orders & Make

29
 4.2. Level-1 DFD

First Level DFD:

ADMIN

Add & update products,

category.
Get Queries.
Check Orders & Check

Check Order Status Add Products

Online. to Carts.
Place Orders & Browse
Make Payments. Products.
Make Query
CUSTOMER

Order Track
Create Account
Update Profile

Get Query Response

Get Payment Reports
Get Orders Reports
Get Delivery Reports

VISITOR MEMBER

30
 Second Level DFD (ADMIN):

Enter Username &

Password Process

ADMIN USER Login USER

I F LOGIN TRUE
THEN ENTER TO
ADMIN SECTION

PRODUCT
Add update, delete
ADMIN SECTION Product & Product
CATEGORY

Update Member Payment

Receiving MEMBER_PAYM
Check Orders & Order ENT
Details (External
Entity)

Get Query &

Update Query

QUERY
Place Orders to
Delivery & Update
DELIVERY Get Member
Check Orders & Order
ORDER DETAIL ORDER MEMBER
(External (External (External
Entity) Entity) Entity)

31
 Second Level DFD (MEMBER):

Enter Username & Process

MEMBER
MEMBER Password
USER Login Login

I F LOGIN TRUE Get or Update

THEN ENTER TO Profile
MEMBER SECTION

PRODUCT
Browse (External
MEMBER Products & Entity)
SECTION Add to
Cart and
Place Cart
to Order CATEGORY
(Check (External
Out) Entity)

Get Payment
Details
MEMBER_PAYMENT

Make Query
& Get
Get Delivery
Status Check Orders & Order
Details
QUERY DELIVERY ORDER DETAIL ORDER
(External (Derived (Derived
Entity) Entity)

32
 Second Level DFD (ORDER TRACK):

ENTER ORDER_ID
FOR ENTERING TO
THIS MODULE

ORDER TRACK
SECTION

Check Orders & Order

Make Query Details
& Get Get Delivery

DELIVERY
QUERY (External ORDER DETAIL ORDER
Entity) (Derived (Derived

33
5. Database Design

The process can be conceptualized in such a way to keep the methodology of main module
process along with some auxiliary task, which will run concurrently with the main program.

The top-down approach is maintained so as to keep track of the process, which satisfies the
maintenance reliability testing requirements. The concurrency of the data is checked during
data entry, by means of validation check for data in each field.

6. Process Design

The process can be conceptualized in such a way to keep the methodology of main module
process along with some auxiliary task, which will run concurrently with the main program.

The top-down approach is maintained so as to keep track of the process, which satisfies the
maintenance reliability testing requirements. The concurrency of the data is checked during
data entry, by means of validation check for data in each field.

7. Code Design

The process of code is to facilitate the identification and retrieve of items of information. The
code should be simple and easy to understandable. The codes were designed in such a way that
the features such as optimum human oriented use and machine efficiency are unaffected.

For the code to be designed effectively, the following characteristics were also considered
while designing the code.

Uniqueness
Versatility
Stability
Simplicity
Consciousness

The code should be adequate for present and anticipated data processing for machine and
human use. Care was taken to minimize the clerical effort and computer time required to
continue operation.

34
 VI.
Screen Shots
&
Functionality

35
1. Graphical User Interface (GUI)

As discussed in earlier chapters, this project deals with the general users, their issues and
notices details. The website contains many links and tabs for various requirements like Add to
cart, Search Keywords etc.
But we will be discussing that part of the project, which has been developed by us. So for this
project we basically dealt with:
1. Adding and updating products details
2. Deals with item Issues.
3. Notices.

36
37
38
39
40
41
42
 VII.

Implementation,
Testing & Analysis

43
1. Implementation

Implementation is the process of having systems personnel check out and put new equipment
into use, train users, install the new app Depending on the size of the organization that will be
involved in using the application and the risk associated with its use, systems developers may
choose to test the operation in only one area of the firm, say in one department or with only
one or two persons. Sometimes they will run the old and new systems together to compare the
results. In still other situation, developers will stop using the old system one-day and begin
using the new one the next. As we will see, each implementation strategy has its merits,
depending on the business situation in which it is considered. Regardless of the implementation
strategy used, developers strive to ensure that the systems initial use in trouble-free.

Once installed, applications are often used for many years. However, both the organization and
the users will change, and the environment will be different over weeks and months. Therefore,
the application will undoubtedly have to be maintained; modifications and changes will be
made to the software, files, or procedures to meet emerging user requirements. Since
organization systems and the business environment undergo continual change, the information
systems should keep pace. In this sense, implementation is ongoing process.

Evaluation of the system is performed to identify its strengths and weakness. The actual
evaluation can occur along any of the following dimensions.

Operational Evaluation: assessment of the manner in which the system functions,

including ease of use, response time, suitability of information formats, overall reliability,
and level of utilization.

Organization Impact: Identification and measurement of benefits to the organization in

such areas as financial concerns operational efficiency, and competitive impact. Includes
impact on internal and external information flows.

User Manager Assessment: Evaluation of the attitudes of senior and user mangers within
the organization, as well as end-users.

Development Performance: Evaluation of the development process in accordance with

such yardsticks as overall development time and effort, conformance to budgets and
standards, and other project management criteria. Includes assessment of development
methods and tools.

Unfortunately system evaluation does not always receive the attention it merits. Where
properly managed however, it provides a great deal of information that can improve the
effectiveness of subsequent application efforts.

2. Testing

44
Testing is a process of executing a program with the intent of finding errors. Testing is
essentially a destructive process where the tester treats the program as an adversary, to be
beaten by showing the presence of errors. With this in mind a test case is good if it detects an
undetected error in the program. The objective of test case design should be to cover all possible
scenarios in the application, both positive and negative, that detect as many errors as possible.

Software testing is performed by an independent group of testers after finishing the software
product and before it is shipped to the Client. However, testing as an activity starts the moment
the project starts and is a continuous process until the project finishes.

One of the reasons for an independent group to engage in software testing is that it is difficult
for a programmer to be destructive on something created by self. A programmer always tends
to believe in my program works, which is not the correct frame of mind for testing. Also,
errors may be induced due to lack of correct understanding of the specification.

Figure-45. Testing Process

2.1. Testing Objectives

Testing is a process of executing a program with the intent of finding an error.

A good test case is one that has a high probability of finding an as yet undiscovered
error.
A successful test is one that uncovers an as yet undiscovered error.

45
2.2. Different types of testing:

Unit Testing
It is the process of taking a module and running it in isolation from the rest of the software
product. In this, each module has to be tested thoroughly in order to discover pitfalls. This
helps us in detecting errors in coding and logic that are contained within that module alone.

Integration Testing
This testing is done by integrating all modules together as a unit. It is done to determine
that the interface between modules is correct.

System Testing
System testing makes a logical assumption that if all the parts of the system are correct, the
goal will be successively achieved. It tests the software as a whole with focus on operations
that will be requested by the user.

2.3. Test Data and Test Cases

The primary objective of test case design is to derive a set of tests that have the highest
likelihood of uncovering errors in software. The test case specification is the major activity in
the testing process. Careful selection of test cases that satisfy the criterion on approach
specified is essential for proper testing. Various characteristics of test cases that are required
for portal are:
A good test has a high probability of finding an error.
A good test is not redundant.
A good test should be Best of Breed.
A good test should be neither too simple not too complex.

2.4. Test plan

Testing commences with a test plan and terminates with acceptance testing. A test plan is a
general document for the entire project that defines the scope, approach to be taken and
schedule of testing as well as identifies the test item for the entire testing process and the
personnel responsible for the different activities of testing.

2.5. Test Cases for the Project:

We didnt develop any test cases as we are only developers. Testing was done by testing team
and by mentor. So we dont have any test cases.

46
2.6. Test Reports and Debugging

Various outputs are produced as a result of test case execution for the unit under test. These
outputs are needed to evaluate whether the testing has been satisfactory. The test report is meant
for project management where the summary of the entire test case execution is provided. The
summary gives the total number and nature of errors found and the summary of any metrics
data collected.

Debugging, in the form of error report, gives the summary of all the errors found. The errors
may also be categorized into different levels, if such a categorization is available and its use
has been planned in the test plan.

In our case, initially many errors were found out. All such errors as reported by the testing team
were rectified.

47
 VIII.

Conclusion

48
Conclusion

As evidence of the success of this mission, there are millions of items listed each day in
thousands of different categories. There are items for almost any interest that one could
imagine, from sheet music to automobiles to hand tools to real estate.

And the variety doesnt stop there. Need a computer? One may find it listed in the proper
category, in any configuration from very old and obsolete to the latest greatest machine
available. What about antiques? One can find an antique quilt that is up for highest bid, or
maybe an old violin, whose beautiful tones have enchanted many though its years. Tickets.
Maybe a ticket to the next concert of once favourite artist or play production. One can even
find that special bottle of wine, some aged, exotic cheese, and the perfect mood music for
that special occasion.

In this instance it may be true that on eBay, they have something for everybody, whatever their
tastes may be.

49
 IX.

References

50
References

http://www.php.net/

https://www.w3schools.com/php/default.asp

https://www.tutorialspoint.com/php/

http://stackoverflow.com/

PHP and MySQL Web Development Book

51