ASSOSA UNIVERSITY

COLLEGE OF COMPUTING AND

INFORMATICS DEPARTMENT OF
COMPUTER SCIENCE

A PROJECT PROPOSAL FOR

BROCKER MANAGEMENT SYSTEM

A Project Proposal Submitted to the Department of Computer

Science of ASSOSA University in Partial Fulfillment of
Requirements for the Degree of Bachelor of Science in
Computer Science
 Prepared By:

OSMAN MOHAMMED, TALILA ROBA, MISGANA DAME, EBISA OBSA, TESHALE FEKADU,
SELEHADIN ALI

Advisors’ Name:

Main Advisor: SILESHI B.

Co-Advisor: FERDIOS Y. 03/03/2017

 APPROVAL SHEET
This is certified that the project entitled on Brocker Management
System of the developed and submitted by
1. OSMAN MOHAMMED
2. TALILA ROBA
3. MISGANA DAME
4. EBISA OBSA
5. TESHALE FEKADU
6. SELEHADIN ALI

A Project Proposal Submitted to the Department of

Computer Science of ASSOSA University in Partial
Fulfillment of Requirements for the Degree of Bachelor
of Science in Computer Science

Advisors’ Name Signature Date

1. SILESHI B.

2. FERDIOS Y.

APPROVED BY

Examining Board Signature Date

1.

2.

Page 2 of 30
3.

Page 3 of 30
 A Project Proposal
for the Brocker Management

Table of Contents

Table of Contents
APPROVAL SHEET------------------------------------------------------------------------------------------------------------2

1 Introduction--------------------------------------------------------------------------------------------------------6

Document Description: -----------------------------------------------------------------------------------------7

2. Statement of the Problem---------------------------------------------------------------------------------------------8

3. Alternative Solutions and Proposed Solution---------------------------------------------------------------------9

3.1 Alternative Solutions:--------------------------------------------------------------------------------------9

3.2 Proposed System Description:---------------------------------------------------------------------------9

-----------------------------------------------------------------------------------------------------------------------10

4.Objectives of the Project:---------------------------------------------------------------------------------------------10

4.2 Specific Objectives-----------------------------------------------------------------------------------------10

5. Project Summary------------------------------------------------------------------------------------------------------11

5.1 Motivation---------------------------------------------------------------------------------------------11

5.2 Project Deliverables---------------------------------------------------------------------------------------11

5.3 Methodology------------------------------------------------------------------------------------------------12

5.4 Scope of the Project---------------------------------------------------------------------------------------13

6.Expected Benefits and Beneficiaries-------------------------------------------------------------------------------15

7.Project Schedule and Preliminary Budget----------------------------------------------------------------------16

------------------------------------------------------------------------------------------------------------16

7.1 Project Schedule--------------------------------------------------------------------------------------------16

8.Staffing Requirements-------------------------------------------------------------------------------------------------20

9.Risk Assessment---------------------------------------------------------------------------------------------------------22

10.Feasibility Study--------------------------------------------------------------------------------------------------------23

Page of
 A Project Proposal
for the Brocker Management
11. Conclusion---------------------------------------------------------------------------------------------------25

References--------------------------------------------------------------------------------------------------------------------25

List of Tables
Table 1Expected Benefits and Beneficiaries-----------------------------------------------------------------------15

Table 2 Grant Chat---------------------------------------------------------------------------------------------------------------16

Table 3 Preliminary Project Budget------------------------------------------------------------------------------------------17

Table 4 Core Project Team Roster--------------------------------------------------------------------------------------------20

Table 5 Supporting Subject Matter Experts--------------------------------------------------------------------------------22

Table 6 Risk Assessment--------------------------------------------------------------------------------------------------------23

Page of
 A Project Proposal
for the Brocker Management System

1 Introduction

Project Name: Rocker Management System

Project Start Date:25/02/2017 Project End Date:02/03/2017

Background – Android application is a smart phone application that works on cell

phones that uses an android operating system. In our county context, mobile phone users
are increasing rapidly from year to year and even day to day, but the mobile phone
applications are in their developing stages, so it is hard to find this application in the hands
of an ordinary user. Because of their mobile platforms difference and internet applicability
in our country most of mobile applications cannot reach or serve their purpose. Considering
this point and other fields that need focus on development of Mobile application we have
planned to develop this application that gives many significant services to its users, it
embedded three applications within it that allows it to give 3 different services to its

users, the services are: -

 House sale and rent service.

 Vehicle sale and rent service.

 Guards and servant online apply.

proposed System Description- Historically, many brokerage firms relied on

manual processes and disparate systems to manage their operations. This approach often
resulted in inefficiencies, increased risk of errors, difficulties in data retrieval, and challenges
in maintaining regulatory compliance. As technology advanced, the need for integrated
solutions became evident.

A Broker Management System emerged as a comprehensive software solution

designed specifically to address the unique needs of brokerage firms. By centralizing

Page 6 of 30
 A Project Proposal
for the Brocker Management System
information and automating various tasks, a BMS enables brokers to focus on what
matters most: serving their clients effectively and growing their businesses.

▎Key Drivers for BMS Adoption.

1. Efficiency: Automation of routine tasks reduces time spent on administrative

duties.

2. Data Centralization: A single platform for all client and policy information
enhances accessibility.

3. Regulatory Compliance: Built-in features help ensure adherence to industry

regulations

4. Enhanced Client Service: Improved tracking and management of client

interactions lead to better service delivery.

5. Scalability: Systems can grow with the firm, accommodating increasing

volumes of data and transactions.

Document Description: -
This proposal outlines the development of a Broker Management System (BMS) designed
to automate broker and transaction management, improving efficiency, reducing costs, and
enhancing customer satisfaction.

Key Sections:

 Existing System Description: Highlights inefficiencies of the current manual system.

 Proposed System Description: Introduces the BMS, detailing its benefits like
automation, scalability, and compliance.

 Objectives: Defines the general and specific goals of the project.

 Methodology: Describes the data gathering process, development approach (Agile),

and testing methods.

Page 7 of 30
 A Project Proposal
for the Brocker Management System
 Feasibility Study: Assesses the system’s economic, technical, operational, and
political viability.

 Risk Assessment: Identifies potential risks and mitigation strategies.

 Project Schedule & Budget: Provides an estimated timeline and budget.

 Staffing Requirements: Lists the core team and their roles.

 Conclusion: Summarizes the project’s feasibility and recommends proceeding with

development.

2. Statement of the Problem

Existing System Description

Traditionally, to
Existing System Description: -

access their need,

customer needs to
directly interact with
the broker or search
by
thems e lve s . Further,
customer needs to

Page 8 of 30
 A Project Proposal
for the Brocker Management System

have a direct contact

with the
their need of interest
Traditionally, to access their need, customer needs to directly interact
with the broker or Most of the systems we are going to develop are not
in work in the current system i.e. no system is developed for it so we
can’t find this service in mobile frames or web too. So, users are using
the

following methods to use the services we are going to build:

1. To get the service of House and Vehicle either for rent/sale

 Open a web browser on his device. i.e. need to have a working

installation of web browser.
 Browse the site i.e. Betoch.net for house and Mekina.net for car
service.
 The site doesn’t care about what is posted i.e. no persistence
check of the information posted is carried out by the system.
 To access the service, payment will take place through online
means.

Apart from this all, the services are posted by the user themselves.
The user can post everything he went which may be for fake, and
even if real he may include additional information that his service
doesn’t have. Through the current system there is no way to check for
this information. Thus, this may result in the user being bored with
system.

Page 9 of 30
 A Project Proposal
for the Brocker Management System

3. Alternative Solutions and Proposed Solution

3.1 Alternative Solutions:

The problems we explained above makes the existing system hard to

use for users because the services we are going to be built cannot be
found in one place, users must search different places to use the
services.

The best alternative solution to solve the problems described

above is to change the system by a new system that the user can
get these four services in one place in their mobile phone without
going and searching different places and also making the services
available for free.

3.2 Proposed System Description:

Digital broker is a server based mobile application. This application
contains server side containing the database of the services, customer,
and broker; and a client side containing GUI (graphical user interface).
And our system will also have detailed information about the services
(house, vehicle, guards, and house servants). This system enables
customer to search and view details of their need posted by the broker
and will generate and forward announcement and the need notifications
for the owner. It wills also shortlist the currently available needs. This
provides customers with a very interactive experience with the
application. Customers are given the facility to register themselves.
Upon registering, the customer gets to have a profile of his own and
provide feedback. An additional feature that we have included in the
customer’s application is that two or more customers can place order
from remote locations. This application helps seekers to view and search

Page 10 of 30
 A Project Proposal
for the Brocker Management System
for their need by accessing it through mobile without the need for
moving physically from broker to broker, installation of web browser and
remembering the domain name of the website.

4.Objectives of the Project:

The main objective of this project is to develop a Broker Management System (BMS) that
improves efficiency, reduces operational costs, and enhances customer service by
streamlining broker registration, client management, and transaction processes.

4.1 General Objective

The general objective of this project is to design and implement a digital

brokering system for Addis ASSOSA CITY

4.2 Specific Objectives

The specific objective of this project includes: -

 Creating a system that can guide customer by providing some

detail information of services including their location.
 Perform requirement analysis.
 Find a solution to the existing problem.
 Design the architecture for the proposed system.
 Develop user friendly and interactive system.
 To develop easy way of registering form for user, house, and
vehicle information.
 To transform the manual process of renting and selling of vehicle
and house in Addis ASSOSA city to a mobile system.
 Design persistent database.
 Implementing mobile application and acquiring a new knowledge.
 Test the developed system.

Page 11 of 30
 A Project Proposal
for the Brocker Management System
 Deploy the system.
 Lay concrete on a way to proposal in android mobile applications in
ASU (ASSOSA University) so that other students can have
foundation on which they can add more advanced.

5. Project Summary
5.1 Motivation
The motivation to develop the Broker Management System (BMS) arises from several key
factors:

1. Technological Perspective: Existing manual processes are outdated and prone to

errors. Automation and integration with modern technology will significantly
improve efficiency, accuracy, and scalability.
2. User Perspective: Brokers, clients, and administrators face frustration with
fragmented systems and slow, manual processes. A unified, automated system will
improve user experience, reduce workload, and increase satisfaction.
3. Existing System Challenges: The current system is inefficient, error-prone, and lacks
real-time data access. This results in delays, operational inefficiencies, and high
costs, which a new automated system will address.
4. Business Growth: As the organization grows, the existing system will struggle to
scale. The proposed system will provide the flexibility and scalability to support
future expansion.

These factors create a clear need for the proposed system to improve operational
efficiency, reduce errors, and support business growth.

5.2 Project Deliverables

The Project Deliverables for the Broker Management System (BMS) include the following:

Page 12 of 30
 A Project Proposal
for the Brocker Management System
• Project Proposal: A detailed document outlining the project scope, objectives,
methodology, and timeline.

• Software Requirements Specification (SRS): A comprehensive document describing

functional and non-functional requirements of the BMS.

• System Design Document (SDD): A blueprint outlining the system architecture,

database design, and technical specifications.

• Software Product: The fully developed and tested Broker Management System ready
for deployment.

• User Manual: A guide for end-users that details how to use the system for various
tasks (broker registration, transaction management, reporting, etc.).

• Programmer Manual: A document to assist developers and system maintainers in

understanding the system’s structure for future updates or modifications.

• Training Program: A series of training sessions for end-users to familiarize them with
the system’s features and operations.

Each deliverable is measurable, specific, and has a set due date, ensuring clear milestones
for project completion.

5.3 Methodology

5.3.1 Data Gathering Methods

 Methods: Surveys, interviews, and document analysis were used to gather data from
stakeholders (brokers, clients, and system administrators).

 Findings: The need for a centralized, automated system was identified due to the inefficiencies,
manual errors, and delays caused by the current system.

5.3.2 Development Methodology

 Agile Development: This methodology will be used for analysis, design, implementation, and
testing. It allows for iterative development, constant feedback, and quick adjustments.

 Process:

Page 13 of 30
 A Project Proposal
for the Brocker Management System
o Analysis: Identify detailed system requirements through stakeholder feedback.

o Design: Develop system architecture and database models.

o Implementation: Build system features in stages, with regular testing and feedback.

o Testing: Continuous testing during development phases to ensure the system meets all
functional requirements.

5.3.3 Development Approach

 Approach: Agile (Scrum) model is selected. It ensures flexibility, continuous improvement, and
the ability to adapt to changes in requirements or user needs during development.

5.3.4 Testing Metrics

 Methods:

o Unit Testing: To test individual components for correctness.

o Integration Testing: To ensure different modules work together.

o User Acceptance Testing (UAT): To verify that the system meets business needs.

o Performance Testing: To measure the system’s speed and responsiveness under load.

5.3.5 Development Tools

 Hardware Requirements:

o CPU: 2.5 GHz

o RAM: 12 GB minimum

o Lenovo Size: 1TB

 Software Requirements:

o Operating System: Windows

o Database: MySQL

o Programming Languages: Java, Android Studio

o IDE: Visual Studio Code

Page 14 of 30
 A Project Proposal
for the Brocker Management System
This methodology ensures a flexible, responsive approach, and the tools meet the system’s
requirements for smooth development and deployment.

4o mini

5.4 Scope of the Project

The system focusses on mobile based brokering system which will cover
only in Addis Ababa city and will perform the following activities:

Registration of user: the proposed system will register full

information of the user.
Registration of services: -The proposed system will register all
service information.
 Registration of House.
 Registration of Vehicle.
 Registration of guards and house servant.
Notification: -notifying the broker and the owner when the need
request is sent by the service seeker. Update Service
information: It updates the service information when needed.
Search for services: To search for the service that the customers
need

Page 15 of 30
 A Project Proposal
for the Brocker Management System

6.Expected Benefits and Beneficiaries

Here put the significance of the project as follows.

Table 1Expected Benefits and Beneficiaries

How the Project Benefits:

Project Benefits Brokers Administrators/ Clients IT Team

Managers

1. Improved Efficiency Faster transaction Easier management of Timely updates on Reduced

processing and brokers and client data. transactions and system
commission tracking. commissions. downtime and
easier
maintenance.

2. Better Data Easy access to client Centralized data for Better communication Simplified data
Management data and transaction better decision-making. with brokers. backups and
history. restoration.

3. Accurate Transparent and Streamlined commission Clear visibility of Less effort in

Commission Tracking automated commission management and commissions earned. managing
calculations. reports. commission-
related errors.

4. Enhanced Reporting Quick access to Comprehensive insights Improved transparency Fewer system
& Analytics performance reports into team performance. in broker performance. bugs and
and insights. enhanced
debugging
process.

5. Increased Security Secure access to Controlled access to Secure handling of Reduced

sensitive data (client, sensitive data based on client data and security
transaction info). roles. interactions. vulnerabilities
and easier
system audits.

Page 16 of 30
 A Project Proposal
for the Brocker Management System

7.Project Schedule and Preliminary Budget

7.1 Project Schedule

Table 2 Grant Chat

Time
02/03/2017

09/04/2017

07/05/2017

22/06/2017

Activities 12/07/2017

Proposal

Requirement Analysis

Design

Page 17 of 30
 A Project Proposal
for the Brocker Management System
Implementation

Testing

Project
Defense/Demonstratio
n

7.2 Preliminary Project Budget

Estimated project related costs for various spending categories.

Table 3 Preliminary Project Budget

A. INFRASTRUCTURE

Page 18 of 30
 A Project Proposal
for the Brocker Management System
Description Quantity Per Unit Total Cost

Development Machines 2 - -

Testing Servers (web-based) 1 - -

Network & Storage (Development/Testing) 1 - -

Total Infrastructure

B. SOFTWARE AND OPERATING SYSTEM LICENCES

Description Quantity Per Unit Total Cost

Integrated Development Environment (IDE) 3 - -

Database Management System (DBMS - 1 - -

proprietary)

Testing Tools & Software 1 - -

Total Software and Operating System

Licenses

C. CONSULTING

Description Quantity Per Unit Total Cost

External Consulting for System Architecture & 1 - -

Security

External Integration Services (for payment gateway) 1 - -

Total Consulting

D. TRAINING

Description Quantity Per Unit Total Cost

End-User Training (for brokers/admins) 1 session - -

Training Materials and Documentation 1 package - -

Total Training

E. TEMPORARY STAFF

Description Quantity Per Unit Total Cost

Page 19 of 30
 A Project Proposal
