Running head: CSIS 375: USER INTERFACE DESIGN 1
CSIS 375: User Interface Design
Student’s Name
Institutional Affiliation
CSIS 375: USER INTERFACE DESIGN 2
CSIS 375: User Interface Design
Section 1
The interviewee is a friend, John, who works in the User Interface Design department and
works explicitly under the User, Task and Environment Analysis and Modelling area. Some of
the questions asked during the interview are below. Also, he provided answers to the questions.
1. Where will the interface be physically located?
The interface will be accessible through any software that can handle touch functions
integrated into a device, like a smartphone.
2. Does the interface hardware integrate with either light, space, or noise
changes?
The interface can take in voice commands, and the user may not have to input some of
the information physically.
3. Will the users require any trained expertise to interact with the user
interface?
Minimal to no supervision is required while interacting with the interface since it is
straightforward.
4. What is the range age of the users that will be interacting with the interface?
Basically, any user that can interact with a touchscreen device can handle the interface.
5. Is the software used in the interface a part of the entire system, or will it have
to be changed occasionally?
The software will be a part of the interface system, and only regular updates will improve
it over time.
6. What will be the primary language used in the interface?
CSIS 375: USER INTERFACE DESIGN 3
The main language, for now, will be English. However, future updates may support other
languages in case the interface design reaches other foreign countries.
7. How will the interface respond if a user inputs the wrong information in the
set application?
The interface will have back functions and pop-up message options to inform a user if
they input wrong information.
8. What is the primary goal of the interface?
The primary goal of the interface is to be integrated with any ticket booking system for
transportation. It could be either by road, rail, or water.
9. What technology will be behind the interface?
The technology behind the interface is in different forms. Firstly, an interactive
visualization presents moving objects of the mode of transport the user wants. Secondly, gesture
and motion sensing recognition will allow the user to interact with the interface for specific tasks
freely. Lastly, it will contain voice and speech analytic software that allows users to command
some words into the application instead of physically typing them.
10. Does the interface contain any security features?
The interface will have biometrics software that integrates with the type of device the
user interacts with. For example, if a user has a smartphone with Face-ID, the interface will
integrate with the feature and Touch-ID. However, if the device has neither, the user can opt to
input a physical password of their choice to ensure that their data is secure.
11. What are some of the tasks the interface will present?
Some of the tasks will include choosing a mode of transportation, payment options,
destination settings, distance estimates, among others.
CSIS 375: USER INTERFACE DESIGN 4
12. What is most important to the user while interacting with the interface?
The users must have an easy time interacting with the interface. Therefore, it must be
smooth and efficient and should not throw errors while in operation.
13. What amount of virtual memory will be efficient for the interface?
Without an implementation into any system, the interface alone will require a minimum
of 1 Gigabyte to run efficiently. Therefore, any system with 1 Gigabyte or more should house the
interface effectively.
14. Since we are on the topic of memory, what space is required to house the
interface without a system implementation?
The interface alone is 238 megabytes and thus will vary within different platforms once it
is implemented in the system.
15. How would a user know if the task they assigned through the interface was
successful?
The interface is designed to work with the implemented system. It pops a green message
with a success notification once the user completes the tasks.
16. What version is this interface in? Will there be future versions?
Since this is the first version, we decided to term it Version1.0. There will be future
versions, primarily if this prototype works efficiently with all the planned systems.
17. What frameworks have you used in the interface design?
Mainly, CSS/Sass frameworks were used in the interface design.
18. What trends have you overlooked to continue in the interface design?
CSIS 375: USER INTERFACE DESIGN 5
One trend will involve two versions of the interface. The main will interface will be the
public release. The other will be a Developer Beta to help figure out errors and improvements
before they are presented to the users.
19. How would the user communicate with the designer about their experience
with the interface?
There is a feedback panel to the bottom left designed for the user to rate their experience
from 1 to 5, and the data is saved in the system database.
20. Is the interface available as a PART download without any integrated
system?
No. the user interface design is copyright protected and cannot be downloaded separately.
Therefore, it is only prone to changes only by the designer. The users can only interact with it
through a system.
Section 2
The interviewee launched the interface using a smartphone. It seemed to have been
integrated into a system called; Fleet Ticketing Management System. However, it took a few
seconds to launch, which seemed long given his interview response of a smooth experience for
the user. I learned that it was a prototype user interface and had not been adequately optimized
for the system. The selection options in the panel were very vibrant and accessible to pick out,
just like he had claimed in the interview. The interviewee also had Touch-ID on the device.
When he tried to input personal details in the system, the interface first provided a security
request notification to verify his ID. This seemed very efficient. Lastly, he did not have to
physically fill in some details like destination and mode of transport. He taped on a microphone
icon at the bottom and commanded a destination with a train option ride. Immediately, the
CSIS 375: USER INTERFACE DESIGN 6
interface picked out the voice command and auto-filled the exact information. This style of
filling out information seemed very easy compared to physically typing and selecting it in the
interface.
Section 3
In the task analysis section, a few automated tasks will be efficient in the user interface.
The first task that requires automation is selection. Once the user selects a destination, the
automated algorithm implemented in the user interface is sequential flow (Oulasvirta & Abowd,
2016). With the sequential flow, the user inputs their information. The algorithm automatically
reviews the saved data in the system to take the user to the next window that matches the saved
information. The second task that needs automation is checkbox fill-outs. If the user does not fill
all the necessary fields, they cannot proceed to the next step. Thus, the necessary automation
strategy will be the use of parallel flow synchronization. The feature will allow the analysis of
different tasks that must first be completed to follow the next actions in the user interface.
The third automation task will be security protocol selection. With the rule-based
algorithm, the user will not proceed without verifying their identity and the mode of payment
they will be using for the transportation services. For example, when the user selects to input
their information, the rule-base will prioritize the security protocol of first asking for their
verification through Face-ID, Touch-ID, or regular digit-passcode fill-in. The final automation
task that can be implemented is the reminders scheduling. When a user interacts with the
interface, the reminders scheduling will provide a pop-up option for different agendas, like a
request for the user to rate the application. The scheduler can be adjusted with the number of
times it pops up for the user if they ignore it.
CSIS 375: USER INTERFACE DESIGN 7
Section 4
The user base in the interface will have users of all ages, mostly above 15 years.
However, since it has payment option modes, younger users without credit card verifications will
require supervision within this section to help them choose payment methods. Moreover, the user
gender does not matter in this interface as it applies to all. The users will not need much
experience while interacting with the interface to perform various tasks. The interface design is
meant to be straightforward for the user to choose and fill out information right from the panel.
Thus it should be easy for users of all ages.
CSIS 375: USER INTERFACE DESIGN 8
References
Oulasvirta, A., & Abowd, G. D. (2016). User interface design in the 21st
century.CComputer,C49(7), 11-13.
