Computerization Is A Trend

Published Date: 02 Nov 2017

Each NCC Education assessed assignment submitted by you must have this statement attached to the assignment as the cover page or it will not be accepted for marking. Please ensure that this statement is either firmly attached to the cover of the assignment or electronically inserted into the front of the assignment.

Student declaration

I have read and understood NCC Education’s Policy on Academic Dishonesty and Plagiarism.

I can confirm the following details:

Student ID/Registration number: 00122524

Name: Liu Chun Tung

Centre Name: Unisoft IT LTD

Module Name: SAD

Module Leader: DP

Number of words:

I confirm that this is my own work and that I have not plagiarised any part of it. I have also noted the assessment criteria and pass mark for assignments.

Due Date: 26/1/2011

Student Signature:

Submitted Date: P.1

Content Page :

Statement and Confirmation of Own Work P.1

Cover Page P.2

Content Page P.3

Introduction P.4

Task 1 : Analyse the required system using OO methods and produce a Function Model P.5-36

Task 2 : Analyse the required system using OO methods and produce a Structural Model P.37-38

Task 3 : Analyse the required system using OO methods and produce a Behavioral Model P.39-

Task 4 : Research the data protection issues that apply to the system P.X

Task 5 : How the system will print tickets and address labels based on customer requirement P.X

Task 6 : Create a relational database design for the system P.X

Task 7 : How the OO approach to the system design differs from using structured methodology P.X

Task 8 : Report of the new system , detail of Task 1-7 and required hardware P.X

Review P.X

Reference P.X

Word count P.X

P.3

Introduction

Computerization is a trend in every industry. It has a lot of advantage including increase the sales amount. Upgrade of the system can increase the competitive power between similar industries. The New Heritage railway Tickets sales system is an innovation and an advanced system which can content all people needs nowadays.

The new tickets sales system will have these new features,

Record all timetable information including which steam engine will be hauling the train

Record customers details (only sales via telephone and mail)

Print tickets

Record tickets sales ( ticket type, price, date, time, buy method and take method)

Print address labels on the tickets (only for telephone and email booking)

Email facilitation ( will notify the headquarter staff about sales booking via email)

Capable allowing for further modification.

The New Heritage railway Tickets sales system is enjoying the principle of convenience, customers will feel user friendly. Therefore, the sales amount will increase.

For details, please read the following.

P.4

P.5

Task 1 – Use-case Specification

Tickets sales via Terminal

Number:

None

Req Doc Ref:

None

Name:

Tickets sales via Terminal

Status:

Working

Actors:

Customers, Terminals

Pre-requisites:

None

Goal:

Let the customer buy tickets via terminal at each station

Use-case relationship:

Extend:

Include: Print ticket, record ticket sold

Association: Customers, Terminals

Generalization:

Description:

Index

Actor event

1

Customers select tickets and it’s quantity.

2

Customers finish the payment

3

Terminal print the tickets

4

Customers take the ticket

Alternatives:

A1

Terminal is out of order

A1.1

Notification send to the station master from the terminal

A2

Ticket are not sufficient available or not available

A2.1

Show Tickets are not available on the screen

A2.2

Request customers to select again

A3

Payment are not success

A3.1

Request customers finish payment again

P.6

Task 1 – Use-case Specification

Tickets booking in person at each station

Number:

None

Req Doc Ref:

None

Name:

Ticket booking in person at each station

Status:

Working

Actors:

Customers, Station Master

Pre-requisites:

none

Goal:

Let the customer book tickets in person at each station

Use-case relationship:

Extend:

Include: Print tickets, record ticket sold

Association: Customers, Station Master

Generalization:

Description:

Index

Actor event

1

Station Master show customers the available tickets

2

Customers choose tickets

3

Station Master request payment

4

Customers finish payment

5

Customers select pick up method

6

Station Master print tickets

Alternatives:

A1

Ticket are not sufficient available or not available

A1.1

Station Master request the customer to choose again

A1.2

Customers can’t select the right ticket, cancel order

P.7

Task 1 – Use-case Specification

Book ticket via telephone or mail

Number:

None

Req Doc Ref:

None

Name:

Book ticket via telephone or mail

Status:

Working

Actors:

Customers, Clerical assistants

Pre-requisites:

none

Goal:

Let the customer book ticket via telephone or mail

Use-case relationship:

Extend: Print address labels

Include: Print ticket, record ticket sold, record customers details

Association: Customer , Clerical assistants

Generalization:

Description:

Index

Actor event

1

Clerical assistants receives order from customers

2

Clerical assistants request payment

3

Customers finish the payment

4

Clerical assistants ask customers details

5

Clerical assistants ask customers pick up method

6

Clerical assistants print the ticket

7

Clerical assistants print address labels for the customers who wants post out

8

Clerical assistants post the ticket out to the customer

9

Customers receives tickets

Alternatives:

A1

Ticket are not sufficient available or not available

A1.1

Clerical assistants ask customers to choose again

A1.2

