Development Money Diary Application Models on

Android
Debi Michael Takeuchi Muarif Gustiar Aliyudin
Computer Science Department Computer Science Department Computer Science Department
BINUS Online Learning BINUS Online Learning BINUS Online Learning
Bina Nusantara University Bina Nusantara University Bina Nusantara University
Jakarta, Indonesia 11480 Jakarta, Indonesia 11480 Jakarta, Indonesia 11480
debi@binus.ac.id michael.takeuchi@binus.ac.id muarif.aliyudin@binus.ac.id

Pratiwi Wahyu Nurhayati

Emny Harna Yossy*
Computer Science Department
Computer Science Department
BINUS Online Learning
BINUS Online Learning,
Bina Nusantara University
Education & Technology, Research Interest Group
Jakarta, Indonesia 11480
Bina Nusantara University
pratiwi.nurhayati@binus.ac.id
Jakarta, Indonesia 11480
emmy.yossy@binus.ac.id

Abstract—Today many people have difficulty controlling their management application is needed.
time and finances. This certainly affects self-productivity and Money management applications are made to help people
work productivity in the office / business. With the establishment who have difficulties in controlling their time and finances.
of the Money Diary application, it is expected to become a solute They can easily access various applications that will indirectly
task and money management application. The purpose of making affect their finances and spend their time. This will certainly
this application is to assist users in managing and managing their disrupt productivity and disrupt the flow of personal and
tasks and finances all at once in an application. The research company finances.
method used in data collection is literature study and indirect
observation. The application development method uses the system Based on this background, several problems can be
development life cycle method with the waterfall model. This identified, namely applications that can be used to control
model uses a systematic and sequential approach that starts at the financial rates. So, based on the identification of the problem
level of requirement to the level of maintenance. This application above, the problem limitation is an application that can be used
is based on Android developed with the Java programming to record and plan financial rates and plan daily tasks.
language. The result is a money diary application that can be used Therefore, researchers will conduct research on the development
to daily actions, to remind users of the need to pay bills on time, to of a daily money application model on Android. This research
facilitate financial management for users, to remind users to was conducted with the aim to produce applications that can
perform certain actions that were previously planned. facilitate users to manage daily activities, remind users to pay
bills on time, make it easy for users to manage finances, remind
Keywords—mobile application, system development life cycle,
money diary, android users to carry out certain activities that have been previously
scheduled.
I. INTRODUCTION
II. LITERATURE REVIEW
In an era that is completely modern as it is today,
smartphones have become very common to have and use in Mobile applications are ready-made programs that are
everyday life. The Project Management Institute's research in designed to make it easy for users and applications are used
2018 showed that, on average, organizations wasted 9.9% of by the intended target while the cell phone can be
project funds due to "poor project performance," while 43% of interpreted as moving from one place to another. Can be
projects were not completed in the budget and nearly half (48%) interpreted as an application that runs on mobile devices or
did not finish on time. This is related to the inability of better known as smartphones. Using a mobile application
personnel in managing their duties and finances [1]. can easily carry out various activities ranging from
In terms of smartphone deployment, Android is at the first entertainment, sales, learning, doing office work, browsing
level with the most market share. This is likely to have a direct and so on [3]. One of the mobile application applications in
or indirect impact on the number of applications developed with the field of services that can be accessed by mobile users is
Android-based to facilitate human life [2]. Online market food delivery services, online motorcycle taxi
applications are becoming one of the applications that are transportation, health consultations, and so on. This mobile
mushrooming and at the same time are causes of financial application makes it easy for us to meet our daily needs in a
control are not well controlled. This is due to several payment more practical and flexible way. The application will be
features such as credit and debit. Therefore, a money developed in a mobile platform, namely Android.
*Corresponding Author

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
142
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.
 Then system evaluations such as the User Acceptance design and logical design, implementation to build a proposed
