15
AN AUTOMATED TICKET ISSUING SYSTEM USED AT A RAILWAY STATION. Submitted to : Prepared by Forhad Rabbi Md. Saiful Islam Asst. Professor Reg:2005331074 CSE, SUST Sheikh Nabil Mohammad Reg:2006331004

An automated ticket issuing system

Embed Size (px)

DESCRIPTION

Software engineering case study- automated ticketing system

Citation preview

Page 1: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM USED AT A RAILWAY STATION.Submitted to : Prepared by

Forhad Rabbi Md. Saiful Islam

Asst. Professor Reg:2005331074

CSE, SUST Sheikh Nabil Mohammad

Reg:2006331004

Page 2: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

In a railway station automated ticket issuing system should have the following requirements:

The system should be fast enough to handle huge amount of transaction.

System must have the ability to provide security.

Page 3: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

So, according to this requirements we have designed a system mentioning the following common steps:

1.System Structuring.2.Control Modeling.3.Module Decomposition.

Page 4: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

System Structuring:

In system structuring we have used Client- Server model.

Page 5: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Page 6: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Why Choosing Client Server Model ? In client server model distribution of data is

fast and straight forward. This model utilize network model effectively. Client server model is more scalable than

other models. Here security is better than repository model.

Though abstract machine which uses layered architecture is also very secured but it is not perfect for this case.

Page 7: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

END OF PART - 01

Page 8: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Control Modeling:This modeling is of two types:1. Centralized control modeling2. Event driven control modeling

In our proposal we have applied centralized modeling. Because, in event driven control modeling, if the value of an event changes then all subsequent value also changes. So, this modeling is not appropriate here.

Page 9: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Centralized control modeling:

In this we have used call and return model.

Page 10: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Page 11: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Why choosing Call and Return Model?

Here each subsystem calls another subroutine, and finally when value is found, it returns the value to the caller.

In Manager model, full system is dependent to one manager, for this manager model is not appropriate here.

Page 12: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM Module Decomposition:

There are two models in Module Decomposition:

1. Object Oriented 2. Data Flow

Here we have chosen Data Flow model for our proposal.

Page 13: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Page 14: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

Why choosing Data Flow Model?

This model is straight forward and easy to understand.

Implementing data flow model is more easier than Object oriented model.

Changing object interface is Complicated and complex entities are hard to represent as object.

Page 15: An automated ticket issuing system

AN AUTOMATED TICKET ISSUING SYSTEM

THANK YOU ALL

----END-----