A Ticket Selling System Computer Science Essay

Published:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

This system is designed for your company station selling ticket system. As your information, your company has 3 steam engines (Morning Sun, Moonlight and Daybreak). They were running amongst 5 stations in accordance with the designated schedule.

There are three types of tickets, Single, Day Return and Standard Return (return within 30 days). Passengers will book the tickets in front of the counters face to face. They could also reserve the tickets by either E-mail or phone. Our system will record customer name, address, phone number and E-mail if they reserve the ticket by E-mail and phone. These customer details will be used to send their tickets by post office. For posting the ticket, the system will print label about customer details on the tickets. Clerical assistants will be easy to post the ticket to the customers. The ticket will show ticket type, start station, destination, price, date, and time. The customer could also pick up the tickets at the designated station. The system will have user friendly GUI (Graphic User Interface) that user will add or edit ticket information.

Your company is expected to expand the business or special events after a few years. The system will have the edit page for allowing the Railway Manger to edit price, date, time, station and add new steam engine.

Use case diagram

In this system, when customers want to book the tickets, there are three ways to book the tickets. First, they can go to station directly. Second, phone to hotline and third through E-mail.

When they book in person in a station directly, the station master shall request the compulsory information, such as start and end stations, date, time. If the customers want to book a day return or month return (return within 30 days), the station master will take start day only. When station master input the ticket information of what customer needs, the system will show that start station information about the departure time of the start station. After the customer confirms the time, the station master will re-confirm the information with customers prior to the issuance of the tickets. After the customer confirms the ticket and pay, the station master will print ticket and hand it to the customer.

If the customers phone to the hotline or send an E-mail, the clerical assistants will follow the customer orders to book the tickets. Otherwise the customers will provide their credit card number to complete to payment at this time. The customers' call or E-mail should be included their personal information. Customers could go to station to pick up ticket or post ticket to customers. If go to station to pick up, customers will receive the E-mail include to booking number. Customer will go to station and show the E-mail with booking number to station master. Station master will check the booking number in the system and print that ticket. If post the ticket, Clerical assistants will print label and ticket and then post it to customers before journey 2 days.

If the customers want to cancel the ticket, the customers will phone to hotline or send an E-mail. Clerical Assistant will follow and cancel the booking.

Railway Manager can update on the system regarding the schedule by updating station information, time table and ticket price, the engine arrangement of hauling the trains. If the company has ether a new station or a new engine, Railway Manager can add the new station or the new engine into system. He could also update the price schedule and time table of the trains

Use case specification

As per your request we design the system has 5 cases. Check Station Location, Select ticket type, Select go/return date, Select time and Input customer information. Station master, clerical assistants and Customer will have action on these 5 cases

Use case specification - Check Station Location

Number:

UC10001

Req Doc. Ref

1

Name:

Check Station Location

Status:

Working

Actors:

Station Master, Clerical Assistants, Customer

Pre-requisites:

None

Goal:

Record station start and end point. Start and end point are not a

same station

Use-case Relationships:

 

Extend:

 

Include:

 

Association:

Station Master, Clerical Assistants, Customer

Generalisation:

 

Descriptions:

Index

Actors event

1

Member request station start point

2

Member request station end point

3

Check start and end point are not same station

4

Station Master, Clerical Assistants confirm booking

 

 

Alternatives:

Index

Actors event

A3/1

Invalid data

A3/1.1

Start and end point are same station

 

 

 

 

 

 

Station master, clerical assistants and customer will check the start station and the end station. Station master and clerical assistants have to make sure the customers to provide the station start and end point correctly. No ticket shall have the as same station for start and end point. Different departure have different price.

Use case specification - Select Ticket Type

Number:

UC10001

Req Doc. Ref

2

Name:

Select ticket Type

Status:

Working

Actors:

Station Master, Clerical Assistants

Pre-requisites:

None

Goal:

Record ticket type, show the ticket price.

Use-case Relationships:

Select go/return Date, Select go/return time

Extend:

 

Include:

 

Association:

Station Master, Clerical Assistants

Generalisation:

 

Descriptions:

Index

Actors event

1

Member request ticket type. Only one type

2

Auto show ticket price. Only one price

3

Station Master, Clerical Assistants confirm.

 

 

 

 

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

Station master and clerical assistants shall confirm the ticket type with the customer. Ticket has 3 types (Single, Day Return and Standard Return). But the ticket shall have type only one type, one start station, one end station and one price. Different ticket types will have different ticket with one price and select start time at the start station.