Customers can’t select the right ticket, cancel order

A2

Customer cannot finish the payment

A2.1

Clerical assistants request payment again

A2.2

Customer finish the payment successfully

P.8

Task 1 – Use-case Specification

Book ticket via website

Number:

None

Req Doc Ref:

None

Name:

Book ticket via website

Status:

Working

Actors:

Customers, Clerical assistants

Pre-requisites:

None

Goal:

Let the customer book ticket via website

Use-case relationship:

Extend: Print address labels

Include: Print tickets, record ticket sold, record customers details

Association: Customer, Clerical assistants

Generalization:

Description:

Index

Actor event

1

Customers book take on the website

2

Clerical assistants receive an email notification

3

Clerical assistants confirm order with customers

4

Clerical assistants request customers payment

5

Customers finish the payment

6

Clerical assistants ask the customers details and pick up methods

7

Clerical assistants print the ticket

8

Clerical assistants print address labels for the customers who wants post out

9

Clerical assistants post the ticket out to the customer

10

Customers receives tickets

Alternatives:

A1

Ticket are not sufficient available or not available

A1.1

Clerical assistants ask customers to choose again

A1.2

Customers can’t select the right ticket, cancel order

A2

Clerical assistants request payment again

A2.1

Customer finish the payment successfully

P.9

Task 1 – Use-case Specification

Plans all timetables

Number:

None

Req Doc Ref:

None

Name:

Plans all timetables

Status:

Working

Actors:

Railway Manager

Pre-requisites:

none

Goal:

Plans all the time tables for Heritage Railway

Use-case relationship:

Extend:

Include: Pass it to clerical assistants to update

Association: Railway Manager

Generalization:

Description:

Index

Actor event

1

Railway Manager plans all the time tables

2

Railway Manager pass the timetables to clerical assistants to update

Alternatives:

A1

Railway Manager plans wrong timetables

A1.1

Railway Manager correct and pass it to clerical assistants to update immediately

P.10

Task 1 – Use-case Specification

Decide which steam engine will be hauling each train

Number:

None

Req Doc Ref:

None

Name:

Decide which steam engine will be hauling each train

Status:

Working

Actors:

Railway Manager

Pre-requisites:

none

Goal:

Decide which steam engine will be hauling each train

Use-case relationship:

Extend:

Include: Pass it to clerical assistants to update

Association: Railway Manager

Generalization:

Description:

Index

Actor event

1

Railway Manager decides which steam engine will be hauling each train

2

Railway Manager pass it to clerical assistants to update

3

Railway Manager has to avoid the railway crisis which is two trains on the rail at the same time

Alternatives:

A1

Railway Manager has wrong decision making

A1.1

Railway Manager correct it now and pass it to clerical assistants to update

A1.2

Railway Manager makes some notification to notify steam engine operators the information updated

P.11

Task 1 – Use-case Specification

Pass it to clerical assistants to update

Number:

None

Req Doc Ref:

None

Name:

Pass it to clerical assistants to update

Status:

Working

Actors:

Railway Manager, Clerical assistants

Pre-requisites:

none

Goal:

Let the clerical assistants to update the latest information

Use-case relationship:

Extend:

Include:

Association: Railway Manager , Clerical assistants

Generalization:

Description:

Index

Actor event

1

Clerical assistants receives the timetables and the hauling of steam engine information from Railway manager

2

Clerical assistants update these information to the database/sever/the headquarter system

Alternatives:

A1

Wrong data was updated

A1.1

Clerical assistants correct and update the right data

P.12

Task 1 – Use-case Specification

General duties

Number:

None

Req Doc Ref:

None

Name:

General duties

Status:

Working

Actors:

Clerical assistants, Station Master

Pre-requisites:

none

Goal:

Let the clerical assistants to do the general duties for the Heritage Railway and let the railway Master to manager the terminal at each station

Use-case relationship:

Extend:

Include: Pass it to clerical assistants to update, manager the terminal

Association: Clerical assistants, Station Master

Generalization:

Description:

Index

Actor event

1

Clerical assistants has to do the general duties

2

Station Master has to manage the terminal at each station

Alternatives:

A1

Clerical assistants do the wrong thing

A1.1

Clerical assistants have to correct it.

A2

Terminal is out of order

A2.1

Station Master has to restart the terminal

P.13

Task 1 – Use-case Specification

Manage the terminal

Number:

None

Req Doc Ref:

None

Name:

Manage the terminal

Status:

Working

Actors:

Station Master

Pre-requisites:

none

Goal:

Let the terminal at each station work perfectly

Use-case relationship:

Extend:

Include:

Association: Station Master

Generalization:

Description:

Index

Actor event

1

Station Master has to ensure the terminal works perfectly

2

Station Master has to test and maintain the terminal on schedule

Alternatives:

A1

Terminal is out of order

A1.1

Terminal send notification to Station Master

A1.2

Station Master restart the terminal

P.14

Task 1 – Use-case Specification

Print ticket

Number:

None

