Mobile Transit Booking System Design

This assignment focuses on designing a mobile transit booking system. Students are tasked with developing a system that allows users to book tickets, recharge their accounts, and automatically track their journeys. The design process involves creating both low-fidelity and high-fidelity prototypes of the system's user interface. Additional requirements include conducting interim evaluations with different user groups (elderly, government/private employees, and students) to gather feedback on system usability and features.

Running head: USER INTERFACE DESIGN AND EVALUATION
Prototyping of Ticket Generating System of
Passenger Transport Victoria
Name of the Student
Name of the University

1USER INTERFACE DESIGN AND EVALUATION
Table of Contents
Introduction:....................................................................................................................................2
1. User Analysis:..............................................................................................................................2
2. Task Analysis:.............................................................................................................................3
3. Interface Design Specification:....................................................................................................5
4. Evaluation:...................................................................................................................................6
4.1 Recommendations on Usability Evolution Tools:.................................................................6
4.2 Methods of Usability Testing:...............................................................................................6
Conclusion:......................................................................................................................................7
Bibliography:...................................................................................................................................8
Appendices:...................................................................................................................................10
Appendix 1: Low-Fidelity Prototype.........................................................................................10
Appendix 2: High-Fidelity Prototype........................................................................................13
Appendix 3: Interim Evaluation................................................................................................15

2USER INTERFACE DESIGN AND EVALUATION
Introduction:
The UI or user interface is the component of the system that is used by the user for
interacting with the computer system. The system uses the user interface to input or output data
or information. The user interface deigning is referred to as the process of developing the UI or
user interface for computer systems (Johnson 2013). The user interface is one of the most crucial
parts of the system. It measures the success of the system as the usability of the system depends
highly on the quality of the user interface. The components of the user interface depends on the
user task and requirements. The system may have different user interfaces for the same task,
depending on the device.
Within this task, the User Interface of the MYKI system for passenger ticketing will be
developed so that the current system interface can be modified. The organization is looking
forward to change the whole system but within this study focus has put only on the system
interface modification. The proposed solution is barcode scanner system for generating ticket. In
this study, the user analysis, task analysis, low-fidelity, high-fidelity and evaluation has been
done.
1. User Analysis:
Product Title and Description: The name of the system is Passenger Transport Victoria
Ticket Generating System. The system will be generating barcode or a fixed barcode will be
generated by the user device that will be used for identifying the user id and credit user account.
The system will have a database that will hold all the information of the user. In case, the user
device has no internet connection, the system will have the information regarding the balance of
the user. The system will allow a user to travel once if he/she has no balance. This will be
considered as emergency.
Date: 9/25/2017
Product Title and Description: The name of the system is Passenger Transport Victoria Ticket
Generating System. The system will be generating barcode or a fixed barcode will be
generated by the user device that will be used for identifying the user id and credit user
account. The system will have a database that will hold all the information of the user. In
case, the user device has no internet connection, the system will have the information
regarding the balance of the user. The system will allow a user to travel once if he/she has no
balance. This will be considered as emergency.
Stakeholder
Category
Role in Product Design Implication Actions Needed
Elderly End user of product The elderly can have
issues with
interacting with the
system as they may
not see the
components of the
system
The interface will
have elements as low
as possible
School Students End user of product The students may
want the system to
provide them
The system will
identify the time of
the day and consider

3USER INTERFACE DESIGN AND EVALUATION
concessions on the
trips during school
time
some of the
concession
Employees End user of product The employees of
government or
private may want the
system to show the
remaining balance
after the ticket is
generated
The system will show
the remaining balance
on the screen of the
device so that the
confidentiality can be
maintained
Middle aged End user of product Middle aged persons
may not be able to
deal with complex
system so that system
must interactions
must be simple
The system will
provide basic
interacting virtual
buttons
Date: 9/25/2017
Stakeholder: Elderly
Attribute Functional
Implications
Desired Product
Characteristics
Actions Needed
Age range: Above 6o Interface must be
simple and effective
Audio visual
feedback and large
fonts
Large fonts will be
used in the system
buttons and
information output
Gender: All types of
Sex
No Impact Null Null
Language: Regional Using English will be
effective in every
way
Using English
language for
communicating
The information will
be visible in English
language
Size of Group:
Medium
Considering the
usability of elderly
will among high
priority tasks
Making the system
user friendly
The interface design
considerations will be
done accordingly to
the usability of
elderly
2. Task Analysis:
Stakeholder Task to Perform Order of Task Potential Solution
End User Recharge the account The user will connect
the mobile device
with the recharge
system
The system will
provide various
The application
system in the device
and database will
have the connection
with same database
The system will be

