Contents

Acknowledgement ............................................................................................ iv
Chapter 1 ........................................................................................................... 1
1. Introduction ................................................................................................... 1
1.1. Background of the organization ........................................................... 2
1.2. Statement of the problem ...................................................................... 3
1.3. Objectives of the project ............................................................................ 5
1.3.1. General objectives ............................................................................... 5
1.3.2. Specific objectives ............................................................................... 5
1.4. Feasibility study.......................................................................................... 5
1.4.1. Technical feasibility ............................................................................ 5
1.4.2. Economic feasibility ............................................................................ 5
1.4.3. Legal feasibility ................................................................................... 5
1.4.4. Operational feasibility ........................................................................ 6
1.5. Significance of the project ......................................................................... 6
1.5.1. Summary of the significance of the project: ..................................... 7
1.6. Beneficiaries of the project ........................................................................ 8
1.7. Methodology ............................................................................................... 9
1.7.1. System Design and Analysis Tools..................................................... 9
1.8. Scope of the project .................................................................................. 10
1.8.1 Limitations of the project .................................................................. 10
1.9. Risk, assumption and constraints ........................................................... 10
1.9.1. Risk ..................................................................................................... 10
1.9.2. Risk assumption ................................................................................ 11
1.9.3. Constraints ......................................................................................... 11
1.10. Organization of the project ................................................................... 11
1.11. Budget allocation .................................................................................... 12
1.12. Work plan ............................................................................................... 13
Chapter 2 ......................................................................................................... 14
2. Business area analysis and requirement definition ................................. 14

i
2.1 Introduction ............................................................................................... 14
2.2 Business area analysis ............................................................................... 14
2.2.1 Detailed analysis ................................................................................. 14
2.2.2. Current system .................................................................................. 15
2.2.3. Players of the existing system........................................................... 15
2.2.4. Proposed system ................................................................................ 16
2.3. Requirement Gathering ........................................................................... 16
2.3.1. Requirement Gathering Techniques ............................................... 17
2.5. Requirement definition ............................................................................ 17
2.5.1 Functional requirement ..................................................................... 17
2.5.1.1. Actor description ........................................................................ 18
2.4. Method of Communication ..................................................................... 19
2.4.1. Communication techniques .............................................................. 19
2.5.1.2 Essential Use case Description ................................................... 19
2.5.2. Nonfunctional Requirements ........................................................... 39
Chapter 3 ......................................................................................................... 41
3. System Modeling ......................................................................................... 41
3.1. Introduction .............................................................................................. 41
3.2.UI Identification ........................................................................................ 42
3.3. Business Rules Identification .................................................................. 43
3.4. Actor Identification .................................................................................. 44
3.5. Use Case Diagram .................................................................................... 45
3.6. Sequence Diagram.................................................................................... 46
3.7. Activity Diagram ...................................................................................... 52
3.8. Class Diagram .......................................................................................... 53
3.9. State Chart Diagram ................................................................................ 54
Chapter 4 ......................................................................................................... 55
4. System Design .......................................................................................... 55
4.2. Database Table Structure ........................................................................ 56
4.3. Database Normalization .......................................................................... 57

ii
4.4. Deployment Diagram ............................................................................... 58
4.5. High Fidelity Prototype ........................................................................... 59
Chapter 5 ......................................................................................................... 61
5. Conclusion and recommendation .............................................................. 61
5.1. Conclusion................................................................................................. 61
5.2. Recommendation ...................................................................................... 61
References ........................................................................................................ 62
Appendix .......................................................................................................... 63

iii
 Acknowledgement
First and foremost, we want to express our sincere gratitude to God Almighty for
making this project possible and for providing us with the strength, perseverance,
and expertise needed to complete it.

Without the assistance of our advisor, Mr. Addisu Anbessa, this project would
not have been accomplished. We are really grateful for his advice,
encouragement, and constructive criticism.

iv
 Chapter 1
1. Introduction
Agriculture eCommerce is revolutionizing the way that farmers,
agricultural businesses, and agricultural based industries buy and sell products
and services. From providing access to interactive global marketplaces to
streamlining order management tools, cataloguing supply chain data and
utilizing farm automation solutions to simplify routine tasks – this emerging
technology promises more visibility, speed, accuracy and control for all
stakeholders involved. Agriculture eCommerce also offers a powerful new set
of cloud-based analytics capabilities to gain meaningful insights into
agricultural behaviors and transactional history. With its ability to save time
and money while boosting workforce productivity, agriculture eCommerce
presents an exciting opportunity for anyone in the industry seeking increased
profitability.
In recent years, eCommerce agriculture has emerged as a promising
new tool for farmers and agricultural businesses. eCommerce agriculture refers
to the use of digital technologies to facilitate the buying and selling of
agricultural products and services. By using eCommerce platforms, farmers
and agricultural businesses can connect with buyers and sellers around the
world, and conduct transactions more efficiently and effectively than with
traditional methods.
The internet has enabled greater visibility into the global supply chain,
as buyers and sellers are much closer and more easily connected. Today, most
journeys in the purchase of products in these segments begin online through
search engines, social media recommendations, online reviews or digital
advertisements. The agricultural sector is one of the few remaining sectors
where e-commerce is yet to have a significant impact. There are several reasons
for this: the agri supply chain is often controlled by well-entrenched
intermediaries (middlemen); the logistical challenge of handling perishable
products is complex; and most farmers still prefer to buy raw materials and
fertilizers in-person going long distances rather than online, given the
inconsistent physical appearance.
However, this is changing rapidly as e-commerce solutions that aim
to overcome barriers around farmer productivity preferences and logistics drive
online currently. Agri e-commerce in developing regions is so far less
pronounced. This is primarily because the challenges to agri e-commerce
adoption are more acute in these regions. For example, there is little in the way
of agri-produce standardization (by quality, size, or age) and the logistical
challenges are more significant. In addition, farmers in these regions often live
in rural areas with low levels of critical infrastructure (roads, storage,
warehouses, transport, etc.), limited access to a full range of digital
1
technologies, and where powerful intermediaries are keen to maintain the
status quo.
There is growing potential for these platforms to disrupt the
agriculture supply value chain as investors build on the rising adoption of
mobile internet and digital payment solutions by end farmers to develop new
go-to-market models for agriculture produce. This could have a significant
impact on the agricultural sector in developing regions.
ECommerce agriculture has several advantages over traditional
agriculture. First, eCommerce platforms provide a more efficient and
convenient way to get more goods that supports farmers. Second, eCommerce
agriculture can help farmers and agricultural businesses to reach new markets
and tap into new revenue streams. Finally, eCommerce agriculture can help to
reduce costs and improve margins for farmers and agricultural businesses.

1.1. Background of the organization

