Flee Bazaar

FLEA BAZAAR
SYNOPSIS
SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 1

FLEA BAZAAR
1. SYNOPSIS
Flea bazaar is a web-based a system for shopping specifically designed to facilitates both
software sellers and buyers. Through this software sellers can post and sell their products
and customers can buy and search for their software’s of different type the customer can
search items based on category. In this seller, buyers can do their job easily. In the client
can find items, can see the video running, the rating of each software, categorized view of
product, can post quires, and view the replies about a product under one roof. In those 4
type users –users, buyers, marketing agents, vendors can work jointly under one software
according to needs.
Front end – asp.net 2012
Back end – Microsoft sql server 2008

FLEA BAZAAR
INTRODUCTION

FLEA BAZAAR
2. INTRODUCTION
Project entitled- “WWW.FLEABAZZAR.COM” is developed for the management of
malls and shops in virtual environment, .FLEABAZAAR is the site which helps the
CUSTOMERS to view shops in that mall, purchase products. The VENDORS to sell
their products And the VENDORS to manage shops that are residing in the tower, etc
through internet. Adamtower is name of shop by a vendor (virtual shop)in this site.
Through this site any vendor having a shop or having a mall can register and sell their
product through internet and world can watch it and can buy just by a click. As like this
many vendors all over the world can register in this shop and can add their products to
the site and can sell them. This project also helps to perform transaction easier, faster and
safer. Details about transaction are also available at any time. This makes it more safe
and accurate. The design of the system is such a way that it is easy to reconfigure and add
more features easily. Interactive user(vendor and customer) interface helps users to easily
use the system without any guide or training . Implementation of the concerned system
enables the use of a fully system controlled Management in the activities of the
Shopping. The main advantage of using such system is Customers can visit each shops by
category or we can say brand they needed and Purchase products easily. The customer
can shop different products they needed from different shops which are in different part
of the world and efficient billing takes place. Visiting each shop by different vendor’s
customers can buy products easily. They can choose more effective products.

FLEA BAZAAR
ORGANIZATION PROFILE
EDUKSHEKTHRA is a Information Technology consultancy and
software development company that has been providing Network Infrastructure
development and consultancy services in enterprise class networking to customers
worldwide for over a decade.
Managed and staffed by IT professionals who have years of cross platform

experience, EDUKSHEKTHRA has what it takes to deliver break-through solutions
in Software Development, Project Management, System Architecture Design,
Database Design, System Administration, Business Process Improvement, Enterprise
Resource Planning, Embedded Technologies, Web Technologies, Database
Warehousing, Wireless Applications, e-Government and e-Commerce.
Dependable Outsourcing Partner
As your outsourcing partner,EDUKSHEKTHRA will bring you world-class

processes and global expertise in application development, in conformity with
industry best practices, so as to enhance the value of your application portfolio and
help you ride the crest of every successive wave of technological advancement.
EDUKSHEKTHRA will ensure proper requirements capture and evaluation,

continuous project monitoring and regular reporting to achieve the multiple
objectives of reduced cycle times, speedy product delivery, lower cost of ownership,
better risk mitigation and faster return on investment to clients.
Our portfolio of reusable frameworks and components can be adapted to suit clients?
Requirements with minimum customization, so we do not have to re-invent the
wheel every time. This ensures speedy product delivery and faster time to market.
Our unflinching commitment to continuous process improvement and our holistic
approach to quality will ensure measurable benefits to our clients by way of cost
savings, productivity increases and speed in achieving business goals.

FLEA BAZAAR
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENTS
Processor requirements: Dual core
Clock speed : 500 MHz
System bus : 32 bit
Hdd : 1.2 Gd
Key board : 104 digits
Mouse : I ball
SOFTWARE REQUIREMENTS
Operating system : windows 8
Front end : asp.net 2012
Back end : Microsoft sql server 2008

FLEA BAZAAR
SYSTEM ANALYSIS

