JOB PORTAL WEBSITE

MINOR PROJECT REPORT

Submitted by

SARANG SHASTRY ENROLL NO:0208CA211053

SUYASH PANDEY ENROLL NO:0206CA211060
ANUJ SHUKLA ENROLL NO:0208CA211013

in partial fulfillment for the award of the degree

of

MASTERS OF COMPUTER
APPLICATION

DEPARTMENT OF COMPUTER APPLICATION

GYAN GANGA COLLEGE OF TECHNOLOGY
JABALPUR (M.P.)
RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA,
BHOPAL (M.P.)
 CERTIFICATE

This is to certify that the Minor Project Report entitled “E-COMMERCE

APPLICATION ” submitted by BHAVESH KUSHWAHA,DEVESH IYER,

GAUTAMI CHHABRA and AYUSH TIWARI has been carried out under my

guidance & supervision. The Minor project report is approved for submission

towards partial fulfillment of the requirement for the award of degree of

BACHELOR OF ENGINEERING in COMPUTER SCIENCE &

ENGINEERING from “RAJIV GANDHI PROUDYOGIKI

VISHWAVIDYALAYA, BHOPAL (M.P).

(Prof.Saurabh Kapoor) (Prof.Ashok Verma)

Guide HOD

Dept. of Computer Science & Engg. Dept of Computer Science & Engg.
 CERTIFICATE

This is to certify that the Minor Project Report entitled “E-COMMERCE

APPLICATION” is submitted by BHAVESH KUSHWAHA, DEVESH

IYER, GAUTAMI CHHABRA and AYUSH TIWARI for the partial

fulfillment of the requirement for the award of degree of BACHELOR OF

ENGINEERING in COMPUTER SCIENCE & ENGINEERING from

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL

(M.P).

Internal Examiner External Examiner

Date : Date :
 DECLARATION

We hereby declare that the Minor Project Report entitled “E-COMMERCE

APPLICATION” which is being submitted in partial fulfillment of the
requirement for award of the Degree of Bachelor of Engineering in Computer
Science and Engineering to “RAJIVGANDHI PROUDYOGIKI
VISHWAVIDYALAYA, BHOPAL (M.P.)” is an authentic record of our own
work done under the guidance of Prof. Saurabh Kapoor, Department of
Computer Science & Engineering , GYAN GANGA INSTITUTE OF
TECHNOLOGY & SCIENCES, JABALPUR..

The matter has not been submitted earlier for the award of any other degree.

Dated : AYUSH TIWARI

BHAVESH KUSHWAHA
DEVESH IYER
GAUTAMI CHHABRA

Place :JABALPUR
 ACKNOWLEDGEMENT

We sincerely express indebtedness to esteemed and revered guide

Prof. Saurabh Kapoor, in Computer Science Department for his
invaluable guidance, supervision and encouragement throughout the
work. Without his kind patronage and guidance project would not
have taken shape.

We take this opportunity to express deep sense of gratitude to Prof.

Ashok Verma, Head of Computer Science Department for his
encouragement and kind approval. Also we thank him in providing
the computer lab facility. We would like to express our sincere
regards to him for advice and counseling from time to time.

We owe sincere thanks to all the faculties in “Computer Science

Department” for their advice and counseling time to time.

Dated :

Place : JABALPUR
 TABLE OF CONTENTS

Serial No. Title Page No.

ABSTRACT 1
1. INTRODUCTION 2
1.1 PURPOSE 2
1.2 SCOPE 3
1.3 INTENDED AUDIENCE 3
1.4 OBJECTIVE 4
2 PROBLEM STATEMENT 5
3 REQUIREMENTS 6
3.1 SPECIFIC REQUIREMENTS 6
3.1.1 EXTERNAL INTERFACE REQUIREMENTS 6

3.2 NON FUNCTIONAL REQUIREMENTS 6

SOFTWARE DEVELOPMENT
4 8
METHODOLOGY
4.1 SOFTWARE PROCESS MODEL 10
4.2 FEASIBILITY STUDY 13
4.2.1 TECHNICAL FEASIBILITY 14
4.2.2 OPERATIONAL FEASIBILITY 14
4.2.3 ECONOMICAL FEASIBILITY 14
5 TESTING 15
6 DIAGRAM 19
7 DATA BASE TABLE 23
8 SCREEN SHOTS 24
9 FUTURE SCOPE 29
10 CONCLUSION 29
11 REFERENCES 30
LIST OF FIGURES

 DATA FLOW DIAGRAM

 LEVEL 0
 LEVEL 1

 CLASS DIAGRAM

 E-R DIAGRAM

LIST OF TABLE

1. DATABASE TABLE
 ABSTRACT

Mobile and e-commerce applications are tools for accessing the Internet and for
buying products and services. These applications are constantly evolving due to
the high rate of technological advances being made. This paper provides a new
perspective on the types of applications that can be used. It describes and
analyses device requirements, provides a literature review of important aspects
of mobile devices that can use such applications and the requirements of
websites designed for e-commerce. The design and security aspects of mobile
devices are also investigated. As an alternative to existing m-commerce
applications, this paper also investigates the characteristics and potential of the
Android platform application. The results suggest that effective mobile
applications do exist for various Smartphones, and web applications on mobile
devices should be effective. As the major Applications do include the local
market, we aim to open the local as well as global market for the manufacturer
via digitalizing them. Also, it will provide Customers with lots and lots of
variety of material they needed.

Page | 1
 1. Introduction

The internet has changed many aspects of society,

from business to recreation, from culture to communication and technology,
as well as shopping and traveling. This new form of communication has
provided new ways of doing business with the help of technological
development. E-commerce is a new way of shopping and doing business.
Technology has allowed companies to promote and sell their products on new
markets, overcoming international borders as never before.

Consumers have access to a wider market of products when they use wireless
and internet technologies. Mobile devices with wide access to the Internet
have allowed companies to reach consumers in more diverse ways, thus
ensuring deep market penetration

1.1 Purpose of the Application

The purpose of designing interfaces for mobile applications should be to
increase consumers’ interest in using and ease of access to m-commerce.
Among the inhibiting factors is that m-commerce applications were developed
based on e-commerce applications. The most important thing when designing
such applications is to design the application in such a way that it does not
distract the user from the main purpose of the application. However, aspects
concerning security and accessibility should not be neglected. Even though
storing sensitive data such as medical, financial, or personal information on
mobile devices can help people, the risks of losing such information or of
unauthorized access are higher and should be considered when an m-commerce
transaction begins.

Page | 2
 1.2 Scope of the document
The basic functionality delivered by the application features two main factors,
product listing, and a product detail page. Two changes were made,
- Spree web services were modified to show complete data in our mobile
application.
- The functionality needed so that the mobile application can list products by
requesting web services provided by the Spree commerce application was
added.
- The functionality of the mobile application was improved to show complete
information on a product by requesting a second web-service from the Spree-
commerce application. Best practices were employed for making the user
interface of the mobile application functional.

1.3 Intended audience

The expected audience of this document is the users of the E-commerce
application (admin and customers) and the developers.

Page | 3
1.4 Objective of the System
The core objective is to implement the project E-commerce application to
reduce the work and efforts and at an identical time increase the flow of the
work done.

1) Development of Business-Relationship.

2) Better-Customer Service.

3) Getting more Customers.

Page | 4
2. Problem Statement
E-commerce shopping is the group of processes that are responsible to collect
consumption data, calculate charging and billing information, produce bills to
customers, process their payments and deliver the products.

Following square measure the most drawbacks of the present system:

 Product Quality

 Delivery Time Is Not Clear

 Payment Preferences Are Limited

 Complicated Navigation

 Payment confirmation missing

 The trouble with Hidden costs

 Unclear Website Policies

 Problem of Plenty

