Final Project Full Documentation Ver.3.0

Unity University
College of Engineering, Technology and Computational Science

Department of Computer Science and MIS
Title: Coffee Export Management System

Final project document
Submitted to department of Computer Science and MIS in partial
fulfillment of the requirements for the degree of Bachelor Science in
Computer Science.
By
Abubeker Misbah
Bereket G/Medhin
Leul Tsegahun
Mai Tut Yoal
Yeab Andargachew
Advisor:
Mr. Melaku Dagnew
August 2022
1
Coffee Exporting System
Final project document
Submitted to department of Computer Science and MIS in partial

fulfillment of the requirement for the degree of Bachelor Science in
Computer Science.
By:
Abubeker Misbah
Bereket G/Medhin
Leul Tsegahun
Mai Tut Yoal
Yeab Andargachew
Advisor:
Mr. Melaku Dagnew ____________
Examiner:
____________
2
Abstract
Coffee was originally native only to a relatively small region in Ethiopia but its
usefulness to an active and productive lifestyle has made it into one of the planet’s most
popular drinks spreading via trade from early travelers.
There is some evidence that the first steps towards modern coffee were taken in the form
of grinding coffee beans into a thick paste that could be easily packed and carried by
travelers. Word of mouth and trade of this paste was responsible for the eventual
spreading of coffee from Africa outward to the rest of the world. As the popularity of
these energizing beans grew, coffee as we know it began to take shape, first as a
fermented wine-like drink. Today, coffee is still a major part of the Ethiopian culture and
economy. Coffee is Ethiopia’s number one export and has been for many decades.
Recently, the fair-trade movement to ensure fair compensation for coffee farmers has
taken hold in Ethiopia after many years of hardship. Ethiopia thrives on its coffee
production, and recent movements are helping secure coffee farming as a viable means of
making a living for Ethiopians. Ethiopian coffee is unique, even among African coffee,
and is completely different from Central and South American coffee. To promote
economic development and survival in the global competitive market, export
competitiveness is an essential component of a country. Massive integration of
information technology into all aspects of modern human life caused demand for
processing e-commerce for international markets. In the world, many types of
products/goods are exported to boost a country’s economy by facilitating international
trades and simulating domestic economic activity by creating employment, production,
and revenues. One of our country’s top exports is coffee 2nd only to gold. Gold is our top
exported product at 21% of the total goods that are exported and coffee is not far behind
at 19% of the entire agricultural products produced in Ethiopia. This project aims to give
illiterate farmers an easy-to-understand access system that’ll handle trade calculations,
handle and organize paperwork, and maximize the profit the farmers rightfully deserve.
We want to ensure that all parties involved get their rightful dues.
Key words
3
Coffee, Export, Farmers, System, Online
ACKNOWLEDGEMENT
First and foremost, praises and thanks to the God, the Almighty, for His showers of
blessings throughout our life and project work to complete the project successfully.
We would like to express our deep and sincere gratitude to our project supervisor Mr.
Melaku Dagnew for giving us the opportunity to do project and providing invaluable
guidance throughout this project. He has taught us the methodology to carry out the
project and to present the project works as clearly as possible. It was a great privilege
and honor to work and study under his guidance. We are extremely grateful for what he
has offered to us. We would also like to thank him for his leadership, empathy, and
knowledge. We take this opportunity to express gratitude to all of the Department
faculty members for their help and support. We are also grateful to our friends who
supported us through this project.
We are extremely grateful to our parents for their love, prayers, caring and sacrifices for
educating and preparing us for our future. We also place on record, our sense of gratitude
to one and all, who directly or indirectly, have lent their hand in this project.
4
List of abbreviation
RMMM – Risk Mitigation, Management, and Monitoring
MMM – Mitigation, Management, and Monitoring
R – Risk
SQL – Structured Query Language
WBS – Work Breakdown Structure
HRP – Human Resource Planning
UI – User Interface
UC- use case
SUC - System Use case
BR – Business Rule
CPU – Central Processing Unit
I/O – Input / Output
PC – Personal Computer
DB- Database
5
List of Tables
Table 1. 1 Project Schedule.............................................................................................................5
Table 2. 1 Human Resources Planning............................................................................................9

Table 2. 2 Human resource financial plan.....................................................................................10
Table 2. 3 Risk item table..............................................................................................................13
Table 2. 4 risk item plan sheet 1....................................................................................................13
Table 2. 10 risk item plan sheet 7..................................................................................................16
Table 2. 11 risk item plan sheet 8..................................................................................................16
Table 3. 1 Users have to be logged in before performing some actions BR.................................29

Table 3. 2 Farmers have to be registered in the system before inspecting the products...............30
Table 3. 3 The payment must be performed by Letter of Credit method(L/C).............................30
Table 3. 4 The Products in the system should be licensed............................................................31
Table 3. 5 Log in............................................................................................................................35
Table 3. 6 Log out..........................................................................................................................35
Table 3. 7 Create account..............................................................................................................36
Table 3. 8 View product................................................................................................................36
Table 3. 9 Add to cart....................................................................................................................37
Table 3. 10 Search Products..........................................................................................................37
Table 3. 11 View Products details.................................................................................................37
Table 3. 12 Checkout product........................................................................................................38
Table 3. 13 Inspect product...........................................................................................................39
Table 3. 14 View profile................................................................................................................39
Table 3. 15 Contact us...................................................................................................................40
Table 3. 16 About us......................................................................................................................40
Table 3. 17 Terms and conditions..................................................................................................41
Table 3. 18 Register new farmer....................................................................................................41
Table 3. 19 Customs Inspection.....................................................................................................42
Table 3. 20 Add Products..............................................................................................................42
Table 4. 1 Client table....................................................................................................................67

Table 4. 2 Client first normal form table.......................................................................................68
Table 4. 3 Client final normalization table....................................................................................68
Table 4. 4 product table.................................................................................................................69
Table 4. 5 product first normal form table.....................................................................................69
6
Table 4. 6 product second normal form table................................................................................70
Table 4. 7 product second normal form table................................................................................70
Table 4. 8 product normalized table..............................................................................................71
Table 4. 9 order table first normal form........................................................................................72
Table 4. 10 order final normalized form........................................................................................72
Table 4. 11 delivery final normalized form...................................................................................73
Table 4. 12 farmer table.................................................................................................................73
Table 4. 13 farmer first normal form table....................................................................................74
Table 4. 14 farmer second normal form table................................................................................74
Table 4. 15 farmer second normal form table................................................................................75
Table 4. 16 admin table.................................................................................................................75
Table 4. 17 admin first normal form table.....................................................................................76
7
List of Figures
Figure 2. 1 Work Breakdown Structure...........................................................................................8

Figure 2. 2 Team Organization......................................................................................................11
Figure 3. 1 Use Case Diagram.......................................................................................................24

Figure 3. 2 Essential UI prototype.................................................................................................28
Figure 3. 3 User Interface Flow Diagram......................................................................................29
Figure 3. 4 System Use Case Diagram..........................................................................................35
Figure 3. 5 Add Product Sequence Diagram.................................................................................45
Figure 3. 6 Checkout Sequence Diagram......................................................................................46
Figure 3. 7 Create Account Sequence Diagram.............................................................................47
Figure 3. 8 Profile Page Sequence Diagram..................................................................................48
Figure 3. 9 Logout Sequence Diagram..........................................................................................49
Figure 3. 10 Logout Sequence Diagram........................................................................................50
Figure 3. 11 Contact Us Sequence Diagram..................................................................................51
Figure 3. 12 Login Sequence Diagram..........................................................................................52
Figure 3. 13 View product Sequence Diagram..............................................................................53
Figure 3. 14 Ratings Sequence Diagram.......................................................................................54
Figure 3. 15 Login Activity Diagram............................................................................................55
Figure 3. 16 Create Account Activity Diagram.............................................................................56
Figure 3. 17 Logout Activity Diagram..........................................................................................57
Figure 3. 18 View Profile Activity Diagram.................................................................................57
Figure 3. 19 Contact us Activity Diagram.....................................................................................58
Figure 3. 20 Add Product Activity Diagram.................................................................................58
Figure 3. 21 Checkout Activity Diagram......................................................................................59
Figure 3. 22 View Product Activity Diagram................................................................................59
Figure 3. 23 Add Farmer Activity Diagram..................................................................................60
Figure 3. 24 Add to Cart Activity Diagram...................................................................................60
Figure 3. 25 Inspect Product Activity Diagram ............................................................................61
Figure 3. 26 Search Activity Diagram...........................................................................................62
Figure 3. 27 View Product Details Activity Diagram...................................................................62
Figure 3. 28 About us Activity Diagram.......................................................................................63
Figure 3. 29 terms and conditions Activity Diagram....................................................................63
Figure 3. 30 View Current Clients Activity Diagram....................................................................63
Figure 3. 31 Customs inspection Activity Diagram......................................................................64
Figure 3. 1 Use Case Diagram.......................................................................................................24

Figure 3. 2 Essential UI prototype.................................................................................................28
Figure 3. 3 User Interface Flow Diagram......................................................................................29
Figure 3. 4 System Use Case Diagram..........................................................................................35
Figure 3. 5 Add Product Sequence Diagram.................................................................................45
8
Figure 3. 6 Checkout Sequence Diagram......................................................................................46
Figure 3. 7 Create Account Sequence Diagram.............................................................................47
Figure 3. 8 Profile Page Sequence Diagram..................................................................................48
Figure 3. 9 Logout Sequence Diagram..........................................................................................49
Figure 3. 10 Logout Sequence Diagram........................................................................................50
Figure 3. 11 Contact Us Sequence Diagram..................................................................................51
Figure 3. 12 Login Sequence Diagram..........................................................................................52
Figure 3. 13 View product Sequence Diagram..............................................................................53
Figure 3. 14 Ratings Sequence Diagram.......................................................................................54
Figure 3. 15 Login Activity Diagram............................................................................................55
Figure 3. 16 Create Account Activity Diagram.............................................................................56
Figure 3. 17 Logout Activity Diagram..........................................................................................57
Figure 3. 18 View Profile Activity Diagram.................................................................................57
Figure 3. 19 Contact us Activity Diagram.....................................................................................58
Figure 3. 20 Add Product Activity Diagram.................................................................................58
Figure 3. 21 Checkout Activity Diagram......................................................................................59
Figure 3. 22 View Product Activity Diagram................................................................................59
Figure 3. 23 Add Farmer Activity Diagram..................................................................................60
Figure 3. 24 Add to Cart Activity Diagram...................................................................................60
Figure 3. 25 Inspect Product Activity Diagram ............................................................................61
Figure 3. 26 Search Activity Diagram...........................................................................................62
Figure 3. 27 View Product Details Activity Diagram...................................................................62
Figure 3. 28 About us Activity Diagram.......................................................................................63
Figure 3. 29 terms and conditions Activity Diagram....................................................................63
Figure 3. 30 View Current Clients Activity Diagram....................................................................63
Figure 3. 31 Customs inspection Activity Diagram......................................................................64
Figure 4. 1 Subsystem decomposition...........................................................................................68