Due to the tighter and easier connections between buyers and sellers,
the internet has made the global supply chain more visible. The majority of
client journeys for these product groups now start online via search engines,
social media suggestions, online reviews, or digital marketing.
As investors build on the rising adoption of mobile internet and
digital payment solutions by end users and farmers to develop new go-to-
market models for agricultural produce, there is an increasing potential for
these platforms to disrupt the agriculture supply value chain in various
Ethiopian regions.
By improving farmers' access to customers and establishing new
ties across steps in the value chain, online purchasing and selling of different
tools and necessary things for agricultural purposes can address significant
problems and inefficiencies in the agriculture supply chain. This is particularly
true in developing nations like Ethiopia, where online platforms can allow
farmers to avoid middlemen and buy various tools, chemicals, and fertilizers
directly from agribusinesses and other customer groups, increasing the supply
chain's efficiency and generating more equitable incomes.
Agriculture Electronic Commerce (Agri-ec) is a type of electronic
commerce that will assist farmers and other buyers in doing the proper business
transactions online. Additionally, this system will link buyers and sellers in a way that
ensures the value and visibility of important products to customers, while allowing
trading partners to communicate a variety of communiques and data.
We think this platform is worth the effort because of the points listed below:

2
✓ There is a vast growing interest in e-commerce and since our country Ethiopia’s
main income is agriculture and there is also a vast growing need of food and
different tools for agriculture this platform will narrow the gap.
✓ This days farmers with small farm does not get chance to sell to big market,
where as the farmers with big farm does, and our platform will also give equal
chance for both types of farmers in order to sell products and grow their farm.
✓ Today in Ethiopia’s economy prices of agriculture products like tef, onion etc. is
very high, and one of the reasons behind is the so called “the middle man”, so
our platform will eliminate this middle man from the process of buying and
selling products online, which will also eliminate the money paid for the middle
man, which will result lower prices of products.
✓ It will create connection directly between the farmers and the customers.
✓ There is also a problem of shortage of needed tools for farmers in order to grow
products, tools like fertilizers, pesticides etc, so this platform will also be able to
connect machinery and fertilizers sellers to farmers in need.

1.2. Statement of the problem

Agriculture eCommerce is a rapidly growing sector of eCommerce, yet
there remain numerous challenges that hinder its development. One problem
commonly faced by the agricultural eCommerce industry relates to the lack of
trust between buyers and sellers. Farmers are often unwilling to purchase
products online due to their concerns about quality, and not being intellectual
making it difficult for agricultural businesses to gain credibility and compete
with more traditional forms of distribution. Additionally, many farmers lack
access to reliable payment methods and service providers that can facilitate
efficient transactions when buying or selling products through an eCommerce
platform. Furthermore, existing frameworks related to buying/selling and
shipping mechanisms may need to be revised in order to ensure simplicity
compliance within the agricultural eCommerce sector globally. Finally, the
integration of new technology designed specifically for agriculture
eCommerce sites will be critical in driving agriculture business growth over
time.
This project addressed by agricultural eCommerce is the production of
safe, high-quality products while meeting both buyer and seller demands at an
acceptable price point. Additionally, factors such as the transportation of goods
in a timely manner, ensuring payment security when handling online
transactions, and providing support services to customers while protecting their
private data must also be taken into consideration.
Many Ethiopian small farmers are struggling to keep up with the
demands of the modern world. With the growth of the internet and eCommerce,
there is an increasing demand for raw materials, and fertilizers. However, the

3
lack of infrastructure and knowledge among small farmers makes it difficult
for them to take advantage of this growing market.
As a result, Ethiopian small farmers are being left behind in the
eCommerce agriculture revolution. They are not able to compete with the
larger, more established farms that are able to invest in the necessary
technology and resources. This can have a devastating effect on the local
economy as 80.0-85.0% of the Ethiopian population are farmers and the
farmers themselves are often struggling to get raw materials to survive and
thrive in their agriculture operations.
There is a need for a comprehensive solution to help farmers catch up
with the eCommerce agriculture trend. This solution should include
information and resources on how to take advantage of the latest technology,
how to set up and run an online store, and how to market and sell their products.
Without this type of support, these farmers will continue to be at a disadvantage
and may eventually be forced out of business.
The eCommerce agricultural industry is just starting and there are
several issues that need to be addressed in order for this industry to really
thrive.
1) Lack of trust and transparency – There is a lack of trust between buyers and
sellers when it comes to eCommerce agriculture. This is due to the lack of
transparency in the industry. There is no way for buyers to know if the products
they are buying are really what they are represented to be. This lack of trust
decreases the likelihood of people wanting to purchase products online.
2) Lack of standardization – There is a lack of standardization in the
eCommerce agricultural industry. This makes it difficult for buyers to know
what they are actually getting when they purchase a product. There is no
guarantee that the product will meet their expectations.
3) Lack of customer service – There is also a lack of customer service in the
eCommerce agricultural industry. This makes it difficult for buyers to get help
if they have any problems with their purchase.
4) Lack of safety and security – Safety and security play major roles but they’re
in nonexistence currently.
5) Non-technical - as farmers are non-technical and lack of latest smart devices
to use the current technology.
The problem that our project aims to solve is that there is currently no good
way for farmers to get access to agricultural raw materials directly to the
authorized sellers. There are many middlemen involved in the process, which
indirectly drives up the cost of food for consumers and limits the profit margins
for farmers.
4
 1.3. Objectives of the project
1.3.1. General objectives
• Analyzing, modeling, designing and developing an agricultural ecommerce
web app called AgriCom.

1.3.2. Specific objectives

• Enabling end users to post, delete, update and view products.

• Enabling end users to generate report about an error and transaction.

• Enabling the admins to manage the users.

• Enabling end users to order products and add to their cart.

• Enabling end users to sign up and login to the system successfully.

1.4. Feasibility study

1.4.1. Technical feasibility
We have the necessary hardware and software tools for this proposed
project, as well as the qualified experts, expertise, and experience that are
needed in the field. We have also completed projects of a similar nature in
previous courses.
1.4.2. Economic feasibility
Because it reduces the amount of money spent on middlemen(brokers),
our system is economically viable. Time is another expense that can be valued
in terms of dollars. The amount of time it takes to complete the tasks is reduced
tremendously by our technology.
1.4.3. Legal feasibility
Our system is technically practical because it complies with all
applicable business and e-commerce laws, thus it won't violate any
constitutional provisions. The system is an improvement over the existing one
in that it will reduce the difficulties with fraud and transparency in the market
taxes system.

5
1.4.4. Operational feasibility

• How effectively the proposed system handles the issues?

The suggested solution would employ an object-oriented approach to
handle the issues described, and it is adaptable, effective, and uses modularity
for simpler troubleshooting. which will make it simpler to find solutions for
any issue.
• Is the problem worth solving?
Yes, of course it’s worth it because in our country the market
connection between the supplier and the market is on the hands of some brokers
which results to a great price fluctuation and transparency between the supplier
and the market.

1.5. Significance of the project

The landscape of agricultural business is predicted to undergo a revolution
thanks to internet access and agent technology. E-commerce is already clearly
starting to have a significant impact on the agricultural sector. The process by
which individuals buy agricultural products is a major concern.
When purchasing agricultural products, consumers often have to travel great
distances, and the quality of the products is not always assured.
The necessity for Agriculture Electronic Commerce (Agric-EC), a type of
electronic commerce that will assist farmers and other buyers in doing the
proper business transactions online, is a lot.
Cost and market efficiency improvements: The potential economic benefits of
agriculture e-commerce may serve as an incentive for farmers to raise their on-farm
investments and productivity. Furthermore, farmers may be able to obtain higher-
quality inputs from internet sellers than they can in their local markets.
Through greater agricultural production efficiency, improved livelihoods, and value
chain development, e-agriculture has the potential to drive economic growth and raise
incomes among the rural poor.

Agricultural e-commerce transforms the way individuals buy and sell

agricultural products and services in the real world into transactions that take
place online. Agricultural e-commerce makes it harder to distinguish between
the real world and the internet because it is increasingly common for people,
places, and things to be present online. Eventually, IT Internet representations
will take the place of people, paper, and product transportation inside a farm.
The size of the farming facility is irrelevant because both small and large farms
have access to the same resources.

6
Furthermore, by enabling various business models, including multi-supplier,
e-sales, and various forms of auctions, agricultural e-commerce creates
favorable trade opportunities.
The sale of agricultural goods and the connection between farms and their
clients are both transformed by agricultural e-commerce. In other words, this
technology is a part of the bigger fields of agriculture and information
technology.
With the use of agricultural e-commerce strategies, smaller farms can now
access the same markets as bigger farms. Small farmers can thus immediately
access markets around the world. Small farms are capable of explosive growth
and can even take on larger ones. Compared to larger farms, they can more
easily offer individualized services to visitors. Agri-e-commerce solutions help
grow one's business by expanding their contacts with clients, vendors, and
other farmers.
Additionally, this system aims to link buyers and sellers in a way that ensures the
value and visibility of important products to customers, while allowing trading
partners to communicate a variety of communiques and data.

1.5.1. Summary of the significance of the project:

⚫ The necessity for Agriculture Electronic Commerce (Agric-EC), a type of
electronic commerce that will assist farmers and other buyers in doing the proper
business transactions online, is alot.
⚫ Cost and market efficiency improvements: The potential economic benefits of
agriculture e-commerce may serve as an incentive for farmers to raise their on-
farm investments and productivity.
⚫ Through greater agricultural production efficiency, improved livelihoods, and
value chain development, e-agriculture has the potential to drive economic
growth and raise incomes among the rural low incomers.
⚫ Agricultural e-commerce transforms the way individuals buy and sell agricultural
products and services in the real world into transactions that take place online.
⚫ The size of the farming facility is irrelevant because both small and large farms
have access to the same resources.
⚫ Furthermore, by enabling various business models, including multi-supplier, e-
sales, and various forms of auctions, agricultural e-commerce creates favorable
trade opportunities.
⚫ The sale of agricultural goods and the connection between farms and their clients
are both transformed by agricultural e-commerce.
⚫ With the use of agricultural e-commerce strategies, smaller farms can now access
the same markets as bigger farms.

7
 1.6. Beneficiaries of the project
A direct connection between buyer and seller, a streamlined agricultural value chain,
and a decrease in inefficiencies in the distribution of farm products are all benefits of
agricultural e-commerce. It offers farmers a brand-new, innovative way to sell their
produce to a variety of customers, including agricultural companies, retailers,
restaurants, and consumers, expanding farmers' access to new markets and increasing
value chain transparency. It enables farmers to cut out a number of middlemen,
increasing their income, cutting waste and carbon emissions, and maybe providing
customers with fresher produce.
Importantly, this new e-comerce platform may help transform the agricultural
industry by lowering or eliminating entry barriers and opening up opportunities for
new farmers. Bypassing intermediaries for new entrants increase the supply chain's
efficiency, gives farmers fairer incomes, and creates a transaction history.
Would make it easier for farmers and other purchasers to conduct legitimate business
transactions online without having to worry about finding the proper producer to
supply them with the right goods at inflated costs affected by middlemen. This makes
it easier to guarantee the sales of high-quality agricultural input and consumer goods.
When purchasing agricultural products, purchasers occasionally have to travel great
distances, and the quality of the products they receive cannot always be assured since
they might be working with unregistered agents and intermediaries. Additionally, it
is impossible to compare market prices because buyers lack the time and resources to
visit every agricultural farm. Instead, they must deal with the same unregistered
middlemen, who then raise the prices of key products for their own personal gain.
Therefore, this platform will deal with any worries about long distance travel, quality,
and intermediaries.
Benefits for sellers include:
✓ improved cash flow, as producers are reimbursed within a few days instead of a
matter of weeks or months.
✓ easier buyer access and management.
✓ the power associated with digital marketing and branding.
✓ and the reliability and insurance provided by a recognized fin-tech platform.
✓ Greater reach.
✓ Waste reduction.
Specific benefits to buyers include:
✓ lower prices and a transparent price discovery mechanism;
✓ reduced sourcing and logistics costs;
✓ increased product choice;

8
✓ a streamlined procurement processes.
✓ Another advantage is, greater agility in adjusting to unexpected issues such as
supply chain disruptions and logistical challenges.

1.7. Methodology
This project employed a descriptive and explanatory research design to assess
system practice. Because it offers insight into the present and tries to determine the
status of the phenomena under study, the descriptive research design technique was
chosen. It also responds to questions like what, where, and when. On the other hand,
an explanatory study design was employed to find out why something happens when
there is little information available. It can assist us in better understanding a topic,
figuring out how or why a specific phenomenon occurs, and making predictions about
the future. Therefore, it effectively responds to the "Why" query.

Data Collection
Both primary and secondary sources are used to collect the data for this project.
To gather primary data, questionnaires, observations, and interviews are used.
Through the analysis of written works, published books, videos, and websites,
secondary data is acquired.
Scientific research frequently uses observation to get data. Using observation,
we learned about the various agricultural tool shops' present systems, agricultural
product stores, other e-commerce sites, and how the purchasing and selling process
is carried out under the current system.
To discover more about the context of the participant's experiences, conduct
an interview. To obtain information about the current system in order to develop our
project, we conducted interviews. In order to better understand how products are
acquired and sold, we were able to speak with store managers of agricultural goods
during this interview.
For the shops and stores we interviewed, we prepared questionnaires that
focused on the buying and selling of agricultural products. The following list of
questions includes a few of them.

1.7.1. System Design and Analysis Tools

For system design and analysis we used tools like:-
✓ Adobe XD
✓ Instagram
✓ Google
✓ Windows operating system

9
 System Development tools
For system development we used tools like:
✓ Windows operating system
✓ Visual studio code
✓ Front end languages like HTML, CSS and JavaScript

✓ Php as a back-end language and MySQL as a database

1.8. Scope of the project

The Geographical scope of our project is limited to farmers in Addis Ababa and its
surrounding.
The system scope of the agri-com is to enable farmers in Addis Ababa and its
surrounding profit by posting (sharing) their agri products without the help of any
broker and communicate with the buyers directly, and also enable the buyers to pay
fair price for the agri products they consume. The farmers can also buy necessary
machinery and tools from this site.

1.8.1 Limitations of the project

• Shortage of internet infrastructure.

• Shortage of familiarity with technology.
• The system is fully dependent on internet.
• It is geographically limited to Addis Ababa and its surrounding.
• People’s acceptance of the system.

1.9. Risk, assumption and constraints

1.9.1. Risk
While working on our project we might encounter the following risks:
✓ Unstable or Unreliable internet connection.
✓ Unstable or Unreliable electricity.
✓ File corruption.
✓ Crashing of computers.

✓ Virus attack.

