|
The first phase was a thorough needs analysis to outline all
workflow processes and business rules, factor out redundant
functionality, so that a set of global routines could be implemented
to service all work orders. With the infrastructure
shaping up, another detailed analysis was done for the user
interface. The concept of work order chains was formulated.
A work order chain is the set of all Web pages necessary for
a customer to traverse in order to completely define the
required work order. They were retrofitted with a mechanism
for carrying work order requirements from page to page
through form variables. This strategy minimized database
input and output.
Since work orders had varying data requirements, a consistent
database record format wasn't possible. A strategy for dynamically
producing a vertical database record consisting of many
database records was put in place to handle the storage of the
different work orders. This proved invaluable during development,
as A&E invariably added requirements to the definitions
as they were produced and presented for review. The code
implementing this dynamic data structure never had to be
changed when the data structure changed, saving countless
coding man-hours.
With the Web application in place to create work orders from
the outside, attention was turned to processing them on the
inside. Another internal Web application was created for internal
employees with features to help them process the work
orders. View filters were implemented using cookies to allow
employees to view only those work orders for which they're
responsible. Employees were given the ability to complete and
lock orders. Completed orders have a configurable expiration
date. Once a completed order expires, the system automatically
deletes it, thus automating a rather tedious responsibility.
|