SOKONI MOBILE APPLICATION FINAL REPORT

THE UNIVERSITY OF DODOMA
SOKONI MOBILE APPLICATION
BY
STUDENT NAME REGISTRATION NUMBER COURSE
Chalamila, Richard T/UDOM/2014/08049 BSc. BIS
Shuhudia, Eliza T/UDOM/2014/02731 BSc. BIS
Timoth, Roland P T/UDOM/2014/02734 BSc. BIS
Oswald, Nickson T/UDOM/2014/02739 BSc. BIS
Minja, Nicomedi T/UDOM/2014/08787 BSc. BIS
A project report submitted in partial fulfillment of the requirements for
BSc Business Information System
Of
University of Dodoma
College of informatics and virtual Education
School of informatics
30th
June 2017

i
STUDENT’S DECLARATION
We, Chalamila Richard, Shuhudia Eliza, Timoth Roland P, Oswald Nickson, Minja
Nicomedi, hereby declare that the Project report named Sokoni Mobile Application submitted in
the partial fulfillment of the requirements for the course of BSc. in Business Information System
to the College of Informatics and Virtual Education, is our original work and has not been
submitted for the award of any other degree, diploma, fellowship, or any other similar, title,
training or prizes.
STUDENT NAME REGISTRATION NUMBER SIGNATURE
Chalamila, Richard T/UDOM/2014/08049
Shuhudia, Eliza T/UDOM/2014/02731
Timoth, Roland P T/UDOM/2014/02734
Oswald, Nickson T/UDOM/2014/02739
Minja, Nicomedi T/UDOM/2014/08787
Place ___________________
Date ___________________

ii
SUPERVISOR’S CERTIFICATION
This is to certify that the project entitled Sokoni Mobile Application submitted in partial
fulfillment of the requirements for the course of BSc Business Information System at the College
of Informatics and Virtual Education by Chalamila Richard, Shuhudia Eliza, Timoth Roland
P, Oswald Nickson, Minja Nicomedi, have worked under my supervision and guidance and that
not part of this report has been submitted for the award of any other degree, diploma, fellowship
or other similar title, training or prizes and that the work has not been published in any journal or
magazine.
STUDENT NAME REGISTRATION NUMBER
Chalamila, Richard T/UDOM/2014/08049
Shuhudia, Eliza T/UDOM/2014/02731
Timoth, Roland P T/UDOM/2014/02734
Oswald, Nickson T/UDOM/2014/02739
Minja, Nicomedi T/UDOM/2014/08787
Certified……………………………….
Guide’s Name…………………………
Certification ………………………….

iii
EXAMINER’S CERTIFICATION
The project report of Chalamila Richard, Shuhudia Eliza, Timoth Roland P, Oswald Nickson,
Minja Nicomedi, with the project named Sokoni Mobile Application is approved and acceptable in
quality and form.
Internal Examiner External Examiner
Name: …………………………....... Name………………………………….
Qualification……………………….. Qualification…………………………..
Designation………………………… Designation……………………………

iv
ABSTRACT
This report comprises of four chapters, the first chapter contain introduction, objectives and
literature review about the project, second chapter contain all issues about design, third chapter
contain implementation, testing and evaluation, and last chapter contain recommendation and
conclusion.
Sokoni Mobile Application is the mobile application that will help customers to communicate with
the market vendors online, to allow prior assurance of customers to the availability of goods of
their interest, purchase the market product and the customer will be able to make payment on
delivery. This project aimed at facilitating business operations by converting manual business
operations to computerized one. The project designed to manage business by allowing the
customers to make orders of the products of their interest online from the specified market like
Majengo market, then make payment after receiving the products from the delivery agent.
The system starts from the administrator who registers the market vendors and delivery agents.
The market vendor login to the system and upload the products for sale, then the customer register
into the system and select the products and add to cart for purchase. When the customer finishes
to add the products to the cart, she/he must click the checkout button so as to send order to the
delivery agent. Then delivery agent delivers the product to the customer and then press the clear
button to confirm the deliverance.

v
ACKNOWLEDGMENT
First and for most we would like to express our spiritual gratitude to the whole management of
Collage of Informatics and Virtual Education of UDOM. We have taken efforts in this project,
however, it would not have been possible without the kind support and help of many individuals
and organizations. We would like to extend our sincere thanks to all of them.
Special thanks should go to Principal of CIVE Prof A. N. Mvuma, Dean School of informatics
Prof. J. Anatory, and Head of department of BIT Dr. Saleh Mrutu for their guidance which made
us to achieve the success.
Every project big or small is successful largely due to the effort of a number of wonderful people
who have always given their valuable advice or lent a helping hand. We sincerely appreciate the
inspiration; support and guidance that we have attained from our beloved project supervisor
Mr. Iddy Sai Mambina. Furthermore, we would like to extend our thanks to project coordinator
Mr. Said H Said who played his role actively to organize all project activities efficiently, to
provide project updates as well as good supervision of project presentation.

vi
TABLE OF CONTENTS
STUDENT’S DECLARATION...................................................................................................................................i
SUPERVISOR’S CERTIFICATION ....................................................................................................................... ii
EXAMINER’S CERTIFICATION.......................................................................................................................... iii
ABSTRACT ................................................................................................................................................................iv
ACKNOWLEDGMENT.............................................................................................................................................v
LIST OF FIGURES....................................................................................................................................................vi
LIST OF TABLES.................................................................................................................................................... vii
LIST OF SYMBOLS AND ABBREVIATIONS................................................................................................... viii
CHAPTER 1.................................................................................................................................................................1
INTRODUCTION...................................................................................................................................................1
OVERVIEW.........................................................................................................................................................1
OBJECTIVES.......................................................................................................................................................2
SCOPE..................................................................................................................................................................2
LITERATURE SURVEY.....................................................................................................................................3
CHAPTER 2.................................................................................................................................................................4
DESIGN ...................................................................................................................................................................4
FUNCTIONAL REQUIREMENTS .....................................................................................................................4
NON-FUNCTIONAL REQUIREMENTS ...........................................................................................................6
DATA FLOW DIAGRAMS.................................................................................................................................7
ENTITY RELATIONSHIP DIAGRAM...............................................................................................................9
FLOW CHART DIAGRAM...............................................................................................................................10
USE CASE DIAGRAM......................................................................................................................................11
INTERFACE DESIGN.......................................................................................................................................15
CHAPTER 3...............................................................................................................................................................21
SYSTEM IMPLEMENTATION .........................................................................................................................21
TESTING...............................................................................................................................................................21
EVALUATION......................................................................................................................................................21
CHAPTER 4...............................................................................................................................................................22
CONCLUSION......................................................................................................................................................22
RECOMMENDATION ........................................................................................................................................22
REFERENCES ..........................................................................................................................................................23
APPENDICES............................................................................................................................................................24
Appendix A: SOURCE CODE.............................................................................................................................24
Appendix B: SUGGESTIONS..............................................................................................................................26

vii
LIST OF FIGURES
Figure 1: Context diagram for Sokoni Application ........................................................................ 7
Figure 2: Level 1 Data Flow Diagram for Sokoni Application ...................................................... 8
Figure 3: Entity relationship diagram for Sokoni Application ....................................................... 9
Figure 4: Flow chart Diagram for Sokoni Application................................................................. 10
Figure 5: Use Case for Sokoni Application.................................................................................. 11
Figure 6: Web Login interface for the Administrator................................................................... 15
Figure 7: Administrator Interface for registering New market Vendor....................................... 16
Figure 9: Administrator interface for editing of market vendor information ............................... 16
Figure 12: Sokoni App Home interface........................................................................................ 17
Figure 11: Sokoni App Login interface ........................................................................................ 17
Figure 8: Administrator interface for delete registered market vendor ........................................ 17
Figure 10: Sokoni App registration form interface....................................................................... 18
Figure 13: Sokoni App List of product interface for market vendor ............................................ 18
Figure 14: Sokoni App add product description interface for market vendor .............................. 18
Figure 15: Sokoni App register product interface for market vendor........................................... 18
Figure 18: View Product Description Interface............................................................................ 19
Figure 19: Change Password Interface ......................................................................................... 19
Figure 16: Sokoni App cart interface for the customer................................................................. 19
Figure 17: Sokoni App market vendors option interface.............................................................. 19
Figure 21: Customer Orders interface........................................................................................... 20
Figure 20: Add Product Description interface.............................................................................. 20
LIST OF TABLES
Table 1: Use Case description....................................................................................................... 12

viii
LIST OF SYMBOLS AND ABBREVIATIONS
BIT - Business information Technology
BSc - Bachelor of Science
CIVE - College of Informatics and Virtual Education
DFD - Data Flow Diagram
ERD - Entity Relation Diagram
ICT - Information and Communication Technology
UDOM - University of Dodoma
U.S - United States

CHAPTER 1
INTRODUCTION
OVERVIEW
Sokoni Mobile Application is the mobile application that will help customers to communicate with
the market vendors online, to allow prior assurance of customers to the availability of goods of
their interest, purchase the market product and the customer will be able to make payment on
delivery.
In Tanzania the existing situation doesn't favor customers to communicate with market vendors
online, order products online and identify the location of vendors who sell different kind of
products at the market place. Due to presence of these problems there is the need of the system
that will act as an intermediate between customers and vendors so as to ensure proper, safe and
easy marketing process.
In response to this, we propose to develop a complete Mobile Application that will allow the
customer to purchase the product online.
The proposed system will resolve the mentioned problems: -
 Assurance of getting goods of high quality.
 Ensured and balanced safety of goods to both side of customers and vendors.
 Reduced purchasing time to customers.
 Prior assurance of customers to the availability of goods of their interest.
 Customer awareness of the market location.
 Increase in nation income through tax collection.
 Increased sales to market vendors.
1

2
OBJECTIVES
Main Objective
Develop a Sokoni mobile application that will allow a customer to purchase market product online.
Specific Objectives
 To collect user requirements from market vendors and customers.
 To design and develop the database for the storage of information in the system.
 To design and develop web and mobile interfaces for administrator, customer, delivery
agency and market vendor.
 To implement and deploy Sokoni mobile application.
SCOPE
The scope of this project is to develop Sokoni Mobile Application that will be able to manage
one market.

3
LITERATURE SURVEY
There is the number of ecommerce sites that were initially started for the purpose of offering
services that relate to services that will be offered by SOKONI mobile application, one of them is
Ingredientsonline.Com.
Ingredientsonline.Com founded by Sherry Wang in 2013, ingredientsonline.com has
revolutionized the manner in which manufactures and co-manufactures purchase raw materials.
Sherry is an FDA regulation expert who has more than 20 years of experience importing raw
ingredients to the U.S, with this background she revolutionized the industry and how raw
ingredients are purchased in an internet-driven world [2].
Ingredientsonline.Com whereby this is one of the best e-commerce platforms for factory-direct,
bulk raw ingredients which provide nutritional raw materials for the dietary supplement, food
&beverage, cosmetic and pet industries. Ingredientsonline.Com does the leg work for you by
housing all ingredients for you in U.S, there by taking care of your lead time you don’t have to
wait before you bring production [2].
Sokoni Foods Indian and British Foods is the main distributor of Indian food, Indian drinks, Indian
herbal oils, Indian Herbal and Ayurveda medicine and other Indian grocery as well as British Food
and Drinks, Filipino Food and Drinks. West African food from Ghana and Nigeria as well as other
Asian products all over Europe and especially to Bulgaria, Romania and Greece with free delivery
offer [1].
In Tanzania there is the mobile application called Sokoni Leo whereby this is the mobile
application designed specifically for giving important information about different crops found in
the market. This mobile application helps customers and farmers to be aware of prices of different
crops found in the market. Currently this mobile application is connected to only one market in
Tanzania (KARIAKOO) [3].

4
CHAPTER 2
DESIGN
We took a structured approach in the designing of the system. So far we have managed to gather
requirements, come up with use case, process modeling (Dataflow Diagram), data modeling
(Entity Relationship Diagram) and simple interface design.
WORKDONE
 Functional Requirements
 Non-functional Requirements
 DFD (context and level 1)
 Entity Relation Diagram (ERD)
 Flow Chart Diagram
 Use case
 Interface design
 Database
 All system users’ functionalities
FUNCTIONAL REQUIREMENTS
Customer
 The system should allow the customer to register and create an account.
 The system should allow customer to login and logout from the system.
 The system should allow customer to select and add to cart the product for purchase.
 The system should allow the customer to browse (search) for the product.
 The system should allow customer to view product price description.
 The system should allow customer to change the password.
 The system should allow customer to delete order.
 The system should allow the customer to checkout after add products to cart.

