University of Gondar

College of Informatics
Department of Information Technology
Web Based Bidding Management System for Aste Tewodros Campus
Prepared By:
Name ID No.
1. Melak Encahalew………………………. GUR/00201/11
2. Melkamu Yalew………………………. GUR /00251/11
3. Sewayehu Monen………………………GUR /00245/11
4. Kirubel Hilemariam……………………GUR/00124/11
5. Mekonen Mengesha …………………...GUR/01800/10
An industrial project-One submitted to the Department of Information Technology in Partial
Fulfillment of the Requirements for the Degree of Bachelor of Science in Information Technology.

Advisor: Amare T. (MSc.)

August , 2022 Gondar, Ethiopia

i
 Declaration
This Group Project entitled “web-based bidding management system” has been read and approved
as meeting the preliminary project requirements of the Department of Information Technology in
partial fulfillment for the award of Bachelor of Science degree in Information Technology,
University of Gondar, and Gondar, Ethiopia.
The idea and work of the project is original and our own. We have sign as follows to assure the
originality of the work Group members:

No. Name ID No signature Date

1. Melak Enchalew GUR/00201/11 ------------------- -------------

2. Melkamu Yalew GUR/00251/11 --------------------
---------------
3. Sewayehu Monen GUR/00245/11 -------------------- ---------------
4. Kirubel Hailemariam GUR/00124/11 --------------------- ---------------

5. Mekonen Mengesha GUR/01800/10 ---------------------- ---------------

Advisor:

Name Signature Date

1. Amare Tesfaw ---------------------- --------------

Examination Board:

Name Signature Date

1. ---------------- ---------------

2. ----------------- ---------------

Chairman:

Name Signature Date

1. --------------- ----------------

ii
Acknowledgment
First, we would like to thank almighty GOD who inspire us to start and finish the project in good
way. And also next we would like to thank university of Gondar to formulate projects should did in
Informatics faculty .Then We wish to express our sincere gratitude to the Faculty Of informatics,
for providing as an opportunity To perform the project work on “Web Based Bidding Management
System” .We sincerely thank our project Advisor, Amare for her kindness in advising and guiding
us to through the right path, from the starting until the completion of this document. Last but not
least. We would to thank for all class of fourth year Information Technology students and our
friends for sharing many useful ideas.

iii
Contents
Declaration...................................................................................................................................... ii

Acknowledgment ........................................................................................................................... iv

Abstract .......................................................................................................................................... ix

Abbreviations ............................................................................................................................x

Chapter One ........................................................................................................................................ 1

1. Introduction ................................................................................................................................. 1

1.1. Background of the organization............................................................................................... 2

1.2. Background of the study .......................................................................................................... 2

1.3. Statements of the problem ....................................................................................................... 3

1.4. Objective of the project ............................................................................................................ 4

1.4.1. General Objective................................................................................................................. 4

1.4.2. Specific Objectives ............................................................................................................... 4

1.5. Methodology for the project .................................................................................................... 4

1.5.1. Data Collection Methodology ................................................................................................ 4

1.5.2. System Development Approach ........................................................................................... 5

1.6. Development Tools .................................................................................................................. 5

1.7. Scope of the project................................................................................................................. 6

1.8. Constraints ............................................................................................................................... 6

1.9. Alternative Solution................................................................................................................. 7

1.10.1 Operational feasibility .......................................................................................................... 7

1.10.2 Economic feasibility ............................................................................................................ 7

1.10.3. Technical feasibility ............................................................................................................ 8

1.10.4. Organizational Feasibility ................................................................................................... 9

1.11. Proposed solution ...................................................................................................................

9

iv
 1.12. Significance of the project .............................................................................................. 10

1.13. Beneficiaries of the Project.................................................................................................. 10

1.14. Hardware and Software tool ................................................................................................

11

1.15.1. Hardware cost .........................................................................................................................

12

1.15.2. Software Cost.......................................................................................................................... 12

1.15.3 Transport Cost........................................................................................................................ 13

1.15.4. Communication cost ............................................................................................................. 13

1.16.Time Schedule............................................................................................................................

16. CHAPTER

TWO .............................................................................................................................. 15

2. SYSYTEM ANALYSIS ............................................................................................................... 15

2.1. Introduction ............................................................................................................................ 15

2.2. Description of existing system............................................................................................... 15

2.3. Overview of the new system.................................................................................................. 18

2.4. Input and output of the system............................................................................................... 18

2.5. Requirements Analysis of the new system ............................................................................ 19

2.6. System architecture diagram.................................................................................................. 21

2.7. System use case diagram ....................................................................................................... 21

2.9. Activity Diagram ................................................................................................................... 36

2.10. Sequence diagram ................................................................................................................ 39

2.11 Class Diagram....................................................................................................................... 48

Chapter..............................................................................................................................................

49 3.

Design ...........................................................................................................................................49

3.1. Introduction ............................................................................................................................ 49

3.2. Process modeling ................................................................................................................... 49

v
 3.2.1. Collaboration....................................................................................................................... 49

3.2.3. Deployment Diagram .......................................................................................................... 56

CHAPTER FOUR…………………………………………………………………………………59
Implementation and Testing……………………………………………………………………….59
4.1. Form or Interface Design…………………………………………………………………….60
4.1 Programming or coding……………………………………………………………………...66
4.2. Testing…………………………………………………………………………………….....74
4.2.1. Unit testing………………………………………………………………………………….74
4.2.2. Integration testing…………………………………………………………………………..74
4.2.3. System testing …………………………………………………….………………………….74
4.3. Installation…………………………………………………………………………………….75
CHAPTER FIVE………………………………………………………….…………......................76
Conclusion and Recommendation ………………………………………………………………...76
5.1. Conclusion………………………………………………………………………………….76
5.2. Recommendation………………………………………………….......…………………..76
References .........................................................................................................................................77

Appendix…………………………………………………………………………….......................78

vi
List of Figure

Figure 1: existing system form ......................................................................................................... 17

Figure 2: input output process of the system. ................................................................................... 19
Figure 3: System architecture diagram ............................................................................................. 21
Figure 4 : System use case diagrams ................................................................................................ 22
Figure 5: Login Activity diagram..................................................................................................... 36
Figure 6: Seller Activity diagram..................................................................................................... 37
Figure 7: Buyer Activity Diagram .................................................................................................... 38
Figure 8: login sequence diagram..................................................................................................... 40
Figure 9: register sequence diagram ................................................................................................. 42
Figure 10: Notify sequence diagram ................................................................................................ 43
Figure 11: upload sequence diagram ................................................................................................ 45
Figure 12: bid sequence diagram ...................................................................................................... 47
Figure 13: Class Diagram................................................................................................................. 48
Figure 14: Collaboration diagram for login...................................................................................... 51
Figure 15: Collaboration diagram for register .................................................................................. 52