Figure 4. 2 Class modeling diagram..............................................................................................69
Figure 4. 3 Mapping class diagram to relation..............................................................................70
Figure 4. 4 UI Design....................................................................................................................90
Figure 4. 5 Network Diagram........................................................................................................91
9
Appendices
 Interview Questions
Priority Questions
1. What is the scope/scale of your work?
2. What were the goals of the system and company?
3. How does the current system work? How do you handle:
a. Payment?
b. Quality Assurance, Certification, and documentation?
i. What types of beans are sold? Pre-roasted, roasted, and/or ready-to-plant.
ii. How are they sanitized? Do you hire third-party aid or is it done within the
company?
c. Storage of the product?
d. Packaging and shipment?
4. How do they get in contact with the importers/ buyers locally and internationally?
5. What happens to the product that wasn’t sold promptly or was rejected by buyers?
6. RISK Management Plan
a. What were the RISKs and how were they managed during the startup and
currently?
7. What system model are you using?
8. Who are the competitors of the company?
10
Non-Priority Questions
1. Does the export company have a website?
2. What were the goals and tradeoffs made when making the system the company uses
now?
3. Tools and Methodologies
a. How was the initial planning and setup of operations done?
b. How was data collected and what was relevant? If possible, may we use it as a
reference for the out project?
c. What were the Development tools used?
4. Continuation of question 4: How do you avoid this problem from occurring? What
happens when buyers don’t want the product after it has been shipped?
5. Where there any beneficiaries? Who were they?
6. How long did it take to get everything set up and operational?
11
Table of Contents
1. Chapter One – Introduction..................................................................................................1
1.1 Background Information...............................................................................1
1.2 Statement of the Problem..............................................................................1
1.3 Objectives........................................................................................................2
1.3.1. General Objective........................................................................................................................2
1.3.2. Specific Objectives......................................................................................................................3
1.4. Scope of the Project.......................................................................................3
1.4.1. Justification..................................................................................................................................3
1.4.2. Deliverables.................................................................................................................................3
1.4.3. Inclusions.....................................................................................................................................4
1.4.4. Exclusions....................................................................................................................................4
1.5 Tools and Methodologies...............................................................................4
1.5.1 Data Collection Methodologies....................................................................................................4
1.5.2 System Development Methodology..............................................................................................4
1.5.3 Development Tools.......................................................................................................................4
1.6 Beneficiaries....................................................................................................6
1.7 Schedule...........................................................................................................6
Table 1. 1 Project Schedule...................................................................................................................6
Chapter Two - Project Management...........................................................................................8
2.1 Introduction....................................................................................................8
2.2 Project Planning.............................................................................................9
2.2.1 Work Breakdown Structure..........................................................................................................9
2.3 Resource Planning........................................................................................10
2.3.1 Human Resource Planning..........................................................................................................10
Table 1.1 Human Resources Planning.................................................................................................10
2.4 Financial Planning........................................................................................11
2.4.1 Human Resource Financial Plan.................................................................................................11
Table 1.3 human resource financial plan.............................................................................................11
2.5 Team Organization......................................................................................12
2.5.1 Conceptual Designers.................................................................................................................12
12
2.5.2 Research......................................................................................................................................12
2.5.3 System and Database Designers.................................................................................................12
2.5.3UI Designers................................................................................................................................12
2.5.4Document Writers........................................................................................................................12
2.6 Process Model...............................................................................................12
2.7 Risk MMM Plan...........................................................................................13
2.7.1 Risk Items Table.........................................................................................................................13
Table 1.6 risk item table.......................................................................................................................13
2.7.2 RMMM Plan..............................................................................................13
Table 1.7 risk item plan sheet 1...........................................................................................................13
Table 1.10 risk item plan sheet 4.........................................................................................................15
Choose the Ideal Packaging Type and Size......................................................16
Chapter Three - System Analysis...............................................................................................18
3.1 Introduction..................................................................................................18
3.2 Current System Overview...........................................................................18
3.3 Proposed System Overview.........................................................................19
3.3.1 Functional Requirements............................................................................................................19
3.3.2 Non-Functional Requirements....................................................................................................22
3.4 System Models - Requirement Determination...........................................23
3.4.1 Essential Use Case Modeling......................................................................................................23
Table 3.1 Essential Use Case Modeling..............................................................................................23
3.4.1.1 Use Case Diagram....................................................................................................................24
3.4.2 Essential UI Prototype................................................................................................................25
3.4.3 User Interface Flow Diagram......................................................................................................29
3.4.4 Supplementary Specifications.....................................................................................................30
3.5 System Models - Analysis............................................................................34
3.5.1 System Use Case Modeling........................................................................................................35
13
Chapter Four - System Design....................................................................................................60
4.1 Introduction..................................................................................................60
4.2 Design Goals..................................................................................................61
4.3 Design Tradeoffs...........................................................................................61
4.4 Subsystem Decomposition...........................................................................63
4.5 Design Phase Models....................................................................................64
4.5.1 Class Modelling..........................................................................................................................64
4.5.2 Persistent Model..........................................................................................................................65
4.5.3 User Interface Design.................................................................................................................78
Chapter Five - Implementation..................................................................................................82
5.1 Introduction..................................................................................................82
5.2 Sample Code.................................................................................................83
Register a new user php code............................................................................................................83
Loin in php code.................................................................................................................................84
Connect to the database php code....................................................................................................85
Cart clear php code............................................................................................................................85
Categories php code...........................................................................................................................86
Cart page php code............................................................................................................................88
Cart update php code........................................................................................................................90
References.....................................................................................................................................91
14
1. Chapter One – Introduction
1.1 Background Information

Ethiopia is the birthplace of coffee and has some of the most dynamic flavors you’ll find
anywhere in the world. There are between 6 and 10 thousand different types of coffee from
Ethiopia, but they are usually distinguished by their region, altitude, and cupping score instead of
by type[1].
Our country's top export is coffee and it is by far our largest export generating $894m in revenue
from the Coffee trade in the first three quarters of the 2021/22 fiscal year[2]. Yet even with all of
this revenue coffee brings in our farmers still live in poverty and most of the coffee we export is
coffee arabica.
1.2 Statement of the Problem

Nowadays the growth of a country is mainly determined by commerce. Commerce done within
a country will keep its citizens from starving, put more money into the hands of both the citizens
and the government, and allow for a better standard of living. With the development of
technology, it is now done with e-commerce, e-commerce done with other nations will introduce
a new friendly relationship
Access to markets and marketing information by small farmers depending on agriculture in
developing countries have always been challenging. Factors such as poor road infrastructure,
illiteracy, financial constraints, poor communication means, and lack of access to information, all
limited their access to markets.[3]
This project aims to provide illiterate farmers with an easy-to-understand and accessible system
that’ll handle trade and tax calculations, organize paperwork, and bring their products to the
trading table. We want that all parties involved get a proper reward.
1
In addition to that most of the coffee, Ethiopia trades is coffee arabica, so we also hope to
bring Ethiopia's diverse variety of coffee to the market and provide a simple and user-
friendly method of buying, exporting, selling, and advertising local coffee (with all
finances and taxes accounted for)!
Our system provides multiple solutions:
● It will enable the exporters to directly get in touch with the farmers and foreign
representatives or importers.
● It will help advertise the price, quality, quantity they are capable of producing at a
time, and various types of the product.
● Manage inventory, stock, and quality management.
● A way to contact and address the farmer and educate him to produce a stable
output of goods that meets international market demands.
● A system to approve a product if its quality meets international market demand or

if they don't meet it will give useful information for how to meet those standards.
● This system will ease the search for good products for importers by distinguishing
between the price, type from a diver’s exporters.
● It will track the fluctuations of foreign currency and tell when and where is the
most optimum time and place to export to.
This and many more functionalities that we think will change the cluster of problems that
are present now in the current system.
1.3 Objectives
1.3.1. General Objective

The overall objective of our project is to develop a platform for exporting, ordering, and
selling coffee.
1.3.2. Specific Objectives
● To have a working store page
2
● To be able to add, modify, display, and remove coffee available for export
● To have order and cart functionalities
● To provide shipping options
● To automatically handle financial calculations like taxes and shipping
● To have a secure login functionality
1.4. Scope of the Project

This project is aimed to develop an online market place for the export of Ethiopian coffee.
1.4.1. Justification
Our justification is that there are no user-friendly and easy-to-access markets that handle
the export of Ethiopian coffee. This is a profitable and exploitable opportunity that we
can use to expose more Ethiopian coffee types to the global market while also providing
local farmers with a better share of profits.
1.4.2. Deliverables
● Catalogue of coffee that are ready for export
● Fully functional e-market
● Report on coffee sales
● Calculation of taxes, shipping, and currency exchange
● Options for shipping
3
1.4.3. Inclusions
● Cart and Order capabilities
● Search for a product by name and add to cart
● Inspect product
● Register a new farmer
● Order a product and a confirmation message after order is complete
1.4.4. Exclusions
● Live tracking of shipments
● Fully functional customer service
1.5 Tools and Methodologies
1.5.1 Data Collection Methodologies
● Observation – by observing how the current system operates
● Interview – conducted with EXC, the Ethiopian coffee and tea authority, and a
business insider
● Document analysis – by analyzing documents and records relating to coffee

export
1.5.2 System Development Methodology

The system development paradigm that we are going to use in this project is Object-
Oriented System Analysis and Design because it is easier to use and it has a modern
paradigm.
4
1.5.3 Development Tools
The tools listed below are what we may use to develop this system.
● Html CSS JS - The Hyper Text Markup Language, or HTML is the standard
markup language for documents designed to be displayed in a web browser. It can
be assisted by technologies such as Cascading Style Sheets and scripting
languages such as JavaScript.
● Visual Studio Code – Code editor to write most of our code
● My SQL - is an open-source relational database management system.
● Adobe XD, Sketch - to design wireframes, UI prototypes, and mockups
● Microsoft Word – to prepare documentation for the project
● Telegram – to communicate with team members
● Figma and creatively – to design the diagrams in use
1.6 Beneficiaries
● Farmers who couldn’t sell their products/goods to exporters directly and access more
customers and business
● Diversifying market opportunities so that even if the domestic economy begins to falter,
you may still have other growing markets for your goods and services.
● Exporters who were backed up with a documentation cluster.
● The country itself will benefit by getting more income from foreign currency.
1.7 Schedule
The project was started on December 17, 2021, and we expect to finish the project within
approximately 7-9 months.
5
Table 1. 1 Project Schedule
Activity Immediate Duration (Week/Month)

predecessor
Initiation and Planning - 1 week
System Analysis Initiation and Planning 2 weeks
Designing System Analysis 1 month
Research and Interviews Designing 3 weeks
Coding and database building Research 2 months
Testing Coding 1 month
Project Closure Testing 1 week
Chapter Two - Project Management
2.1 Introduction
Project management is the process of leading the work of a team to achieve all project goals
within the given constraints the information is usually described in project documentation
created at the beginning of the development process. Our project is a coffee exporting system to
create a system that will help farmers produces good quality products for international markets.
Realizations of these objectives require systematic planning and careful implementation. Project
management in recent years has proliferated, reaching new heights of sophistication. It has
emerged as a distinct area of management practices to meet the challenges of the new economic
environment, globalization process, rapid technological advancement, and quality concerns of
the stakeholders.
6
2.2 Project Planning
2.2.1 Work Breakdown Structure

A WBS is a deliverable-oriented breakdown of a project into smaller components. WBS is a key
project deliverable that organizes the team’s work into manageable sections. It’s the hierarchical
decomposition of the total scope of the work. The project is classified into seven common major
tasks or activities which are initiation, planning, analyzing, execution, control, and closure. In the
initiation phase, we will identify where the project will be implemented and we will recommend
certain areas for the implementation of the project. Next is the planning phase which will include
the scope of the project and recruiting team members then we will analyze the requirement
specifications after that we will head to the project kickoff, developing, designing, and testing
the system. Risk management, updating, and closure of the project are done in the final phases.
(The figure below was done using https://app.creately.com/, a SaaS visual collaboration tool with
diagramming and designing capabilities by Cinergix, We used the online cloud edition on windows10).
7
Figure 2. 1 Decomposed Work Breakdown Structure
2.3 Resource Planning
Our resources planning will allocate tasks to human and non-human resources to maximize
efficiency. The tasks for employees are communicating with the customer, evaluating the
products, and effortlessly connecting exporters with importers of other nations. The software will
keep track of the foreign exchange rate and advertise the product's type, quantity, quality, and
price.
8
2.3.1 Human Resource Planning
To give the best experience for our user/customer when using our services, we systematically
plan ahead of time and continuously to achieve an optimum customer-employee relationship that
is the most valuable asset of our organization
 The following table shows the human resources that we are going to need for the
project:
Table 1.1 Human Resources Planning
ROLE HUMAN RESOURCES NUMBER OF EMPLOYMENT TYPE

YEARS
1 Project manager >2 Employee
2 Developer >3 Employee
3 UX Designer >1 Employee
4 Database designer >1 Employee
5 System Analyzer >2 Employee
6 Test Engineer >3 Employee
7 Sponsor - -
8 User/customer - -
2.3.2 Material / Equipment Planning

 The following table shows the material/equipment resources that we are going to need
for our project:
Table 1.2 Material/Equipment planning
Material/Equipment unit Requirement Purchase/Lease

1 Office 1 100 square feet Lease
2 Office telephone 5 Panasonic KX-TG7875S Bluetooth Purchase
Cordless Phone
3 Office furniture 25 1-Desk, 5-workstations(cubical), 1- Purchase
9
long desk, and 15 chairs.
4 Office car 2 Toyota Hilux X-Cab 2000 Purchase

