User Interface Modernization Case Study - Unisys

adhocjackpotΑσφάλεια

5 Νοε 2013 (πριν από 3 χρόνια και 11 μήνες)

121 εμφανίσεις

User Interface Modernization
Case Study


EAE 3019


Wednesday 25 May 2011


8:00 AM




Alan Hood, Consulting Engineer


Global Technology Centre Solutions


Unisys Corp.

Outline


Customer profile


Modernization goals


Process


Workshops with end users


Prototyping


Agile development process


Results and timeline

Copyright 2011, Unisys Corp.

2

Copyright © 2011, Unisys Corp.

3

Minister

of Transport

Ministry

of Transport

New Zealand
Police

Aviation

Security
Service

Civil Aviation

Authority

NZ Transport
Agency


Manages land
transport
infrastructure and
services.


Access

to transport
system through
driver and vehicle
licensing, vehicle
inspections, and
rules development.


Provides land
transport

safety and
sustainability
information.


Manages

state
highway network.

Maritime
New Zealand

Transport
Accident

Investigation
Commission

Crown Entities

Board

Board

Board

Board

EAE applications control
Driver License and
Vehicle Registers


Important Locations in New Zealand

Copyright © 2011, Unisys Corp.

4

1.
Auckland



Production Data Centre


Production systems hosted in Unisys
Outsourcing Data Centre in Auckland

2.
Kapiti



Development / DR Data Centre


Development and testing is done on
equipment in the Unisys
Kapiti

Data Centre


This doubles as Disaster Recovery

3.
Wellington



Unisys Dev / NZTA Offices


Application development is provided by
Unisys services in Wellington


NZTA administrative offices located in
Wellington

4.
Palmerston North


NZTA Call Centre


NZTA operations and national Call Centre
located in Palmerston North

Application Integration

Common Data Interface (CDI)

Application Architecture and Client Interfaces


Mainframe

channel

Green

Screen

Web Delivery
channel

WOF
Online

(Cool ICE)

VIN Direct

(Cool ICE)

MotoChek

(Cool ICE)

NOF

Terminal
emulator

Web Delivery
channel

eGovt

Transact

(ASP .NET)

Driver Check

(ASP .NET)

TORO

(ASP .NET)

Programmatic
Interface
channel


Application

Programmatic

Interface

Electronic

Data

Interchange

Interface

XML/Web Service

Component Enabler

BP Card

Upload

Rich Client channel


WinDLR

(
VB6
PowerClient
)

Image Capture

Application

(VB 6)

Image
Management
System

(non
-
EAE)

Solaris

EAE applications

NOF

FTP/Flat File

NOF

FTP

I/Fs used by these
clients must not
change

Access

Control
(ACC)

Motor Vehicle
Register
(
Landata
)

Driver License
Register

(DLR)

CE

Gate

CE

Gate

CE

Gate

Application Integration

Application Modernization


Phase 1

Replace older client technology with Component Enabler based clients

Mainframe

channel

ASP .NET

GUI

Web Delivery
channel

WOF
Online

Cool ICE

VIN Direct

Cool ICE

Web Delivery
channel

MotoChek

(ASP .NET)

eGovt

Transact

(ASP .NET)

Common Data Interface (CDI)

Driver Check

(ASP .NET)

TORO

(ASP .NET)

Programmatic
Interface
channel


Component Enabler
















BP Card

Upload

EAE applications

Rich Client channel


WinDLR

(
ASP .NET
)

Image Capture

Application

(VB 6)

Image
Management
System

(non
-
EAE)

Solaris

FTP/Flat File

Application

Programmatic

Interface

Electronic

Data

Interchange

Interface

NOF to
Component
Enabler
gateway

CE

Gate

XML/Web Service

FTP

I/Fs used by these
clients must not
change

Access

Control
(ACC)

Motor Vehicle
Register
(
Landata
)

Driver License
Register

(DLR)

Application Information

Model Name

Ispecs

Reports

Global
Logics

Profiles

AccessControl

(AC)

48

35

42

43

Driver

License
Register

(
DLR)

454

239

280

383

Motor Vehicle
Register (
Landata
)

557

356

342

320

Copyright © 2011, Unisys Corp.

7


8
-
16 EAE

developers, depending on project needs


Users include agency employees, other government agencies, and third
party partners


Most DLR users currently using
WinDLR

(
PowerClient
/Visual

Basic)


Most
Landata

users currently using “Green Screen” terminal emulator


Some external access coming through custom CDI (Common Data
Interface) module, using Web Services (relatively low volume currently)

Client modernization goals


Minimize impact to third party application interfaces


Some external agencies have programmatic interfaces to the Registers


These interfaces must not change at this time


Remove dependence on older, or unsupported technology


Visual Basic 6,
PowerClient


Unable to deploy newer Windows 7 workstations due to deprecated functionality in
the Visual Basic clients


Replace terminal emulators with web browser interfaces


Reduce software license and maintenance costs


Improve usability


Maintain high user productivity


Enable roll out to end users with no retraining


Reduce training for new employees


Enable Call Centre personnel to work on both Registers

Provide equivalent business functionality while reducing training,
maintenance and licensing costs



Copyright © 2011, Unisys Corp.

8

The Process


Step 1


Proof of Concept


Step 2


Prototyping


Step 3


Development and deployment

Copyright © 2011, Unisys Corp.

9

Step 1


Proof of Concept

(December 2010)


We defined several proof points to demonstrate feasibility


Show “green screen” (
Landata
) functionality in a Web browser


Show
PowerClient

(
WinDLR
) functionality in a Web Browser


Design (“paper proof”) of revised user access


Demonstrate image capture and custom printing interfaces


Copyright © 2011, Unisys Corp.

10

Vehicle Change Attributes

VCATS


“Green Screen” starting point

Vehicle Change Attributes

VCATS


After simple GUI update

Proof of Concept Results


Custom label printing and integration with Image Capture
(Visual Basic) application were successfully demonstrated


ASP .NET client interface was shown to be a viable
replacement for
WinDLR

(
PowerClient

with Visual Basic 6)


Users were thrilled with ASP .NET Web forms replacement
for “Green Screen” terminal interface



NZTA executive committee approved proposal for user
interface modernization

Copyright © 2011, Unisys Corp.

13

Step 2


Prototyping

(February 2011)


Workshops held in Palmerston North with user
representatives to determine requirements and define
interface standards


Development team produced a prototype with some key
business processes and 15
-
20 “screens” to show resulting
interface


Team adopted agile development approach


Rapid prototyping


End user involvement


Daily “scrum” meeting with stakeholders


Duration: approx. 2 weeks

Copyright © 2011, Unisys Corp.

14

Workshops


Workshops included representatives from all user
departments


Each user demonstrated or described their normal activities


Highlighted what they like about the current interface, and
what they would like to have done differently


Observed Call Centre employees as they were with the
applications


Several screen layouts and font/color/control combinations
were prototyped and demonstrated



Preliminary GUI design guideline was produced

Copyright © 2011, Unisys Corp.

15

Special Consideration for GUI Design


Primary end users are the Call Centre data
entry personnel


Web browser interface must not require use of
too many graphical controls


They are very adept at keyboard operations and
shortcuts


Frequent switching from keyboard to mouse will
slow them down


To minimize retraining the form layout must be
the same as the existing character based
interface (one exception noted in workshop)


Special concern for hot key macros and
copy/paste functionality

Copyright © 2011, Unisys Corp.

16

No elaborate GUI

GUI Standards


first pass

Copyright © 2011, Unisys Corp.

17

Ingredients of the Style Guidelines


NZTA already had style guidelines for online applications
(for public Web pages)


Used these where applicable


Minimal use of GUI controls (remember data entry people)


Drop Down list boxes for data items with a finite set of options


Most lists populated using
Sendlist.Static

in a single report


To improve ease of use, location of one navigation field
(Quick Navigate) was changed on every
Landata

form


Change made in Global Logic

Copyright © 2011, Unisys Corp.

18

GUI Standards


first pass

Copyright © 2011, Unisys Corp.

19


Landata

form layout the same as the green
screen forms


one exception


Move Navigation field to top of form, above

Maint
” field


Rename it “Quick Navigate”


Consistent browser layout for
Landata

and
DLR


Little/no change to GUI from
WinDLR