5
Market Vendor
 The system should allow the market vendors to add the product and product
description.
 The system should allow market vendor to login and logout from the system.
 The system should allow market vendor to change the password.
Administrator
 The system should allow an administrator to register market vendor and delivery agent.
 The system should allow administrator to login and logout from the system.
 The system should allow an administrator to delete the market vendor or delivery agent.
 The system should allow an administrator to edit the details of market vendor or
delivery agent.
 The system should allow the administrator to view the detail of registered customers.
Delivery Agent
 The system should allow delivery agent to login or logout into the system.
 The system should allow delivery agent to view the orders of the customer.
 The system should allow the delivery agent to change the password.
 The system should allow the delivery agent to clear customer orders.

6
NON-FUNCTIONAL REQUIREMENTS
These are constraints on the services or functions offered by the system. Non-functional
requirements often apply to the system as a whole. They do not usually just apply to individual
system features or services
Some of these non-functional requirements that the system should also embrace are the following
requirements: -
 Reliability: The system will consistently perform its intended function, example, the
important information must be validated.
 Efficiency: Unnecessary data will not be transmitted on the network and database server
will be properly connected.
 Integrity: Only System Administrator has rights to access the database, not every user can
access all the information. Each user will be having rights to access the modules.
 Security. The system should log administrator that have been assigned user names and
passwords. The system should be designed to make it impossible for anybody to login
without a valid username and password. Data encryption should be employed to keep the
user login name and password secret.
 Accessibility. Users can access the system from any location provided that he or she has
internet connection.

7
DATA FLOW DIAGRAMS
These are diagrams that graphically illustrate movement of data between external entities and the
processes and data stores within a system. In our system we illustrate two dynamic mechanics of
data flow diagram, Level 0(context diagram) and Level 1 diagram.
LEVEL 0 (CONTEXT DIAGRAM)
Figure 1: Context diagram for Sokoni Application

8
LEVEL 1 DATA FLOW DIAGRAM
Figure 2: Level 1 Data Flow Diagram for Sokoni Application

9
ENTITY RELATIONSHIP DIAGRAM
The entity relationship diagram (ER diagram) is a diagram which shows the relationship between
entities of the system. Each entity has its own attributes that describe and characterize it. The
following is the entity relationship diagram which shows the relationship between the entities and
their attributes.
Figure 3: Entity relationship diagram for Sokoni Application

10
FLOW CHART DIAGRAM
Figure 4: Flow chart Diagram for Sokoni Application

11
USE CASE DIAGRAM
The use case diagram describes the functions in terms of events and actors. The figures below
show how the users communicate with system.
Figure 5: Use Case for Sokoni Application

12
USE CASE DESCRIPTION
The following tables describe in details each of the use case in term of its actors, actor action and
system without forgetting the assumptions if any.
Table 1: Use Case description
Use case Login
Description The system should allow the user of the system to login by capturing the
username and password of the user and grant a user appropriate access and
privilege to the resource.
Actor Administrator, Customer, Market Vendor
Assumption Customer and Administrator has been registered with the system and
Market vendor has been registered by Administrator.
Scenarios 1) User click login button.
2) System display Sign in screen.
3) User write username and password and click login button.
4) System verify user username and password.
5) System grant access to user according to user privilege.
6) Main user Screen is opened.
Extension 3a) Unable to login due to invalid username or password, notify with
the message “please try again”.
3b) If the account does not exist, please register first before login.
Use case Add market Vendor
Description The system should allow an administrator to add market vendor to the
system with their details.
Actor Administrator
Assumption Administrator has already login to the system.
Scenarios 1) Administrator click Add Market Vendor button.
2) The system will display the page with form to write the market
vendor details.

13
3) Administrator write the market vendors details and submit to
system.
4) System will notify the Administrator that the Market Vendor has
been registered successfully
Extension
Use case Register
Description The system should allow customer to register him/herself in the system
and create account.
Actor Customer
Assumption The customer should be able to view his or her filled details.
Scenarios 1) Customer click the registration button.
2) System will display the form which will allow the customer to enter
his or her details.
3) Customer fill the form with his/her details and place ‘submit’
button.
4) System display the confirmation message ‘Submitted successful’
or ‘Not Submitted’.
Extension
Use Case Add Product
Description The system should allow the market vendor to add product in the system
with their details.
Actor Market Vendor
Assumption The Market Vendor has already login to the system.
Scenarios 1) Market Vendor click add product button.
2) The system will display the form which will allow the market
vendor to fill the product details.
3) Market vendor click upload button.

