POINT OF SALE

BS (SOFTWARE ENGINEERING)
SESSION: 2017F-2021

Submitted to:
Minhaj University Lahore
School of Software engineering

Submitted by:
Muhammad Bin Saeed
Roll No.03
Iqra Hussain
Roll No: 14

Supervised by:
Saleem Akhtar Shahib
(Head, School of Software engineering)
In the name of ALLAH,
The Most Beneficial,
The Most Merciful.
 ACKNOWLEDGEMENT

We express our thanks and gratitude to Allah almighty and our parents, our brilliant lecturers and
friends without whose uncontained support; we could not have made this career in project
development.

We wish to place on record our deep sense of gratitude to our project supervisor Saleem Akhtar
Sahib who helped us throughout the project work and motivated us constantly. We also express
our gratitude to Saleem Akhtar Sahib for his motivation and valuable suggestion throughout the
BS (SE) program. We also extend our thanks to other Faculty members for their cooperation
during our program.

Finally, we would like to thank our friends for their cooperation to complete this project.

Student Name: Muhammad Bin Saeed

Student Name: Iqra Hussain
 ABSTRACT

Point of Sale is an web based application that An arrangement needed for present and next
coming time of advanced age businesses to increase profitability and Business insight about their
business clients and stock administration of manual truly stores and for online virtual web based
business stores that have same items that is introduced in physically in stores and needs to
permitting their clients to access on online store for buying things them. Presently they need a
framework that takes all duties about information the board and their stock or auto treatment of
their all on the web or manual clients.
Darning my statistical surveying, I gather a few discoveries about the issues of sellers or shippers
of dress and other supermarkets directors, that is about a computerized result of retail location that
have one data set and cover all sides of partners that are working under an organization or stage.
I think a retail location that is utilized for manual bulling or online store invoicing with stock
administration tending to every one of the difficulties with one window activity. At that point I
choose to foster a retail location programming and picked it into my last year project.
 DECLARATION

It’s stated that Students of Bachelor of Science in Software Engineering 2017f-2021 at Minhaj
University Lahore hereby declare that the matter printed in this documentation titled “Point of
sale” is our own work in the fulfill meant of Graduation program under Minhaj University
Lahore.
The supervision is provided by Saleem Akhtar Sahib under their very good supervision, guidance
and command we are able to produce this work.
The information and data presented in this document is authentic and legitimate to the best of our
Knowledge. We have performed this project with our own effort. We have also mentioned the
resources in the reference list from which we have taken help and gotten to guidance.

Name of the student: Muhammad Bin Saeed

Signature of Candidate: _______________________

Name of the student: Iqra Hussain

Signature of Candidate: _______________________

 CERTIFICATE

This is to certify that the project work contained in this documentation titled “Point of sale” has
been carried out and completed by the joint efforts of “Muhammad Bin Saeed” and “Iqra
Hussain” under my supervision and command.
It is now my judgment that this project and this documentation is of sufficient standard to warrant its
acceptance by Minhaj University Lahore for BS (H) degree in the subject of Software Engineering.

Date: _________________

Supervisor: Saleem Akhtar Sahib

(Head, School of Software Engineering)
_________________

FYP In charge: (Head, School of Software Engineering)

_________________

Head: (Head, School of Software Engineering )

_________________
 PROJECT BRIEF

Project Name Point Of Sale

Undertaken by Muhammad Bin Saeed & Iqra Hussain

Session 2017f-2021

Supervised by Saleem Akhtar Sahib

Platform Point Of Sale (Web Application)

Source Language PHP7, Laravel, MYSQL, JavaScript, bootstrap, HTML5

Tools NetBeans Ide, Apache Xampp Server

TABLE OF CONTENTS

CHAPTER 1 INTRODUCTION TO PROJECT...................................................................................................................... 1

1.1 BACKGROUND & CURRENT TECHNOLOGIES................................................................................................................ 2
1.2 MOTIVATION............................................................................................................................................................................... 3
1.3 SCOPE.............................................................................................................................................................................................. 3
1.4 PROBLEM STATEMENT.......................................................................................................................................................... 4
1.5 STRUCTURE OF DISSERTATION......................................................................................................................................... 4
CHAPTER 2 LITERATURE
REVIEWS.................................................................................................................................... 5
2.1 OVERVIEW.................................................................................................................................................................................... 6
2.2 PURPOSE....................................................................................................................................................................................... 7
2.3 OBJECTIVE.................................................................................................................................................................................... 7
2.4 FACILITATIONS.......................................................................................................................................................................... 7
2.5 MAJOR FEATURES..................................................................................................................................................................... 8
2.6 PRODUCT PERSPECTIVE........................................................................................................................................................ 8
2.7 USERS.............................................................................................................................................................................................. 9
2.8 SKILLS OF TEAM MEMBERS.................................................................................................................................................. 9
2.9 SCOPE OF THE SYSTEM......................................................................................................................................................... 10
2.10 USABILITY.................................................................................................................................................................................. 10
2.11 SUPPORTABILITY.................................................................................................................................................................... 11
2.12 SOFTWARE AND HARDWARE REQUIREMENTS....................................................................................................... 11
2.12.1 HARDWARE REQUIREMENTS.................................................................................................................................. 11
2.12.2 SOFTWARE REQUIREMENTS.................................................................................................................................... 11
2.13 TOOLS REQUIREMENTS....................................................................................................................................................... 11
CHAPTER 3 ANALYSIS AND DESIGN............................................................................................................................... 12
3.1 INTRODUCTION....................................................................................................................................................................... 13
3.2 PROPOSED SYSTEM................................................................................................................................................................ 13
3.3 PERFORMANCE........................................................................................................................................................................ 14
3.4 USER INTERFACES.................................................................................................................................................................. 14
3.5 DEVELOPMENT METHODOLOGY..................................................................................................................................... 14
3.6 USER FRIENDLY....................................................................................................................................................................... 15
3.7 PORTABILITY............................................................................................................................................................................ 15
3.8 SYSTEM INCOMPLETE........................................................................................................................................................... 15
3.9 SPECIFIC FUNCTIONAL REQUIREMENTS AND PROJECT FILE STRUCTURE................................................. 16
3.10 LIST OF ACTIVITIES FILES IN THIS PROJECT.............................................................................................................. 16
3.11 LIST OF XML FILES IN THIS PROJECT............................................................................................................................. 17
3.12 LIST OF OTHER JAVA FILES IN THIS PROJECT............................................................................................................ 18
3.13 CLASSIFICATION OF FUNCTIONAL REQUIREMENTS............................................................................................. 18
3.14 NON-FUNCTIONAL REQUIREMENTS............................................................................................................................. 19
3.15 PROJECT FEASIBILITY........................................................................................................................................................... 19
 3.15.1 TECHNICAL FEASIBILITY FOR POINT OF SALE....................................................................................................... 20