Features of the System

 Consistent interface with high economic options

designed into it.

 System style in standard and structured manner thus on create the

combination with alternative subsystems easier.

 User has complete management because it provides and accepts solely

acceptable and valid knowledge.

 User-friendly error messages square measure provided where necessary.

Page | 5
3 REQUIREMENTS

3.1 SPECIFIC REQUIREMENTS

3.1.1 External Interface Requirements

User Interface
The user interface required to be developed for the application should be user
friendly and attractive.
For designing and interface, Android studio has been used,
supported by Google Firebase.

Hardware Interfaces
• A stable Internet Connection Required.
• RAM 512MB and Above.
• Android Marshmallow(6.0) or above needed.

Software Interfaces
Programming Language - JAVA, XML.
Database - Google Firebase.

3.2 Nonfunctional Requirements

Safety Requirements

One way of calculating software safety is to categorize our software failures

into the following states:

 Transient - Occur only with certain inputs.

Page | 6
  Permanent - Occur with all inputs

 Recoverable –System can recover data with no operator intervention

 Unrecoverable-operator intervention needed for recovery.

 Non-corrupting-Failure does not corrupt data.

 Corrupting-Failure corrupts data.

Security Requirements:

 Authorization - only license creators can acquire content from the content
creator

 Trust -The manager/renderer pair on the user side will only render the
content if all terms of any one valid license governing this content are
met

 Robustness- The internal workings of the manager/renderer pair cannot

be influenced or disrupted by the license creator, the user nor any third
party.

 Authentication- no component sends the content to another component,

unless the receiving component is authenticated as an official component.

Software Quality Attributes:

i.) Performance - from the tradition of hard real-time applications and capacity
planning.

ii.) Usability - from the tradition of human-computer interaction and human

factors.

iii.) Safety - from the tradition of hazard analysis and system safety
engineering.

iv.) Security - from the traditions of the government, banking and academic
communities.

Page | 7
4. SOFTWARE DEVELOPMENT METHODOLOGY
The establishment and use of engineering principles in order to obtain
economically developed software that is reliable and works efficiently on real
machines is called software engineering.

Software engineering is the discipline whose aim is:

1. Production of quality software

2. Software that is delivered on time
3. Cost within the budget
4. Satisfies all requirements.

Software process is the way in which we produce the software. Apart from
hiring smart, knowledgeable engineers and buying the latest development tools,
effective software development process is also needed, so that engineers can
systematically use the best technical and managerial practices to successfully
complete their projects.
A software life cycle is the series of identifiable stages that a software product
undergoes during its lifetime .A software lifecycle model is a descriptive and
diagrammatic representation of the software life cycle .A life cycle model
represents all the activities required to make a software product transit through
its lifecycle phases .It also captures the order in which these activities are to be
taken.

Typical formal definitions of software engineering are:

 "research, design, develop, and test operating systems-level software,

compilers, and network distribution software for medical, industrial,
military, communications, aerospace, business, scientific, and general
computing applications."

 "The systematic application of scientific and technological knowledge,

methods, and experience to the design, implementation, testing, and
documentation of software."

 "The application of a systematic, disciplined, quantifiable approach to the

development, operation, and maintenance of software."

Page | 8
 "An engineering discipline that is concerned with all aspects of software
production."

 "The establishment and use of engineering principles in order to

economically obtain software that is reliable and works efficiently on real
machines."

Page | 9
4.1 SOFTWARE PROCESS MODEL
There are various life cycle models to improve the software processes.

 WATERFALL MODEL
 PROTOTYPE MODEL
 ITERATIVE INCREMENTAL MODEL
 EVOLUTIONARY MODEL
 SPIRAL MODEL

 Waterfall Model
Waterfall model is the simplest model of software development paradigm. It
says the all the phases of SDLC will function one after another in linear manner.
That is, when the first phase is finished then only the second phase will start and
so on.

This model assumes that everything is carried out and taken place perfectly as
planned in the previous stage and there is no need to think about the past issues
that may arise in the next phase. This model does not work smoothly if there are
some issues left at the previous step. The sequential nature of model does not
allow us go back and undo or redo our actions.

Page | 10
This model is best suited when developers already have designed and developed
similar software in the past and is aware of all its domains.

In the project, Waterfall model is followed.

Page | 11
WATERFALL MODEL

This model contains 6 phases:

 Feasibility study
The feasibility study activity involves the analysis of the problem and collection
of the relevant information relating to the product. The main aim of the
feasibility study is to determine whether it would be financially and technically
feasible to develop the product.

 Requirement analysis and specification

The goal of this phase is to understand the exact requirements of the customer
and to document them properly (SRS).

 Design
The goal of this phase is to transform the requirement specification into a
structure that is suitable for implementation in some programming language.

 Implementation and unit testing

During this phase the design is implemented. Initially small modules are tested
in isolation from rest of the software product.

 Integration and system testing

In this all the modules are integrated and then tested altogether.

 Operation and maintenance

Release of software inaugurates the operation and life cycle phase of the
operation.

The phases always occur in this order and do not overlap.

Page | 12
4.2FEASABILITY STUDY
Once scope has been identified (with the concurrence of the customer), it is
reasonable to ask: “Can we build software to meet this scope? Is the project
feasible?” All too often, software engineers rush past this questions (or are
pushed past them by impatient managers or customers), only to become mired
in a project that is doomed from the onset.

When we are developing the system (software), we must know the proposed
system will be feasible or i.e. practically implemented or not it may possible the
proposed( candidate ) system may not implemented due to many reasons like it
may take long time in development than the specified time limit ,cost may
increase than proposed one etc. Therefore we must analyze the feasibility of the
system.

Feasibility is the analysis of risks, costs & benefits relating to economics,

technology & user operation. There are several types of feasibility depending on
the aspect they covers.

Some important feasibility is as follows:-

 Technical Feasibility
 Operational Feasibility
 Economical Feasibility

Page | 13
4.2.1 TECHNICAL FEASIBILTIY
The technically feasibility study basically centers on alternatives for hardware,
software and design approach to determine the functional aspects of application.
This project on E-commerce application is made with the help of Android
studio, so it will be accessible to more than 80% Smartphone users in the
World. Firebase database has been be used for storing data.
Hardware requirements used are compatible with android devices. Only
registered person would be able to use the applications it would be secure. The
application can also be expanded as per the needs of requirement specification.

4.2.2 OPERATIONAL FEASIBILTY

Operational Feasibility is a measure of how people are able to work with
system. This type of feasibility demands if the application will work when
developed and installed.
Since Mobile based applications are very user friendly so users will find it
comfortable to work on it.

4.2.3 ECONOMICAL FEASIBILITY

Economic analysis is the most frequently used evaluating the effectiveness of
proposed system, more commonly known as Benefit analysis. The Benefit
analysis is to determine benefits and savings which are expected from billing
system and compare them with cost. If the benefits are more than the cost, then
decision is made to design and implement the system. The constant benefits
may be direct or indirect and tangible or intangible.

Page | 14
5. TESTING

 Software testing is the process of executing a program with intension of

finding errors in the code. It is a process of evolution of system or its
parts by manual or automatic means to verify that it is satisfying specified
or requirements or not.

 Generally, no system is perfect due to communication problems between

user and developer, time constraints, or conceptual mistakes by
developer.

 To purpose of system testing is to check and find out these errors or

faults as early as possible so losses due to it can be saved.

 Testing is the fundamental process of software success.

 Testing is not a distinct phase in system development life cycle but

should be applicable throughout all phases i.e. design development
and maintenance phase.

 Testing is used to show incorrectness and considered to success when

an error is detected.

Page | 15
OBJECTIVES OF SOFTWARE TESTING
The software testing is usually performed for the following objectives:-

 SOFTWARE QUALITY IMPROVEMENT

