UNIVERSITY OF GONDAR

COLLEGE OF INFORMATICS
SCHOOL OF COMPUTING AND INFORMATICS
DEPARTMENT OF INFORMATION TECHNOLOGY

Title: Web based Online Auction Management System

A project submitted in partial fulfillment of the requirements for the degree of
B.Sc. in Information Technology - Part 1

by

Terngo Chekle (GUE/09724/09)

Desalegn Emuhay (GUE//08029/10)

Behailu Alemayhu GUE/08016/10)

Fasika Abbu (GUE07977/10)

Tiringo Ayelign (GUE/09729/09)

Adviser: Aleka Melese

June 2022

Gondar, Ethiopia

i
 CERTIFCATE
Online Auction Management System

BY

Terngo Chekle (GUE/09724/09)

Desalegn Emuhay (GUE//08029/10)

Behailu Alemayhu GUE/08016/10)

Fasika Abbu (GUE07977/10)

Tiringo Ayelign (GUE/09729/09)

BACHELER OF SCIENCE

FROM

University Of Gondar

This is to certify that the project work prepared by group five members of Information
Technology students entitled: developing web based online auction management system for
online this system users submitted in partial fulfillment of the requirements for Degree of
Bachelor of Science in Information technology complies with the regulations of the University
and meets the accepted standards with respect to originality and quality.

Advisor.1. Name_________________ Signature_____________ Date_______________

Examiner.1. Name_________________ Signature_____________ Date_______________

2. Name _________________Signature_____________ Date_______________

Signed by the Head of the Department:

Name --------------------------------------------Signature _____________ Date______________

ii
Acknowledgment
First of all we would like to thank GOD keeping us healthy. Lots of problems have overcome
with the assistance of GOD. Without his will nothing could be done. We have taken efforts in
this project. And also thanks our Advisor Mr. Aleka Melese for all his support with this project.
Mr. Aleka Melese always has time for our questions and his comments on our project have
been valuable. In addition to this we wish to thank our friends for supporting us in many ways.
Last but not least, we are deeply grateful to our family supported in many ways. Lastly, our
thanks’ and appreciations also go to department of Information Technology in developing the
project and people who have willingly helped us out with their talents.

iii
LIST OF ACRONYM AND ABBREVIATION

BR Business Rule
CSS Cascading Style Sheet
DB Database
GB Gigabyte
HTML Hyper Text Markup Language
PHP Hyper Text Pre Processer
ID Identification
My SQL My Structured Query Language
OAMS Online Auction Management System
RAM Random Access Memory
UML Unified Modeling Language
UC Use Case
WAMP Windows, Apache, MySQL, PHP

TABLE OF CONTENTS

iv
LIST OF ACRONYM AND ABBREVIATION..................................................iv
TABLE OF CONTENTS........................................................................................v
CHAPTER ONE:.....................................................................................................1
1.INTRODUCTION................................................................................................1
1.1. Background of the organization.........................................................................................2
1.3. Statement of Problem.........................................................................................................3
1.4.Objective of the project.......................................................................................................3
1.4.2.General Objective..........................................................................................................3
1.4.2 Specific Objective..........................................................................................................3
1.5 Methodology of the project.................................................................................................4
1.5.1. Fact Finding Techniques..............................................................................................4
1.5.2.Systems Analysis and Design........................................................................................4
1.5.3.Programming Language...............................................................................................4
1.6. Development Tools..............................................................................................................5
1.7 Scope of the Project..............................................................................................................5
1.8 Constraints............................................................................................................................6
1.9 Alternative Solution.............................................................................................................6
1.10.Feasibility Study.................................................................................................................6
1.10.1.Technical Feasibility....................................................................................................6
1.10.2.Operational Feasibility................................................................................................6
1.10.3.Economic Feasibility...................................................................................................7
1.10.4.Legal Feasibility...........................................................................................................7
1.11. Proposed solution..............................................................................................................7
1.12. Significance of the Project................................................................................................8
1.13. Target beneficiaries of the system...................................................................................8
1.14. Hardware and Software Tools.........................................................................................9
1.14.1. Hardware Requirement.............................................................................................9
1.10.5.Software Requirement................................................................................................9
1.15 Cost/Budget Estimation...................................................................................................10
1.16. Schedule feasibility/Time Schedule...............................................................................10
CHAPTER TWO...................................................................................................11

v
2.SYSTEM ANALYSIS........................................................................................11
2.1.Overview of the Existing System......................................................................................11
2.2.System Requirement Specification...................................................................................11
2.2.1.Functional Requirements............................................................................................11
2.2.2.Nonfunctional Requirements......................................................................................12
2.2.3.Business Rules..............................................................................................................13
2.3.System Requirements Analysis.........................................................................................14
2.3.1.Actor Identification.....................................................................................................14
2.3.2.Use Case Identification...............................................................................................14
2.3.3.Sequence Diagram.......................................................................................................18
2.3.4. Activity Diagram........................................................................................................22
2.3.5. Analysis Class Diagram.............................................................................................29
CHAPTER THREE...............................................................................................30
3. SYSTEM DESIGN............................................................................................30
3.1. Introduction.......................................................................................................................30
3.2. Design Goal........................................................................................................................31
3.3 Proposed Software Architecture.......................................................................................32
3.6 State Chart Modeling State...............................................................................................32
3.4 Collaboration Diagrams....................................................................................................35
3.5. Persistent Data Management...........................................................................................36
3.4 .Deployment Diagram........................................................................................................40
REFERENCE........................................................................................................41

List of table

vi
Table 1. 1 development tools...........................................................................................................5
Table 1. 2 Cost of the project.........................................................................................................10
Table 1. 3 Time Schedule..............................................................................................................10

Table 2. 1 use case identification...........................................................................................................14

Table 2. 2 login Use case description......................................................................................................16
Table 2. 3 Customer registeruse case description....................................................................................16
Table 2. 4post auction use case description.............................................................................................17
Table 2. 5Bid on the item use case description.......................................................................................17
Table 2. 6 create account use case description........................................................................................18

Table.1 Description for Table Auctioneer...............................................................................................36

Table 2 Description for Table binder......................................................................................................36
Table 3 Description for Table Compliant................................................................................................36
Table 4 Description for Table trade liance..............................................................................................37
Table 5 Description for Table feedback..................................................................................................37
Table 6 Description for Table ADMIN...................................................................................................37

vii
List of Figure
Figure . Use Case diagram 15
Figure . Sequence diagram for create user account. 19
Figure . Sequence diagram for login use case 20
Figure . Sequence diagram for Send request use case 21
Figure . Sequence diagram for view note fide winner use case 22
Figure . Activity diagram for login use case 23
Figure . Activity diagram for customer registration use case 24
Figure . Activity diagram for auctioneer and binder account use case 25
Figure . Activity diagram for bid on the item use case 26
Figure . Activity diagram for create account 27
Figure . Analysis class diagram 30
Figure . State diagram of login 33
Figure . State diagram of search binder 34
Figure . Collaboration diagram of login 35
Figure . Collaboration diagram of create account 36
Figure . Mapping system architecture 39
Figure . Mapping System Architecture (Deployment Diagram) 40

viii
 CHAPTER ONE:
1. INTRODUCTION
The term auction means the process of placing items on an auction and letting people compete
on the item by bidding, then based on the business rule the winners will get the auction. It is
all about getting the right price for the product and the services offered by the companies or
Individuals .Auction is offering a competitive price for a product or a service in order to get or
to own the product or the service offered. Similarly auction invites competitive bidding in
order to understand and sell a product and a service offered at a competitive and a high value
and price. Auction can also be in order to receive a competitive low price for a product or a
service offered by a vendor to an organization in order to win the bid and so as to get to
contract. Now a day there are deferent type of auction such as open auction, restrict auction,
direct auction, competitive thought auction, two stage, and by cost offer. Those auctions are
announced by media, newspaper and notice board.
Auction is the process of getting goods and/or services by public bodies or organization. The
primary objective is acquiring and selling the right product or service, at the right price and
quality at the right time in a fair and transparent manner. However, mostly auction processes
are known for being highly vulnerable to corruption and the processes is tedious and slow.
In this regard, online auction system is designed to store profile of bidders in their respective
specialization area; advertise new bids; accept bid proposal and notify bidders about bid
evaluation result. The use of online auction system reduces errors and also ensures greater
transparency and accountability in public auction of goods and services. It ensures greater
participation as well as security of bid and related documents.

1
 1.1 Background of the organization
During the following years we have evolved according to the changing needs of our society and
endeavoured to tailor our institution to the address the urgent needs of our country. In 1980/81
the Training Center was renamed Gondar College of Medical Sciences (GCMS). Medical
training was provided at the College by German medical experts, creating opportunities for the
subsequent training of Ethiopian staff in Germany. GCMS gained autonomy from Addis Ababa
University in 1992. In 2001 the first new Faculty, the Faculty of Management Sciences and
Economics, was created. Located in the history of Gondar, Ethiopia, University of Gondar is
one of the oldest and most distinguished higher education institutions in the country.it was
established in 1954 as a public health college and training center (PHC and TC) to train middle
level health professionals who can run a network of health centers to address the pressing
health issue. This was the birth of the philosophy of team approach and community based
teaching which now has grown to Team Training Program (TTP) undertaken by the medical
college. Established as the Public Health College in 1954, it is located in Gondar, the former
capital of Ethiopia. In 2010, the university offered 42 undergraduate and 17 postgraduate
programs. As of 2016, the University offers 56 undergraduate and 64 postgraduate. These are
organized under the College of Medicine and Health Sciences, College of Business and
Economics, College of Natural and Computational Sciences, College of Social Sciences and
Humanities, and Faculty of Veterinary Medicine and Faculty of Agriculture, and three schools
(School of Law, School of Technology and School of Education).[1] The current president of the
University is Dr. Asrat Atsedeweyn.

1.2. Background of the Project

When we see auction in University of Gondar want to acquiring goods or service by bidding
the organization to announce this auction pay money to news paper or media. The
organizations have unified set of bidding regulations. Bidders to contract with organization
face different set of bidding rules and regulations. Thus, both bidders and organizations are
often faced with different key bidding requirements such as timing, advertising bid content etc.
from these, often conflicting, requirements cause’s challenges and results in delays to
organization bidding process. Errors are most commonly made by bidders when submitting bid
proposals issued by public invitations. The most common mistakes that bidders make when
submitting a proposal are failing to include all forms (requirements) at the time of submission
to possess the required licensing and registration required by the bidding document (e.g VAT
registration, Trade License, etc…), and not respecting submission deadline. The team members
designed to address these issues replacing the existing paper-based system by computerized
system.

2
1.3. Statement of Problem
The current auction system work manually and it is tedious. And also needs cost to accomplish
the activity. The customer wants to compute in the auction item he or she attends the place of
bidding. Some the major problems that are listed below:-
 Time consuming.
 Cost for transportation.
 Cost for printing document that contains auction content.
 high Payment cost for media, newspaper to announce the bids.
 Requires manpower.
 Poor coordination between the auctioneer and the bidder.
 It covers only limited Area this means not express media bidder participate exist that
space only.
 Limited number of Bidders.
 vulnerable to corruption
1.4 Objective of the Project
1.4.2 General objective
The general objective of our project to develop an online auction management system; which
will provide a forum for sellers to meet and interact with buyers, and sell items to interested
bidders

1.4.2 Specific objective

 To develop system that is easily portable and used by any authorized user.
 To develop a database that is secure to keep the overall records associated with the bids.
 To develop a database for registration and post auction form.
 To create easy and user friendly system.
 To develop a system for an automatic report generation.
 To develop a system to provide reliable services for customer
 To make management of bidding information easier and more effective

1.5 Methodology of the Project

1.5.1. Fact finding techniques

 Interview

3
Our teams use this method by orally asks different peoples who have some knowledge
regarding to auction. We orally discuss and interview university of Gondar procurement
workers for necessary information’s regarding about the process of auction. This information
helps us to identify the main actors that participate on the auction and also about the way that
how the system works.

 Document Analysis

To understand the existing system, we collect more information by referring internet,

documents and other reading materials about the general information of the auction. It helps us
to analysis, design and organizes our project.

1.5.2. Systems Analysis and Design

