– Process Flow and Design –

  • Users do not experience code or tables directly- but rather via the User Interface.
  • Therefore, GUI design must play a central role for all customer-facing applications.
  • Likewise, humans do not process concepts in terms of words, but in images.
  • Intelligent process flow diagrams are indispensable when defining abstract concepts.

Provided are numerous examples of both GUI Design and Process Flowcharts pulled from my career. This includes specific samples of the following:

  • GUI Design
  • UML Process Mapping
  • Standard Mappings (Swimlane, ERP, SQL Mapping)
  • Prototype Creation

PORTFOLIO DIRECTIONS

ov

PORTFOLIO CONTENTS

(REDACTED ORIGINAL): Process mapping illustrating the connection between Access Rights and Application Flow. 

flow1a

(OBSOLETE ORIGINAL):  Flowchart defining the processing required by different types of rail cargo at the depot.

flow2a

(REDACTED ORIGINAL) :  Visual mapping of an out-of-date SQL file that was required by DEV. The map allowed the lead developers to unravel the old code. 

flow3a
(PUBLICLY AVAILABLE):  The process for submitting a change to a GDOT project is, like most government agencies, very complicated and labyrinthine. This chart clarified the change management process.

 

flow5a
(OBSOLETE ORIGINAL): The initial screen to create an Invoice in a new system was multi-page. Super-users requested a one-page, bare-boned version for experienced users that did not require usability guides. 

 

REDACTION POLICY

  • REDACTED ORIGINAL: Document edited for online display to protect sensitive data from Public view while still retaining it’s structure and form.
  • OBSOLETE ORIGINAL: Projects that are  authored yet later permanently consigned to the bin fall in this category. The project never existed and never will exist.
  • PUBLICLY AVAILABLE:  Any documents authored at GDOT are available to the general public on request and therefore are not redacted in any way.

Georgia-Pacific-stack-logo