14
4) System will notify market vendor that the product has been
uploaded.
Extension 2a) Unable to add product because the product already added, notify the
market vendor with error message to add another product.
Use Case Browse Product
Description The system should allow the customer to browse for the specific category
of the product.
Actor Customer
Assumption The system has already display the home page to the customer.
Scenarios 1) Customer place the cursor to the search box and write the keyword
of the product.
2) Then place search button.
3) The system display the list of available product relate to that
keyword.
4) Customer view and select the product he or she want.
5) System display the product and its description.
Extension 3a) Unable to display the product due to the unavailable of the product
the customer want to view, notify customer include error message ‘product
not available’.
Use Case Buy Product
Description The system should allow the customer to select and buy the product in the
system.
Actor Customer
Assumption The customer has already login to the system.
Scenarios 1) System display the product to sell.

15
2) The customer selects the product to buy.
3) Then select the buy product button.
4) The system display a feedback message that the customer has
successful buy the product.
Actor Delivery Agent
Assumption The Delivery Agent has already login to the system.
Scenarios 1) System display different orders reserved by customers
2) The delivery agent selects the orders by customer
3) The delivery agent click clear button when the order has been
already delivery to the customer.
INTERFACE DESIGN
Figure 6: Web Login interface for the Administrator

16
Figure 7: Administrator Interface for registering New market Vendor
Figure 8: Administrator interface for editing of market vendor information

17
Figure 11: Administrator interface for delete registered market vendor
Figure 10: Sokoni App Login interface Figure 9: Sokoni App Home interface

18
Figure 12: Sokoni App registration
form interface
Figure 13: Sokoni App List of product
interface for market vendor
Figure 15: Sokoni App register
product interface for market vendor
Figure 14: Sokoni App add product
description interface for market
vendor

19
Figure 19: Sokoni App market
vendors option interface
Figure 18: Sokoni App cart interface
for the customer
Figure 17: Change Password Interface
Figure 16: View Product Description
Interface

20
Figure 20: Customer Orders interfaceFigure 21: Add Product Description
interface

21
CHAPTER 3
SYSTEM IMPLEMENTATION
Is the practice of creating or modifying a system to create a new business process or replace an
existing business process. The implementation part in our project includes the following tools and
technical skills.
 backend – java and php.
 frontend - java, xml.
 Tools -android studio (android development), xampp (server database).
 Database - MySQL(Backend), SQLite (Android).
TESTING
i. Unit testing - Are automated tests. Each unit test typically will test only a single
component, or a small cluster of the system.
ii. Integration testing - Integration testing will be conducted after combining and linking
together all modules of the system.
iii. System testing - The aims to check whether the new programs operate together as a
working system and conform to necessities specification.
EVALUATION
The system will be evaluated to see if meets the user expectations and if it fulfils all
requirements as planned during the first phase of development. Two approaches will be used to
evaluate the systems, Formative (at each stage) and Summative (at the end of the system)
evaluations. The system evaluation will base mostly in the following issue: -
 Usability: It include Easy accessed by different users.
 Functionality: The system will be designed well to assure it address the requirements at
hand by the user to solve the stated and justified issues.
 Acceptability: The system will be designed to help the user recover from the error,
eliminate user errors, and error cost, by making it simple as it can to satisfy the user and at
the same time to address the required functionalities.
 Security issues: Security will be assured by only granting the user access to the information
(interface) that he/she is allowed to interact with system administrator will have full
authorization to the system.

22
CHAPTER 4
CONCLUSION AND RECOMMENDATION
CONCLUSION
The system that we have developed will be beneficiary to businesses and customers. It will provide
conducive environment to conduct business smoothly and efficiently. Also it will motivate the
penetration of modern systems in conducting daily businesses activities
RECOMMENDATION
We recommend the college management to take action on improvement of our project, because
this project may play the great role if it will be implemented in business entities and may increase
business operation effectiveness and efficiency.

