COMP 1661 Application - Development - For - Mobile
COMP 1661 Application - Development - For - Mobile
Contents
Section 1 .................................................................................................................................... 3
Section 2 .................................................................................................................................... 4
Section 3 .................................................................................................................................... 5
Section 4 .................................................................................................................................... 6
Section 5 ...................................................................................................................................12
Evaluation .............................................................................................................................12
Security ..............................................................................................................................12
Maintainability ....................................................................................................................12
Section 1
Checklist Table
Feature Implementation
Basic details input screen • Fully implemented
Implement forms validation • Fully implemented
Store, View, Delete and check • Fully implemented
duplicate events
Search • Implemented but can only do a simple search by storage
type and has a bug showing global variables
Add a note input screen • Fully implemented
Android app coded in java • I have created a native app of both feature a) and feature b)
Additional features • Login and registration, Crop and save photos from gallery
Section 2
Bugs and Weaknesses
• When saving an additional note, you need to click the save button twice for it to respond.
• The Login and Storage database are not connected to each other resulting in always
entering a reporter for each new record.
• The app is able to search but is showing global results.
Section 3
Special Strengths
All the operations and hints needed to save a record are found on one screen which makes it
easy for a user to know what type of input needs to be entered. The main screen has two
buttons “Add” and “Storage” and eight input fields which two of them have date and time listener
which make it easy for a user to input information using a date and time dialog. The app is able
to store images associated with particular storage and users are able to update the images
even after they have been saved. The app is able to retrieve saved data and displaying it on
the input fields when users want to update the data instead of users seeing empty input fields.
Section 4
Screen Shots of Features
User registration screen with user name input and password, confirm password input.
Login screen enables the user to enter their user name and password to log in.
Basic details input screen enables the user to enter records about storage.
Users permission to access the phone gallery in order to pick an image to crop and place the
image on the camera icon.
Form validation for mandatory fields, display of error messages to the user to enter information
in the required fields.
Security
Improvement security in terms of access control which type of users has access to certain type
of data, some users depending on their access level can be able to view only certain types of
storages. Another improvement in security is encryption of user registration data, in the current
state the app is not able to encrypt any data. The app can be made more secure by
segmenting each user to their own storage library, currently, all users have access to the same
data. Email verification feature will make the app more secure by authenticating each user how
wants to register to the app, it will also enable password recovery for forgotten passwords.
Maintainability
The app is able to handle some Logic errors using exception handling which prevents the
application from abruptly stopping when it encounters an error. Additional features caused
changes in requirements and functionality which later led to new bugs and errors. Perfective
maintenance was used to correct some of the bugs that came from adding additional features.
Some code needed to be optimized in order to support the additional features which are also
new features to the system.