E-BROKER

Supervised by: Mr
Developed by: GENIUS

Department of Computer Sciences

COMSATS Institute of Information
Technology
Year 20
DEDICATION

i
 To My Dearest and Loving Parents, My Family Members

And my Respected Teachers

Who Motivated, support and encourage me

At every step of my Life.

Acknowledgments

First of all I am very thankful to my almighty ALLAH who gave me the courage
and patience to complete this difficult task.

I would like to express my profound gratitude, most sincere appreciation and

special thanks to my project supervisor Mr for their fabulous suggestions,

ii
invaluable advice and continues encouragement through the completion of
project.

I must thank to all my friends and teachers who did extend their invaluable
support and priceless suggestions during working on project.

Finally I wish my deepest appreciations to my respectable parents and family

members who are the strength of my life, who have motivated me in all
phases of m life, for their long loving support, their patience, there
understanding and their prayers.

GENIUS

BS (IT)

PREFACE
This document has been divided into logical chapters to aid easy navigation
through the material. The development of electronic broker has gone through
a series of sequential steps to its final form, which is explained by sufficiently
detailed chapters as follows.

• Chapter 1 ------------ Introduction

Explains the introduction of software, proposed solution and problems
in the existing system. Moreover this chapter has key concepts about
software and technologies, which are used to develop this system.

Chapter 2 ------------ System Analysis

iii
 Covers data analysis, system requirement and system functions. This
chapter also provides basic functionality of software through diagrams
and description.

• Chapter 3 ------------ System Design

Covers the design of system using DFDs, STDs and entity relationship
diagram.

• Chapter 4 ------------ Systems Development

Covers implementation techniques and technology used in the system.

• Chapter 5 ------------ Quality Assurance & Configuration

Management
This chapter covers testing of the system.

• Chapter 6 ------------ System Evaluation & Future Enhancement

This chapter covers whether the goals and objectives set out for the
system has been met or not.

• Chapter 7 ----------- User Guide

All information for the Guidance of the user is given in this chapter.

ABSTRACT

Electronic Broker System is part of a dynamic commerce strategy that allows

buyers and sellers to come on common platform and undergo the buying-
selling transaction process under the bidding mechanism.

Following the growing demand for user-friendly systems, dedicated to help

people (not necessarily skilled with computers) solve selling and purchasing
iv
in easier and convenient way on web. The aim of this project is to design and
implement a web-based electronic broker that can take the user’s input of
products/items and then search for them in database and can perform the
buying process by placing bid on the product/item of desire. E-Broker will
entertained the highest bid placed against any product/item and notify both
the buyer and seller that a bid has been placed and it is highest bid (provided
if it is highest by that time). Similarly a person can also put his/her product
for sale on e-broker. This project will help a lot to minimize the time being
consumed and give the exact output of user demand.

SUMMARY

Computer is playing a vital role in calculating and managing the every kind of
problems in all organizations worldwide. Computer is being used in every
sphere of life. Its uses are increasing day by day. It seems that after a few
years life would useless without computer as well an internet. A system which
utilize electronic means especially computer, is a computer-based system. As
computer is one of the power full tools used in present society and it has a
strong impact on human lives. That is why the use of computer-based system
is increasing day by day and is called computerization

v
There is not even a single field that is beyond the grip of computer and
internet is a great source of information. Given the rapid growth and success
of public information sources on the World Wide Web, it is increasingly
attractive to extract data from these sources and make it available for further
processing by end users and application programs.

The increase in the number of internet user has led to an increase in the
ways internet is used. The application used in this thesis will eventually lead
to an increased usage of internet for buying and selling products on the
WWW, using bidding mechanism. Thorough this web-based electronic broker
system the status about the purchasing and selling items from the web
market is provided in an efficient manner. The speed and processing time of
the purchasing and selling are quick enough thus giving better data
manipulation an d correct calculated results.

PROJECT IN BRIEF

Project Title: E-Broker

Objective: To provide with the effective and efficient electronic

Broker Solution that can be used by any company or

Individual.

Submitted By: GENIUS

Supervised By:

Duration: September 20-March 20

vi
Languages: ASP, Java Scripts & HTML.

Tools: Dreamweaver MX, Photoshop, MS-Office XP, MS Visio

Operating System: Windows XP

TABLE OF CONTENTS

Chapter 1 Introduction………………..…………………

1.1 Project Description

2

1.2 Scope of the Project

2

1.3 Objective of the Project

3

1.4 Software Process Model

3

1.5 Impact on Society 3

1.6 Overall Description

4

1.6.1 Product Perspective 4

vii
 1.6.2 Product Feature
5

1.6.3 Product Users and Characteristics

5

1.2 Monitoring Activities

6
1.3 Project Modules
6

Chapter 2 System Analysis……………………………….

2.1 Data Analysis

8

2.1.2 System Requirements

8

2.1.2.1 Clients, Customers and Users

8

2.2 Functional Requirement 8

2.3 Non Functional Requirement

11

2.4 Proposed Solution 13

Chapter 3 System Design………..……………………………

3.1 Introduction 15

3.2 Architectural Design 15

3.3 Data Flow Diagram 17

3.4 Entity Relationship Diagram 21

3.5 Database Design 22
3.6 Interface Design 26

viii
Chapter 4 System Development……..………………………

4.1 Introduction 29

4.2 Hardware and Software Requirement 29

4.3 Software Selection 30

4.4 Tool Selection 30

4.5 Implementation Activities Involved In My Project 32

Chapter 5 Quality Assurance and Configuration Management…

5.1 Introduction 40

5.1.1 General Type of errors 40

5.2 Testing Levels 41

5.2.1 Unit Testing 41

5.2.2 Integration Testing 41

5.2.3 System Testing 41

5.2.4 Regression Testing 41

5.3 Testing Plans 42

5.4 E-Broker Testing 43
5.5 Testing Strategies 44
5.6 Test Cases 44

Chapter 6 System Evaluation and Future Enhancement…

6.1 Introduction
48

6.2 Evaluation of the software

48
6.3 Features 49
6.4 Future Enhancement

50

ix
Chapter 7 The User Guide……...……...………………………

7.1 Introduction 52
7.2 External Interface Requirements
52

7.3 Screenshots of E-Broker System 53

References & Bibliography 63

CHAPTE
R
x
 1

INTRODUCTION

MAIN TOPICS COVERED

• Project Description

• Scope of the Project

• Objectives of this Document

xi
 • Software Process Model

• Impact on Society

• Overall Description

• Management Process

Chapter 1

INTRODUCTION

1.1 Project Description:

The basic aim of this project is to design and implement a web-based buying
& selling Electronic Broker System which is part of a dynamic commerce
strategy that allows buyers and sellers to come on common platform and
undergo the buying-selling transaction process using bidding mechanism.
xii
Following the growing demand for user-friendly systems, dedicated to help
people (not necessarily skilled with computers) solve purchasing and selling
in easier and convenient way on web. The aim of this project is to design and
implement a web-based electronic broker that can take the user’s input of
products and then search for them in database and can perform the
buying/selling process through lucid bidding mechanism.

This system will be used to guide many users in choosing online products,
helping them in comparing the different product offers, in order to reach an
optimal satisfaction for the customer in synthetic and coherent way.

1.2 Scope of the Project:

Electronic Broker system is an application that is capable of providing the
facility to its users to buy the products which are available on the system
through placing highest bid on item/product. Similarly it also facilitates the
sellers which can place their product for sale on e-broker by adding the item
with all the necessary information e.g. asking price, image of product, its
description etc to e-broker. Users of the system can signup/register
themselves in order to buy/sell the products. Products available for sale on e-
broker are arranged in categories to add to ease of the users of the system.
Along with that the nine Hot Products i-e the products with the highest
number of bids are shown on the main page and top three items which are
newly added to the system are shown in what’s new corner.

1.3 Objectives of the Project:

• To facilitate the users to buy and sell products through bidding.
• To reduce the time consumption.
• Provide with easy access facility of products.
• Better availability of information of online products.
• Easy administrative control of system.

1.4 Software Process Model:

xiii
I used the waterfall process model for my project of e-broker as it suits it
best.

The waterfall model is a software development model (a process for the

creation of software) in which development is seen as flowing steadily
downwards (like a waterfall) through the phases of requirements analysis,
design, implementation, testing (validation), integration, and maintenance.
The term was introduced in 1970 by W. W. Royce.

Usage of the waterfall model

The unmodified "waterfall model". Progress flows from the top to the bottom,
like a waterfall.

To follow the waterfall model, one proceeds from one phase to the next in a purely
sequential manner. When and only when the requirements are fully completed, one
proceeds to design. The software in question is designed and a "blueprint" is drawn for
implementers (coders) to follow — this design should be a plan for implementing the
requirements given. When and only when the design is fully completed, an
implementation of that design is made by coders. Towards the later stages of this
implementation phase, disparate software components produced by different teams are
integrated. After the implementation and integration phases are complete, the software
product is tested and debugged; any faults introduced in earlier phases are removed here.
xiv
Then the software product is installed, and later maintained to introduce new
functionality and remove bugs.
Thus the waterfall model maintains that one should move to a phase only when its
preceding phase is completed and perfected. Phases of development in the waterfall
model are thus discrete, and there is no jumping back and forth or overlap between them.

1.5 Impact on Society:

The main characteristic of the e-business world is that companies will
inevitably move more and more into a customer-centric paradigm in order to
increase competitiveness. Customer behavior cannot be accurately predicted
using traditional analytic methods like forecasting or budgeting. Instead,
companies seeking a competitive edge will investigate other kinds of
analytical methods based on, for example, heuristics and AI techniques. E-
broker system supports a natural way of knowledge based technologies. It
can facilitate the incorporation of reasoning capabilities within the business
application logic e.g. encapsulation of business rules within agent or modeled
organizations. It permits the inclusion of learning and self-improvement
capabilities at both infrastructures.

The opportunities for using e-broker in an e-business application are

enormous. For example, they can be used for online buying-selling
transaction, involving different parties in supply-chain network. Suppliers can
present their products on the web and e-broker system support a natural way
of knowledge based technologies.

In addition e-broker system can help address serious technological challenges

such as concerns about effective searching, security and privacy, and
effective use of interoperability between diverse business processes and
diverse information required to achieve tele-cooperation and global e-
commerce. E-broker system can carry out work on behalf of human
knowledge workers both on the supplier’s and customer’s behalf. A vision of
how agent-enabled, business-to- business e-ecommerce could provide an
unprecedented level of functionality to people and enterprises.

1.6 Overall Description:

1.6.1 Product Perspective:
xv
An e-broker system guide many users in choosing products, helping them to
select items they may recognize as important for their need and comparing
on these basis the different product offers, in order to reach optimal
satisfaction of the customer. And all the required information is presented to
the customer in a very synthetic and coherent way. Similarly users can
present their products/item for selling purpose to a large target market.

1.6.2 Product Features:

The following features are provided by the software:

• Implementing a user interface, to process user’s queries, access the

database and supply the user with product information.
• Store the information in database, in order to feed the system with the
data to be presented to the user/customer.
• Notify the buyer if his/her bid is highest for an item.
• E-broker announces if the particular buyer wins certain bid on seller
acceptance.
• Provide efficient searching facility through DB for specific or all items.
• Implements an administrator console to control the whole E-broker
system

1.6.3 Product Users and Characteristics:

i. Site Visitors :
The main users of the system are the site visitors who use the
system for gathering information of the products to buy and sell through
bidding process. E-broker will also help the visitors in order to search for
relevant products.

ii. Administrator:
Administrator handles the whole e-broker system.

xvi
 • He manages the bids that are placed by the users of the system.
He can view and cancel the bids.
• Administrator can add new admin users.
• He controls all the registration of the users of the system.
• Can keep track of all the IP Logs for security purpose.
• Can keep a look on all the sales going on.

1.7 Monitoring Activities:

Project is monitor in three ways:

• Initially project is monitor by the supervisor.

• Project committee or internal supervisor.
• Finally external supervisor.

1.8 Project Modules:

For the project “e-broker” the major modules are subdivided into smaller
logically independent sub modules, which gives, desired output when work
together. The following factors are considered.

• User Registration
• Bid Placement
• Item/Product Search.
• Administrative users’ Security & Administration

CHAPTE
R

xvii
 2

SYSTEM ANALYSIS

MAIN TOPICS COVERED

• Introduction

• Data Analysis

• Functional Requirements

• Non-Functional Requirements

• Proposed Solution
xviii
Chapter # 2
System Analysis

2.1 Data Analysis

2.1.2 System Requirements
Requirement analysis involves understanding the problem, establishing the
system should provide, and the constraints under which the system must
xix
operate. A good analyst leads to a good final product, and poorly analyzed
system will disappoint the user and bring problem to the developer

2.1.2.1 Clients, Customers and Users

This generic E-Commerce application may be used by any
company/individual who wants to start his online business. So these will be
the clients of the e-broker application. Its users are the employee of that
company and the visitors of the system who want to do the e-commerce
transactions.

2.2 Functional Requirements

Requirements analysis is the first step towards the software development.
One can’t build any good system without doing proper analysis. The
robustness and reliability of the software highly depend upon it. The main
objective of this phase is to identify the requirement of the software. Primarily
problems are identified, and then a solution is proposed. For the project “e-
broker” the major modules are subdivided into smaller logically independent
sub modules, which gives, desired output when work together. The following
factors are considered.

• User Registration
• Buying/Bid Placement
• Selling Product.
• Browse Listings
• Administrative users’ Security & Administration

xx
 Electronic Broker

User Buying/Bid Administration

Registration Selling Product Browse Listing
Placement & Security

2.2.1 User Registration:

Electronic Broker system will be capable of registering the users of the
system through the process of filling up a form with basic information about
the user for example the email of the user, family name, given name,
address, city, state, Postal Code, Country and password. This whole process is
given the name of signup with system. As a user sign up with e-broker s/he
will be able to buy and sell products and items of their own choice through
the mechanism of bidding. He will be able to edit his registration information
and can view the specific items s/he put for sale. All the information
regarding the user’s registration is stored in the database of the electronic
broker.

2.2.2 Buying / Bid Placement:

Electronic Broker provide a very simple and user friendly procedure to buy a
product/item by placing a bid on that item. The whole process is like that the
user has to login into the system through the user specific email and
password combination s/he is shown the home page where the user can view
the hot products and the newly added products. Along with that whole list of
the categories of the items are shown to him too. Now buyer/bidder can

xxi
select the product of his/her own choice and by clicking on the image of the
product the buyer will be redirected to the page where s/he can view the old
bidding history on that specific product, item name and the description of the
product. Now user can place bid of his own choice which must be greater
than the previous bid. If his/her bid is successful and seller is agreed to that
bid he will won that bid.

2.2.3 Selling Product:

E-Broker is very efficient in its working. The selling process is very convenient
in this system. The seller must have to register with the system in order to
sell his/her product. He has to login to the system with the seller specific
email and password combination and then he just has to click on the tabbed
link of sell products. As he click that link seller will be redirected to a page
where he can input the selling product’s information like item category, item
name, description, image, asking price and expiry date etc and then just click
the add button. His product will be added to the system for sale and will
immediately be displayed in home page’s “What’s New” corner.

2.2.4 Browse Listings:

