Case Overviews

Use Case Name: Collect Data Primary Actor: SYSTEM ID: 1 Importance Level: HIGH Use Case Type: DETAIL, ESSENTIAL

Stakeholders and interests: System needs data to function Sensors needs to send data somewhere Sister System Sister system is a fail over system, it needs the most current data Information Systems Management needs to know if something is wrong Brief Description: This use case describes how the systems gets data. Trigger: System queries sensors Type: Internal Relationships: Association: Sensors Include: Sensor type and location Extend: Append record, store data Generalization: Normal Flow of Events: 1. System queries all sensors 2. Sensor sends type of sensor and location 3. System verifies sensor record 4. Sensor sends data 5. System appends sensor record 6. System calls Sister System 7. Sister system sends ACK 8. System sends sensor record and CRC 9. Sister system verifies CRC and sends ACK Subflows: S-1: contact sister system 1: Sister system does respond 2: Sister system does not respond Alternate/exceptional Flows: 4a: system creates new record for sensor and location 4b: system writes new sensor record data 4c: system flags data for review by Information Systems management S-1, 2a: System sends urgent notification to Information Systems Management

Use Case Name: BACKUP DATA Primary Actor: BACKUP SYSTEM

ID:

Importance Level: HIGH

Use Case Type: DETAIL, ESSENTIAL

Stakeholders and interests: System an off site backup in the event the primary and sister system crashes Information Systems Management needs to know if something is wrong Brief Description: This use case describes how we handle data backups Trigger: Backup system internal timer Type: External Relationships: Association: Backup System Include: Extend: Generalization: Normal Flow of Events: 1. The daily system timer executes 2. Backup system contacts System 3. System send ACK 4. Backup system sends backup query to System 5. System executes backup query 6. System sends backup data to Backup system with CRC 9. Backup system verifies CRC and sends ACK Subflows: S-1: Contact System 1: System does respond 2: System does not respond S-2: backup query 1: append backup 2: full weekly backup Alternate/exceptional Flows: S-1, 2a: Backup system sends urgent notification to Information Systems Management

Use Case Name: SHARE DATA Primary Actor: USERS Stakeholders and interests: Users users need access to data Sister System this is the fail over system

ID:

Importance Level: HIGH

Use Case Type: DETAILED, ESSIENTIAL

Brief Description: This use case describes how we share data with users. Trigger: Users queries Type: External Relationships: Association: Users Include: Extend: Generalization: Normal Flow of Events: 1. User sends query 2. System verifies Users access rights 3. System checks System load 4. System executes query Subflows: S-1: System checks System load 1: System load is 75% or higher 2: System load is below 75% Alternate/exceptional Flows: S-1, 1a: if the system load is 75% or higher, send the request to the Sister System

Use Case Name: Maintain Data Primary Actor: SYSTEM

ID:

Importance Level: HIGH

Use Case Type: DETAILED, ESSIENTIAL

Stakeholders and interests: System the system has a lot to process, it cant be bogged down by inefficient data Information Systems Management management needs to know what is going on Sister System - Sister system is a fail over system, it needs the most current data Brief Description: This use case will describe how the System will maintain the data Trigger: Record response time Type: Internal Relationships: Association: System Include: Extend: Store Data Generalization: Normal Flow of Events: 1. The System will constantly monitor record response time 2. When the response time reaches 75% of critical, the System will contact the Sister System 3. Sister System will send ACK 4. The System will hand over all function 5. The System will notify Information Systems Management 6. The System will initiate data optimization 7. The System will retake control from Sister System 8. System will update records from Sister System 9. The System will notify Information Systems Management Subflows: S-1: System contacts Sister System 1: System does respond 2: System does not respond S-2: Data Optimization 1: Check Disk for error and Defragment 2: Attempt repair of incomplete records 3: Remove duplicate records Alternate/exceptional Flows:

Use Case Name: Model Traffic Patterns Primary Actor: SYSTEM

ID:

Importance Level: MED

Use Case Type: DETAILED, ESSIENTIAL

Stakeholders and interests: System The system is where the primary process will take place Sister System - Sister system is a fail over system, it needs the most current data Users Users need to be able to interact to override or make changes as needed Brief Description: This use case will describe how the system models traffic patterns as well as how the user interacts with the system and model

Trigger: System Type: Internal Relationships: Association: build model Include: Share Data Extend: analyze, store data Generalization: Normal Flow of Events: 1. System builds Traffic Model 2. System builds Traffic Pattern 3. System analyze Traffic Model 4. System analyze Traffic Pattern 5. System builds projected Traffic Model 6. System outputs recommended data 7. System writes new record 8. System sends data to Sister System 9. Modeling Restarts Subflows: S-1: System builds Traffic Pattern 1: System retrieves 30 min data interval 2: System analyze traffic pattern 3: System optimizes Traffic Signal Timing S-2: System builds Traffic Model 1: System retrieves past Traffic Model 2: System retrieves one month data interval 3. System builds new Traffic Model 4. System analyzes Model 5. System builds new Projected Traffic Model Alternate/exceptional Flows: 7: User input new values requires reanalysis S-1, 3a: User Override

Use Case Name: Model Road Degradation Patterns Primary Actor: System

ID:

Importance Level: MED

Use Case Type: DETAILED, ESSIENTIAL

Stakeholders and interests: System The system is where the primary process will take place Sister System - Sister system is a fail over system, it needs the most current data Users Users need to be able to interact to override or make changes as needed Brief Description: This use case will describe how the system models Road Degradation as well as how the user interacts with the model.

Trigger:System Type: Internal Relationships: Association: build model Include: Share Data Extend: analyze, store data Generalization: Normal Flow of Events: 1. Subflows:

Alternate/exceptional Flows:

Use Case Name: Dispatch Emergency Services Primary Actor: System Stakeholders and interests: Brief Description:

ID:

Importance Level: HIGH

Use Case Type: DETAILED, ESSIENTIAL

Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events:

Subflows:

Alternate/exceptional Flows:

Use Case Name: Monitor Air Quality Primary Actor: System Stakeholders and interests: Brief Description:

ID:

Importance Level: LOW

Use Case Type: DETAILED, ESSIENTIAL

Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events:

Subflows:

Alternate/exceptional Flows:

Use Case Name: Model Future City Expansion Primary Actor: Users Stakeholders and interests: Brief Description:

ID:

Importance Level: LOW

Use Case Type: DETAILED, ESSIENTIAL

Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events:

Subflows:

Alternate/exceptional Flows:

Use Case Name: Primary Actor: Stakeholders and interests:

Blank Template ID: ______ Use Case Type:

Importance Level: ____

Brief Description:

Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events:

Subflows:

Alternate/exceptional Flows: