User Interface Design Document.

  

Assignment:

create a User Interface Design Document for this desktop part of the vehicle of interest application. 

The project background and requirements information are attached. Take the template User Interface Design Template and complete it for your design. 

You are to use Pencil GUI Designer for screen mockups.

This design must conform to good design standards.

Description

In your job you are to build the Maryland State Police Vehicle of Interest user interface, your first assignment will be to create a design document for the desktop part of the application. This will be used by users at the headquarters.

Make sure to review the Vehicles of Interest Introduction and requirements document that outlines the major features of the application

Vehicles of Interest Background information.

You are employed in the Information Technology department of the Maryland State Police. Your department is working on modernizing law enforcement duties.

You have been assigned to a project called Vehicles of Interest (VOI). There are many reasons that law enforcement might be interested in identifying a Maryland registered vehicle. Some of the reasons are:

Silver Alert – vehicle is associated to a missing elderly person.

Amber Alert – vehicle is associated to a missing child.

Stolen – vehicle has been report stolen.

Arrest Warrant – the owner of the vehicle has an active arrest warrant.

After the program is deployed there might be additional reasons that need to be added.

Group of users.

There are three general groups of users that all have special user interface needs.

Headquarters – User’s at the police headquarters receive all information about what vehicles are of interest to the police department. They will need to perform all functions of the system. They are centrally located at the headquarters and would like a desktop application.

Police Departments from other States – Sometimes police departments from other states want to check (ie read-only) the vehicle list. This often happens after they arrest someone. This will be from their police station, which could be anywhere in the United States. They would like a web interface.

Maryland State Troopers – Maryland State Troopers need access (ie read-only) to the list during traffic stops. They would like a mobile interface.

High Level Requirements:

Here is a list of high level requirements for this project.

The system shall track the reason for interest. This will start with values and descripts shown in the table above (Silver Alert, Amber Alert, etc). Headquarters can add, edit and delete this reason. For reason for interest, it contains data for the reason and a description of the reason.

The system shall track the vehicles of interest. Headquarters can add, edit and delete from this list. Police Departments from other States and Maryland State Troopers can read the list. For vehicle of interest, it contains data for license plate number, make, model, color, year manufactured, owners name and owners’ phone. Sometimes we don’t know the year, color and owner’s information; so, they are optional fields.

The Headquarters users also have to keep up-to-date the list of vehicle makes and model.

You should not build any type of login screen(s) or implement roles. You can assume that will be done by another developer once you have finished

User Interface Design

Table of Contents

1. Introduction 1

1.1 Purpose 1

1.2 Scope 1

1.3 Reference Document 1

1.4 Terms, Abbreviations and acronyms 1

2. Graphical Interface Design 1

2.1 1

2.1.1 1

2.1.2 1

2.2 2

2.2.1 2

2.2.2 2

User Interface Design Document Page 2

1. Introduction

1.1 Purpose

Give a brief description of the purpose of this document.

Please note: All areas of the document that include words between < > are implied that they will be replaces with the appropriate terms. For example, replace with the name of the project.

1.2 Scope

Define the scope of the interface design. This could include the application or modules within the application.

1.3 Reference Document

If there are any document reference, include requirement documents, reference them there.

1.4 Terms, Abbreviations and acronyms

If this domain has any special terms, abbreviations or anonyms, list them here with their definitions.

2. Graphical Interface Design

Logically decompose your application’s UI into logical units. For last applications this might be modules of the application. For very small programs this might simple be screens. This will be organized on the 2.x level of the document. You may copy and paste to get as many 2.x subsections of the template as you need.

2.1

Rename to be the logical name of this module. For each screen create a 2.x.y level of the document. You may copy and paste to get as many 2.x.y subsections of the template as you need.

2.1.1

Screen Name:

Give a logical name for the screen.

Image: Put an image of the screen.

Internal UI functionality:

Explain all relevant internal UI functionality. Include images with parts of screens if needed. For example, if the user clicks a specific button a drop-box gets populated. This example is functionality internal to the screen that is relevant to UI.

External UI functionality:

Explain all relevant external UI functionality. This includes UI features that interact with application functionality outside for the screen. For example, when the user clicks a specific button another window opens.

2.1.2

Screen Name:

Image:

Internal UI functionality:
External UI functionality:

2.2

2.2.1

Screen Name:

Image:

Internal UI functionality:
External UI functionality:

2.2.2

Screen Name:

Image:

Internal UI functionality:
External UI functionality: