Train Management Control System Requirements

David Newman Eric Omanoff Shant Tashjean Sunny Zuehlsdorf

ZONT Group Train Management Control System Introduction An automated railroad management and control system is to be developed. The track network for the system consists of stations and routes between the stations. The system reads in a description of the track network, and either rejects it as invalid, or forms a model of the valid track network that it will use in its other tasks. The system displays the model of the valid track network in human-readable form. The system reads in descriptions of trains' planned journeys and checks whether the journeys are valid. If a journey is valid, the system forms a model of the train's proposed journey that it will use in its other tasks. If a journey is not valid, the submitter is informed and asked to propose another journey. The system monitors trains on the track network using input from sensors placed along the tracks. The system controls traffic lights along the tracks, which train engineers should obey. The traffic lights signal to train engineers whether or not they should proceed. A train should not proceed into a segment of track if that segment already contains a train, or if that segment is closed for safety purposes. The system also monitors trains for compliance with the control signals and the trains' planned journeys. The system will notice and respond to runaway trains that have run red lights or have deviated from their planned journeys. It will also notice and respond to ghost trains that have left a segment of track but have not appeared in the next segment within a limited time. When either a runaway or ghost train is detected, the traffic lights on that route are all turned red. The system is intended to prevent collisions between trains and promote safety.

ZONT Group Train Management Control System Glossary Crash - Two trains are in the same segment at the same time. Entry - A sensor ID for a segment that corresponds to a sensor at the entrance of the segment. Exit - A sensor ID for a segment that corresponds to a sensor at the exit of the segment. Ghost Train - A train that leaves a segment but does not appear in the next segment within a certain time interval. Journey - A list of routes and stations indicating where a train plans to go and what stations it will stop at. Light - A sensor has a light at its entrance and exit indicating red or green, intended to signal to a train whether it may or may not enter or leave the segment. LightStatus - An enumerated type with two values, RED and GREEN, corresponding to the color displayed by a light. Trains may enter or leave a segment if the corresponding light is green, and may not enter or leave a segment if the corresponding light is red. Location - The segment where a train is currently located. Operator - An actor, the person running the TMCS, who enters sets of stations and routes into the system. Plan - Each train has a plan, which is the journey it will make or is making. Route - A track between two stations, composed of one or more segments. Trains may only travel a route in one direction. Route ID - A unique identifier, consisting of three Arabic digits. Runaway Train - A train that deviates from its registered journey or runs a red light. Segment - A portion of a track between two stations, with lights and sensors at each end. Segment ID - A unique identifier, consisting of an Arabic number, indicating the location of the segment within its route. Sensor - An actor, a device that indicates to the TMCS when a train has passed. Sensors are installed at the entrance and exit of each segment. SensorID - A unique identifier, consisting of three parts. The first part is a route ID, the second is a sensor ID, and the third is either 1 or 2, indicating the sensor is at the entrance or exit of the segment, respectively. Set of Stations and Routes - The input to the TMCS, indicating the stations, routes, and segments that will be managed by the TMCS. Station - A place within a train system, where trains may begin or end routes, or stop en route. Station ID - A unique identifier, consisting of three letters. Stops - The stations where a train will stop during its journey. System - The TMCS, as referenced by other components of the system. TMCS - The Train Management Control System, which monitors sensor events, controls lights, and validates proposed journeys. Train - An object that travels between stations using routes. TrainID - A unique identifier, consisting of three Arabic digits. Train Representative - An actor, who submits a proposed journey or change to a journey to the TMCS on behalf of a train. TrainStatus - An enumerated type, indicating whether a train is a runaway, a ghost, or operating normally.

ZONT Group Train Management Control System Requirements Model

ZONT Group Train Management Control System Use Case Diagram

ZONT Group Train Management Control System Use Cases - Page 1 Use Case #1: Create a New Train With a Journey Actors: Train Representative, Operator Precondition: There are already valid sets of stations and routes in the system. Main Flow: (1) Train representative requests creation of a train with a specified journey. (2) If a train with the requested train ID exists, then the system prints a message indicating that the train ID is a duplicate. Alternate Flow: (2) If the requested journey is valid, then the system prints a message indicating that the journey has been accepted, else the system prints a message indicating that the journey has not been accepted. Postcondition: Only valid journeys are within the system.