5 Printer 2 Xerox B215 Multifunction Purchase
Monochrome Laser Printer
6 A4 Paper 4 Double-A Purchase
7 Wi-Fi router 1 TP-LINK Purchase
8 Lockers 2 15” wide standard metal lockers Purchase
9 Accessories (pen, pencil, 1 1-pack of each accessory Purchase
stapler
10 Hard disk 2 Transcend Hard Drive 2TB Purchase
11 Mobile’s (Android and 2 Samsung Galaxy A10 and Purchase
iPhone) iPhone 9
12 Small Fridge 1 Samsung Purchase
13 Water filter 1 Live is Good Purchase
14 Computer’s 10 5-desktops Brand: DELL Purchase
Model: OptiPlex 7010
Processor: Intel Core i5
Storage Size: 500GB
RAM: 8GB
Screen Size: 21 inch
Storage Type: Hard Disk Drive
(HDD)
5-workstations Brand: Acer
Aspire TC-895-UA92,
Processor: 7th Gen Intel Core i7-
7700 6-Core Processor,
Ram:16GB DDR4,
Storage:1TB SSD
15 Warehouse 1 1000 square feet Lease
10
2.4 Financial Planning
2.4.1 Human Resource Financial Plan

 The following table shows the financial plan for the human resources (which are
mentioned above)
Table 1.3 human resource financial plan
Human Roles Duration unit hour Payment Payment Budget

Resources per hour per week
1 Project Manages the 17 weeks 1 720 100 4,000 72,000
manager overall process
2 developer Builds the actual 8 weeks 3 320 80 3,200 25,600
solution
3 Ux-designer Creates user- 2 weeks 1 80 70 2,800 5,600
friendly user
interfaces
4 Database Models, designs, 2 weeks 1 80 70 2,800 5,600
designer and creates a
database system
5 Test engineer Ensures the 2 weeks 3 80 70 2,800 5,600
system meets the
6 System Define system 2 weeks 2 80 75 3,000 6,000
analyzer requirements
Total 120,400
2.4.2 Material / Equipment Financial Plan

 The following table shows the financial plan for materials and equipment (which are
mentioned above)
Table 1.4 material/equipment financial plan
Material/Equipment Quantity $/Unit
1 Laptops/PC/Mac 10 285,000
11
2 Hard Drive 2 6,000
3 Office 1 40,000
4 Office Telephone 5 4,000
5 Office Furniture’s 7 100,000

6 Office Car 2 1,500,000
7 Printer 2 14,000
8 A4 Paper 4 1,200
9 Wi-Fi Router 1 3,000
10 Mobile’s (Android and iPhone) 2 20,000
11 Small Fridge 1 15,000
12 Software Licenses 1 1,500
13 Server Costs - 4,000
14 Water filter 1 20,000
15 Lockers 2 120,000
16 Warehouse 1 20,000
Total 2,135,700
2.4.3 Project Budget

 The following table shows the total budget for our project
Table 1. 1 Project Budget
Human Resource total budget Material (Equipment) Total

total budget
120,400 2,135,700 2,256,100
12
2.5 Team Organization
We have organized our teams by their roles as shown in the following team organization chart.
Vehicle Service
Platform Project
Management Development
Stakeholders Analysis Team Design Team Test Team
Team Team
Project System Cross-platform UI/Ux Database

Sponsor Test Engineer
Manager Analysts Mobile App Designers Designer
Developers
Project System
Users Designer1 Designer1 Engineer1
Manager1 Analyst1
Developer 1
Designer2
Developer2
Developer3
Figure 2. 2 Team Organization
2.5.1 Conceptual Designers
 Whole Team
2.5.2 Research
● Yeab Andargachew
● Abubeker Misbah
● Leul Tsegahun
13
2.5.3 System and Database Designers
● Bereket G/Medhin (Lead software and database designer)
● Mai Tut Yoal
2.5.3UI Designers
● Bereket G/Medhin
2.5.4Document Writers
 Whole Team
2.6 Process Model

The process model that we are going to use throughout this project is the waterfall model. The
waterfall is a linear and sequential software development method.
Here are some of the reasons why we choose to use this model:
● Because our deliverables are easy to define at the start

● It helps us to determine the end goals early and work toward our goal without getting lost
● Our team has previous experience using this model so we don’t need new training to use
the model
● It’s simple to understand and use
● Because the project outline is sequential by itself, the waterfall model is the best option
2.7 Risk MMM Plan

To control the risks that might occur from the beginning to the end of the project process we will
first try to foresee all problems that might arise and plan a contingency plan.
14
2.7.1 Risk Items Table
Here we will see a table of all the risks
Table 2. 2 Risk item table
No. Risk type
1 Communication problem human/managerial
2 Employee exiting the facility problem human/managerial
3 Poor customer service Personal shortfalls
4 Inadequate resources Resource shortfalls
5 Unrealistic schedules in due dates and ques Managerial shortfalls
6 Transport and logistics failure Managerial shortfalls
7 Inadequate human resource Managerial shortfalls
8 The problem when a buyer abroad refuses to accept the

product
2.7.2 RMMM Plan

Table 2. 3 risk item plan sheet 1
No 1
Description Communication fails
Probability 10%
Impact High
Response Manage all communications
✔ Establishing a baseline for all communications

Mitigation
15
✔ Being consistent
✔ Proactively seeking feedback
Management
✔ Creating a safe place for the employees to communicate
Assigned Project Manager
16
No 2
Description Team members may leave the project
Probability 5%
Impact High
Response Manage the workforce
Mitigation
✔ Enforce documentation of everyone's work
✔ Reassign responsibility when needed
✔ Encourage members from time to time
Management
✔ Staffing with top talent, job matching, team building, morale
building, cross-training
Assigned Project Manager
No 3
Description When we fail to meet customer expectations
Probability 5%
Impact High
Response Double-check the product quality
Mitigation
✔ Establish a golden sample to set quality expectations
17
✔ Test products and inspect throughout the production
Management
✔ Set quality standards
✔ Review results, get feedback, and make improvements
Assigned Product Manager
No 4
Description Resource shortage
Probability 7%
Impact High
Response Being more proactive
Mitigation
✔ Decide what needs to be done first and make sure everyone
is on board.
Management Put modern process control systems in place to manage production in ways
that reduce or eliminate waste and ensure minimal use of scarce resources.
Assigned Project manager
No 5
Description Impossible deadline
Probability 5%
Impact High
18
Response Managing time
Mitigation
✔ Schedule risky activities earlier
✔ Reduce the number of critical paths
✔ Plan regular schedule reviews
Management
✔ Group meetings
✔ Using appointment slots
✔ A daily reminder of the deadline
No 6
Description Lose or damage of product on transit
Probability 5%
Impact High
Response delivering new products
Mitigation
✔ Getting insurance
✔ Using a transport agency which has the lowest product
damage rate
Management
Choose the Ideal Packaging Type and Size
19
No 7
Description Insufficient no of teams and members
Probability 5%
Impact Medium
Response
Mitigation
✔ Reuse available team members by reassigning them to other
positions
Management Assign team members in a rotating base by prioritizing the hardest task
first
No 8
Description The problem when a buyer abroad refuses to accept the product
Probability 5%
Impact High
Response Find a new buyer
Hire an agent in the company to find a new buyer
Mitigation Make sure that the company will not go back on its word Ensuring
the quality of the products is the same as promised
Management Producing a good quality product that meets international standards
20
21
Chapter Three - System Analysis
3.1 Introduction
In this chapter, our goal is to explain the system’s goals, and purposes and create procedures that
will efficiently achieve them. We will also try to address potential problems and their possible
solutions.
3.2 Current System Overview.
● Companies usually have insurance that will account for all transportation and storage
accidents.
● Coffee is first purchased from a representative of a farmers' group who brings the product
to a market where it is bid on. The buyers can be local businesses that plan on directly
using the coffee, coffee cleaners, traders, ECX, and/or exporters directly.
o Most of these representatives severely undercut the farmers on prices.
o If the coffee was purchased by cleaners, they bring it back to the market once
more after sanitizing it. Buyers who have a cleaning factory of their own may buy
dirty coffee straight from the market instead.
o If the coffee is bought by ECX they put it through an extensive grading process
that bumps up the price considerably. Buyers can instead hire a quality assurance
worker to manually assess the coffee from the Buna Board for a fee and grade it
themselves.
● Exporters consider many different types and attributes of coffee such as grade (ranging
from 1-4), acidity, and strength, before making a purchase. They do this to better find
what is in demand by their potential or current customers.
22
● After purchasing the coffee comes transportation to either exporting company’s cleaning
factory or the warehouse for storage. If the exporters bought already clean coffee, they
send it straight to storage.
● Once a buyer has been secured and a trade deal is finalized the coffee is taken to the
Djibouti border. Once border taxes and trade permits have been paid and verified, they
are taken to Djibouti’s docks to be shipped overseas.
● Depending on the trade agreement liability for the goods may end here at this stage or
will continue until the coffee reaches the destination port where the buyers verify the
product.
3.3 Proposed System Overview
It will be very similar to the current system but it has a few key changes.
● Our system will allow the option of directly purchasing coffee from individual farmers as
well as all the current avenues of purchase.
● Customers overseas will be able to purchase coffee virtually without any human
interaction outside of customer support.
3.3.1 Functional Requirements
● Inspect: - New farmers are evaluated by examiners who will physically go to the
plantation area and examine the soil, temperature, infrastructure, quality, type
altitude, and roads (accessibility) to the plantation area and sample the product to
determine whether it’s approved or not.
▪ If approved the site will calculate the total expenses needed to export the
product and a fair price with future gains to the farmers themselves and if
23
there is any improvement area it will suggest an improvement page for the
farmers to make an improved higher-grade coffee.
▪ If rejected the system will analyze the problem and suggest a better way of
improving the quality of the products
▪ It needs to automatically handle financial calculations and banking

transactions including everything from the initial purchase of the coffee,
cleaning, roasting, and packaging transactions if those options are chosen,
transportation and storage costs, tax, insurance, and border crossing fees, as
well as sea transport costs.
▪ If the user is a farmer providing us coffee directly the system needs to accept
new orders from those farmers that coffee is ready for pick up and processing
via simple text messages.
● Add product: - It includes the information of the products, grade, acidity, bitterness,
flavor, aroma, type, price, etc. it is also the admin where they can put the information
of the product on websites.
● Order: - The system allows the customers to order a product and provide a list of
orders that are made by the customers.
▪ A user can order a product for trial to evaluate the taste of the coffee and they
can also be subscribers who can get a constant amount of coffee delivered
every month.
▪ It needs to be able to handle interactions from multiple users.
● Stock report: - produces the list of products available and the status for each product
with detailed information about the product/coffee. The system needs to be able to
update, add, and remove available coffee on the store page.
24
▪ When the store page is updated, it needs to include information on the
attributes of the coffee available such as:
▪ Quality (Grade)
▪ Quantity (In Kilos)
▪ Price
● Cart: - Allows the user to buy different types of coffees once done with browsing
instead of buying them one at a time which is inefficient and time taking but also the
customer gets distracted or forgets to get all of what they came here for to get. Users
can also make changes to the carts like
▪ Choosing different types of coffee to purchase in varying amounts.
▪ Update the cart to increase/decrease the amount of coffee they need in total.
▪ Remove a product from the cart
● Sign up: - The system allows users to store their credentials to gain the services.
▪ There will be 2 logging pages, one for the user, and the other for the company
▪ There will be online user documentation and feedback sessions.
● Sign in: - The system allows users to login into their accounts by using their phone
number and email.
▪ For the farmers who want to work with us, they have to provide the following
information.
▪ Full name, gender, DOB, location (where the plantation is located currently),
ID image, the amount they want to sell the coffee to as, the amount of coffee
they produce in a year, and phone number.
25
● Search and filtering: - The system allows users to search products by name or just
filter by highest rating, quality, favorite, price location, and altitude.
● Reporting/Receipt: - After ordering a product or a subscription the system will send

one copy of the bill to the customer and another one for the system database. The
system needs to be able to provide reports on the different stages of the process and it
needs to be able to document everything properly in the appropriate database.
● Logout: - After ordering and surfing the site for products the user has to log out.
3.3.2 Non-Functional Requirements
● Security: -The system needs a security system in place with features like
o Authentication of the user whenever they log into the system.

o System shutdown in case of a cyber-attack.
● Performance: - there will not be any ambiguous data being fetched to the site to
make it faster to organize and integrate the data entered. Guarantee the safety of the
crucial data kept in the databases by:
o Frequently backing up system is placed by both hard copies of the documents
and stored in a secure location.
o By uploading it to their databases. And through these simple steps, we can
potentially alleviate coming disasters massively and quickly recuperate to
reopen as fast as possible.
o There should be immediate updates when we change things in the database or
when a user switches between web pages with a max delay of 5 seconds.
o The transaction in the system will be fast and safe.
● Reliable: - To satisfy our customers’ needs we start by hiring the best people and
training them to a high standard and then we will invest in the most reliable tools in
the market for the job at hand and as a company Mato we will never promise more
26
then we can deliver and always deliver on the promised(agreed) upon the contract as
efficient as possible to earn our customers up most trust.
o Availability The system will be available almost for 24 hours except for some
failure, maintenance access, and degraded mode operations.
o MTBF (mean time between failures): according to the type of failure it could
take from an hour to a month
● Usability: - The site will be easily understood by an English speaker and be used by
anyone who wants to start a coffee importing and exporting business.

o The system we are going to build is so easy that we expect a minimized
training time for the normal user
o Specify requirements to conform to common usability standards
● Availability: - The site will be available from any device with an Internet connection
and browser at any time and anywhere.
3.4 System Models - Requirement Determination
3.4.1 Essential Use Case Modeling
Essential use cases are typically written in two-column formats of a simplified, abstract,
generalized use case that capture the intentions of the user in a technological and
implementation-independent manner column on the left indicates the intention of the
user, and the column on the right the system’s responsibility to respond.
Table 3.1 Essential Use Case Modeling
User Intention System Responsibility
User identifies Verifies eligibility to use the system
Browse Web Site Display appropriate Web page and links
Shop and add to the cart Provide an interface for adding items to the user’s cart in whateve
27
quantity is allowed and calculate the total cost of the items.
Purchase items in the car Offer the user appropriate payment methods and finalize purchas
then store purchase data in the database.
Register new client(farmers) Enroll new farmers who meet the standards.
28
3.4.1.1 Use Case Diagram
Figure 3. 1 Use Case Diagram
29
3.4.1.2 Use Case Documentation
● The Farmer accesses the system to log in, give an update on the
availability of their crop, and be notified of their payment.
● The customer accesses the system to log in, browse the coffee we have
available for purchase, or put in an order and purchase the coffee they
want in the quantity they want it in.
● The company workers are the ones who primarily manage the quality
verification. They have access to certain databases in the system and can
update information on them such as the attributes of different batches of
coffee. They are the ones who update the store page with events. They are
also partially responsible for system maintenance
● The System Admin is the one who owns the system and has full access to
the database and can alter access rights. They can add and remove users
and alter their access level. They are also partially responsible for system
maintenance.
3.4.2 Essential UI Prototype
● Prototyping is a development approach used to improve the planning and

execution of software projects by developing executable software systems
(prototypes) for experimental purposes [4]. It is suitable for gaining experience in
new application areas and supporting incremental or evolutionary software
development. user interface prototyping is a testing and evaluation approach that
is a crucial component of the User-Centered Design (UCD) methodology, widely
used in IT projects since the 1990s [Sharp, 2005].
Figure 3. 2 Essential UI prototype
30
3.4.3 User Interface Flow Diagram
31
Figure 3. 3 User Interface Flow Diagram
3.4.4 Supplementary Specifications
Provide an overview of the design constraints, business rules, resources in use, and change case,
and also capture the system requirements that are not readily captured in the use cases of the use-
case model.
3.4.4.1 Business Rules
● Business rule: is a set of directives designed for a software project to achieve its
goals, they set up rules and guidelines on how work will be conducted to ensure
compliance throughout the system. Business rules apply to users, general corporative
individuals or officers, and admins.
Table 3. 1 Users have to be logged in before performing some actions BR
ID BR01
Name Users have to be logged in before performing the following actions
Description  checkout
 view profile
 edit profile
Table 3. 2 Farmers have to be registered in the system before inspecting the products.
ID BR02
Name Farmer has to register at our services to get:
Description  Their coffee was inspected and graded.

 Export their coffee with fair pay and learn how to improve the quality of
the coffee they produce.
32
Table 3. 3 The payment must be performed by Letter of Credit method(L/C).
ID BR03
Name The payment must be performed by Letter of Credit method(L/C).
Description  To ensure that customers are going to pay for the products that they will
receive they must pay using the Letter of Credit method (L/C).
 The transaction should only pass through the system we have lined
Table 3. 4 The Products in the system should be licensed.
ID BR04
Name Products in the system should be licensed.
Description  The quality will be tested by inspection officers that will go to the site
and report back to ensure international quality coffee.
 The officer will educate the farmers at the plantation site on how to
grow better-quality coffee.
 The quality of the product going through our system will only be
standardized by the authority of the system owner
3.4.4.2 Constraints
Constraints are limitations of what the system is expected to accomplish in terms of quality and
delivery and overall project success. So, to succeed we have to find the optimal point between
the many constraints that we have, such as cost, quality, time, scope, risk, and customer
satisfaction. We need to manage them separately and integrate them.
33
I. Cost
Cost is a very important constraint because it gives of what is financially
required to start the project and the sponsors can give a remark and
improve the cost to their going price and the price, we settled with will be
our project constraint and should complete the project with our said budge
II. Quality
This and cost go hand in hand. The more money we spent on educating the
farmers the better quality they will produce and this will affect our project
budget in other areas like shipping, transportation, and more. Also, if we
have lots of orders at a given time this will affect our quality as well.
III. Time
When we start the project there are deadlines to be met and deliveries and
a fully booked Wearhouse that are effectively eating at our budget so we
must be strict at following schedules thus time is a constraint that we need
to give attention to the most.
IV. Scope
The scope is everything that our project needs to accomplish thus it is very
important to get a clear idea of what we include in the scope and the ones
that we reserve for the future because the scope is very wide and difficult
to cover everything at our level.
V. Risk
Risks can be either positive or negative in a project. Project managers
must enhance the opportunities for positive risks and reduce the threats of
negative risks in a project. There are risk mitigators with normal risks such
as an employee leaving the company they should inform us before leaving
and work for an extra couple of days, the transport vehicles are not
working then we should hire a truck transport company to fill in for the
time our vehicles are repaired and if the transactions are not paid before
the product is shipped then the order should be canceled. In general, risk is
a very crucial constraint that will help us from sinking and keep us afloat.
VI. Customer satisfaction
34
This is a key factor for a sustainable and long-running business in the
market. A dissatisfied customer can paint a bad image for the company
and because we have many competitors who have been in the coffee
exporting business, we need to start by having a checkered customer
service. Because a satisfied customer will continue to buy from you and
refer other customers and in general be a superstar advocate for our
business, Customer service shouldn’t just be a department it should be the
entire company and those who get dissatisfied are our biggest learning
sources.
3.4.4.3 Change Case

A change case is used to define new requirements for a system or to modify the existing
requirements of a system. Software needs to be maintained and changed to satisfy the new
requirement and existing faults.
Without analyzed changes, change implemented to software often cause unexpected ripple
effects to avoid this and diminish the risk of performing undesirable changes, an impact analysis
of the change is done. Here are some of the change cases.
▪ Need to support extra systems
o This is a common occurrence because most people would rather use

applications to use.
o But it is still not known how impactful it will be on our total business,
maybe in the future, we will design and add an application to increase
the number of users.
▪ Need to support large databases
o Very probable to happen, as we grow and many users start using our
system, we will be required to increase the database size to
accommodate all the transaction information and other data.
35
o More customer means more budget sent to satisfy the customers that
need fast browsing time and more resources to work on the incoming
orders.
▪ Need to support a large number of customers
o Depending on the time and the reach of our advertisements we believe

that we will get more and more people to become our customers.
o Large customers will be able to register to buy our product and larger
farmers can register to sell their products.
o Additional costs, time, and resources are needed to accommodate the
new large number of customers.
36
3.5 System Models - Analysis
3.5.1 System Use Case Modeling
3.5.1.1 Use Case Diagram
Figure 3. 4 System Use Case Diagram
3.5.1.2 Use Case Documentation

Table 3. 5 Log in
37
1 User case name Log in
2 Trigger Signing in to an account
3 Precondition The user must already have an account on the website
4 Postcondition Use the website fully
5 Use Case Id UC01
6 Actor User/Admin
7 Basic Flow 1. The user enters their email address and password on UI02.
2. The system checks whether the password and email match and
are in the DB based on business rule BR01.
3. The system will match the password and email from the DB
and display the home page on UI03.
8 Alternative Flow 1. If the password or email is not correct, the system will send a
message to indicate the wrong password/email based on
business rule BR01.
2. Navigates to UI02 to let the user reenter their password.
3. The use case ends.
Table 3. 6 Log out
1 User case name Log out

2 Trigger Signing out of an account
3 Precondition The user must already be in the system with an account
4 Postcondition Close session to logout
5 Use Case Id UC02
6 Actor User/Admin
7 Basic Flow 1. User/Admin chooses to leave the system by pressing the log
out button on UI03 for users or UI14 for admins.
2. The system deletes sessions and activates the security system
to keep intruders away.
Table 3. 7 Create account
1 User case name Signup

2 Trigger Register a new user
3 Precondition New user
4 Postcondition A new account will be created for the user
5 Use Case Id UC03
6 Actor User/Admin
7 Basic Flow 1. The user inputs their full name, phone number, email, country,
city, state, gender, and password into the System on UI01.
2. The system saves data on the DB and creates an account for
38
the users.
3. redirects them to the login page on UI02.
8 Alternative Flow If it is a new Admin.
1. Admin creates an account for new admin by filling a form on
UI25 and proceeds to enter the data into the database.
2. The system saves data on the DB and creates an account for
the users.
Table 3. 8 View product
1 User case name Categories

2 Trigger Browse available products
3 Precondition None
4 Postcondition I. Users can add a product to the cart.
II. Users can buy a product.
III. Users can order a checkout product.
IV. Admin can edit a product.
5 Use Case Id UC04
6 Actor User/Admin
7 Basic Flow 1. The user opens the website home page on UI03.
2. The user chooses to see all products by clicking on a button
called “enjoy now” or” compare”.
3. The system displays all available products on UI04.
8 Alternative Flow Admin wants to see the current products.
1. Admin selects products icon on UI14.
2. The system displays the current products in the system on
UI19.
Table 3. 9 Add to cart
1 User case name Add to cart

2 Trigger User add a product to the cart
3 Precondition None
4 Postcondition The user adds a product to the cart
5 Use Case Id UC05
6 Actor User
7 Basic Flow 1. The user chooses a product to see the details from the
categories page on UI04.
2. The system displays the details of the product that the user
clicked on screen UI05.
3. The user adds the product to the cart by clicking “add to cart”
on page UI05.
4. The user can view the total products in the cart on page UI06.
39
8 Alternative Flow If the product is already in the cart
1. The system notifies that the product is already in the cart.
2. Use case ends
Table 3. 10 Search Products
1 User case name Search

2 Trigger Search available products
3 Precondition None
4 Postcondition Matching search results are displayed.
5 Use Case Id UC06
6 Actor User
7 Basic Flow 1. User types in the name or type of coffee into the search bar on
screen UI03.
2. The system searches for matching results and fetches them
from the DB table.
3. The system then displays total matching results on screen
UI07.
8 Alternative Flow If there are no matching results on the current products in the DB.
1. The system displays a message to the user that there is no
matching search result on UI07.
Table 3. 11 View Products details
1 User case name products

2 Trigger Products details
3 Precondition None
4 Postcondition Product details are displayed.
5 Use Case Id UC07
6 Actor User
7 Basic Flow 1. The user clicks on a product on UI04.
2. The system displays the product details on UI05.
Table 3. 12 Checkout product
1 User case name Checkout

2 Trigger Checkout products
3 Precondition 1. There must be a product in the cart to checkout.
2. The user must be signed in to their account to checkout.
4 Postcondition Order a Product
40
5 Use Case Id UC08
6 Actor User
7 Basic Flow 1. The user checks out the product currently in the cart shown on
page UI06.
2. The system displays the checkout page on UI08.
3. The user enters more information about the amount and type
of transportation they are interested in using and the user
clicks on place order on UI08.
4. The system saves an order on the DB and displays it on the
order page on UI16.
5. The system displays a confirmation popup message for the
user on page UI28.
8 Alternative Flow If the user is not signed in with an account:
1. The system checks whether the user is signed in with an
account based on business rule BR01.
2. The system displays a message to let the user sign in before
checking out a product on UI08.
3. The user navigates to the login page UI02 and the user logs in
with an account.
4. The user clicks on the icon cart on the header of the home
page on UI03.
5. The system fetches the product that is in the cart and displays
it on the checkout page on UI08.
6. The user continues to fill in the required information on the
displayed form and click place order on UI08.
7. The system saves the data on the DB and displays it on the
order page for admin on UI16 and displays a confirmation
popup message for the user on page UI28.
Table 3. 13 Inspect product
1 User case name Inspect product

2 Trigger Officer inspects the quality of a product.
3 Precondition The product must pass the inspection test.
4 Postcondition Product is approved or Product fails quality standard.
5 Use Case Id UC09
6 Actor Admin
7 Basic Flow 1. A farmer must be registered in the system to have their
products inspected and graded based on business rule BR02
2. Admin contacts farmers to schedule an inspection date by
using the farmer's contact information displayed on the UI21.
3. The inspection officer goes to the location and examines the
plantations.
41
4. Returns and reports on the product condition, quality, and
roads leading to the site plus other attributes of the coffee, and
location itself on the UI22 inspection page.
5. The system calculates the grade and total expenses on UI23.
6. Admin grants or denies the product quality on UI23.
8 Alternative Flow 1 If the system doesn’t approve the product:
1. The system declines the product on UI22 due to having a low
grade.
2. The system determines the problem and informs the inspector
to instruct the farmers on how to grow a better-quality coffee
3. Inspector goes to the plantation site and instructs the farmers
4. Farmer accepts and implements instruction
5. Informs the inspection when good crops are grown. Inspector
examines the product again
9 Alternative Flow 2 If the Admin doesn’t approve of the product:
1. Admin declines the product due to transport storage and other
expenses on UI23.
2. The system deletes the farmer's information and product
detail.
Table 3. 14 View profile
1 User case name View Profile

2 Trigger Profile
3 Precondition The user must already be logged in to an account
4 Postcondition Profiles confirmation
5 Use Case Id UC10
6 Actor User
7 Basic Flow 1. User signs into their account on UI02.
2. User clicks on the settings icon on the header and profile on
UI03.
3. System fetches user profiles from the database.
4. User views profile on UI09.
8 Alternative Flow If user wants to change information on the profile:
1. User clicks on edit profile on the UI09 page.
2. System displays the edit profile page UI10.
3. User enters new information and saves it.
4. System updates the new data in the DB table.
5. Use case ends.
42
Table 3. 15 Contact us
1 User case name Contact us

2 Trigger User contact customer services
3 Precondition None
4 Postcondition The message is sent to the admin officers
5 Use Case Id UC11
6 Actor User
7 Basic Flow 1. User logs into the system and has a question to ask about the
overall operation of the site on UI02.
2. User clicks on the contact us links on UI03.
3. System display contact us page with an input form for name,
email, subject, and description on UI13
4. The user writes his/her questions or complaint and sends a
message
5. System saves to database and fetches to the officer on page
UI24.
6. Use case ends.
Table 3. 16 About us
1 User case name About us

2 Trigger About us services
3 Precondition None
4 Postcondition About us page
5 Use Case Id UC12
6 Actor User
7 Basic Flow 1. User logs into the system and have question on the overall
operation of the site on UI02.
2. User click on the about us link on UI03.
3. System display about us page with input form for name,
email, subject and description on UI12.
4. Use case ends.
Table 3. 17 Terms and conditions
1 User case name Terms and conditions

2 Trigger Terms and conditions
3 Precondition None
43
4 Postcondition Terms and conditions
5 Use Case Id UC13
6 Actor User
7 Basic Flow 1. User clicks on Terms and conditions on page UI03.
2. System displays the Terms and conditions on the system on
UI11.
3. Use case ends.
Table 3. 18 Register new farmer
1 User case name Farmer Sign up

2 Trigger Register a new farmer
3 Precondition New farmer
4 Postcondition A new account will be created for the farmer
5 Use Case Id UC14
6 Actor Admin
7 Basic Flow 1. Farmer contacts the admin via phone call.
2. The admin takes simple contact information and the location
of the farmer and plantation.
3. Admin takes the farmer's information and enters it into the
system on page UI18.
4. The system saves the data under newly registered farmers and
in due of inspection for products.
5. Use case ends.
Table 3.20 Total Clients
1 User case name Clients

2 Trigger Customers
3 Precondition None
4 Postcondition View all current clients.
5 Use Case Id UC15
6 Actor Admin
7 Basic Flow 1. Admin signs in with the account on page UI02.
2. The system displays the admin page and clicks on the
“customers” icon on UI14.
3. The system displays the total current clients registered in the
system on UI17.
4. Use case ends.
8 Alternative Flow If the admin fails to sign up/login
1. Return to sign up/login interface.
2. Use case ends.
44
Table 3. 19 Customs Inspection.
1 User case name Customs

2 Trigger Display Order
3 Precondition Client orders a product.
4 Postcondition All customs documentation for export is generated by the system
automatically.
5 Use Case Id UC16
6 Actor Admin
7 Basic Flow 1. The system displays the orders of clients on the order page
UI16 and the admin clicks on display.
2. The system displays all the customs documentation on
customs page UI17.
3. Admin prints the compiled documents UI017 and send them
to the bank of the client’s desire.
Table 3. 20 Add Products
1 User case name Add products

2 Trigger Add products
3 Precondition The product needs to be approved by the inspectors.
4 Postcondition Add a Product to the DB
5 Use Case Id UC17
6 Actor Admin
7 Basic Flow 1. Admin signs in with the account on page UI02 and adds a
product that is inspected by the system based on the business
rule BR04.
2. The system displays the admin page and the admin clicks on
the “Add products” icon on UI14.
3. The system displays the Add product form page on UI26 and
the admin enters the product information on the page and
clicks on the “add product” button.
4. The system adds a product into the DB and displays it on
UI04 for users to order.
8 Alternative Flow If the product entered has a mistake.
1. Admin clicks on products icon on UI014 of the admin page.
2. And selects the product with error and clicks on display on
page UI19.
3. The system displays the details of the selected product and a
form to reenter the product on the edit product page on the
UI20.
4. Admin reenters the products on the UI20 page and submits the
product.
5. The system updates the product based on the newly entered
detailed information.
45
6. The system displays it on UI04 for users to order.
7. Use case ends.
3.5.2 Sequence Diagram
Figure 3. 5 Add Product Sequence Diagram
46
Figure 3. 6 Checkout Sequence Diagram
Figure 3. 7 Create Account Sequence Diagram
47
Figure 3. 8 Profile Page Sequence Diagram
Figure 3. 9 Logout Sequence Diagram
48
Figure 3. 10 Register New Farmer Sequence Diagram
Figure 3. 11 Contact Us Sequence Diagram
49
Figure 3. 12 Login Sequence Diagram
Figure 3. 13 View product Sequence Diagram
50
Figure 3.9 Search Product Sequence Diagram
Figure 3.10 Inspect Farmer Product Sequence Diagram
51
Figure 3.12 Add to Cart Sequence Diagram
52
Figure 3.9 Customs Inspection Sequence Diagram
53
Activity Diagram
Figure 3. 14 Login Activity Diagram
54
Figure 3. 15 Create Account Activity Diagram
55
Figure 3. 16 Logout Activity Diagram
Figure 3. 17 View Profile Activity Diagram
56
Figure 3. 18 Contact us Activity Diagram
Figure 3. 19 Add Product Activity Diagram
57
Figure 3. 20 Checkout Activity Diagram
Figure 3. 21 View Product Activity Diagram
58
Figure 3. 22 Add Farmer Activity Diagram
59
Figure 3. 23 Add to Cart Activity Diagram
Figure 3. 24 Inspect Product Activity Diagram
60
61
Figure 3. 25 Search Activity Diagram
Figure 3. 26 View Product Details Activity Diagram
62
Figure 3. 27 About us Activity Diagram
Figure 3. 28 terms and conditions Activity Diagram
Figure 3. 29 View Current Clients Activity Diagram
63
Figure 3. 30 Customs inspection Activity Diagram
64
Chapter Four - System Design
4.1 Introduction
The system design is the process where a programmer designs a plan to be followed in
satisfying the need of customers, with the construction of what is termed as “the physical model”
of the software. It defines the architecture or the structure of the software interns of a hierarchy
of software components or modules and data structures.
This is the software development stage and it is based on the user requirements and the detailed
analysis of a system that was analyzed from the system analysis. The purpose of this system
design is to create a technical solution that satisfies the functional requirements for a coffee
exporting system.
Several alternative designs could be proposed, one of which is selected for further refinement
and detailed design. The construction of possible designs and the selection between them should
be governed by the set of software design criteria described in the following section. Technically
difficult or critical parts of the design should be identified, and prototypes could be built to
analyze the validity of the design assumptions used.
The deliverables produced in this chapter are the design goals, the tradeoffs of the design that we
are going to develop, decomposing the subsystems, designing the phase models which is
modeling the classes, and the persistent which is mapping class diagram with relation and
normalization, and designed user interface, deployment diagrams and the design of the network
of the vehicle service platform.
65
4.2 Design Goals
The system we design should be easy to understand and use. Therefore major design goals for
our system are:
● Performance: Our system must be able to handle all requests from users such as logging
in, searching, and updating information, immediately.
● Dependability: it must be able to properly respond to invalid user input by displaying
appropriate error messages. It will also be reliable as it will only deliver related results as
requested by users.
● Cost: the system can be initialized with a low cost, since the system is simple to
understand installation and training costs are also low. And also the system is not that
much complicated it will cost small to administer.
● Maintenance: our system also must have an understandable code that allows as to add
new functionalities ,modifications and adaptation to different application domains.
● End-user : it ease the energy and time wasted searching for good quality product
4.3 Design Tradeoffs
Design trade-off strategies are always present in the design process. While designing our system
we went through multiple alternative ideas, and solutions and it can be difficult to decide which
was vital to select and which were unnecessary or expandable.
To reach a decision we looked at the design trade of methods. In a project, the three most
common metrics are time, scope, and cost. We needed to negotiate on these metrics. Tradeoffs
also depend on priorities. it may be done to attain the system goal, sometimes for technical
limitations, sometimes to put user needs above others.
And there are some tradeoffs that we considered to be happening in our system.
66
● Space vs Speed: we prioritize the roll of space on of speed because at the end we need
more storage to store the databases we collect but we also will make the system
interactive and fast for use as possible.
● Security vs Ease of use: since our system involves payment systems we prioritize
security over ease of use so a user may go though many validation and verification steps.
● Flexibility vs simplicity: the task that our system can perform is known so we need our
system to be simple than it need to be flexible.
● Functionality vs aesthetics: we don’t need our system to be gold platted so indeed of the
system outer view, we wanted the system to function as it supposed to.
4.4 Subsystem Decomposition

Subsystem decomposition is the process of decomposing the system into smaller subsystems in
order to easily understand the design and maintain the system. A Subsystem is collection of
classes, associations, operations, events and constraints that are closely interrelated with each
other. The objects and classes from the object model are the “seeds” for the subsystems. In UML
subsystems are modeled as packages
The document management system under consideration is decomposed into subsystems. The
diagram below shows a connection between different system components.[ Object Using UML,
Patterns, and Java -Oriented Software Engineering]
67
Figure 4. 1 Subsystem decomposition
68
4.5 Design Phase Models
4.5.1 Class Modelling
Figure 4. 2 Class modeling diagram
69
4.5.2 Persistent Model
4.5.2.1 Mapping Class Diagram to Relation
Figure 4. 3 Mapping class diagram to relation
70
4.5.2.2 Normalization
Here we will be explaining how many tables there are and how to normalize them,
showing all first form, second form, and third form with written steps. The following are
the tables in their normalized forms
❖ Client Table
Table 4. 1 Client table
Client_i Fullname Gende Email Password Address Phone

d r
1 Bereket M bereket@gamil.com 123 Ethiopia, Addis 0923516232,

G/medhin Ababa
0923414141
2 Melat T/wold F melat@gmail.com 789 Punjab, India 91923516232
First normal form
To change this to a first normal form we need to:
1. There should not be a duplicate of rows

2. Each cell contains one value (each attribute contains atomic values).
3. Columns contain values of the same type.
4. Each column contains have a unique name
5. There should not be a top to down ordering of rows and no left-to-right ordering of
columns
71
Table 4. 2 Client first normal form table
Client_id Fullname Gender Email Password Countr City Phone

y
1 Bereket M bereket@gamil.com 123 Ethiopia Addis 0923516232

G/medhin Ababa
1 Bereket M bereket@gamil.com 123 Ethiopia Addis 0923414141

G/medhin Ababa
2 Melat F melat@gmail.com 789 Punjab India 91923516232

T/wold
The second normal form
This table is in the second normal form because:
1. It is in its first normal form

2. There are no partial dependency present in the relationship. All non-prime
attributes are fully functionally dependent on the candidate’s key
The third normal form
This table is in the third normal form because:
1. It is in second normal form.

2. There are no transitive dependency present in the relationship. All fields are determined
by the primary key, not by other keys.
This is the final normalized client’s table with attributes, datatype, field size, and
constraints
Table 4. 3 Client final normalization table
72
Attribute Datatype Field text Constraints Null or Not Default value
Name Null
Client_id Char 11 - Not Null -
Fullname Varchar 25 - Not Null -
Email Varchar 255 - Not Null -
Password Varchar 255 - Not Null -
Country Varchar 255 - Not Null Saudi Arabia
Phone Int - Not Null -

number
city Varchar 255 - Not Null -
Gender Varchar 1 - Not Null -
Product_id Char 11 - Null -
❖ Product table
Table 4. 4 product table
buna_id bunatype properties location Image Price Order_id Order_date
1 Arabica Soft, Jimma, Arabicaimg.jpg 150 3 7/07/2014

highly 2000ft
acidic, and
bitter
2 Yergachefe Hard, Jimma, Yergachefeimg.jp 200 4 13/07/2014

medium 1400ft g
acidic,
bitter,
73
First normal form
Table 4. 5 product first normal form table
Buna_id type Softness Acidic Bitterness Location Altitude Image Price Order_id Order_date
1 Arabica Soft highly bitter Jimma 2000ft Arabica.jpg 150 3 7/07/2014

acidic
2 Yergachefe Hard medium bitter Jimma 1400ft Yergachefe.jpg 200 4 13/07/2014

acidic
The first normal form is done because
● each cell has a single value and
● Columns contain values of the same type.
Second normal form
Table 4. 6 product second normal form table
Buna_id type Softness Acidic Bitterness Location Altitude Image Price Order_id
1 Arabica Soft highly acidic bitter Jimma 2000ft Arabica.jpg 150 3
2 Yergach Hard medium bitter Jimma 1400ft Yergachefe.jp 200 4

efe acidic g
Table 4. 7 product second normal form table
Order_id Order_date
3 7/07/2014
4 13/07/2014
The second normal form is done because
74
● It is in first normal form and
● There is no partial dependency
The third normal form is done because
● It is in second normal form
● There is no transitive dependency and
● Each cell depends on the primary key.
This is the final normalized Products table with attributes, datatype, field size, and
constraints
75
Table 4. 8 product normalized table

Name Null
product_id Char 11 - Not Null -
pname Varchar 25 - Not Null Arabica
Body Varchar 255 - Not Null medium
Acidity Varchar 255 - Not Null -
Bitterness Varchar 255 - Not Null -
Softness varchar 255 - Not Null -
Roast Varchar 255 - Not Null Medium roast
Aroma Varchar 255 - Not Null -
flavor varchar 255 - Not Null -
Viscosity Varchar 255 - Not Null 27.4810
Location varchar 255 - Not Null -
Altitude Int - - Not Null -
Image Text - Not Null -
Price Currency - - Not Null -
Order_id Char 11 - Null -
76
❖ Order table
Table 4. 9 order table first normal form
Order_id Order_name Date Authorized Amount Pay_id
1 Subway 7/07/2014 Admin01 $2000 3
2 netflex 13/07/2014 Admin02 $1500 4
This table satisfies all three normalization forms:
First normal form:
● each cell has a single value and
● Each cell contains one value (each attribute contains atomic values).
Second normal form:
Third normal form:
This is the final normalized orders table with attributes, datatype, field size, and
constraints
77
Table 4. 10 order final normalized form

Name Null
Order_id Char 11 - Not Null -
Order_name Varchar 25 - Not Null -
Date Date/time - - Not Null -
Authorized Varchar 255 - Not Null -
Amount currency - - Not Null -
Pay_id Char 11 - Null -
This is the final normalized delivery table with attributes, datatype, field size, and
constraints
Table 4. 11 delivery final normalized form

Name Null
delivery_id Char 11 - Not Null -
Dname Varchar 25 - Not Null Arabica
Pname Varchar 255 - Not Null
Date Date/Time 255 - Not Null -
Country Varchar 255 - Not Null -
City varchar 255 - Not Null -
Quantity int - - Not Null -
Client_id Char 11 - Null -
78
❖ Farmer table
Table 4. 12 farmer table
Farmer_id Fullname Gender Age Address Price Phone Admin
1 Nati M 30 Jimma,06 80 0923223344 3

mulugeta ,
2 Mekdes F 41 Oromia 70 0976347876 4

Abebe bale, 5 ,
0987654323
First normal form
✔ No duplicates
✔ Unique name
✔ Columns contain same type
Table 4. 13 farmer first normal form table
Farmer_id Fullname Gender Age Location woreda Price Phone Admin
1 Nati M 30 Jimma 06 80 0923223344 3

mulugeta ,
2 Mekdes F 41 Oromia 05 70 0976347876 4

Abebe bale ,
79
2 Mekdes F 41 Oromia 05 70 0987654323 4
Abebe bale
Second normal form
✔ Is in the first normal form
✔ Removing partial dependency
Table 4. 14 farmer second normal form table
Farmer_id Fullname Gender Age Location woreda Price Phone Admin
1 Nati M 30 Jimma 06 80 0923223344 3

mulugeta ,
2 Mekdes F 41 Oromia 05 70 0976347876 4

Abebe bale ,
2 Mekdes F 41 Oromia 05 70 0987654323 4

Abebe bale
80
Table 4. 15 farmer second normal form table
Admin Name
3 Adan oroale
4 Amare mokale
Third normal form
✔ Is in the second normal form
✔ No transitive dependency
❖ Admin table
Table 4. 16 admin table
Admin_id Fullname Username Password Gender Email Phone
1 Adan Adaneor 123 M Adan@gmail.com 0978567823

oroale
2 Amare Amare 456 M amare@gamil.com. 09567890

mokale
Amare@mukblack.com
First normal form
✔ No duplicates
✔ Unique name
81
✔ Columns contain same type
82
Table 4. 17 admin first normal form table
Admin_id Fullname Username Password Gender Email Phone
1 Adan Adaneor 123 M Adan@gmail.com 0978567823

oroale
2 Amare Amare 456 M amare@gamil.com. 0956789023

mokale
2 Amare Amare 456 M 0934567823

mokale
Amare@mukblack.com
This table satisfies the second and third normal form
Second normal form:
Third normal form:
83
4.5.3 User Interface Design
84
85
86
87
88
89
90
91
92
Figure 4. 4 UI Design
93
4.5.4. Deployment Diagram
Figure 4. 5 Deployment Diagram
4.5.4 Network Diagram
Figure 4. 6 Network Diagram
94
Chapter Five - Implementation
5.1 Introduction
Our main goal is to set out in some detail the proposals and measures that will be implemented
over the next years in order to achieve the goals outlined in the previous chapters.
The research done by Infomineo about agriculture in Ethiopia shows that there is over 51 million
hectares of arable land, land that can feed many people but only 20% of that land is use and, 50%
of those are owned and used by small farmers which rarely produce high quality crops and
mostly sold and used by residents. This are 12 million householder who are currently leading
there lives this way holding 95% of the total agriculture GPD. Agricultural production is mainly
subsistence, and a large portion of the country’s commodity exports is provided by the small
agricultural cash-crop sector.[1]
Ethiopia has a great potential for coffee production, thanks to the country’s abundant rainfall,
optimum temperatures, conducive altitude and fertile soil. Over 60% of Ethiopian coffee is
produced as forest coffee, and therefore the use of fertilizers is usually unnecessary as the falling
leaves enrich forest floor. Also, the use of chemicals such as pesticides, fungicides among others
is limited since the high genetic diversity in the forest creates a balance between parasites and
pests [2]
so, we have the farmers who are capable of producing high quality coffee land to produce them
in and the perfect environment but are poorly rewarded in the overall schema of coffee trading.
Our system will allow to directly benefit the farmer to export their products, the exporters to
spend little expenses as possible without having connections outside the country and it will
greatly help Ethiopia with foreign exchange and currency.
5.2 Sample Code

Register a new user php code
<?php
if(isset($_POST['save'])){
include 'includes/connect.php';
$fname = $_POST['fname'];
$id_no = $_POST['id_no'];
95
$gender = $_POST['gender'];
$email = $_POST['email'];
$country = $_POST['country'];
$phone = $_POST['phone'];
$location = $_POST['location'];
$qry = "INSERT INTO client (fname,id_no,gender,email,country,phone,location,status)
VALUES('$fname','$id_no','$gender','$email','$country','$phone','$location','Available')";
$result = $conn->query($qry);
if($result == TRUE){
echo "<script type = \"text/javascript\">
alert(\"Successfully Registered.\");
window.location = (\"login.php\")
</script>";
} else{
alert(\"Registration Failed. Try Again\");
window.location = (\"signup.php\")
</script>";
Loin in php code

<?php
if(isset($_POST['log'])){
include 'includes/config.php';
$uname = $_POST['email'];
$pass = $_POST['pass'];
$qy = "SELECT * FROM client WHERE email = '$uname'
96
AND id_no = '$pass'";
$log = $conn->query($qy);
$num = $log->num_rows;
$row = $log->fetch_assoc();
if($num > 0){
session_start();
$_SESSION['email'] = $row['email'];
$_SESSION['pass'] = $row['id_no'];
alert(\"Login Successful.\");
window.location = (\"index.php\")
</script>";
} else{
alert(\"Login Failed. Try Again\");
window.location = (\"signinn.php\")
</script>";
}
}
?>
Connect to the database php code

<?php
$host = "localhost";
$user = "root";
$pass = "";
$db = "coffee";
97
$conn = new mysqli($host, $user, $pass, $db);
if($conn->connect_error){
echo "Failed:" . $conn->connect_error;
}
?>
Cart clear php code
<?php
session_start();
if (isset($_SESSION['cart'])) {
unset($_SESSION['cart']);
echo "<script>
alert('Cart Cleared');
window.location.href='../catagories.php';
</script>";
} else {
header('location: cart.php');
}
Categories php code
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="Styles/catagories.css">
<link rel="stylesheet" href="Styles/list.css">
<link rel="stylesheet" href="Styles/index.css">
<link rel="stylesheet" href="images/material-icons-main/iconfont/material-icons.css">
<title>Document</title>
98
</head>
<body>
<?php
include("attach/header.php")
?>
<h1 class="title"> MARKETPLACE</h1>
<div class="coffee_img" style="display: block;height:400px">
<img style="width: 100%;height:400px; object-fit:cover;margin-left200px;"
src="images/coffee_categorie.jpg">
</div>
<h2 class="title">Featured Prodcuts</h2>
<section class="listings">
<div class="wrapper">
<ul class="properties_list">
<?php
include 'includes/connect.php';
$sel = "SELECT * FROM buna";
$rs = $conn->query($sel);
while($rws = $rs->fetch_assoc()){
?>
<li>
<a href="product.php?id=<?php echo $rws['buna_id'] ?>"><img class="thumb" src="images/<?
php echo $rws['image'];?>" width="300" height="200"></a>
<span class="price"><?php echo '$.'.$rws['price'];?></span>
<div class="property_details">
<h1><a href="product.php?id=<?php echo $rws['buna_id'] ?>"><?php echo 'Coffee Body and
Location>'.$rws['body'];?></a></h1>
<h2>Coffee Name: <span class="property_size"><?php echo $rws['fname'];?></span></h2>
</div>
99
</li>
<?php}?>
</ul>
</div></section>
<?php include("attach/footer.php")?>
</body>
</html>
Cart page php code
<body>
<div class="small-container cart-page">
<table>
<tr>
<th>Product</th>
<th>Quantity</th>
<th>Subtotal</th>
</tr>
<tr>
<td>
<div class="cart-info">
<div>
<?php
$total = 0;
$itemTotal = 0;
if (isset($_SESSION['cart'])) {
foreach ($_SESSION['cart'] as $key => $value) {
$itemTotal = $value['item_price'] * $value['quantity'];
$total = $total + $value['item_price'] * $value['quantity'];
?>
100
<br>
<form action="attach/cartremove.php" method="POST">
<button name="remove">Remove</button> <input type="hidden" name="item_name" value=
<?php echo $value['item_name']?>></form>
<?php echo $value['item_name']?>
</div>
</div>
</td>
<form action="attach/cartupdate.php" method="POST">
<td><input type="number" min="1"value="<?php echo $value['quantity'] ?>"
name="qty"><button name="update">Update</button> </td><input type="hidden"
name="item_name" value= <?php echo $value['item_name']?>></form>
<td>$<small> <?php echo $value['item_price'];?></span></small></td>
</tr>
</table>
<div class="total-price">
<table>
<tr>
<td>Subtotal</td>
<td>$<?php echo $value['item_price'];?></td>
</tr>
<tr>
<td>Tax</td>
<td>15%</td>
</tr>
<tr>
<td>Total</td>
<td>$<?php echo $itemTotal ?></td>
</tr>
101
</table>
</div>
<div class="buttons">
<a href="catagories.php"><button>Continue Shopping</button></a>
<a href="checkout.php"><button>Proceed to Checkout</button></a>
</div>
<a href="attach/cartclear.php"><button>Clear Cart</button></a>
</div>
<?php }}?>
Cart update php code

<?php
session_start();
if (isset($_POST['update'])) {
if ($value['item_name'] == $_POST['item_name']) {
$_SESSION['cart'][$key]['quantity'] = $_POST['qty'];
$_SESSION['cart'] = array_values($_SESSION['cart']);
header('location: ../cart.php');} }
Remove form cart php code

<?php
session_start();
if (isset($_POST['remove'])) {
if ($value['item_name'] == $_POST['item_name']) {
unset($_SESSION['cart'][$key]);
$_SESSION['cart'] = array_values($_SESSION['cart']);
echo "<script>alert('item removed');
102
window.location.href='../cart.php'; </script>";}}}
Chapter Six – Conclusion and Recommendation
6.1Conclusions
This system was designed to develop a system that serves as a bridge between coffee farmers and
exporters our system manages information easily and precisely, and provide an automated
system to get services to the customers. Accordingly, efforts have been made to assess the skill
development, the improvements achieved on solving export service problems, technological
bariers, the utilization of trade and additional investments from traditional (current)coffee
exporting services. the improvements gained from our system are automation, reliabilty, ease of
use, reducing cost, building reputation, building trust making a profit, and giving the rural
farmers a bigger share of the revenue..
6.2Recommendation
As we have mentioned in the conclusion statement there are problems that our system will
solve.so we are going to recommend them here in recommendation statement.one of the most
recommended things we have provided to potential importers are broad information about
ethioipian coffee, with variety of types and prices and also find the best brewing coffee in the
world
103
References
1. https://enjoyjava.com/ethiopian-coffee/
2. https://ethiopianmonitor.com/2022/04/15/ethiopia-racks-up-894m-from-nine-
month-coffee-export/
3. Linking Rural Farmers to Markets Using ICTs. Mawazo M. Magesa
4. [Heinz Züllighoven, 1996]
5. Infomineo 2016 agriculture in Ethiopian
6. Retrieved from https://infomineo.com/agriculture-in-ethiopia-3/#:~:text=Sectoral
%20overview,million%20hectares%20of%20arable%20land.
7. Ethiopian Coffee Exporters Association, 2016.
8. Object Using UML, Patterns, and Java -Oriented Software Engineering

9.
104

Final Project Full Documentation Ver.3.0

Uploaded by

Copyright:

Available Formats

Final Project Full Documentation Ver.3.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Project Full Documentation Ver.3.0

Uploaded by

Copyright:

Available Formats

Unity University

College of Engineering, Technology and Computational Science

Title: Coffee Export Management System

Final project document

Submitted to department of Computer Science and MIS in partial

RMMM – Risk Mitigation, Management, and Monitoring

MMM – Mitigation, Management, and Monitoring

SQL – Structured Query Language

WBS – Work Breakdown Structure

HRP – Human Resource Planning

UC- use case

SUC - System Use case

CPU – Central Processing Unit

I/O – Input / Output

Table 2. 1 Human Resources Planning............................................................................................9

Table 3. 1 Users have to be logged in before performing some actions BR.................................29

Table 4. 1 Client table....................................................................................................................67

Figure 2. 1 Work Breakdown Structure...........................................................................................8

Figure 3. 1 Use Case Diagram.......................................................................................................24

Figure 3. 1 Use Case Diagram.......................................................................................................24

Figure 4. 1 Subsystem decomposition...........................................................................................68

1. What is the scope/scale of your work?

2. What were the goals of the system and company?

3. How does the current system work? How do you handle:

b. Quality Assurance, Certification, and documentation?

i. What types of beans are sold? Pre-roasted, roasted, and/or ready-to-plant.

c. Storage of the product?

d. Packaging and shipment?

6. RISK Management Plan

7. What system model are you using?

8. Who are the competitors of the company?

1. Does the export company have a website?

3. Tools and Methodologies

a. How was the initial planning and setup of operations done?

c. What were the Development tools used?

5. Where there any beneficiaries? Who were they?

6. How long did it take to get everything set up and operational?

1.1 Background Information

1.2 Statement of the Problem

● Manage inventory, stock, and quality management.

● A system to approve a product if its quality meets international market demand or

1.3.1. General Objective

1.3.2. Specific Objectives

● To have a working store page

● To have order and cart functionalities

● To provide shipping options

● To automatically handle financial calculations like taxes and shipping

● To have a secure login functionality

1.4. Scope of the Project

● Catalogue of coffee that are ready for export

● Fully functional e-market

● Report on coffee sales

● Calculation of taxes, shipping, and currency exchange

● Options for shipping

● Cart and Order capabilities

● Search for a product by name and add to cart

● Register a new farmer

● Order a product and a confirmation message after order is complete

● Live tracking of shipments

● Fully functional customer service