4USER INTERFACE DESIGN AND EVALUATION
options like change
barcode and recharge
The user will click on
recharge
The system will ask
for card number
The user will input
card number
The user will input
verification code or
OTP to confirm
payment
The system will
credit balance in
account
able to retrieve the
data regarding the
account of user
In order to change the
barcode, the mobile
device needs to have
internet connection
The colors will be
bright so that each
and every
information can be
properly visible
The fonts will large
so that elderly has no
issue in reading the
information
Ticket generating The user click on the
show barcode button
in the mobile
application
Then the user will
show the barcode to
the system
The system will scan
the code and retrieve
the account details of
user
If the user has no
balance then a
warring will appear
on screen
If a travel has been
done without balance
then the system will
reject the request
Or else a dentation
selection screen will
appear
The system will debit
the amount of travel
from the account
The remaining
balance will appear
on screen
The application
system in the device
and database will
have the connection
with same database
The system will be
able to retrieve the
data regarding the
account of user
In order to change the
barcode, the mobile
device needs to have
internet connection
The colors will be
bright so that each
and every
information can be
properly visible
The fonts will large
so that elderly has no
issue in reading the
information
System Administrator System Maintenance The system
administrator will
The system will have
configuration settings

5USER INTERFACE DESIGN AND EVALUATION
click on the login
button that is at the
bottom of the screen
The admin will input
scan the card
provided to him/her
The system will
redirect the admin to
the admin section
3. Interface Design Specification:
System Requirements: The system requirements are based on the above findings.
1) Color of text: The text colors must be bright and eye catchy. The users will be in
a hurry so concentrating on every information is not possible. The colors can be
deep blue or red or violet so that the user can catch the information as soon as it
appear on screen.
2) Font of Text: The font of the txt will be large. Times new roman or Calibri can be
used as fonts as these are easy to read. With the large fonts, the users can easily
read what is appearing on screen. The need of additional information is not
required.
3) Database: The system will need to have a dedicated database server. This
database will be connected to all the devices of the ticket generating system (Saito
et al. 2014). The database will store the information like user information,
account details, recharge details, journey details, train details and many more.
4) Interface: The interface of the system is very crucial as this will allow the user to
interact with the system. The interface will have four different screens. One for
recharge, one for ticket generating, one for admin and one for mobile devices
(Dick, Hull and Jackson 2017). The items to be displayed on the screens are very
low.
5) Items to Display on Interface: The interface will display the user information and
account details on the recharge screen. The screen will also show the same
elements on the user mobile device. Recharge from mobile device is not
considered in the initial implementation to make the system secure from external
threats (Saito et al. 2014). The ticket generating screens will show the map of
route, destinations, and account remaining balance.
6) Usability: Usability is a very crucial non-functional requirement of the system.
The system must be easy to user and understand. The elderly and middle aged
persons may not be able to cope with a complex system. Therefore the system
will low communication buttons as much possible. Only the required buttons will
appear one screen. The system will clearly show every interacting competent in
simple and understandable English.
7) Security: The system will not hold the card number of the user as in the
preliminary stages the system will be vulnerable and prone to cyber-attack. The
system will use encryption for protecting the data. Three layers of security will be
used for protecting the devices connected to the main system (Ameller et al.
2013). The system and database will be connected to different servers.

