Shira’ MPOS, Mobile Point of

Sale for Multipurpose Use

PREPARED BY: AMIRULL MUSTAQIM BIN MOHAMMAD
MATRIX NO: 16B07015
COURSE: BCNS
FACULTY: FKMPT
SUPERVISOR: MADAM NORANIAH
Introduction

 The name of the project, Shira’ comes from the

word Arabic ‫رررررراء‬
‫ ش‬, meaning purchase / buy.
 The term Mobile Point of Sail (MPOS) is a
smartphone, tablet or dedicated wireless device
that performs the functions of a cash register or
electronic point of sale.
 mPOS represent the ability for a customer
transaction to be documented by a smartphone or
tablet instead of by a traditional checkout register
1.0 Problem Statement

 Most of mobile point of sale nowadays offer

subscription based payment model for using their
software, so we offer to the public to develop apps
and publish it as open source software.
 How could MPOS developed and by using what
tools, library and framework?
 What is the best way to develop the software to
prevent fraud transaction and security problem?
2.0 Research Objective

 To research and implement real world mobile

point of sale application best practice by
comparing various type of available mobile point
of sale.
 To develop mobile point of sale android
application
3.0 Scope of Works

 The software will be available for customer,

cashier and manager of grocery store.
 The environment where the mobile point of sale
used typically in grocery store and warehouse for
inventory management and tracking.
 The platform for installing software is only android
phone.
 Security – finger print & password
4.0 Project Significance

 Shira MPOS is an easy and affordable way for

retailers to accept payments with mobile devices.
Customers can use mobile devices to select and
pay for items without assistance.
 Does not need Hardware and Equipment with less
expenses
 Paying with a mobile device at point of sale
eliminates the need for check-out equipment.
 Today, customers demand purchase options that
match their shopping habits
5.0 Literature review
 5.1 Comparisons of Software
Process Models
Process Strengths Weakness
Model
Waterfall Simple , concise, easy to execute, Requirements are frozen early, user
logical ordering, For well understood feedback & changes not allowed, Linear
problems, short duration’s projects. series of actions
Prototyping Help in requirements elicitation, Heavy process, disallow later changes
constructive feedback, reduce risks,
leads to better systems
Iterative Quick delivery , reduce risk, allows Each iteration have planning overhead,
user cost increase during iteration, effective
feedback, when requirement are not management to control iterations
known earlier.
Spiral Planning and negotiations easier, Requirement not clear , needs
flexibility in development, for larger confirmations and high risks
projects
Knot Reusability, Easy Planning , Selecting a right component is difficult,
Model requirements reservoir may be huge or difficult to
clear , no complexity of software manage
applications, reduces risk and
development time, reduces cost,
applicable on larger & complex
systems
Table 1: Comparisons of Software Process Models
Project Framework

1. Functional Requirement
 Able to scan barcode.
 Able to read NFC enabled discount card
 Can easily scan product and fast checkout
2. Non-fuctional requirement
 Store data in SqlLite3
 Use Scandit Barcode SDK
 Store password in hash form and not in plaintext
 Adhere guideline to Google Material Design