FLEA BAZAAR
3.SYSTEM ANALYSIS
3.1 EXISTING SYSTEM
The existing system contains outdated contents and technologies. It has lot of difficulties
and draw backs. The users have to go through number of sites for their needs. In existing
systems downloading is only possible and in most cases their only two users are present
an admin and a user.
Draw backs
1. Most of the operation is done manually. So it is time consuming and costly
2. The site contains no advertising methods
3. The vendors are called through advertising through newspaper or through an external
source
3.2 PROPOSED SYSTEM

Proposed system provides increased client satisfaction by boosting support and service
level to 24 hours. The proposed system is developed in such a way that to overcome the
drawbacks of existing system.
FEATURES OF THE PROPOSED SYSTEM
Since it is a Web-Based application, it is very user-friendly.
It supports networking.
It supports multi-user, multi-tasking.
It provides good security.
It handles large amount of records correctly without any corruption.
It is RDBMS. So we can set relations to other tables.
“FLEABAZZAR.COM” is a complete site which performs all the activities of a

Shopping Complex in virtual environment.
This system contains two main modules.

FLEA BAZAAR
1.Administration
Administractor has overall control for the software.he manages the vendor and
customers.Vendors first contact the adin for posting their products .only after the
administractors varification the vendor and normal user can acess the system.he provide
valid user name and password to the vendors.ADMIN have role to add and delete
Vendors,customers,products,reply enquiries of customers about customers.main modules
of admin are
*Authorize and control Vendors
*Anthorize and control users
*Providing Productwise and Vendor wise sales Report to Vendors
*Delete product if needed
*change password
2 .Vendor management
vendor posts his products in system after adimin varification.he add his products with its
all details and add advertaisement schemes to make product attactive to user.This system
consists of lot of advertaisement methods like adding vedios ,photos etc to add marketing
tecnics.the normal user can post qurories about that product and vendor have provision to
reply to them based on their products
main modules of vendors are
*Vendor registraction and Login
*Add product and details
*Marketing products
*Payment and Offer schemes
*Deleting Products
*Password change
*Change password

FLEA BAZAAR
3.Customer
Customer is the end user of this software.he can login computer using his username and
password.The main modules of user are
*.User registraction and login
*Searching products based on Productwise,CostWise,Companywise
*Viewing Products
*Post quories to Admin and Vendor
*Manageing Cart provided to Customer
*Manageing his payment schemes like credit card or cash on delivery
*Change password
3.3 FESIBILITY SYUDY

It is a procedure that identifies, describes and evaluate systems and select best system for
jobes.An estimate is made of weather the identifies user may used. It list system proposal
according to its workability, Impact on the organization ability to meet user need of use
of resource. The objective of feasibity study is not only to solve the problem but to
acuquire a since of its scope. The 3 consideration involved in feasibility analysis is
 Economical feasibility
 Technical feasibility
 Behavioral feasibility
3.3.1 ECONOMIC FEASIBILITY

Economical analysis is most frequently used method for evaluating the effectiveness for
candidate system. It is more commonly known as cost benefit analysis. It’s the procedure
to determines benefits and saving that are expected from candidate system and compare
them with cost
The advantages are
 Decrease the work load

 Less expensive
 Less time consuming

FLEA BAZAAR
3.3.2 TECHNICAL FEASIBILITY
Technical feasibility checks where the work done using the current equipment. The
assessment of technical feasibility must be based on the outline of system requirement in
terms of input, output, files, programs, procedures and staff. This can be quantified in
terms of volume of data,trends,frequent updating etc having a identified outline ,the
investigators must go on to suggest the type of equipment required, methods of
developing the systems and methods of running system.
There are number of technical issues
 Avoid duplication
 High security
3.3.3 BEHAVIORAL FEASIBILITY
People are inheritantly resistant to change and computers have been known to facilitate
change. Staff and user react positively as computer application will decrease workload.
As a result this new system gets approval from the employee. New system issue friendly
since training is not needed.

FLEA BAZAAR
REQUIREMENT ANALYSIS

FLEA BAZAAR
REQUIREMENT ANALYSIS
The requirement analysis is a process of discovery, refinement, modeling
and specification. Both the developers and customers take an active role in requirement
analysis. Requirement analysis is a communication intensive activity. Requirement
analysis can be divided into:
 Problem recognition
 Problem evaluation and synthesis
 Modeling
