sdd
Post on 17-Oct-2014
115 Views
Preview:
TRANSCRIPT
ONLINE TICKET BOOKING
SYSTEM
SOFTWARE DESIGN DESCRIPTION
SUBMITTED BY,
AMMU.C (09BCE333)
SHRUTHI.R (09BCE444)
TABLE OF CONTENTS
1. Introduction 1.1. Purpose 1.2. Scope 1.3. Glossary 1.4. Overview of document
2. Architecture design 2.1.client server model 2.2.manager model 2.3.class diagram
3. Data structure design 3.1. Data field types and sizes.
4. Use case diagram
5. Use case realizations 5.1 Use Case:Login Use Case:New account Use Case:Change password Use Case:Ticket cancellation Use Case:Add bus/train/flight Use Case:Booking ticket 5.2 Collaboration:Add new b/t/f details Collaboration:Ticket cancellation Collaboration:Booking ticket
6. Activity diagram
7. Interface design 7.1 login page 7.2 registration page 7.3 select comfortable journey 7.4 search bus 7.5 book ticket 7.6 search flight 7.7 admin page 7.8 add bus
TABLE OF FIGURES
Figure 1: Client Server ModelFigure 2: Manager ModelFigure 3. Class DiagramFigure 4: Use Case DiagramFigure 5: Sequence Diagram:loginFigure 6: Sequence Diagram:new accountFigure 7: Sequence Diagram:change passwordFigure 8: Sequence Diagram:ticket cancellationFigure 9: Sequence Diagram:add bs/train/flightFigure 10: Sequence Diagram:booking ticketFigure 11: Collaboration Diagram: Add new b/t/f detailsFigure 12: Collaboration Diagram: ticket bookingFigure 13: Collaboration Diagram: ticket cancellationFigure 14 : Activity DiagramFigure 15: Login Page Figure 16: Registration Page Figure 17: Select Comfortable Journey Figure 18: Search Bus page Figure 19: Book Ticket page Figure 20: Search Flight page Figure 21: Admin Page Figure 22: Add Bus page
Section 1
1. Introduction
The purpose of this document is to analyze the design details, architectures and other various relationships involved in developing the online ticket booking system(OTBS).
1.1 Purpose
The purpose of Software Design Document (SDD) is to describe the design details, architectures and entity-relationships involved in the development of the online ticket booking system. Design Specification includes activity diagrams, to describe activities and flow of data or decisions between activities; sequence diagrams, to model object interactions arranged in time sequence and to distribute use case behavior to classes;state chart diagrams, to describe the dynamic behavior of a system in response to external stimuli; and class diagrams, to depict classes and their interrelationships, to describe structure and behavior in the use cases, to provide a conceptual model of the system in terms of entities and their relationships, and for requirement capture and end-user interaction.
1.2 Scope
This document contains a complete description of the design of Toll Gate System. The basic architecture is a web server from a client server paradigm.The designated administrator in charge of the Online Ticket Booking System will have full access to make changes, as he/she deems necessary. The changes could include, but not limited to,updating system details,sending email if necessary and report generation.
1.3 Glossary
Term Definition
Administrator The person who manages and administrates the toll database and can make required changes.
OTBS Online Ticket Booking System
Database Collection of all information.
Member
SDD
Users who check or book tickets.
Software Design Document
1.4 Overview
The remaining chapters and their contents are listed belowSection 2 is the Architectural Design that specifies the design entities that collaborateto perform all the functions included in the system. Each of these entities has an Abstractdescription concerning the services that it provides to the rest of the system. In turn, eachdesign entity is expanded into a set of lower-level design operations that collaborate toperform its services.Section 3 concerns the Data Structure Design.Section 4 concerns with use case diagram.Section 5 contains the Use Case Realizations. Each Use Case stated in the SRSSection 6 contains activity diagrams.Section 7 discusses the User Interface Design.
Section 2
2. Architectural Design
Client Server Model
2.Manager Model
2.1 class diagram
Section 3
3.Data structure design
The data is stored in a relational database using Wampserver(MySql). The relations aredescribed by the database administrator . The fields for transmitting to andfrom the database are given in the following table.
3.1Data field types and sizes
ATTRIBUTE NAME ATTRIBUTE TYPE SIZE
Customer_id varchar 20
password varchar 10
Admin_id varchar 20
Password varchar 10
Customer_name varchar 20
Age integer 2
Gender char 1
Email varchar 30
Source string 20
Destination string 20
B_no/F_no/t_no varchar 10
Ticket_no integer 5
Ticket_name varchar 20
Date date -
Time date -
Seat_no integer 2
Bus/train/flight name Varchar 20
Passenger_name varchar 20
Passenger_Age integer 3
Section 4
4. Use Case Diagram
Section 55. Use Case Realizations
1.Login
2.New account
3.Change password
4.Ticket cancellation
5. Add new bus/train/flight
6.Ticket booking
COLLABORATION DIAGRAM
1.Add new b/t/f details
2. booking tickets
3. ticket cancellation
Section 6
6. Activity Diagram
Section 7
7. Interface Design
Login Page
New Account
Select Comfortable Journey
Search Bus
Book Ticket
Search Flight
Admin Page
Add Bus
top related