e-Transit: Electronic Business Strategies for Public Transportation, Volume 4: Advanced Features of Transit Websites (2003) / Chapter Skim
Currently Skimming:
Pages 147-157
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 147... ...
7-1 7. Transit Web Site Technology Considerations When the Work Plan for this J-09 Task Order was written, the project team had expected to obtain basic technical information about hardware and software requirements during the research.
|
From page 148... ...
7-2 7.1 Application Design, Development, and Performance Issues Once a transit agency has decided to implement one or more advanced Web site features, a host of questions must be addressed concerning how to acquire or construct the required applications and how to deploy them. This section will discuss the following questions: (1)
|
From page 149... ...
7-3 System Architecture Issues In direct contrast to the PC-centric distributed computing model that has dominated office applications, modern Web-based applications are host-based.66 That is, most (if not all) computations are performed by one or more powerful computer servers, and the client (whether a personal computer at work or home, personal digital assistant (PDA, such as a Palm Pilot)
|
From page 150... ...
7-4 In client/server or two-tier architecture, the presentation and business logic functions are performed on the user's PC, which makes requests directly to a database server across a network. This requires computing power on each desktop and considerable bandwidth (or data communication capacity)
|
From page 151... ...
7-5 tenth of second, but takes 10 seconds to deliver those results to a customer is simply too slow. Indeed, the project team experienced significantly different response times on the many itinerary planning sites it reviewed and tested.
|
From page 152... ...
7-6 These issues apply whether the user uses a PC or a handheld device (although the applicability of maps to very small handheld displays is questionable)
|
From page 153... ...
7-7 When headways are long, however, and the trip is planned shortly before departure, an AIP system that incorporated real-time schedule adherence data could alert the customer to delay their departure or that a planned transfer is not feasible. A simpler approach, already in use, might be to have the system access an incident database to determine if an itinerary calculated with planned schedules utilizes a transit route or roadway affected by a known incident, such as ongoing construction, and simply indicate a risk of delay.
|
From page 154... ...
7-8 are provided by the manufacturer.68 However, the struggle between information technology security professionals and hackers is a dynamic one, and it is not the purpose of this document to provide a treatise on Internet security. The bottom line is that security is a complicated issue that requires the attention of a knowledgeable IT professional who has a full understanding of how a transit agency Web application will be utilized and by whom.
|
From page 155... ...
7-9 When evaluating co-location providers (and even the strategy of co-location) , transit agencies should carefully examine the specifics of the "Service Level Agreement" (SLA)
|
From page 156... ...
7-10 Figure 7.1: King County Metro Rider Alerts
|
From page 157... ...
7-11 CRM in the transit industry context involves providing accurate and appropriately current travel information to transit customers based on knowledge accumulated about that customer via a Web site. If the customer is encouraged to open an "account" or "subscribe" to CRM on an AIP Web site (and has accepted a privacy policy that allows their data to be used on their behalf)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.