USED PRODUCTS STORE 201

Project Report
On
“USED PRODUCTS STORE”

Faculty Team Members

Mr. Vijay Gupta ILA HAJELA
MCA Department AKSHAY PAREEK
AVINASH
GAUTAM

International School of Informatics &

Management

1|Page
 USED PRODUCTS STORE 201
1

Formerly India International Institute of

Management

2|Page
 USED PRODUCTS STORE 201
1

CERTIFICATE
This is to certify that USED PRODUCTS STORE
embodies the original work done by ILA
HAJELA,AKSHAY PAREEK,AVINASH GAUTAM
during this project submission as a partial
fulfillment of the requirement for the System
Design Project of Masters of Computer Application
IV Semester, of the Rajasthan Technical University,
Kota.

Dr.Swati V. Chande
Principal
(MCA Department)
International School of
Informatics and Management

Mr.Vijay Gupta
Assistant Professor
International School of
Informatics and Management

3|Page
 USED PRODUCTS STORE 201
1

ACKNOWLEDGEMENT
The satisfaction that accompanies that the
successful completion of any task would be
incomplete without the mention of people whose
ceaseless cooperation made it possible, whose
constant guidance and encouragement crown all
efforts with success.

We are grateful to our project guide Mr.Vijay Gupta

for the guidance, inspiration and constructive
suggestions that helpful us in the preparation of
this project.

We also thank our colleagues who have helped in

successful completion of the project.

ILA HAJELA
AKSHAY PAREEK
AVINASH GAUTAM

4|Page
 USED PRODUCTS STORE 201
1

Table of Contents Page

No.
1.0 Introduction 6
1.1 Purpose 7
1.2 Scope 7
1.3 Overview 7
1.4 Goals of Proposed System 8
1.5 Project Requirements 9
1.6 Technologies Used 9
1.7 User Characteristics 10
1.8 Constraints 10
1.9 Definition of Problems 11

2.0 Feasibility Study 12

2.1 Technical Feasibility 13
2.2 Economical Feasibility 15
2.3 Operational Feasibility 16
2.4 Schedule Feasibility 16

3.0 System Analysis 17

3.1 Working of Present System 17

5|Page
 USED PRODUCTS STORE 201
1

3.2 Disadvantages of Present System 17

3.3 Proposed System 18
3.4 Architectural Design 19
3.5 E-R Diagram 20
3.6 Data Flow Diagram 21
3.7 Use Case Ddiagrams 25
3.8 Class Diagram 28

4.0 System Design 29

4.1 Database Tables 29

5.0 Conclusion 31

6.0 Bibliography 31

6|Page
 USED PRODUCTS STORE 201
1

Software Requirements
Specifications

1.0Introduction
One of the most interesting aspect of online trading is the
buying and selling of used or secondhand products. It
makes the task of selling and purchasing used goods so
much easier. With minimal marketing efforts from you as
a seller or a reseller, you can be assured that prospective
customers will still be available for the products that you
are selling. Just make sure that you give a good
description of your product, and more importantly good
quality pictures of the products that you are selling so
that you can be noticed by prospective buyers

1.1 Purpose
This project is aimed at developing a website for buying and
selling of the pre-used gadgets. It provides an interface for the customers
and users to sell and buy second hand products.
If you want to save a bit of money then it can be a
good idea to buy second hand electronic devices. It can
be a risky business, buying second hand items and even
more so with electronic devices.

1.2 Scope
7|Page
 USED PRODUCTS STORE 201
1

 The user have to login to use the facilities.

 Product details are posted by the seller.
 Buyer can browse the website and selects the
desired product
from the various categories.
 Admin is allowed to generate various reports
according to the requirement.
 The admin have rights to add, delete, and update the
information.

1.3 Overview
 Project is related to USED PRODUCTS
STORE (UPS).
 This project maintains 3 types of users.
 Buyer
 Seller
 Administrator
 Facilities provided by this projects are as follows
 Details of product.
 Update of easy data.
 Reports .
 Flow of information is fast and easy.
 Sellers can login to their accounts and view their
products.

1.4 Goals of Proposed System

1) Accuracy: - The level of accuracy in the proposed
system will be higher. All operation would be done

8|Page
 USED PRODUCTS STORE 201
1

correctly and it ensures that whatever information is

coming from the center is accurate.
2) Reliability: - The reliability of the proposed system
will be high due to the above stated reasons. The
reason for the increased reliability of the system is
that now there would be proper storage of
information.
3) Immediate Retrieval of Information: - The main
objective of proposed system is to provide for a quick
and efficient retrieval of information. Any type of
information would be available whenever the user
requires.
4) Immediate storage of information: - In manual
system there are many problems to store the largest
amount of information.
5) Easy to Operate: - The system should be easy to
operate and should be such that it can be developed
within a short period of time and fit in the limited
budget of the user.

1.5 Technologies Used

This project will be an Internet application to be

developed in following tools and technologies.
a) ADO (ActiveX Data Objects) – ADO is used to
access database from web pages.
b) AJAX (Asynchronous JavaScript and XML) – It is
used to make Internet application smaller, faster and
more user-friendly.
c) ASP.NET (Active Server Pages.NET) – It is part of
the Microso
ft .NET framework, and a powerful tool for creating
dynamic and interactive web pages.
9|Page
 USED PRODUCTS STORE 201
1

d) C# (C Sharp) – It is part of Microsoft .NET framework

and a powerful tool for creating dynamic and
interactive web pages.
e) CSS (Cascading Style Sheets) – It is used to create
stylish web pages.
f) DHTML (Dynamic Hyper Text Markup Language)
– It is used to create dynamic web pages.
g) DREAMWEAVER – It is a tool to develop web pages.
h) HTML (Hyper Text Markup Language) – It is used
to describe web pages.
i) JAVASCRIPT – It is used improve the design, validate
forms, detect browsers, create cookies, and much
more.
j) SQL (Structured Query Language) – It is a
standard language for accessing and manipulating
databases.
k) VISUAL STUDIO – It is a tool to develop a complete
and dynamic web application.
l) XML (Extensible Markup Language) – It is used to
transport and store data over the Internet.

1.8 PROBLEMS IN CONVENTIONAL SYSTEM

 Lack of immediate retrievals: -The information is

very difficult to retrieve and to find particular
information. This results in inconvenience and
wastage of time.
 Lack of immediate information storage: - The
information generated by various transactions takes
time and efforts to be stored at right place.

10 | P a g e
 USED PRODUCTS STORE 201
1

 Lack of prompt updating: - Various changes to

information are difficult to make as paper work is
involved.
 Preparation of accurate and prompt reports: -
This becomes a difficult task as information is
difficult to collect from various registers.

2.0Feasibility Study
Depending on the results of the initial investigation the
survey is now expanded to a more detailed feasibility
study. “FEASIBILITY STUDY” is a test of system
proposal according to its workability, impact of the
organization, ability to meet needs and effective use of
the resources. It focuses on these major questions:
 What are the user’s demonstrable needs and how
does a candidate system meet them?

11 | P a g e
 USED PRODUCTS STORE 201
1

 What resources are available for given candidate

system?
 What are the likely impacts of the candidate system
on the organization?
 Whether it is worth to solve the problem?

During feasibility analysis for this project, following

primary areas of interest are to be considered.
Investigation and generating ideas about a new system
does this.

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:
 Form a project team and appoint a project leader.
 Prepare system flowcharts.
 Enumerate potential proposed system.
 Define and identify characteristics of proposed
system.
 Determine and evaluate performance and cost
effective of each proposed system.
 Weight system performance and cost data.
 Select the best-proposed system.
 Prepare and report final project directive to
management.

2.1 Technical Feasibility

Technical feasibility is the study of resource availability
that may affect the ability to achieve an acceptable
system. This evaluation determines whether the

12 | P a g e
 USED PRODUCTS STORE 201
