SHOPEE IN STYLE

An institutional oriented mini project report

Submitted By

G SUDHEER KUMAR G VENKATA MEGHANA

(14W91A0585) (14W91A0583)

EHTESHAM JAWEED K N CHANDRA SEKHAR

(14W91A0576) (14W91A0591)

Under the Esteemed Guidance of

Mr. PSRB SHASHANK

Asst.Professor, CSE
To

JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY HYDERABAD

In partial fulfillment of the requirements for award of degree of

BACHELOR OF TECHNOLOGY
IN
COMPUTER SCIENCE & ENGINEERING
2014 – 2018

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

MALLA REDDY INSTITUTE OF ENGINEERING AND TECHNOLOGY (MRET -
W9)
(Sponsored by Malla Reddy Educational society)
(Affiliated to JNTUH, Accredited to NBA)
Maisammaguda, Dhulapally post, Secunderabad-500014.
 DECLARATION

We hereby declare that the project entitled “SHOPEE IN STYLE” submitted to Malla Reddy Institute

of Engineering and Technology (MRET-W9), affiliated to Jawaharlal Nehru Technological University

Hyderabad (JNTUH) for the award of the degree of Bachelor of Technology in Computer Science &

Engineering is a result of original industrial oriented project done by us. It is further declared that the

project report or any part thereof has not been previously submitted to any University or Institute for the

award of degree or diploma.

1. G SUDHEER KUMAR

(14W91A0585)

2. G VENKATA MEGHANA

(14W91A0583)

3. EHTESHAM JAWEED

(14W91A0576)

4.K N CHANDRA SEKHAR

(14W91A0591)
MALLA REDDY INSTITUTE OF ENGINEERING & TECHNOLOGY
(Sponsored by Malla Reddy Educational Society)
Affiliated to JNTUH, Accredited to NBA
Maisammaguda, Dhulapally (post via Hakimpet), Sec’Bad-500 014.
Phone: 040-65969674, Cell: 9348161223

Department of Computer Science and Engineering

PROJECT CERTIFICATE

This is to certify that this is the bonafide record of the project titled “SHOPEE IN STYLE” is submitted
by G SUDHEER KUMAR (14W91A0585), G VENKATA MEGHANA(14W91A0583),
EHTESHAM JAWEED(14W91A0576), K N CHANDRA SEKHAR (14W91A0591) of B.Tech in the
partial fulfillment of the requirements for the degree of Bachelor of Technology in Computer Science
and Engineering, Dept. of Computer Science &Engineering and this has not been submitted for the award
of any other degree of this institution.

INTERNAL GUIDE PRINCIPAL

PROJECT COORDINATOR HOD

INTERNAL EXAMINER EXTERNAL EXAMINER

 ACKNOWLEDGEMENT

First and foremost, we are grateful to the Principal Dr. K. E. Balachandrudu, for providing us with all
the resources in the college to make our project a success. We thank him for his valuable suggestions at
the time of seminars which encouraged us to give our best in the project.

We would like to express our gratitude to Mr. M. Sreenivas, Dean Academics for his support and valuable
suggestions during the dissertation work.

We would like to express our gratitude to Dr. M. Ashok, Head of the Department, Department of
Computer Science and Engineering for his support and valuable suggestions during the dissertation work.

We offer our sincere gratitude to our project coordinator Dr. Ashfiqul Hasan Ali and internal guide Dr.
G. R. Anantha Raman Professor of Computer Science and Engineering department who has supported
us throughout this project with their patience and valuable suggestions.

We would also like to thank all the supporting staff of the Dept. of CSE and all other departments who
have been helpful directly or indirectly in making the project a success.

We are extremely grateful to our parents for their blessings and prayers for our completion of project that
gave us strength to do our project.

G SUDHEER KUMAR

G VENKATA MEGHANA

EHTESHAM JAWEED

K N CHANDRA SEKHAR
 INDEX
Abstract--------------------------------------------------------------------------------------i
List of Figures------------------------------------------------------------------------------ii
List of Tables-------------------------------------------------------------------------------iii
List of Screens------------------------------------------------------------------------------iv

S.NO CONTENTS PAGE NO.

1. INTRODUCTION 01

1.1 Motivation 02
1.2 Problem Definition 02
1.3 Objective of the Project 02
1.4 Limitations of Project 03
1.5 Organization of Documentation 03

2. LITERATURE SURVEY 05

2.1 Introduction 06
2.2 Existing System 07
2.3 Disadvantages of Existing System 07
2.4 Proposed System 07
2.5 Conclusion 08

3. ANALYSIS 09

3.1 Introduction 10
3.1.1 Economic Feasibility 10
3.1.2 Operational Feasibility 10
3.1.3 Technical Feasibility 11
3.2 Software Requirement Specification 11
3.2.1 User Requirements 11
3.2.2 Software Requirements 11
3.2.3 Hardware Requirements 11
3.3 Content Diagram of Project 12
3.4 Algorithms and Flowcharts 13
3.5 Conclusion 13
4. DESIGN 14
4.1 Introduction 15
4.2 Data Flow Diagrams 19
4.3 UML diagrams 22
4.4 Module Design and Organization 31
4.5 Conclusion 32

5. IMPLEMENTATION AND RESULTS 33

5.1 Introduction 34
5.2 Explanations of Key Functions 35
5.3 Methods of Implementation 36
5.3.1 Forms 47
5.3.2 Sample code 49
5.3.3 Output Screens 56
5.4 Conclusion 59

6. TESTING AND VALIDATION 60

6.1 Introduction 61
6.2 Design of test cases and Scenarios 62
6.3 Validation 65
6.4 Conclusion 66
7. CONCLUSION 67
7.1 Project Conclusion 68
7.2 Future Enhancement 68
REFERENCES 69
8.1 Text books 70
8.2 Web References 70
 SHOPPE IN STYLE

ABSTRACT
The purpose of this document is to define scope and requirements for company launching a range of
accessories on their website. With a tough competition having its presence in the Internet world, the
company focused on its strategy to leverage the state of the art search capabilities available on the WEB.
This document is the primary input to the development team to architect a solution for this project .

ii
 SHOPPE IN STYLE

LIST OF FIGURES

S.NO Figure No. Description Page no’s

01 4.1 Dataflow Case Diagrams 19

02 4.2 UML diagrams 22

04 4.4 ER Diagram for User 29

iii
 SHOPPE IN STYLE

LIST OF TABLES

Table No Title Page

4.1 Table for Admin Login 16
4.2 Table for File Information 16

4.3 Table for User Details 17

4.4 Table for User Login 18

4.5 Table for Approval 18

6.1 Example for GUI Test Cases 63

6.2 Example for positive Tests 63

6.3 Login Page Test Case 664

