1 / 14

Creating a Trouble Call Tracking System

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

mrinal
Download Presentation

Creating a Trouble Call Tracking System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Creating a Trouble Call Tracking System John Alger algerja@jmu.edu James Madison University

  2. Topics • Development • Deployment • Maintenance

  3. Terminology • RDBMRelational 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

  4. Development Steps • System Mission Statement • Business Model / Environment • Graphical User Interface (I/O) • Tables, Relationships, Queries, VBA • Prototype • Refinement

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

  6. 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 Our Business Model(We are an auxiliary)

  7. Environment Ethernet Billing DialUP System Client Call History Staff

  8. Interface Design • Communication • Input screens (FORMS) • Output (REPORTS) • Controls (The OK button) • Properties (The color of OK) • Events (OK was clicked) • Methods (External code) • Macros/Wizards (No Code)

  9. Table Creation • Singular Entity • Primary key • Index • Relationships • QBE interface

  10. Internet Access • Web forms - CGI • Post Only • Interactive • Perl Generated • SMTP - Email from the app • SNMP - Managing the hub ports • TCPIP sockets

  11. Deployment • Splitting the Database • Production • Development • Server environment

  12. Maintenance • Backup solution • Contingency processing • Business rules change • Continuous Improvement

  13. Questions ? ? John Alger algerja@jmu.edu James Madison University

More Related