We have use Object Oriented System Analysis and Design (OOSAD) using Unified
Modeling Language (UML).Because of the following reasons:
 These techniques enable to reduce the communication gap between user and designers.
 These techniques enable designers to model the real world accurately.
 These techniques have usability features (it allows to use codes repeatedly on other system).

1.5.3. Programming Language

Programming Language is a formal computer language designed to communicate to a machine,
particularly computer. We would use the following programming language:-
 PHP:-is a server-side back-end programming languages. Simple and easy to learn,
Speed, Easier to fix problems, Optimized for making web applications quickly.
 HTML:- is a client-side front-end fundamental coding language that creates and
organizes web content so it can be displayed by a browser. HTML is easy to use and
understand, all browsers support HTML, Most development tools support HTML,
HTML is most search engine friendly. Why we use to display the web page.
 CSS: -is a client-side front-end language that accompanies HTML, and defines the style
of a website’s content, such as layout, colors, fonts, etc . browser compatibility. Why we
use for the formatting of the system.
 Java Script: - It also a client-side front-end programming language used for more
interactive elements like drop down menus, modal windows, and contact forms.

4
 Interpreted languages, easy to learn, platform independence. Why we use for animation
purpose and to display prompt boxes.

1.6. Development Tools

The programming tools that the project concentrates are the following:
Software requirements and its environment
Table 1 development tools

Activities Tools/ Programs

Language Java/html
Client side scripting JavaScript
Platform MS Windows 10
Database server Mysql
Web server Apache
Server-side scripting Php
Browsers Explorer
Editors Notepad++, MS Excel, eclipse, android
Documentation MS Word 2016
User Training MS PowerPoint
Varied technologies As per the technical requirement in future

1.7 Scope of the Project

The Scope of the project covers the area of the project and activities, operations done by the
system. Our project will cover organization or public body in Ethiopia to sell or to buy goods or
to get service by open auction system. Bidders participate on the auction by visiting or viewing
the auction item. Bidder registers online to participate on the auction. Auctioneer can create or
post auction with their auction start date and closed date. Bidders can bid on auction item by
filling the necessary information on the form. In order to apply auction correctly Auctioneer
checks the bidders’ trade license from service and also check the bidders are paid or not paid,
using internet banking, but this is not the team members of project scope. After the end of the
auction, the system responsible to notify the winner of the auction. Administrator is responsible
to manage register auctioneer or bidder information from the database. Then project team will
be able to perform the above activity and give efficient service to the customer or the user of
the system.

5
1.8 Constraints
The choice of the database to use should be considered carefully, since there will be a lot of
data traffic and the large amounts of data will also judge the database. A good database will
yield speed querying of data.
The browser used should support HTML to satisfy user experience.
The device should be enabled with internet.
The new system should offer more flexibility and functionality.
 It may decrease wastage of time.
 The service will be interesting and helpful for any one.
 The system will be clear and safe.

1.9 Alternative Solution

Looking for Online Auction management System alternatives? Analyze a range of top Auction
software that offers similar benefits at competitive prices. Empower your team by choosing the
best Online Auction management System competitor that meets your unique business
requirements. The live auction software offers end-to-end auctioning solutions .[1].

1.10. Feasibility Study

The objective is determines whether or not the proposed system is feasible. The fourth carryout
feasibilities are:-

1.10.1. Technical Feasibility

We are fully confident that the system we develop is fully attainable by existing technology. the
system will also be portable in different platforms as long as the platform can use internet .

1.10.2. Operational Feasibility

When the system is applied in to operation, we are fully confident that the system will be
operationally feasible because as we will develop a system that is easy to use and maintain.
With a little training anyone will be able to understand and will be able to handle with the
system easily.
The main users of this system are the auctioneer and buyer, so the user should:-
 Familiar with internet.
 Familiar English or Amharic language.
 Able to use and do according to the graphical user interface (GUI) on the website.

6
1.10.3. Economic Feasibility
This stage determines the cost or value analysis. It can be software, hardware and others. The
new proposed system would be economically feasible.

 Tangible benefits:-
 Reduce cost of printing documents.
 Reduce cost of transportation for the customer to register and participate in the
auction.
 Payment cost for media and newspaper to announce the auction is reduced.
 Intangible benefits:-
 Increase speed of activity.
 On time information.
 Satisfying customer requirements

1.10.4. Legal Feasibility

The system to be developed is not conflict with any government directives, because it gives
services for organization and public body. So the government and peoples are profitable and
the system will be legally feasible.

1.11. Proposed solution

 To use Time properly and effectively.
 Cost for transportation.
 Cost for printing document that contains auction content.
 Payment cost not for media, newspaper to announce the bids it announce using the
internet for the system users.
 No requires of manpower.
 God coordination between the auctioneer and the bidder.
 It covers only large Area.
 Multiple numbers of Bidders exist.
 It fitting to corruption using administrator to control accounts of the binder.

1.12. Significance of the Project

The significant of the system is to facilitate and give short and precise auction service for
the customer of the system.

7
 The project has the following significances:-
 It saves manpower.
 Reduce time.
 Reduce corruption
 Satisfying customer requirements in short time via online.
 Give full information about auction content.
 Improve the communication between auctioneers and bidders each other.
 Reduce cost of transportation to register.
 Reduce cost for printing document which contain auction content.
 Minimize the work load.
 Reduce cost for paying to media or newspaper.
 Cover large number of bidders.
1.13. Target Beneficiaries of the System
Buyer
 Save Money: Competitive bidding drives down purchasing costs for capital
equipment, materials and services.
 Save Time: Stop waiting weeks or months for suppliers to submit bids. Online auction
services streamline the purchasing process by compressing the bidding cycle to hours,
allowing an organization to move forward immediately with its procurement goals.
 Expand Supplier Pool: Reverse auctions can help an organization to expand its access
to high-quality local, national and global suppliers.
 Get Started Quickly: the auction software is easy to use, minimal training is required
for your organization to start realizing immediate cost- and time-saving benefits.
 Supplier
 Uncover New Business Opportunities: Once a supplier organization register, it will be
eligible to participate in future auctions.
 Level the Playing Field: Reverse auctions allow a supplier organization to see what
other bidders are offering, so it has a clearer understanding of what the market price is
and can compete more effectively for the business.
 Eliminate Security Risks: While suppliers can see what their competitors are offering,
company names are cloaked to protect confidentiality.

8
1.14. Hardware and Software Tools
1.14.1. Hardware requirement
 Computer: - used to write the proposal, documentation, develop online auction
management system. The computer specifications have followed:-
 Processor – core i3 @ 2.4 GHz.
 Hard Drive - 120 GB:-used to store data permanently.
 RAM - 4 GB.
 8GB flash:-to use back up data and store data.
 Pen and paper used to design the system before typing on the computer.

1.10.5. Software Requirement

 WAMP Server: manage servers setting.
The reason of selecting WAMP server is:-
 Due to their popularity to any web based applications.
 They are secure means they are not easily attack by virus when we compare to other
servers.
 It’s window independent.
 E draw: used to draw different UML those are necessary to structure the system.
 Microsoft word 2010: This is used to write the documentation of the proposed system
from the starting to the end of the project.
 Power Point 2010: to presentation purpose.
 Text editor:- used to write the code of the project. like notepad, notepad ++.
 MYSQL:-used to data base connection.
 Operating System - Windows 7 used to perform applications.

1.15 Cost/Budget Estimation

Cost of the project
Here we have tried to mention some of hardware cost. Software tools we used are open
without any payment. Just for reminder we have put our intellectual property that will not
be given a price

9
 Table 1. 2 Cost of the project
No Item Quantity Unit Price Total Price (inbirr)

1 Pen 5 10.50 52.50

2 Paper 1 pack 550 550
3 For print 100 3.00 300
4 USB flash 2 350 700
5 CD 3 50 150
6 Acer Computer 1 30,000 30,000
Total 31,752.5

1.16. Schedule feasibility/Time schedule

Table 1. 3 Time Schedule

I Task name Start Finish 13-06-2014 20-09-2014

D
13-06-2014

16-07-2014

17-07-2014

18-08-2014

25-08-2014

19-09-2014

20-09-2014

29-10-2014

30-10-2014

15-11-2014

16-11-2014

10-12-2014
Complete
Duration

1 Project proposal 13-06-2014 16-07-2014 33 10

0
2 Requirement 17-07-2014 18-08-2014 30 10
analysis 0
3 Design 25-08-2014 19-09-2014 21 40

4 Implementation 20-09-2014 29-10-2014 39 0

& coding
5 Testing 30-10-2014 15-11-2014 15 0
6 Project defense 16-11-2014 10-12-2014 24 0

10
 CHAPTER TWO
2. SYSTEM ANALYSIS
2.1. Overview of the Existing System
In the existing auctions system are takes place in traditional way a person must be there exist
physically to participate on the auction. In existing auction system auctions announce by media,
newspaper, and notice board. To participate in existing auction system bidders must have a
valid trade license number and VAT registration number. Bidders fulfill in the above
information first buy a document which contains the bids information about product or item
and bids form.
Bidders read the bid document and fill the required data after this, bidder return the form or bid
proposal to the auctioneer. At this time the bidder pays some money or if bidders have a bank
account he or she transfers to the auctioneer account at this time bank workers write a bill bond
to bidder. The bidders give the bill bond with the bid proposal form to the auctioneer. The
auctioneers store this information in the box up to the auction end date. After the end of the
auction date auctioneers open the box and identifying the winner of auction. The winner of the
auction announce by phone or notice board.

Users of the Existing System are:-

Bidder: is a customer that is buying or selling an item by placing a bid.
Auctioneer: is a customer that is acquiring service or selling an item by auction. The person
who manage the process of auctions by arranging optimum schedule time and place.
Bank: is an actor in which money payment will be performed. Based on the auction rule and
regulation they must pay money after winning the auction. For example if a bidder to
participate on auction first make some present of payment. So this payment will be performed
(transferred) to the auctioneer bank account using the bank.

2.2. System Requirement Specification

2.2.1. Functional requirements

Functional requirements are fundamental building block requirements. It is a statement of
exactly what the system must do. The new system being the following functional requirements:

11
Admin:-
 The Administer shall allow create or activate account for the registered customer.
 The administer can take backup and restore the database.
 The administer shall allow should keep bidders’ data confidential.
 The Administer shall allow can View feedback.
 The Administer shall allow can Update account of the user.
 The Administer shall allow can Block account of the user.
Binder:-
 The system shall allow bidders to submit their bid proposal.
 The system shall allow bidders to download a bidding document.
 The system shall allow bidders bid on the item online.
 The system shall allow bidders can send compliant.
 The system shall allow bidders can view auction.
 The system shall allow bidders can register to system.
 Bidders are able to view the outcomes of bidding.
Auctioneer:-
 Auctioneer can post auction.
 The system shall allow customer registration to participate on the auction online.
 The system shall allow maintain complaints and feedback of bidders about the overall
bidding process and responds.
 The system shall allow generate reports and its result is provided for all interested parties.
 The system shall allow generate the winner of the auction.
 The system shall allow auctioneer to modify time.
 The system shall allow auctioneer can upload bid document.
 The system shall allow auctioneer view and replay compliant.
 The system shall allow auctioneer can register to the system.

2.2.2. Non-functional requirements

Non-functional requirements describe how the system works, while functional requirements
describe what the system should do. Non-functional requirements, as the name suggests, are
requirements that are not directly concerned with the specific services delivered by the system
to its users. Such as:-

12
Security:-The system only permits authorized user to enter the system. Authorized users are
who have username and passwords.
Scalability: If the number of binders and user increases in the organization it does not effect
on the database.
Usability: The system has an interactive and attractive GUI which eases users’ usage problem.
It needs simple training, because it is easy to use and adapt.
User Interface: The interface will be user friendly and can properly guide the user how to use
the system and perform operations easily since every link name in the system similar to the task
performed.
Performance: The system performs its task efficiently and effectively because the team
project will uses advanced programming language, less number of iterations for a given task
and optimized query to develop the system
Availability: -This system should always be available for users to access.
Portable: It becomes portable for different platform because we develop the system using
online so it very smart technology to use any browser.

2.2.3. Business Rules