for the Brocker Management System

UI/UX Designer 1designer - -

QA Testers 2 testers - -

Total Temporary Staff

G. OTHER PROJECT COSTS

Description Quantity Per Unit Total Cost

Project Management Software 1 - -

Miscellaneous Costs (meetings, documentation, 1 - -

office supplies)

Total Other Project Costs -

Total Project Estimated Cost Less -

Contingency

Contingency (25%) -

TOTAL PROJECT ESTIMATED COST INCLUDING CONTINGENCY -

Page 20 of 30
 A Project Proposal
for the Brocker Management System

8.Staffing Requirements

The staffing requirements for the Broker Management System (BMS) project are outlined
below, specifying the core project team members as well as supporting subject matter
experts (SMEs) who will contribute their expertise at various stages of the project. An
organizational chart and detailed role descriptions will provide clarity on the staffing
structure and relationships.

Core Project Team Roster

The core project team is responsible for the development, design, implementation, testing,
and deployment of the system. This team will work on the project full-time or near full-
time.

Table 4 Core Project Team Roster

Name / Name /
Position of Position of
First Alternate
Role Qty Required Skills Choice(s) Choice(s)

1. Project Manager 1 Project management, OSMAN TALILA ROBA

(PM) leadership, risk MOHAMMED
assessment,
communication skills,
experience with software
development projects.

2. Lead Developer 1 Full-stack development OSMAN EBISA OBSA

(HTML, CSS, JavaScript,

Page 21 of 30
 A Project Proposal
for the Brocker Management System
Python, Java), database MOHAMMED
design, API development,
agile development
experience.

3. Backend Developer 1 Knowledge of server-side TALILA ROBA EBISA OBSA

technologies (Java,
Node.js, Python),
experience with
database management
(SQL, NoSQL), API
integration.

4. Frontend 1 Frontend technologies EBISA OBSA MISGANA DAME

Developer (React.js, Angular, HTML,
CSS, JavaScript), UI/UX
experience, responsive
design.

5. UI/UX Designer 1 UI/UX design, MISGANA DAME TESHALE FEKADU

wireframing, user
research, Adobe Suite,
Figma, prototyping.

6. System Architect 1 Software architecture, TESHALE FEKADU SELEHADIN ALI

system design, cloud
infrastructure, integration
design.

7. Database 1 Database design, SELEHADIN ALI OSMAN MOHAMMED

Administrator (DBA) optimization, backup
strategies, query
performance tuning.

8. Business Analyst 1 Requirements gathering, EBISA OBSA OSMAN MOHAMMED

documentation, stakeholder
communication, process
analysis, business process
modeling.

Page 22 of 30
 A Project Proposal
for the Brocker Management System
Supporting Subject Matter Experts
The supporting subject matter experts (SMEs) will not be involved in the day-to-day
development of the system but will provide specialized expertise when needed at specific
stages of the project. Their time allocation is more flexible but crucial to ensure quality and
accuracy.

Table 5 Supporting Subject Matter Experts

Role Knowledge Name/position of Name/Position of Time Allocated
Alternative Choice To Project
First Choice

9.Risk Assessment
Risk assessment is a critical part of project planning to ensure potential problems are
identified early and managed effectively. Below are the key risks that could negatively
impact the Broker Management System (BMS) project, along with strategies for preventing
them and contingency actions to take if they do occur.

Table 6 Risk Assessment

Potential Problem Preventive Actions Contingency Actions
1. Delays in Project Timeline - Establish clear milestones - Reevaluate the project
and deadlines. schedule and reallocate
resources if necessary.

2. Budget Overruns - Delay non-essential

Assign a dedicated financial manager to oversee and control costs.
purchases or activities to

Page 23 of 30
 A Project Proposal
for the Brocker Management System
reduce costs in the short
term.

3. Technical Complexity or - Conduct thorough feasibility - Bring in additional technical

Integration Issues and technical analysis in the experts or consultants for
early stages of design. guidance.

4. Security Vulnerabilities or - Educate the team on secure - Immediately notify

Data Breaches coding practices and integrate stakeholders of the breach
security testing. and provide them with a
mitigation plan.

5. Lack of User - Involve stakeholders and - Conduct additional user