Figure 16: Collaboration diagram for buyer ..................................................................................... 53

Figure 17: Collaboration diagram for upload................................................................................... 55
Figure 18: Collaboration diagram for bidding timer ........................................................................ 56
Figure 19: Deployment diagram..................................................................................................... 58
Figure 20: User interface design for home page……………………………………………………60

Figure 21: User interface design for signup page……………………………………………………

61

Figure 22: User interface design for login page………………………………………………………62

Figure 23: User interface design for admin page………………………………………………………63

Figure 24: User interface design for supplier page……………………………………………………64

Figure 25: User interface design for buyer page………………………………………….……………65

vii
List of table
Table 1 Development tool................................................................................................................. 5
Table 2 Hardware cost in the project ................................................................................................ 12
Table 3 Software cost in the project ................................................................................................. 12
Table 4 Transport cost ...................................................................................................................... 13
Table 5 communication cost ............................................................................................................. 13
Table 6 Project Schedule .................................................................................................................. 14
Table 7 Login use case documentation. ........................................................................................... 27
Table 8: Register use case documentation ........................................................................................ 28
Table 9: Notify use case description ................................................................................................. 29
Table 10: Upload item use case documentation ............................................................................... 30
Table 11: Search use case documentation ........................................................................................ 32
Table 12: View use case description............................................................................................... 33
Table 13: Delete use case documentation ........................................................................................ 34
Table 14: Place bid use case description .......................................................................................... 36

viii
Abstract
Open Bidding is a method of procurement that could be used for National Competitive Bidding and
International Competitive Bidding. This is a method of procurement where by qualified and
eligible bidders are invited to bid through mass media, such as newspaper, radio and TV. In
addition to these Medias, companies may also use websites for advertisement. It is bidding system
that is not private it is opened for all qualified bidders. Our project is concern with develop
webbased bidding management system for Aste Tewodros campus. This system enables us to
perform tender online using need of internet without goes to the bid place physically.

The document shows the detail study on bidding management system. Like interview and
documents analysis have been used to collect information about the system. The new system is
proposed and analyzed using object-oriented methods like Use Case Diagram, Activity Diagram,
and Sequence Diagram. A specification of the new system is designed using deployment diagram
and persistence diagram. A detailed algorithm is also developed for each method identified in the
class diagram. The design part also incorporates database design at the back end and interface
design at the front end.

ix
Abbreviations
PHP: Hypertext pre-processor

MySQL: My Structured Query Language

UC: Use Case

CSS: cascading style sheet

HTML: hypertext markup language

UML: Unified Modelling Language

ODD: Object Design Diagram

OO: Object Oriented

OOSAD: Object Oriented System Analysis And Design

OOAD: Object Oriented and Design

UI: User Interface

GUI: Graphical User Interface

GB: Giga Byte

TV: television

XAMP: Cross Platform Apache MySQL and Php

WAMP: windows Apache MySQL and Php

UOG: university of gondar

x
 Chapter One

1. Introduction
The main concern of this project is developing a bidding system, which is widely used procurement
method in our country in general and in our institute in particular. There are different kinds of bidding
system. These are Open Tender, Limited/Restricted Competitive Bidding, Direct Procurement/Single
Source Procurement, Request for Proposal, Request for Quotation/Performa Purchasing and Two Stage
Bidding/Tendering. Open Tender is a method of procurement that could be used for National
Competitive Bidding and International Competitive Bidding. Limited/Restricted Competitive Bidding
methods where by an initiative to bid is sent to a limited number of qualified firms who are interested to
participate/compete in the tender rather than floating the invitation through open media. Direct
Procurement/Single Source Procurement method allows procurement of goods and services directly
from a single firm for various reasons. Request for Quotation/Performa Purchasing method is commonly
used for low value and low volume procurement (mostly operational and stock goods) made by
requesting a limited number of suppliers for quotations. Request for Proposal is a procurement method
mainly applicable to the procurement of consultancy service. Two Stage Bidding/Tendering is a method
where by two invitation to bids are issued for a single purchase. From this six procurement method our
teams select open tendering system, because open tendering is opened for all qualified bidders or all
suppliers can participate in the tender and executed in clear procedure. In the current open tender system,
there exist some problem and also bidders can’t have satisfaction in the current system. The current
bidding system, bidders must attend specific place; otherwise, they can't participate for the bid. So, our
team aim to develop web based open bidding system that avoid problems both bidders and organizations
might face [3].

1
1.1. Background of the organization
University of Gondar is located in Amhara region of Ethiopia, and is one of the 44 Universities in
Ethiopia. The University has five Campuses one of them is Aste Tewodros campus is the main campus
of the University. College of Natural and Computational Science, College of Veterinary and Animal
Sciences, Faculty of Informatics and Institute of Biotechnology are found here [6].

Nowadays the way we think and we live is being shaped by technology. As the advancements in the
technology are Spreading rapidly and widely, those who could make advantage of these advancements
are making their life better and easy.

Open bidding is a method of procurement where by qualified and eligible bidders are invited to bid
through mass media, such as newspaper, radio and TV. In addition to these Medias, companies may also
use websites for advertisement.

1.2. Background of the study

Nowadays the way we think and we live is being shaped by technology. As the advancements in
technology are spreading rapidly and widely, those who could take advantage of these advancements are
making their life better and easy.

There are two major types of Bidding:

Forward Bidding [5]:

Buyer Buyer
3 4
Buyer Buyer
2 5

Buyer Buyer
Supplier
1 6

2
Reverse Bidding [5]:

Supplier 3 Supplier 4

Supplier2 Supplier 5

Supplier 1
Buyer Supplier 6

In reverse bidding the roles of the buyer and the seller are reversed, with the primary objective to drive
purchase prices downward. While forward bidding provides suppliers the opportunity to find the best
price among interested buyers, reverse bidding gives buyers a chance to find the lowest-price supplier.
During a reverse bidding, suppliers may submit multiple offers, usually as a response to competing
suppliers’ offers, bidding down the price of a good or service to the lowest price they are willing to
receive. The reverse bidding is widely used by corporations, state and local Governments, and other
organizations. For example, one company may post an auction for developing some project the lowest
bid will be the winner of that auction.

