WOLLEGA UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY
POST GRADUATE IN COMPUTER SCIENCE
PROJECT TITLE: E-PROCUREMENT
MANAGEMENT SYSTEM FOR EEU(Ethiopian
electric utility)
SUBMITTED BY:BELAY BEYENA
ID:WU1400187
SUBMITTED TO :MR.BODENA
Overview of the project
One country government has a number of Federal and non-federal organizations,
this offices purchase a number of goods and services from different supplier’s
throughout their budget year through a process called Procurement. And this
process is an essential part in a way to support organizations achieves their goal.
EEU is the one of the federal organization that has its own procurement
management system based on defined set of rules and instruction that has to be
followed written in federal negarit gazeta even if most of the process are processed
manually. So this going to develop e-procurement management system for eeu.
Let see requirement proposed for the system
Requirement proposed for the system going to developed.
User requirement
User requirement are statement ,in natural language plus diagram ,of what service
the system is expected to provide to the system user and constraints under which it
must operate. with this definition user requirement of the system is as it described
below.
The system will be able to accept plan for procurement and request from the staff,
approve the plan/ request, suppliers will be able to offer their price for a bid on the
system and the system will let them know when why have won a bid.
System requirement
System requirement are more detailed description of the software system
function ,services and operational constraints.
The system shall have easy to use user interface.
The system shall authenticate and authorize users.
The system shall provide response within shorter time – maximum of 3
minutes’
The system shall list name of procurement for bid and so on.
Functional requirement
Most of the tangible and business processes will be included in the main functional
requirements; the following functional requirements are essential tasks that the
system should be able to accomplish
Employee and offices of the institution should be able to plan their
procurement plan on the system.
Head of the department should be able to approve or reject the plan
on the system.
Planed purchases should be able to request on the system.
Head of the department should be able to approve or reject based on
the office current demand .
The procurement directorate director should be able to accept
procurement requests and assign them to available experts; and
reject the request with a reason.
The procurement experts should be able to categorize bid and start
them process them until they are out for bid and winner for the bid is
identified.
Suppliers should be able to see what bid they can participate on,
Suppliers should be able to give their price for a bid they are
interested in.
The system should handle deadline of the bid.
When there is a winner for a specific bid the winner supplier as well
as the suppliers that didn't win should be notified on the system.
Through this processes the employee and the department that has
asked for procurement should be notified on every progress.
Non-functional Requirements
For an efficient, correct, and robust operation of the system, some additional non-
functional requirements emerged as necessary. These requirements are not directly
related to functionality.
The system shall have easy to use user interface.
The system shall authenticate and authorize users.
The system shall provide response within shorter time – maximum of 3
minutes.
The system shall allow users from wrongdoing in entering inputs.
The system is reliable in providing accurate information to users.
The system shall be designed using standardized software development
procedure.