3.15.2 OPERATIONAL FEASIBILITY FOR POINT OF SALE................................................................................................. 20
3.16 TIME ESTIMATION.................................................................................................................................................................. 20
3.17 PROJECT COST ESTIMATION/ECONOMIC FEASIBILITY........................................................................................ 21
3.17.1 SERVER CONFIGURATION.......................................................................................................................................... 21
3.17.2 TOTAL ESTIMATED COST BECOMES..................................................................................................................... 21
3.18 USE CASE MODELING............................................................................................................................................................. 21
3.19 REGISTERED USER.................................................................................................................................................................. 22
3.20 USE CASE DIAGRAM FOR BRAND..................................................................................................................................... 23
3.21 USE CASE DIAGRAM FOR ADMIN...................................................................................................................................... 24
3.22 BEHAVIORAL MODELING.................................................................................................................................................... 25
3.23 DATA MODELING..................................................................................................................................................................... 25
3.24 SEQUENCE DIAGRAM OF USER......................................................................................................................................... 26
AUTHENTICATION SYSTEM FOR POINT OF
3.25 SALE........................................................................................................... 28
3.25.1 USERNAME AND EMAIL.............................................................................................................................................. 28
3.25.2 PASSWORD FOR SIGN IN............................................................................................................................................ 28
3.26 DATABASE HIERARCHY STRUCTURE FOR ADMIN.................................................................................................. 29
3.27 DATABASE HIERARCHY STRUCTURE FOR BRAND.................................................................................................. 30
3.28 DATABASE HIERARCHY STRUCTURE FOR USER...................................................................................................... 31
3.29 CONTEXT DIAGRAM............................................................................................................................................................... 32
3.30 DATA FLOW DIAGRAM.......................................................................................................................................................... 34
CHAPTER 4 IMPLEMENTATION........................................................................................................................................ 35
4.1 INPUT AND OUTPUT .............................................................................................................................................................. 36
4.1.1 INPUT OPTIONS FOR USER............................................................................................................................................. 36
4.1.2 OUTPUT FOR USER............................................................................................................................................................. 36
4.1.3 INPUT OPTION FOR BRAND ........................................................................................................................................... 36
4.1.4 OUTPUT FOR BRAND......................................................................................................................................................... 36
4.1.5 INPUT OPTION FOR ADMIN............................................................................................................................................ 37
4.1.6 OUTPUT FOR ADMIN ......................................................................................................................................................... 37
4.2 GUI.................................................................................................................................................................................................. 38
4.2.1 SPLASH SCREEN .................................................................................................................................................................. 38
4.2.2 SELECTION PANEL............................................................................................................................................................. 39
4.2.3 USER LOGIN PANEL ........................................................................................................................................................... 40
4.2.4 USER DASHBOARD ............................................................................................................................................................. 41
4.2.5 USER EDIT SETTINGS........................................................................................................................................................ 42
4.2.6 ADMIN PANEL ...................................................................................................................................................................... 43
4.2.7 ADD ADMIN ........................................................................................................................................................................... 44
4.2.8 ALL BRANDS.......................................................................................................................................................................... 45
4.2.9 BRANDS HOME..................................................................................................................................................................... 46
4.2.10 BRANDS CHAT PANEL ................................................................................................................................................. 47
4.2.11 AUTHENTICATE REQUESTS...................................................................................................................................... 48
4.2.12 ADD OFFER....................................................................................................................................................................... 49
CHAPTER 5 TESTING ........................................................................................................................................................... 50
5.1 TEST CASES ................................................................................................................................................................................ 51
5.1.1 USER PANEL TEST CASE .................................................................................................................................................. 51
5.1.2 BRAND PANEL TEST CASE .............................................................................................................................................. 52
 5.1.3 ADMIN PANEL TEST CASE.................................................................................................................................................. 53
5.2 ANDROID UNIT TESTING FOR POINT OF SALE...................................................................................................... 54
5.3 UNIT TESTING FOR POINT OF SALE........................................................................................................................... 54
5.4 VALIDATION TESTING FOR POINT OF SALE........................................................................................................... 54
5.5 PROJECT (POINT OF SALE) TESTING.......................................................................................................................... 55
5.6 POINT OF SALE TESTING RESULTS............................................................................................................................. 55
CHAPTER 6 CONCLUSION....................................................................................................................................................56
6.1 CONCLUSION......................................................................................................................................................................... 57
6.2 BENEFITS OF POINT OF SALE........................................................................................................................................ 57
6.3 LIMITATIONS........................................................................................................................................................................ 57
REFERENCE..............................................................................................................................................................................58
 CHAPTER 1

INTRODUCTION TO PROJECT
 Point of Sale

1.1 BACKGROUND & CURRENT TECHNOLOGIES

Shopping is coming from histories and it is an activity in which a customer browses the
available goods or services presented by one or more retailers with the potential intent to
purchase a suitable selection of them. Some persons do shop to have fun, enjoy and view it as a
leisure activity [1].
Online shopping has become a major disruptor in the retail industry as now people prefer to
do everything on their single clicks [2]. Consumers just have to search for product information and
place product orders across different regions while online retailers deliver their desired products
directly to the consumers' home, offices or wherever they want. The business to consumer process
has made it easy for consumers to select any product online from a retailer's website and their linked
resources and to have it delivered relatively quickly. Using online shopping methods, consumers just
need to chill and do not need to consume energy by physically visiting physical stores, but save time,
the cost of travelling and no headache of any kind. Shoppers' shopping experiences may vary
according to their moods, based on a variety of factors including how the customer is treated,
convenience, the prices of the product according to their quality.
So, now people do shop for fun and their life style, but there’re some people who don’t
afford a lot of things because they are depending on others like students. They want to buy things
but they don’t have a lot of money. It will be a good facility if somehow students start getting
some concession over the prices of different products in a very accessible platform so they could
get these products [1].
Currently, there are some sources like Facebook where different brands offer discounts
over different products but the discounts are very limited and it’s hard to find as you don’t follow
every single brands page and you already liked so many pages that you hardly can see any single
one’s offer [3]. This is the major problem where you can’t catch everything over the social sites.

2|Page
 Point of Sale

1.2 MOTIVATION

