Aprilla Alexandra M.

Nazi CMSC 128 AB-1L

Roda Athea E. Baraquio January 21, 2007
Alexis Anthony T. Lugod
Rachelle Anne P. Bonza
Jervy R. Escoto

Project: OVCCA Vehicle Database

Overview

What are the most important facts that a developer should know about the user interface
of this system?
- It is vital for the developer to understand the functionalities of the IDE he/she
will use; the modules that will best suit the interface design; user-friendliness
of the user interface, etc.

What are the ranked goals for the user interface of this system?

1. Understandability and learnability

2. Task support and efficiency
3. Consistency and familiarity
4. Safety

Metaphors, Exemplars, and Standards

What is the central metaphor of this UI design?

What existing systems have user interfaces similar to the UI you want to build? What
specific aspects are similar?

- AppFuse.com: the modules(specifically included in j2ee) used; the

frameworks used to implement the web application

What UI design standards, guidelines, and styles are you following?

- Java UI guidelines
Task Models

What types of users will use this system?

- The program allows users that are predefined by the developers (can be
modified by the time the program has been delivered). Users are only
members of the office, that is, members are officers of OVCCA and
University Police Force.

What types of tasks will those users perform?

- Administrator: has all privileges (Registration, Search, Renewal, Violation,

Update)
- Registration: only allowed to create another registration and to search profile
- Renewal: only allowed to renew franchise and to search profile
- Violation: only allowed to add new violations and to search profile
- Update: only allowed to add new violations and to search profile

Interaction Context Purpose Contents/Constraints/Behavior

Login dialog Verify that the current user is
actually the person that they
claim to be (can be verified by
the username and the set
password).
--Prompt Tell the user that this page is
to login.
-- Message Area Give the user some feedback
about the login process.
-- Username Identify the user account that
the current user is trying to
access.
-- Password Verify that the current user
knows a secret password that
only the true user of that user
account should know.
-- Login Allow the user to indicate that
they have completed entry of
“Login”
Initially black. Changes to
“Invalid username and
password”, if login fails,
otherwise jump to another page
depending on the current user.
The name of the user account.
The password of 4-16 characters.
Do not display the password on
the screen. The application
should not do anything that
would help users guess
passwords.
"Login" Only enabled when
Username != "". If the username
 their username and password.
--Lost Password Allow the current user to start
a process of generating a new
password for a given
username.
-- Administrator- Offers all the privileges the
Main Page administrator can do.
-- Edit profile Allow the Administrator to
edit his/her profile in case of
discrepancies in his/her
account.
-- Administration Links to all pages such as
those that include main
functionalities (Registration
for PUJ and Private, Search,
Renewal, Violation, Update)
and others (View User,
Current User).
-- Registration Page where the user can create
new registrations. Registration
must be specified either for
PUJ or Private (since PUJ
have other form to be filled
up)
-- Search Page where the user can
search for profile in case of
viewing profile, violations,
obtain information, etc.
-- Search – Result Page where the user can view
Page the query results (includes
vital information about the
owner, vehicle, driver)
-- Renewal Page where the user enter the
plate number for the franchise
to be renewed. The page also
includes the table view of all
the vehicles’, both PUJ and
Private, status (whether
or password is incorrect, delay a
few seconds, and then clear all
fields.
"Forgot your password? Click
here." Only enabled when
Username != "".
Only the Administrator account
can access the page since all the
functionalities can be done by
him/her (security is rendered in
the login page).
Text field containing all the
information in his/her last update
of profile.
(Components to be discussed
individually).
Text field to be filled up and to
be stored in the database. Warns
the user to review all the fields
before finalizing the registration
process (in case of missing
fields, invalid input, etc). OK
button to finalize the process,
CLEAR to clear all fields,
MENU to back to main menu.
Search page can have options;
Search using plate number only,
or with other options such as
Color, Type, Model of car, etc.
Table format that includes the
information. Hitting BACK
button jumps to the Search page,
and MENU to the main page.
Requires the vehicle’s plate
number. In case of empty field or
no existing plate number, output
“invalid plate or plate number
does not exist…”, otherwise
jumps to ChangeStatus page.
 expired or renewed).
-- Renewal – Change Page where the user can
Status Page change the vehicle status
(whether to renew the
franchise or not).
-- Renewal – Update Informs that the specified
Success Page vehicle’s franchise renewal
has been updated.
-- Update Allows user to update the
profile (owner, vehicle, driver) to the registration page and
base on the plate number.
-- Update – Update Informs user that the specified Prints “Updating PLATE
Success Page profile has been updated
successfully.
-- Violations pop up Special feature that allows the Includes plate numbers as
window Administrator to view pending hyperlinks to view all the
or existing violation records
such as expired franchise,
driver’s violations, etc.
-- Registration – Refer to Registration Page
Main Page under the Administrator
privileges above (reusability
(User: Registration ) of functions).
-- Renewal – Main Refer to Renewal Page under
Includes check boxes and the
plate number specified. Yes to
renew the franchise, No for not
renewing the franchise. Hitting
OK button updates the status of
the franchise, and MENU jumps
back to the main menu.
Includes the text that says
“PLATE NUMBER franchise
status: RENEWED” when
clicked Yes check box, otherwise
prints “PLATE NUMBER
franchise status: NOT
RENEWED”. Hitting BACK
button to go back to the Renew
page, MENU jumps to the main
menu.
Includes disabled fields similar
requires the plate number. In
case plate number field is empty
or plate number does not exist,
prints “PLATE NUMBER does
not exist or invalid plate
number”, otherwise enable the
fields. Users will then fill up
forms according to available or
given changes.
NUMBER profile completed
successfully…”. Hitting BACK
button jumps back to Renewal
Page allowing user to update
another profile, MENU button
jumps back to the main menu.
necessary information of the
owner, vehicle and driver.
Page the Administrator privileges
above (reusability of
(User: Renewal) functions).
-- Violations – Main Allows user to add, edit or
Page delete violation records.

(User: Violations)

Technical Constraints / Operational Contextualization

What are your assumptions about the output devices?

We assume that the user’s display systems are capable of rendering the GUI, such
as viewing the pages in any target size. We will not use any audio features.

What are your assumptions about the input devices that you will use?
We assume only that the user has a standard keyboard and mouse.

What are your assumptions about the amount of time users will spend on tasks?
Use case UC-00 is expected to take only few seconds for each user. Use cases
UC-01 and UC-02 are expected to take few minutes for each registration and
update process. All other use cases should take less than 30 seconds each.

What windowing systems, UI libraries, or other UI technologies will you use?

Java 2 Enterprise Edition capable of creating Java-driven web applications along
with the Netbeans IDE. Additional plugins are used to layout the pages.

User Interface Checklist

Understandability and learnability

Are there any labels of icons that are likely to be misunderstood?
Somehow, there are. The pages may render dynamic creation of tables, text,
buttons, etc that has unusual views compared to the traditional HTML-based web
pages.

Is the user's current place and state clearly visible? E.g., wizard step 2 of 5, or edit-mode
vs. play-mode.
Yes. User clearly knows that he/she is in the proper page, including texts that tell
whether he/she is in the Registration process, etc.

Are advanced options clearly separated from the most commonly used options?
Yes. The pop-up windows for violations is located or must appear in the lower
right hand side of the page, therefore user knows that this feature is specially
created and not in included in the main processes the program offers.
Are there no invisible options or commands? E.g., hold down the control key when
opening a dialog box to see advanced options.
None. The developers intend to deliver the software with utmost correspondence
to the client’s requirements. The client wanted the software to be user-friendly as
much as possible.

Task Support and Efficiency

Which use cases force the user to work through more than two interaction contexts?
One is the Search functionality, another is the Registration.

Which use cases force the user to perform slow or difficult UI steps?
UC-01, UC-02, and UC-05.

Safety
Are there any dangerous or irreversible actions that are done with only one step?
None, but the developers are still arguing whether to include the Delete profile
function or not.

Consistency and Familiarity

Do UI elements in your system work the same as they do in the existing example systems
you identified?
Somehow. Since the Appfuse.com system is Java-driven web application the same
with the software we are developing.

Do all elements in your system that appear the same, actually function the same?
Yes. For example Search for Violation and Search for Vehicle Profile work the
same, but with different output. Registration and Update processes include similar
fields to be filled up.

Are all elements share consistent visual characteristics such as font and color scheme,
unless there is a reason for them to differ?
Yes, for the reason to maintain formality among the pages, and to prevent
inconsistency while using the programs.

Are labels used consistently throughout the system?

Yes. Pages include BACK button to go back in the main page for each process,
OK to finalize the process or to confirm actions, and MENU to go back in the
main page.