10
1.9.2. Risk assumption
We made the following assumption while creating this software. The
assumptions are as follows:
✓ We assume that there is a stable and reliable internet connection in Addis
Ababa and its surrounding.
✓ We assume that there is a stable and reliable electricity in Addis Ababa and
its surrounding.
✓ We assume that in this specific area (Addis Ababa and its surrounding)
people know how to use social medias since the social media effect on e-
commerce is high.
✓ We assume that we have the necessary tools for developing the system.
1.9.3. Constraints
✓ Natural disaster.
✓ Technological infrastructures.
✓ Lack of technological awareness.
✓ Seasonal price fluctuation.
✓ Conflict.

1.10. Organization of the project

Chapter 1:

✓ Introduction of Agri-com and ecommerce.

✓ Problem on the current system.
✓ Why AgriCom is better.
✓ The objective, significance and benefit of our project.
✓ Method used for data collection.
✓ Scope and limitation of the project.

Chapter 2:

✓ Business area analysis and requirement definition.

✓ Requirement gathering techniques.
✓ Method of communication.

11
Chapter 3:

✓ System use case

✓ UI identification.
✓ Business rule identification.
✓ Actor identification.
✓ Use case diagram.
✓ Use case description.
✓ Sequence diagram.
✓ Activity diagram.
✓ Class diagram.
✓ State chart diagram.
✓ User interface prototype.

Chapter 4:

✓ Database normalization.
✓ Database table structure.
✓ Deployment diagram.
✓ Interface design.
✓ High fidelity prototype.

Chapter 5:

✓ Conclusion.
✓ Recommendation.

1.11. Budget allocation

Our costs post-development is going to be included but not limited to
costs for database hosting server & API hosting server.

Reasons Budget

1 Transport (data collection) 1000 birr

2 Web & cloud hosting 500 -1000 birr per year

12
 1.12. Work plan
The Work plan for this project is as follows:
Week 1:
✓ Getting started: reading about agriculture, communicating with advisor.
Week 2:
✓ Preparing work plan, discussing it with group members, getting approval from
our advisor.
Week 3:
✓ Working on objective, significance and benefit of our project.
✓ Deciding on budget allocation.
✓ Work on feasibility of our study.
✓ Assessing risk and assumption.
✓ Deciding on the scope and limitation of our project.
✓ Deciding on methodology of data collection.
Week 4:
✓ Study the business area of our project.
✓ Gather requirements (functional and non-functional).
✓ Work on use case modeling.
✓ Defining the actors and use case description.
Week 5:
✓ Working on UI, business rules and actors’ identification.
✓ Work on use case description and diagram.
✓ Diagramming sequence and activity.
✓ Work on database normalization and database table structure.
✓ Deploying diagram and Interface design.
✓ Work on high fidelity prototype.
Week 6:
✓ Conclusion and Recommendation.

13
 Chapter 2
2. Business area analysis and requirement definition
2.1 Introduction
2.2 Business area analysis
Agriculture eCommerce is the business of selling agricultural products and
services online. This can include items such as seeds, fertilizers, livestock, and crop
production tools. It can also include services such as crop consultations, farm tours,
and online marketplaces.
Agri e-commerce businesses have an online platform, which provides market
linkages between buyers and sellers. Other than this, the Agri e-commerce service
does not perform any other operational functions. Agri e-commerce businesses at this
have staff working on farmer acquisition, as well as marketing and customer care. In
addition, it facilitates payments through its platforms and arranges logistics.
There is a lack of reliable data on the business of agriculture eCommerce in
Ethiopia, but it is likely that the sector is growing rapidly. The country has a
population of over 100 million people and is one of the world's most agriculturally
productive countries. There is a growing demand for agricultural products in Ethiopia,
and online retailers are likely to benefit from this. Let alone the agricultural sector in
Ethiopia is one of the most important sectors in the economy, contributing to over 30%
of the GDP. The sector is dominated by smallholder farming, which employees over
80% of the population.

2.2.1 Detailed analysis

The agricultural ecommerce web app is a web application that allows farmers and
agricultural businesses to sell their products online. The app features a user-friendly
interface, and allows farmers to list their products, track sales, and receive customer
feedback. The app also allows businesses to find new customers, and to purchase
products from farmers.

According to a report by the World Bank, agricultural e-commerce in Ethiopia is

growing rapidly. The report projects that the sector will grow from $5 million in
2016 to $27 million by 2021. This growth is attributable to increases in online sales
of agricultural products, as well as the growth of mobile commerce. One of the main
challenges facing agricultural e-commerce in Ethiopia is the lack of a secure online
payment system. This is due in part to the fact that many Ethiopians do not have
access to internet or mobile phones. As a result, they are not able to make online
purchases. In order to overcome this obstacle, the government is working to develop
a national e-payment system.

14
2.2.2. Current system
The current system of agriculture eCommerce in Ethiopia is characterized by
a low level of online penetration and limited online retail activity. The country has
only around 7% of the population online, compared to an average of around 50% in
other African countries. There is also a lack of reliable and affordable
telecommunications infrastructure, which hampers the ability of businesses to
conduct online transactions. This is likely to limit the growth of agricultural
eCommerce in Ethiopia in the short term.
The current infancy state is used rarely by consumers and the government of
Ethiopia is preparing a draft national law to govern e-Commerce. The current system
relies heavily on traditional markets, with limited access to technology, such as the
internet, and financial services. Farmers in Ethiopia are typically smallholders and
lack access to capital, and knowledge therefore are unable to take advantage of digital
markets. Additionally, there is a lack of secure checkout, escrow and delivery systems
to facilitate the sale of agricultural products.
Currently, agriculture eCommerce in Ethiopia is fragmented and inefficient.
There is a lack of standardization and interoperability among the different platforms,
which makes it difficult for farmers to sell their products. Additionally, the country's
infrastructure is not well suited to support eCommerce, making it difficult for farmers
to get their products to market.
The current lack of infrastructure leads to a lack of awareness and
understanding of the potential of e-commerce among potential users. While the
Government of Ethiopia is investing in building the necessary infrastructure, there is
a need to raise awareness and understanding in the country, especially among farmers.
The price we’ve found on the current player also has no difference from the
old brick and mortal shops even more expensive when additional costs are added like
logistics. However, given the country's strong agricultural sector and growing
population, there is potential for agricultural eCommerce to grow in the medium to
long term.

2.2.3. Players of the existing system

The one and only player in Addis Ababa is KeGeberew e-commerce site
presented by purpose black Ethiopia. This company is working directly with the
farmers to process farm products and sell the processed and raw products directly to
consumers through its e-commerce marketplace it retails with farmers throughout
Ethiopia. In addition to helping the farmer, the project also reduces the price of
products to consumers, thus, helping stabilize the market and creating a win-win
situation for all involved in the process.
The platform also provides a marketplace for consumers to purchase quality
goods directly from farmers and small businesses in Ethiopia. Consumers can also
find information about product availability, prices, and farmers and businesses that
have the products they are looking for.

15
 Kegeberew.com has created a platform that allows users to access markets
and products without leaving their homes. This eliminates the need for costly
travelling to markets as well as long wait times for products to arrive. In addition, the
platform is easy to use and secure.

2.2.4. Proposed system

The system is a B2C online eCommerce platform that would enable farmers
and consumers to buy or sell anything related to the agriculture and farming category.
The system aims to create an organic e-farming system based on three business value
models (value chain, value shop, and value network). It should involve features such
as the ability to create a digitally verified identity for farmers, the ability to manage
supplies and logistics, and the ability to accept payments through various digital
checkout options.
The system should also include an analytics system to enable farmers to gain
insights into their customers, products, and services. This would enable the system to
continuously improve and optimize the customer experience. The system should also
include a secure payment gateway or easy checkout to enable customers to make
payments safely and securely. Additionally provide provides analytics and insights
not only to farmers but also to us to help Agri eCommerce
space better understand our customers and their purchasing behaviors which leads us
to help make better decisions and optimize our operations.
The system would manage customer data, such as order history and
preferences, to provide personalized services and a better customer experience. To
ensure a secure and reliable system, the system should be built on a secure server
infrastructure with a strong data encryption system.
Finally, the system has a customer service module. This should include
features such as the ability to provide customer support and answer customer inquiries.
Additionally, the system should include features such as the ability to provide product
support. This would ensure that customers receive the best possible experience when
using the system. In conclusion, this system of agricultural e-commerce could have
far-reaching benefits for both farmers and consumers.

2.3. Requirement Gathering

Requirement gathering is the process of collecting and understanding the
needs and constraints of a research project. Its main goal is to determine the
prerequisites necessary for the successful completion of the research project. This
may include objectives or goals, the scope of the project, data sources and methods,
budget, timeline, stakeholders, and another requirement. The corporate world uses
requirement collecting the most, particularly in relation to information technology.

We employed three different forms of requirement gathering techniques that

would enable us to comprehend each vital component of the existing system.

16
2.3.1. Requirement Gathering Techniques
We attempted to apply the following technique for requirement collection
in our project:
i. Interview:- is one of the main methods of information collection where the
system analyst will speak with pertinent stakeholders or subject matter experts in
person.
ii. Observation:- is the active process of capturing information about an object ,
event or phenomenon , The act of observing involves paying attention to it and
gathering data about it, which can be used for further analysis or to form a
conclusion about the subject of the observation.
iii. Brainstorming:- is a creative problem-solving technique that involves
generating a large number of ideas in a short period of time. The goal of brain-
storming is to generate a wide range of ideas, without evaluating or criticizing
them during the initial idea generation stage.

2.5. Requirement definition

2.5.1 Functional requirement
1. Super Admin:-
✓ Can add / remove admins.
✓ Can view log records.
✓ Can view reports.
✓ Can update admins.
✓ Can view reported error messages.
✓ Can login / logout
2. Admin:-
✓ Can login/logout.
✓ Can add/remove users.
✓ Can view accounts.
✓ Can send registration form for confirmation.
✓ Can generate and send reports to super admin.
3. Transaction checker:-
✓ Can login/logout.
✓ Can check and confirm transaction.
✓ Can send confirmed transaction report to super admin and admin.
4. User:-
i. Seller:-
17
✓ Can sign up.
✓ Can login/logout.
✓ Can delete and update account.
✓ Can post products.
✓ Can update and delete post.
✓ Can send feedback.
✓ Can subscribe for a better service.
ii. Buyer:-
✓ Can sign up.
✓ Can login/logout.
✓ Can see post.
✓ Can delete and update account.
✓ Can message or notify seller about needed product.
✓ Can search for product.
✓ Can place order.
✓ Can send feedback.
✓ Can rate seller’s product.
2.5.1.1. Actor description
i. Super Admin:
✓ Is the one that manages admins and users. can do almost every possible activity
on the platform, has full control and access on the platform.
ii. Admin:
✓ Is the one located in different areas in order to help peoples who’s not familiar
with the technology, they have control and access but it is limited, don’t have full
access like the super admin. They are an IT personal.
iii. Transaction checker:
✓ Is the one who checks if a certain transaction is legit, they are also IT personals,
if any transaction is or is not legit, they will notify the admin and super admin. If
it is legit, they will confirm it and if not, they will deny the confirmation.
iv. Users:
✓ The users are divided into two, buyers and sellers. the buyers are the one who
places order, buy products, and rate the sellers, whereas the sellers are the one
who posts and sell the products, the one being rated.

18
 2.4. Method of Communication
Is a means by which information is exchanged individuals or groups. There are
seven different types of communication methods like Verbal communication, Non-
verbal, written, visual, audio, digital, sign language communication however we
mostly paid attention to the verbal and non-verbal.

2.4.1. Communication techniques

• Verbal communication

It refers to the use of words, this type of communication can take place face-
to-face, over the phone. Verbal communication is one of the most common and
effective forms of communication.

• Non-Verbal communication

It refers to the use of gestures, body language, and facial expressions to

convey a message. It can also include the way that we use our voice, such as the tone,
pitch, and volume.

Typically, these things serve to support spoken communication. Except

when a person is employing sign language, non-verbal communication is rarely
employed in isolation from verbal communication.

2.5.1.2 Essential Use case Description

A use case is a written description of how users will perform tasks on your
website. It outlines, from a user’s point of view, a system’s behavior as it responds
to a request. Each use case is represented as a sequence of simple steps, beginning
with a user's goal and ending when that goal is fulfilled.

Benefits of Use case

Use cases help explain how the system should behave and, in the process, it
also helps to identify what could go wrong. And here are some of our project’s
functionality using Use case:

19
Super admin

Use case name Add Admin

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin clicks “add admin” button then a form will
appear and the super admin will fill the form and clicks
“save admin”.

Post-condition The new admin will be added into the system.

Use case name View report

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin clicks “view report” on their dashboard

and the report will appear.

Post-condition Report will be viewed.

20
Use case name Update admin

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin will click “list admins” button, the list of
admins will appear and super admin will choose the
admin that is going to be updated and click “update”,
after updating super admin clicks “confirm update”

Post-condition Admin gets updated.

Use case name View reported error messages

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin clicks “view reports” then choose “view
reported error messages” from the listed options and the
maintenance needed error’s report will appear

Post-condition Error’s report will be viewed

21
Use case name Log in

Actor Super Admin

Precondition Super admin account should be created or have to exist.

Basic flow Super admin goes to the site and from the home page
clicks “login” button then login page will appear, and
the super admin will log in as a super admin.

Post-condition Super admin will login and go to the “super admin

dashboard “.

Use case name Log out

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin clicks “account setting” and go to the

“logout” button and confirm.

Post-condition Super admin will be logged out.

22
Use case name Remove Admin

Actor Super Admin

Precondition Super admin should be logged into the system.

Basic flow Super admin clicks “list admins” then go to the admin
being removed and clicks “delete account”, confirm the
removal through authentication.

Post-condition Admin will be removed.

Admin

Use case name Log in

Actor Admin

Precondition Admin’s account has to exist.

Basic flow Admin goes to the site and clicks “login “button then
login page will appear, and the admin will log in as an
admin.

Post-condition Admin is logged in and the dashboard will appear.

23
Use case name Log out

Actor Admin

Precondition Admin’s account has to be logged in.

Basic flow Admin clicks “account setting” and go to the “logout”

button and confirm.

Post-condition Admin is logged out.

Use case name Add users

Actor Admin

Precondition Admin’s account has to be logged in.

Basic flow Admin clicks “add user” button then a form will appear
and the admin will fill the form and clicks “register”.