Req Doc Ref:

None

Name:

Print ticket

Status:

Working

Actors:

Terminal, Clerical assistants, Station Master

Pre-requisites:

none

Goal:

Print the ticket to the customer

Use-case relationship:

Extend:

Include:

Association: Terminal , Clerical assistants, Station Master

Generalization:

Description:

Index

Actor event

1

Terminal print the ticket to the customer by their order

2

Clerical assistants print the ticket to the customer

3

Station Master print the ticket to the customer

Alternatives:

A1

Printer cannot print the ticket to cutomers

A1.1

For terminal, Station Master change the ink for the printer

A1.2

For the printer located in the station office, station master changes the ink for the printer

A1.3

For the printer located in the headquarter, clerical assistants changes the ink for the printer

P.15

Task 1 – Use-case Specification

Record ticket sales

Number:

None

Req Doc Ref:

None

Name:

Record ticket sales

Status:

Working

Actors:

Terminal, Clerical assistants, Station Master

Pre-requisites:

none

Goal:

Record the ticket sold after the transection

Use-case relationship:

Extend:

Include:

Association: Terminal , Clerical assistants, Station Master

Generalization:

Description:

Index

Actor event

1

Record the ticket sold when there is a ticket transection via the terminal

2

Record the ticket sold when there is a ticket transection via telephone or mail

3

Record the ticket sold when there is a ticket transection via website

4

Record the ticket sold when there is a ticket transection via station master

Alternatives:

A1

Invalid data recorded by the terminal

A1.1

Station Master has to repair the terminal

P.16

Task 1 – Use-case Specification

Print address labels

Number:

None

Req Doc Ref:

None

Name:

Print address labels

Status:

Working

Actors:

Clerical assistants

Pre-requisites:

none

Goal:

Print the address labels for the customers who wants to post the ticket out

Use-case relationship:

Extend:

Include:

Association: Clerical assistants

Generalization:

Description:

Index

Actor event

1

Clerical assistants print the address labels for the customers who wants to post the ticket out

Alternatives:

A1

Printer cannot print the ticket to customers

A1.1

Clerical assistants changes the ink for the printer

A2

Clerical assistants print the wrong address labels

A2.1

Clerical assistants corrects the address

A2.2

Clerical assistants prints the ticket again

P.17

Task 1 – Use-case Specification

Record customers details

Number:

None

Req Doc Ref:

None

Name:

Record customers details

Status:

Working

Actors:

Customers, Clerical assistants

Pre-requieites:

none

Goal:

Record customers details

Use-case relationship:

Extend:

Include:

Association: Clerical assistants

Generalisation:

Description:

Index

Actor event

1

Clerical assistants record customers details during the ticket transection via website, telephone and mail

Alternatives:

A1

Clerical assistants collect the wrong data from the customer

A1.1

Clerical assistants collect the data from the customer again

A2

Clerical assistants record the wrong data

A2.1

Clerical assistants collect the data from the customer again

P.18

P.19

Explanation

There are eight activities working parallel. They are tickets sales via Terminal at each station, tickets booking in person at each station, tickets sales via mail and telephone, tickets sales via website, plan the timetable, print tickets, plan for use which steam engine and record ticket sold.

Every part of activities in the system are very important and relevance. The system has 4 ways for book or buys tickets.

For more details, there are others diagram to explain the relationship between customers and these activities.

P.20

P.21

Explanation

About this activity diagram, it showed that the process of customers buying ticket from the terminal machine at each station.

From the beginning, the Terminal machine will check the ticket availability; it will show the available tickets to the customers. If there are no available tickets, it will notify customer no tickets are available.

When it shows the available ticket, customer can choose by their need. After choosing the ticket, the terminal will check the availability again. If no, customer has to choose again. If yes, customer will have a payment.

After the payment, terminal machine will record the ticket sold (ticket type, price, date, time, destination etc) .

Then the terminal machine will print the ticket. Print the ticket information on the ticket ( Date, time, destination etc) also will write these data into the RFID tag .

All these data will be sent to the headquarter system for further verification.

Customer take the ticket. End.

P.22

P.23

Explanation

Station Master is in charged in taking ticket bookings in person at each station. About this activity diagram, it showed that the process of customers booking ticket in person at each station from station master.

From the beginning, the Terminal machine will check the ticket availability; it will show the available tickets to the customers. If there are no available tickets, it will notify customer no tickets are available and apologize to the customer.

When it shows the available ticket, customer can choose by their need. After choosing the ticket, the terminal will check the availability again. If no, customer has to choose again. If yes, customer will have a payment.

After the payment, terminal machine will record the ticket sold (ticket type, price, date, time, destination etc) .

Then the terminal machine will print the ticket. Print the ticket information on the ticket ( Date, time, destination etc) also will write these data into the RFID tag .

All these data will be sent to the headquarter system for further verification.

Customer take the ticket. End.

P.24

P.25

Explanation

Clerical assistant is responsible to the ticket sales via telephone or mail. About this activity diagram, it showed that the process of customers buying ticket via telephone or mail Clerical assistant.

From the beginning, Clerical assistants will receive order from customer. Then they will check the ticket availability; If there are no available tickets, it will notify customer no tickets are available and apologize to the customer and ask for choose again.

If the ticket chose by customer are available, clerical assistant will confirm order for them.

Then clerical assistants will request payment and record customers details at the same time.

After that, customer will have a payment.

After the payment, clerical assistants will print the ticket information on the ticket ( Date, time, destination etc) also will write these data into the RFID tag and print address label.

Moreover, clerical assistants will record ticket sold.

All these data will be sent to the headquarter system for further verification and for record.

After these procedure, clerical assistants will ask for the pick up ticket method ( Post it out or pick up on the day of their journey ) .

Customer choose post out or pick up on the day of their journey by their own need.

Customer get the ticket and enjoy the journey.

P.26

P.27

Explanation

One of the requirement of the new system is provide the ticket booking service on the railway’s website and it will have email notification to clerical assistants when there are bookings. Clerical assistant is not only responsible to the ticket sales via telephone or mail but also the website bookings. About this activity diagram, it showed that the process of customers booking ticket on the website.

Once customer ordered on the website, there are email notifications to clerical assistants for follow up action.

Clerical assistants will check the ticket availability; If there are no available tickets, it will notify customer no tickets are available and apologize to the customer and ask for choose again ( Reply via email or contact customer on phone ) .

If the ticket chose by customer are available, clerical assistant will confirm order for them (Reply email to the customer ) .

Then clerical assistant will request payment and record customers details at the same time.

After that, customer will have a payment.

After the payment, clerical assistants will print the ticket information on the ticket ( Date, time, destination etc) also write these data into the RFID tag and print address label.

Moreover, clerical assistants will record ticket sold.

All these data will be sent to the headquarter system for further verification and for record.

After these procedure, clerical assistants will ask for the pick up ticket method ( Post it out or pick up on the day of their journey ) .

Customer choose post out or pick up on the day of their journey by their own need.

Customer get the ticket and enjoy the journey.

P.28

P.29

Explanation

The Railway Manager is responded to plan all timetables. Updating the latest timetables will be done by the clerical assistant, it is their general duties. Headquarter system stored all the record including the latest timetables.

The Railway Manager plans all the timetables.

Then the railway manager will pass it to the staff who are working in the headquarter.

Clerical assistants, the staff who are working in the headquarter, tidy up the data and upload or update to the headquarter system.

Headquarter system’s data keep up to date.

Others sellers will know the latest sales situation.

P.30

P.31

Explanation

Terminal, Station Master and Clerical assistants are responsible to deal with ticket sales.

When customers book ticket via telephone or mail, clerical assistants will collect customer details.

Based on the new railway system requirements, it must be recorded customer details and print address labels for those telephone or mail bookings customer.

Therefore, the printer will print ticket information on the ticket and write these data into the RFID tag.

And the address labels for those who choose to post out ticket’s customer.

Moreover, it will print parallel.

P.32

P.33

Explanation

The Railway Manager is responded to plan all timetables and decides which engine will be hauling each train. Updating the latest timetables and information will be done by the clerical assistant, it is their general duties. Headquarter system stored all the record including the latest timetables.

The Railway Manager plans all the timetables.

Then the railway manager will post it to the staff who are working in the headquarter.

Clerical assistants, the staff who are working in the headquarter, tidy up the data and upload or update to the headquarter system.

Headquarter system’s data keep up to date.

Others sellers will know the latest sales situation.

P.34

P.35

Explanation

Terminal, Station Master and Clerical assistants are responsible to deal with ticket sales.

At the same time, when they sold tickets, they will also record tickets sold.

Based on the new railway system requirements, it must be recorded tickets sold.

When Terminal, Clerical assistants and Station Master are selling tickets, the system will automatically record their sales.

Then these record will send to the headquarter system to store of it.

P.36

P.37

Attributes and operations

For the class, customers details, it contains Name, address, Telephone no, Mobile no, ticket ID. When there are tickets transaction via telephone, mail or website, clerical assistants will record customers details also the ticket ID. Clerical assistants are responded to this task. All the customers details are in private to other class.

For the class, ticket sold, it contains salespointID, dayAndTime, PlaceID and TicketID. When there are ticket transaction in every sales way, the system will record ticket sold. If the Heritage Railway wants the sales report, the system can output a detail report for it. These data will be public in the system but encrypted.

For the class, sold method, it contains methodID and methodName. There are 4 sales methods in the system, tickets sales via terminal, ticket sales via telephone or mail, tickets sales via website and book ticket in person at each station. These data will be inserted into the class. These data will be public. System administrator can create sold method and this data will be in private.

For the class, timetables, it contains dayAndTime, PointtoPointID and steam engine. Railway Manager is responded to plan the timetables and decide which steam engine will be hauling . After these data confirmed, he will pass to the clerical assistants. Clerical assistants will create and update these data. The container of this class will be in public. System administrator and clerical assistants will join in this class.