PROBLEM RECOGNITION
The conventional l product trading operated in partially web based manner.
Administration of product trading is a very tedious and time-consuming task.
The problem with the current manual system includes:
 Difficult to find out details.
 Only share buying occurs. Not possible to calculate profit or loss.
PROBLEM EVALUATION & SYNTHESIS

The online product trading open a new trading tecnic through web which make easier to
user and seller. The web has changed all that it has transformed this old-fashioned
process in to something closer to an exact science. An intranet web means the server and
clients are located in an organization.
 Reduce administrative overhead
 Mailing facility
 Users are allowed to know all details of their products with the help of advertising
agents
 One of the important features of the proposed system is its security.
 Users can easily process and buy their products needed

FLEA BAZAAR
MODELING
During software requirement analysis, we create models to be built to gain
better understanding of the actual logical entities to be built. The following are the roles
of models in requirement analysis.
 The model helps analyst to understand information, function and behavior of the
system.
 The model becomes the main reference for review to determine completeness,
consistency and accuracy of the specification.
 The model becomes fountain for design.

FLEA BAZAAR
SYSTEM DESIGN

FLEA BAZAAR
SYSTEM DESIGN
System design is the solution to the creation of a new system. This
phase is composed of several systems. This phase focuses on the detailed implementation
of the feasible system. It emphasis on translating design specifications to performance
specification.
DATA DESIGN
Data design creates a new model of data or information that is
represented at a high level of abstraction the structure of data has always been an
important part of software design. The data design activity translates these elements of
requirement model into data structure at the software component level. In actuality, the
design of data begins during the creation of analysis model.
The database modeling involves Normalization of the database

structure so as to avoid data redundancy. The different levels of normalization are first
level, second level and third level. Normally normalization up to third level is followed.
ARCHITECTURAL DESIGN
Architectural design is a comprehensive framework that
describes its form and a structure- its components and how they fit together. Architectural
design, a software component can be something as simple as a program module, but it
can also be extended to include database and “middleware” that enable the configuration
of a network of client and servers. The properties of components are those that
characteristics that are necessary to an understanding of how the component interacts
with other components. Architectural design focuses on the representation of the structure
of software components, their properties and interactions.
The entire project is going to be developed using N-tier

architecture. The methodology includes component based development. The software is
divided in to three components. The presentation layer, business layer and data layer. The
presentation layer will concentrate only on the user interface while business layer will
deal with the common business rule. This will help in creating independent business
components which can be used in different projects and thus helps in reusability of the
components.

FLEA BAZAAR
PROCEDURAL DESIGN
Procedural design or component level design occurs after data,
architectural and interface designs must be translated in to operational software. The
procedural design for each component, represented in graphical, tabular or text-based
notation, is the primary work product produced during component level design.
INTERFACE DESIGN
Interface design creates an effective communication medium
between the computers and human. Different interface designs are:
INPUT DESIGN
The input design is the link between the information system and
the user. It comprises the developing specification and procedures for data preparation
and those steps are necessary to put transaction data into a usable form for processing
data entry. The activity of putting data into the computer for processing can be achieved
by inspecting the computer to read data from a written or printed document or it can
occur by having people keying the data directly in to the system. The design of input
focuses on controlling the amount of input required, controlling errors, avoiding delay,
avoiding extra steps and keeping the process simple.
The system needs the data regarding the asset items, depreciation
rates, asset transfer, and physical verification for various validation, checking, calculation
and report generation. The error raising method is also included in the software, which
helps to raise error message while wrong entry of input is done.
OUTPUT DESIGN
Computer output is the most important and direct information
source to the user. Output design is a process that involves designing necessary outputs in
the form of reports that should be given to the users according to the requirements.
Efficient, intelligible output design should improve the system’s relationship with the
user and help in decision making. Since the reports are directing referred by the
management for taking decisions and to draw conclusions they must be designed with
almost care and the details in the reports must be simple, descriptive and clear to the user.
So while designing output the following things are to be considered.
 Determine what information to present
 Arrange the presentation of information in an acceptable format
 Decide how to distribute the output to intended receipts

FLEA BAZAAR
CODING

FLEA BAZAAR
CODING
Coding is often used to provide that identification. Codes are unique usually
briefer than names or descriptions. Knowledge of codes and coding techniques is
essential to the system’s analyst. The ability to interpret codes, evaluate coding schemes,
and devise new or improved codes is important skills. Some codes to us from external
sources. The requirement for codes on external reports does not necessarily mean that we
must use those same codes for internal purpose. Coding a program is the actual writing of
computer programs. These instructions will be translated into machine code and followed
by the computer; they should follow the steps of the program logic plan.

FLEA BAZAAR
SYSTEM TESTING

FLEA BAZAAR
System Testing
System testing is the stage of implementation highly aimed at ensuring that the
system works accurately and efficiently before the live operation commences. Testing is
vital to the success of the system. The primary objective of testing is to derive a set of
tests that has the highest likelihood for uncovering defects in the software. The system
test in implementation should conform that all is correct and an opportunity to show the
users that the system work as expected. It accounts the largest percentage of technical
effort in the software development process. Testing phase in the development cycle
validates the code against the functional specification.
There are two categories of test case designing techniques. They are
 White Box Testing
 Black Box Testing
White box is a test case design method that uses the control structure of the procedural
design to derive test cases. Using the white box testing methods, we derived test cases
that guarantee that all independent paths within a module have been exercised at least
once. This testing should
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.
Black box testing might be called testing in large.
In functional testing, the software or module to be tested is treated as a black
box and the test case is decided based on specifications of the system or module. So this
testing is also called black box testing. It tests the external behavior of the system.
Black box testing is done to find incorrect or missing function, interface errors,
errors in external database access, performance errors and initialization and termination
errors.
The specification states what the program should do and how it should perform
under various conditions used. Test cases are developed, that will result in the execution
of every instruction on the program or module.
Another strategy of the software testing may be envisaged by moving outward

along the development spiral. Unit testing begins at the vertex of spiral and concentrates
on each unit of the software as implemented from the source code.
Testing progress by moving outward along the spiral to the integration testing
where the focus is to design and construction of the software architecture. Taking
another turn out of the spiral, we finally encounter validation testing.

FLEA BAZAAR
Unit Testing
In unit testing each module of the project is individually tested. Unit testing
focuses verification efforts and small unit of software design in the module. This is the
first level of testing. In this testing of each module and the integration of the overall
system is done. This testing is carried out during the programming stage itself. In this
testing step, each module is found to be working satisfactorily as regard to the expected
output from the module. There are some validation checks for the fields. It is very easy
to find error and debug the system.
Unit testing heavily make use of white box testing strategies exercising
specific paths in a modules control structure to ensure complete coverage and maximum
error detection. Unit testing focuses on modules to locate errors. The test cases needed
for unit testing must exercise each condition and option. If the module receives input or
generates output test case are needed to test the range of values expected including valid
and invalid data.
After coding, each dialog was tested and run individually. All the
unnecessarily coded statements were removed and it was endured that all the
functionalities worked as expected. Any logical errors found were corrected.
Integration Testing
Integrated testing is a systematic testing that can be done with sample data.
The need for the integrated test is to find the overall system performance. In integration
testing, the relationship between the modules is tested. For this purpose, test cases are
developed for each condition or combination of inputs. By examining the results it can
be determined whether the program performs according to its specified requirements. In
this project the modules that are specified in unit testing are testing are tested for their
relationships.
Black box test case design techniques are the most prevalent during
integration. Integration testing is the systematic technique for constructing the program
structure by condition tests to uncover error associated with the interfacing. Many test
modules are combined into subsystems, which are then tested. Rigorous integration is
conducted to make the application free for any interface errors that may occur during
transactions. Integration testing is a verification of the interface among system parts.
Integration test addressing the issues associated with the dual problems of verification
and program construction.

FLEA BAZAAR
Validation Testing
After the culmination of black box testing, software is completely assembled
as a package, interfacing errors have been uncovered and corrected and final series of
software validation tests begin. Validation testing can be defined as many, but a single
definition is that validation succeeds when the software functions in a manner that can be
reasonably expected by the customer. Validation refers to the process of using the
software in a live environment to find errors. During the course of validation system
failure may occur and the software will be changed.
System validation checks the quality of the software in both simulated and live
environments. First the software goes through a phase in which errors and failures based
on simulated user requirements are verified and studies. The modified software is then
subjected to phase two in the actual user’s site or live environment. Validation testing
provides the final assurance that the software meets all the functional, behavioral and
performance requirements.

FLEA BAZAAR
IMPLEMENTATION

FLEA BAZAAR
IMPLEMENTATION
Implementation includes all those activities that take
place to convert from the old system to the new. The old system consists of manual
operations, which is operated in a very different manner from the proposed new system.
A proper implementation is essential to provide a reliable system to meet the
requirements of the organizations. An improper installation may affect the success of the
computerized system.
Implementation Methods:
There are several methods for handling the implementation and
the consequent conversion from the old to the new computerized system.
The most secure method for conversion from the old system to
the new system is to run the old and new system in parallel. In this approach, a person
may operate in the manual older processing system as well as start operating the new
computerized system. This method offers high security, because even if there is a flaw in
the computerized system, we can depend upon the manual system. However, the cost for
maintaining two systems in parallel is very high. This outweighs its benefits.
Another commonly method is a direct cut over from the existing

manual system to the computerized system. The change may be within a week or within a
day. There are no parallel activities. However, there is no remedy in case of a problem.
This strategy requires careful planning.
Implementation Plan:
The implementation plan includes a description of all the
activities that must occur to implement the new system and to put it into operation. It
identifies the personal responsible for the activities and prepares a time chart for
implementing the system. The implementation plan consists of the following steps:
 List all files required for implementation.
 Identify all data required to build new files during the implementation.
 List all new documents and procedures that go into the new system
 Equipment acquisition & installation

 System conversation
 User training
 Personnel needs

FLEA BAZAAR
SOFTWARE MAINTENANCE

FLEA BAZAAR
SOFTWARE MAINTENANCE
The maintenance phase of the software cycle is the time in which a Software product
performs useful work. After a system is successfully implemented, it should be
maintained in a proper manner. System maintenance is an important aspect in the
software development life cycle. The need for system maintenance is for it to make
adaptable to the changes in the system environment. There may be social, technical and
other environmental changes, which affect a system, which is being implemented.
Software product enhancements may involve providing new functional capabilities,
improving user displays and mode of interaction, upgrading the performance
characteristics of the system. So only through proper system maintenance procedures, the
system can be adapted to cope up with these changes. Software maintenance is of course,
far more than “finding mistakes”. We may define maintenance by describing four
activities that are undertaken to after a program is released for use.
The first maintenance activity occurs because it is unreasonable to assume that

software testing will uncover all errors in a large software system. During the use of any
large program, errors will occur and be reported to the developer. The process that
includes the diagnosis and correction of one or more errors is called corrective
maintenance.
The second activity that contributes to a definition of maintenance

occurs because of the rapid change that is encountered in every aspect of computing.
Therefore, adaptive maintenance- an activity that modifies software to properly interfere
with a changing environment is both necessary and common place.
The third activity that may be applied to a definition of maintenance occurs when
a software package is successful. As the software is used, recommendations for new
capabilities, modifications to existing functions, and general enhancements are received
from users. To satisfy requests in this category, preventive maintenance is performed.
This activity accounts for the majority of all effort expended on software maintenance.
The fourth maintenance activity occurs when software is changed to improve

future maintainability or reliability, or to provide a better basis for future enhancements.
Often called preventive maintenance, this activity is characterized by reverse engineering
and re-engineering techniques.

FLEA BAZAAR
APPENDICES

FLEA BAZAAR
APPENDIX – A (TABLES)
Table name: login
Primary key: userid

FIELD TYPE SIZE DESCRIPTION
Loginid int 10 Login id
Username varchar 20 User name
Usertype varchar 20 User type
Password varchar 20 Password

FLEA BAZAAR
Table Name: vendor details
Field Name Data Type Constraints Description
Vendorid Varchar(50) Primary key Id of the vendor
Vfname Varchar(50) notnull Vendor’s first name
Vlname Varchar(50) Notnull Vendor’s last name
Age Varchar(50) Notnull Vendor’s age
Gender Varchar(50) Notnull Gender of vendor
Address Varchar(50) Notnull Address of vendor
Ph1 Varchar(50) Notnull Phone number of vendor
Ph2 Varchar(50) Notnull Phone number of vendor
City Varchar(50) Notnull Name of vendor’s city
Postal code Varchar(50) Notnull Postal code of vendor
Country Varchar(50) Notnull Country of vendor
Email Varchar(50) Notnull Email id of vendor
Paypalid Varchar(50) Notnull Paypal id
status Varchar(50) Notnull status of vendor
Primary Key: vfname
Table Name: product

FLEA BAZAAR
Primary Key: pid
Pid Bigint Primarykey Id of the product
Pname Varchar(50) Noptnull Name of the product
Vendorid Varchar(50) Foreign key Id of the vendor
Status varchar(50) Notnull Status of product
Price Float Notnull Price of the product
Descriciption Varchar(50) Notnull About the product
Rating Bigint Notnull Rating of the product
Last_update_date Datetime Notnull Date of last updation
Stock Bigint Notnull Product stock
Shopping cost Money Notnull Total shop cost
Catid varchar(50) Foreign key Category name
Cityid Varchar(50) Foreign key Name of the city
Image Varchar(50) Notnull image
Table Name: category

FLEA BAZAAR
Primary Key: cname
Catid varchar(50) notnull Category id
Cname varchar(50) primarykey Category name
Table Name: keywords
Primary Key: keyword
Pid varchar(50) Foreign key Product id
Keyword Varchar(50) primarykey keywords
Table Name: cities
Primary Key: cityname
cityid varchar(50) notnull city id
Cityname varchar(50) Primary key Name of the city of vendor
Table Name: user profile
Uid Nvarchar(max) Primary name Customer name

FLEA BAZAAR
Email id Nvarchar(max) Notnull Email id of customer
Bio Nvarchar(50) Notnull Biography
B’day Nvarchar(50) Notnull Datetime
Image Nvarchar(50) Notnull Image of customer
Primary Key: uname
Table Name: order details
Primary Key: ordid
Ordid Varchar(100) Primarykey Order id
Uid Varchar(50) Foreignkey Name of the user shopped the

item
Pid Varchar(50) Foreignkey Id of the product
Qty Float Notnull Quatity of the product
Uprice Decimal(18,2) Notnull Unique price of a product
Cmts Varchar(50) Notnull Comments
Tot Decimal(18,2) Notnull Total price
Ostatus Varchar(50) Notnull Order status
Table Name: shipping_info
invid Varchar(50) Primary key Shipping details id

FLEA BAZAAR
Uid Varchar(50) Foreign key Customer name
Fname Varchar(50) Notnull Firstname
Lname Varchar(50) Notnull Lastname
A1 Varchar(50) Notnull Address of customer
A2 Varchar(50) Notnull Address of customer
City Varchar(50) Notnull City name of customer
Country Varchar(50) Notnull Name of country of customer
state Varchar(50) Notnull Name of the state
Pobox Varchar(50) Notnull Postbox id
Email Varchar(50) Notnull Email id of customer
Phnum Varchar(50) Notnull Phone number
Cmts Varchar(50) Notnull Comments by customers
Status Varcahr Notnull Status of products
Primary Key: invid
Table Name:user payment
Primary Key:payid
payid Varchar(max) Notnull Payment id