Test and Performance Test are carried out. User Acceptance system, testing to test using the user method acceptance test
Test is a test that will be carried out by the Team with the and performance test, and maintenance to maintain the function
client when the system has been developed [4]. The can run as expected, described as follows:
development team initially planned to conduct a
demonstration and testing process for fellow students. After
that, the development team will continue testing the client's
activities. Testing activities will be carried out by the client
to ensure the system is in accordance with the desired
requirements. The ultimate goal of this activity is to get the Fig. 1. Waterfall Model
client's agreement that the requirements have been met.
Performance Testing is a testing process that aims to
determine and measure the run-time performance of the
IV. RESULT AND DISCUSSION
system. This trial will be carried out on the whole system.
Then will be tested on the response time of the system when A. Process Analysis
an event is carried out by the user. In addition, the In this application, users can input transactions or daily
objectives of Performance Testing include, (1) documenting schedules / tasks. Users can also delete or change a
test objectives, test requirements, test designs, test transaction or schedule that has been previously set if there
procedures and other information, (2) providing a means for is indeed an error in inputting the data needed. Later, users
feedback interaction with users and (3) determining the can view financial reports and daily / weekly / monthly
deliverables of the development process and processes schedules that they made earlier. The following is an
testing. illustration of how Money Diary Application works through
Research development uses the system development life use case diagrams and activity diagrams.
cycle (SDLC) method. System development life cycle is
described by the software phase and the sequence of phases
that are run [5]. Each phase produces the results needed by
the next phase in the life cycle. Renewal requirements in
design. The code is purchased according to a design called
the development phase. After coding and development, the
verification phase approves the implementation
requirements for the requirements. The evaluation team
follows the Software Life Cycle (STLC) which is like the
development cycle followed by the development team [6].
This research uses the waterfall method. Waterfall was
chosen because it is easy to understand, easy to use,
provides structure to experienced staff, milestones are well
understood, sets requirements stability, good for
management control (plan, staff, track), works well when
quality is more important than cost or schedule [7].
Design application development using the Unified
Modeling Language (UML). UML is a modeling language
that is intended to provide a standard way to visualize
system designs (generally software) through object-oriented
diagramming schemes[8]. UML is recognized by the
International Organization for Standardization (ISO) as an
industry standard for modeling intensive software systems.
UML is composed by various types of diagrams, each
designed for specific modeling purposes[9]. UML
diagrams, which are showed in application design are: use
case diagram, activity diagram, architecture diagram, entity
relationship diagrams, and class diagrams,
III. RESEARCH METHODS
The money diary application was developed using the
system development life cycle (SDLC) method with the
waterfall model, the design of the design uses a unified
modeling language (UML), the design of the application uses Fig. 2. Use Case Diagram
eight golden rules [10], and the application testing uses the
black box testing method, namely user acceptance test. The
stages in designing a money diary application are requirements
by observing and studying literature to collect the data needed,
design to describe the data that has been obtained into physical

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
143
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.
 C. Database Design
Some data stores generated include users, transactions,
tasks, notification types, repeat types. Thus, it can be
determined relations between the tables as follows:

Fig. 3. Activity Diagram

This application can help users in controlling their

finances. In the future this application is also developed in
web form. However, due to the rapid growth of
smartphones, the authors optimize the Android-based
applications first.
The hardware specifications for a user's smartphone are
as follows: 1 GB RAM, 8 GB internal memory, internet
connection. While the software specifications for
smartphone users are Android 4.2 Jellybean. Fig. 5. Entity Relationship Diagram

B. Application Design
In its implementation, in the deployment view, Money
Diary App will use Three-Tier Architecture. In Tier 1 the
web browser as a client is a representation of the interface
between the user and the system. Tier 1 (Client) and tier 2
(application server) are designed separately because they
require an independence to accommodate changes that
might occur. Tier 2 consists of sub-tier web servers and
business logic.
Business Logic is represented as a controller. This sub-
tier has a method that can access the web server. Web
server sub-tier stores classes that will be used by the system
to carry out its functions and the web server also has a
method that can access data in tier 3, namely the database
server for application purposes. Tier 3 consists of a database Fig. 6. Class Diagram
server that stores data needed by the system to carry out its
functions.
D. Application Menus
Menus produced include:
1. Registration menu to register as a member of the system.

Fig. 4. Architecture Diagram

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
144
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.
 Fig. 10. Input Transaction Menu

Fig. 7. Registration Menu 5. Task/ schedule input menu for adding schedules and
reminders as desired by the user.
2. Login menu to enter the system and use the available
features.

Fig. 8. Login Menu

3. Edit profile menu to view your own profile and change your
self-description and profile photo. Fig. 11. Input Task Menu

6. Notification and repeat menu to make notifications on each

transaction.

Fig. 9. Profile Menu

4. Transaction input menu to add expense transactions

and reminders as desired by the user. Fig. 12. Notification Menu

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
145
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.
 Fig. 13. Repeat Menu

7. The delete and edit transactions menu is used to delete and

edit transactions that have been entered in the application.

Fig. 16. Logout Menu

