2005 a1 - josh swift

8/4/2019 2005 A1 - Josh Swift

1/13

RailLink

System for Supporting thePublic Train Transport Network

By Josh Swift

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

2/13

2 | Page

Part 1Requirements Workflow.

Key requirements of the desired system

Themain aim of the desired new system is to make the experience ofthe system users

(commuters) the best it can possiblybe.

The Key requirements of the system have been summarised. These requirementshavealso

been classified as being either functional or non functional requirements of the RailLink

system .

1. Platform screens and speakers.

These willprovide accurate, up to date information about all incoming and outgoing trains ateachof the stations. These screens and speakers will also be utilised for the purpose of providing

community information messages and various forms of advertisement to commuters .- Non functional requirement

2. Assist users with disabilities.System must be user friendly to comply with commuters with disabilities. Public announcementspeakers will be installed on the platforms to provide visually impaired persons with the

information they desire.- Non functional requirement

3. Delays, cancellations and additions.

System must be capable of dealing with Delays, Cancellations and Additions to the RailLink

services. Must be capable of accurately estimating all trains ETAs at every station.

- Functional requirement

4. Real time information.

The ability for the system to efficiently and effectively manage real time information is vital to its

success. RailLink staff are to be provided with real time information on their personal computers

of all incoming and outgoing trains at each station. Real time information will also be displayed

on the platform screens and issued through the audio speakers at each of the various stations.

- Functional requirement

5. SMS service + RailLink website

Provide simular functions.

The SMS service allows commuters to receiveinformation on delays +ETAs of their trainson

their mobile phones.

While the web query page is provided to display information about all train lines and times.

BothFunctional requirements

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

3/13

3 | Page

System Actors_______________

The following is a set of actors that will be used to model the use cases for the system.The

roles the actors perform are also discussed here.

Actors:

1. Commuters: The passengers/people that use the RailLink system

- They purchase tickets and travel on the trains to their required destinations

2. Station supervisors:

- Help toensure that commuters/passengers know which platform to wait on for their train.

- The supervisorshave a personal computer which tells them the next trains due to arrive or travelpastthe station (based on live information and standard timetables), and allows them to assigneach train to a particular physical line/platform.

-They must make this decision no later than 5 minutes before the train is due to arrive.If they dont make a decision, then a default value is used.

3. Operational headquarters staff:

- Responsible for entering much of the static (or semi-static) information about the train networkand train fleet into the system.

- Also responsible for uploading the videos of commercials and community safetyannouncements, and designating the times when, and stations where, these are to be played.

4. Train Drivers:

- Guide the trains from station to station

- Responsible for stopping at correct stations/platforms andforthecorrect amount of time

- The driver of the traintriggers audio announcements 10 seconds prior to train departing

when they press the button to close the train doors.

5. Signalling system:- The system that manages the track controllers, which mechanically shift trains from one track toanother in order for the train to arrive at desired station platforms.

- Detects train delays via radio frequencies and sends to information system.

(Note: The Signalling System is connected to the service information via software links).

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

4/13

4 | Page

Use Cases_______________

The following is a set of the use cases for this system, considering the actors and the

requirements.

For each use case, it is stated whether or not they input new data into the system, perform

processing, or reporting about data that is already in the system.

Commuter Use Cases:-RequestTrainInformation (reports about data thats already in system)

- PurchaseTickets (inputs new data into system)

- BoardCorrectTrain (reports about data thats already in system)

Station Supervisor use cases:

- AssignTrainToPlatform (inputs new data into system)

- DetermineRF-ID (inputs new data into system)

Operational head quarters staff use cases:

- UploadVideos (inputs new data into system)

- EnterTrainInformation (inputs new data into system)

Train driver use cases:

- CheckStationStatus (reports about data thats already in system)

- TriggerAnnouncements (performs processing in system)

- StopAtStations (reports about data thats already in system)

Signalling system use cases:

- ShiftTrain (performs processing in system)

- DetectDelay (inputs new data into system)

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

5/13

5 | Page

Detailed Use Case Descriptions_

The following are detailed use case descriptions for 2 input use cases, 2 processing use cases,

and 2 reporting use cases.

Input Use Cases:

Use Case:PurchaseTickets

ID:2.

Brief description: A commuter purchases train ticket(s).

Primary actors: Commuters.

Secondary actors:None.

Preconditions:

1.Commuter must have sufficient funds to make purchase.

Main flow:

1. Commuter researches the correct train to catch and from which platform.(on station screen) .

2. Commuter approaches ticket machine and inserts money.

3. Commuter selects desired options and collects ticket(s).

Post conditions:

1.Commuter must keep ticket to board train.

Alternative flows:None.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

6/13

6 | Page

Use Case:DetectDelay

ID:12.

Brief description: Detecting a train that has been delayed. Trains are fitted with radio-frequency transmitters that

are emitting a signal to uniquely identify a train. As they leave a station, this signal is detected by a device

connected to the RailLink information system.

Primary actors: Signalling system.

Secondary actors: Station supervisor.

Preconditions:

1.A train must be running behind schedule.

Main flow:1. A train is held up for whatever reason (longer than expected at a station, issue with track availability or signal

etc.).