Header and navigation part of the ASP .NET
form, not painted in EAE

Copyright © 2011, Unisys Corp.

20

NZTA Online Style Guide for Web Applications

Approved Colors

Approved Fonts

Agile development process


Team adopted elements of agile development during the
prototype phase


Small team


Daily scrum meeting


Rapid prototyping, frequent releases (sprints)


Continuous testing


Continuous user feedback


Requirements were refined as the project progressed


Positive response from both the development team and the
end users

Copyright © 2011, Unisys Corp.

21

GUI Standards



refined during second workshop

Copyright © 2011, Unisys Corp.

22

GUI Standards



refined during second workshop


Users decided to use Drop down list for any predefined
case with 2 or more options


Decided against using radio buttons


Wanted to force users to make a selection


lists make easier


Chose to highlight enterable fields differently from non
-
enterable data fields


Errors and Warnings dynamically highlighted in red



At the end of the prototype phase requirements were well
defined, and formal style guideline was approved



Copyright © 2011, Unisys Corp.

23

Development process during prototype
phase


Made “global” changes to EAE model, according to style
guidelines


Defined process for Ispec changes


Produced reports for
listbox

data


Refine style guide


Document exceptions


End user exposure


Feedback rapidly incorporated

Copyright © 2011, Unisys Corp.

24

Prototype Phase

Development
Team

(some part
time
)
:


1 Project manager


2 Architects


2 EAE developers


2 .NET developers


Various from operations,
support, test, as needed

Vehicle Change Attributes

VCATS


Using Final Style

Copyright © 2011, Unisys Corp.

25

Step 3


Develop and Deploy

(Begin March 2011)


Prototype phase flowed naturally into development


Added development and test personnel


Global changes made during prototyping were kept


Project test team verified functionality


Minor changes to DLR GUI


Due to differences between
PowerClient
/Visual Basic and Web
Browsers)


Internet Explorer selected as default browser


Firefox and others were tested


Any differences or exceptions noted


User representatives confirmed usability factors


Copyright © 2011, Unisys Corp.

26

Typical Ispec Form Modifications


Check the SMNT field, if the form has one


Set Grid, Snap to Grid, Show Align Palette


Select All
-

adjust position on screen


Select Display Items
-

change BG to the NZTA Light Grey


Adjust position


keeping orientation as the Character screen


Adjust display and data fields horizontally


Locate Input and Inquiry data fields


change the BG to match form


Change control type on specific data fields, according to design
guidelines


Dropdown Combo List


Push Buttons, Radio Buttons


only used by exception


Document Data Items for Lists, fields requiring highlights


Document all exceptions

Copyright © 2011, Unisys Corp.

27

Elapsed Time:


For simple forms
~5 minutes


For complex

CopyFrom

Ispecs
20
-
30 minutes


Summary of typical changes

Copyright © 2011, Unisys Corp.

28

Summary of typical changes

Copyright © 2011, Unisys Corp.

29

Navigation

Quick links

In ASP.NET
Web form


Header / Logo

/

User name

In ASP .NET
Web form


Summary of typical changes

Copyright © 2011, Unisys Corp.

30

Some alternatives
under discussion


User reaction



midway through project

“In terms of how Unisys has delivered to date


it’s a quantum change in
approach. We have held several workshops with Unisys


bounced
ideas around and then they have returned with working prototypes
where it is clear they are listening and implementing what we have
asked for and in some cases doing much better than we had anticipated.

Most recently we identified a concern with the allocation of outlet IDs


Unisys held a workshop in Palmerston North and then 3 days later
provided a working prototype that delivered all three of the options we
had suggested as alternative approaches. We are now in a position to
move forward and allow different types of outlet choose the option that
best suits them.”

Christian Hayes, NZTA Project Manager, NZ Transport Agency


Copyright © 2011, Unisys Corp.

31

Timeline


December 2010


Proof of Concept


December 22, 2010


executive committee approves project


February 2011


Prototype


Feb 2
-
3


First User Workshop


Define initial requirements


Feb 22


Second User Workshop


Demonstrate prototype forms, refine requirements and style guide


March
-
May 2011


Development and Testing


June 2011


Production Target


Copyright © 2011, Unisys Corp.

32