Business rules are statements about the system way of doing business. They reflect business
polices. Systems have policies in order to satisfy the business objectives, satisfy customers,
make good use of resource and conform to laws or general business conventions.
 To participate on the auction in the existing system:
BR1:-Must have come early in the place of auction.
BR2:- Must never bid if you don’t intend to pay, you will be banned.
BR3:-People who have not paid after winning an auction will be instantly punished the first
paid amount.
BR4:-Create the auction again when the winner does not pay within a specified time.
BR5:-Extend the deadline of the auction when there is no participant within the specified
schedule.
 To participate on the auction in the proposed system you:
BR1:-must be first register to bid and post or create the auction
BR2:-bidders have not trade license can’t be register in the site.
BR3:-in order to bid bidders first pay that you went to bid on the auction.

13
 BR4:-Extend the deadline of the auction when there is no participant within the specified
schedule.

2.3. System Requirements Analysis

2.3.1. Actor identification

 Bidder: is a customer that is buying or selling an item or give service by placing a bid.
 Auctioneers: is a customer that is acquiring or selling an item or get service by posting
auction.
 Administrator: is responsible for managing the overall system and manage customer data.
2.3.2. Use Case Identification
Each Use Case describes the functionality to be built in the proposed system, which can
include another Use Case’s functionality or extend another Use Case with its own behavior.
The most important and basic use cases of this system are the following:-
Table 2. 1 use case identification

ID Use Case Name Include

UC1 Login
UC2 Customer Register
UC3 post auction UC1
UC4 View report
UC5 Update account UC1
UC6 Bid on the item UC1
UC7 View Nonparticipant bidder UC1
UC8 View Notified winner
UC9 View and replay compliant UC1
UC10 Modify date UC1
UC11 View feedback UC1
UC12 Download bid document UC1
UC13 Modify bid amount UC1
UC14 Send compliant UC1
UC15 View auction
UC16 Give feedback
UC17 Logout
UC18 Create account UC1
UC19 Block account UC1
UC20 Backup database UC1
UC21 Restore database UC1

14
Figure 1. Use Case diagram
 Use Case Description
System use cases reflect analysis description, design decisions and it consists of actors, use
cases and their relationships. An actor is an external entity that interacts with the system. A use
case describes a sequence of actions that provide a measurable value to an actor.

15
 Table 2. 2 login Use case description

Use case Name Login

ID UC1
Actor Administer, auctioneer, and bidder.
Description Required for login to access the system.
Precondition The user must have a valid username and password.
Post condition Administrator, auctioneer, bidder, successfully login to his page.
Flow of action Actor Action System response
Step 1: user wants to log to the system Step 3: The system
Step 2: open the system displays the login form.
Step 4: .enter user name and password. Step 6: validate on the
Step 5: Submits the form. form controller
andcheck on thedatabase
Step 7: Notifies about
the status of login
(success or failure).
Step 8: Use case ends.
Alternative Course of Action If user submits invalid information to database, send a notification
to the user to re-submit valid information.
The system redirects to step 4.

Table 2. 3 Customer register use case description

Use case Name Customer register

ID UC2
Actor Auctioneer, bidder
Description Required for register the auctioneer and bidder information
Precondition The customer must have a valid user data.
Post condition The customer information registered to the database in order to
participate in the auction.
Basic course of action Actor Action System response
Step1: customer wants to register in the
Auction database. Step 3: The system
Step 2: click customer register link. displays the customer
Step 4:Fill customer registration form. registration form.
Step 5: Submits the form. Step 6: validate on the
form controller and check
the input data in the
database.
Step 7: Notifies about the
status of registration
(success or failure).
Step 8: Use case ends.
Alternative Course of Action If customer submits invalid information to database, send a
notification to the customer to resubmit valid data.
The system redirects to step 4.

16
Table 2. 4 post auction use case description

Use case name Create auction

ID UC3
Actor Auctioneer
Description Required to post auction.
Precondition Auctioneer has valid user name and password to login into the system.
Post condition Auction registered to database and display to the home page in the
view auction link.
Basic course of Actor Action System response
action Step 1: auctioneer login Step 3: the system display auction form.
in to his page. Step 6: validates the input in the form
Alternate courses The system display error message when auction data is incorrect
of action The system redirects to step 4 fill the form again.

Table 2. 5 Bid on the item use case description

Use case name Bid on the Item

ID UC7
Actor Bidder
Description Required to bid on the bids item.
Precondition Valid user name and password in order to enter his page
Post condition Bidder data store in the database.
Basic course of action Actor Action System response
Step1: bidder login in to his Step3: The system display bid
page. form.
Step2: Select bid on the item Step6: validate the given input in
link. the form controller and database.
Step4: the bidder fills the bid Step7: the system notifies about
form. the status of bids data (success or
Step5: submit the bid failure).
information. Step8: Use case ends.
Alternate courses of The system display error message when the bidder information is
action incorrect.
The system redirects to step 4 fill the form again.

17
Table 2. 6 create account use case description

Use case name Create account

ID UC19
Actor Administer
Description Required to create account for register customer.
Precondition Admin have valid user name and password in order to login
the system
Post condition Admin create account for the registered customer
Basic course of action Actor Action
Step 1: admin login in to his System response
page. Step3: the system displays
Step2: Clicks create account create account form.
form. Step6: the system notifies
Step4: admin create or fill about the status of (success
user name and password or failure).
Step5: submit the form. Step7: use case end.
Alternate courses of action The system display error message when the customer
information is incorrect.
The system redirects to step 4.

2.3.3. Sequence Diagram

Sequence diagrams are used to model the logic of usage scenarios. Usage scenario is exactly
which its name indicates-the description of a potential way our system is used. The logic of
usage scenario developed here comprises the basic course of actions.
The boxes across top of the diagram represent classifiers or their instances; typically use cases,
objects, classes or actors.
The solid lines hanging from the boxes are called objects lifelines, representing the life span of
object during the scenario being modeled. The long, thin boxes on the long life lines are
method invocation boxes indicating that the target object/class to fulfill a message is
performing processing. Messages indicate as labeled arrows, when the source and the target of
a message is an object or class labels the signature of the method invoked in response to the
message. However, if either the source or target is the human actor, then the message is labeled
with brief text describing the information is available [2].