Once you have been able to track sales by the customer and the salesperson you can use the
strategies to motivate employees who are behind sales and reward sales people who always get
high sales numbers. Competing is healthy and good store competition is a great way to motivate
friends, however you should have accurate numbers and information.
POS systems allow sales participants to access information about customers' previous purchases to
better assist them or provide them with sales opportunity information during the sale.

Even where the sale is, a sales partner can quickly identify customer buying habits and
make recommendations based on their previous purchases. "Do we have a table recommending the
sofa you bought last month or do we have a few jerseys sold by your favorite designer have you
seen them?" you can quickly add sales to your day.

Affects Retail & wholesale Businesses.

Market impact Manual traditional billing and managing the sale and backup
inventory stock will be upgraded and easy to handling of store

Unique Solution Business reporting will be very fast and accurate due to point of
sale advance reporting tools.

Table No. 1.1: Affects and Impacts of Point of Sale

1.3 SCOPE

Designing a complete POS solution for your business will unfortunately have limits on
how big it can be and what service it can provide. This will force you to tackle your system sales
point and limit with a consistent eye. Starting a business means taking an attitude of not letting
any restrictions get in your way. Building a strong platform for products and services, and
integrating this with the next level of customer service, has helped your business grow without
self-control.

3|Page
 Point of Sale

1.4 PROBLEM STATEMENT

These are the following problem statements that must be tackling properly [9, 10]:
 Build software that solves the problem of online and traditional sale inventory.
 Software should be able to fulfill all the needs of billing and invoicing of customers.
 Provide the one window operation of managing inventory of online and manual store.
 Software will decrease the cost of manpower and give fast and accurate nonstop sales.
 Retail store easily measure the daily profit, sales volume, top rated products.
 Software gives the benefit of balancing the product availability and product demand.
 Handling and supply of goods with the reporting tools are very easy for managers.
 Hourly, daily monthly or yearly profit lose by items will be estimated with accurately.
 Admin can block and allow all types of users anyone he wants.

1.5 STRUCTURE OF DISSERTATION

There are 5 phases of this documentation. First one with the basic background and
problem statement with relevant cited work. Second one includes literature review, which is
explaining the entire solution in a very effective manner. Third one is analysis with complete
design for the app. Forth one is explaining all implementation details of this app and fifth chapter
is about testing of the app. In the end, conclusion of this documentation with all references used
during developing this documentation [11, 12, 13].

4|Page
 CHAPTER 2

LITERATURE REVIEW
 Point of Sale

2.1 OVERVIEW

The POS is an advance digital age revolution in web based Software’s. By using this
application, the owners of the retails stores get the benefit in different ways. The customers will
get access of products from both method of purchasing items from stores the first method is
purchase manually takeaway and here is second method order from same store online by using
web interface cart both method will access items from single inventory with help of point of sale
they can easily manage their shopping cart interface and they are facilitated with their secure
login customers panel. The main idea of this project is that to give the facility to retail store
market to easy managing their businesses digitally and live reporting of their businesses with
help of advance reporting tools. POS give the facility of digital system for sales activism to store
and give the confidence to customers by billing advance billing POS is divided up in three
categories which are USER (which will be the customers of store), Admin Panel and the store
Panel.
In Customers panel, customer will purchase online products with online stock on
connected interface of ecommerce store of POINT OF SALE and will be able to login into their
account for handling the product billing invoicing and they can view and track shipping of the
product that will be order from their account. Customers have also the authorization of cancel
and refund orders. They can view purchase history and compare the products. They can view
wish list for saves items for future purchase. Customers have their wallet option to manage
payments.
In Store panel, authorized staff can add Products and manage inventory. Staff can view
dashboard for reporting purpose and also view performance of their work that is performed from
their account about the selling and management. Into the purchase history module they can
analyze the sell’s payment reports. Authorized staff also views the review of the customers that
is leaved by the customers and answers them against their feedback. Another feature that is
important that is order taking and invoicing for billing purpose. Authorized staff can handle and
fulfill available orders that are active on manually store counter or generated online by the
customers on web interface cart.
In Admin panel, admin can authenticate any brand or reject if he wants. Admin can add
users and remove them. Admin can chat with the customers for their queries.
6|Page

Point of Sale

2.2 PURPOSE

We are atomizing Project Offline and Online Project Management System, due to current
issues solve by online system. It also enhances their intelligence level. This enjoyable interface
will satisfy the customers and the other system users because we’re creating new system on
World’s best web based Application [20].
 It is easy for the users.
 User can save their data automatically by system.
 Customers can see the different discounts and products.
 Customers can leave feedback & review.

2.3 OBJECTIVE

As for as our project is developed, we have maintained the functionality of our system
simple and user friendly. The main objective is our project is to provide the opportunity to make
sure the serve to customer’s time is going to be fruitful by deploying this system in everyone’s
favorite and accessible platform [4]. Our objective also includes the admin to be satisfied with
this project in positive image toward students as well as brands.

2.4 FACILITATIONS

The Point of Sale facilitates the customers and the staff over web (POS) platform [4, 6].
In customers perspective the customers can avail the different discount on different brands and if
we look on the brand side, they can earn a profit using this app by providing the special offers to
the students and increase their sales and advertise their brands as well.

7|Page
 Point of Sale

2.5 MAJOR FEATURES

We have studied about Android Development and make a list of features that will be
available in our app. An informative app that facilitate the students and the brands with many
functionalities like [6, 21, 22]:
 Discounts.
 Special Offers.
 Advertisement.
 Increase sale.
 User Friendly.

2.6 PRODUCT PERSPECTIVE

We made modules for the students, brands, and the admin. The Brand can add the list of
the special offers by logging in to their account [6]. The Students can see that discounts and avail
the discounts if they want or they can also search the specific brand with the specific category.
Some benefits and supporting features are given in the Table No. 2.1 below:

Benefits Supporting Features

Student, The dates of the coming discounts and the expiry dates can be seen by
Brand the students which will display a Brand on their products.

Table No. 2.1: Benefits and Perspective of Point of Sale

8|Page
 Point of Sale

2.7 USERS

Users of this and their descriptions are given in the below Table No. 2.2:

Representative Students, Brands

Description User is a sensible person and wants quick work.

Type Primary

Responsibilities He will use the system directly and will up to date with the system.

If the user will totally satisfy with this system it will be success of the
Success Criteria
Project otherwise, project will fail.

Table No. 2.2: Users for Point of Sale

2.8 SKILLS OF TEAM MEMBERS