1.3. Statements of the problem

Currently university of Gondar in Aste Tewodros campus performs biding service with the old
traditional manual system. Based on the current system procurement team prepares a lot of open bidding
notice or advertisements to buy different service, goods, work and consultancy service. During this
transaction there are so many problems both buyer and supplier face.

During the bidding procedure, the buyer encounters numerous issues. The first issue is that many bidders
are unable to participate in the bidding process because suppliers are unable to see or hear the
advertisement .The second issue is that time is wasted; in other words, it takes one or more days to get
bid documents to the federal press for distribution through media or newspaper, to register each supplier
with their complete information on a specific day; and when the tender is opened, suppliers are unable to
reach in a specific day. The third issue is the high cost of materials (resource-intensive), such as paper
and printers. The fourth problem is losing of data or information because of data handling method of
existing system is manual or paper based.

3
Supplier faces many problems during bidding process. The first problem is cannot get full information
about bidding; it might not view all advertisement or view after left their closed days. The second
problem is maximizing transport cost. This means if supplier lives far away from tender place it wastes
high cost to register in the bidding.

1.4. Objective of the project

1.4.1. General Objective

The general objective of this project is to develop Web Based Bidding Management System for Aste
Tewodros campus.

1.4.2. Specific Objectives

In order to achieving the general objective, the following specific objectives are required:

• To identify the problem of the existing system for biding related service in Aste Tewodros
campus.
• To design the new biding system based on the identified requirements
• To develop database for bid registration and biding file management.
• To design bid registration and upload item forms for bid
• To test the functionality of the bidding system

1.5. Methodology for the project

In developing this project, we have been using the following standard development methodologies.

1.5.1.Data Collection Methodology

The main data source of our project is that by studying the existing system of bidding activity that takes
place in Aste Tewodros campus Finance and Budget. For the development of the proposed system the
team uses different data sources such as books, bid document, internet and brochures.

• Interview
• Observation
• Document analysis

4
1.5.2. System Development Approach
It is a collection of phases, procedures, guidelines, strategies, tools, documentation, and training that are
recommended for improving the quality and facilitate software project development.

Because of its greater benefit of polymorphism, abstraction, and encapsulation, we use the object-
oriented system analysis and design (OOSAD) approach. An object-oriented system analysis and design
methodology, the purpose of we use OOanalysis and design is Identifying the objects of a system,
identify their relationships and generate a design which can be converted into applications using OO
languages, it is easy to understand, it is easy to maintain. Due to its maintainability OOAD is becoming
more popular day by day, it provides re-usability, it reduces the development time & cost and it
improves the quality of the system due to program reuse.

1.6. Development Tools

To build our system, we will use the following software tools:

Table 1 Development tool

No, Development tool Activity
1 Notepad++ important to write our html code and PHP
codes

2 PHP (hypertext preprocessor) Used to develop or create website

3 Edraw-Max setup To develop the UML diagrams
4 Browser Used to browse user interface and
reference

5 JavaScript Used to validate data and develop different

messages

6 Micro Soft word 2010 Used to write documents

7 WAMP server Used to create the database

5
1.7. Scope of the project
The scope of our project plans and targets in developing web-based bidding management system to
replace and solve the problems of the existing system within Ate Tewodros campus web-based bidding
management system is designed suppliers apply online to get advertisement and new bidding information. The
system is bounded in the following tasks.

• Individual customers both to create auctions, and participate in auctions by bidding

• Search auction status and update the auction status if its closed..
• Create auction by uploading different products
• Registration of supplier and purchased items
• View bidder history and register item.
• Bidders participate on the auction by visiting the items
• Notify the winner of the bidding.
• The supplier View winner buyer
1.8. Constraints
Constraints refers to a number of factors that we encountered during the development of this system,
such as during the data collection or gathering stage, system review, system design, and also during the
project's implementation and testing stages, all of which prevented us from to add some basic features.

These are: -

Time constraint: We are students and in the learning process we have a shortage of time to include
some basic features to the project. The time given for this project was too short to go through,
understand the system and come up with an updated, new and easily usable and reasonable system.

Resources constraint: like failure of electric power, network connection, and others may affect our
project to complete on the specified time.

Budgetary constraints: Because we are students, financed ileus are difficult for us to spend a certain
amount of money on the project.

1.9. Alternative Solution

Some of the alternative solutions we recommend are: -

6
Developing web-based system: - Creating an online system that can be used if the internet is available.
As is clear, gaining internet access is becoming easier and more economical these days. As a result, it is
the most advantageous and recommended as alternative solution.

Developing a mobile based application: - implies creating a mobile application that can operate on
Android and be accessible using smart phones.

Developing a desktop application: creating a desktop application that can run independently on the
organization's desktop or laptop devices. Although this backup plan may not be the optimal answer, we
agree that it should be used as a backup/reserve.

1.10. Feasibility Analysis

Feasibility study is conducted to evaluate the feasibility of the project in various aspects. For our Project
we have done the feasibility study and our project is feasible in almost all aspects. The Following sub
chapters are brief description of each aspect of feasibility study.

1.10.1 Operational feasibility

Operational feasibility is mainly concerned with issues like whether the system will be used if it is
developed and implemented in the real world. When the system is applied to operation, we are fully
confident that the system will be operationally Feasible because as we will develop the system that is
easy to use. With a little training anyone will be able to understand and will be able to handle with the
system easily. They gave us necessary information and resource about the existing system. All these
shows that their willingness for the successful development of the new system so as to get rid (removed)
of the previous manual system. And also the system is operationally feasible as it is very easy for the end
users to operate it.

1.10.2 Economic feasibility

The proposed system is economically feasible because: -

• The system requires very less human power.

• The system will provide fast and efficient automated environment.

7
Cost benefit analysis

Cost benefit analysis is also known as (benefit cost analysis) is process by which an organization can
analyze decision, system or project. According to our determination the project we are going develop
will provide the next benefits as

The team members calculated the corresponding tangible benefits with sample monetary: to calculate the
following things will be considered.

Total number of employees in exiting system =19

Average salary of each employee per month=5000.00Birr

Total money required for payment per year=19*5000*12=1,140,000.00Birr

Average number of employees needed when the new system is deployed=10

