ICT311 Mobile Development: MVC Diagrams and Database Design Report

This report outlines the development of a mobile application designed for users to record and store trip details. It includes Model-View-Controller (MVC) diagrams for the Log UI, Setting UI, and Display UI, illustrating the application's functionality and data flow. The report also presents database schema designs for both a trip table and a settings table, utilizing SQLite for data storage. A reflection section discusses challenges encountered during development, such as fetching location data from Google Maps and updating saved data, and highlights lessons learned regarding Android application functionalities and interface design. The application aims to provide a user-friendly interface for storing trip information, including location data obtained through GPS, and offers fields for remarks and comments.

ICT311 TASK 2
i

Contents
List of figures.........................................................................................................................................1
Introduction...........................................................................................................................................2
1. MVC diagrams for each UI. There should be 3 MVC diagrams for 3 key Activities. The diagram
for Google Map Activity is not required................................................................................................3
2. Database schema design. There should be at least two tables, one for trips, and one for
Settings..................................................................................................................................................6
3. A final section of 'Reflections'. In this part, discuss any difficulties you had implementing the
program and how you solved those difficulties. Reflect on how the development process went for
you, what you learned, and what you might do differently next time..................................................8
Conclusion...........................................................................................................................................10
List of figures
Figure 1 MVC 1......................................................................................................................................2
Figure 2 MVC 2......................................................................................................................................3
Figure 3 MVC 3......................................................................................................................................4
Figure 4 Database Schema 1..................................................................................................................5
Figure 5 Database schema 2..................................................................................................................6
Figure 6 Code 1......................................................................................................................................7
Figure 7 code 2......................................................................................................................................8
ii

Introduction
This report is prepared for users by a start-up company to help in the store the personal trip record
to recognize in future if needed. This application will provide user to store the details and store in
application database itself and can be accessed anytime. This report describes the model view
control diagram for 3 different activities of this application along with an explanation and it also
provides database schema designs for a trip table and setting table with diagrams to understand in
an easy way. The application provides mainly 2 interfaces for trip details and user details and this will
save in the application database. This stored information can be accessed any time and trip details
can be modify or delete by the user in which it takes the location of place through GPS technology
and it can’t be entered manually by the user.
1

1. MVC diagrams for each UI. There should be 3 MVC
diagrams for 3 key Activities. The diagram for Google Map
Activity is not required.
The MVC implies for model view controller in which it defines the functionality of user interfaces as
this application consists of 3 User Interface which is designed for storing personal trip details. The 3
MVC are Log UI, Setting UI and display UI which describes the application functionality and their
fields which store the data relevant to the location by taking automatically or can say that from GPS
tracker it’ll determine the exact location.
The below MVC for Log user interface which is to determine the functionality as:
The Log user interface store the details of the trip which consist of various fields to save the data and
store in the database for future use. It consists of a title, the address of place which is determined
through GPS, date of trip, type of trip, destination and time period along with comment field which
stored remark and this interface having 2 buttons for save the record and cancel the record. The
controller is used for control the fields by inputting details, the model includes the fields which store
the data and pass to view level for entering and get output. The last one is view level which is used
for users to view the record.
Figure 1 MVC 1
2

The below MVC for Setting user interface which is to determine the functionality as:
This MVC design is for setting user interface in which consists of various fields used to store the
user’s detail and this application is developed for store personal trip record. So this provides fields to
user record as entering id, name, address, email, gender, and comment which is used to recognizing
any remark for that place. The controller recognizes the fields and model provides an area to enter
details of user and view level will show the inputted data information which will be saved
automatically.
Figure 2 MVC 2
The below MVC for Display user interface which is to determine the functionality as:
3

The last MVC is for display user interface which is described below and it provides an interface for
view the saved record which includes all details of the trip along with the comment. The controller
level provides control over data and model level help in to update the saved record, deletion and
use GPS location and the view level is for view the record which is stored in the database of this
application.
Figure 3 MVC 3
4

2. Database schema design. There should be at least two
tables, one for trips, and one for Settings.
Database schema design is used to make a blueprint of structure in which it defines how will store
the values and how will show it to the user. Basically, it is a set of instructions to store the values and
it produces a detailed model which stores all the details and display according to the database
schema. The below two schemas are design for trip and setting table.
The below database schema is for a trip table which provides a blueprint of this schema to store the
values and details of the trip in table form. This table produced by the relational database using
SQLite language programming to store the data in the application database. It consists of log
interface which consists of various fields to enter the information such as the title of the trip,
address, and date of trip, duration or time period, type of trip and comment as a remark. And these
inputted details will store in the database by a tap on save button and it also has a cancel button to
cancel the inputted data.
Database Schema for Trip table:
Trip (user_id)
Log (title, address, trip_type, destination, date, duration, comment)
Figure 4 Database Schema 1
The below database schema design is for a setting table which is used for store the user details as
this application is developed for storing personal trip details for future use. This setting table consists
of user detail as id, name, email, gender, and comment if any and this interface automatically stores
the data which is entered by the user in the application. The details can be modified anytime.
Database schema for setting table:
5

Setting (user_id, enter_name, enter_email, enter_gender, comment)
Figure 5 Database schema 2
6

3. A final section of 'Reflections'. In this part, discuss any
difficulties you had implementing the program and how
you solved those difficulties. Reflect on how the
development process went for you, what you learned, and
what you might do differently next time.
While developing this application for users who love traveling, this application helps those who want
to keep a record of trips. This application provides interfaces to store the trip details as title, date,
duration, the address of the place, type of trip and all and another interface designed for store the
user personal details to keep track of this application. The application sometimes creates problems
while developing as fetching the location from google map, update the data after storing once, and
save the Google map location form saved data. The whole process helps me to understand various
functionalities of android application and new features which help in to enhance the interface of the
application to interact the people more. This application teaches various things as utilizing Google
map location, use of buttons, interface designs through the XML file and many more. The below
code determine the fields of XML file which is designed for making an interface to store and provide
support for this application.
Figure 6 Code 1
7

Figure 7 code 2
If I get a chance to make this type of application again in future, it’ll help me in many ways as this
time I understand the various functionalities and can be implemented more effectively next time
which will enhance the performance of the application in the more interactive way. The application
designed for storing the trip record and the location of place through GPS technology help to save
exact location of that particular area and it also provides a field to enter any remark for that place
used in many ways like recommendations, specialties, etc.
8

Conclusion
This report concludes that all the above explanation of this application is provided in a proper way
which is developed by a start-up company to help the humans to keep a record of trips along with
the comment. This report describes the 3 different MVC for user interfaces as setting UI, log UI, and
display record UI. The application is designed along with the functionality of database to store the
record of trip and users personal information which can be accessed anytime by the user from this
application. It also explained the design of this application and some reflection which occurred while
implementing or developing this application for people to store the information on trips. The whole
application is developed successfully and this report determines all the aspects of this application
through some diagrams and their descriptions.
9