For the class, place, it contains placeName and PlaceID. Station Name will be record in this class. PlaceName and PlaceID will be in public. System administrator can create place but hidden for other class.

For the class, P2P, it contains pointtopointID and startpointEndpoint. StartPointEndPoint is the combination of the station between station. This class will be in public . System administrator can create point to point but hidden for other class .

For the class, ticket type, it contains typeID and type. There are three types of ticket , single, day return and standard return. These data will be inserted in this class. System administrator can create and update ticket type.

For the class, sales point, it contains salespointID, salespointName, MethodID and PlaceID. Salespoint Names are the station Name or null. Method ID is ticket sales method. Check sales point is in public. Also, system administrator can create, update or delete the sales point.

For the class, ticket , it contains ticketID, pointtopointID and type ID. System administrator can create, update or delete the ticket but hidden for other class.

For the class, available ticket, it contains salespointID, stockLevel, price and dayAndTime. In this class, it shows the available ticket. The computer which is connected to the system can check available ticket. Clerical asistants can update the available and hidden for others class.

For the class, price, it contains priceID , price and ticketID. In this class it’s contain all ticket price. The computer which is connected to the system can check price of the ticket.

P.38

P.39

P.40

P.41

P.42

P.43

P.43

P.44

P.45

P.46

P.47

P.48

P.49

P.50

P.51

P.52

P.53

P.54

P.55

Task 4

a)

Principle 1 – Collected only if they are relevant to the data user’s activities and in a manner that is lawful and fair.

Principle 2 – Accurate and not retained longer than necessary.

Principle 3 – Used only for the purposes for which the data were to be used at the time of collection, unless the data subject expressly consents; and

Principle 4 – Held securely

Principle 5 – A data user’s policies and practices and the kinds, and main purposes, of personal data held; and

Principle 6 – Whether data are held relating to that individual and have the right to access and correct and correct such data.

These are the Data protection laws in Hong Kong. In my opinion, the best practice part of the data protection law is matching procedures of personal data. Because when we are asking bank for any personal account question, they will confirm our information at first. Nowadays, people in Hong Kong are more concerning personal data especially after octopus sells customers data to third party, this matching information checking is becoming more and more popular in Hong Kong. Most of the telephone hotline services no matter any industry will matched customers information after provide service especially bank or other related industry.

b) Based on the laws, it required that data must delete after it’s unless, matching customers information before make change, data user must keep a log book, transfer information outside Hong Kong etc. I would like to discuss in these 4 majors .

Delete data when it becomes useless

When we are designing the computer system, we can set the system delete customers details after the customer had journey 20days.Also, set it as automatically to ensure it will not effect by human mistake.

Matching customers information

When customers wants to ask any related to the personal data, the helper, the staff, must ask customers details and matching. The information have shown to the staff is only few part of data, there are missing button randomly, the staff must ask customers these details before make change or other actions.

Data user must keep a log book

Data user must keep a log book to record the data use. When we are designing computer system, we can design a log book for it. Anyone use or copy the data will be recorded in the log book.

Held securely

The data that collect from the customer, customers details or address labels, will be encrypted in the system in AES encrypt. If the data stolen by someone, they cannot get the data information because

It was encrypted.

c) Data of the system or customers is an invisible assets of the Heritage Railway. We must have ways to protect it. Therefore, I recommend these methods for it.

Firstly, I think education for staff is the most important especially clerical assistants, they will record

customers details ( name, address, telephone no.) , educate them the importance of data protection and protect ways. Held some examination about data protection on schedule.

Secondly, no portable device can be plug in the system, no matter terminals, headquarter computer or computer at each station. The way is to ensure that staff cannot copy or bring virus to the new computer system that cannot copy customer’s data and others. Also ensure the new system integrity.

Thirdly, do not collect sex and job etc , these information is not related. Moreover, if the customer is booked in person, station master will not collect their address because it is no need to do so.

Last but not least, based on the law, the system must delete customers information ( name, address, telephone no.) after its useless. Therefore, the system will delete these customers information within 20days automatically.

At last, build up limitation for access customers details. Only supervisor or high level manager can access these data. Less people can access these data , less opportunity to be lost or leaked.

These are my opinion and it can be implemented in the new system to ensure and the best practice in data protection.

Task 5

-Three ways to prevent ticket are easy to copy or forge

To commence, to avoid, I would like to use the RFID technology, Radio Frequency Identification. A RFID tag will be inserted into each ticket to become a RFID ticket. The RFID tag which I choose is barcode. It is not easy to be forged or copied because the data is inserted into the RFID tag.

On the other hand, not only all the information (ticket type, train time, customers name, start point and end point etc.) will be printed on the ticket but also inputted into the RFID tag. When the ticket connect to the reader , the reader will receive all the information from the RFID tag also scan the information which is printed on the ticket and check them whether correct or not .