1

technology needed for the proposed system is available

or not.
 Can the work for the project be done with current
equipment existing software technology & available
personal?
 Can the system be upgraded if developed?
 If new technology is needed then what can be
developed?

This is concerned with specifying equipment and software

that will successfully satisfy the user requirement. The
technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the
selection of suitable front-end and back-end. When we
decided to develop the project we went through an
extensive study to determine the most suitable platform
that suits the needs of the academy as well as helps in
development of the project.
The aspects of our study included the following factors.

Front-end selection:
 It must have a graphical user interface that assists
employees that are not from IT background.
 Scalability and extensibility.
 Flexibility.
 Robustness.
 According to the organization requirement and the
culture.
 Must provide excellent reporting features with good
printing support.

13 | P a g e
 USED PRODUCTS STORE 201
1

 Platform independent.
 Easy to debug and maintain.
 Event driven programming facility.
 Front end must support some popular back end like
Ms Access.

According to the above stated features we selected Web

Browser as the front-end for developing our project.

Back-end Selection:
 Multiple user support.
 Efficient data handling.
 Provide inherent features for security.
 Efficient data retrieval and maintenance.
 Stored procedures.
 Popularity.
 Operating System compatible.
 Easy to install.
 Various drivers must be available.
 Easy to implant with the Front-end.

According to above stated features we selected SQL

Server as the backend.
The technical feasibility is frequently the most difficult
area encountered at this stage. It is essential that the
process of analysis and definition be conducted in parallel
with an assessment to technical feasibility. It centers on
the existing computer system (hardware, software etc.)
and to what extent it can support the proposed system.

14 | P a g e
 USED PRODUCTS STORE 201
1

2.2 Economical Feasibility

Economic justification is generally the “Bottom Line”
consideration for most systems. Economic justification
includes a broad range of concerns that includes cost
benefit analysis. In this we weight the cost and the
benefits associated with the candidate system and if it
suits the basic purpose of the organization i.e. profit
making, the project is making to the analysis and design
phase.
The financial and the economic questions during the
preliminary investigation are verified to estimate the
following:
 The cost to conduct a full system investigation.
 The cost of hardware and software for the class of
application being considered.
 The benefits in the form of reduced cost.
 The proposed system will give the minute
information, as a result the performance is improved
which in turn may be expected to provide increased
profits.
 This feasibility checks whether the system can be
developed with the available funds. The USED
PRODUCTS STORE does require enormous amount
of money to be developed. This can be done
economically if planned judicially, so it is
economically feasible.

2.3 Operational Feasibility

15 | P a g e
 USED PRODUCTS STORE 201
1

It is mainly related to human organizations and political

aspects. The points to be considered are:
 What changes will be brought with the system?
 What organization structures are disturbed?
 What new skills will be required? Do the existing staff
members have these skills? If not, can they be
trained in due course of time?

The system is operationally feasible as it very easy for

the End users to operate it. It only needs basic
information about Windows platform.

3.0System Analysis
System analysis uses a combination of text and
diagrammatic forms to depict requirements for data,
function and behavior in a way that is relatively easy to
understand, and more important, straightforward to
review for correctness, completeness and consistency.

3.1 Working of Present System

In present system, buyers and sellers used to go to either
a retail outlet or contact some person after seeing an
advertisement in newspaper or TV.
This approach is quite time consuming as customer
cannot buy the product as soon as possible. Here both
money and time are wasted in comparison to sell or buy
such product online.

3.2 Disadvantages of Present System

16 | P a g e
 USED PRODUCTS STORE 201
1

Since, our present system has several disadvantages

described below:
 Lack of immediate retrievals: -The information is
very difficult to retrieve and to find particular
information. This results in inconvenience and
wastage of time.
 Lack of prompt updating: - Various changes to
information are difficult to make as paper work is
involved.
 Preparation of reports: - This becomes a difficult
task as information is difficult to collect from various
registers.

3.3 Proposed System

The “USED PRODUCTS STORE” is web-based