Table No. 2.3 is showing the skills of the developers working on this project.
Sr. Name Skills Email
JAVA, XML, SQLite, Firebase,
1 M. Waleed waleedislive@gmail.com
MS Office Professional, Adobe Photoshop.
JAVA, XML, SQLite, MS Office
2 M. Shoaib mughalshoaib15@gmail.com
Professional.
Table No. 2.3: Skills of Team Members

9|Page
 Point of
Sale

2.9 SCOPE OF THE SYSTEM

Main scope of this project is to assist and facilitate the Students and the Brands to gain
fruitful time from latest technology [4, 6]. It assures students and the brands to consume the
latest technology. The main purpose of this project is to make interest of students and brands to
sell and purchase with attractive interface.
We planned to make an android system which can be placed online. It will not only help
the students but also the brands can check their data belong to this system on their dashboard.
However, we discussed some steps [23]:
 Focused to provide a better way to consume Students and Brands time.
 Providing an attractive interface.
 Assuring our users that the technology is useful too.
 Provide free advertising platform for the Brands.
 Provide a platform to the student to avail the offers easily.

 Using Firebase for our database as it is the latest technology and secure database for our
app.

2.10 USABILITY

It is important to include usability activities in our project; we can build in the time and resources
to carry out those activities [24]. We will use the step by step usability guide to better understand
which activities fit our needs to include in our project.
In this project, usability of Point of Sale is effective but according to Minhaj University Strength.
In Minhaj University Lahore, there are 12,000+ students are studying. That means there’s a good
reason for different brands to come over to this platform and be part of this amazing project.
Brands can happily use this service as it is free for every brand. If this app attracts brands,
it directly means that there’s high attractiveness for students too as there’ll be much brands for
offering them their best services.

10 | P a g e
 Point of Sale

2.11 SUPPORTABILITY

Our App will run in Android Mobile Phone and it will run from API level 19 to above
[25]. Any Android Mobile Phone system will support this App. This app will run effectively or
component can be kept running after deployment. Based on resources that include quality
documentations, diagnostic information, and both knowledgeable and available technical staff.

2.12 SOFTWARE AND HARDWARE REQUIREMENTS

2.12.1 HARDWARE REQUIREMENTS

 Processor – Core 2 Duo.

 RAM - 1.00 GB and above.
 Hard Drive - 6 MB Drive space and above.

2.12.2 SOFTWARE REQUIREMENTS

 Android 4.4 (KitKat) or above.

2.13 TOOLS REQUIREMENTS

 Android Studio latest (Tool used for designing and programming of the application).
 Android Emulator (Tool for checking the output).
 Microsoft Office (For presentation and many other tasks).
 Operating System: Android.
 Database: Firebase.
 Adobe Photoshop.
 Balsmiq.
 IODraw.

11 | P a g e
 CHAPTER 3

ANALYSIS AND DESIGN

 Point of
Sale

3.1 INTRODUCTION

After requirement gathering phase, we do System analysis. In first step of System analysis we
observe the existing system, after that we gather requirements and domain of proposed (new) system.
Both systems either existing or new are equally important. In our case we proposed a new system.
When we create a new system, it requires complex procedure and creative thoughts; but on the other
hand, understanding the old system may also require more difficulties and problems. So, if the
requirements are not clear and no understanding of the implementations, an ambiguous situation is
created and sometimes may lead to diverse from solution.

Point of Sale System provides the facility to the Students and Brands to avail the
opportunity of selling and buying. User can easily register on this application if he/she is
belonging to some Brand and the student of the Minhaj University. Otherwise the system will not
allow signing up on the application. Because, we use Google Authentications for registration of
the students which is provided by the University for sign up on the system.

3.2 PROPOSED SYSTEM

Our proposed system will provide the facility of our MUL students and different brands
as well. By using our Point of Sale app we facilitate the students of our university to check the
different brands offer and avail those offers as well. There is no need to go out physically or call
the franchise or look for the offers on social pages, our students just need to install the app and
get the fruitful experience.

13 | P a g e
 Point of Sale

3.3 PERFORMANCE

This application gives a responsiveness and stability under a particular workload. This
application gives a good performance device with at least 1 GB of RAM and 10 MB of free space.
This app doesn’t save a lot of caches that results a very effective performance in devices. This app
requires internet as all the processing will go over network. So, in the absence of internet, the app
won’t be able to make any action as it will not have saved any local caches in user’s phone/device.

3.4 USER INTERFACES

User interface must be user friendly and easily understandable. User interfaces must be
creating in GUI. It means system describe the function into graphical user interface. We have
created app’s very basic UI over a software called “MALSMIQ”. In this software, we have
created a very simple layout for our user and brands so that even illiterate could be able to use
this application very easily.

3.5 DEVELOPMENT METHODOLOGY

Android Studio is being chosen because the requirements for our application were known
before hand and the objective of our application Point of Sale development is the computerized
of an already existing time-consuming system. Android Studio is an official software
development tool for Android Application Development.
Methodology that we selected for the development of this application is Waterfall
MODEL; ID is lightweight, efficient, low-risk, predictable, scientific, and the fun way to develop
software.

14 | P a g e
 Point of
Sale

The waterfall model of development requires customers for a system to commit to a set of
requirements before design begins and the designer to commit to particular design strategies before
implementation. Changes to the requirements require work of the requirements, design and
implementation. However, the separation of design and implementation should lead to well
documented systems that are amenable to change. By contrast, an evolutionary approach to
development allows requirements and design decisions to be delayed but also leads to software that
maybe poorly structured and difficult to understand and maintain. In a waterfall development
process, customer identify all requirement at once, the services to be provided by the system.

3.6 USER FRIENDLY

The interface of the system is user friendly and user can easily understand this
application. For every category of product, we use a different interface in User’s home page. For
brands, for every specific functionality, we use a separate slider.

3.7 PORTABILITY

The ease with which a system or component can be transferred from one environment to
another. Our app’s data is quite portable as we are using Firebase for our database. We can share
our data over different technologies or systems.

3.8 SYSTEM INCOMPLETE

They identify which of the services are most important and which are least important to
them. The allocation of services to this system depends on the service priority with the highest
priority services delivered first. During development, future requirements analysis for later
increment scan takes place, but requirements changes are not done as it will be cover in
maintenance phase. As new system is completed, the complete project is examined.

15 | P a g e
 Point of Sale

3.9 SPECIFIC FUNCTIONAL REQUIREMENTS AND PROJECT FILE

STRUCTURE

As for this app, we have maintained the functionality of our system simple and user friendly.
Point of Sale’s functional requirements are exactly according to students and brands need.
Features in this project:
 Firebase Real Time Database.
 Firebase Authentication.
 Firebase Storage.