18
Figure 2. Sequence diagram for create user account.

Figure 3. Sequence diagram for login use case

19
Figure 4. Sequence diagram for Send request use case

20
Figure 5. Sequence diagram for view note fide winner use case
2.3.4. Activity Diagram
Activity diagram are best starting point to model logic of business process, use case or method.
This activity diagrams are developed based on the requirement analysis which is done
previously. The team members try to depict the logic of the business process and use case
which was done previously. The black filled circle represents the starting point of the activity
diagram effectively. A place holder and a filled circle with a border represent the ending point.
The rounded circle represents a process of activities that are performed. The diamond
represents decision points and arrows represent the transition between activities modeling the

21
flow order between the various activities[3].

Figure 6. Activity diagram for login use case

22
Figure 7. Activity diagram for customer registration use case

23
Figure 8. Activity diagram for auctioneer and binder account use case

24
Figure 9. Activity diagram for bid on the item use case

25
Figure 10. Activity diagram for create account

26
 2.3.4. Analysis Class Diagram
Class models are the main study of object-oriented design and analysis. Class model shows the
classes of the system, their interrelationships (including inheritances, aggregation and
association) the operations and the attributes of classes. In this class diagram the team members
try to describe the types of object in the system and the various kinds of static relationships that
exist among them as well as depicted the detailed understanding of problem domain of the
system. These Class diagrams are developed based on the functional requirement.
Show the classes of the system, their inter-relationships, and the operations and attributes of the
classes [4]. Class diagrams are typically used, although not all at once to:
 Explore domain concepts in the form of a domain model
 Analyze requirements in the form of a conceptual/analysis model
 Depict the detailed design of object-oriented or object-based software

27
Figure 11:- Analysis Class Diagram

28
 CHAPTER THREE
3. SYSTEM DESIGN
3.1. Introduction
System design is give solution for problem domain specified in system analysis. System design
concern transfer analysis model to design model. This chapter mainly concerned with the
design Web Based Online Auction Management System for public service. System design very
important so the design is very important to implement system easily, but system analysis not
concerned internal structure of the system and hard ware configuration of the system. We
expect one can understand our new system implementation because it gives full description
about whole system. Also one can understand easily and enable to answer how the system
developed and functioned in simplified manner. Within the Software Design Document are
narrative and graphical used throughout the document, Next, the document describes the
system under development in terms of subsystem decompositions, hardware/software mapping,
persistent data management and access control. Generally the purpose of this document is to
determine how we are going to implement our system and to obtain the information needed to
derive the actual implementations of our system.

3.2. Design Goal

Design goals describe the qualities of the system that the developers should consider. Our
system designing phase is on the bases of object-oriented system approach, this designing
phase uses different type of diagrams to model the system. The design phase is the interface
between the requirement specification and the implementation part. These goals can be inferred
from the nonfunctional requirements already discussed in previously. The design goals can be
generally grouped into many categories.. These are: Performance Criteria, Dependability
Criteria, Cost Criteria, Maintenance Criteria, and End User Criteria.
End User Criteria: it describes the Usability of Web based job searching for BFRSPS system
should provide an easy-to-use graphical interface so user can easily learn. The system should
be user friendly so that users can use it easily without confusion and the system interface.
Maintenance Criteria: it describe modifiable, extensible, adaptable and readable of the system.
Web based Online Auction Management System should be modifiable for further modification
and enhancement of the application by add new functionality, portable to different platforms.
The code for the system should be easily readable, understandable and should be easily mapped

29
to specific requirements. The system can handle errors to be corrected and can be maintained if
and only if system structure changed.
Dependability Criteria: The public service needs the system to be highly dependable. The
system should be robust (forceful) i.e. it should be able to carry on invalid user inputs, fault
tolerant, reliable and available, secure. The system shouldn’t allow non-authorized users to
access data or modify. The system should be available for any valid users at any time at any
place. This system provides an access to privilege to an authorized user by giving account for
each and every special function.
Performance Criteria: The Web Online Auction Management system should respond fast
with high throughput, i.e. it should perform the task quickly possible as possible such as
allocating binder and auctioneers, viewing customer’s information. The system does not taking
up too much space in memory to store system’s data.
Cost Criteria: The Web based Online Auction Management System should be developed,
deployed, administered and maintained with minimum cost possible.

3.3 Proposed Software Architecture

The current system doesn’t use any computerized system to provide service and it is started
with the traditional file processing. The architecture of our project uses Client/Server
architecture. In this type of architecture the server is responsible to receive a request from the
client and respond to the request, whereas the client is responsible to interact with that of the
users of the system. The server does two types of work. The first type is a web server, which is
responsible to receive browsers‟ request through http protocol and the web server give
response by using HTML,CSS and java script. Whereas the second type of server is a database
server, which is responsible to provide the requested database services to the web server. It can
only communicate with the web server. The client side is a web browser which receives
requests from the user of the system and responds to the request by communicating with the
web server if the user has a request on data.
The browser passes the request to the web server then the web server pass the request to the
database server. The following figure shows the architecture of the system.

3.6 State Chart Modeling State

State chart diagram describes the flow of control from one state to another state. The state chart
diagram shows the change of an object through time based upon events that occur and it shows

30
how the object changes from start to finish. State chart diagram used to model dynamic nature
of a system. So the most important purpose of State-chart diagram is to model life time of an
object from creation to termination. The main purposes of using State-chart diagrams are to
model dynamic aspect of a system, to model life time of a reactive system and to describe
different states of an object during its life time.

Figure 12. State diagram of login

31
Figure 13. State diagram of search binder

32
3.4 Collaboration Diagrams
UML collaboration diagrams, like UML sequence diagrams are used to explore the dynamic
nature of our system. Collaboration diagrams show the message flow between objects in an
object-oriented application, and also imply the basic associations (relationships) between
classes. One use of a collaboration diagram is to show the implementation of an operation.
In collaboration Diagrams the rectangle represents the various objects involved that make up
the application, the line between the classes represent the relationship (association, aggregation,
composition dependency between them) ,the text along the line is for invoking message on the
collaboration diagram.

Figure 14. Collaboration diagram of login