Moreover, it will be treble check all the information between the tickets, the RFID tags and the Headquarter system to verify all the data and records .

Therefore, it prevented tickets will be easy to forge or copy.

Allow customers to select multiple tickets of different types.

There are four approaches provided to customers for buying or booking tickets, buy tickets via terminal and book ticket in person at each station and book ticket via telephone and mail and book ticket via website, during the transaction, they can select multiple tickets of different types ( Single , Day Return and Standard Return ). Therefore, the system provided 1 ways using computer and 3ways using human to book and buy tickets. I will describe in detail how it’s work.

For the computerization process, customers buying ticket via terminals at each station. Terminals will provide a GUI to the customer to simplify their buying process. In the GUI, it is clearly show that the latest timetables and the stock of different types of tickets. Customers can select by their need at once no matter it’s multiple tickets of different types or not.

After the ticket selection process, there are printing process. Due to it is the computerization process, no human will join into it. There are two machines insert into terminals , one is the ticket printer, others is the RFID writer. Printer is responded to print ticket information on the ticket. RFID writer is responded to write those data into the RFID tag which is inserted in the ticket.

For human process, when the customer take order via them, after the payment, they will print ticket for the customer. Also, print the ticket information on the ticket and write these data into the RFID tag. Moreover, there are at least two machines located in the headquarter and each station, they are printer and RFID writer.

On the other hand, due to some customers selected post out their tickets, we will also print the address labels. Printer are also responsible to print the address label.

Because of human process, they can select multiple tickets of different types for the customer.

Hardware and print media available for printing labels and tickets for the railway.

I have researched two hardware and print media. They are Datamax-O’Neil ST3210 printer and BOCA Lemur.

About BOCA Lemur , It’s Dimensions is 7.7 H x 6.5 W x 8.25 L inch, it’s weight 11.5 lbs, It can connected by USB and it can cut the ticket one-by-one automatically .It’s price is $1,195.00USD.

About Datamax-O’Neil ST3210, 1It’s dimension is 10"Hx8"Wx14"D inch, it’s weight 10kg, it can connected by centronics parallel port and USB port and it can cut the ticket one-by-one automatically also provided a tray to store of it. It’s cost $1283.50USD.

Compare with them, although Datamax-O’Neil ST3210 have more interface supported also the tray, consider the size , the brand and the need, I would like to choose BOCA Lemur because it’s size is smaller then Datamax’s one, it’s more easy to install into the terminal. Secondly, it’s price is the cheapest.

Thirdly, usb port supporting is very important and convenience to install. Thirdly, most of the enterprise are using BOCA Lemur. Other than those features , the BOCA Lemur can also print the RFID tag, the barcode, it can save a RFID writer.

Therefore, I recommend the BOCA Lemur.

Task 6 (548 words)

a)

A set of fully normalized tables showing the normalization process for each

A relational Database design for the system.

Un-normal form

Repeating

Group :

Attributes :

methodID

methodName

salesptID

salesptName

plName

plID

stockLevel

price

R

name

R

address

R

telephoneNo

R

mobileNo

R

ticketID

R

dayAndTime

priceID

p2pID

tickettyID

spep

type

se

Keys:

salesptID = sales point ID

plName = place name

plID = place ID

telephoneNo = telephone number

p2pID = point to point ID

tickettyID = ticket type ID

spep = start point end point

se = steam engine

salesptName = sales point Name

First normal form

Repeating

Group :

Primary Key:

Tables name :

Attributes :

P

Sold method

methodID

methodName

Sale point

methodID

P

salesptID

priceID

salesptName

Place

plName

P

plID

Available tickets

stockLevel

salesptID

price

R

Customers details

name

R

address

R

telephoneNo

R

mobileNo

R

ticketID

Ticket sold

salesptID

R

dayAndTime

priceID

ticketID

R

P

Ticket

ticketID

p2pID

tickettyID

P

P2P

p2pID

spep

P

Tickettype

tickettyID

type

P

Price

priceID

ticketType

price

P

Timetables

dayAndTime

p2pID

se

Keys:

salesptID = sales point ID

plName = place name

plID = place ID

telephoneNo = telephone number

p2pID = point to point ID

tickettyID = ticket type ID

spep = start point end point

se = steam engine

salesptName = sales point name

Second normal form

Repeating

Group :

Foreign Key:

Tables name :

Attributes :

Sold method

methodID

methodName

F

Sale point

methodID

salesptID

salesptName

priceID

Place

plName

plID

Available tickets

stockLevel

F

salesptID

price

R

Customers details

name

R

address

R

telephoneNo

R

mobileNo

R

F

ticketID

F

Ticket sold

salesptID

R

dayAndTime

F

priceID

F

methodID

ticketID

R

Ticket

ticketID

F

p2pID

F

tickettyID

P2P

p2pID

spep

Tickettype

tickettyID

type

Price

priceID

ticketType

price

Timetables

dayAndTime

p2pID

se

Keys:

salesptID = sales point ID

plName = place name

plID = place ID

telephoneNo = telephone number

p2pID = point to point ID

tickettyID = ticket type ID

spep = start point end point

se = steam engine

salesptName = sale point Name

Third normal form

Repeating

Group :

Composite Key:

Tables name :

Attributes :

C

Ticket sold

methodID

C

salesptID

priceID

p2pID

dayAndTime

ticketID

tickettyID

Place

plName

plID

Available tickets

stockLevel

salesptID

price

R

Customers details

name

R

address

R

telephoneNo

R

mobileNo

R

ticketID

R

Ticket

ticketID

p2pID

tickettyID

P2P

p2pID

spep

C

Tickettype

tickettyID

type

Price

priceID

ticketType

price

C

Timetables

dayAndTime

p2pID

se

Keys:

salesptID = sales point ID

plName = place name

plID = place ID

telephoneNo = telephone number

p2pID = point to point ID

tickettyID = ticket type ID

spep = start point end point

se = steam engine

salesptName = sales point Name

b) Data Dictionary

Sold method

int

methodID

varchar 2

methodName

varchar 26

Sale point

int

methodID

Varchar 2

salesptID

Varchar 6

priceID

Varchar 29

salesptName

Varchar 20

Place

int

plName

Varchar 20

plID

Varchar 10

Available tickets

int

stockLevel

Varchar 3000

salesptID

Varchar 6

price

float

Customers details

int

name

Varchar 30

address

Varchar 100

telephoneNo

Varchar 15

mobileNo

Varchar 15

ticketID

Varchar 100000000

Ticket sold

int

salesptID

Varchar 6

dayAndTime

Char(16)

priceID

Varchar 29

methodID

Varchar 2

ticketID

Varchar 10000000

Ticket

int

ticketID

Varchar 10000000

p2pID

Varchar 10

tickettyID

Char 10

P2P

int

p2pID

Varchar 10

spep

Varchar 21

Tickettype

int

tickettyID

varchar 5

type

Char 15

Price

int

priceID

Varchar 29

ticketType

Char 10

price

flow

Timetables

int

dayAndTime

Char 16

p2pID

Varchar 10

se

Varchar 11

Task 7

Explain the advantage and disadvantage of both the object-oriented and structured approaches using the system I have designed to illustrate this.

There are a advantage and a disadvantage of both the object-oriented and structured approaches in the system that I have designed.

For the object-oriented, the advantage is convenience for the programmer to finish the program, object-oriented have three models, structural model, functional model and behavioral model also there are lots of diagrams to define the system clearly. For user it is also clearly to know how it’s work.

The disadvantage of the object-oriented is the system definition is too complicated. Although the system definition, the diagram, have lots of details definition, there are too much diagrams. For example, the use case diagram, after drawing the use case diagram, we have to finish the use case specification, each use case have one specification. It is too annoying.

For the structured approaches, the advantage is better quality systems. There are three view of the SSADM, they are event view, data view and function view. The system is constructed by these views and work step by step.

The disadvantage of the structured approaches is update too slow, the structure of the system is constructed like a water fall. Every step, every changes are wants approval. Everything is changing nowadays, the system cannot update fast . Therefore , it will decrease it’s productivity . In this case, it cannot update the ticket inventory fast.

Task 8

This is the professional standard report of the New Heritage Railway system. I will describe the system from ticket sales ways, new systems features, duties of staff and the software and hardware requirement.

To commence, the ticket sales ways, there are four ways for selling tickets. Terminals, tickets sales via terminal at each station. Customers can buy ticket via terminals at each station. Few terminals will be located at each station for customers use. Terminals will print the tickets for the customers after payment, customers can pick up tickets immediately. Book tickets in person at each station, customers can book their tickets in person at each station, station master will help them to finish the transaction. Customer can choose to pick up at the journey day or after payment. Book tickets via telephone or mail, customers can book tickets via telephone or mail, clerical assistants is responsible for this. The transaction will be finished on phone or mail. Not only these sales ways but also book tickets via website, customers can book their tickets via Heritage Railway website. When customers ordered on the website, there will be an email notification to notify clerical assistants, clerical assistants will finish the transaction with customers. For the customers who booked ticket via telephone , mail or website, they can choose pick out on the journey day or post out. If these customers choose to post out , clerical assistants will print the ticket and address label and post out to the customers, at first, clerical assistants will collect and record their details. All the ticket sold will be recorded.