[Note: As there are three login systems in our app (Student, Brand, and Admin). When
they login successfully go to the dashboard]

3.10 LIST OF ACTIVITIES FILES IN THIS PROJECT

Lists are divided up in three categories:

 Admin Activities.

 AddAdmin.java  Login.java

 AddUser.java  Menu.java

 AuthBrand.java  RemoveAdmin.java

 DeactivateBrand.java  ViewBrands.java

 DeactivateUsers.java  ViewUsers.java
 Inbox.java

 Brand Activities.

 AddOffer.java  Home.java

 AuthRequestOrder.java  Inbox.java

 EditProfile.java  Index.java

16 | P a g e
 Point of
Sale

 Login.java  SignUp.java

 SaleRecord.java  BrandsCurrentOffers.java
 User Activities.

 Home.java  Setting.java

 Login.java  ShowOffers.java

 Pendings.java

There are some other activities which resides under no specific category like:
 SplashScreen.java
 HomeScreeen.java

3.11 LIST OF XML FILES IN THIS PROJECT

These are the following layout files for this project:

 admin_add_admin.xml  brands_settings.xml

 admin_add_user.xml  brands_home.xml

 admin_auth_brands.xml  brands_login.xml

 admin_deactivated_brands.xml  brands_sale_record.xml

 admin_deactivated_users.xml  brands_sign_up.xml

 admin_inbox.xml  brands_view_current_offers.xml

 admin_inbox_contacts.xml  user_home.xml

 admin_login.xml  user_login.xml

 admin_menu.xml  user_pendings.xml

 admin_remove_admin.xml  user_settings.xml

 admin_view_brands.xml  user_show_offers.xml

 admin_view_users.xml  home.xml

 brands_auth_requests.xml  splash_screen.xml

17 | P a g e
 Point of Sale

3.12 LIST OF OTHER JAVA FILES IN THIS PROJECT

 admin_auth_adapter.java  brand_auth_offer_adapter.java

 admin_deactivated_brands_adapter.j  brand_sale_record_adapter.java
ava
 brand_tab_pager_adapter.java
 admin_deactivated_users_adapter.ja
va  brand_view_offers_adapter.java

 admin_inbox_contacts_adapter.java  users_pending_adapter.java

 admin_inbox_adapter.java  users_show_offers_adapter.java

 admin_remove_admin_adapter.java  admin_db.java

 admin_view_brands_adapter.java  users_db.java

 admin_view_users_adapter.java  brands_db.java

The above-mentioned java files with their model classes for data passing.

3.13 CLASSIFICATION OF FUNCTIONAL REQUIREMENTS

These are the following functional requirements for Point of Sale:

For Admin:
 An admin can add users.
 An admin can make more admins.
 Admins can authenticate brands.
 An admin can view current users and block them if he wants.
 An admin can block the brand or reactivate any blocked brand.
 An admin can chat with the brands.

18 | P a g e
 Point of
Sale

For Brands:
 A brand can authenticate user’s discount requests or reject if any uncertain condition
happened from the user.
 A brand can add new offers as many as he wants.
 A brand can view its current offers.
 A brand can see his sale record.
 Brand also can chat with the admin. For the chat panel we will use Firebase.
 A brand can change his name, profile picture and password.

For Users:
 Users can get any offer served by the brands.
 Users can see his pending requested offers.
 Users also can edit this name, profile picture and password.

3.14 NON-FUNCTIONAL REQUIREMENTS

Developer must meet these given Non-Functional Requirements:

 Brands/Users use Google Authentications for implementing this app.
 Database use for this app should be Firebase.
 Data should be sync automatically throughout the app.

3.15 PROJECT FEASIBILITY

In our project, we test the technical, operational and economic feasibility. It completely
shows that our project is completely feasible. The feasibility relates with the risk analysis in
many different ways. As the risk for the app increases, the quality of feasibility of production
will decrease directly. Because of that, the analysis for feasibility of Point of Sale has
categorized into these two categories:
 Technical Feasibility for Point of Sale.

19 | P a g e
 Point of Sale

 Operational Feasibility for Point of Sale.

3.15.1 TECHNICAL FEASIBILITY FOR POINT OF SALE

Our Project is going to be developed by implementing the available modern technologies

(Android Mobile Devices). That are well established and highly secured with their distinctive
features. Our application is technically feasible as working of our project as perform with current
equipment’s. This feasibility report provides technical guarantee of accuracy, security and less
costly reliable app.

3.15.2 OPERATIONAL FEASIBILITY FOR POINT OF SALE

Our application will be operationally feasible as it will be able to satisfy the user’s
requirements of data in timely manner. So, all the working and operations of the application
fulfill the users need accurately. Our project will be operationally feasible as it will handle large
amount of data, it is fast and accurate information about every data will be provided.

3.16 TIME ESTIMATION

The Table No. 3.1 is showing the duration required to complete this project. In which, we
have shown via Gantt Chart that this project will take up to 8 months for completion.

Table No. 3.1: Time Estimation Gantt Chart for Point of Sale

20 | P a g e
 Point of
Sale

3.17 PROJECT COST ESTIMATION/ECONOMIC FEASIBILITY

We are using a very well-known method which is called “Line of Code” (LOC). By
viewing its domain and functionality this project is very feasible. We estimate cost to our front
end and back end application on the basis of estimated lines of codes for our application is
100,000+ PKR.
We will charge Rs.8/line.
Estimated cost for the application is:
Estimated cost = No. of estimated lines *cost per line
No. of estimated lines = 12,500+
Estimated cost = 12,500 * 8
Estimated cost = 100k

3.17.1 SERVER CONFIGURATION

After installing all features and services = 5000 only/- Miscellaneous charges. Some of the
other charges also included the project development for this purpose we charged Rs. 1000/- only/

3.17.2 TOTAL ESTIMATED COST BECOMES

100,000 + 5,000+ 1000 = 106,000

So, the total estimated cost for our project is total only.
This app is economically feasible as according to our technical reports it does not require any
additional software or hardware.

3.18 USE CASE MODELING

For Use Case Modeling we studied a research paper [26]. Point of Sale has categorized in
three categorize:
 User.  Brand. Admin.

21 | P a g e
 Point of Sale

3.19 REGISTERED USER

Figure 3.1 represents the features available to the users which includes the view categories,
select and get offers, edit profile, view pending requests and logout.

Figure No. 3.1: Use Case Model for Registered Users

22 | P a g e
 Point of Sale