33
Figure 15. Collaboration diagram of create account
3.5. Persistent Data Management
In this section the team describes how the persistent data stored by the system and the data
Management infrastructure required for it. The purpose of persistence modeling is which
objects in the system design are required to be stored persistently. Clearly, in a database driven
application like this one, almost all system interactions have deal with persistent data. In order
to store information persistently we map objects into tables and the attributes of the object into
fields to the specific table based on the objects found on the system. The system will use the
MY SQL database server for storing data. Each of these items will be store in a separate table.
As described in the system contain nine tables which are stored in MYSQL server.
These tables are:-
User account table: a table which store user account information.
Bidder table: a table which contain binder information.
Bind table: a table which contain bind item.
Comment/: table which contain information about (feedback).
Recovery table: Table which store information about verification.
Auctioneer table: table which contain information about auctioneer.
Compliant table: table which contain compliant questions.

34
Feedback table: table which contain feedback information.
Upload table: table which contain upload document.
Table.1 Description for Table Auctioneer

Table 2 Description for Table binder

Table 3 Description for Table Compliant

35
Table 4 Description for Table trade liance

Table 5 Description for Table feedback

Table 6 Description for Table ADMIN

36
Figure 16. Mapping system architecture

37
3.4 .Deployment Diagram
Deployment diagrams show the component of the software will installed on which the
hardware machine and how they interact with each other. That is hardware and software part of
the system work together efficiently. We want to create a deployment diagram for applications
that are deployed to several machines. It is representing the allocation of components to
different nodes and the dependencies among components. The proposed system has layers:
presentation layer, web server and the database server. The first layer is presentation layer
which is used to clients that enable them to communicate with the web server. It is shown as a
client application which is found under the client machine. Web server contains a number of
functionality supported by the system. The database is developed using MYSQL. It stores the
data persistently. The presentation layer and make decision about task assignments and needed
skill enhancement communicates with the web server using http connection that makes it to
invoke methods remote

Figure 17. Mapping System Architecture (Deployment Diagram)

38
 CHAPTER FOUR

Implementation and Testing

4.1 User Interface design
home page User interface

Auctioneer registration user interface

39
 Bidder Registration user interface

Admin user interface

40
Algorithm Used
Pseudo code Pseudo code is compact and informal high level description of a computer
programming algorithm that uses the structural conventions of a programming language but is
intended for human reading rather than machine reading. The purpose of using pseudo code is
that it is easier for humans to understand than conventional programming language code, and
that it is a compact and environment independent description of the key principles of an
algorithm.

Algorithm use for login

Begin -if

Fill

The Login Form

Click the Login button

If (Form is filled)

If (valid)

Generate SQL select queries

Connect to database

Pass queries to database

If (any query fails)

Display error message

Else

Read session

If session exists on database, user is already logged in,

Display the page

41
 Else

Display the page error message

End if

End if

Else

Display error message

Ask the user to refill the form

End if

End if

4.1.1 Sample code

<?php

error_reporting();

session_start();

include("connection.php");

?>

<html>

<head>

<link rel="stylesheet" type="text/css" href="setting3.css" />

<link rel="stylesheet" type="text/css" href="setting2.css" />

<link rel="stylesheet" type="text/css" href="setting4.css" />

42
 <title>online auction</title>

<script type="text/javascript" src="js1.js"></script>

</head>

<body>

<div id='Main' align=center>

<div id='mainblock' align=left>

<div id='toptext'>

<!-- Header Table -->

<table border="0" cellpadding="0" cellspacing="0">

<tr valign="top">

<td><?php

include("header.php");

?>

</td>

</tr>

</table>

</div>

<!-- End of Header Table -->

<!-- Menu Bar -->

<div id="navigationmenu">

<table border="0">

43
 <tr>

<td>

<?php

include("menu.php");

?>

</td>

</tr>

</table>

</div>

<!-- End of Menu Bar -->

<div id='leftnavigation'>

<!-- Left Menu -->

<?php

include("leftmenu.php");

?>

<!-- End of Left Menu -->

</div>

<div id='rightnavigation'> <!-- End of Content Table -->

44
<!-- Right Menu -->

<?php

include("rightmenu.php");

?>

<!-- End of Right Menu -->

</div>

<!-- Content -->

<div id='content'>

<table>

<tr><td>

<h2> <u>auctioneer Registeration page</u></h2>

<form action="" method="post">

<table><tr><td>

<tr><td>auctioneer id:</td><td><input type="text" name="aid"

required=""pattern="^[a-zA-Z0-9/ ]+"></td></tr>

<tr><td>FirstName:</td><td><input type="text" name="fname"

pattern="^[a-zA-Z ]+"required=""/></td></tr>

45
<tr><td>SecondName:</td><td><input type="text" name="sname"
pattern="^[a-zA-Z ]+"required=""/></td></tr>

<tr><td>LastName:</td><td><input type="text" name="lname"

pattern="^[a-zA-Z ]+"required=""/></td></tr>

<tr><td>Gender:</td><td>Male:<input type="radio" value="male"

name="sex"required="">

Female:<input type="radio" value="female"

name="sex"required=""></td></tr>

<tr><td>City:</td><td><input type="text" name="city" pattern="^[a-zA-Z0-

9/ ]+"required=""/></td></tr>

<tr><td>Gmail:</td><td><input type="email" name="gmail"

required=""/></td></tr>

<tr><td>phone number:</td><td><input type="text" name="phone"

pattern="^[+0-9/ ]+" required="" /></td></tr>

<tr><td>question:</td><td><select name="question">

<option value="what" selected>what is</option>

<option value="what is" selected>what is your</option>

<option value="what is your" selected>what is your lovely</option>

<tr><td>answer:</td><td><input type="text" name="answer" pattern="^[a-

zA-Z ]+"required=""/></td></tr>

<tr><td>password:</td><td><input type="password" name="pwd"

required=""></td></tr>

<tr><td>confirm password:</td><td><input type="password"

name="cpassword" required=""></td></tr>

<tr><td>date:</td><td> <div class="bootstrap-iso"><input type="date"

name="date" placeholder="dd/mm/yyy"/></div></td></tr>

46
<tr><td><input type="submit" name ="register" value="register
user"></td><td>