iv
 SHOPPE IN STYLE

LIST OF SCREENS

S.NO Screen No. Description Page no’s

1 7.1 Home page 55

2 7.2 User register page 56

3 7.3 Admin login page 67

v
 SHOPEE IN STYLE

ACRONYMS

ABRIVATION

GUI Graphical User Interface

HTML Hypertext Markup Language

JDBC Java Database Connectivity

JVM Java Virtual Machine

SQL Structure Query Language

SDLC Software Development Life Cycle

UML Unified Modelling Language

DFD Data Flow Diagram

0
 SHOPEE IN STYLE

INTRODUCTION

1
 SHOPEE IN STYLE

1. INTRODUCTION

1.1 MOTIVATION:

The Shopee in style 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 Shopee in style Service online quickly and comfortably.

Target groups of customer of the Shopee in style are huge. The customers can have a payment option
through credit card only. In order to use the load writing procedure, the customer registers itself and
receives a login for its purchases names and its applications.

1.2 PROBLEM DEFINITION:

We all want our project to work seamlessly, without defects, where everyone is aware and

informed of the outcomes and status.

Today the client has fine number of rollbacks which if ignored might cost them to lose revenue. We

use the Kaizen Blitz Method in order to keep improving the project with its every fundamental update.

1.3 OBJECTIVES:

 Simple and intuitive interface to enter the range of products.

 Automatically generate the html page for publishing on their website.
 Each product in their range shall be published as Rich Snippets. They will comply with the
Microdata format requirements of Google’s shopping search view.

2
 SHOPEE IN STYLE

1.3 LIMITATIONS OF PROJECT:

The problem for this system is the need of internet connection. The marketer will not be able to use

personal interaction to influence the audience.

1.4 ORGANIZATION OF DOCUMENTATION

The first step of the system analysis process involves the identification of the needs of the user. The
success of a system depends on how accurately a problem is analyzed and how efficiently it is resolved.

In the existing system, information pertaining to all organizations is unavailable to the user. The user/s
is/are unaware of current offers or deals provided by every organization/vendors/marketers. Only
information associated with the renowned organizations are accessible whereas petty vendors/marketers
are not approachable to the user and vice versa. Therefore, loss incurred by both parties.

The proposed system is intended to meet the expectations of the users facing the above mentioned issues
with the existing system. The scope of this system is to enhance the efficiency of information
accessibility.

The analysis phase is structured by mentioning the feasibility of the project. A feasibility study aims to
objectively and rationally uncover the strengths and weaknesses of an existing business or proposed
venture, opportunities and threats present in the environment, the resources required to carry through,
and ultimately the prospects for success. In its simplest terms, the two criteria to judge feasibility are cost
required and value to be attained.

The design of the project is made by considering various UML diagrams such as use-case, class,
sequence, collaboration, ER diagrams. This helps us to analyze the structure of the project and
functionality as well. The data flow diagrams are used to analyze the sequence of flow of the data.

The results of the project are obtained by implementing various methodologies on it. The java IDE
is used in the development of the front end of the project. For the backend, the DB2 database is used with
the assist of xml.

3
 SHOPEE IN STYLE

The testing is performed with various test cases such as unit testing, integration testing, black box
testing, white box testing, positive and negative testing. The modifications are made on the project based
on the results obtained from the test cases.

4
 SHOPEE IN STYLE

LITERATURE SURVEY

5
 SHOPEE IN STYLE

2. LITERATURE SURVEY

2.1 INTRODUCTION:
Building a platform for buyer and seller who are situated at different locations and connecting them
through Internet. This provides easy accessing of data and provides communication channel between
users.
 Reliability: The project performs intended function with required precision; hence this project is very
reliable.
 Feasibility: The project maintenance is very easy and modifications can be made in the existing system in
future. The project can improve the communication between the buyer and seller.
 Online Processing: The online processing of the project is simple and suitable validation is provided for
the easy and correct access of users.
 Security: Security measures are taken to avoid mishandling of data, Password restrictions are provided
to enter into database. A correct password only will access to the database.

2.1.1 OVERVIEW OF CITY CLASSIFIEDS:

SHOPPE IN STYLE was developed using MYSQL, and scripted using Java, under windows operating
system. It is simply a service provider for online advertising user like any other advertising services
available in the market. The user will have his own credentials which will help the admin for unique
identity. This will work as the simplest way to buy or sell products under different categories.

Review of Literature

The process of the research into complex data basically concerned with the revealing of the hidden
patterns.
Alur, et al (2003).Software design patterns are pre-defined solutions to recurring problems in
software engineering. Although many patterns exist which can be applied to a wide range of platforms,
the Sun Java Center has also published a set of patterns relating specifically to J2EE development project.
Winn and Calder (2002); explain, adherence to software design patterns can significantly aid the process
of development by providing expertly verified solutions and accepted standards for good practice.

6
 SHOPEE IN STYLE

2.2 EXISTING SYSTEM:

 Time consuming
 Expensive
 Need an agent
 We have to out for that

2.3 DISADVANTAGES OF EXISTING SYSTEM:

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

2.4 PROPOSED SYSTEM:

To debug the existing system, remove procedures those cause data redundancy, make navigational
sequence proper. To provide information about audits on different level and also to reflect the current
work status depending on organization/auditor or date. Required to build strong password mechanism.

2.5 SURVEY CONCLUSION:

 Shopee in style is a different experience.
 This will allow customers to place order without even visiting the shop.
 Being able to buy anytime, anyplace.
 It will be more enjoyable and easier than real world shopping.

7
 SHOPEE IN STYLE

ANALYSIS

8
 SHOPEE IN STYLE

3. SYSTEM ANALYSIS

3.1 INTRODUCTION:

3.1.1 Economic Feasibility

Economic feasibility attempts to weigh the costs of developing and implementing a new system,
against the benefits that would accrue from having the new system in place. This feasibility study gives
the top management the economic justification for the new system. A simple economic analysis which
gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this
proves to be a useful point of reference to compare actual costs as the project progresses. There could be
various types of intangible benefits on account of automation. These could include increased customer
satisfaction, improvement in product quality better decision making timeliness of information, expediting
activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of
information, better employee morale.

3.1.2 Operational Feasibility

Proposed project is beneficial only if it can be turned into information systems that will meet the
organizations operating requirements. Simply stated, this test of feasibility asks if the system will work
when it is developed and installed. Are there major barriers to Implementation? Here are questions that
will help test the operational feasibility of a project: Is there sufficient support for the project from
management from users? If the current system is well liked and used to the extent that persons will not be
able to see reasons for change, there may be resistance. Are the current business methods acceptable to
the user? If they are not, Users may welcome a change that will bring about a more operational and useful
systems. Have the user been involved in the planning and development of the project? Early involvement
reduces the chances of resistance to the system and in general and increases the likelihood of successful
project. Since the proposed system was to help reduce the hardships encountered. In the existing manual
system, the new system was considered to be operational feasible.

9
 SHOPEE IN STYLE

3.1.3 Technical Feasibility

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point
in time, not too many detailed design of the system, making it difficult to access issues like performance,
costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be
considered while doing a technical analysis. Understand the different technologies involved in the
proposed system before commencing the project we have to be very clear about what are the technologies
that are to be required for the development of the new system. Find out whether the organization currently
possesses the required technologies.

3.2 SOFTWARE REQUIREMENT SPECIFICATION:

3.2.1 USER REQUIREMENTS:

The user needs to have an Integrated Development Environment (IDE) that can be used to implement the
programming required for the application. The user also needs to meet the basic hardware and software
requirements to develop the application.

3.2.2 SOFTWARE REQUIREMENTS:

Operating System : Any Windows family or Linux/Solaris

User Interface : HTML, CSS

Client-side Scripting : JavaScript

Programming Language : Java

Web Applications : JDBC, JSP

Database : MySQL

Server Deployment : Apache Tomcat Server (7.0 version& above)

IDE/Workbench : Eclipse

10
 SHOPEE IN STYLE

3.2.3 HARDWARE REQUIREMENTS:

Processor : Intel CORE Pentium& above

Hard Disk : 120GB

RAM : 2GB

3.3 CONTENT DIAGRAM OF PROJECT:

11
 SHOPEE IN STYLE

3.4 ALGORITHAMS AND FLOWCHARTS:

ALGORITHM:
Algorithm is the first step of the solution, after the analysis of problem, programmer writes the
algorithm of the problem.
FLOW CHART:
A flow chart is a type of diagram that represents an algorithm, workflow or process, showing the steps in
various kinds of boxes connecting them with arrows. The diagrammatic representation illustrates a
solution model to a given problem.
3.5 CONCLUSION:
The main objective of the application is to help Computer Science students understands the basics of Java,
JavaScript and HTML. The users can post and view any number of ads by registering. The user is verified
with the details during registration. Once he is verified, user is given the right to post an ad with complete
details without any scams or illegal registrations for the service he is ready to sell.

12
 SHOPEE IN STYLE

DESIGN

13
 SHOPEE IN STYLE

4. DESIGN

4.1 INTRODUCTION:
Database Design:
Databases are normally implemented by using a package called a Data Base Management System
(DBMS). Each particular DBMS has unique characteristics, and so such, general techniques for the design
of database are limited. One of the most useful methods of analysing the data required by the system for
the data dictionary has developed from research into relational database, particularly the work of E F
Codd. This method of analysing data is called “Normalization”. Un Normalized data are converted into
normalized data by three stages. Each stage has a procedure to follow.
Normalization:
The first stage is normalization is to reduce the data to its first normal form, by removing repeating items
showing them as separate records but including in them the key fields of the original record.
The next stage of reduction to the second normal form is to check that the record, which one is
first normal form, all the items in each record are entirely dependent on the key of the record. If a data
item is not dependent on the key of the record, but on the other data item, then it is removed with its key
to form another record. This is done until each record contains data items, which are entirely dependent
on the key of their record.
The final stage of the analysis, the reduction of third normal form involves examining each record,
which one is in second normal form to see whether any items are mutually dependent. If there are any
item there are removed to a separate record leaving one of the items behind in the original record and
using that as the key in the newly created record.

14
 SHOPEE IN STYLE

TABLES:
1.Administrator Login table

Key Name Data type Length Nullable

Primary Username Varchar 50 No

Password Varchar 50 No

Table 4.1: Admin login table

2. Admin Table

Key Name Data Type Size Nullable

Primary Aid Varchar 25 No

name Varchar 25 No

phone Varchar 25 No

Address Varchar 60 No

Mail id Varchar 25 No

Table 4.2: File Information Table

15
 SHOPEE IN STYLE

3.User details table

Key Name Datatype Length Nullable

First name Varchar 25 No

Last name Varchar 25 No

Primary Contact Varchar 10 No

Address Varchar 60 No

Gender Varchar 10 No

State Varchar 25 No

City Varchar 25 N0

Primary Email id Varchar 25 No

Password Varchar 25 No

Date of birth Varchar 30 No

Ques Varchar 25 No

Table 4.3: User details table

16
 SHOPEE IN STYLE

4.User Login table

Key Name Data type Length Nullable

Primary Emailid Varchar 25 No

Password Varchar 25 No

Ques Varchar 25 No

Ans Varchar 25 No

Table 4.4: User login table

5.Approval table

Key Name Datatype Length Nullable

Msg Varchar 100 No

Primary Email id Varchar 25 No

Date Varchar 25 No

Status Varchar 25 No

Table 4.5: Approval table

17
 SHOPEE IN STYLE

4.2 Data Flow diagram:

A Data Flow Diagram (DFD) is a graphical technique that depicts information flow and transforms that
are applied as data move to represent a system or software at any level of abstraction. Data Flow Diagram
may be partitioned into levels that represent increasing information flow and functional detail. The
notation used to create a DFD is illustrated in the given as:

1. Process: A Process transforms incoming data flow(s) into outgoing data flow(s).
2. External Entity: An External Entity is a system element (hardware a person) that produces
information for transformation by the software or received information produced by the software.
3. Data Store: A repository of data for the use of one or more process.
4. Arrow (  ):A data item or collection of data items, the arrowhead indicates the direction of data
flow.

Data Flow

Processing Node

Source or Destination

Data Store

18
 SHOPEE IN STYLE

DFD at top level:

Figure 4.7: Data Flow Diagram

Browse
Catalogue Item Details
*

Product Info

2
Product ID Customer
Register
Customer
Profile
Details
Public *
Product Qty
D1 Product Inventory
D2 Customers
9 Username and
Password
Username+passw- Login
ord
*

Customers
Product-ID

3
Product ID
Add product
to
Cart
*

Cart Item
Cart Item ID
5
Shopping Customer
D3 Cart Items Check-out Customer Order D4
Cart Orders
Order
*
Cart Item
New Credit Card Customer Order
4 Credit Card
Credit Card
Credit Card
View/Amend Details 8
Cart
Issue Order
* Credit
D5 to Shipping
Cards
Agent
Credit Card *
Status 7
Issue Shipping
Credit CC for CopyOfCustomers Request
Card Validation
Co *

Credit Card Shipping

Agent

19
 SHOPEE IN STYLE

4.3 UNIFIED MODELING LANGUAGE DIAGRAMS

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the
field of software engineering that is intended to provide a standard way to visualize the design of a system.
UML was originally motivated by the desire to standardize the disparate notational systems and
approaches to software design developed by Grady Booch, Ivar Jacobson and James
Rumbaugh at Rational Software in 1994–95, with further development led by them through 1996.
UML 2 has many types of diagrams, which are divided into two categories. Some types
represent structural information, and the rest represent general types of behaviour, including a few that
represent different aspects of interactions. These diagrams can be categorized hierarchically as shown in
the following class diagram.

These diagrams may all contain comments or notes explaining usage, constraint, or intent.

Interaction Diagrams
Interaction diagrams, a subset of behaviour diagrams, emphasize the flow of control and data among the
things in the system being modeled. For example, the sequence diagram shows how objects communicate
with each other in terms of a sequence of messages.

20
 SHOPEE IN STYLE

Use Case Diagram

A use case diagram at its simplest is a representation of a user's interaction with the system that shows the
relationship between the user and the different use cases in which the user is involved. A use case diagram
can identify the different types of users of a system and the different use cases and will often be
accompanied by other types of diagrams as well.

Figure 4.2: Use Case Diagrams

21
 SHOPEE IN STYLE

Sequence diagram:
A sequence diagram is an interaction diagram that shows how objects operate with one another and in
what order. It is a construct of a message sequence chart.
A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the objects needed
to carry out the functionality of the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in
which they occur. This allows the specification of simple runtime scenarios in a graphica

fig4.3: sequence diagrams

CUSTOMER CATEGORY CATEGORIES

View Categories Request

Search Categories

Categories List

Result

Fig: searching categories

22
 SHOPEE IN STYLE

CUSTOMER PRODUCT PRODUCTS

MANAGER
View Products Request

Search Products

Products List

Result

Fig: searching product list

23
 SHOPEE IN STYLE

USER CUSTOMER MANAGER CUSTOMERS

Personal, Address & credential details

Register User

Customer Registration Status

Result

Fig: user registration

24
 SHOPEE IN STYLE

Product Shopping Payment Orders

Customer Login Products
Cart Gateway
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: product purchase process

25
 SHOPEE IN STYLE

Login Screen
Admin Order Manager Orders

Login Details

Order Details
Manage Orders

Status

Result

Result

Fig: order management

ER Diagram
An entity–relationship model (ER model) describes inter-related things of interest in a specific domain of
knowledge. An ER model is composed of entity types (which classify the things of interest) and specifies
relationships that can exist between instances of those entity types.
In software engineering an ER model is commonly formed to represent things that a business
needs to remember in order to perform business processes. Consequently, the ER model becomes an
abstract data model that defines a data or information structure that can be implemented in a database,
typically a relational database.

26
 SHOPEE IN STYLE

ER modelers’ show super and subtype entities connected by generalization-specialization

relationships, and an ER model can be used also in the specification of domain-specific ontology.

Figure 4.9: ER Diagram for User

Figure 4.9: ER Diagram for User

27
 SHOPEE IN STYLE

4.4 MODULE DESIGN AND ORGANIZATION:

User
The activities that are carried out in this module are related to software’s installation viewing in their
systems, Repairs forwarding to Administrator, and updating, their profiles. Users can also view his profile
to know the details. He can join the conference to communicate with people in the Organization.User can
get organization Information and also communicate with Administrator Those activities that are carried
out in this module are related viewing The Installed Hardware and Software's of a computers and its
Associated Peripherals.

Administrator
The activities that are carried out in this module are related to the maintenance of master records such as
Managers, Department master and Employee master for the entire organization. This module provides for
performing addition, deletion, updating and viewing the records in the master tables. This module also
provides viewing profiles of branches, departments and user’s.
The master entries can only be accessed by the administrator of the organization. This module also
provides viewing the software and hardware. Of it resources in Organization. Features of administrator
module:

• Login system
• Add/delete user’s Profiles
• Response for organizations
• View system peripherals
• Viewing software installations
• Solving repairs in Organization
• View reports
• Logout

28
 SHOPEE IN STYLE

4.5 CONCLUSION:
The conclusion has been drawn on the basis of the findings, and the recommendations that have
been made to enable retailers, IT support and researchers to devise strategies to ensure the ultimate
objective of customer loyalty is achieved. The findings, recommendations and future scope of research
are given as follows.

29
 SHOPEE IN STYLE

IMPLEMENTATION
AND
RESULTS

30
 SHOPEE IN STYLE

5. IMPLEMENTATION AND RESULTS

5.1 INTRODUCTION:
The Implementation and Results show the overall outcome of the application with the help of different
output screenshots and explanation.
Initially the language was called as “oak” but it was renamed as “Java” in
1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture
neutral) language that could be used to create software to be embedded in various consumer electronic
devices.
 Java is a programmer’s language.
 Java is cohesive and consistent.
 Except for those constraints imposed by the Internet environment, Java gives the programmer,
full control.
 Finally, Java is to Internet programming where C was to system programming.

Importance of java to the Internet:

Java has had a profound effect on the Internet. This is because, Java expands the Universe of objects that
can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the
Server and the Personal computer. They are: Passive information and Dynamic active programs. The
Dynamic, Self-executing programs cause serious problems in the areas of Security and probability.
However, Java addresses those concerns and by doing so, has opened the door to an exciting new form of
program called the Applet.

Java can be used to create two types of program, Applications and Applets: An application is a
program that runs on our Computer under the operating system of that computer. Java’s ability to create
Applets makes it important. An Applet is an application designed to be transmitted over the Internet and
executed by a Java –compatible web browser. An Applet is actually a tiny Java program, dynamically
downloaded across the network, just like an image.

31
 SHOPEE IN STYLE

5.2 EXPLANATIONS OF KEY FUNCTIONS:

We make the use of Java APIs to build the web application and user interfaces. The server or cloud tier
shall involve the connectivity and interfacing of the web application with database directly.
We use HTML in the implementation of GUI to make users understand
easily and this HTML provides tags (special codes) to make the document look attractive. HTML tags are
not case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the presentation of the
document. Anything that is not a tag is part of the document itself.

Basic HTML Tags:

<BODY>…</BODY> Contains all tags and text in the HTML document

<CENTER>...</CENTER> Creates text
<DD>…</DD> Definition of a term
<DL>...</DL> Creates definition list
<FONT>…</FONT> Formats text with a particular font
<FORM>...</FORM> Encloses a fill-out form
<FRAME>...</FRAME> Defines a particular frame in a set of frames
<H#>…</H#> Creates headings of different levels( 1 – 6 )
<HEAD>...</HEAD> Contains tags that specify information about a document
<HR>...</HR> Creates a horizontal rule
<HTML>…</HTML> Contains all other HTML tags
<META>...</META> Provides meta-information about a document
<SCRIPT>…</SCRIPT> Contains client-side or server-side script
<TABLE>…</TABLE> Creates a table
<TD>…</TD> Indicates table data in a table
<TR>…</TR> Designates a table row
<TH>…</TH> Creates a heading in a table
<TD>…</TD> Indicates table data in a table
<TR>…</TR> Designates a table row
<TH>…</TH> Creates a heading in a table

32
 SHOPEE IN STYLE

METHODS OF IMPLEMENTATION:
Implementation is the process of having systems personnel check out and put new equipment into use,
train users, install the new application 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 system’s 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. It 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. It includes assessment of development methods and tools.

33
 SHOPEE IN STYLE

Java Virtual Machine (JVM):

Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element
of the Java technology. The virtual machine can be embedded within a web browser or an operating
system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process,
a class loader is invoked and does byte code verification makes sure that the code that’s has been generated
by the compiler will not corrupt the machine that it’s loaded on. Byte code verification takes place at the
end of the compilation process to make sure that is all accurate and correct. So byte code verification is
integral to the compiling and executing of Java code.

Overall Description

Java Source Java byte code JVM

Java .Class

5.3.1.1 JVM Architecture

Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box indicates that the
Java source code is located in a. Java file that is processed with a Java compiler called java-C. The Java
compiler produces a file called a. class file, which contains the byte code. The .Class file is then loaded
across the network or loaded locally on your machine into the execution environment is the Java virtual
machine, which interprets and executes the byte code.

Java Architecture:

Java architecture provides a portable, robust, high performing environment for development. Java
provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted
on each platform by the run-time environment. Java is a dynamic system, able to load code when needed
from a machine in the same room or across the planet.

34
 SHOPEE IN STYLE

Compilation of code:

When you compile the code, the Java compiler creates machine code (called byte code) for a
hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute the byte code.
The JVM is created for overcoming the issue of portability. The code is written and compiled for one
machine and interpreted on all machines. This machine is called Java Virtual Machine.

5.3.1.2:
Compilation of Code

Compiling and interpreting Java Source Code:

During run-time the Java interpreter tricks the byte code file into thinking that it is running on a Java
Virtual Machine. In reality this could be an Intel Pentium Windows 95 or SunSARC station running
Solaris or Apple Macintosh running system and all could receive code from any computer through Internet
and run the Applets.

Simple:

Java was designed to be easy for the Professional programmer to learn and to use effectively. If you
are an experienced C++ programmer, learning Java will be even easier. Because Java inherits the C/C++
syntax and many of the object oriented features of C++. Most of the confusing concepts from C++ are
either left out of Java or implemented in a cleaner, more approachable manner. In Java there are a small
number of clearly defined ways to accomplish a given task.

35
 SHOPEE IN STYLE

Object-Oriented:

Java was not designed to be source-code compatible with any other language. This allowed the Java team
the freedom to design with a blank slate. One outcome of this was a clean usable, pragmatic approach to
objects. The object model in Java is simple and easy to extend, while simple types, such as integers, are
kept as high-performance non-objects

Robust:

The multi-platform environment of the Web places extraordinary demands on a program, because the
program must execute reliably in a variety of systems. The ability to create robust programs was given a
high priority in the design of Java. Java is strictly typed language; it checks your code at compile time and
run time.

Java virtually eliminates the problems of memory management and de-allocation, which is
completely automatic. In a well-written Java program, all run time errors can –and should –be managed
by your program.

Java Database Connectivity

