Technical Portfolio

Experience Type:

Issues Tracking and Reporting
Help Systems
Presentations (Also Visio)
Programmer Interface Documentation
Reports
Software Manuals
Training
Web Pages

Issues Tracking and Reporting
This is a sample of an Issues Database that I often create in Access for the benefit of the project team. The data entry screen is accessible for all team members, as are the reports.

Note: Using Access I can also create screen mockups to demonstrate how a program might look in production. This is helpful for end users to see how the data will flow--they can provide input as to the best tab order for their needs and the most intuitive method of using the proposed system.

Help Systems
I am currently working in RoboHelp to put reference materials online as part of the State paperless initiative. In addition to providing standard context-sensitive help in our applications, I am also publishing the ADEQ Employee Manual for access through the intranet.

These screenshots show the new Employee Manual's Table of Contents and the searchable Index.

Presentations
This Presentation is a sample of my PowerPoint work. I have created numerous presentations for C-level executives at both Alltel Wireless and Verizon Wireless. I can honestly say that the highest level of executives at both companies know who I am and are familiar with my work. I have also presented before the executive leadership at Arkansas Department of Environmental Quality as part of project closing activities.

For those looking specifically for Visio skills, here's a nice sample showing the procedure for tracking legal actions at ADEQ.

Programmer Interface Documentation
This CORBA Programmer Interface Guide was created in FrameMaker. It provides programmer interface instructions and other notes from the engineers who created the software it describes.

Reports
When reports aren't delivered per the expectations (even unstated expectations!) of the Client, user-acceptance of the project takes a big hit. Since reports are the actual output of a database, the failure to meet that need is equivalent in the users' eyes of project failure and therefore wasted money and resources. To circumvent this problem, I work hard throughout the project to sniff out every report requirement. Once somebody mentions a report they've used in the old program, I find out what fields are needed and make a mock-up.

I created a number of report mock-ups for the Arkansas Department of Environmental Quality. The project is a database that tracks legal actions. The following samples reflect Supplemental Environmental Projects (SEPs) performed by facilities for the State of Arkansas. (This information is all FOI-able, but you'll notice my favorite test guy Bob Smith is often mentioned.)

The Penalty Amount Change Report is used by Fiscal to show amounts paid along with the value of SEPs. Fiscal uses the SEPs Collected Report to report values of all SEPs collected for each division. I created these reports in Microsoft Word.

Once all reports were approved I created this Report Summary to show our report programmer the possible similarities. She'll use this to determine where some reports can be combined, or where she can reuse report code to create a report that is similar to one she's already done.

Software Manuals
The following books are other projects for the Arkansas Department of Environmental Quality. As with most of my work, the writing is done in Microsoft Word (though I prefer FrameMaker). The diagrams were created in Visio, and I obtained all screenshots using PaintShop Pro. The books are printed to PDF and distributed online.

To demonstrate the continuity between projects, I am including the cover, contents, and first chapters of two of the four books. The purpose of this continuity is for ease of you and also to increase user confidence--thereby increasing user acceptance of the software. For each book the user will know what to expect and will be comfortable with the general look and feel of the book, even though each of the software applications is significantly different.

Permit Data System User Guide
CAO/NOV User Guide

Training
I spent two seasons as a trainer for the Girl Scouts of the USA Tejas Council. To become a Girl Scout trainer, a 16 hour weekend course is required to learn training facilitation skills approved by GSUSA. Most of my training experiences were dual-trainer. During each class we were required to use training techniques desiged for each learning type.

At First American Real Estate Information Services, I created the training materials for a Siebel product and assisted in the training classes.

As an example of my training development experience, here is the ArcGIS Self-Training Guide. (Best viewed with Acrobat Reader)

Web Pages
I initially created the pages for this site using Yahoo PageBuilder, a drag-and-drop Web page creator. Changes (and there have been many) are done in the HTML editor.

Using an interface similar to FrontPage, I created the Web pages for Alltel's Western Wireless Transition Help Site. This site was created for employees affected by Alltel's purchase of Western Wireless.

Last Words

Legally required recognition to Peanuts.com.

You are visitor number: