cse-364 new

Upload: saheb-chhabra

Post on 07-Apr-2018

218 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/3/2019 CSE-364 NEW

    1/24

    LOVELY

    PROFESSIONAL

    UNIVERSITY DESIGN PROBLEM

    CSE364

    NAME : NITIN SRIVASTAVAReg. No. : 10904052Roll No. : RK1904A06

    Section : K1904

  • 8/3/2019 CSE-364 NEW

    2/24

    ONLINE AIRLINE

    TICKET BOOKINGSYSTEM

    DEFINITIONJET Airways are one of the private airlines in India, which caters large

    number of people. It has about 10 planes in which 5 serves for domestic and

    5 for international. As the company is doing good business, they want to

    make the reservation system as a computerized Airline Reservation System.

    The plane details, their departure and arrival time, source and destination areas follows.

    S.No Plane Source Destinatio

    n

    Departure

    Time

    Arrival

    Time

    DOMESTIC

    1 JET1D01 Chennai Mumbai 10.00 11.00

    2 JET2D02 Kolkatta London 12.00 13.00

    3 JET3D03 Delhi Bangalore 11.15 12.30

    4 JET4D04 Mumbai London 13.30 14.305 JET5D05 London Delhi 15.30 17.00

    INTERNATIONAL

    1 JET01 Mumbai London 00.30 10.30

    2 JET02 Delhi Paris 03.20 13.20

    3 JET03 London Colombo 19.30 20.30

    4 JET04 Mumbai Los Angles 05.00 22.00

    5 JET05 Delhi Dubai 04.00 11.00

    The system should get the passengers details such as name, age,

    address, passport number, which plane he/she wants to travel and the

    destination point.

    The software should provide search options. If the source point and

    destination point are entered, then all the planes traveling between these

  • 8/3/2019 CSE-364 NEW

    3/24

    planes with arrival and departure time should be displayed for the sake of

    passenger.

    The software should have option for checking availability of the

    tickets. If the ticket is not available, a short message will appear as ticket

    unavailable will be displayed to the passenger. The software should have

    facility to cancel the reservation of the ticket and also can modify the

    changes if the customer has some changes in his reservation ticket.

    A small statement regarding cancellation should be displayed to

    passenger after cancellation of their tickets. The ticket which is cancelled is

    then added up to the available ticket column. The airline software should

    have the facility to print the ticket with all the details such as data, name of

    the plane, destination with timings and the class along with the passenger

    details.The price list of the ticket is also put up according to the class the

    passenger prefers to travel.

  • 8/3/2019 CSE-364 NEW

    4/24

    1. Design a SRS of the system.

    Contents1. INTRODUCTION 7

    1.1 PURPOSE1.2 SCOPE

    1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

    1.4 REFERENCES1.5 OVERVIEW

    2. OVERALL DESCRIPTION .8

    2.1 PRODUCT PERSPECTIVE2.2 PRODUCT FUNCTIONS

    2.3 USER CHARACTERISTICS

    2.4 GENERAL CONSTRAINTS

    2.5 ASSUMPTIONS AND DEPENDENCIES

    3. SPECIFIC REQUIREMENTS 113.1 EXTERNAL INTERFACE REQUIREMENTS

    3.1.1 USER INTERFACES3.1.2 HARDWARE INTERFACES

    3.1.3 SOFTWARE INTERFACES

    3.1.4 COMMUNICATION INTERFACES3.2 SOFTWARE PRODUCT FEATURES

    3.2.1 FEATURE 1

    3.2.1.1 PURPOSE3.2.1.2 STIMULUS/RESPONSE

    3.2.1.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

    3.2.1.3.1 FUNCTIONAL REQUIREMENTS3.2.1.3.1.1 INTRODUCTION3.2.1.3.1.2 INPUTS

    3.2.1.3.1.3 PROCESSING

    3.2.2 FEATURE 23.2.2.1 PURPOSE

    3.2.2.2 STIMULUS/RESPONSE

    3.2.2.3 ASSOCIATED FUNCTIONALITY REQUIREMENTS3.2.2.3.1 FUNCTIONAL REQUIREMENTS

    3.2.2.3.1.1 INTRODUCTION

    3.2.2.3.1.2 INPUT

    3.2.2.3.1.3 PROCESSING3.2.2.3.1.4 OUTPUT

    3.2.3 FEATURE 3

    3.2.3.1 PURPOSE3.2.3.2 STIMULUS/RESPONSE

    3.2.3.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

    3.2.3.3.1 FUNCTIONAL REQUIREMENTS

  • 8/3/2019 CSE-364 NEW

    5/24

    3.2.3.3.1.1 INTRODUCTION

    3.2.3.3.1.2 INPUT

    3.2.3.3.1.3 PROCESSING3.2.3.3.1.4 OUTPUT

    3.2.4 FEATURE 4

    3.2.4.1 PURPOSE3.2.4.2 STIMULUS/RESPONSE

    3.2.4.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

    3.2.4.3.1 FUNCTIONAL REQUIREMENTS3.2.4.3.1.1 INTRODUCTION

    3.2.4.3.1.2 INPUT

    3.2.4.3.1.3 PROCESSING

    3.2.4.3.1.4 OUTPUT3.4 DESIGN CONSTRAINTS

    3.5 SOFTWARE SYSTEM ATTRIBUTES

    3.5.1 RELIABILITY

    3.5.2 AVAILABILITY

    3.5.3 SECURITY

    3.5.4 MAINTAINABILITY

    3.5.5 PORTABILITY

    3.6 LOGICAL DATABASE REQUIREMENTS

    3.7 OTHER REQUIREMENTS4. INDEX .16

    5. APPENDICES .16

  • 8/3/2019 CSE-364 NEW

    6/24

    ONLINE AIRLINE TICKET BOOKING SYSTEM

    SOFTWARE REQUIREMENTS SPECIFICATION

    1. INTRODUCTION

    1.1. PURPOSE

    The main purpose of this software is to reduce the manual errors involved in

    the airline reservation process and make it convenient for the customers to

    book the flights as when they require such that they can utilize this software

    to make reservations, modify reservations or cancel a particular reservation.

    1.2 SCOPE

    The name of the software is AIRLINE RESERVATION SYSTEM. This

    software provides options for viewing different flights available with

    different timings for a particular date and provides customers with the

    facility to book a ticket, modify or cancel a particular reservation but it does

    not provide the customers with details of cost of the ticket and it does not

    allow the customer to modify a particular part of his reservation and he/she

    can modify all his details.

    1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

    ARS-Airline Reservation System

    LAN-Local Area Network

    GUI-Graphical User Interface

    OS-Operating System

    RAM-Random Access Memory

    MB-Mega Bytes

    GB-Giga BytesMbps-Mega bits per second

    HDD-Hard Disk Drive

  • 8/3/2019 CSE-364 NEW

    7/24

    1.4 REFERENCES

    The books and materials referred during the pre-development stages of the

    project include

    1. Software Engineering-A Practitioners Approach

    By Roger S. Pressman

    2. Software Engineering-By James Peters

    1.5 OVERVIEW

    The rest of the document deals about all the main features of this software

    each will its purpose and its main functions. It also gives details about the

    interface with other products and related functionality of each product.

    2. OVERALL DESCRIPTION

    2.1 PRODUCT PERSPECTIVE

    The ARS software is an independent application. It is a self-contained

    product. The system interfaces, user interfaces and hardware interfaces

    related with this software are defined as follows.

    2.1.1 System Interfaces

    The client systems should be able to share the data available in the data basethrough the network connection.

    2.1.2 User Interfaces

    The screen formats and menu structure should be in such a way that even

    have users will find it easy to use. The product must be use-friendly and very

    inter-active. The functionality provided by the system like displaying error

    messages should adapt itself to the different users of the software.

    2.1.3 Hardware Interfaces

    Nil

    2.1.4 Software Interfaces

    Name of the language: Visual Basics

  • 8/3/2019 CSE-364 NEW

    8/24

    2.1.5 Communication Interfaces

    There is an LAN used for communication among the different client systems

    to be used.

    2.1.6 Memory Constraints

    The system would require disk space of 10 GB and a 256 MB HDD and 64

    MB RAM for client systems.

    2.1.7 Operation

    The users can first make a reservation in a particular flight for a particular

    date and time. The system provides the customer with a pin code which

    gives him access to either make any changes in his reservation or cancel a

    reservation. These must also be back up of data to enable any easy recovery

    from any features.

    2.1.8 Site Adaptive Requirements

    The ARS software is an independent and self-contained product and no

    modification are required to adapt to a particular installation.

    2.2 PRODUCT FUNCTIONS

    The major functions include

    Providing flight details

    Flight bookings for a particular destination, date and time and alsoproviding with a pin code.

    Allowing the customer to modify or cancel his reservation provided

    the correct pin code is given.

    Displaying a report of the number of people flying in a particular

    flight.

    2.3 USER CHARACTERISTICS

    No technical experience is required basic knowledge of handling system is

    sufficient.

  • 8/3/2019 CSE-364 NEW

    9/24

    2.4 CONSTRAINTS

    Regulatory policies: It is a mandatory that no text book must be left

    empty or contains insufficient data. Hardware limitations: There must be a 64 MB on board memory

    Control functions: The software must be very user-friendly and

    display appropriate error messages.

    Interfaces to other applications: Not applicable.

    Parallel operations: It must support many users simultaneously.

    Reliability requirements: Data redundancy and use of special/blank

    characters must be avoided.

    Safety/security considerations: The application must be exited always

    normally. Higher order language requirements: VB

    2.5 ASSUMPTIONS AND DEPENDENCIES

    It is assumed that the details of the cost of ticket are already known to the

    customer. Future changes like providing different types of flights with

    different classes like business class, economic class will allow the customers

    to benefit from one facility.

    2.6 APPORTIONING OF REQUIREMENTS

    The necessity of providing options to customer to choose their seat or to

    choose for economic or business class can be delayed until future versions of

    the software are developed.

  • 8/3/2019 CSE-364 NEW

    10/24

    3. SPECIFIC REQUIREMENTS

    3.1 EXTERNAL INTERFACE REQUIREMENTS

    3.1.1 User Interfaces

    The interface must be easy to understand. The user interface includes

    SCREEN FORMATS/ORGANIZATION: The introductory screen

    will be the first to be displayed which will allow the users to choose

    either of the two options, viewing flight detail or booking a ticket.

    WINDOW FORMAT/ORGANIZATION: When the user chooses

    some other option, then the information pertaining to that choice will

    be displayed in a new window which ensures multiple windows to be

    visible on the screen and the users can switch between them.

    DATA FORMAT: The data entered by the users will be alpha

    numeric.

    END MESSAGES: When there are some exceptions raising error like

    entering invalid details, then error messages will be displayed

    prompting the users to re-enter the details.

    3.1.2 Hardware Interfaces

    The system must basically support certain input and output devices. Their

    descriptions are as follows.

    Name of Item Description of Purpose Source of Input/Description of output

    Key board To accept data from

    user like pin code,

    personal details, flight

    details

    Source of Input

    Printer To print the bookings

    mode E.g.: Destination

    chosen with date and

    timings

    Destination of Output

    3.1.3 Software Interfaces

    Not applicable since the product under considerations is an independent one.

  • 8/3/2019 CSE-364 NEW

    11/24

    3.1.4 Communication Interfaces

    Every client system connected through LAN establishes a communication

    only with the server and not with any client system. An LAN of 10 Mbps is

    used.

    3.2 SOFTWARE PRODUCT FEATURES

    3.2.1 FEATURE 1

    The ability of the software is to provide the details of the flights available

    and allow the customers to choose a particular destination and make a

    reservation.

    3.2.1.1 PURPOSE

    The purpose of this is to enable the users to view the different flightsavailable so as to make it convenient for him to make a reservation.

    3.2.1.2 STIMULUS/RESPONSE

    Once the user chooses the particular option, the web pages

    corresponding to that are to be displayed on the screen i.e., it will

    display the different flights available to their respective destinations

    and allow the customer to book a ticket.

    3.2.1.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

    3.2.1.3.1 FUNCTIONAL REQUIREMENTS

    Once the user makes a reservation, he must be provided with a

    pin code.

    3.2.1.3.1.1 INTRODUCTION

    The user must be provided with the required information within

    10 seconds.

    3.2.1.3.1.2 INPUTSThe user must enter the destination with date and timings and

    must make reservation by giving his personal details like name,

    address, age, gender, nationality.

    3.2.1.3.1.3 PROCESSING

  • 8/3/2019 CSE-364 NEW

    12/24

    Recognizing the correct details are entered that a message is

    displayed confirming his reservation and displays the pin code.

    3.2.2 FEATURE 2

    The software allows the user to modify an already existing reservation

    made by the customer if in case there are any changes that are to be

    modified in the reservations of the ticket.

    3.2.2.1 PURPOSE

    The purpose is to allow the customer to make any changes in his

    personal details or flight booking details.

    3.2.2.2 STIMULUS/RESPONSE

    Once the user requests for changing his reservation, it must be

    displayed on the screen prompting the customer to enter his pin code.

    3.2.2.3 ASSOCIATED FUNCTIONALITY REQUIREMENTS

    3.2.2.3.1 FUNCTIONAL REQUIREMENTS

    If the pin code provided by the customer does not match, then

    would notify the person by displaying error messages.

    3.2.2.3.1.1 INTRODUCTION

    The system will allow the customer to modify his reservation

    provided correct pin code has been entered by him.

    3.2.2.3.1.2 INPUT

    The user should enter his pin code which gives him access to

    modify his reservation.

    3.2.2.3.1.3 PROCESSING

    The pin code is processed and checked for his validity. If it is

    correct then the user can modify his reservation else an error

    message will be displayed asking the user to enter the correctpin code number.

    3.2.2.3.1.4 OUTPUT

    Given the correct pin code, the user can now modify his

    reservation. A new pin code will be generated for the

    customers.

  • 8/3/2019 CSE-364 NEW

    13/24

    3.2.3 FEATURE 3

    The software allows the user to cancel an already existing reservation made

    by the customer who has booked the ticket.

    3.2.3.1 PURPOSE

    The purpose is to allow the customer to cancel his reservation if not

    required.

    3.2.3.1 STIMULUS/RESPONSE

    Once the user requests for canceling his reservation, it must be

    displayed on the screen prompting the customer to enter his pin code.

    3.2.3.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

    3.2.3.3.1 FUNCTIONAL REQUIREMENTS

    If the pin code provided by the customer does not match, then it

    would notify the person by displaying error messages.

    3.2.3.3.1.1 INTRODUCTION

    The system will allow the customer to cancel his reservation

    provided correct pin code has been entered by the customer.

    3.2.3.3.1.2 INPUT

    The user should enter his pin code which gives him access to

    cancel his reservation.

    3.2.3.3.1.3 PROCESSING

    The pin code is processed and checked for its validity. If it is

    correct, then the user can cancel his reservation else an error

    message will be displayed asking the user to enter the correct

    pin code number.

    3.2.3.3.1.4 OUTPUT

    Given the correct pin code, the user can now cancel his

    reservation.

  • 8/3/2019 CSE-364 NEW

    14/24

  • 8/3/2019 CSE-364 NEW

    15/24

    3.3 PERFORMANCE REQUIREMENTS

    At any instant, a maximum of four nodes or users will be given accesssimultaneously.

    Since the program handles multiple users, if more than one person

    attempts to same date to the files stored in the data base, the program

    will lock the data file using a 2-phase commit protocol to prevent

    simultaneous access.

    3.4 DESIGN CONSTRAINTS

    Requires 256 MB on-board memory.

    Based completely on Windows functionality platform.

    The software should be portable and must be inaccessible to

    unauthorized users.

    3.5 SOFTWARE SYSTEM ATTRIBUTES

    3.5.2 RELIABILITY

    The factors needed to establish the software expected reliability are

    The user inputs should be valid and within the given range.

    Normal termination of the program.

    3.5.2 AVAILABILITY

    The factors guarantee the softwares availability includes proper termination

    and correct input details. Also the resources used for the project

    development are Microsoft Certified which speaks of its high quality

    standards.

    3.5.3 SECURITY

    It must be ensured that access will be provided to the authorizedpersons through user ID and password.

    Network security will be provided by the use of firewalls.

    Checks can be performed at regular internals to ensure data integrity.

  • 8/3/2019 CSE-364 NEW

    16/24

    3.5.4 MAINTAINABILITY

    The software will be developed by implementing the concept of modularity

    which in turn reduces the complexity involved in maintaining it. The

    administrator should have a sound technical knowledge about maintaining

    the software and further enhancements will be undertaken by the developer.

    3.5.5 PORTABILITY

    The application is portable which ensures its adaptability for use on different

    computer terminals with different operating systems and standards.

    3.6 LOGICAL DATABASE REQUIREMENTS

    The system requires the use of text files to maintain the customers personaldetails and his booking details. An entity must be used to specify the various

    departments and the seats available in them. This information will be used

    frequently by the authorities for verification.

    3.7 OTHER REQUIREMENTS

    4. INDEX

    5. APPENDICES

  • 8/3/2019 CSE-364 NEW

    17/24

    UseCaseID: Search for Flights

    Goal In Context: A customer wishes to search for available flights between two cities for the

    chosen dates.

    Scope: Airline Reservation System (ARS)

    Pre-Condition: Actor has successfully navigated to the main options screen.Success End Condition: A list of flight matching the search criteria is presented.

    Failed End Condition: A list of flight matching the search criteria is NOT presented.

    Primary Actor: Customer

    Trigger Event: Selects the "Search Flights" option.

    Main Success Scenario

    Step Actor Action Description

    1 Customer Selects the "Search Flights" option.

    2 ARS Displays a screen with input fields for source airport, destination airport, : tyof ticket (one way or round trip) and the departure and arrival date based on

    choice of ticket type. Two-way ticket will force an arrival date to be entered.3 Customer Enters the all information and clicks the "Search" button.

    4 ARS Displays a listing of all flights that match the customers input from step 3, ea

    item in the list has an associated price and a "Book This Flight" link.

    Scenario Extensions

    Step Actor Action Description

    1 Customer Selects the "Cancel" option.

    2 ARS Displays the main options screen.

    3 Customer Does not complete all the necessary fields.

    4 ARS Redisplays the input fields from step 2 with the input data and a note stating

    that certain required data is missing.

    Scenario Variations

    Step Actor Action Description

    None

  • 8/3/2019 CSE-364 NEW

    18/24

    UseCaseID: Purchase Ticket

    Goal In Context: A customer wishes to purchase the ticket for a reserved flight.

    Scope: Airline Reservation System (ARS)

    Pre-Condition: Actor has successfully made a reservation as documented in the "Make

    a Reservation" use case.

    Success End Condition: A ticket has been purchased.

    Failed End Condition: A ticket has NOT been purchased.

    Primary Actor: Customer

    Trigger Event: Selects the "Purchase Ticket" link from the list of options.

    Main Success Scenario

    Step Actor Action Description

    1 Customer Selects the "Purchase Ticket" link from the list of options.

    2 ARS Displays a screen with an input field for a reservation number.

    3 Customer Enters a reservation number and clicks the "Submit" button.

    4 ARS Displays the details of the reservation.

    5 Customer Selects the "Purchase Ticket" option.

    6 ARS Displays a screen with input fields for: a credit card number,

    cardholder name, and credit card expiration date.7 Customer Enters a credit card number, the cardholder name and the credit card

    expiration date and clicks the "Submit" button.

    8 ARS Displays the main options screen. The message "Ticket Successfully

    Purchased" is also displayed.

    Scenario Extensions

    Step Actor Action Description

    3.a Customer Selects the "Cancel" option.

    3.a.1 ARS Displays the main options screen.

    5.a Customer Selects the "Cancel" option.

    5.a.1 ARS Displays the main options screen.

    7.a Customer Selects the "Cancel" option.

    7.a.1 ARS Displays the main options screen.

    7.b Customer Selects the "Use Credit Card on Record" option; this is illegal and

    hence may have to go.

    Scenario Variations

    Step Actor Action Description

    NONE

  • 8/3/2019 CSE-364 NEW

    19/24

    DATA FLOW DIAGRAM:

    LEVEL 0:

    LEVEL 1(a):

    LEVEL 1(b):

    User ReservationAcceptthe

    details

    Passenger

    Database

    User AirlinereservationSystem

    Reserve in

    the file

    Reservati

    on

    Displa

    y

    Cancellatio

    n

    UserCancellatio

    n

    Acceptthe

    details

    Passenger

    Database

    Cancel in

    the file

  • 8/3/2019 CSE-364 NEW

    20/24

    LEVEL 2:

    ACTIVITY DIAGRAM

    Activity diagram is another important diagram in UML to describe dynamic

    aspects of the system.Activity diagram is basically a flow chart to represent

    the flow form one activity to another activity. The activity can be described

    as an operation of the system.So the control flow is drawn from one operation to another. This flow can be

    sequential, branched or concurrent. Activity diagrams deals with all type of

    flow control by using different elements like fork, join et

    Branching

    A branch specifies alternate paths takes based on some Boolean expression

    Branch is represented by diamondBranch may have one incoming transition and two or more outgoing one on

    each outgoing transition,you place a Boolean expression shouldnt overlap

    but they should cover all possibilities.

    UserDispla

    y

    ReadPassenger

    details

    Customerdatabase

    Display in

    tabular

    form

  • 8/3/2019 CSE-364 NEW

    21/24

    Forking and Joining

    Fork

    A fork represents the splitting of a single flow of control into two or more

    concurrent

    Flow of control.

    A fork may have one incoming transition and two or more outgoing

    transitions, each of which represents an independent flow of control.

    Below fork the activities associated with each of these path continues in

    parallel.

    Join

    A join represents the synchronization of two or more concurrent flows of

    control.

    A join may have two or more incoming transition and one outgoingtransition.

    Above the join the activities associated with each of these paths continues in

    parallel.

    Swimlane:

    Swimlanes are useful when we model workflows of business processes to

    partition the activity states on an activity diagram into groups.

    Each group representing the business organization responsible for those

    activities,these groups are called swimlanes.

  • 8/3/2019 CSE-364 NEW

    22/24

    ACTIVITY DIAGRAM FOR MAKING RESERVATION

    Select Flight

    Available

    Submit Request

    Not Available

    Accepted Rejected

    Payment

    View Report

  • 8/3/2019 CSE-364 NEW

    23/24

    ACTIVITY DIAGRAM FOR CHANGING RESERVATION

    Cancel

    Reservation

    New reservation Get R efunded

    Submit Request

    Select F light

    Accept Rejec t

    View Report

  • 8/3/2019 CSE-364 NEW

    24/24