23
REFERENCES
[1] Sokoni team. 2016. Sokoni Foods Indian and British Foods.
http://www.mysupermarketbulgaria.com/home.asp (accessed 22 June 2017), Time 21:50 PM.
[2] Sherry Wang, 2013. ingredientsonline.com. http://www.ingredientsonline.com/ (accessed 19
June 2017), Time 02:06 AM
[3] Antihuman, Mahiza. 2016, June 24. Sokoni Leo. http://www.mobogenie.com/download-
sokoni-leo-3516063.html (accessed 17 June 2017), Time 00:03 AM.
[4] Jean Claude KANYESHYAMBA, 2012. Online ordering and inventory system.
http://www.memoireonline.com/07/12/5995/m_Online-ordering-and-inventory-system0.html
(accessed 25 June 2017), Time 13:03 PM.

24
APPENDICES
Appendix A: SOURCE CODE
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1">
<meta name="description" content="">
<meta name="author" content="">
<meta name="viewport" content="width=device-width, initial-
scale=1">
<script type="text/javascript"
src="js/ajaxcode.js"></script>
<title>Sokoni: <?php echo $pageTitle; ?></title>

<link href="bower_components/bootstrap/dist/css/bootstrap.min.css"
rel="stylesheet" media="screen">
<link href="bower_components/bootstrap/dist/css/printer.css"
rel="stylesheet" media="print">

<link href="bower_components/metisMenu/dist/metisMenu.min.css"
rel="stylesheet">

<link href="dist/css/timeline.css" rel="stylesheet">

<link href="dist/css/sb-admin-2.css" rel="stylesheet">

<link href="bower_components/morrisjs/morris.css"
rel="stylesheet">

25

<link href="bower_components/font-awesome/css/font-
awesome.min.css" rel="stylesheet" type="text/css">
<link type="text/css" rel="stylesheet" href="css/sytlepage.css"/>
</head>
<body style="font-family:Century;background:url(image/2.png)">
<div class="row" style="margin-top:-17px;">
<div class="col-md-1 col-xs-1 col-lg-1"></div >
<div class="col-md-10 col-xs-10 col-lg-10">
<?php if(isset($_SESSION['sokoni_user_id'])){?>
<div class="row">
<div class="page-header"></div>
<div class="col-md-12">
<div class="well"
style="background:#336666;text-align:center;font-
size:30px;color:#ffffff">
Welcome to Sokoni
Application: Admin Panel
<ul class="nav navbar-top-links navbar-right"
style="font-size:12px">
<li class="dropdown">
<a class="dropdown-toggle" data-
toggle="dropdown" href="#">
<span cla ss='alert alert-success'> <i class="fa
fa-user fa-fw"></i> <?php echo $_SESSION['sokoni_firstname']."
".$_SESSION['sokoni_lastname']; ?> <i class="fa fa-caret-
down"></i></span>
</a>
<ul class="dropdown-menu dropdown-user">
<li><a href="index.php?q=logout"><i class="fa fa-sign-out fa-
fw"></i> Logout</a>
</li>
</ul>
</body>
</html>

26
Appendix B: SUGGESTIONS
Since the form of teaching courses had been more practical oriented, we were able to see and
practice what we merely learnt in class and read in lecture notes especially in Internet
Programming Application, C++, Data Structure and Operating System. All courses’ sessions gave
us knowledge of what we could experience as a normal user of computer and to know how create
or develop System that is useful to specific market the deals with the selling of goods. Also some
of courses such as Database Management System, E-business Strategy Architecture and Design,
IS strategy, System Analysis and Design and ICT Research Method gave us knowledge on how to
follow the strategies and methods as guidelines on early stage of development of our System till
to the finally development.
However, the time factor has been a barrier towards more and efficient learning. Consequently,
we would recommend the final year project to be given enough period of time so that teaching
courses for the last semester for final year can be reduced to the maximum of four. Also final year
project can be carried out in as much time as required.
Also we recommend the provision of enough funds that will cover overall processes from the data
collection, data analysis, designing and development, testing and finally implementation of the
System which requires capital for their completion.
In our opinion, this course is good and we encourage it to be continued because it equips students
with additional knowledge and experience more than what is gained in their regular studies.

SOKONI MOBILE APPLICATION FINAL REPORT

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SOKONI MOBILE APPLICATION FINAL REPORT

Similar to SOKONI MOBILE APPLICATION FINAL REPORT (20)

Recently uploaded

Recently uploaded (20)

SOKONI MOBILE APPLICATION FINAL REPORT