Average salary of each employee per month=5000.00Birr

Total money required for payment per year=10*5000*12=600,000.00Birr

Difference between before and after deployment per year =1,140,000.00Birr -600,000.00Birr
=540,000.00Birr

1.10.3. Technical feasibility

We develop the system by the available tools, since our system is built with available tools and by the
group member.so the system is technically feasible.

The system is going to be developed by following the php language, html, java script, MySQL, CSS, and
Diagram drawing tools. Each of the technology are freely available and the technical skill required are
manageable. Time limitation of the product development the ease of implementing using these
technologies are synchronized.

Bandwidth required in this application is very low, since it doesn’t incorporate any multimedia aspect.
And we have the ability to develop this system without any difficulty since the supplier has studied the
required methodologies and tools. So, the system will be technically feasible and the system will have
GUI interface and very less user-training is required to learn it.

8
1.10.4. Organizational Feasibility
The system cans organizationally feasible attempts to develop and implement a new system, against the
benefits that would accrue (store) from having the new system in place. This feasibility study gives the
top management the organizational justification for the new system and the system we will developed
based on the policies of the company and it will be developed according to the interest of the
organization. Since it privileges the assets of the organization, so the new system is considered to be
organizationally feasible.

1.11. Proposed solution

In the existing system there are so many problems to adhere those problems we proposed new automated
computerized system that is web-based bidding management system. From the stated idea in the
alternative solutions, out of the three choices, which means from web-based application, mobile based
application and desktop-based application team members will try to study and identify advantage of each
alternative. A desktop-based application requires a hardware supply, which is they need computers for
accessing and also, they are not mobile and freely accessible. So, our proposed system is deploying a
web-based application because of these unique properties.

• Development of convenient system web-based biding system to participate on the tender

everywhere as their own interest.
• It enables the biding to store information on the database.
• Reduce wastage of time for preparing bid document for procurement team.
• Reduce wastage of cost.
• Reduces the number of employees in the bidding.
• Minimize the work load of employee.
• Enable computerized form of information handling method, this protect information from
accessed by unauthorized user.
• The system will enable suppliers get any information about the bidding quickly.

The system has an account that they can access the central database to register, view, and
produce reports easily and more secure. The proposed system will enable the auction to store
information on the database. The errors that occur in paper forms do not occur in our system.

9
 1.12. Significance of the project
This project is focuses on open bidding system. It will cover different activities, such as suppliers can be
registered to the tender in everywhere, system display the list of registered suppliers in the database.

The significance of the system in the supplier side is:-

• Minimizing wastage of time and energy.

• Reducing transport cost
• View winner and also easily registered to the tender.
• Reducing face to face communication from buyer.
• give service without any time constraint
• It increases social interaction between seller and bidder
Significance for the Buyer

• The Aste Tewodros campus procurement team office will be benefited after the completion of
the project in many ways including
• Reduce the workload of employee.
• Reduce redundancy and losing of data
• reduce resource consumption,
• Access of information will be easier, faster, and well-organized way.
• There is no geographical boundary

1.13. Beneficiaries of the Project

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.

10
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.

1.14. Hardware and Software tool

Throughout this project we used the following hardware and software tools to develop our system. Some
of these are listed as follows:

Hardware tool

• Laptop
• Flash (16 GB) and Cable
• Pen and paper

Software tool

• XAMP
• Notepad++
• JavaScript
• PHP
• Edrawmax
• browser
• Microsoft word 2013

1.15. Cost/Budget Estimation

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 by birr.

11
1.15.1. Hardware cost
Table 2 Hardware cost in the project
No Material Amount Price per unit Total price

1 A4 size paper 200 1.00birr 200birr

2 Pen 1 14birr 14birr

3 Flash 32 GB 1 350birr 350birr

4. For Print 200 1.50birr 300birr

5 Cables 1 200birr 200birr

Total 1064birr

1.15.2. Software Cost

Table 3 Software cost in the project
No Material Price per unit

1 Microsoft office 2013 Free

2 Internet explorer Free

3 PHP Free

4 XAMP Free

5 Notepad++ Free

6 Microsoft Visio 2007 Free

7 Edrawmax Free

Total 00.00 Birr

12
1.15.3 Transport Cost
Table 4 Transport cost

13
Transport type From To Cost

14
By Walk UOG Organization Cost free

15
By Walk Organization UOG Cost free

16
Total 0.00

1.15.4. Communication cost

Table 5 communication cost

17
Communication by mobile phone Cost

18
With Advisor 50birr

19
With Project team members 40birr

20
With organization manager 30birr

21
Total 120birr

1.16. Time Schedule

22
Table 6 Project Schedule

23
 CHAPTER TWO

2. SYSYTEM ANALYSIS

2.1. Introduction
In our project we used unified modelling language to model our system. The Unified Modelling
Language (UML) is a general-purpose modelling language in the field of software engineering, which is
designed to provide a standard way to visualize the design of a system. There is different model diagram
in UML that we used to model the system. The techniques and associated notation used for object
oriented analysis and design are incorporated in to a standard object – oriented language called unifies
Modeling language (UML). Important goal of requirement modeling understand the problem that the
new system is to address.

In the project these include the use case diagram, use case description for each use case, sequence
diagram, activity diagram and class diagram of the system as well as system architecture diagram [3].

2.2. Description of existing system

In the existing system bidding are takes place in traditional way or a person must be there physically to
participate on the open bidding system. A traditional open bidding is performed manually that bidders
must be present physically to submit bids document, to view winner and also make agreement to the
institute. After approving bid document prepared by procurement team send to press and distribute
through media or newspaper in order to enable suppliers get information about the notice. Institute buys
item by bid different suppliers who have submit bids document and select winner by assess their bids
document based on appropriate price and quality of item.