Adoption/Acceptance end-users early in the design training or offer support
phase to align the system with services.
their needs.

10.Feasibility Study

A feasibility study decides whether the proposed system is worthwhile

in different dimensions. It measures how much the proposed system is
beneficial or practical at development of the system. The feasibility
factors of our project are:

 Economic feasibility
 Operational feasibility
 Technical feasibility
 Time feasibility
10.1 Economic feasibility

Page 24 of 30
 A Project Proposal
for the Brocker Management System
Economic feasibility attempts to weigh the costs of developing and
implementing a new system, against the benefits that would
accrue from having the new system in place. This feasibility study
outlines the economic justification for the new system. It gives the
actual comparison of costs and benefits are much more meaningful
in this case. Since this type of Application’s are new in our country
in that it supports a lot of services, the people acceptance toward
this system will be high and also there will be very less
computation in the market due to this reasons and other causes
the project. benefits will outweigh the expected cost. But Since the
Application is free for users the agencies only get benefit (income)
from advertisement of those services that are included in the
application.

10.2 Technical feasibility

We believe that building a working system with acceptable
characteristics, response time and other performance parameter
will involve through technical knowledge and technology
availability.
10.3 Operational feasibility
Measure how much the proposed system solves the existing
system problems. This project is surely operationally feasible
because the proposed system (the project) is a good solution
maker of the problem and create a good environment towards the
user of our application by providing easy, user interactive,
everywhere, and anytime accessible.
10.4 Time feasibility
Time feasibility determines whether the proposed system will be
completed on the given schedule or not. Whatever the scarcity of
time given for the project by the internal motivation and potential
of the team members of the project, we expect the project will be

Page 25 of 30
 A Project Proposal
for the Brocker Management System
completed on time that is described under the project work plan
below.

11. Conclusion
In conclusion, the development and implementation of the Broker Management System
(BMS) represents a significant opportunity for the organization to streamline and enhance
its operational capabilities. Based on the feasibility study, which covers economic, technical,
operational, and political considerations, the proposed system is deemed feasible across all
these dimensions. The Cost-Benefit Analysis (CBA) indicates that the anticipated benefits—
such as increased efficiency, cost savings, and improved revenue—outweigh the costs of
development and implementation. Moreover, the system's technical requirements can be
met with the current resources available, and it will be compatible with existing operational
processes without significant disruptions.

Key Expectations and Outcomes:

 Improved Efficiency: The BMS will automate manual processes, thus reducing administrative
overhead and operational inefficiencies.

 Enhanced Customer Satisfaction: With faster processing times and better management of
broker relationships, customer satisfaction is expected to improve, leading to higher client
retention rates.

 Scalability and Flexibility: The system will be built with flexibility in mind, allowing it to adapt to
future changes and requirements as the business grows.

 Cost-Effectiveness: By streamlining processes and reducing operational costs, the system is

expected to provide a strong return on investment within the first few years of deployment.

 Regulatory Compliance: The system will ensure that the organization complies with relevant
industry standards and legal requirements, thus minimizing the risk of non-compliance.

References

Page 26 of 30
 A Project Proposal
for the Brocker Management System
 Scott w, Amber, the object primer, second edition, Cambridge
University press (c), 2001.
 Scott w, Amber, the object primer, third edition, Cambridge
University press (c), 2004.
 Bembridge and Allen H. Dutoit, object-oriented software
engineering, third edition,2009.
 Genereux and McLeod, (1995) as cited in Weimer, 2002.
 Gary Shelly, Harry J. Rosenblatt, “Systems Analysis and Design”,
Cengage Learning, 2009.
 Preeti Gupta,“System Analysis and Design”, Firewall Media,
2008.
 Charles S. Wasson ,“System Analysis, Design, and Development:
Concepts, Principles, and Practices”, John Wiley & Sons, 2006.
 Charles S Wasson, “System Analysis, Design, and Development:
Concepts, Principles, and Practices”, Wiley-Intercedence.
 Elias M. Awed ,“Systems Analysis and Design”, Richard D. Irwin,
1985 2nd edition.
 https//: www.stackoverflow.com.
 https//: www.youtube.com.
 https//: www.codegroup.com.
 https//: www.programmerguru.com

Page 27 of 30