3.20 USE CASE DIAGRAM FOR BRAND

Figure 3.2 represents the features available to the brands which includes add offers, inbox,
authenticate requests, view offers made, view sale records, edit profile and logout.

Figure No. 3.2: Use Case Model for Registered Brands

23 | P a g e
 Point of Sale

3.21 USE CASE DIAGRAM FOR ADMIN

Figure 3.3 represents the features available to the admin which includes inbox add users, add
admin, authenticate brands, view users, view deactivated users, view brands, view deactivated
brands, remove admin and logout.

Figure No. 3.3: Use Case Model for Admins

24 | P a g e
 Point of Sale

3.22 BEHAVIORAL MODELING

When we refer to external events, we mean those that pass between the system and its
actors (active are external to the system). Conversely, internal events are passed between objects
that live inside of the system.
As mentioned above, in the UML, we model four kinds of events:
 Signals.
 Calls.
 Passing of time.
 Change in the state.

3.23 DATA MODELING

We’re doing Data modeling in Point of Sale for the following reasons:
 To manage the details in large systems.
 To communicate a common meaning for all system elements.
 To document the features of the system.
 To locate the error and omissions in the system.

The data dictionary in Point of Sale contains two types of descriptions as following:

 Data Elements.
 Data Structures.

25 | P a g e
 Point of Sale

3.24 SEQUENCE DIAGRAM OF USER

Sequence diagram for all users is given below in Figure 3.4, 3.5, 3.6, 3.7. These figures are
representing how the users (all brands, users and admin) is going to access the Point of Sale.

Figure No. 3.4: Sequence Diagram of Users (overall)

26 | P a g e
 Point of Sale

Figure No. 3.5: Sequence Diagram of Admin Panel

Figure No. 3.6: Sequence Diagram of Brand Panel

27 | P a g e
 Point of Sale

Figure No. 3.7: Sequence Diagram of User Panel

3.25 AUTHENTICATION SYSTEM FOR POINT OF SALE

We are using Firebase Email Authentication system for authentications of Point of Sale
plus admin permission. For the Logging in, user/brand need the following data:

3.25.1 USERNAME AND EMAIL

The identifier user/brand need email and username to access Realtime DB. After clicking
the Log in button, this is the first info that is transmitted to Firebase Authentication System.

3.25.2 PASSWORD FOR SIGN IN

This field is not encrypted before transmitting to Firebase Authentication System as firebase
don’t accept any encrypted data and return process failure message or incorrect form error.

28 | P a g e
 Point of Sale

3.26 DATABASE HIERARCHY STRUCTURE FOR ADMIN

For the database hierarchical structure, we have studied different database books and
research papers [27]. The given Figure 3.8 represents the admin database:

Figure No. 3.8: Database Hierarchy for Admin

29 | P a g e
 Point of Sale

3.27 DATABASE HIERARCHY STRUCTURE FOR BRAND

For the database hierarchical structure, we have studied different database books and
research papers [27]. The given Figure 3.9 represents the brand database:

Figure No. 3.9: Database Hierarchy for Brands

30 | P a g e
 Point of Sale

3.28 DATABASE HIERARCHY STRUCTURE FOR USER

For the database hierarchical structure, we have studied different database books and
research papers [27]. The given Figure 3.10 represents the user database:

Figure No. 3.10: Database Hierarchy for Users

31 | P a g e
 Point of Sale

3.29 CONTEXT DIAGRAM

Context Diagram for Point of Sale is representing all the features that will be working in this
app. Context Diagram is showing level 0, 1 and 2 for DFD of Point of Sale [28]. These
features are showing in the Figure 3.11, 3.12, 3.13.

Figure No. 3.11: Context Diagram Level 0 for Point of Sale

32 | P a g e
 Point of Sale

Figure No. 3.12: Context Diagram Level 1 for Point of Sale

Figure No. 3.13: Context Diagram level 2 for Point of Sale

33 | P a g e
 Point of Sale

3.30 DATA FLOW DIAGRAM

Data Flow Diagram level 0 for Point of Sale is representing all the flow of data over database
which are shown in Figure 3.14.

Figure No. 3.14: Data Flow Diagram for Point of Sale

34 | P a g e
 CHAPTER 4

IMPLEMENTATION
 Point of Sale

4.1 INPUT AND OUTPUT

For the implementation of the app, we have studied through these references [29, 30, 31].

4.1.1 INPUT OPTIONS FOR USER

 User can tab on User Panel and must Login.

 User can select any category for what he is interested.
 User can tab on GET THIS button to get any offer.

4.1.2 OUTPUT FOR USER

 User receives the Home page if the Login gets successful.

 User receives the data/offers according to the category he selected.
 User receive the success message if it gets successful.

4.1.3 INPUT OPTION FOR BRAND

 Brand user can tab on Brand Panel and must Login.

 Brand user can Authenticate Request.
 Brand user can move side by side in Pager Fragment to see different features.
 Brand user can tab on View Offers Made.
 Brand user can tab on View Sale Record.
 Brand user can Add the Offer.

4.1.4 OUTPUT FOR BRAND

 Brand user can see the Brands Home Page.

 Brand user receive and see the results in the Inbox screen.
 Brand user receive the Authenticate Request screen.

36 | P a g e
 Point of Sale

 Brand user receive the View Offer Made screen.

 Brand user receive the Sale Record screen.
 Brand user can receive the next activity by clicking on any button on the Brands Home.

4.1.5 INPUT OPTION FOR ADMIN

 Admin can tab on the Admin Panel and must Login.

 Admin can click on any Sign in the button to go to the next activity or Admin Panel
Home screen.
 Admin can input the details for the new users.
 Admin can input the details for an admin.
 Admin can click on the Inbox.

4.1.6 OUTPUT FOR ADMIN

 Admin can see the Home screen after Login.

 Admin receive the next activity by clicking on any button on the Home Panel.
 Admin receive the next activity for adding a user and admin.
 Admin can also receive the next activity to authenticate the user and brand.
 Admin can view the Inbox.

37 | P a g e
 Point of Sale

4.2 GUI

4.2.1 SPLASH SCREEN

Figure No. 4.1: Splash Screen Point of Sale

Figure 4.1 shows Splash Screen is starting screen for Point of Sale, this is the first screen that
the user will see after tab on the app icon.

38 | P a g e
 Point of Sale

4.2.2 SELECTION PANEL

Figure No. 4.2: Selection panel Point of Sale

Figure 4.2 shows Selection Panel screen where the user of the app will select for what
purpose he is using this application.

39 | P a g e
 Point of Sale