Use case specification - Select Go/Return date

Number:

UC10001

Req Doc. Ref

2.1

Name:

Select go/return Date

Status:

Working

Actors:

Station Master, Clerical Assistants

Pre-requisites:

None

Goal:

Record OS date and select date on the system.

Use-case Relationships:

Select ticket type, Select go/return time

Extend:

 

Include:

 

Association:

Station Master, Clerical Assistants

Generalisation:

 

Descriptions:

Index

Actors event

1

Record OS date.

2

Select date on the system.

3

When ticket type is "Single" or "Day return", select only one date

4

When ticket type is "Standard Return", select one date and automatic

select after 30 days

5

Station Master, Clerical Assistants confirm.

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

When the customers confirm the ticket type, station master and clerical assistants will follow customers they want. When single type is selected, the system will go to select time because ticket can be used only once. Otherwise, Day Return and Standard Return will just choose start date. The customers can use Day Return ticket for return journey on the same day or Standard Return any time within 30 days.

Use case specification - Select Time

Number:

UC10001

Req Doc. Ref

2.2

Name:

Select time

Status:

Working

Actors:

Station Master, Clerical Assistants

Pre-requisites:

None

Goal:

Check and record every station departure.

Use-case Relationships:

Select ticket type, Select go/return date

Extend:

 

Include:

 

Association:

Station Master, Clerical Assistants

Generalisation:

 

Descriptions:

Index

Actors event

1

Check every station departure.

2

Member requests departure.

3

Station Master, Clerical Assistants confirm.

 

 

 

 

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

This is only designed for ticket type "Single". When the customer chooses Single and confirms date and the start station, the system will show the schedule of the departure time of the station. Customers will select the departure time. Station master and clerical assistants will record the time on the system.

Use case specification - Input customer information

Number:

UC10001

Req Doc. Ref

3

Name:

Input customer information

Status:

Working

Actors:

Clerical Assistants, Customer

Pre-requisites:

None

Goal:

Record customer information for send the ticket to them

Use-case Relationships:

 

Extend:

 

Include:

 

Association:

Clerical Assistants, Customer

Generalisation:

 

Descriptions:

Index

Actors event

1

Record customer name, address, phone No. and E-mail

2

Clerical Assistants confirms.

 

 

 

 

 

 

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

When customers call to station or send E-mail to book ticket, customer will include their personal information. Clerical assistants will input their personal information to system. When ticket printed, clerical assistants will print their name and address. Finally post to customer.

Use case specification - Editing

Number:

UC10001

Req Doc. Ref

4

Name:

Editing

Status:

Working

Actors:

Railway Manager

Pre-requisites:

None

Goal:

Update station information, time table and ticket price.

Add new station and new engine.

Use-case Relationships:

 

Extend:

 

Include:

 

Association:

Railway Manger

Generalisation:

 

Descriptions:

Index

Actors event

1

Update station information, time table and ticket price

2

Add new station and new engine.

3

Delete station and engine.

 

 

 

 

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

Stations' timetable, price have been controlled by Railway manager. If the company has ether a new station or a new engine, Railway Manager can add the new station or the new engine into system.

Use case specification - Delete Ticket

Number:

UC10001

Req Doc. Ref

5

Name:

Delete Ticket

Status:

Working

Actors:

Clerical Assistant

Pre-requisites:

None

Goal:

Delete customer ticket book before post it.

Use-case Relationships:

 

Extend:

 

Include:

 

Association:

Clerical Assistant

Generalisation:

 

Descriptions:

Index

Actors event

1

Delete ticket

 

 

 

 

Alternatives:

Index

Actors event

 

 

 

 

 

 

 

 

 

 

When the customers want to cancel booking, the customers will call or E-mail to clerical assistant. Clerical assistant will follow and cancel the ticket.

Activity Diagram

The system will have 4 actions. They are booking Ticket, Making Ticket, Checking Station Information and Recording Customer Information divided into 3 stages.

Fig.1 Fig.2 Fig.3

At the first stage, station master or clerical assistants will select station start and end point. Our system will check station selection correct or not (Fig.1).

At the second stage, the system will go to ticket stage book ticket and make ticket. The system will follow station master or clerical assistants to select customer ticket type, go/return Date, time. When there is wrong selection, the system will return to ticket type selection to request station master or clerical assistants to select again (Fig.2).