6USER INTERFACE DESIGN AND EVALUATION
8) Availability: The system will be available 24*7. The system will be implemented
in such a way then it can be repaired quickly (Li et al. 2013). The data back and
restore system will be connected to the system in case of data lost or corruption.
4. Evaluation:
4.1 Recommendations on Usability Evolution Tools:
UXCam: UXCam gives you a chance to watch recordings of your clients connecting with
your application. Two lines of code and under two minutes of mix that is what really matters to
UXCam. Accessible for both Android and iOS, UXCAM is a distinct advantage, with highlights
that†record all occasions in your application, giving experiences into client conduct and helping
you take care of issues that clients experience.
The UXCam stage catches client encounter information and envisions this information so
you can see how to enhance the UX of your application (Borjesson and Jonsson, 2015). It is a
SDK (programming advancement unit) that keeps running out of sight of your application and
catches client encounter information, records what's going on-screen, and alternatively, when
helpful, it catches your client's feelings with a face video - with the assent of both the designer
and the client.
Camtasia: Empowers remote directed ease of use testing, in light of the fact that the
specialist has an immediate association with the member. Sessions can be imparted to other
remote onlookers utilizing the screen sharing apparatus (Turner, Fuchs and Todman 2015).
Sound and video accounts of the screen communication with the voice of the analyzer are
promptly accessible for altering on the experts PC.
For low maintenance or specially appointed utilizations, this approach might be more
costly than utilizing a portion of the other remote unmoderated apparatuses accessible from
sellers.
UserTesting: UserTesting gives a system of pre-screened analyzers who can meet a few
indicated socioeconomics. Or, on the other hand, professionals can welcome their own particular
analyzers utilizing the apparatus. Specialists make an arrangement of errands for the analyzers to
finish, either on your site or even contender locales (Haun et al. 2014). Generally minimal effort
approach to direct remote unmoderated ease of use testing. Sound and video of the analyzer are
recorded, and altering devices empower feature reels to be made effortlessly and rapidly. Cell
phone ease of use testing is accessible.
Since UserTesting pays little charges to the analyzers for each finished test, it is basic to
deliberately make non-one-sided errands, else you chance the analyzer endeavoring to
compromise to fulfill the test as fast as could reasonably be expected.
4.2 Methods of Usability Testing:
Formative Evaluation: Formative assessment is a kind of convenience assessment that
structures the outline for an item or administration. Developmental assessments include assessing
an item or administration amid improvement, regularly iteratively, with the objective of
distinguishing and disposing of ease of use issues.
One critical part of developmental assessment is that the group of onlookers for the
perceptions and suggestions is simply the venture group, used to instantly enhance the outline of

7USER INTERFACE DESIGN AND EVALUATION
the item or benefit and refine the improvement determinations (Walji et al. 2014). Results can be
less formal than in summative assessment, as suits the requirements of creators, designers,
venture directors, and other undertaking members.
Formative assessment, UI reviews, verbally processing testing, pluralistic convenience
walkthrough, and intellectual walkthrough are a few techniques that can be utilized for
developmental assessment (Melnick et al. 2017). This approach is as opposed to a Summative
assessment which must be begun when an outline is sensibly total and includes judging the plan
against quantitative objectives or focused items.
Conclusion:
The above study concludes that the system interface have to be very simple and fragile.
The interface is one of the most crucial components of the ticket granting system. The study has
successfully provided the idea regarding the system interface implementation factors of the ticket
generating system. The most unique that has been done in the study is that the system will not
generate any physical ticket instead it will generate virtually. The system will hold all the
travelling information which will prevent any issue in journey. The study successfully covered
the requirements and recommendations for the end users.

8USER INTERFACE DESIGN AND EVALUATION
Bibliography:
Ameller, D., Ayala, C., Cabot, J. and Franch, X., 2013. Non-functional requirements in
architectural decision making. IEEE software, 30(2), pp.61-67.
Bang, G., 2016. UX Gap: Analysis of User Experience Awareness in practitioners’ perspective.
Borjesson, V. and Jonsson, K., 2015. Evaluating the user experience in mobile games using
session recording tools.
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Haun, J.N., Lind, J.D., Shimada, S.L., Martin, T.L., Gosline, R.M., Antinori, N., Stewart, M. and
Simon, S.R., 2014. Evaluating user experiences of the secure messaging tool on the Veterans
Affairs’ patient portal system. Journal of medical Internet research, 16(3).
Johnson, J., 2013. Designing with the mind in mind: simple guide to understanding user interface
design guidelines. Elsevier.
Li, F.L., Horkoff, J., Mylopoulos, J., Guizzardi, R.S., Guizzardi, G., Borgida, A. and Liu, L.,
2014, August. Non-functional requirements as qualities, with a spice of ontology. In
Requirements Engineering Conference (RE), 2014 IEEE 22nd International (pp. 293-302). IEEE.
Melnick, E.R., Hess, E.P., Guo, G., Breslin, M., Lopez, K., Pavlo, A.J., Abujarad, F., Powsner,
S.M. and Post, L.A., 2017. Patient-Centered Decision Support: Formative Usability Evaluation
of Integrated Clinical Decision Support With a Patient Decision Aid for Minor Head Injury in
the Emergency Department. Journal of Medical Internet Research, 19(5).

