Rhode Island Transportation Information System. (RITIS)

1
Rhode IslandTransportation Information
System.(RITIS)

• Spring, 2000

2
Rhode IslandTransportation Information System.

• Introduction
• System Design
• Platform / Software Selection
• Server Side and Client Side Platform
• DBMS
• Scripting Technology
• Hardware Requirements
• Participating Actors
• Use Cases
• Current Plans and Future Work

3
Introduction

• Requirements
• Cynthia Levesque
• Dr. Chris Hunter
• High level design
• Overall architecture
• Technologies to be used
• Software / Platform selection

4
System Design

• Multi-tier model
• Sensors
• Sensors Interfaces
• Persistent Storage
• Business Logic
• Presentation
• Unified Modeling Tool
• Participants
• Use Cases

5
Multi-tier model
6
Platforms

• Client Side
• Any platform allowing to run web browsers
• Internet Explorer, Netscape Navigator, Mozilla
• Server Side
• OS RedHat Linux
• Web Server Apache JSP
• DBMS PostgreSQL

7
DBMSMySQL, mSQL, PostgreSQL

• Open Free Software
• Scalability
• Ease of Administration
• Performance
• SQL Compatibility
• Programming Support
• Important Features (replication ability,
  triggers, stored procedures, transactions,
  locking)

8
Scripting Technologies

• Open Free Software
• Performance
• Ease of Programming
• Expandability
• DBMS connectivity
• Portability

• CGI
• ASP (Microsoft JScript, VBScript)
• PHP
• Java Servlets (JSP)
• Java Server Scripts (Netscape)

9
Participating Actors

• Department of Transportation (DOT)
• Regular User/Research Team
• Emergency Service
• Sensor
• Police Department
• Dynamic Sign Board
• Primary/Secondary Data Mining Agent
• Video Camera
• E-Mail Robot

10
Use Cases
11
Use Cases Details
12
Use Cases Details
13
Use Cases Details
14
Use CasesDescription Structure

• 6. Flow of Events
• 7. Alternate Flow E1
• 8. Business Rules
• 9. Use Case Extension
• 10.Outstanding Issues

• 1. Overview
• 2. Actors
• 3. Starting Point
• 4. Ending Point
• 5. Measurable Results

15
Current and Future Work

• Implementation
• Database Structure (Relations, Constraints etc.)
• Platform / Software Installation
• Scripting and Coding (Server / Client)
• Preliminary Testing
• GIS GRASS Integration
• Final Testing / Stress Testing
• Deployment