Performance of any system is required exhibition of users `need of the system. The current system’s
performance is weak. This is due to the following reasons: -first the acceptable through put rate is
relatively high i.e., the time required from initiation to completion of a particular task is relatively high.
For example, bidding one item it may take a day or more due to its manual operation. The system
manipulates and manages all of these and other records manually on papers.

Every record of the existing system is paper based that stored in shelf, so, it is difficult to control and
secure these manual records, since it doesn’t have any authentication and authorization system.

24
Due to the manual operation most of the activities are prone to wastage of resources like papers, man
power, time etc., to produce the corresponding outputs. This makes the current system inefficient while
utilizing resources. There should be a mechanism that reduce wastage of resources and that make the
system to be efficient.

Forms and other documents of the existing systems

25
Figure 1: existing system form

26
2.3. Overview of the new system
In the existing system there are so many problems listed on the above to adhere those problems we
proposed new automated computerized system integrated to technology that is web-based bidding
management system. Development of convenient system “web-based bidding management system” to
participate on the auction everywhere as their own interest. The proposed system will enable the bidding
to store information on the database. Items are uploaded on bidding house websites and displayed in list
view form in web application, and buyers can access to learn more details about them and once buyers
see items, they are interested in.

2.4. Input and output of the system

The following section will summarize the function of existing system with their input, process and
output.

Input

• Uploading of items that are necessary to create bidding.

• Create the process of bidding by providing different items.
• Password and username
• Participate on the bidding.
• Reads the items provided by the auctioneer.

Process

Sellers post notice regarding the items that wants to bid with a specified day without initial cost in case
of open bidding. Then bidders want to reach the place physically in the specified day. Finally participate
on the bidding. If the buyer becomes winner makes payment by using bank, then takes the items.

27
Output

• The system display login page

• Sending a notification
• Notify winner buyer
• The system should store all the data related to all the tasks performed into a database.  Validate
the input information

Input Process Output

1. Product information
2. Seller and buyer 1. Register buyer and 1 Generate user
information seller information information
3..user name and 2. done other process 2 Provide
password manually registration form

Figure 2: input output process of the system.

2.5. Requirements Analysis of the new system

Functional requirement

• Administrative login can access and control admin page and also have full access right to the
system.
• Sellers give item information to the admin that describes the item Login to the system options is
authorized by the administrator.
• Admin upload the auctioned items and register the seller information on the database.
• Any buyer can participate more than one item by using one account.
• Buyers can view all uploaded items and if you have valid account can participate on the auction.

28
 • Bidders participate on the auction by using their own computer device.
• Only store the currently participated buyer with their participated price on a secure database
• The customer shall provide contact information such as a phone number, address, and payment
information.
• The administrator notifies the winner of the bidding.

Nonfunctional requirement

The following are the non-functional requirement associated with the system: -

Security: should allow login to only authorized users

Reusability: Ability of an item that allows it to be used repeatedly unlike a disposable item.

Performance: this system gives service 24 hours per day with minimum response time so, it is easy to
participate on the auction.

Accuracy: proposed system will be better due to reduction of error. All operation can be done correctly
and it ensures that whatever information is coming from the data base is accurate.

Reliability: The reliability of the proposed system will be better due to proper storage of information
when users access the application and take backup in the cloud if the storage fails.

No Redundancy: In the proposed system can be avoided reputation of data anywhere in the database.

Availability: All data in the system will be available all the time.

Efficiency: The system must ensure allocation and use of services being requested for the users by using
minimum memory storage, cost, time and human power.

User friendly Interface: Users can easily input and retrieve item information from database

2.6. System architecture diagram

Bidding management system will have its own software architecture

29
 Figure 3: System architecture diagram

2.7. System use case diagram

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: -

Register: - sellers are registered to the database.

Login: - administrator must be login to perform all administrative tasks.

Upload product: - sellers task which enables us to advertise the items to the buyer.

Manage account: administrator manage account to seller and buyer

Search: the administration is responsible to search the information of customers and uploaded item
detail either closed or open auction status.

View: the administrator is responsible for visiting the bidder information, uploaded item information and
winner buyer information.

Bid: the potential bidder or buyer bid the product based on auction status.

Notify: - the administrator notifies the auction winner.

30
Figure 4 : System use case diagrams

31
2.8. Use Case Narrative

Based on the above use case diagram and the identifications made earlier we now will proceed to
use case description part. In this sub section each use case will be described and clarified
thoroughly.
Use case Name Login

Use case ID UC01

Actor(s) Administrator

Description Required for login to the system

Flow of action: Actor Action System response

Step 1: admin wants to log to

the system

Step 2: open the system

Step 3: The system displays the

Step 4: enter user name and login form.
password.

Step 5: Submits the form.

Step 6: check on the database

Step 7: Notifies about the status of

login (success or failure).

Step 8: Use case ends.

Alternate courses of The system displays the error input message.

action (username and
The system redirects the administrator to step4 i.e., to enter

26
password is incorrect) username and password Use
case ends.

Precondition: The admin must have a valid username and password

Post condition: The administrator successfully login to the system.

Table 7 Login use case documentation.

Use case Name Register

Use case ID UC02

Actor(s) seller, purchaser

Description Required for register the seller and buyer information

Flow of action: Actor Action System response

Step 1: customer wants to

register on the bidding
database.

Step 2: Select the register

link.

Step 3: The system displays the

registration form.
Step 4: Fill registration form.

Step 5: Submits the form.

Step 6: Validates the input data in

the form on the database.

Step 7: Notifies about the status of

registration (success or failure).

27
 Step 8: Use case ends.

Alternate courses of The system displays the error input message.

action (if filling the
form is incorrect) The system redirects the administrator to step 4 i.e., to fill incorrect
registration form Use case ends.

Precondition: The customer must have a valid trade license and password

Post condition: The customer information registered to the database.

Table 8: Register use case documentation

Use case Name Notify

Use case ID UC07

Actor(s) Administrator

Description Required to notify the winner buyer

Flow of action: Actor Action System response

Step 1: The administrator

wants to notify the winner.

Step 2: Select view link.

Step 3: The system display winner

Step4: click on the notify link buyer
on each row

Step 5: the system display notify

28
 Step 6: fill notify form form

Step7: click on notify

Step 8: validate the given input

Step 9: the system notify the status

of notifying.

Step 10: use case

Precondition: There are winner buyers on the database

Post condition: Successfully notify the winner.

Table 9: Notify use case description

Use case Name Upload item

Use case ID UC04

Actor(s) Seller

Description Required to upload item on the auction system to create auction.

29
Flow of action: Actor Action System response

Step 1: the seller wants to

upload item to create auction.

Step 2: select on upload link.

Step 3: the system display upload
form

Step 4: fill the upload form

Step 5: Submits the form Step 6: validates given input

Step 7: the system notifies about

the status of upload

Step 12: Use case ends.

Alternate courses of The system display error message when upload item is incorrect
action
The system redirects the seller to step 4.

Use case ends.

Precondition: First seller has valid trade license that is registered on the auction.

Post condition: An auction will now be created and the buyers can participate on the
auction.

Table 10: Upload item use case documentation

Use case Name Search

Use case ID UC05

Actor(s) Administrator

30
Description Required to Search Upload item and seller information.

Flow of action: Actor Action System response

Step 1: Administrator wants to

search item

Step 2: Select Search link.

Step 3: The system display the

Step 4: Fill search form. search form.

Step 5: Submits the form.

Step 6: Validates the input data in

the form.

Step 7: Notifies about the status of

searching (success or failure).

Step 8: Use case ends.

Alternate courses of The system displays the error input message.

action (if the filling
the form is incorrect) The system redirects the administrator to Step 4 i.e to fill search
form.

Use case ends.

31
Precondition: The administrator must login in to the system

Post condition: The required information now be displayed

Table 11: Search use case documentation

Use case Name View

Use case ID UC06

Actor(s) Administrator

Description Required to view the customer Information or the uploaded item or

the winner buyer.

Flow of action: Actor Action System response

Step 1: The administrator

wants to view customer
information or uploaded item
or winner buyer.

Step 2: Select view link.

Step 3: The system displays all

customer information or upload
item.

Step 4: use case ends.

Alternate courses of The system displays no information message

action (if no
information or upload
item)

32
Precondition: Administrator first login in to the system and registered customer
information in the database or uploaded item or winner buyer.

Post condition: View all available information

Table 12: View use case description

Use case Name Delete

Use case ID UC07

Actor(s) Administrator

Description Required to delete the customer Information or the uploaded item at

the end of auction.

33
 Flow of action: Actor Action System response

Step 1: The administrator

wants to delete customer
information or uploaded item.

Step 2: Select view link.

Step4: click on the detail link Step 3: The system display all
customer information or upload
on each row item.

Step 6: click on the delete Step 5: the system display row data
button
from the whole database

Step 7: the system show the status

of deleting

Step 8: use case ends.

Precondition: Administrator first login in to the system and view registered

customer information in the database or uploaded item.

Post condition: Delete unnecessary customer information or uploaded item after the
end of auction.

Table 13: Delete use case documentation

34
Use case Name View upload item, register

Use case ID UC09

Actor(s) Purchaser

Description Required to view uploaded item on the auction

Flow of action: Actor Action System response

Step1: the customer wants to

buy an item.

Step 2: open web based app

Step 3: The application displays the

item list.

Step 4: view item list

Step 5: click on bid link. Step 6: the application display form

Step 7: Fill place bid form.

Step 8: click on send button Step 9: The application notifies

about the status of placing bid of
an item.

Step 10: Use case ends.

35
 Alternate courses of The system displays the error.
action:(if the trade
license is not valid or The application redirects the customer to step 7 i.e. to fill the place

have no account no) bid form.

Use case ends.

Precondition: The buyer must have valid bank account or valid trade license

Post condition: The bidder now competes among other buyers to buy the item on
which the bid was placed.

Table 14: Place bid use case description

2.9. Activity Diagram

We used activity diagram to describe dynamic aspects of the system. Activity diagram is basically
a flow chart to represent the flow form one activity to another activity. The activity can be
described as an operation of the system.

36
 admin login
page<<UI>>

enter username
and password

click l ogin

validate the valid display home

input page

invalid

Figure 5: Login Activity diagram

37
 open system

upload p roduct

yes
place product sell product? no

wait until the no

winner is is ther a winner ? ex tend dead line
notified

yes

au ction exp ired

Figure 6: Seller Activity diagram

38
 open app

view product

yes no
place bid buy product?

no

wait for yes

E nd of Auction? am i a winner??
notification

no yes

Figure 7: Buyer Activity Diagram

39
2.10. Sequence diagram
In our system the sequence diagrams that we identified and presented are sequence diagram for
login, registration, bidder and others. Each sequence diagram in the bidding management system is
displayed as follows.

2.10.1 Sequence diagram for login

5:
check;

40
 Figure 8: login sequence diagram

2.10.2. Sequence diagram for registration

Next let us see the sequence diagram for registration. To register seller goes through the following
sequences of actions.
41
42
Figure 9: register sequence diagram

43
2.10.3. Sequence diagram for notify

Figure 10: Notify sequence diagram

2.10.4 Sequence diagram for seller upload item

44
upload sequence
diagram seq(4)

upload sequence
diagram seq(4)

45
 Figure 11: upload sequence diagram

2.10.5 Sequence diagram for bidder

46
6 valid account
insert to DB

47
Figure 12: bid sequence diagram

48
2.11 Class Diagram
Class diagram are the basis of object oriented analysis and design. A class diagram shows the
classes of the system, their interrelationships (including, inheritance, aggregation and association)
and the operations and attributes of the classes. Class diagrams are used for wide variety of
purposes, including both conceptual/domain modeling and detailed design modeling.

49
Figure 13: Class Diagram

Chapter

3. Design

3.1. Introduction
The design phase is the architectural phase or the transformation of the analysis model into a
system design model. It seeks to develop detailed specifications that emphasize the physical
solution to the user information technology needs. System design is the process of defining the
components, modules, interfaces, and data for a system to satisfy specified requirements. System
development is the process of creating or altering systems, along with the processes, practices,
models, and methodologies used to develop them. In this chapter, we define the design goals of our
project and decompose the system into smaller subsystems that it can be understandable. We also
select strategies for building the system, such as the hardware/software platform on which the
system will run, the persistent data management strategy and the access control policy. The result
of this chapter is a model that includes a clear description of each of these strategies, a subsystem
decomposition, and a UML deployment diagram representing the hardware/software mapping of
the system [4].

3.2. Process modeling

Process models are processes of the same nature that are classified together into a model. Thus, a
process model is a description of a process at the type level. Since the process model is at the type
level, a process is an instantiation of it. The same process model is used repeatedly for the
development of many applications and thus, has many instantiations. One possible use of a process
model is to prescribe how things should be done in contrast to the process itself which is really
what happens. A process model is roughly an anticipation of what the process will look like. What
the process shall be will be determined during actual system development [1].

3.2.1. Collaboration
A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior of
individual objects as well as the overall operation of the system in real time. Objects are shown as
rectangles with naming labels inside. These labels are preceded by colons and may be underlined.
The relationships between the objects are shown as lines connecting the rectangles. The messages

50
between objects are shown as arrows connecting the relevant rectangles along with labels that
define the message sequencing.

Collaboration diagrams are best suited to the portrayal of simple interactions among relatively
small numbers of objects. As the number of objects and messages grows, a collaboration diagram
can become difficult to read. Several vendors offer software for creating and editing collaboration
diagrams.

51
Figure 14: Collaboration diagram for login

52
Figure 15: Collaboration diagram for register

53
Figure 16: Collaboration diagram for buyer

54
55
Figure 17: Collaboration diagram for upload

56
 Figure 18: Collaboration diagram for bidding timer

3.2.3. Deployment Diagram

UML deployment diagrams show the physical view of our system, bringing our software into the real
world by showing how software gets assigned to hardware and how the pieces communicate.
It is also used to show a collection of nodes and also dependencies of associations among them.
The associations between nodes represent a physical connection. The physical deployment model
provides a detailed model of the way components will be deployed across the system infrastructure.
It details network capabilities, server specifications, hardware requirements and other information
related to deploying the proposed system.

57
Figure 19: Deployment diagram

58
 CHAPTER FOUR

Implementation and Testing

Introduction
In this phase what the group members have done is turning the physical design specification into
working computer code and also application, and then the code is tested until most of the errors
have been detected and corrected. User sites are prepared for new system and user must come
totally on the new system rather than the existing one to get there work done. There are some
managerial activities in this, coding, testing, and installation.

59
4.1. Form or Interface Design

Figure 20 User interface design for home page

60
Figure 21: User interface design for sign up page

61
Figure 22: User interface design for login page

62
Figure 23: User interface design for admin page

63
Figure 24: User interface design for supplier page

64
Figure 25: User interface design for buyer page

65
 4.1.2 Programming or coding

Sample code for home page

<html>

<head>

<link href="images/favicon.ico" rel="shortcut icon">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Web based biding management sysytem for aste tewodros campus</</title>

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

</head>

<body>

<div id="body">

<div id="templatemo_wrapper">

<img src="image/g.jpg" width="200" height="70"/>

<img src="image/ca.jpg" alt="andu" width="800" height="70"/>

<img src="image/d.jpg" alt="andu" width="190" height="70"/></td>

<!-- end of header -->

<div id="toptabmenu">

<ul id="nav">

<li><a href="index.php">ዋና ገጽ</a></li>

<li><a href="about.php">ስለእኛ</a></li>

<li><a href="vission.php">ራዕይ</a></li>

<li><a href="mission.php">ተልዕኮ</a></li>
66
 <!-- <li><a href="createaccount1.php">መለያ ፍጠር</a></li>

--> <li><a href="createaccount13.php">መለያ ፍጠር</a></li>

<!-- <li><a href="register.php">ምዝገባ</a><li>

<li><a href="">ተመልከት</a>

<ul><h1>

<li> <a href="viewuploadd.php">በጫራታ ላይ የቀረበ</a></li>

<li><a href="viewnotification.php">የጫራታዉ አሸናፊ</a></li>

</ul></h1>

</li>&nbsp;&nbsp;

<li><a href="upload.php">መረጃ መጫን</a></li>

<li><a href="bidder.php">ተጫረት</a></li> -->

<li><a href="login1.php">ግባ</a></li>

<li><a href="admin.php">የኣስትዳዳሪው መግቢያ</a></li>

</ul>

</div>

</div>

<div id="templatemo_main" style="background-color:white">

<div id="sidecon">

<div id="left">

Sample code for signup page

67
 document.getElementById('error').innerHTML = 'The first name field is required';

document.getElementById("error").style.color= "red";

document.signupform.fname.focus() ;

return status;

else if(!n.test(fnam))

document.getElementById('error').innerHTML = ' The first name field is incorrect

format';

document.getElementById("error").style.color= "red";

document.signupform.fname.focus() ;

return status;

if(mnam==""||mnam==null)

document.getElementById('error').innerHTML = 'The father name field is required';

document.getElementById("error").style.color= "red";

document.signupform.mname.focus() ;

return status;

else if(!n.test(mnam))

document.getElementById('error').innerHTML = ' The father name field is incorrect

format';

document.getElementById("error").style.color= "red";

document.signupform.mname.focus() ;

return status;

68
 }

if(lnam==""||lnam==null)

document.getElementById('error').innerHTML = 'The grand father name field is

required';

document.getElementById("error").style.color= "red";

document.signupform.lname.focus() ;

return false;

else if(!n.test(lnam))

document.getElementById('error').innerHTML = ' The grand father name field is

incorrect format';

document.getElementById("error").style.color= "red";

document.signupform.lname.focus() ;

return false;

if(gen==""||gen==null)

document.getElementById('error').innerHTML = 'Select the gender field';

document.getElementById("error").style.color= "red";

document.signupform.sex.focus() ;

return false;

Sample code for login page

</style>

<script type="text/javascript">

69
function validate()

var un=document.login.uname.value;

var pas=document.login.pass.value;

var e=/^\w+([.-]?\w+)*@\w+([.-]?\w+)*(\.\w{2,3})+$/;

var u=/^[a-zA-Z]+(([0-9])*(\.+)*(\-+)*(\_+)*(\s+)*([a-zA-Z]))*$/;

var status=false;

if(un==""||un==null)

document.getElementById('error').innerHTML = 'The username/email field is required';

document.getElementById("error").style.color= "red";

document.login.uname.focus() ;

return false;

else if(!e.test(un))

document.getElementById('error').innerHTML = ' The sername/email field is incorrect format';

document.getElementById("error").style.color= "red";

document.login.uname.focus() ;

return false;

if(pas==""||pas==null)

document.getElementById('error').innerHTML = 'The password field is required';

document.getElementById("error").style.color= "red";

document.login.pass.focus() ;

return false;
70
}

else if(pas.length<5)

document.getElementById('error').innerHTML = 'Password should be at least 6 characters ';

document.getElementById("error").style.color= "red";

document.login.pass.focus() ;

return false;

71
Sample code for admin page

?>

<html>

<head>

<link href="images/favicon.ico" rel="shortcut icon">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<meta http-equiv="refresh" content="900;url=indexx.php" />

<title>Web Based Biding Management System For Aste Tewodros Campus </title>

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

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

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

</head>

<body>

<div id="body">

<div id="templatemo_wrapper">

<div class="mainbox">

<td height="130">

<img src="image/b.jpg" alt="andu" width="950" height="70" />

<img src="image/d.jpg" alt="andu" width="240" height="70" />

</td>

</div> <!-- end of header -->

<div id="toptabmenu">
72
<ul id="nav">

<li><a href="home.php">ዋና ገጽ</a></li>

<li><a href="#">የተጠቃሚን መለያ መቆጣጠር</a>

<ul><h1>

<li><a href="users.php">መለያ ፍጠር</a></li>

<li><a href="activateaccount.php"> Activate </a></li>

<li><a href="deactivateaccount.php">deactivate </a></li>

</h1></ul>

<li><a href="notify.php">አሳዉቅ</a></li>

<li><a href="#">ተመልከት</a>

<ul><h1>

<li><a href="viewcustomer.php">የተመዘገበ አጫራች</a></li>

<li> <a href="viewupload.php">በጫራታ ላይ የቀረበ</a></li>

<li> <a href="viewprepayment.php">የጫራታዉ ቅድመ ክፍያ</a></li>

<li><a href="winner.php">የጫራታዉ አሸናፊዎች</a></li>

<li><a href="viewbidder.php">የጫራታዉ ተሳታፊዎች</a></li>

<li><a href="viewbidderhistory.php"> ሙሉ የጫራታዉ ተሳታፊዎች</a></li>

</ul></h1>

73
4.2. Testing
Testing is a procedure to show the correctness of the program and designed to analyses the logic
used in the implementation of the System. In the case of our project we use unit, function and
system testing method.

4.2.1.Unit testing:
In unit testing, each module (roughly a section of code that performs a single function) is tested
alone in an attempt to discover any errors that may exist in the module’s code. We use unit testing
to test the individual functional component of our system before testing the whole system once.

4.2.2. Integration testing:

Is the phase in software testing in which individual software modules are combined and tested as a
group Integration testing is conducted to evaluate the compliance of a system or component with
specified functional requirements. It occurs after unit testing and before system testing. Integration
testing takes as its input modules that have been unit tested, groups them in larger aggregates,
applies tests defined in an integration test plan to those aggregates, and delivers as its output the
integrated system ready for system testing.

4.2.3. System testing

System testing is also intended to demonstrate whether a system meets its

objectives. For verifying as the whole system is functioning in integrated manner
with respect to the goal of our system.

74
 4.3 Installation Process
Firstly install the software adobe Notepad++, Sublime and XAMPP server, after that follow the
steps:

Step 1- put the developed system folder on C:\Xampp on your computer.

Step 2- Active your installed Xampp server software (apache and MySQL module

Step 3- open the browser on your computer and write localhost (127.0.0.1) or (localhost/folder
name/index.php) on the place of URL or as a url.

Step 4- finally you can view and access the system.

NB: Before you are run the system you must have import the dataase which is arrived on your
folder to the Xampp server dataase (on phpmyadmin).

 check your folder which is available on the C:\Xampp

 Open any of the browser and write on the pace of url “localhost/folder name/filename. File
extention” then run it.

NB: REMEMBER THAT:

Before you are run the project on the Xampp server you must have import the database on the
MySQL server. To import the database on the Xampp server follow the steps here:

 Step1: activate the Xampp server apache and MySQL module.

 Step2: write “localhost/phpmyadmin” on the browser.
 Step3: then click on “localhost” on the displayed page and click on the “Databases” then go to
“create database” and create the database by the name of your dataase name then click on “create”
button. After that:
 Open the newly created database.
 Select import
 Then browse database by pushing the “choose file” button then say “Go” at the bottom of the page.
 Finally it is successful importing of database.

Finally installation can be successful when you are follow the steps appropriately.

Then you can run the project

75
 CHAPTER FIVE
Conclusion and Recommendation
5.1 Conclusion
Until now we have been doing the documentation of the web based bidding management system and
mainly the implementation of the web based bidding management system. In the documentation we have
seen the introductory sections about the overall system we have also done the detail analysis and the
design of the system that we developed and implemented in the final year project. We have developed
this web based bidding management system in Amharic language interface that support web application.
We also think that we have tried to show what the web based bidding management system looks like in
terms of documentation and implementation.

When the web based bidding management system becomes available on the network, i.e. when it is web
hosted and deployed on WWW. The web based bidding management system will be used to conduct an
online auction. Which is an initiative for those who are trying to expand technology in Ethiopia using
localization/customization method, i.e. if there is an existing technology in abroad, customizing it in a
way that suits the local interest and develop it. In this sense web based bidding management system
application will be a step towards bridging the digital divide.

5.2 Recommendations
According to scope of our project the team develops web based bidding management system. Because of
the time constraint we cannot do beyond to our scopes, but in the future the team believes that this
system can be fully operational by having enough time and full information. Next, the team would
recommend that further work should be done on the system in order to make the system fully functional
like official website and will developed android application.

76
 References

[1] A. Gallia, "UML Tutorial: How to Model any Process," 26 October 2018. [Online]. Available:
https://www.process.st/uml-tutorial/. [Accessed 19 may 2021].

[2] ".Open Tendering – The Procurement ClassRoom.," [Online]. Available: Open Tendering – The
Procurement ClassRoom.. [Accessed 13 April 2022].

[3] . Kenneth E.Kedall. Juile E Kedall. System Analysis and Design 8th edition. Prentice hall. [Accessed
21 Appril 2022]..

[4] L. A. Maciaszek, "https://www.cs.le.ac.uk/people/rh122/papers/2005/EFHT05PAIS.pdf.," 19

04 2001. [Online]. Available:
https://www.cs.le.ac.uk/people/rh122/papers/2005/EFHT05PAIS.pdf.. [Accessed 25 April
2022].

[5] https://www.g2.com/articles/types-of-auctions, "https://www.g2.com/articles/types-ofauctions,"

[Online]. Available: https://www.g2.com/articles/types-of-auctions. [Accessed 24 4 2022].

[6] "https://tzadmission.net/university-of-gondar-atse-tewodros-campus/," [Online]. Available:

https://tzadmission.net/university-of-gondar-atse-tewodros-campus/. [Accessed 20 04 2022].

77
APPENDIXS

Symbol Description

Actor

Use Case, Attribute

Message line extend from the lifeline,

Entity Attribute relationship

Starting point of activity/state diagram

Entity

Ending point of activity/state diagram

Dependency line

Return message extend from the

lifeline of one object

Decision

Note

Activity

Boundary Object

Control Object

78
 Entity Object

DB Database

SD Sequence Diagram

UC Use Case

UI User Interface

UML Unified Modeling Language

79
80
81