Secondly, features of the new system (Business system options), there are seven new features in the system. The first one is record timetable information including which steam engine will be hauling the train. When the railway manager plans the timetable and decided which steam engine will be hauling the train, he will pass these data to the clerical assistants to update. All the computer in the system can see the latest information. The second one is record customer details ( name, address, telephone number) for sales via telephone , mail or website, clerical assistants is responded to these sales, when customers buying tickets via these ways, clerical assistants will record their details. Because of the data protection laws, the system will pre-set delete these data after the journey 20days.The third one is record tickets sold, once there are tickets sales, the data inputted into the system, the system will record it’s sales. It can output the sales report. The fourth one is print tickets, for the sales via terminals, after customers payment, the printer inside the terminal will print the tickets to the customer. For sales via station master, if customers choose to pick the ticket up immediately, station master will press print tickets on the system and print it to the customer. For sales via telephone, mail or website, after customers finish the payment, clerical assistants will print the tickets for them. The fifth one is print address labels, for those customers who buy tickets via telephone, mail or website, they can choose post the ticket out. If these customers choose to post out, clerical assistants will print the address labels and post the ticket to the customer. The sixth one is the email facilities. When customers order tickets on the website, there will be an email notification to notify clerical assistants. Clerical assistants will be done the follow up action. The seventh one is capable of allowing the further modification. Due to the Heritage Railway plans to expand it’s operations within 2years, the system is designed to be can add function for the further development.

Last but not least, duties of the staff, there are three types of staff in the system ( Railway Manager, Station Master and Clerical assistants ) . For the Railway Manager, the staff who are working in the headquarter, Railway Manager is responded to plan all timetables, decide which steam engine will be hauling and pass it to the clerical assistants to update. For Station Master, the staff who are working in each station, Station Master is responded to manage the terminal at each station and help customers to book tickets. Once the terminal at each station is out of order, station master is responded to restart or repair the terminal. Moreover, customers can book tickets from the station master. For Clerical assistants, the staff who are working in the headquarter, clerical assistants are responded to update timetables, handle ticket sales via telephone, mail and website, print address labels. Firstly, update timetables, once railway manager plans all the timetables and decided which steam engine will be hauling, he will pass these data to the clerical assistants to update to the database/system/server. Secondly, handle ticket sales via telephone, mail or website, clerical assistants are responded to handle these ticket sales, when the receive customers order, clerical assistants will contact the customer and finish the transaction. Thirdly, print address labels , when the customer buy ticket via telephone, mail or website, they can choose pick up ticket at the journey day or post out, once customers choose to post out, clerical assistants will print ticket and the address labels and post out.

In conclusion, the software and hardware requirement. For the software requirement, the system should be running in the Windows XP, windows vista and windows 7. The hardware, the computer, run this system should be at least 2GB ram, Core2Duo 1.86Ghz processer and must be supporting USB port. Due to the ticket printer, it support windows OS, Linux OS or Mas OS. The most important thing is it connect the system, the computer via USB port. Therefore, the hardware requirement must be supporting USB port.

To conclude, the system is designed as an innovation and it will increase Heritage Railway productivity.

Review

In this case, I assumed that there is a server, system, database located in headquarter to record or store data ( Timetables, customers details, tickets sold and use of steam engine etc.) for terminal, clerical assistants, station master, railway manager and others use. And this system’s data will keep up to date, clerical assistants is responded to update these date to the headquarter system. Sales system and terminal will update automatically. Also, a RFID system have already been there. And the ticket printing paper had already insert RFID tag

During do the homework, I have learned a lot, how to analysis and design a system, also, I have read lots of passage on website. I have learned lots of thing that I don’t know before, for example data protection laws. I faced lots of difficulties, the most, the major difficult is the difference of language. Although I have been educate English for more than ten years, I also feel hard. It seems too difficult to express my feelings, my ideas. To solve it , I will read , write and talk more.

Moreover, due to first time to study UML, I was faced lots of difficulties to draw class diagrams, use case, sequence diagrams, state machines and communication diagrams etc. After discuss with classmate and lecture, I have a more clear concept.

Undoubtedly, this is my first homework and it’s quality is not good enough so I will read more journals, books, website and do more preparation to face the next challenge. I will do better.

Reference – Harford Harvard Reference

Website

Office of the Privacy Commissioner For Personal Data, Hong Kong,2001

The ordinance (Full text)

Retrieved from 22 January 2011

http://www.pcpd.org.hk/english/ordinance/ordfull.html

- Barcodes Inc, 2011

Ticket Printer

Retrieved from 21 January 2011

http://www.barcodesinc.com/cats/ticket-printers/

Vendini Answer, 2011

Terminal Ticket Printer

Retrieved from 21 January 2011

http://www.vendini.com/e/a.php?id=3&v=02bfbcf89f5f2c27eafcbcef7e5b9493

Book

TK law Professional Guide

Data Protection Laws , Hong Kong

Retrieved from 20 January 2011

Author Mark & Raymond 1997, p. 103

System analyses international diploma in Computer studies , 2008

NCC education

Retrieved from 3 January 2011

System Design international diploma in Computer studies, 2008

NCC education

Retrieved from 3 January 2011

Word Count

Word do not count in diagrams, specification, normalization tables , data dictionary and reference

Introduction - 167 words

Task 1 - 1275 words

Task 2 - 498 words

Task 3 - 0 words

Task 4 - 675 words

Task 5 - 704 words

Task 6 - 176 words

Task 7 - 243 words

Task 8 - 975 words

Review - 257 words

Total words – 4970 words