What Is JDBC?
JDBC is a Java API for executing SQL statements. (As a point of interest, JDBC is a trademarked
name and is not an acronym; nevertheless, JDBC is often thought of as standing for Java Database
Connectivity. It consists of a set of classes and interfaces written in the Java programming language. JDBC
provides a standard API for tool/database developers and makes it possible to write database applications
using a pure Java API.
Using JDBC, it is easy to send SQL statements to virtually any relational database. One can write a
single program using the JDBC API, and the program will be able to send SQL statements to the
appropriate database. The combinations of Java and JDBC lets a programmer write it once and run it
anywhere.
What Does JDBC Do?

Simply put, JDBC makes it possible to do three things:

 Establish a connection with a database

36
 SHOPEE IN STYLE

 Send SQL statements

 Process the results.

Connection:
A connection object represents a connection with a database. A connection session includes the SQL
statements that are executed and the results that are returned over the connection. A single application
can have one or more connections with a single database, or it can have connections with many
different databases.

Opening a Connection:
The standard way to establish a connection with a database is to call the method Driver Manager .get
Connection. This method takes a string containing a URL. The Driver Manager class, referred to a the
JDBC management layer, attempts to locate a driver than can connect to the database represented
Driver classes, and when the method get Connection is called, it checks with each driver in the list
until it finds one that can connect uses this URL to actually establish the connection.
<Sub protocol> - usually the driver or the database connectivity mechanism, which may be
supported by one or more drivers. A prominent example of a sub protocol name is “oracle”, which has
been reserved for URLs that specify “thin”-style data source names.

<Sub name> - a way to identify the database. The sub names can vary, depending on the sub
protocol, and it can have a sub name with any internal syntax the driver writer chooses. The point of a
sub name is to give enough information to locate the database.

Sending Statement:
Once a connection is established, it is used to pass SQL statements to its underlying database. JDBC
does not put any restrictions on the kinds of SQL statements that can be sent; this provides a great deal
of flexibility, allowing the use of database-specific statements or even non-SQL statements. It requires,
however, that the user be responsible for making sure that the underlying database can process the
SQL statements being sent and suffer the consequences if it cannot.

37
 SHOPEE IN STYLE

Driver Manager:
The Driver Manager class is the management layer of JDBC, working between the user and the drivers.
It keeps track of the drivers that are available and handles establishing a connection between a database
and the appropriate driver. It addition, the driver manager class attends to things like driver login time
limits and the printing of log and tracing messages. The only method in this class that a general
programmer needs to use directly is Driver Manager get Connection. As its name implies, this method
establishes a connection to a database.
A JAVA2 Platform, Enterprise Edition Deployment

38
 SHOPEE IN STYLE

MySQL:
Introduction to MySQL:
Any programming environment used to create containers, to manage human data, in the conceptualization
as a Data Management System. Traditionally, the block of human data being managed is called a
Database. Hence, in very simple terms, these programming environments can the conceptualized as
Database Management Systems, in short DBM systems.
All Databases Management Systems allow users to create containers for data stories and management.
These containers are called ‘cells’. The minimum information that has to be given for a suitable container
to be constructed, which can hold free from human data is,
1. The cell name
2. The cell length
Another name that programming environments use for a ‘Cell’ is ‘Field’. These can the
conceptualized as follows.
BASIC DATABASE CONCEPTS:
A database is a corporate collection of data with some inherent meaning, designed, built and populated
with data for a specific purpose. A database stores data that is useful to us. This data is only a part of the
entire data available in the world around us.
To be able to successfully design and maintain databases we have to do the following:
Identify which part of the world’s data is of interest to us. Identify what specific objects in that part of the
world’s data are of interest to us. Identify a relationship between the objects.
Hence the objects, their attributes and the relationship between them that are of interest to us are
still owed in the database that is designed, built and populated with data for a specific purpose.

Characteristics of a Database Management System:

 It represents a complex relationship between data.

 Keeps a tight control of debtor redundancy.

 Enforces user-defined rules to ensure integrity of table data.

 Has a centralized data dictionary for the storage of information pertaining

 to data and its manipulation.

 Ensures that data can be shared across applications.

39
 SHOPEE IN STYLE

Relational Database Management:

A relational database management system uses only its relational capabilities to manage the information
stored in its databases.
Information Representation:
All information stored in a relational database is represented only by data item values, which are stored
in the tables that make up the database. Associations between data items are not logically represented in
any other way, such as the use of pointers from one table to the other.
Logical Accessibility:
Every data item value stored in relational database is accessible by stating the nature of the table it is
stored in, the name of the column under which it is stored and the value of the primary key that defines
the row in which it is stored.
Representation of Null Values:
The database management system has a consistent method for representing null values. For example, null
values for numeric data must be distinct from zero or any other numeric and for the character data it must
be different from a string of blanks or any other character value.
Data Language:
The relational database management system may support many types of languages for describing data
and accessing the database. However, there must be at least one language that uses ordinary character
strings to support the definition of data, the definition of views, the manipulation of data, constraints on
data integrity, information concerning authorization and the boundaries for recovery of units.
View Updatability:
Any view that can be defined using combination of basic tables, that are theoretically updateable, these
capital of being updated by the relational database management system.
Insert Update and Delete:
Any operand that describes the results of a single retrieval operation is capable of being applied to an
insert update or delete operation as well.
Java Server Pages (JSP)
Java server Pages is a simple, yet powerful technology for creating and maintaining dynamic-content web
pages. Based the Java programming language, Java Server Pages offers proven portability, open standards,
and a mature on re-usable component model .The Java Server Pages architecture enables the separation
40
 SHOPEE IN STYLE

of content generation from content presentation. This separation not eases maintenance headaches; it also
allows web team members to focus on their areas of expertise. Now, web page designer can concentrate
on layout, and web application designers on programming, with minimal concern about impacting ech
other’s work.

Features of JSP

Portability:

Java Server Pages files can be run on any web server or web-enabled application server that provides
support for them. Dubbed the JSP engine, this support involves recognition, translation, and management
of the Java Server Page lifecycle and its interaction components.

Components:

It was mentioned earlier that the Java Server Pages architecture can include reusable Java
components. The architecture also allows for the embedding of a scripting language directly into the Java
Server Pages file. The components current supported include Java Beans, and Servlets.

Processing:

A Java Server Pages file is essentially an HTML document with JSP scripting or tags. The Java Server
Pages file has a JSP extension to the server as a Java Server Pages file. Before the page is served, the Java
Server Pages syntax is parsed and processed into a Servlet on the server side. The Servlet that is generated
outputs real content in straight HTML for responding to the client.

41
 SHOPEE IN STYLE

Access Models:

A Java Server Pages file may be accessed in at least two different ways: A client request comes
directly into a Java Server Page.

Bea
n
Request

Browser
Response

5.3.1.5: Access Model

In this scenario, suppose the page accessed reusable Java Bean components that perform particular
well-defined computations like accessing a database. The result of the Bean’s computations, called result
sets is stored within the Bean as properties. The page uses such Beans to generate dynamic content and
present it back to the client. A request comes through a servlet.

5.3.1 FORMS:
User
The user will now login with the following credentials:
 Email id: a@a.a
 Password:

Admin
The admin will now login with the following credentials:
 Email id: admin
 Password: admin

42
 SHOPEE IN STYLE

5.3.2 SAMPLE CODE

Code for Admin Login

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"

pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="keywords" content="" />
<meta name="description" content="" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>shope in style</title>
<link href="style.css" rel="stylesheet" type="text/css" media="screen" />
<script type="text/javascript" src="jquery/jquery-1.4.2.min.js"></script>
<script type="text/javascript" src="jquery/jquery.gallerax-0.2.js"></script>
<style type="text/css">
@import "gallery.css";
</style>
</head>

<body>

<div id="wrapper">
<div id="header">
<div id="logo">
<h1><a href="#"><strong>ADMIN LOGIN</strong></a></h1>

</div>
</div>
<!-- end #header -->
<div id="menu">
<ul>
<li class="current_page_item"><a href="Home.jsp">Home</a></li>
<li><a href="contactus.html">Contact</a></li>
<li><a href="Photos.html">Photos</a></li>
<li><a href="About.html">About</a></li>

</ul>
</div>
<!-- end #menu -->
<div id="page">
43
 SHOPEE IN STYLE

<div id="page-bgtop">
<div id="page-bgbtm">
<div id="content">
<div id="gallery-wrapper">
<div id="gallery"> <img class="output"
src="images/download.jpg" alt="" />
<div id="thumbnail-bg">
<ul class="thumbnails">
<li><img class="active"
src="images/download.jpg" title="Accesories" alt="" width="604" height="375"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/hd.jpg"
title="Headphones" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/printer.png"
title="printer" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/monitor.jpg"
title="Monitor" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
</ul>
</div>
<br class="clear" />
</div>
<script type="text/javascript">

$('#gallery').gallerax({
outputSelector: '.output',
// Output selector
thumbnailsSelector: '.thumbnails li img',
// Thumbnails selector
captionSelector: '.caption'
// Caption selector
});

</script>
<!-- end -->
</div>
<div class="post">

44
 SHOPEE IN STYLE

<div style="clear: both;">&nbsp;</div>

<div class="entry">

</div>
<div id="Hright">

</div>
</div>

<div style="clear: both;">&nbsp;</div>

</div>
<!-- end #content -->
<div id="sidebar">
<ul>
<li>
</ul>
</div>

<div>
<form method="post"
action="AdminLogin">
<table>
<tr>
<td>USERNAME</td><td><input type="text" name="username" id="IES"/></td>
</tr>
<tr>
<td>PASSWORD</td><td><input type="password" name="pwd" /></td>
</tr>
<tr>
<td> </td><td><input type="submit" value="SIGN IN" /></td>
</tr>
</table>
</form>

</body>
</html>

45
 SHOPEE IN STYLE

Code for login page:

<!-- end #header -->
<div id="menu">
<ul>
<li class="current_page_item"><a href="#">Home</a></li>
<li><a href="#">Contact</a></li>
<li><a href="#">Photos</a></li>
<li><a href="#">About</a></li>
<li><a href="http://localhost:8080/shoppeinstyle/Admin.jsp">Admin
Login</a></li>

</ul>
</div>
<!-- end #menu -->
<div id="page">
<div id="page-bgtop">
<div id="page-bgbtm">
<div id="content">
<div id="gallery-wrapper">
<div id="gallery"> <img class="output"
src="images/download.jpg" alt="" />
<div id="thumbnail-bg">
<ul class="thumbnails">
<li><img class="active"
src="images/download.jpg" title="Accesories" alt="" width="604" height="375"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/hd.jpg"
title="Headphones" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/printer.png"
title="printer" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
<li><img src="images/monitor.jpg"
title="Monitor" alt="" width="100" height="75"
onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70" /></li>
</ul>
</div>
<br class="clear" />
</div>
<script type="text/javascript">

46
 SHOPEE IN STYLE

$('#gallery').gallerax({
outputSelector: '.output',
// Output selector
thumbnailsSelector: '.thumbnails li img',
// Thumbnails selector
captionSelector: '.caption'
// Caption selector
});

</script>
<!-- end -->
</div>
<div class="post">

<div style="clear: both;">&nbsp;</div>

<div class="entry">

</div>
<div id="Hright">

</div>
</div>

<div style="clear: both;">&nbsp;</div>

</div>
<!-- end #content -->
<div id="sidebar">
<ul>
<li>

<div>
<form method="post"
action="Log">
<table>
<tr>
<td>USERNAME</td><td><input type="text" name="username" id="IES"/></td>
</tr>
<tr>
<td>PASSWORD</td><td><input type="password" name="pwd" /></td>
</tr>
<tr>
47
 SHOPEE IN STYLE

<td> </td><td><input type="submit" value="SIGN IN" /></td>

</tr>
</table>
<table>
<tr>
<td>
<li><a href="registration.jsp"><img src="s.jpg" title="SIGN UP" alt="" width="80"
height="65" onmouseover="this.style.opacity=1;this.filters.alpha.opacity=100"
onmouseout="this.style.opacity=0.4;this.filters.alpha.opacity=70"/></a></li></td></tr></table>

</form>
</div>

<div style="clear: both;">&nbsp;</div>

</li>

<li>
<h2>Computer accessories</h2>
<ul>
<li><a href="#">Monitor</a></li>
<li><a href="#">Printer</a></li>
<li><a href="#">Scanner</a></li>
<li><a href="#">Keyboard</a></li>
<li><a href="#">Mouse</a></li>
<li><a href="#">Joystick</a></li>
<li><a href="#">CPU</a></li>
<li><a href="#">PenDrive</a></li>
<li><a href="#">Headphones</a></li>
<li><a href="#">Web CAm</a></li>
</ul>
</li>

</ul>
</div>
<!-- end #sidebar -->
<div style="clear: both;">&nbsp;</div>
</div>
</div>
</div>
<!-- end #page -->
</div>
<div id="footer">

48
 SHOPEE IN STYLE

</div>
<!-- end #footer -->

</body>
</html>

5.3.3 OUTPUTS
Figure 7.1: Home Page

49
 SHOPEE IN STYLE

Figure 7.2: User Register Page

This page is used to register new users. The users have to enter his/her details in the fields mentioned in
the page and if he is new, then the user gets his credentials for logging in to access the profile page
through which he can order his order.

50
 SHOPEE IN STYLE

Figure 7.3:Admin Login Page

This page is used for the login of Admin.

51
 SHOPEE IN STYLE

RESULT ANALYSIS:

The analysis of the results are based on the expected and obtained outputs can be stated to be valid
according to the requirements of the application and all the objectives that are necessary for the
functionality of the application are achieved.

5.4 CONCLUSION:

Based on the obtained outputs, we check the requirements and comparing with the result, the
results are satisfactory.so, we conclude that the application is functioning properly and is as per
expected and objective of the project.
-

52
 SHOPEE IN STYLE

TESTING
AND
VALIDATION

53
 SHOPEE IN STYLE

6. TESTING AND VALIDATION

6.1 INTRODUCTION:

Software Testing Techniques:

Software testing is a critical element of software quality assurance and represents the ultimate review of

specification, designing and coding

In general, software engineers distinguish software faults from software failures. In case of a

failure, the software does not do what the user expects. A fault is a programming error that may or may

not actually manifest as a failure. A fault can also be described as an error in the correctness of the

semantic of a computer program. A fault will become a failure if the exact computation conditions are

met, one of them being that the faulty portion of computer software executes on the CPU. A fault can

also turn into a failure when the software is ported to a different hardware platform or a different

compiler, or when the software gets extended. Software testing is the technical investigation of the

product under test to provide stakeholders with quality related information.

Software testing may be viewed as a sub-field of Software Quality Assurance but typically exists
independently (and there may be no SQA areas in some companies). In SQA, software process specialists
and auditors take a broader view on software and its development. They examine and change the software
engineering process itself to reduce the amount of faults that end up in the code or deliver faster.

Regardless of the methods used or level of formality involved the desired result of testing is a level
of confidence in the software so that the organization is confident that the software has an acceptable
defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade
video game designed to simulate flying an airplane would presumably have a much higher tolerance for
defects than software used to control an actual airliner.

54
 SHOPEE IN STYLE

A problem with software testing is that the number of defects in a software product can be very
large, and the number of configurations of the product larger still. Bugs that occur infrequently are difficult
to find in testing. A rule of thumb is that a system that is expected to function without faults for a certain
length of time must have already been tested for at least that length of time. This has severe consequences
for projects to write long-lived reliable software.
A common practice of software testing is that it is performed by an independent group of testers
after the functionality is developed but before it is shipped to the customer. This practice often results in
the testing phase being used as project buffer to compensate for project delays. Another practice is to
start software testing at the same moment the project starts and it is a continuous process until the
project finishes.
Another common practice is for test suites to be developed during technical support escalation
procedures. Such tests are then maintained in regression testing suites to ensure that future updates to the
software don't repeat any of the known mistakes. It is commonly believed that the earlier a defect is found
the cheaper it is to fix it.
Unit tests are maintained along with the rest of the software source code and generally integrated
into the build process (with inherently interactive tests being relegated to a partially manual build
acceptance process).

The software, tools, samples of data input and output, and configurations are all referred to
collectively as a test harness.

6.2 DESIGN OF TEST CASES AND SCENARIOS:

A test case is a software testing document, which consists of event, action, input, output, expected result
and actual result. Clinically defined (IEEE 829-1998) a test case is an input and an expected result. This
can be as pragmatic as 'for condition x your derived result is y', whereas other test cases described in more
detail the input scenario and what results might be expected. It can occasionally be a series of steps (but
often steps are contained in a separate test procedure that can be exercised against multiple test cases, as
a matter of economy) but with one expected result or expected outcome.
The optional fields are a test case ID, test step or order of execution number, related requirement(s),
depth, test category, author, and check boxes for whether the test is automatable and has been automated.

55
 SHOPEE IN STYLE

Larger test cases may also contain prerequisite states or steps, and descriptions. A test case should
also contain a place for the actual result. These steps can be stored in a word processor document,
spreadsheet, database or other common repository.

The term test script is the combination of a test case, test procedure and test data. Initially the term
was derived from the byproduct of work created by automated regression test tools. Today, test scripts
can be manual, automated or a combination of both.

The most common term for a collection of test cases is a test suite. The test suite often also contains
more detailed instructions or goals for each collection of test cases. It definitely contains a section where
the tester identifies the system configuration used during testing. A group of test cases may also contain
prerequisite states or steps, and descriptions of the following tests.

Collections of test cases are sometimes incorrectly termed a test plan. They might correctly be
called a test specification. If sequence is specified, it can be called a test script, scenario or procedure

TEST CASES

Test Cases are of two types:

1. Positive Test Case
2. Negative Test Case

6.2.1 Guide Lines for Test Cases

Test cases should have:

1. Test Case ID
2. Test Case Name
3. Test Case Description
4. Actual Value
5. Expected Value
6. Result

56
 SHOPEE IN STYLE

6.2.2 Implementation of Test Cases

1.GUI Test Case

 Total no of features that need to be check

 Look & Feel
 Look for Default values if at all any (date & Time, if at all any require)
 Look for spell check

Test Test Case Test Case Expected Actual

Result
Case ID Name Description value value
Tc #1 Check for all the The screen The result Pass
Features in the must contains we get on
screen features checking
Tc #2 GUI Check for the The Alignment The result Pass
alignment of the should be in we get on
objects as per the proper way checking
validations
Table 6.1: Example for GUI Test Cases

2. Positive Test Case

 The positive flow of the functionality must be considered
 Valid inputs must be used for testing
Must have the positive perception to verify whether the requirements are justified.

Test Test Case Test Case Actual

Expected value Result
Case ID Name Description value
Tc #1 Positive Test Check for The available The Jobs Pass
Case the jobs Jobs in the are
available organization Must displayed
be displayed
Table 6.2: Example for Positive Test Cases

3.Unit Test Case for Login Page

57
 SHOPEE IN STYLE

Test Case Test Case Test Steps Result

Name Description Input Expected Actual

Enter only login Enter login id Error message an error True

id and press is displayed message
submit button showing “all “password is
fields must be empty” is
entered” displayed

Enter only Enter Error message an error True

1.Login
password and Password is displayed message “email
click Submit showing “all id is empty” is
Button fields must be displayed
entered”

Table 6.3: Login Page Test Case.

6.3 VALIDATION:
Although testing varies between organizations, there is a cycle to testing:

 Requirements Analysis: Testing should begin in the requirements phase of the software
development life cycle. During the design phase, testers work with developers in determining what
aspects of a design are testable and under what parameter those tests work.
 Test Planning: Test Strategy, Test Plan(s), Test Bed creation.
 Test Development: Test Procedures, Test Scenarios, Test Cases, Test Scripts to use in testing
software.
 Test Execution: Testers execute the software based on the plans and tests and report any errors
found to the development team.
 Test Reporting: Once testing is completed, testers generate metrics and make final reports on their
test effort and whether or not the software tested is ready for release.

58
 SHOPEE IN STYLE

 Retesting the Defects:Not all errors or defects reported must be fixed by a software development
team. Some may be caused by errors in configuring the test software to match the development
or production environment. Some defects can be handled by a workaround in the production
environment. Others might be deferred to future releases of the software, or the deficiency might
be accepted by the business user. There are yet other defects that may be rejected by the
development team (of course, with due reason) if they deem it inappropriate to be called a defect.
A test case is a software testing document, which consists of event, action, input, output,
expected result and actual result.

Black box Testing:It is being an external view of the test object. It is also called as functional
testing.

White box Testing: It is being an internal view of the test object. It is also called as structural
testing.

Unit testing :In which each unit (basic component) of the software is tested to verify that the detailed
design for the unit has been correctly implemented.

Integration testing: In which progressively larger groups of tested software components

corresponding to elements of the architectural design are integrated and tested until the software works
as a whole.

System testing:

In which the software is integrated to the overall product and tested to show that all requirements are met.

6.4CONCLUSION:

59
 SHOPEE IN STYLE

Testng and validation helps in finding the bugs in various modules of the project using various testing
processes and the found bugs are removed by validating them. This testing helps to improve the quality
of the software and the hardware requirements of the project. The throughput of the project also
increases in a better way if the project is built without any errors.

60
 SHOPEE IN STYLE

CONCLUSION

1. CONCLUSION

7.1 PROJECT CONCLUSION:

61
 SHOPEE IN STYLE

 Online Shopping is different experience

 This will allow customers to place order without even visiting the shop
 Being able to buy anytime, anyplace, anywhere
 it will be more enjoyable and easier than real world shopping

7.2 FUTURE ENHANCEMENTS

It is not possible to develop a system that makes all the requirements of the user. User requirements
keep changing as the system is being used. Some of the future enhancements that can be done to this
system are:
 As the technology emerges, it is possible to upgrade the system and can be adaptable to desired
environment.
 Because it is based on object-oriented design, a
 Any further changes can be easily adaptable.
 Adding payment gateway will help admin.
 Implementing points based system will enhance the users interest towards this web-
application.

62
 SHOPEE IN STYLE

REFERENCES

8.REFERENCES
8.1 Text Books:
[1] Gary Cornell: Core Java, Volume II--Advanced Features, Pearson Education –Sun
63
Microsystems, 9th Edition, Published in 2013.
[2] George Reese: Database Programming with JDBC and Java, O'Reilly Media, 2nd Edition, Published
in 2010.
[3] Grady Brooch, James Rumbaugh, Ivar Jacobson: The Unified Modeling Language User Guide,
Pearson Education 2nd Edition, Published in 2007.
[4] Roger S Pressman: Software engineering (A practitioner’s approach), McGraw-Hill Education
6th Edition, Published in 2012.
[5] Joshua Bloch: Effective Java – Programming Language Guide, Addison-Wesley
Professional 2nd Edition, Published in 2008.
8.2 Websites:
[1] http://www.w3schools
[2] http://www.javatpoint
[3] http://eclipse.org
[4] http://javaserverpages.com
[6]http://mapki.com/wiki/Google_Map_Parameters
[7] https://developers.google.com/maps

64