4.2.3 USER LOGIN PANEL

Figure No. 4.3: User login Point of Sale

Figure 4.3 shows User’s Login screen. The same way for Brand and Admin panel.

40 | P a g e
 Point of
Sale

4.2.4 USER DASHBOARD

Figure No. 4.4: User dashboard Point of Sale

Figure 4.4 shows User’s home screen where user can access to any category he wants.
Moreover, user can see his name with his profile picture and a Logout button. In action bar
there’s a drop-down menu where user can edit his profile and one button for seeing pending
requests for offers.

41 | P a g e
 Point of Sale

4.2.5 USER EDIT SETTINGS

Figure No. 4.6: Edit profile Point of Sale

Figure 4.6 shows Edit Profile screen. User can change his profile picture, username or
password. Brands have same settings in his profile.

42 | P a g e
 Point of Sale

4.2.6 ADMIN PANEL

Figure No. 4.7: Admin panel Point of Sale

Figure 4.7 shows the Admin Home panel screen with its rights and features.

43 | P a g e
 Point of Sale

4.2.7 ADD ADMIN

Figure No. 4.8: Add admin Point of Sale

Figure 4.8 shows admin can add more admins. Moreover, admin can add as many users as he
wants. The user screen has some fields with one more field for Email.

44 | P a g e
 Point of Sale

4.2.8 ALL BRANDS

Figure No. 4.10: View brands Point of Sale

Figure 4.10 shows admin can add or reject any brand if he wants. As you can see in the
above figure, admin can see detail for the brand and their account info and he can delete by just
clicking delete button.

45 | P a g e
 Point of Sale

4.2.9 BRANDS HOME

Figure No. 4.11: Brands home panel Point of Sale

After brands login, there is Home Panel for the brand. These are some features displaying in
the above given figure 4.11.

46 | P a g e
 Point of Sale

4.2.10 BRANDS CHAT PANEL

Figure No. 4.12: Chat panel Point of Sale

Figure 4.12 shows brands can chat with admin for any query, complain or any suggestion.

47 | P a g e
 Point of Sale

4.2.11 AUTHENTICATE REQUESTS

Figure No. 4.13: User request auth Point of Sale

Figure 4.13 shows brand can authenticate requests from the users for discounts by clicking
the tick button or can reject if any misbehave happened by the user at the site.

48 | P a g e
 Point of Sale

4.2.12 ADD OFFER

Figure No. 4.14: Add offer Point of Sale

Figure 4.14 shows brands can add any new offer by filling this description form and
taping the button CREATE OFFER.

49 | P a g e
CHAPTER 5

TESTING
 Point of Sale

For Android Application Testing we studied a research paper and conducted these tests
according to the requirements and standards [32, 33]. By these testing’s, we clarify that the app
is completely meetings it's all requirements.

5.1 TEST CASES

5.1.1 USER PANEL TEST CASE

Test Case ID: Test No. 01

Test Priority (Low/Medium/High): High

Module Name: User Panel

Test Title: Verify working of the User Panel

Pre-conditions: User Login Panel

No. Test Case Name Test Data Expected Result Actual Result Status

Navigate to Login User is navigated to User

1 Email with Password User should be able to login Pass
Screen Home Screen

Show data with relevant

2 Select Category Click any category Showed relevant data Pass
category

3 Get Offer Click on Get Offer button Opeartion Success message Pop up message of success Pass

4 Edit Profile Edit username Name updated Name updated succesfully Pass

Post-conditions: User is performing all tasks successfully with no error

51 | P a g e
 Point of Sale

5.1.2 BRAND PANEL TEST CASE

Test Case ID: Test No. 02

Test Priority (Low/Medium/High): High

Module Name: Brand Panel

Test Title: Verify working of the Brand Panel

Pre-conditions: Brand Login Panel

No. Test Case Name Test Data Expected Result Actual Result Status

Navigate to Login User is navigated to Brand

1 Email with Password Brand should be able to login Pass
Screen Home Screen

2 Add Offer Fill all Add offer Data Offer Added Offer Added succesfully Pass

Click on Auth Request Accepted/Rejected

3 Auth Requests Accept or Reject Offer Pass
button Successfully

4 View Current Offers Click on View Offer button All data show Data showed on Screen Pass

Post-conditions: Brand is performing all tasks successfully with no error

52 | P a g e
 Point of Sale

5.1.3 ADMIN PANEL TEST CASE

Test Case ID: Test No. 03

Test Priority (Low/Medium/High): High

Module Name: Admin Panel

Test Title: Verify working of the Admin Panel

Pre-conditions: Admin Login Panel

No. Test Case Name Test Data Expected Result Actual Result Status

Navigate to Login Admin should be able to User is navigated to

1 Email with Password Pass
Screen login Admin Home Screen
Admin/User Added
2 Add Admin/User Email with Password Admin/User Added Pass
succesfully
Click on Accept/Reject Accepted/Rejected
3 Auth Brand Accept or Reject Brand Pass
Button Successfully
Admin/User removed
4 Remove Admin/User Email with Password Admin/User removed Pass
successfully

Post-conditions: Admin is performing all tasks successfully with no error

53 | P a g e
 Point of Sale

5.2 ANDROID UNIT TESTING FOR POINT OF SALE

Android testing is based on JUnit is general, a JUnit test is a method whose statements
test a part of the app. We organize test methods into classes called test cases. We build one or
more test classes and use a test runner to execute them on our local machine. With Android
Studio, we build one or more test source files into an Android test app and use it to test the app
on the emulator or physical android device.

5.3 UNIT TESTING FOR POINT OF SALE

Unit tests are the fundamental tests in app testing strategy. By creating and running unit
tests against code, can easily verify that the logic of individual’s units is correct. Running unit
tests after every build helps to quickly catch and fix software regression introduce by code
changes to the app. A unit testing generally exercises the functionality of the smallest possible
unit of the code (which could be a method, class or component) in repeatable way.

5.4 VALIDATION TESTING FOR POINT OF SALE

In Integration testing, the software is assembled as a package. Validation Testing is

completely associated with requirement satisfaction of customers. In Point of Sale, this testing
checks weather all functional requirements of customer are satisfied or not. According to this
test, the project is tested and found to be satisfactory for functional characteristics, behavioral
characteristics and performance requirement. It is also found to have good documentation up to
the last stage. So, the performance characteristics conform to specification and are accepted.

54 | P a g e
 Point of
Sale

5.5 PROJECT (POINT OF SALE) TESTING

In this session, we try to overcome all the problems of our project. For this purpose, we
conduct a session of testing. We run our project.
First of all, we try to get registered. For this we go on Sign Up form for Brand. Fill the form, and
here we get results as we expected. We tried with every single combination of input and
checkout our checks are working completely and showing on error while any kind of data entry.
Secondly, we visit our app as a user. There we see that a user doesn’t really need to enter any
input. All he has to do is just clicking and checkout what he really needs. This means our app cannot
go wrong anywhere in user panel as there is no input chance from user that can go wrong.

Then, we see that after login of the user all edit profile settings where user can add or
change data. We checked all checks properly and found no error in this module. Users can not
add any redundant data here means there is no chance of any error from this module.
Then, we see admin panel where we check all features with their checks so we could
make sure that there’s no error in our admin panel. We added testing data and found no problem
here. We tested some brand authentications and found app has no error in this module too.

5.6 POINT OF SALE TESTING RESULTS

The application is tested according to the given functional and non-functional requirements and
found that the app is meeting all its requirement and found no error while testing! The project is
completely ready to deliver to the customer.

55 | P a g e
CHAPTER 6

CONCLUSION
 Point of
Sale

6.1 CONCLUSION

Today world is of Mobile Computing and people are using the smart phones and internet
in everywhere rather than computers. Especially, students are too much in touch with the
technologies and as well as the companies. Point of Sale app provides the facility to the MUL
students to see the discounts offers of the different brands and avail those offers and on the other
hand the same opportunity for the brands to upload their offers through this app so that their
number of sales increase as well as do some advertisement for free as it is the world of the
mobile. This app will give equal benefits to the both sides as both parties will be happy to give
their services over this platform.

6.2 BENEFITS OF POINT OF SALE

Any app is identified by the services and UI of the app offered to the user. The benefits of
Point of Sale are as follows:
 This app will save time and headache of keeping in touch with every page.
 It is more efficient than local advertisements.
 It can be used anywhere with the internet connection.
 It will give you the different brands discount in one platform.
 It will increase the sale of the brands especially the newly introduced brands.

 It will help university in making a good impression among students as this app will make
edge over other universities.

6.3 LIMITATIONS

 It is Android Based Application so the internet connection is necessary to access it.

57 | P a g e
 Point of
Sale

REFERENCE

(1) Wolfinbarger, M., & Gilly, M. C. (2001). Shopping online for freedom, control, and fun.
California management review, 43(2), 34-55.
(2) Lee, G. G., & Lin, H. F. (2005). Customer perceptions of e-service quality in online
shopping. International Journal of Retail & Distribution Management, 33(2), 161-176.
(3) Kapp, J. M., Peters, C., & Oliver, D. P. (2013). Research recruitment using Facebook
advertising: big potential, big challenges. Journal of Cancer Education, 28(1), 134-137.
(4) Developers, A. (2011). What is android.

(5) Android Developers (https://developer.android.com/).

(6) Google Firebase (https://firebase.google.com/).

(7) Moroney, L., Moroney, & Anglin. (2017). Definitive Guide to Firebase. Apress.
(8) Sonwane, S., Takalkar, S., Kalyankar, S., Wanare, K., & Baviskar, S. (2017). Doctor
Patient Data Sharing Using Android Chat Application. International Journal of Recent
Trends Ni Engineering & Research, 2455-1457.
(9) Moroney, L. (2017). The firebase realtime database. In The Definitive Guide to Firebase
(pp. 51-71). Apress, Berkeley, CA.
(10) Zimányi, P. D. E., Martínez, G., & López, P. (2018). REAL-TIME DATABASES AND
FIREBASE.

(11) Tutorial Point (https://www.tutorialspoint.com/android/index.htm).

(12) Software Engineering – A Practitioner’s Approach by Roger S. Pressman 6th Edition.

(13) IT Project Management, by Kathy Schwalbe 6th Edition.
(14) Meier, R. (2012). Professional Android 4 application development. John Wiley & Sons.
(15) Sarma, B. P., Li, N., Gates, C., Potharaju, R., Nita-Rotaru, C., & Molloy, I. (2012, June).
Android permissions: a perspective combining risks and benefits. In Proceedings of the
17th ACM symposium on Access Control Models and Technologies (pp. 13-22). ACM.
(16) Brahler, S. (2010). Analysis of the android architecture. Karlsruhe institute for
technology, 7(8).

58 | P a g e
 Point of
Sale

(17) Stack overflow (https://stackoverflow.com/).

(18) Fernandes, E., Chen, Q. A., Paupore, J., Essl, G., Halderman, J. A., Mao, Z. M., &
Prakash, A. (2016, February). Android ui deception revisited: Attacks and defenses. In
International Conference on Financial Cryptography and Data Security (pp. 41-59).
Springer, Berlin, Heidelberg.
(19) Li, W. J., Yen, C., Lin, Y. S., Tung, S. C., & Huang, S. (2018, February). JustIoT Internet
of Things based on the Firebase real-time database. In 2018 IEEE International
Conference on Smart Manufacturing, Industrial & Logistics Engineering (SMILE) (pp. 43-
47). IEEE.

(20) Udemy (https://www.udemy.com/topic/android-development/).

(21) Nudelman, G. (2013). Android design patterns: interaction design solutions for
developers. John Wiley & Sons.
(22) Rogers, R., Lombardo, J., Mednieks, Z., & Meike, B. (2009). Android application
development: Programming with the Google SDK. O'Reilly Media, Inc.
(23) Head First Android Development: A Brain-Friendly Guide (Book by David Griffiths and
Dawn Griffiths).
(24) Hello, Android: Introducing Google's Mobile Development Platform (Book by Ed Burnette).
(25) Professional Android 4 Application Development (Book by Reto Meier).
(26) Cockburn, A. (2000). Writing effective use cases for designers. Addison-Wesley
Professional.
(27) Database System by Addison Wesley 4th Edition.
(28) Lucid Chart (https://www.lucidchart.com/pages/data-flow-diagram ).
(29) Android UI Design (Book by Jessica Thornsby).

(30) GitHub (https://github.com/).

(31) Android Hive (https://www.androidhive.info/).

(32) Gao, J., Bai, X., Tsai, W. T., & Uehara, T. (2014). Mobile application testing: a tutorial.
Computer, 47(2), 46-55.
(33) Kaasila, J., Ferreira, D., Kostakos, V., & Ojala, T. (2012, December). Testdroid:
automated remote UI testing on Android. In Proceedings of the 11th International
Conference on Mobile and Ubiquitous Multimedia (p. 28). ACM.

59 | P a g e