BSIS 310 - IS Theory&Practice - Fiat Travel - A Proposal
Upcoming SlideShare
Loading in...5
×
 

BSIS 310 - IS Theory&Practice - Fiat Travel - A Proposal

on

  • 397 views

BSIS 310 – PowerPoint Presentation of the Solution - Fiat Travel Databases -- IS Theory and Practice - Submitted for a Solution to Fiat Travel, 2004-08-04

BSIS 310 – PowerPoint Presentation of the Solution - Fiat Travel Databases -- IS Theory and Practice - Submitted for a Solution to Fiat Travel, 2004-08-04

Statistics

Views

Total Views
397
Views on SlideShare
391
Embed Views
6

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 6

http://www.linkedin.com 3
https://www.linkedin.com 2
http://www.docseek.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

BSIS 310 - IS Theory&Practice - Fiat Travel - A Proposal BSIS 310 - IS Theory&Practice - Fiat Travel - A Proposal Presentation Transcript

  • A ProposalFiat Voluntas Tua Travel and Tours
  • Currently . . . 3 Desktop PC’s. Each performs a different task - 1. PC1 prints tickets, invoices and itineraries. 2. PC2’s function is limited to miscellaneous reports and functions. 3. PC3 creates reports, name and luggage tags. All 3 PC’s are subject to viruses. Data is not backed up on any of the PC’s.
  • Current Network Topography Fiat Voluntas Tua Travel and Tours Current Network Topography Mainframe Internet Galileo International Modem Router Norton Personal Firewall PC3 Must be disabled to issue tickets! Norton Anti-Virus Firewall IBM Compatible PC1 IBM Compatible Scanner Airline Ticket Printer Norton Personal Firewall Firewall Invoice/ Itinerary Printer PC2 IBM Compatible William Turnley Daryoush D. Farsi, PhD. BSIS 310 - IS Theory and Practice 4 August 2004
  • Proposed . . . Setup a network. Make PC’s 1 and 2 workstations, as they are now, though connected to a common network. Make PC 3 the print and possibly the application server. Databases and applications will reside on PC3. Reports, including tickets, will be printed from all 3 PC’s.
  • Proposed Network Topography Fiat Voluntas Tua Travel and Tours Internet Proposed Network Topography Mainframe Galileo International Modem Router Norton Internet Security Professional Firewall PC3 PC1 IBM Compatible IBM Compatible Scanner Token-ring or LAN Invoice/ Itinerary Printer Ticket Printer PC2 IBM Compatible William Turnley Daryoush D. Farsi, PhD. BSIS 310 - IS Theory and Practice 4 August 2004
  • Systems Analysis and Design Four tasks to perform - 1. Record Clients and Events. 2. Book Clients for Tours, Retreats, and Conventions. 3. Print Tickets, Invoices, and Tags (Name/Luggage). 4. Maintain mailing lists for future events. All can be done in one program application, as shown in the following slide.
  • Program Flowchart Fiat Voluntas Tua Travel and Tours Proposed Client, Eventsand Report ProgramOverview Greeting Make a Selection . . .  Work with C lients Who/ What would you  Work with Events like to work with?  Create a Report Clients Events Reports Clients Events Reports 1) Add a Client 1) Add an Event 1) Event Master List 2) Change a Client 2) Change an Event 2) Name & Luggage 3) Delete a Client 3) Delete an Event Tags 3) Itineraries 4) AccountsReceivable Hasthe Client been Booked? Yes No Back to Greeting 1) Book Travel, i.e. Galileo William Turnley 2) Add C lient to Daryoush D. Farsi, PhD. Event list BSIS310 - ISTheory and Practice 4 August 2004
  • Programming -Start The Day The Greeting Screen Select which to work with – 1. Events 2. Clients 3. Reports
  • Work with Events . . . Search for Events by entering Date, or by using the Data Control bar. Events may be Added, Changed, or Deleted. A button is provided for reporting on a selected event.
  • Working with Clients . . . Clients are located using the Data Control bar and buttons. Client details are modified using this screen. Events associated with the Clients are displayed, and may be selected by “clicking” on the displayed Event. A button for Client Accounting is provided.
  • Client Accounting - Clients are entered, or selected using the Data Control bar, and are already associated with a selected Event. Prices, taxes and totals are calculated with the Calculate button. The Print Receipt button will stimulate the interface with Galileo International. This function will book the travel, print the ticket, and the invoice/itinerary.
  • Working with Reports Report selection will be based on the current date. Clients selected from the Data Control bar will be displayed with their associated Events. Events selected from the Data Control bar will be displayed with their associated Clients. Buttons will be added to create Name Tags, Luggage Tags, and Payment Reports.
  • Sample Reports -  A sample Name Tags report showing the nickname of those Client’s participating in a tour. ---------------------------------  A sample Tour Report showing the Clients participating and their details.
  • Testing & Implementation The program will be unit tested and modified when errors or needs are discovered. Each Visual Basic (VB) form can run from the VB editor. Data testing will be performed using data from past events, i.e. Tours, Retreats and Conventions. Stress testing should not be an issue, so it will not be emphasized.
  • Conversion Parallel systems will be used in order to populate databases for upcoming events and new clients. Booking travel on the new system will not necessitate connecting to Galileo International. A surrogate ticket and invoice/itinerary will still be printed for record and accuracy. Those clients not already on file will have to be entered manually, as needed.
  • Production & Maintenance The “cutover” to the new system will be made with a new tour making recovery minimal. Maintenance will continue as needed. A five year warranty will be provided for troubleshooting, repairs, modifications and advising. System backups will be scheduled at the time of the “cutover.”
  • The EndPresented by:William L. TurnleyDaryoush D. Farsi, PhD.BSIS 310 – IS Theory and Practice11 August 2004