At the third stage, the system will go to input customer information. That is optional because when customers could go to station to buy ticket in person. However, this will be compulsory for clerical assistants if customers call or E-mail to book ticket. They will input the customers' personal information to post their ticket or pending for the customer to pick up at the station on or before the date of journey (Fig.3).

At the final stage, the system goes to last print out the ticket. When customers go to station to buy, station master will print ticket to them. When phone or E-mail to book ticket, clerical assistants will print customers' personal information label for post the ticket to them or allowing them to pick up the ticket at the station on or before the date of journey.

Class Diagram

This class diagram will show our system database relationship. The database has 3 main classes (Station, Customer and Ticket).

At Station, this class is used for recording your 3 steam engines information and print into the ticket. Railway Manger will arrange these 3 engines in accordance with the timetable. Customers will know which engines are they travel.

Ticket is divided into 3 classes (Single, Standard Return and Day Return). These 3 classes will have 2 classes (Date and Time) to follow. Date is to record year month day on system. This is automatic from OS. Time is record the departure time. At the Single, Standard Return and Day Return. These 3 classes have recorded price of each station. Include Date class and Time class. At Ticket class, it records the Type ID to show on ticket. It just selects 1 type only.

Customer class is a single class. It records customers' personal information for clerical assistants print label to post ticket to customers.

Sequence Diagram

For Sequence Diagram, we break down 2 figures for station master and clerical assistants.

Sequence Diagram - Station Master

Fig. 1

On the Fig.1 is station master, Customer order the ticket. Station master will follow customer to select Station ID and Type ID for station start and end point. Type ID is about ticket type, price, date and time (optional). When customers confirm the details, the customer will make payment accordingly. When confirm the payment, final station master will print the ticket to customers.

The customers will book the ticket by phone or E-mail. Station master will check the

Sequence Diagram - Clerical Assistant

Fig.2

On the Fig.2, the customers will order the ticket by phone or E-mail. Customers will provide their name, address, phone number, E-mail and credit card number to clerical assistant. Clerical assistant will follow customer request to create the ticket record. The system shall allow time (2 days) for posting the ticket. The input of the shorter time will be considered to be invalid and the system will return to the beginning stage. At the payment clerical assistant will make payment to credit card center and confirm. When it is confirmed, the customers shall choose ticket pick up selection. When post to customer, clerical assistant will print ticket and post ticket to customers. When pick up on journey day, they will send the confirm mail to customers. The E-mail will include the booking number. Customers will go to station and pick up with station master on journey day.

When the customers will cancel the ticket, they will call hotline or E-mail to clerical assistant. Then clerical assistant will follow the cancel order.

State Machines

Fig.1

Fig.2

These 2 figures are about the system's state. Figure 1 is station master. It has 4-5 action. Select station, select ticket type and select date. When ticket is Single, it will have more 1 action - select time. Make payment and finally is confirm print the ticket.

Figure 2 is clerical assistant state. It has 6-7 action. Select station, select ticket type and select date. When ticket is Single, it will have more 1 action - select time, input customer Information. Then make payment. When confirm payment it will print the ticket and customers name and address label. Clerical assistant will post ticket to customers.

Communication Diagram

Fig.1

Figure 1 is station master's communication diagram.

Firstly, the customer requests a ticket, station master will input station start and end point. System will use start and end point to find station ID. Then station master will ask customer ticket type and date. If they buy "Single", system will show the option is time to select which time do customers use this ticket. Station master input this data to system. System will show date, time (optional) and price. Customer should be confirmed the all ticket information is their request. Then station master will make payment for customers and confirm payment on this time. Finally station master will print the ticket.

Fig.2

Figure 2 is clerical assistants' communication diagram. Customers can phone or E-mail to request the ticket. Clerical assistants will follow their E-mail or phone call to make ticket. First clerical assistant read customer E-mail or listen the call. Then select station start and end point. . System will use start and end point to find station ID. Then input ticket type and date. If they buy "Single", system will show the option is time to select which time do customers use this ticket. Then input customer's personal information. System will make payment. When confirm payment system will print the ticket and customer name and address label. Finally clerical assistant will post to customer

Data protection

Base on Office of the Privacy Commissioner for Personal Data, Hong Kong Special Administrative Region. Prohibition against transfer of personal data to place outside Hong Kong except in specified circumstances (No.33 CHAPTER 486 PERSONAL DATA (PRIVACY) ORDINANCE 2001 Office of the Privacy Commissioner for Personal Data, Hong Kong) and Repeated collections of personal data in same circumstances circumstances (No.35 CHAPTER 486 PERSONAL DATA (PRIVACY) ORDINANCE 2001 Office of the Privacy Commissioner for Personal Data, Hong Kong).

In our system, we design all users have user login to control user level. Basically users are classified into 4 levels. The levels are Administrator, Editor, Power User and User.

Administrator is the highest level. He has the highest authority to control the system. He can create account, edit system database, make the log sheet, etc. This level would be controlled by IT Department.

Editor is a higher middle level. He can update the station information, ticket price, timetable, add new station and engine, etc. This level would controlled by Railway Manger.

Power user is a lower level. He can read log sheet and edit station and price on the system. But he cannot create account and make log sheet. He could also amend the information of the input errors by the operatives. This level includes Department Supervisor or high; such as station master.

User is a limited account. It is a low level. He can produce ticket and record customers' information. This level includes all operatives; such as the clerical assistant. Clerical assistant are the lowest user. If ticket has some mistakes when they input and confirmed they could not correct everything. They will call power user or high to correct the ticket data.

The system administrator would be under by your IT Department to control and create user. They will take the log sheet for every user which the system uses everyday. The log sheet would controlled by IT Department and it will be kept for 6 months. IT Department can make log sheet hardcopy and softcopy. If have any problem IT Department will provide log sheet to Department Head to make decisions. Every user could not output customers' personal information to hardcopy and softcopy. Supervisor or higher level could be read the database customers' information list only. The customers' information will remove by our system at the last input that information on 12 months. Also customers just tell station master or clerical assistant their name and phone number. It will search that information. It will not ask as same customer their information again within 12 months.

Printing

As the label printer, we search the Zebra, Brother and Casio to have label printer. We suggest Zebra 110xi4 and Brother QL-550 label printer because these companies have supplied these products in the market for many years. In Hong Kong most companies and government departments have used their products. The size of these printers is smaller than other printers. As your station, the call center will have 3 clerical assistants. The office area may be small. The printer will be put it on desk corner. Their specifications are on P.28-P.30.

As the ticket printer, we think the customer service center will show clear. We suggest the Datamax SV-3210 because this is the professional ticket printer. SV-3210 design is installing inside the desk. It will be safe area. Many airlines, trains and bus companies are using this. This specification is on P.31.

Printer specification

 

 

Zebra 110xi4

Brother QL-550

Print methods: Thermal transfer or direct thermal (is thermal type good)

Housing Color

Blue/Silver

 

Operation Modes

PC Connected only

Construction: 12-gauge steel frame 

Cutter

Auto

 

Cutter Life

up to 10,000 (die-cut labels) 5,000 (continuous labels)

Single 32 bit 133 Mhz RISC processor 

Maximum Print Speed (labels per min.)

50

 

Display

1 color LED

16 MB SDRAM; 8 MB non-volatile Flash memory 

Tape Sizes

Die Cut and Continuous

 

Maximum Tape Width (inches)

2.4

Automatic media/ribbon sensing capability 

Maximum Print Width (inches)

2.3

 

Maximum Label Length

3 feet

Improved head test for element out

Maximum Resolution (dpi)

up to 300 dpi

 

Font Styles

TrueType dependent

Auto calibration

Memory

N/A

 

Memory for Transferred Data (number)

No

Clear media side door for ease of supplies monitoring

Symbols for Windows ( No. of Clip arts in P-touch Editor)

1,379

 

Multiple Copies

Up to 9,999 copies

300 unique darkness settings

Mirror Printing

Yes

 

Vertical Printing

Yes

RS-232, Parallel ports

Rotate Printing

Yes

 

Date/Time Stamp

PC Generated

USB 2.0 port 

Bar-codes Types

Code 39, 1-2/5, UPC-A, UPC-E, EAN 13, EAN 8, CODABAR (NW-7), CODE 128, EAN 128, POSTNET, Laser Bar Code, ISBN-2, ISBN-5, PDF417, QR CODE, Data Matrix

 

Microsoft® Add-ins

Yes

Internal ZebraNet 10/100 PrintServer

Database File Compatibility

csv, txt, mdb, xls

 

Software

P-touch® Editor 4.2 & P-touch® Address Book 1.0 for Windows® & P-touch® Editor 3.2 for Mac OS®

ZPL or ZPL II Programming Language

Networking

Optional

 

Interface

USB

XML enabled printing

Compatibility

Windows® & Mac OS®

 

Operating System

Windows® 2000, XP Home/Pro, Windows Vista®, Windows® 7; Mac OS X 10.6.x

Mirror feature allows user-defined printer configurations to be retrieved from the network

Carton Contents

Starter rolls: DK-1201 Die-cut Standard Address Labels (100 labels), plus DK-2205 2.4" Continuous Length Paper Tape (25 ft.), USB Cable, Quick Start Guide, CD (includes software & user's guide)

 

Housing Dimensions

5.7" (W) x 7.6" (D) x 5.9" (H)

Create and design customizable printer LCD menus

Warranty

1 Year Limited Warranty & Replacement Service

 

Options

PS-9000 Print Server

Large (240W x 128H pixel), graphical, multilingual, backlit LCD display 

 

 

 

 

 

Transmissive and reflective media sensors 

 

 

 

 

 

Multi-level Element Energy Equalizer (E3) for superior print quality 

 

 

 

 

 

Unicodeâ„¢ - Compliant

 

 

 

 

 

Intelligent printhead

 

 

Datemax SV-3210/3306

For integrated box office applications, the Datamax SV-3210 and SV-3306 ticket printers are designed specifically for vertically oriented, in-counter installation and operation. Using the same high performance electronics and firmware as the Datamax ST models, the SV printers are designed to eject the printed ticket from the top of the printer utilizing either a manual tearplate, or an integrated rotary cutter mechanism. 

STANDARD FEATURES

• 10 ips print speed (3210), 6 ips print speed (3306)

• 203 dpi print resolution (3210), or 300 dpi print resolution (3306)

• Self-loading, self-aligning print mechanism

• Adjustable ticket sensor

• Adjustable media width guides

• 3.25" maximum media width

• 3.15" maximum print width

• 3-button, 3-LED control panel for maximum configuration flexibility and printer status indication

• Open vertical orientation to accommodate in-counter installation and operation

• Two internal printer languages: Datamax Printer Language (DPL) and Datamax Ticket Printer Language (DTPL).

Protection

The ticket is composed of 3 parts. That is customer ticket, ticket of start point and ticket of end point. It will have barcode and watermark to protect each part. The barcode will use ticket number, Station start and end point ID and make calculation. The barcode will show on ticket. Watermark is pre-printed on the ticket with fluorescent ink and could only, shown under ultraviolet lamp.

When customers go to take the train, customers must be buy the ticket and go to sluice gate. Then they would insert the ticket into the sluice gate. Sluice will use ultraviolet lamp to scan the ticket. Then it will calculate the barcode to make sure the station start point. If this is true ticket, the portion the ticket of start point will be cut and return the stub of the ticket to the customer. The customer shall collect the stub of the ticket and go. If not, the gate will open the sluice gate.

At the destination station, customer will go through the sluice gate again. Sluice gate will check the watermark and barcode. The barcode will calculate the end station. If it true, it will cut out ticket of end point. Customer will leave. If not, customer could not leave the station.

Multiple Tickets Type

For customers buy 2 or more tickets type to take railway service. The system will include multi tickets function. When customers need to buy the multi tickets, they can tell to station master or clerical assistants. They will record their need one-by-one. Station master and clerical assistants will see the icon for buy multi ticket type. The system will have space to save that customer ticket record temporary. It will calculate total tickets and price. Customers confirm that and station master or clerical assistants will make the payment and print these tickets.

Customers could buy more than 1 ticket and ticket type at one time. But the ticket will be 1 ticket, 1 type and 1 start and end point. It is because multi type and multi start and end point ticket control very difficult. The cost is very high.

Normalisation

This is the system the third normalisation.

In the system have Station, Steam Engine, Customer, Ticket Type, Single, Day Return, Standard Return, Time, Date, and Temp Database.

Steam Engine will be always run to each station. The station will have own timetable. We design Steam Engine will connect to station.

Single, Day Return and Standard Return will connect to Ticket Type. These three types will show customer what ticket he buys, how much it is, and what date and time. In the Single, Day Return and Standard will have Time and Date to connect. Date is show these three types what date is the customer goes to and ticket last day. Time is for Single. It is record the departure time. Customer must go to the train on time. If customer late the ticket it will be lost.

Customer is single database. It is record the customers' personal information to post the ticket to them and has recorded by clerical assistant.

As customer order more than 1 ticket. We design the system will have the temporary database - Temp for station master and clerical assistant to record customers order. When customers order more than 1 ticket, first, station master or clerical assistant book the ticket one-by-one. Second, the ticket will save to Temp on the system temporary. When the customer orders confirm these tickets, finally Station Master or clerical assistant will re-confirm these tickets and make a payment.

Database Dictionary

Class Number

Class Name

Field Name

Field Type

Field Width

Field Description

1

Steam Engine

Engine ID

String

3

Primary Key

Engine Name

String

20

 

2

Station

Station ID

String

5

Primary Key

Station_1

String

20

 

Station_2

String

20

 

3

Ticket

Type ID

String

30

Primary Key

Type

String

20

Search the Class: Single

Standard Return & Day Return

4

Single

Price

Double

3,2

e.g: $100.11

5

Standard Return

Price

Double

3,2

e.g: $100.11

6

Day Return

Price

Double

3,2

e.g: $100.11

7

Time

Time

Date

 

 

8

Date

Date

Date

 

 

9

Customer

Customer ID

Integer

10

Primary Key

Name

String

50

 

Address

String

100

 

Phone No.

String

10

 

E-mail

String

50

 

Description

The system is designed for your company selling ticket and easy mange the system data. Such as station, departure, timetable and price to add and update, in the station, Railway Manger, station masters and clerical assistant always use this system. We are designed the system GUI (Graphic User Interface) for user easy to do every job and main system for storage data to server.

In the system, when customers need to book ticket. They have 3 ways to book the tickets (Go to station directly, phone to hotline or E-mail).

When they book in person in a station directly, station master shall request the compulsory information, such as start and end stations, date, time. If the customers want to book a day return or month return, station master will take start day only. The system will auto calculate 30 days to out of date this ticket when the customer select Standard Return type. When station master input customers what need the system will show that start station information about the departure time. When customers confirmed the time, station master will re-confirm the information with customer with the detail. After the customer confirms the ticket and pay, station master will print ticket and hand it to customer.

When customer phone to hotline or send E-mail, clerical assistants will follow customer orders to book the ticket. Otherwise customers will provide their credit card number on E-mail or call to finish payment at this time. Customers' call or E-mail should be included their personal information. Clerical assistants will print label and ticket and ship it to customers.

Our ticket use point-to-point and single function because the database to easy control. When customers need to 2 or more type they will have 2 or more ticket. This is not convenience but customers would see which station start and departure, price clearly. Your company has 3 steam engines, single type advantages will because show 3 steams engine which the customer travel.

Some stations have used the ticket of ticket has fix price. The travel price will decrease on that ticket. This ticket is the best but the cost is very high. It is not just to ticket cost. Otherwise sluice gate, printer, etc the cost will high than other.

Into database, we designed simple because could use low performance. Railway Manger, station master, clerical assistant have been use this system everytime. The data transfer speed is very important. Simple database will reduce the server work load and increase data transfer and server calculation speed. Selling processes will be smoothly.

On the class -- Ticket Type, it normalize Single, Day Return and Standard Return 3 classes. Class - Single connect to Date and Time 2 classes. Day Return and Standard Return, these 2 classes just connect Date only. When station master or clerical assistant help customers to book ticket, system will show start day only. When station master input customers what need the system will show that start station information about the departure time. When select Standard Return, system will calculate 30 days after start day automatically. This function convenient station master and clerical assistant.

Writing Services

Essay Writing
Service

Find out how the very best essay writing service can help you accomplish more and achieve higher marks today.

Assignment Writing Service

From complicated assignments to tricky tasks, our experts can tackle virtually any question thrown at them.

Dissertation Writing Service

A dissertation (also known as a thesis or research project) is probably the most important piece of work for any student! From full dissertations to individual chapters, we’re on hand to support you.

Coursework Writing Service

Our expert qualified writers can help you get your coursework right first time, every time.

Dissertation Proposal Service

The first step to completing a dissertation is to create a proposal that talks about what you wish to do. Our experts can design suitable methodologies - perfect to help you get started with a dissertation.

Report Writing
Service

Reports for any audience. Perfectly structured, professionally written, and tailored to suit your exact requirements.

Essay Skeleton Answer Service

If you’re just looking for some help to get started on an essay, our outline service provides you with a perfect essay plan.

Marking & Proofreading Service

Not sure if your work is hitting the mark? Struggling to get feedback from your lecturer? Our premium marking service was created just for you - get the feedback you deserve now.

Exam Revision
Service

Exams can be one of the most stressful experiences you’ll ever have! Revision is key, and we’re here to help. With custom created revision notes and exam answers, you’ll never feel underprepared again.