Use Case #2: Change a Train Journey Actors: Train Representative, Operator Precondition: A train with the specified train ID already exists, the system already contains valid sets of stations and routes. Main Flow: (1) Train representative requests a new journey. (2) If the first station in the new journey is not the location of the train, the system prints a message indicating that the new journey is denied. (3) If the new journey is valid, then the system prints a message indicating that the new journey has been accepted, else the system prints a message indicating that the new journey has not been accepted. Postcondition: Only valid journeys are within the system.

Use Case #3: Enter new sets of stations and routes Actors: Operator Precondition: None. Main Flow: (1) Operator submits sets of stations and routes. (2) If the sets of stations and routes are valid, then the system prints a message indicating that they have been accepted and prints out a human-readable version, else the system prints a message indicating that the sets of stations and routes have not been accepted, and an error message is printed. Postcondition: Only valid sets of stations and routes are within the system.

ZONT Group Train Management Control System Use Cases - Page 2 Use Case #4: Trigger a Sensor Actors: Sensor, Operator Precondition: A sensor with the specified sensor ID exists (route exists, with enough segments). Main Flow: (1) A sensor transmits a report to the TMCS for a known train id on a route that is approved for that train. (2) If the train is exiting from a segment and the next segment is not a platform, then the TMCS turns the light green for the segment the train is leaving. (3) If the train is entering a segment for which the traffic light is red, then the TMCS reports to the operator that the train is a runaway train and turns all lights on that route red. Else, if the train is entering a segment for which the traffic light is green, then the TMCS reports to the operator that the train has entered the segment, and turns the traffic light for entry into that segment red. Alternate Flow 1: (1) A sensor transmits a report to the TMCS for a known train id on a route that is not approved for that train. (2) The TMCS reports to the operator that the train is a runaway train and turns the lights of the segments succeeding the runaway trains location red. (3) After the runaway train leaves that route, all of the lights on that route can be set according to the presence or absence of a train. Alternate Flow 2: (1) A sensor transmits a report to the TMCS for an unknown train id. (2) The TMCS reports to the operator that sensors are being triggered by an unknown train. Alternate Flow 3: (2) If the train is exiting from a segment and the next segment is in a station, then the TMCS turns the light green for the segment the train is leaving. The TMCS also turns the light red for the segment in the station. Postcondition: The sensor and the time it was triggered are recorded.

ZONT Group Train Management Control System Use Cases - Page 3 Use Case #5: Ghost Train Detected Actors: Operator, Sensor Precondition: A sensor with the specified sensor ID exists (route exists, with enough segments). (1) A sensor transmits a report to the TMCS for a known train id on a route that is approved for that train, indicating the train has left a segment. (2) If the next segment is not a platform, and the train does not enter the next segment after three time steps, then the TMCS reports to the operator that the train is a ghost train and turns the lights of the segments succeeding the ghost trains location red. (3) After the ghost train triggers another sensor, the TMCS sets the previously modified lights on that route according to the presence or absence of a train. Postcondition: The status of the train is correctly recorded.

Use Case #6: Crashes detected and cleared Actors: Operator, Sensor Precondition: There are at least two trains in the system with known locations. Main Flow: (1) A sensor transmits a report to the TMCS for a known train id on a route that is approved for that train, indicating the train has entered a segment that already contains a train. (2) The TMCS reports to the operator that a crash has occurred and turns the lights of the segments succeeding the crashs location red. (3) After three time iterations, the TMCS clears the crash by removing the trains from the system. The TMCS sets the previously modified lights on that route according to the presence or absence of a train. Postcondition: The trains involved in the crash are no longer in the system.

ZONT Group Train Management Control System Supplementary Requirements 1) The program should run on standard commercially available hardware, including the Linux systems available in the Computer Science labs at Colorado State University. 2) The program should be written in the Java programming language. 3) The program should be developed using an iterative incremental approach with three iterations, with deadlines of September 21, November 9, and December 10, 2009. 4) The program should be accompanied by requirements and design documents as specified by the customer. 5) The program should be developed with a team of 2-4 developers. 6) The program should display the train map for verification after a train map has been entered. 7) The program should produce output at each time step describing the state of the entire system, including: a. A list of all routes in the system and their segments, and an indication of whether or not any trains are on listed segments; b. A list of every light in the system and whether it is red or green. 8) The program should provide the user the ability to control the number of time steps executed before waiting for further input.