The user of the system of electronic broker is facilitated by another very
handy option that s/he can view and browse all the products/items for sale
with electronic broker. Through this browsing mechanism the users of the
system can select the product/item of their own choice and need in very
interactive way.

On browse listing page the user of the system is provided with the
information about the product concerning the item image, item name, asking
price, current bid placed, the time of the bid placed and the date of the bid
placement. It also shows that “you are the current highest bidder” on any
specific item if you have placed the highest bid amount on any product.

xxii
2.2.5 Administration User’s Security &
Administration:
Electronic broker has infact two consoles one is the user console that I have
discussed above and other is the admin console. The admin console is
secured by the combination of the email and password combination so that
no unauthorized person can use that. The administrator of the system is fully
capable of administering the e-broker system by keeping track of all the bids
placed and the items placed for sale. He can track all the user’s registrations.
He can view and delete/inactive the any bid or item if there is something
wrong with that.

2.3 Non Functional Requirements

2. 3.1 Look & Feel Requirement

For every software Human computer interface is the most important
because user is not concerned how the things work, s/he is more
concerned about his/her ease, so the interface has to be made according
to user requirements. What do they like and what is convenient for them.

Consistency:
All forms should have a consistent format for menu selection, data display
and command input. All the titles are of same color and font. So that user
needs not to learn every screen.

Meaningful Feedback:

xxiii
Provide the user with visual feedback to ensure that two-way
communication between user and interface is established. Messages are
displayed to inform user about his/her work status.

User is not expected to memorize anything:

The user does not have to remember a list of things so that s/he can reuse
them in a subsequent form. Memory load should be minimized. For
example in placing a bid on an item for buying, existing products/items
are enlisted, and the user has to just click the option.

Minimum number of clicks required:

Minimum numbers of clicks are required to get the desired output. This
concept is used in whole application. The user just have to enter the
records, which are necessary, there is no need to fill out redundant
information.

2.3.2 Usability Requirements

Usability is an attempt to quantify “user friendliness”. System is easy to
learn and operate. For this, the users do not have to wade through
extraneous buttons/links. A very easy navigation approach is adopted.

Meaningful error messages are displayed in user understandable

language. An attempt has been made to reduce the amount of typing
required. Furthermore interaction with the interface is simple. For example
end users are very happy with the keyboard input because it saves their
time and they can make entries quickly whereas administrator is more
comfortable with mouse.

xxiv
2.3.3 Security Requirements
In order to filter data access with in the company employees all possible
steps have been taken. No employee or the software user is authorized to
view information not related to his/her job. For this, administrative
security is implemented.

As the main objective of the site is E-commerce, therefore, it must be

handled carefully to ensure security and reliability. For this purpose the IP
address of every user of the application who enter the system, is logged in
database.

2.3.4 Performance Requirements

Performance considerations encompass processing speed, efficiency,
through put, resource consumption and response time. In order to do this
secure and full transactions are ensured and graphics are optimized so
that they can be loaded fastly.

2.4 Proposed Solution

E-broker is being designed to compete with other broker companies that

have also chosen the path of e-commerce to keep their businesses alive.
By eBroker, broker companies increase their revenue and their customer
database. There are many benefits to converting the existing system
structure to a new e-commerce approach. Some of the benefits include
enjoying an increased market share, increased revenue, increased
customer satisfaction, create new business contacts, rapid turn around

xxv
times, more advertising recognition of the company as a leading provider
of bidding items.

CHAPTE
R

3
xxvi
System Design &
Configuration
Management

MAIN TOPICS COVERED

• Introduction

• Architectural Design

• Data Flow Diagram

xxvii
 • Entity Relationship Diagram

• Database Design

• Interface Design

3.1 Introduction:

Design is a decision-making activity. The first activity in the development

phase of any project is design. Design works as a base for the proceeding
activities in the development life cycle. It is not possible to develop efficient
software without a good design.

There are two design strategies:

• Structural Design
• Object Oriented Design.

xxviii
The approach I have used is structured one. The design phase begins with the
requirement specification documentation is available. While the requirement
analysis is in the problem domain, the design phase is the first step towards
moving from the problem domain to the solution domain. In the system
design phase all the processes of the proposed system are discussed.

This means to identify that what are the different processes, how they will be
implemented and how they will interact with each other.

The database structure is also defined in the system design phase. The
primary key for the each table is mentioned and the relations between the
tables are defined. The design of a system built precisely according to it
completely satisfies the requirements specified in the requirement
specification documentation.

System design is a solution to a problem. Design demands the translation of

the requirements gathered during the analysis.

3.2 Architectural Design:

xxix
 Dynamic
Web
Pages
3- Web Server locates the instruction file in E -Broker System

p ts
i.e. HTML

cr i
4- Web Server Processes instructions w .r.t E-Broker System
P /S
AS
es
ut
ec
Ex

Server with E-Broker System 5- HTML Stream

Returned to

AL R Browser
1- Electronic Broker System on the
UR KE
Server Side
CT RO
I TE E-B
C H F
AR N O
SIG
DE `
en
t
li
2- User of E-Broker Requests o nC
webpage ser
rU
oke
Br
E-

6- Browser process HTML and displays the E -Broker Page

Developed By:
Nouman Ali

3.3 Data Flow Diagram

xxx
0 – Level DFD:

xxxi
 Re
gis
ter
/L
og

I-Level DFD:
in
C
re
Buyer

at
e
Sa
R esu le
lt s R s
eturn
ed
Br

Admin
ow
se
Th
ro
ug
h

R esul t
s R etu
ed rn Re

xxxii
su
Ta
ke
lts
P la

Bu
R
ce

ye
et
u
b

r/ rn
ite

Da
m

t
ids

s
/B
id

m
s/ Loo

Sy aBas
Se
k ite
lle
ste e
m in
r
E-Broker Sys

DB
in Pl
fo ac
V es
ie
w I te
S m
al
es
I te
m
D
is
pl
ay
C I te
on m
f ir
m s
Sa
le
R s
eg
is
Seller

te
r/
Lo
gi
n
 DFD
Resu
l ts R
et urn
ed

Admin

xxxiii
Re sul t
Re turn s
ed
Ta
ke
Bu
ye
r/
i te
Da

m
s
t

s
/B
id
Sy aBa

s/ Loo
Se
k i te
ll e
tem se

m in
E-Broker Sys

DB
ri
nf
o
 DFD
Re sul t
Re turn s
ed

Da
s
t
Sy aBa
Loo
k i te

tem se
m in

E-Broker Sys
DB
Pl
ac
V es
ie
w Ite
S m
al
es
I te
m

xxxiv
D
is
pl
ay
C I te
on m
fir
m s
Sa
le
R s
eg
is
Seller

t er
/ Lo
gi
n
 i n DB
k item
Loo
E-Broker Sys

tem se
Sy aBa
ids

t
s
Da
h
eb

g
ou rned
ac

r
Th ts R et u
R esul
Pl

se
w
ro
B
rn

xxxv
tu
Re
lts
su
Re
s
le
Sa
e
Buyer at
re
C
in
og
/L
er
g ist
Re
 3.4 Entity Relationship Diagram: (ERD)

CatName CatID

Category

1
ID Name Email Password

Have
Person Confirms
1 1
M

Bids Name
Name ID

M M
Status Item Exp Date ADMIN
1
M 1 1
Password

Has For

Items Place On
Active M ID
1 1
ID Seller Confirm Sale
1 1
1
Items Comp
Place
Listed Date
M M

Accepts Bids Monitor

1 M

Bid
Bid ID
Item

xxxvi
3.5 Database Design of E-Broker:

In database design of e-broker, the name and structure of all the data tables is described. The
structure of each table is described table is as follows:

xxxvii
ITEMS TABLE:
xxxviii
ADMIN TABLE:

xxxix
BID TABLE:

xl
xli
PERSON TABLE:

CATEGORY TABLE:

xlii
SALE ITEM:

xliii
SELLER TABLE:

3.6 INTERFACE DESIGN OF E-BROKER:

xliv
xlv
SITE MAP:

xlvi
 CHAPTE
R

System
Development

xlvii
 MAIN TOPICS COVERED

• Introduction

• Technologies used in System

• Implementation Activities Involved In My Project

Chapter 4
System Development

4.1 Introduction:

xlviii
Implementation is the activity of getting the design system is operation. The
new system may be total replacement of the existing system or it may be
major modification to the existing one. In either case proper implementation
is essential to provide a reliable system to meet the organization’s
requirements. It is planed worked and requires more attention of the system
designer.

Once the software design phase is accomplished then the designer moves
towards the implementation phase of the software in accordance with the
proposed system and design specification. The purpose of the
implementation phase is to transfer design into executable computer
software that may then be tested as a new system. For software development
it is necessary to identify functional requirements of the system. For the
system development, selection of software and hardware is vital for the
success of the system. The work is done according to the programming rules
that attempt to standardize code, developed by the programmers, and to
prevent dangerous or unsuitable construction in language.

4.2 Hardware and Software Environment:

One advantage of the advancement in the software field is that now when a
particular application is to be developed there are a number of tools and
technologies to choose from. Various competing companies come up with
enhancements and features so that the developer can select the set of tools
most suited for his requirement.

4.3 Software Selection:

One of the most difficult tasks after system design is to determine whether
particular software is capable of meeting the system requirements.
xlix
4.4 Tool Selection:
The implementation phase of the system is concerned with the tools and
resources used in the development and the major steps that are taken to
implement the system.

The selection of tool to use is decisive. The choice of appropriate tool is

essential for avoiding unnecessary complexity in the later stages of the
system life cycle. Therefore the following things have to be considered:-

• Operating System Selection

• Language Selection

4.4.1 Operating System Selection:

For the development of the system The Operating system I used is a window
XP running on Intel Hardware.

4.4.2 Language Selection:

ASP:
During its spectacularly successful life, Microsoft® Active Server Pages (ASP)
has grown from a simple scripting environment for creating dynamic Web
pages into a powerful and easy-to-use platform for fully-fledged Web
application development. In its latest incarnation, it provides a complete
solution for building almost any type of interactive user interface, as well as
for implementing extensive back-end processing operations.

As a language, ASP has powerful and speedy features that make it the best
language to code the background processing. I coded the ASP code using the
Macromedia Dreamweaver MX, which is very efficient and reliable software to
code ASP.

l
4.4.3 Technologies used in System:
The technologies used in E-Broker are:

• Adobe Photoshop 7.0

• Microsoft Visio
• Dreamweaver MX
• MS Access

Adobe Photoshop:
Adobe Photoshop is used for manipulating the images changing the sizes,
making the images transparent and changing the graphics used in designing
the web interface of e-broker.

Microsoft Visio:
Visio is the drawing package based on the green plastic drawing templates of
the past.

Rather than require the user to have excellent drawing skills, the user selects
pre-drawn shapes from the template and drag them to the drawing. I have
used Microsoft Visio for the development of different diagrams like:

• Data Flow Diagram

• Entity Relationship Diagram
• Architectural Diagram
• etc

li
Macromedia Dreamweaver MX:

Macromedia Dreamweaver MX was used for the development of the e-broker

system using ASP. Dreamweaver facilitates the development process very
much as it provide very handy coding environment with the facility of site
definition so that we can work with all the modules of the system with simple
clicks.

MS-Access:

Microsoft Access is used as a backend database as it is known for its

simplicity, efficiency and data storage. MS Access works with the ASP in a
very effective way. All the tables of the eBroker are developed, designed and
stored using MS Access, which works at optimum level with each other and
on individual basis.

MS Access is 100% compatible with the personal computer based on Pentium

Processor and Windows 2000 and XP. It utilizes the 32 MB of RAM for standard
starter database.

4.5 Implementation Activities Involved In

My Project:

• Story Boarding
• Graphics Designing
• Interface Designing
• Database Description
lii
4.5.1 Story Boarding:

Story Boarding is a special term which is mostly used in the website

development. In Storyboarding process a rough template or prototype of the
website is designed on paper i-e it is decided that what portion or module is
shown on which place on the face of website. As my project electronic broker
is a web application in which the buyers and sellers come together on
common place in order to execute to buying selling transactions and that
common platform is provided in the form of the website interface as front
end. So this front end should be attractive enough to compel the visitors to
go through the website of the electronic broker and buy the product of their
choice or if visitor is a seller then he can put his item for sale on the system.

So the storyboarding plays a vital role in the whole system of electronic

broker as the working efficiency, user attraction and the attraction all
depends on it; because it is the first impression of the system on the visitors.

4.5.2 Graphics Designing:

Electronic Broker is a web application so it is supposed to be the attractive

and appealing one. In order to do so the graphics of the web layout of the
electronic broker are developed using the Adobe Photoshop 7.0. All the
graphics of the electronic broker are fully optimized in terms of size and
weight so that they can be loaded fast on any browser and on any type of
internet connection. This will not cause the users of the electronic broker to
get frustrated by the system startup.

liii
4.5.3 Interface Designing:

The interface design of the electronic broker was of very importance as it was
the first thing with which the user of the system interacts as s/he logins to
the system. The interface of the electronic broker is very easy and user
friendly.

The interface designing of the system was developed by keeping in mind all
the points that were discussed in the storyboarding process.

4.5.4 Database Description:

Database of the electronic broker is of vital importance as all the data and
information regarding the electronic broker is saved in the database. So the
design of the database for the system was very crucial. The database of the
system is developed using the Microsoft Access. The tables formed in the
database for e-broker are:

4.5.4.1 TABLES OF DB:

• Categories
• Persons
• Items
• Bids
• Admin
liv
 • Seller
• Sale

4.5.4.2 Attributes of DB:

Category Table:
Following are the attributes of the Category table of the database:

• CatID
• CatName

Person Table:
Following are the attributes of the Person table of the database:

• ID
• Name
• Email
• Password

Item Table:
Following are the attributes of the Item table of the database:

• ID
• Name
• Status
• Expiry Date
• Bid count

lv
Bids Table:
Following are the attributes of the Bids table of the database:

• Bid ID
• Bid Item

Seller Table:
Following are the attributes of the Seller table of the database:

• ID
• Items Active
• Items Listed

Sale Table:
Following are the attributes of the Sale table of the database:

• ID
• Completion Date

Admin Table:
Following are the attributes of the Admin table of the database:

• Name
• Password

RELATIONSHIPS:

B/W ADMIN & BIDS:

lvi
 Bids M
Monitor
1
ADMIN

B/W PERSON & ITEM:

M M
Person Bids Items

B/W ITEM & BIDS:

Items 1
Placed On
M
Bids

B/W SELLER & BIDS:

Seller 1
Accepts
1
Bids

lvii
B/W SELLER & SALE:

Seller 1
Confirms 1
Sale

B/W PERSON & BIDS;

M
Person 1
Place Bids

B/W PERSON & SALE:

M
Person 1
Confirms Sale

lviii
B/W CATEGORY & ITEMS:

1 M
CATEGORY HAVE Items

B/W ITEMS & SALE:

Items 1
FOR
M
SALE

CHAPTE
R

lix
Quality Assurance
and configuration
Management

MAIN TOPICS COVERED

• Introduction

• Testing Levels

• Testing Strategies

• Test Cases

lx
Chapter 5

Quality Assurance and

configuration Management

5.1 Introduction

Software testing strategy roadmaps for the software developers, the quality
assurance organization and the user. Quality assurance consists of the
auditing and reporting functions of management. The goal of quality
assurance is to provide management with the data necessary to be informed
about product quality thereby gaining insight and confidence that product
quality is meeting its goals. Quality assurance is an essential activity for any
business that produces products to be used by others.

We do the testing process to identify the maximum number of errors in code

with a minimum amount of efforts. Finding an error is thus considered a
success rather than failure. On finding an error efforts are made to correct it.

A test consists of a number of test cases, where different aspects of the part
under test are checked. Each test case tells what to do, what data to use, and
what results to expect. When conducting the test, the results including
deviations from the planed test case are noted in a test protocol. Normally a
deviation indicates an error in the system. An error is noted and described in

lxi
a test report for removal or directly removed by programmer who develops
that part.

5.1.1 General Type of Errors:

Errors can be of the following types.

• Functional (e.g. a function is missing or incorrect)

• Nonfunctional (e.g. performance is slow)
• Logical (e.g. user interface details are not considered logical)

5.2 Testing Levels ;

Various test were performed, errors were reported and fixed. There are
number of different types of testing.

• Unit Testing
• Integration Testing
• System Testing
• Regression Testing

5.2.1 Unit Testing:

A unit test is one of a component or a set of components, often done by the
developer of the component.

5.2.2 Integration Testing:

Integration testifies is one of packages that are put together where interface
of packages and their collaborations are validated. People having good
knowledge of the architecture of the system do this testing.

lxii
5.2.3 System Testing:

System testing is a functional testing of the entire system and viewed by end
user. It is done on the basis of the design. The system test verifies that the
system delivers the specified functionality to the end user.

5.2.4 Regression Testing:

It is basically a technique to handle changes in the system. A regression test

is run after changes have been made to the system, it is actually a series of
tests run on the entire system to determine whether any other functionality
has been incorrectly affected by the changes. Continuous regression tests will
unveil such problem.

5.3 Test Plans

The test plan carried out during the testing of the software developed,
was based on the strategies described above.

The testing plan was to carry the following four steps sequentially

• Unit testing
• Integration testing.
• Validation testing
• System testing.
The following tests were focused tests during the above-mentioned
testing

i) Input Testing:

lxiii
This process was carried out to test whether the proposed software can
take the valid input and the checked blocks invalid entry of the data, to
ensure that the software provides best performance.

ii) Output Testing:

This process was carried out to test the output generated by the
software and to specify that either the software is providing the
required output or not.

iii) Code Testing:

This process was carried out to test the coding and to specify that
either the coding is errorless and check that the developed software
provides a quick flow of data and that either the code designing satisfy
the performance of the software.

iv) Database Testing:

Database designed for the software is tested and its performance identifies such
that either the software provides effective storage or not. The testing of database
plays a major role, as it is the stage to indicate that either software is satisfying the
user of the organization
The above test plans were carried out in the following manner.

Initially test was focused on each component individually, ensuring that it

functions properly as a unit. The process of exercising specific paths in a
module’s control structure was carried out to ensure complete coverage and
maximum error detection.
Next component were assembled / integrated to form the complete
software package. Integration testing addressed the issues associated
with the dual problems of verification and program construction.

After the software had been integrated a set of higher order tests were
conducted. Validation criteria (established during requirement analysis)
were tested to check that software meets all functional, behavioral,
and performance requirements.

lxiv
 And finally system testing was carried out that verified that all
elements mesh properly and that overall system function/performance
is achieved.

During all these tests input, output, code and database testing was
carried out.

5.4 E-Broker Testing:

Testing process of the eBroker started as the different programs units were
completed. All the test phases are primarily implemented on each module,
separately and collectively. Initially Unit testing was performed on every
program unit. Syntax errors were removed. All the scripting errors were
detached, and the validation checks were tested and corrected entirely. For
semantic errors every program unit was tested with the help of test data.

Different units were combined in the form of web pages and the required
functionality of the pages, and their links were also tested. During the
integration of all the pages, syntax and semantic errors were applied then
errors were checked and removed. In the next step the system test was
applied and all the errors were checked and removed. When all these errors
were detected and removed, the final test applied to the system to check
whether these changes are affecting the remaining part of the program unit
or not. The errors occurred were removed. After these checking all the
functionality was checked and found correct.

5.5 Testing Strategies:

lxv
This project will use incremental approach in the integration testing:

Top Down:
Testing on the higher modules. If there was any error, continue to test the
individual modules.

Bottom Up:
Testing on the individual modules first, continue to test the higher modules if
no error.

Sandwich:
Mixed testing approach of top down and bottom up approach. There are some
modules, which will be tested by Top Down approach, and some modules by
Bottom Up approach.

5.6 TEST CASES:

Following are the couple of test cases among all the test cases that were
carried out to determine whether the system fulfills its requirements.

Test Date: December 22,

Test Id: User Registration
2005
Tester: Nomi Ali Test Pass (Y/N): “Yes”
Remarks: The User registration was tested .The specific user is asked to
enter his registration details. User registered to software successfully and
then user authentication was also checked on valid username and
password. Error message displayed either the user name or password
incorrect.

Figure: User Registration Test Case

lxvi
 Test Date: December 28,
Test Id: Bid Placement
2005
Tester: Nomi Ali Test Pass (Y/N): “Yes”
Remarks: It was tested whether the bid is placed on specific product for
the logged user or not. User name and password were entered and then
Bid was placed it was concluded that the register users can be placed on
runtime.

Figure: Bid Placement Case

Test Id: Selling Product Addition Test Date: December 28, 2005

Tester: Nomi Ali Test Pass (Y/N): “Yes”

Remarks: Selling Product Addition was done and it was tested whether the
new item for sale is added properly. If not all required fields entered error
message displayed asking user to enter all the fields before adding.

Figure: Selling Product Addition Test Case

lxvii
Test Id: Browse Listings Test Date: January 02, 2006

Tester: Nomi Ali Test Pass (Y/N): “Yes”

Remarks: The e-broker system was checked against the menu of the
browse listings and this test was successful as all the available items for sale
at that time were shown in browse listings page.

Figure: Browse Listings Test Case

lxviii
Test Id: Admin Security Test Date: January 10, 2006

Tester: Nomi Ali Test Pass (Y/N): “Yes”

Remarks: The admin security was tested by entering the wrong email and
correct password and then by entering correct email and wrong password
and leaving the fields blanks. Neither case was successful until the correct
info was entered.

Figure: Admin Security Test Case

CHAPTE
R
lxix
 6

System Evaluation
& Future
Enhancements

lxx
 MAIN TOPICS COVERED

• Introduction

• Features

• Future Enhancements

Chapter 6

System Evaluation &

Future Enhancements

6.1 INTRODUCTION:

lxxi
The evolution of the computerized system is very important to judge whether
the goals and objectives set out for the system has been met or not. The
eBroker system is multifunctional and has number of advantages over the old
system.

The final stage of system life cycle is evaluation and future enhancement. In
evaluation of the system we check and make sure that all the functional
requirements and non functional requirements have been fulfilled or not.

In future enhancement, the system can be extended by adding new improved

features in it or nor is discussed.

6.2 Evaluation of Software:-

Evaluation of the system of electronic broker was very successful in terms of

all the functional requirements and the non-functional requirements. After
evaluating the functional and non functional requirements of the electronic
broker system the following conclusions are drawn.

6.2.1 Functional Requirements:

Following are the requirements that have been evaluated for completion

Functional Requirements
Evaluation
lxxii
 • User Registration

• Buying/Bid Placement

• Selling Product. Completed

• Browse Listings

• Administrative users’ Security &

Administration

Similarly all the nonfunctional requirements evaluation was also

completed

6.3 Features:
Some of the key features of the new system are as follows:

a) Efficiency:
The new system is more efficient as compared to the existing system;
checks have been kept to ensure that no wrong information is entered.

b) Accuracy:
The result produced by system are accurate and per requirements.

c) Time saving:
The system is quick in responding to queries and generate fast out put.

d) Reliability:

lxxiii
The results produced by the computerizes system are reliable and make
data handling easy and interesting.

e) Flexibility:
The proposed system should be flexible. There should be an option to
change the proposed system n future according to needs and
requirements of the organization.

f) End User Characteristics:

The end users are assumed to be will educated and capable of operating
computer so they come under the category of knowledgeable, frequent
users who have good semantic and syntactic knowledge and capability of
learning this easy to use software.

6.4 Future Enhancements:

Current version of the software may be thought as a prototype of the
version to come ahead. Maximum effort has been done to keep
enhancement holes in the existing system.

Software is flexible enough to welcome enhancements both at database

and programming level. I hope that with more experience and knowledge I
will be able to thoroughly gather ever-changing project management
requirements, which will ultimately help me better analysis and design of
the software.

lxxiv
 CHAPTE
R

lxxv
THE USER GUIDE

MAIN TOPICS COVERED

• Introduction

• External Interface Requirements

• Screen Shots of the System

lxxvi
Chapter 7

THE USER GUIDE

7.1 Introduction:

System is windows based with the graphic user interface tool kit. In fact the
application itself has its own environment of Graphical User Interface with all
the available menus.

The Operating System is windows based WINDOWS XP with all the latest and
enhanced user friendly interface.

7.2 External Interface Requirements:

From the point of view of the end user, the interface with the software will be
primarily mouse-based. Users will have the ability to click on the items to

lxxvii
search. There is no hardware that this software product will access directly.
Everything including the mouse-clicks will be delivered to the product by
operating system, most likely Microsoft windows XP, and running on their
local computer. The only other software requirement that the software will
require is an Internet Browser.

7.3 The Screenshots of E- Broker:

(Welcome Page)

lxxviii
(Login Page)

lxxix
(Product Display Page)
lxxx
(Signup Page)
lxxxi
(My Sale Items Page)
lxxxii
(Edit Sale Item)
lxxxiii
(Add Item For Sale Page)
lxxxiv
(Administrator Console)
lxxxv
(Admin General Info Page)
lxxxvi
SITE MAP:
lxxxvii
lxxxviii
References & Biblography:
• Software Engineering (A practioneers Approach) By Roger S.PressMan
• Active Server Pages…A professional approach
• Concepts of E-Commerce
• www.eBay.com
• www.google.com

lxxxix