2. Thetrainpasses one of various radio frequency detectors on the train line.

3. This signal is detected by devices connected to the RailLink information system and the trains unique RF- ID

helps to identify this train as being delayed.

4. The specific train is now marked as delayed and this information is processed in the system. A new estimated

time of arrival (ETA) can now be calculated and be provided to commuters.

Post conditions:None.


Processing use cases:

Use Case: TriggerAnnouncements

ID:9.

Brief description: An audio announcement is triggered 10 seconds prior to a train departing, based on expected

train departure time.

Primary actors: Train Driver.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

7/13

7 | Page

Secondary actors: Signalling system.

Preconditions:

1.Train must be stopped at a platform.

2. Train drives pushes a button to close doors .

Main flow:

1. Train stops at station platform and doors open.

2. Passengers board, exit or stay on train.

3. Driver pushes a button which sends out a radio frequency which triggers announcement .

4. Announcement is heard.

5. The doors will begin to close 10 seconds after button is pushed.

6. Train departs.



Use Case:ShiftTrain

ID:11.

Brief description: Moving a train from one track to another in order for it to arrive at the correct platform at the

specified station.

Primary actors: Signalling system.

Secondary actors: Station supervisors.

Preconditions:1.A decision must be made about what platform the train is destined to arrive at 5 minutes prior to the train

arriving at the station.

Main flow:

1. Station supervisor decides which platform a train is to arrive at no later than 5 minutes prior to the trains

arrival.

2. If supervisor does not make a decision.

3. Else.

3.1. A default value is used.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

8/13

8 | Page

Post conditions:1: Train changes onto new track.

2. Train arrives at desired platform.


Reporting Use Cases:

Use Case: CheckStationStatus

ID:8.

Brief description: Train driver receiving information about upcoming stations. For example how busy they are,

which platform they are going to arrive at, the time in which they are due to arrive at each of the various stations

etc.



Preconditions:

1.Train and station data must be already entered into system.

Main flow:

1. Trains being assigned to platform.

2. Operational HQ staff entering information about train network and train fleet into system.

3. Drivers being provided with a timetable regarding their train.

3. Driver being provided with upcoming station status for piece of mind.



http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

9/13

9 | Page

Use Case:StopAtStation

ID:10.

Brief description: Drivers stopping at correct stations.



Preconditions:

1.Train and station data must be already entered into system.

Main flow:

1. Trains being assigned to platforms.

2. Operational HQ staff entering information about train network and train fleet into system.

3. Drivers being provided with a timetable regarding their train.

3. Drivers gaining information about the stations they are required to bypass and the ones they are required to stop

at.



http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

10/13

10 | Page

Use Case Diagram____________

The following is a use case diagram that incorporates all identified use cases and actors.

RailLink

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

11/13

11 | Page

Part 2Analysis workflow

Sets of Classes______________

The following are sets of classesthat are to be used by the system. These sets have beenbroken up into 2 groups. A definition is provided for eachnominated class that describes its

key responsibility/purpose within the system .

-(1.) Classes that represent important information for the system.

- Train

Purpose is to monitor all the trains that are used in the RailLink public transport system.Usedfor the purposeof assigning unique radio-frequency IDs to trains so they can be tracked

and directed to the right platforms at the right stations etc.

- Platform

Data on all platforms is provided. For example platform name/number, suburb and so on.

Responsible for keeping track of trains that have been assigned to specific platforms. Managingthe platform allocations of trains is a key responsibility of this class.

- StationInformation on all of the stations is provided (suburbs, time it takes to travel from station tostation, how many station screens there are at a particular station, how many staff are required ateach stationetc). All this can be managed and maintained with the station class.

-AnnouncementManages the timing when announcement are due to be made (e.g 10 seconds before a traindeparts, after the driver pushes the button to close the doors). The announcements are automatedmessages to commuters which can be properly maintained using this class.

- Updates (Delay, cancellations and additions)

Key requirement is to assess these three issues in real time. This class will update the traintimetable, including information on station + platform screens etc. System will be updatedafter asensor detects a delayed train or a RailLink Staff member updates the system with a cancellationor an addition to a service. This integral information will be managed via this class.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

12/13

12 | Page

-(2.)Classes whichsupport to processing requirements and use cases.

- Tickets

Provides information on the range of tickets available andcalculates the price.

- Video (Advertisement/community message)

Provides the logic to display these uploaded videos at the correct times. For example, thesemessages cannot be displayed within 2 minutes of the next train arriving.

- Lines/route

Manages the information about all the separate train lines (which trains run where and when) .

Also which stations can be found on each line etc.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

8/4/2019 2005 A1 - Josh Swift

13/13

13 | Page

Analysis Class Diagram________

The following is a UML Analysis Class Diagram that shows the classes and the relationships

they have with the other classes in the system.

http://www.SmartP

DFC

reator

.com

http://www.SmartP

DFC

reator

.com

http://www.Sma

rtPD

FCreator

.com

http://www.S

martPDFC

reator

.com

http://www.S

martPDFC

reator

.com

2005 a1 - josh swift

Documents