management system. If you want to save a bit of money
then it can be a good idea to buy second hand electronic
devices. It can be a risky business, buying second hand
items and even more so with electronic devices. The
following are a few ideas of what you need to be looking
for when buying second hand items so that you don’t end
up with buyer’s remorse.

- It is essential that you try out any second hand

electronic device that you are considering before actually

17 | P a g e
 USED PRODUCTS STORE 201
1

buying it. However be aware that not all problems will be

instantly noticeable. Try to use as many of the functions
as you can before you buy these devices.

- It is a good idea to check if the device you are

considering is still supported before you buy it. If the
device is not supported any longer then it could mean
that you cannot fix it if it breaks and replacement
batteries will not be available. And if the device uses a
memory card, then you need to make sure that they can
still be bought.

- Check to see if the game developers are still making

games for the device if it is a games console or mobile
gaming device.

- Get some help and advice from someone with a bit of

knowledge about the device if you are not sure about it. If
you want to make sure that you buy an appropriate
device and not end up with something that you are sorry
you bought, then you should really get this help.

3.4 Architectural Design

Architectural design represents the structure of data and

program components that are required to build a
computer-based system. It considers the architectural
style that the system will take, the structure and

18 | P a g e
 USED PRODUCTS STORE 201
1

properties of the components that constitute the system,

and the interrelationships that occur among all
architectural components of a system.

Administrator

Database
Buyer
USED
PRODUCTS
Seller STORE

=
Request
=
Response Figure: Architectural
= Request &
Response Design

3.5 E-R Diagram

The object/relationship pair is the cornerstone of the data
model. These pairs are represented graphically using E-R
diagrams. A set of primary components are identified for
19 | P a g e
 USED PRODUCTS STORE 201
1

the ERD: data objects, attributes, relationships and

various type indicators. The primary purpose of ERD is to
represent data objects and their relationships.

20 | P a g e
 USED PRODUCTS STORE 201
1

3.6 DFD
The data flow diagram enables the software engineer to
develop models of the information domain and functional
domain at the same time. As the DFD is refined into
greater level of detail, the analyst performs an implicit
functional decomposition of the system. At the same
time, the DFD refinement results in corresponding
refinement of data as it moves through the processes
that embody the application.

Context Diagram:-

21 | P a g e
 USED PRODUCTS STORE 201
1

user

Form
Registration Filling
form

Form
view
Filling ONLIN
update
Login E AD
addus Admin
Compan MGMT
Reports er
y user SYSTE
Post Ad M login

Level 1:-
Company User:-

22 | P a g e
 USED PRODUCTS STORE 201
1

login

Compan unsuccess Login Comp-

y user
ful 1.0 table

OAMS
1.1
requset
request

response
response
Repor Post
Form
t add
filling
1.1.2 1.1.3
1.1.1

User:-

Rep-ort

user OAMS

23 | P a g e
 USED PRODUCTS STORE 201
1

Com_acc_i
nfo
Admin:-
login

Logi
Administr Admin table
n
ator Unsu8ccessf
ul 1.0

OA
MS
requset

response
response request

Admi Updat
View
n e
1.1.3
1.1.1 1.1.2

24 | P a g e
 USED PRODUCTS STORE 201
1

3.7 Use Case Model

Use Case Model is an approach that is a combination of
text and pictures in order to improve the understanding
of requirements. A „use case model' is describes the
complete functionality of a system by identifying how
everything that is outside the system interacts with it.
A Use Case Diagram is given below that relates to this
application.

 Description – This project is a web application that

manages a tennis academy.

 Actors – It has 4 actors.

1)Administrator
2)Company_user
3)user

25 | P a g e
 USED PRODUCTS STORE 201
1

Manag
e
Compl
ete
Syste
m

Create
Accoun
t
Administrat
or

View
report

Fill Up
detail
s of
comp.

Compan Updat
y_user e Info

View
Detail User

Visit
Accou
nts

Figure: Use Case

Model

26 | P a g e
 USED PRODUCTS STORE 201
1

 Flow of Events –
o User logins into the system using ID and
password.
o If user is an authorized user then access is
granted otherwise denied.
o User selects any tasks to do and task is
performed.

 Special Requirements –
o Data will flow from one user to another.
o Data generated by one user can’t be altered by
another user.
o One user can’t change the status of another user
except administrator.

 Pre Condition –
o All users s
o hould have their account created on the system.
o Data entry operator should have updated the
details of other users.

 Post Condition –
o Details are available to users.
o Details and information are intact and valid.

3.8 Class Diagram

A class diagram shows relationship among classes used
in the system. Every class has some contents, attributes
and objects associated with it. Every class produces some
outputs and uses some inputs. Outputs generated are
consumed by other classes and inputs consumed are

27 | P a g e
 USED PRODUCTS STORE 201
1

generated by other classes. Class diagram shows which

class is producing what and consuming what.
ADMINISTRATOR Comp_ID_table
ID
NAME
DOB
PASSWORD ID
CONTACT NO. PASSWORD
ADDRESS
SECURITY QUESTION
ANSWER

updateOwnDetails( )
viewOwnDetails( ) CheckDetails( )
createAccounts( )
manageSystem( )

Comp_info_Table COMP_ACC_INFO
COMPANY_NAME
ID ID
PASSWORD TOTAL_SIZE
DOJ REM_SIZE
COMP_EMAIL_ID START_DATE
ADDRESS LAST_DATE
SECURITY QUESTION COUNTER
ANSWER

viewDetails( )
Acc_Info()
viewDetails( )

Figure: Class
Diagram

28 | P a g e
 USED PRODUCTS STORE 201
1

4.0System Design
System design is a solution, a ‘how to’ approach to the
creation of a new system. It provides the understanding
and procedural details necessary for implementing the
system recommended in the feasibility study. Emphasis is
on translating the performance requirements into design
specifications. Design goes through logical and physical
stages of development. Logical design reviews the
present physical system; prepared input and output
specifications; details the implementation plan; and
prepares a logical design walkthrough. The physical
design maps out the details of the physical system, plans
the system implementation, devises a test and
implementation plan, and specifies any new hardware
and software.

4.1 Database Tables

 Admin Login Table

Field Name Data Type Description

AdminId Varchar
Password Varchar
F_name Varchar
L_name Varchar
Contact Number
Dob Date
Security Question Varchar
29 | P a g e
 USED PRODUCTS STORE 201
1

Answer Varchar

 Comp_Id Table

Field Name Data Type Description

Comp_id Varchar
Password Varchar

Comp_acc_info Table

Field Name Data Type Description

Id Varchar
Total_size Number
Rem_size Number
Start_date Date
Last_Date Date
Counter Number

 Comp_Info Table

Field Name Data Type Description

Comp_Name Varchar
Id Varchar
Password Varchar
Email Varchar
Address Varchar
DOJ Date
30 | P a g e
 USED PRODUCTS STORE 201
1

Security_que Varchar
Answer Varchar

5.0Conclusion
The project Online Advertisement Management
System (TAMS) is for computerizing the working in
advertisement. The software takes care of all the
requirements of a company details and is capable to
provide easy and effective storage of information related
to advertisement .
It generates performance reports of company details. The
system also provides the facility of backup as per the
requirement.
This system (OAMS) provides online storage/ updates
and retrieval facility. This system promises very less or no
paper work and also provides help to customer of latest
product information available on market. In this system
everything is stored electronically so very less amount of
paper work is required and information can be retrieved
very easily without searching product information of
different site and user does not registers for watching
the information on site.

6.0Bibliography
• HTML: Complete Reference
• www.w3schools.com

31 | P a g e
 USED PRODUCTS STORE 201
1

• Various e-books and tutorials provided on Internet

• www.asp.net
• www.wikipedia.org
• www.learn-sql-tutorial.com
• www.learn-xml-tutorial.com

32 | P a g e