9USER INTERFACE DESIGN AND EVALUATION
Ocak, N. and Cagiltay, K., 2017. Comparison of Cognitive Modeling and User Performance
Analysis for Touch Screen Mobile Interface Design. International Journal of Human–Computer
Interaction, pp.1-9.
Paige, R.F., Kokaly, S., Cheng, B., Bordeleau, F., Storrle, H., Whittle, J. and Abrahao, S., 2017,
June. User Experience for Model-Driven Engineering: Challenges and Future Directions. In
ACM/IEEE 20th International Conference on Model Driven Engineering Languages and
Systems. Institute of Electrical and Electronics Engineers Inc..
Saito, S., Iimura, Y., Takahashi, K., Massey, A.K. and Antón, A.I., 2014. Tracking requirements
evolution by using issue tickets: a case study of a document management and approval system.
In Companion Proceedings of the 36th International Conference on Software Engineering (pp.
245-254). ACM.
Schwanghart, W. and Scherler, D., 2014. TopoToolbox 2-MATLAB-based software for
topographic analysis and modeling in Earth surface sciences. Earth Surface Dynamics, 2(1), p.1.
Turner, B., Fuchs, C. and Todman, A., 2015. Static vs. dynamic tutorials: applying usability
principles to evaluate online point-of-need instruction. Information Technology and Libraries
(Online), 34(4), p.30.
Walji, M.F., Kalenderian, E., Piotrowski, M., Tran, D., Kookal, K.K., Tokede, O., White, J.M.,
Vaderhobli, R., Ramoni, R., Stark, P.C. and Kimmes, N.S., 2014. Are three methods better than
one? A comparative assessment of usability evaluation methods in an EHR. International journal
of medical informatics, 83(5), pp.361-367.

10USER INTERFACE DESIGN AND EVALUATION
Appendices:
Appendix 1: Low-Fidelity Prototype
Figure 1: The Low-Fidelity Prototype of Mobile Interface
(Source: Created by Author)

11USER INTERFACE DESIGN AND EVALUATION
Figure 2: The Low-Fidelity Prototype of Booking Ticket Part 1 Interface
(Source: Created by Author)
Figure 3: The Low-Fidelity Prototype of Booking Ticket Part 2 Interface
(Source: Created by Author)

12USER INTERFACE DESIGN AND EVALUATION
Figure 4: The Low-Fidelity Prototype of Account Recharge Interface
(Source: Created by Author)

13USER INTERFACE DESIGN AND EVALUATION
Appendix 2: High-Fidelity Prototype
Figure 5: The High-Fidelity Prototype of Mobile Interface
(Source: Created by Author)

14USER INTERFACE DESIGN AND EVALUATION
Figure 6: The High-Fidelity Prototype of Booking Ticket Part 1 Interface
(Source: Created by Author)
Figure 7: The High-Fidelity Prototype of Booking Ticket Part 2 Interface
(Source: Created by Author)

15USER INTERFACE DESIGN AND EVALUATION
Figure 8: The High-Fidelity Prototype of Account Recharge Interface
(Source: Created by Author)
Appendix 3: Interim Evaluation
Elderly: The questionnaire are as following.
1) Do you want the system to show low information or many information?
2) Do you want to manage all the information by yourself?
3) From 1 to 10 how much usability do you want?
4) Do you want to recharge account through mobile?
5) Do you want the system automatically track the journey?
Government or Private Employees: The questionnaire are as following.
1) Do you want the system to show low information or many information?
2) Do you want various methods of recharging account?
3) Do you want to recharge the account through virtual wallet?
4) Do you want the system automatically track the journey?
Students: The questionnaire are as following.
1) Do you want the system to recognize your identity through mobile device
connection?

16USER INTERFACE DESIGN AND EVALUATION
2) Do you want the system to function properly even if internet connection is not on
mobile?