Creating a Trouble Call Tracking System John Alger

advertisement

Creating a Trouble

Call Tracking System

John Alger algerja@jmu.edu

James Madison University

Topics

Development

Deployment

Maintenance

Terminology

RDBM Relational Database Model

Table information about a single thing

Record a single row in a table

Field a single column in a table

SQL Simple Query Language

QBE Query By Example

VBA Visual Basic for Applications

Development Steps

System Mission Statement

Business Model / Environment

Graphical User Interface (I/O)

Tables, Relationships, Queries, VBA

Prototype

Refinement

Our Mission Statement

Our system needs to effectively and efficiently track our client trouble calls, history and billing.

Our Business Model

(We are an auxiliary)

• One call per client

• Trouble call FIFO que

• Support Standards

• DHCP access

• Pay up front

• Machine registration

• Web/Phone front end

• Contact Staff and

Clients via Web or

Email

• Client work history and payment history

• Staff demerit system

• Work order process

Environment

Interface Design

• Communication

• Input screens (FORMS)

• Output (REPORTS)

• Controls

• Properties

(The OK button)

(The color of OK)

• Events

• Methods

(OK was clicked)

(External code)

• Macros/Wizards (No Code)

Table Creation

Singular Entity

Primary key

Index

Relationships

QBE interface

Internet Access

Web forms - CGI

Post Only

Interactive

Perl Generated

SMTP - Email from the app

SNMP - Managing the hub ports

TCPIP sockets

Deployment

Splitting the Database

Production

Development

Server environment

Maintenance

Backup solution

Contingency processing

Business rules change

Continuous Improvement

Questions

John Alger algerja@jmu.edu

James Madison University

Download