Post-condition New user is added.

24
Use case name Remove users

Actor Admin

Precondition Admin’s account has to be logged in.

Basic flow Admin clicks “list users” then go to the user being
removed and click “remove”, confirm the removal.

Post-condition User is removed from the system.

Use case name View user accounts

Actor Admin

Precondition Admin's account has to be logged in.

Basic flow Admin clicks “list users” from the dashboard and list of
users will appear.

Post-condition List of users will be viewed.

25
Use case name Send registration /confirmation form

Actor Admin

Precondition Admin's account has to be logged in.

Basic flow After filling the “add user” form then click “send” and
send the form for confirmation.

Post-condition Form will be sent for confirmation.

Use case name Generate and send reports.

Actor Admin

Precondition Admin's account has to be logged in.

Basic flow Admin goes to report section by clicking “report” and

generates one, then fill it out and send it by clicking
“send”.

Post-condition Report will be generated and sent.

26
Transaction checker

Use case name Log in

Actor Transaction checker

Precondition Checkers account have to be logged in.

Basic flow Checker goes to the site and clicks “login” and logging
in as “Transaction checker”.

Post-condition Checker is logged in and dashboard will appear.

Use case name Log out

Actor Transaction checker

Precondition Checker has to be logged in

Basic flow Checker clicks “account setting” and go to the “logout”

button and confirm.

Post-condition checker is logged out.

27
Use case name Check and Confirm transaction.

Actor Transaction checker

Precondition Checker account have to be logged in.

Basic flow Checker will click “list transactions” and choose the
transaction that is going to be checked, check if it is
legit then confirm it by clicking “confirm”.

Post-condition Transaction is checked and confirmed.

Use case name Send confirmed transaction report.

Actor Transaction checker

Precondition Checker account have to be logged in.

Basic flow After checking and confirming a transaction the

checker will generate report about it by clicking
“generate report” and send it by clicking “send” and
“confirm”.

Post-condition Transaction report is sent.

28
Seller

Use case name Sign up

Actor Seller(user)

Precondition Seller have to have internet access.

Basic flow Seller(user) will go to the site and click “sign up” and
signs up as “seller”.

Post-condition Seller(user) is signed up so the seller(user) dashboard

will appear.

Use case name Log in

Actor Seller(user)

Precondition Seller have to have existing account.

Basic flow Seller(user) will go to the site and click “log in ” and
logs in as “seller”.

Post-condition Seller(user) is logged in so the seller(user) dashboard

will appear.

29
Use case name Log out

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “account setting” and go to the

“logout” button and confirm.

Post-condition Seller(user) is logged out.

Use case name Delete account

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “account setting” from dashboard

and click “delete account” from the listed settings and
confirms it.

Post-condition Seller(user) account is deleted.

30
Use case name Update account

Actor Seller(user)

Precondition Seller have to be logged in.

Basic flow Seller (user) clicks “account setting” from dashboard

and click “update account” from the listed settings and
confirms it.

Post-condition Seller(user) account is updated.

Use case name Post products

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “manage posts” from dashboard

then clicks “create post”, a form will appear, seller fills
it out and clicks “create”.

Post-condition Post is created.

31
Use case name Delete post

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “manage posts” from dashboard

then choose a certain post and clicks “delete post”.

Post-condition Post is deleted.

Use case name Update post

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “manage posts” from dashboard

then choose a certain post and clicks “update post” and
confirms.

Post-condition Post is updated.

32
Use case name Send feedback

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller (user) clicks “send feedback” then form appears,
seller will fill it out and clicks “send” and confirms it.

Post-condition Feedback is sent.

Use case name Subscribe

Actor Seller(user)

Precondition Seller have to be logged in

Basic flow Seller(user) clicks “account setting” choose

“subscription” from listed settings, then choose
subscription types and click “subscribe “ then a form
will appear , fill it out and click “confirm.

Post-condition Seller(user) is subscribed.

33
Buyer

Use case name Sign up

Actor Buyer(user)

Precondition Buyer have to have internet access.

Basic flow Buyer(user) will go to the site and click “sign up ” and
signs up as “buyer”.

Post-condition Buyer(user) is signed up so the buyer(user) dashboard

will appear.

Use case name Log in

Actor Buyer(user)

Precondition Buyer(user) have to have existing account.

Basic flow Buyer(user) will go to the site and click “log in ” and
logs in as “buyer”.

Post-condition Buyer(user) is logged in so the Buyer(user) dashboard

will appear.

34
Use case name Log out

Actor Buyer(user)

Precondition Buyer(user) have to be logged in

Basic flow Buyer (user) clicks “account setting” and go to the

“logout” button and confirm.

Post-condition Buyer(user) is logged out.

Use case name See post

Actor Buyer(user)

Precondition Buyer(user) have to be logged in

Basic flow Buyer (user) goes to the site and see products posted by
sellers.

Post-condition Buyer(user) sees/checks posted products.

35
Use case name Delete account

Actor Buyer(user)

Precondition Buyer(user) have to be logged in

Basic flow Buyer (user) clicks “account setting” from dashboard

and click “delete account” from the listed settings and
confirms it.

Post-condition Buyer(user) account is deleted.

Use case name Update account

Actor Buyer(user)

Precondition Buyer(user) have to be logged in.

Basic flow Buyer (user) clicks “account setting” from dashboard

and click “update account” from the listed settings and
confirms it.

Post-condition Buyer(user) account is updated.

36
Use case name Message/notify seller

Actor Buyer (user)

Precondition Buyer (user) have to be logged in.

Basic flow Buyer(user) wanted products post then more detailed

page will appear then click message and send it by
selecting “send”.

Post-condition Message will be sent to the seller.

Alternative flow 1 Buyer goes to seller’s account either by searching or from

the post and message by clicking “message”.

Use case name Search for products

Actor Buyer(user)

Precondition Buyer(user) have to be logged in.

Basic flow Buyer(user) goes to “home” by selecting “home” from

dashboard navigation link and type needed product then
click “search”.

Post-condition Search result will appear.

37
Use case name Place order

Actor Buyer(user)

Precondition Buyer(user) have to be logged in.

Basic flow Buyer(user) selects wanted/needed product then a more

detailed form appears and within that form buyer
selects “place order”.

Post-condition An order is placed.

Use case name Send feedback

Actor Buyer(user)

Precondition Buyer(user) have to be logged in

Basic flow Buyer(user) clicks “send feedback” then form appears,

seller will fill it out and clicks “send” and confirms it.

Post-condition Feedback is sent.

38
 Use case name Rate sellers.

Actor Buyer(user)

Precondition Buyer(user) have to be logged in.

Basic flow Buyer(user) goes to seller’s account either by searching

or from the post, then rate and confirms it by clicking
“rate seller”.

Post-condition Seller is rate by buyer.

2.5.2. Nonfunctional Requirements

1. Usability:
✓ Our platform is easy and clear to use, the familiarity with technology in Ethiopia
is very low so developing easy to use platform will decrease the level of
confusion while using the platform.

✓ In order to attract users usability plays major role, if one’s system is difficult and
unclear to use many of the users will leave and go to a system with much simpler
and clearer user experience.

2. Security:
✓ Is a major problem, in some e commerce platforms accounts are being hacked
and used in order to buy products by the hackers. but our system will not be
affected with such risk.
✓ Our system is highly secured by applying security measures like authentication,
verification, authorization.

39
3. Maintainability:
✓ Systems could break down for a lot of reasons, one of them being large number
of users might apply to the crashing of a certain server. And when systems crash
or stop working a lot of things are on risk.
✓ But our system has its own maintenance team so even if some problem happened
and the system shuts down our maintenance team will make sure it’s up and
running in no time.
4. Performance:
✓ According to Performance wise our system fast and has a quick response, this
days performance is major measurement of systems like ours, performance will
also help us to attract more users. So, our system comes with a fast and satisfying
user experience.

5. Scalability: Scalability refers to the potential of a web application to increase

its ability to handle a heavier workload. During the first stages of our application
development, the app might be able to handle a certain number of users. But
after some time it will be up scaled in order to meet users needs , there by can
handle more clients .

40
 Chapter 3

3. System Modeling

3.1. Introduction
System modeling is the process of designing abstract models of a system, with
each model presenting a different view or perspective of that system. It is about
representing a system using some kind of graphical notation, which is now almost
always based on notations in the Unified Modeling Language (UML). Models help
the analyst to understand the functionality of the system; they are used to
communicate with customers.
Models can explain the system from different perspectives:

• An external perspective, where you model the context or environment of

the system.
• An interaction perspective, where you model the interactions between a
system and its environment, or between the components of a system.
• A structural perspective, where you model the organization of a system
or the structure of the data that is processed by the system.
• A behavioral perspective, where you model the dynamic behavior of the
system and how it responds to events.

Five types of UML diagrams that are the most useful for system modeling:

• Activity diagrams, which show the activities involved in a process or in

data processing.
• Use case diagrams, which show the interactions between a system and its
environment.
• Sequence diagrams, which show interactions between actors and the
system and between system components.
• Class diagrams, which show the object classes in the system and the
associations between these classes.
• State diagrams, which show how the system reacts to internal and
external events.

41
3.2.UI Identification

42
 3.3. Business Rules Identification
• System wise:
✓ Site must be registered with a domain name and hosted on a secure server.
✓ Site must have a shopping cart and an order form.
✓ Site must have product descriptions, images, and prices.
✓ Site must have a search engine optimized layout.
✓ Site must have customer reviews and ratings.

• Sellers wise:
✓ Have to provide valid information in order to sign up.
✓ Have to provide valid login information in order to login.
✓ If can’t sign up by themselves then the admins planted around will create the
account for them.
✓ Have to pay half of the delivery cost.
✓ Have to subscribe in order to gain from premier package like faster delivery etc.
✓ Have to pay to subscribe.
✓ If payment is not done the subscription will be canceled.
✓ Have to provide valid information about the product before posting.
✓ Will receive payment when the product is delivered to the buyer.
✓ Can cancel subscription anytime.
✓ Must be over the age of 18.
• Buyers wise:
✓ Have to provide valid information in order to sign up.
✓ Have to provide valid login information in order to login.
✓ Have to pay half of the delivery cost.
✓ Have to pay for the product they ordered.
✓ If canceled order payment will be refunded.
✓ Can rate seller depending on the quality of the product and character of the
seller.
✓ Must have valid address.
✓ Must be over the age of 16.
43
 • Admin wise:
✓ Can’t create their own account the super admins will handle that.
✓ Must create user account for those who are unable.
✓ Can’t create user account without super admin’s approval.
✓ Have to send reports to the super admins depending on the situation.
✓ Can’t update or delete user account without super admin’s approval.

3.4. Actor Identification

Identifying actors is one of the first steps in use case analysis. Each type of external
entities with which the system must interact is represented by an actor. It Includes
the actor's area of responsibility and the goals that the actor will attempt to
accomplish when using the system. Eliminate actor candidates who do not have
any goals.

An actor in use case modeling specifies a role played by a user or any other system
that interacts with the subject.

Actors
Primary actors of the use case are the stakeholders that calls on the system to
deliver its services. It has a goal with respect to the system, one that can be
satisfied by its operation.

➢ Primary Actors:
✓ Super Admins
✓ Admins
✓ Sellers
✓ Buyers
✓ Transaction Checkers

44
 3.5. Use Case Diagram
A use case diagram is used to represent the dynamic behavior of a system. It
encapsulates the system's functionality by incorporating use cases, actors, and their
relationships. It models the tasks, services, and functions required by a
system/subsystem of an application. It depicts the high-level functionality of a system
and also tells how the user handles a system.

45
 3.6. Sequence Diagram
UML Sequence Diagrams are interaction diagrams that detail how operations are
carried out. They capture the interaction between objects in the context of a
collaboration. Sequence Diagrams are time focus and they show the order of the
interaction visually by using the vertical axis of the diagram to represent time what
messages are sent.
i. Signup
• The sequence diagram below shows how a user signs up in order to
access the dashboard.
• The user will access the signup page from the home page by clicking
“sign up” link or button.
• The user will also access the home page by using URL.

46
ii. Login
• The sequence diagram below shows how a user logs in in order to
access the dashboard and profile.
• The user will access the login page from the home page by clicking
“login” link or button.
• The user will also access the home page by using URL.

47
iii. Logout
• The sequence diagram below shows how a user can log out of the
site.
• The user will access the logout button or link from the dashboard
settings.
• After the logout the session will end.

48
iv. Post Product
• The sequence diagram below shows how a seller posts their products
on the site.
• The sellers have to fill all the fields in order to post the product.
• The sellers can access the post form from their dashboard.

49
v. Update user
• The sequence diagram below shows how an admin updates user’s
account.
• The admin needs the user’s and super admin’s approval in order to
update the account.
• The admin will access the update user link or button from their
dashboard.

50
vi. Delete user
• The sequence diagram below shows how an admin deletes user’s
account.
• The admin will access the delete user through link or button from
their dashboard.
• The admin will need the user’s and super admin’s approval in order
to delete user’s account.

51
 3.7. Activity Diagram
Activity diagram in UML diagram is used to describe dynamic aspects of the
system. Activity diagram is essentially an advanced version of flow chart that
modeling the flow from one activity to another activity. In the UML, activity
diagrams are intended to model both computational and organizational process.

52
 3.8. Class Diagram
A class diagram is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects.

53
 3.9. State Chart Diagram
A state diagram is a type of diagram used in computer science and related
fields to describe the behavior of systems. State diagrams require that the system
described is composed of a finite number of states; sometimes, this is indeed the case,
while at other times this is a reasonable abstraction.

54
 Chapter 4
4. System Design
4.1. ER-Diagram
An Entity Relationship (ER) Diagram is a type of flowchart that
illustrates how entities such as people, objects or concepts relate to each other
within a system. ER Diagrams are most often used to design or debug relational
databases in the fields of software engineering, business information systems,
education and research. Also known as ERDs or ER Models, they use a defined
set of symbols such as rectangles, diamonds, ovals and connecting lines to depict
the interconnectedness of entities, relationships and their attributes. They mirror
grammatical structure, with entities as nouns and relationships as verbs.

55
 4.2. Database Table Structure
A database is an organized collection of data. Instead of having all the data in
a list with a random order, a database provides a structure to organize the data. One
of the most common data structures is a database table. A database table consists of
rows and columns. A database table is also called a two-dimensional array. An array
is like a list of values, and each value is identified by a specific index.

56
 4.3. Database Normalization
Is a database design technique that reduces data redundancy and eliminates
undesirable characteristics like Insertion, Update and Deletion anomalies.
Normalization rules divides larger tables into smaller tables and links them using
relationships. The purpose of Normalization in SQL is to eliminate redundant
(repetitive) data and ensure data is stored logically.

Tables:

1) Super Admin (Id, FName, LName, Username, Password, Address).

2) Admin (Id, FName, LName, Image, Address, Admin_type_id, Username,
Password).
3) Seller (Id, FName, LName, Image, Address, Username, Password,
Seller_type_id).
4) Buyer (Id, FName, LName, Image, Address, Username, Password).
5) Product (Id, Product_name, Location, Product_category_id, Price,
Product_type_id, Product_description, Image).
6) Discount (Id, Name, Product_id, Discount_%, Discount_discription,
Product_type_id, Product_category_id, Expiry_date).
7) Activity (Id, Activity_type).
8) Product_Category (Id, Product_category).
9) Product_type (Id, Product_type).
10) Seller_type (Id, Seller_type).
11) Admin_type (Id, Admin_type).
12) Ordered_item (Id, Product_id, Product_type_id, Product_category_id,
Quantity, Location, Buyer_id, Seller_id)

1NF(First normal form):

Rule1: Each table cell should contain a single value.

Rule2: Each record needs to be unique.

✓ So when we come to the first normal form all the tables satisfy both rule 1 and
2, so they are in 1nf.

2NF(Second normal form):

Rule1: Be in 1NF.

Rule2: Single Column Primary Key that does not functionally dependent on any
subset of candidate key relation.

✓ All the tables above are in 1NF and they are not functionally dependent so
they fulfill the rules , and that makes them in 2NF.

57
3NF(Third normal form):

Rule 1: Be in 2NF.

Rule 2: Has no transitive functional dependencies.

✓ A transitive functional dependency is when changing a non-key column,

might cause any of the other non-key columns to change.
✓ Again, all the above tables fulfill both rule 1 and 2 of 3nf, so they are in 3nf.

4.4. Deployment Diagram

A UML deployment diagram is a diagram that shows the configuration of run
time processing nodes and the components that live on them. Deployment diagrams
is a kind of structure diagram used in modeling the physical aspects of an object-
oriented system. They are often be used to model the static deployment view of a
system (topology of the hardware).

58
 4.5. High Fidelity Prototype
High fidelity (hi-fi) design closely matches the final result of a product's
design. Content, visual styles, and animated transitions all work together to make high
fidelity assets look and work as close to the final product as possible.

59
60
 Chapter 5

5. Conclusion and recommendation

5.1. Conclusion
Agri-e-commerce is revolutionizing the way farmers, agricultural enterprises,
and agro-based industries buy and sell goods and services. The internet has tightened
and facilitated relationships between buyers and sellers, increasing the visibility of
the global supply chain. Online buying and selling of various tools and necessities for
agricultural purposes can address important issues and inefficiencies by enhancing
farmers' access to clients and creating new linkages across steps in the value chain.
There is an increasing possibility that these platforms will disrupt the agriculture
supply value chain in various Ethiopian regions as investors build on the rising
adoption of mobile internet and digital payment solutions. E-agriculture has the
potential to spur economic growth and increase incomes for the rural poor by
enhancing the efficiency of agricultural production, enhancing livelihoods, and
developing value chains. It converts in-person transactions involving the purchase
and sale of agricultural goods and services into online exchanges, providing a direct
connection between buyer and seller, a simplified agricultural value chain, and a
reduction in inefficiencies in the delivery of farm products. It also expands farmers'
access to new markets and boosts value chain transparency by giving them a fresh,
cutting-edge way to sell their food to a range of clients. This new ecommerce platform
could significantly alter the agricultural economy.

5.2. Recommendation
We recommend this system to all marketers and agricultural product suppliers
those who buy and sell agricultural products in Addis Ababa.

61
 References
1. www.scialert.com, O. Folorunso, Sushil K. Sharia, H.O.D Lounge and

K. Lasaki, 2006 . An agent-based model for agricultural ecommerce system.

Information journal.

2. visual paragdim developers team. UML-Unified-Modeling-Language.

Visual paragdim. [Online] 2023. [Cited: January 19, 2023.]

https://www.visual-paradigm.com.

3. www.psu.edu, Sarah Cornelissen, Senior extension Associate.

Ecommerce for agricultural business and challenges.

4. freecodecamp.com, Kolade Chris article, Database Normalization.

5. wikipidia.org. E-commerce. Wikipedia. [Online] February6, 2023.

https://en.wikipedia.org.

62
 Appendix
Interview Questions
1. ለቤት አስቤዛ የሚሆኑ የግብርና ምርቶችን ከየት ነው የሚያገኙት?
Where do you get agricultural products for daily home usage?
_________________________________________________________________________________________________________
የሚያስፈልግዎትን የግብርና ምርት ለመግዛት ዘመን አፈራሽ ቴክኖሎጂዎችን ወይም የኦንላይን
ግብይትን በመጠቀም ተገበያይተው ያውቃሉ?
Have you ever used digital technologies to trade agricultural products?
_________________________________________________________________________________________________________
2. ካልተጠቀሙስ ላለመጠቀምዎ ምክንያትዎ ምንድን ነው?
If you didn’t used it, why?
_________________________________________________________________________________________________________
3. ለችርቻሮ ሽያጭ የምታቀርቧቸውን የግብርና ምርቶች ከየት ነው የምታገኙት?
Where did you find your retail agricultural products for sale?
_________________________________________________________________________________________________________
4. ለገበያ የምታቀርባቸውን የግብርና ምርቶች እንዴት ነው ለገበያ ተደራሽ የምታደርጉት?
How did you make your agricultural products accessible for the market?
_________________________________________________________________________________________________________
5. የግብርና ምርቶችን ለገበያ ተደራሽ ለማድረግ ዘመን አፈራሽ ቴክኖሎጂዎችን ወይም የኦንላይን
ግብይትን በመጠቀም ተገበያይተው ያውቃሉ?
Have you ever used digital technologies to provide your agricultural
products for the market?
_________________________________________________________________________________________________________

63
 Certificate of Authenticated work
This is to certify that the project report entitled Agricultural Ecommerce
System (AgriCom) submitted to St. Mary’s University in partial fulfillment of
the requirement for the award of the degree of Bachelor of Science in
Computer Science is an original work carried out by:

1. Amanuel Zegeye RCD/1250/2012

2. Dagmawi Tariku RCD/1256/2012
3. Kirubel Mulugeta RCD/1275/2012
4. Victor Getnet RCD/1287/2012

The matter embodied in this project is authentic and is genuine work

done by the students and has not been submitted whether to this university or
to any other university/institute for the fulfillment of the requirement of any
course of study.

Signature of the Group members: 1) ……….……….……….

2) ……….……….……….

3) ……….……….……….

4) ……….……….……….

Advisor Name: Mr. Addisu Anbessa (MSc.)

Date 17-02-2023

Signature of advisor ……….……….……….

64