The computer and the software are mainly used for complex and critical
applications and a bug or fault in software causes severe losses. So a great
consideration is required for checking for quality of software.

 VERIFICATION AND VALIDATION

 Verification means to test that we are building the product in right way
.i.e. are we using the correct procedure for the development of software
so that it can meet the user requirements.
 Validation means to check whether we are building the right product or
not.

 SOFTWARE RELIABILTY ESTIMATION

The objective is to discover the residual designing errors before delivery to the
customer. The failure data during process are taken down in order to estimate
the software reliability.

Page | 16
PRINCIPLES OF SOFTWARE TESTING

Software testing is an extremely creative and challenging task. Some important

principles of software testing are as given:-

 All tests should be traceable to customer requirements.

 Testing time and resources should be limited i.e. avoid redundant testing.
 It is impossible to test everything.
 Use effective resources to test.
 Test should be planned long before testing begins i.e. after requirement
phase.
 Test for invalid and unexpected input conditions as well as valid
conditions.
 Testing should begin in “in the small” and progress towards testing “in
the large”.
 For the most effective testing should be conducted by an independent
party.
 Keep software static (without change mean while) during test.
 Document test cases and test results.
 Examining what the software not doing which it expected to do and also
checking what it is doing that was not expected to do.

Page | 17
STRATEGY FOR SOFTWARE TESTING
Different levels of testing are used in the test process each level of testing aims
to test different aspects of the system.

 The first level is unit testing. In this testing, individual components are
tested to ensure that they operate correctly. It focuses on verification
efforts.

 The second level is integration testing. It is a systematic technique for

constructing the program structure. In this testing, many tested modules
are combined into the sub systems which are then tested. The good here is
to see if the modules can be integrated properly.

 The third level is system testing. System testing is actually a series of

different tests whose primary purpose is to fully exercise computer based
system. These tests fall outside scope of software process and are not
conducted solely by software engineers

Page | 18
6. DIAGRAMS

 DATA FLOW DIAGRAM

LEVEL 0

Page | 19
LEVEL-1

Page | 20
 ER DIAGRAM

E-R Diagram for Ecommerce Application

Page | 21
 CLASS DIAGRAM

Class Diagram for Ecommerce Application

Page | 22
7. DATABASE TABLES

Page | 23
8. SCREEN SHOTS

 Main Page

Page | 24
 Login Page

Page | 25
 Registration Page

Page | 26
 Admin Addition of Products Pages

Page | 27
 Customer Home Page/Product Details Page

Page | 28
9. FUTURE SCOPE
After implementing the system the project will be great scope of application.
Now days in all the organization the work culture has totally changed. The
entire application of the system targets to connect the people to products. The
table should be converted to computer terminals and all officers are to be
considered as the local workstations. In the near future all the systems will be
manipulated by Mobile devices. Our application will be smart and modern.

Every project whether large or small has some limitations no matter however
diligently developed. In some cases limitations is small while in other cases they
may be broad also. The new system has got some limitations. Major areas where
modifications can be done are as follows:

 The security is limited so some additional arrangement could be made to

provide more security to the system.
 There is no provision of complain handling so further it can be added.

10. CONCLUSION

In this project we have tried our best to make user friendly software .This
software can be handled by any person who has little bit of idea of Mobiles. In
this software we have tried to meet most of the requirements of the present E-
commerce shopping application including maintaining details of customers,
their accounts and other information’s. We also keep provision to alter the
database of customer details and records of the accounts. We have given a
professional look to the reports of the services of our system using data-report.
In our effort we have tried to make our application all the more user friendly but
there may some features which we would like to include in our continuous
attempts.

Page | 29
11. References

 www.google.com
 https://www.researchgate.net/publication/259844267_E-
commerce_Smartphone_Application
 https://www.lucidsoftech.com/blog/e-commerce-solution-feasibility-
future-and-check-list-for-purchasing

Page | 30