<input type="reset" value ="reset"></td></tr>

</table>

</form>

<?php

include("connection.php");

if(isset($_POST['register']))

$aid=$_POST['aid'];

$fname=$_POST['fname'];

$sname=$_POST['sname'];

$lname=$_POST['lname'];

$sex=$_POST['sex'];

$city=$_POST['city'];

$gmail=$_POST['gmail'];

$phone=$_POST['phone'];

$uname=$_POST['fname'];

$question=$_POST['question'];

$answer=$_POST['answer'];

$upass1=$_POST['pwd'];

$cpass=$_POST['cpassword'];

$role="auctioneer";

$date=$_POST['date'];

47
 $cryptKey = 'qJB0rGtIn5UB1xG03efyCp';

//$upass=base64_encode( mcrypt_encrypt( MCRYPT_RIJNDAEL_256,

md5( $cryptKey ), $upass1, MCRYPT_MODE_CBC,
md5( md5( $cryptKey ) ) ) );

//$upass=md5($upass1);

if($upass1==$cpass)

$p=strlen($phone);

if ($p==10||$p==13)

$query="INSERT into
auctioneer(aid,fname,sname,lname,sex,city,gmail,phone,date)values('$aid','$fn
ame','$sname','$lname','$sex','$city','$gmail','$phone','$date')";

$result=mysql_query($query);

if($result)

echo "<div id=success>User successfully registered!</div>";

else

48
 echo "<div id=success>please enter valid data!</div>";

$query2="Insert into
user(userid,fname,sname,gmail,username,password,role)values('$aid','$fname'
,'$sname','$gmail','$uname','$upass1','$role')";

mysql_query($query2);

else

echo"please enter valid phone number";

else

echo "<div id=success>please enter identical conformation

password!</div>";

?>

49
 </td>

</tr>

</table>

</div>

<div id='foot'> <!-- Footer -->

<table width="100%" border="0" cellpadding="0" cellspacing="0">

<tr>

<td> <?php

include("footer.php");

?>

</td>

</tr>

</table>

<!-- End of Footer -->

</div> </div></div>

</body>

</html>

Auctioneer registration form

50
 4.2 Testing
4.2.1 Introduction
Testing is the final phase of implementation. Testing is a process to show the correctness of the
program. Testing is checking of the system work ability in an attempt to discover errors and
avoiding such errors from the system. In this the team members tested the entire system as a
whole with all forms, code, modules.

4.2.1.1 unit testing:

Unit testing focuses verification effort on the smallest unit of software design that is the
module. Using procedural design description as a guide, important control paths are tested to
uncover errors within the boundaries of the module. The unit test is normally white box testing
oriented and the step can be conducted in parallel for multiple modules.In our project we test
all modules and the system components work correctly.

51
 4.2.1.2 System Testing:
System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer-based system. Althou gh each test has a different purpose, all work to verify that
all system elements have been properly integrated to perform allocated functions.we test our
system and work correctly.

4.2.1.3 Integration Testing:

Integration testing is a systematic technique for constructing the program structure while
conducting test to uncover errors associated with the interfacing. The objective is to take unit
tested methods and build a program structure that has been dictated by design.

Implementation of the Database

The implementation document helps users on how to work with the system. It acts as a user
manual and it helps users not to be the system confused with. It includes sample forms and
some selected fragment code. It gives the users a brief over view of the system. This document
describes the project implementation for developing the prisoner information management
system. The project implements PHP, MySQL and standard HTML.

52
4.2 Configuration of the Application Server
Firstly instal the software adobe dreamwaver or Notepad++ and wamp server, after that follow
the steps:
Step 1- put the developed system folder on C:\wamp\www on your computer.
Step 2- Active your installed wampserver software
Step 3-open the browser on your computer and write (localhost/foldername/index.php) on the
place of URL or as a url.
Step 4- finally you can view and access the sysem.
NB: Before you are run the system you must have import the databse which is arrived on your
folder to the wamp server databse (on phpmyadmin).
Follow the folllowing steps to success you activity
Step one install the wamp server.

Installation process

53
54
55
56
Installation process

57
 CHAPTER FIVE

5.Conclusions and Recommendation

5.1 conclusions
The existing oline auction management system is performs or doing based on manually like,
record bindder data, generate report, searching for bidder data and deleting data, so the
developed “web based Oline Auction Management System ” has been developed aimed in
such a way that it meets almost some the criteria that are expected by the user and in further, if
any further enhancements are required by the user, it can be done with minimal effort such as
design or coding. The team gathered all the requirements by studying the existing system ,
analyzed the system in terms of the tasks it is performing and the types of users using the
system and problems that to be overcome in the proposed system. All the requirements that are
gathered in the Analysis phase are given a basic structure by following the Design principles in
the Design phase and data from the analysis stage is converted in to design in the form
interface.

5.2 Recommendations
Nowadays, the world is highly becoming a competitive world in technology. So, Organizations
should have to divert their attention on using the recent technology to facilitate their work
properly. This can be real if they are able to use recent information technology (IT) to
successfully achieve their objective.
We are recommended Oline Auction to use the developed system in order to facilitate the
work process and to reduce wastage time to manage all bidder information in the organization.
Finally, we would like to recommend some points on the usage and accessibility of this system.
The organization should have adequate computer facilities for the introduction of the new
system.
These systems need an educated person so every user’s should know about how
computer works and take basic computer training skills.

58
 REFERENCE
[1] f. g. fethiya mehammed, "online auction management system," 19 april 2004. [Online].
[Accessed 21 november 2016].

[2] E. Torlak, 2 Spring 2015. [Online]. Available:

https://courses.cs.washington.edu/courses/cse403/15sp/lectures/L10.pdf. [Accessed 12
december 2016].

[3] M. Felici, 14 January 2004. [Online]. Available:

http://www.inf.ed.ac.uk/teaching/courses/seoc/2009_2010/notes/10_notes.pdf. [Accessed
23 Decmber 2016].

[4] D. Bell, 15 Sep 2004. [Online]. Available:

https://www.fing.edu.uy/inco/cursos/ingsoft/iis/files/UML-Class%20diagram.pdf.
[Accessed 19 December 2016].

59