E. System Evaluation
In the Money Diary app development project, of course
there will be a testing phase for checking and researching
the results of the system that has been built. There are 2
types of tests that will be carried out by the development
team, namely User Acceptance Test (UAT) and
performance testing. The team will provide a test scenario
that can be tested by the client. The preparation of this test
scenario is the responsibility of the tester of the UAT
development team and will display the possible scenarios of
each use case and the expected results that occur in the
system when the scenario is carried out. However, clients
Fig. 14. Delete and Edit Transaction Menu
can also carry out additional scenarios as long as they are
still within the scope of this project. This testing is expected
8. Report menu to find out transaction reports and schedule
to be carried out in less than 1 day.
reports that have been previously entered.
The stages carried out in preparing the UAT include the
following: (1) Requirement analysis; (2) Making a UAT
Test Plan; (3) Making a Scenario Test; (4) Running a Test
Case; (5) Documentation; (6) Consent from the client. The
tools that will be used to do this testing include: android-
based mobile phones will be used in this testing, namely
laptops belonging to the developer team members and
clients, laptops will be used in this testing, namely laptops
belonging to the developer team members and clients,
browser browser that will be used in this test is Google
Chrome or Mozilla Firefox.
The allocation of resources for testing is planned for 2
people for the role author, 1 person for the role admin, and
2 people for the role reader. This test will be run for all
planned use cases on this system. Use cases include: login,
logout, input transactions / tasks, create alarms / reminders,
make transactions / tasks repeat, delete transactions / tasks,
view Report transactions / tasks, change profiles, and
Fig. 15. Report Menu
change passwords.
Testing this system access will be used by the internet
9. Logout menu to exit the application. network of the client so that the performance of access to
the system depends only on network activity. In addition,
system performance will also be affected by limitations
such as limited database and server storage capacity owned

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
146
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.
 by our clients. The tools used for the testing process are 2020].
[8] V. Paradigm, “What is Unified Modeling Language (UML)?,” 2020.
Microsoft Visual Studio 2013 Test Professional. For
[Online]. Available: https://www.visual-paradigm.com/guide/uml-
resource allocation in the testing process, 2 people are unified-modeling-language/what-is-uml/. [Accessed: 18-May-2020].
allocated for the account creation role and 1 person for the [9] F. Haag, “UML Quick Reference,” 2017. [Online]. Available:
admin role. https://medium.com/federicohaag/uml-unified-modeling-language-
5a2a0c2fb973. [Accessed: 27-May-2020].
Below is a sample table regarding the performance
[10] Interaction Design Foundation, “Worksheet: How You Can Apply
testing scenario that will be performed. This includes the Shneiderman’s 8 Golden Rules to Your Interface Designs,” 2020.
type of event what will be done, the expected load time [Online]. Available: https://www.interaction-
(expected response time), and the actual load time is the design.org/literature/article/shneiderman-s-eight-golden-rules-will-
help-you-design-better-interfaces. [Accessed: 18-May-2020].
actual response time of the system. However, information
from the actual load time cannot be known, because the
actual load time can only be known when the system has
finished being developed.

TABLE I. EXAMPLE PERFORMANCE TESTING MONEY

Input Transaksi / Task Expected load Actual load
time time
User login 5 ms
User choose menu 5 ms
Planner → Money
User choose Budgets 5 ms
atau Bills
User input transaction / 20 ms
task

CONCLUSION

From these results it can be concluded that the application

makes it easy for users to manage daily activities, reminds
users to pay bills on time, makes it easy for users to manage
finances, reminds users to carry out certain activities that have
been previously scheduled. The resulting application is still not
perfect and can be further developed as developed in other
platforms like web and iOS to produce optimum results to meet
the needs of the community.

ACKNOWLEDGMENT
The author would like to thank the lecturers in the
Computer Science Department, BINUS Online Learning, Bina
Nusantara University for providing direction in designing this
application.
REFERENCES

[1] P. M. Institute, “Success in Disruptive Times | Expanding the Value

Delivery Landscape to Address the High Cost of Low Performance,”
2018.
[2] A. J. G. Silvius and C. M. Silvius., “Exploring Functionality of
Mobile Applications for Project Management,” Procedia Comput.
Sci., vol. 64, pp. 343 –351, 2015.
[3] R. Purnama, Introduction J2ME Java 2 Micro. Jakarta: Prestasi
Pustaka, 2010.
[4] D. W. Utomo, D. Kurniawan, and Y. P. Astuti, “Software Testing
Techniques in Evaluating the Hajj Monitoring Independent Service
System at the Ministry of Religion in Central Java Province,”
SIMETRIS, vol. 9, no. 2, 2018.
[5] R. S. Pressman, Software Engineering: A Practitioner’s Approach,
6th ed. McGraw-Hill, 2005.
[6] J. Pinheiro, “Software Development Life Cycle (SDLC) phases,”
2018. [Online]. Available:
https://medium.com/@jilvanpinheiro/software-development-life-
cycle-sdlc-phases-40d46afbe384. [Accessed: 27-May-2020].
[7] Chandu, “SDLC Models | Software Development Life Cycle
Models,” 2019. [Online]. Available:
https://medium.com/@chandu_22532/sdlc-models-software-
development-life-cycle-models-452a1e10d015. [Accessed: 27-May-

978-1-7281-7071-8/20/$31.00 ©2020 IEEE 13-14 August 2020

2020 International Conference on Information Management and Technology (ICIMTech)
147
Authorized licensed use limited to: UNIVERSITY OF WESTERN ONTARIO. Downloaded on November 09,2020 at 08:06:37 UTC from IEEE Xplore. Restrictions apply.