FLEA BAZAAR
Uname Varchar(max) Foreign key Username
Ordid varchar(max) Foreign key Total price
Table Name: Activities
Primary Key: actid
Actid Varchar(50) Primary key Activity id
Acfrm Varchar(50) Notnull Activity from(name of the

user done the activity)
Acto Varchar(50) Notnull Activity to(name of the

product done the activity)
Date Datetime Notnull Date and time
Acttype Varchar(50) Notnull Type of Activity
Image varchar(150) Allow Null Image
Posturl Varchar(50) Allow null Recent posts

FLEA BAZAAR
APPENDIX – B (DFD)
CONTEXT LEVEL(LEVEL0)
Request Response
User FLEE BAZAAR User

FLEA BAZAAR
Level1_Administrator

FLEA BAZAAR
LEVEL 2 _VENDOR

FLEA BAZAAR
LEVEL 3_CUSTOMER

FLEA BAZAAR
CONCLUSION

FLEA BAZAAR
CONCLUSION
Any system which has been in use for a number of years gradually,
decays become less effective because of the change in environment to which has to
adapt. For a time it is possible to overcome problems by amendments and minor
modification to acknowledge the need of fundamental changes.
Computerization was proposed as a solution to the problem of being

outdated with the fast present technologies. In the project, our aim is to maximize our
effort to computerize it accordingly that meet the entire user needs.
I successfully completed our project work on

“www.FLEABAZAAR.com” for trading of products through internet. Testing of the
whole system has been done with sample data and outputs obtained are according to the
requirements.
The efficiency of this System is found to be better than the existing

system in all respects. The system will be able to manage the all the details in an
efficient manner.

FLEA BAZAAR
BIBLIOGRAPHY

FLEA BAZAAR
BIBLIOGRAPHY
 Elias M Award, System Analysis and Design,

Galgottia Publications Pvt.Ltd 1991
 Beginning ASP.NET 3.0 Christ hart, chris Ulman,

David Sussman.
 Roger S Pressman, Software Engineering- A

practitioners Approach, McGraw Hill Inter
Editons 1991

Flee Bazaar

Uploaded by

Copyright:

Available Formats

Flee Bazaar

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Flee Bazaar

Uploaded by

Copyright:

Available Formats

FLEA BAZAAR

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 1

Front end – asp.net 2012

Back end – Microsoft sql server 2008

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 2

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 3

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 4

Managed and staffed by IT professionals who have years of cross platform

Dependable Outsourcing Partner

As your outsourcing partner,EDUKSHEKTHRA will bring you world-class

EDUKSHEKTHRA will ensure proper requirements capture and evaluation,

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 5

Clock speed : 500 MHz

System bus : 32 bit

Key board : 104 digits

Front end : asp.net 2012

Back end : Microsoft sql server 2008

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 6

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 7

1. Most of the operation is done manually. So it is time consuming and costly

2. The site contains no advertising methods

3.2 PROPOSED SYSTEM

FEATURES OF THE PROPOSED SYSTEM

Since it is a Web-Based application, it is very user-friendly.

It supports multi-user, multi-tasking.

It provides good security.

It handles large amount of records correctly without any corruption.

It is RDBMS. So we can set relations to other tables.

“FLEABAZZAR.COM” is a complete site which performs all the activities of a

This system contains two main modules.

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 8

*Authorize and control Vendors

*Anthorize and control users

*Providing Productwise and Vendor wise sales Report to Vendors

*Delete product if needed

main modules of vendors are

*Vendor registraction and Login

*Add product and details

*Payment and Offer schemes

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 9

*.User registraction and login

*Searching products based on Productwise,CostWise,Companywise

*Post quories to Admin and Vendor

*Manageing Cart provided to Customer

*Manageing his payment schemes like credit card or cash on delivery

3.3 FESIBILITY SYUDY

3.3.1 ECONOMIC FEASIBILITY

The advantages are

 Decrease the work load

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 10

There are number of technical issues

3.3.3 BEHAVIORAL FEASIBILITY

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 11

SWAMY SASWATHIKANANDA COLLEGE, POOTHOTTA 12

 Problem evaluation and synthesis

The problem with the current manual system includes:

 Difficult to find out details.

 Only share buying occurs. Not possible to calculate profit or loss.