arun mini project

30
index & Tables 1)Introduction:……………………………………………………………………3 1.1)Purpose:…………………………………………………………………………...3 1.2)Scope:……………………………………………………………………………..4 1.3)Abbreviations:…………………………………………………………………….5 1.4)References:……………………………………………………………………......7 1.5)Technologies:……………………………………………………………………...7 2)Overall Description:…………..……………………………………………….8 2.01)Product Perspective……………………………………………………………...8 2.02)Software Interface…………...…………………………………………………..9 2.03)Hardware Interface:……………………………………………………………..10 2.04)Communication Interface……………………………………………………….11 2.05)Product Function:………………………………………………….…………....12 2.06)User Characterics:……..……………………………………………………......13 2.07)Constraints:……………………………………………………………………..14 2.08)LifeCycle Model:………………………………………………………………15 2.08)Use-Case Model Survey:……………………………………………………16,17 2.09)Architecture diagram:………………………………………………………......18 2.10)Database design: ……………………………………………………………….19 2.11)Assumptions and Dependencies:………………………………………………20 3)Specific Requirements:…….…………………………………………………….21

Upload: anuj-singh

Post on 21-Apr-2015

117 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Arun Mini Project

index & Tables

1)Introduction:……………………………………………………………………3

1.1)Purpose:…………………………………………………………………………...3

1.2)Scope:……………………………………………………………………………..4

1.3)Abbreviations:…………………………………………………………………….5

1.4)References:……………………………………………………………………......7

1.5)Technologies:……………………………………………………………………...7

2)Overall Description:…………..……………………………………………….8

2.01)Product Perspective……………………………………………………………...8

2.02)Software Interface…………...…………………………………………………..9

2.03)Hardware Interface:……………………………………………………………..10

2.04)Communication Interface……………………………………………………….11

2.05)Product Function:………………………………………………….…………....12

2.06)User Characterics:……..……………………………………………………......13

2.07)Constraints:……………………………………………………………………..14

2.08)LifeCycle Model:………………………………………………………………15

2.08)Use-Case Model Survey:……………………………………………………16,17

2.09)Architecture diagram:………………………………………………………......18

2.10)Database design: ……………………………………………………………….19

2.11)Assumptions and Dependencies:………………………………………………20

3)Specific Requirements:…….…………………………………………………….21

3.1)Use-CaseReports: ……………………………………………………………22-24

Page 2: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

INTRODUCTION

1.1)PURPOSE

Computers have been used for commercial purposes for the past fifty years. In present time, all manual works are go with different management , different projects work for making processes secure and easy.

Here our project is for AIRPORTS and AIRLINES which is serving people by providing them the travelling facility from one destination to another destination. Also it has certain enlisted services to help customers and satisfy them fully. It is systematic and secure transaction projects which any institute can deal easily with their customers and can store their details in their database.

There are many facilities provided for searching and security as login name and password given in it. Only some sophisticated users can access database and the software.

The airport website is the place to look for specific information about making airline reservations, schedules of the flights including cancellations and their fares. It is always better to book the ticket directly online or by phone rather than to rely on the travel agent but we will provide reservations with the help of the desk. The traveller can easily reserve seats online, negotiate airfares or even find a cheaper fare. It helps to find the best deals.

2

Page 3: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

1.2)SCOPE

The main objective of our project “Airport Management System” is to manage all the activities of airport. It includes reservation facility to customers, flight schedule and staff details. This can be used to view flight arrival and departure times, employees’ details pertaining to leave, salary or shift and for reservation to all kind of flights. Its working environment is airline office, which deals with customers in the field of reservation, so it serves the public utility facilities.

Proper maintenance of records of each customer and their details of reservation.

Proper maintenance of records of every employee pertaining to leave, shifts and salary.

Generation of reports as and when required by the management for their use.

Maintenance of flight schedules, their arrival and departure times.

Keeping track of status of each customer.

Managing take off and runway terminals.

Cost and time effective systems.

Ease in adding new item or details.

Automation of whole sole manual work.

Activities like insertion of a new record, updating, editing will be done by system administrator of the issues will be maintained in the form of logs for auditing and maintaining the integrity of the system.

3

Page 4: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

1.3)ABBREVIATONS

SRS: Software Requirements Specification - specifies customer and detailed requirements.

SOL SERVER: Structured Query Language is a database computer language designed for managing data in relational database management systems (RDBMS), and originally based upon relational algebra. SQL Server is a relational model database server produced by Microsoft.

IEEE: The Institue Of Electrical and Electronics Engineering, Inc

ASP: Active Server Pages

SMS: Staff Management System

OS: Operating Systems

Categories: Categories are a subdivision of the forum and have a specific theme , they consist out of 1 or more subcategories (about a sub theme of the main category) or consist out of threads all talking about the category theme.

Thread: A topic and all its replies , located in a category.

Topic: A topic is the first post in a thread.

Reply: An answer on a topic/reply.

Post: A post can be a topic or a reply on a topic/reply. A post can be

submitted in more than one category.

Registered User: A forum user that is registered and logged in to the forum.

Also called an ``Author''.

4

Page 5: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

LAN: A local area network (LAN) is a computer network that connects

computers and devices in a limited geographical area such as home, school, computer laboratory, office building, closely positioned group of buildings, or an airport.

Protocol: A protocol is a set of guidelines or rules. The information exchanged

between devices on a network or other communications medium is governed by rules that can be set out in a technical specification called a communication protocol standard. The nature of the communication, the actual data exchanged and any state-dependent behaviors are defined by the specification. This approach is often taken for protocols in use by telecommunications.

PNR:In the travel industry, a Passenger Name Record (PNR) is a record in the

database of a Computer Reservation System (CRS) that contains the itinerary for a passenger, or a group of passengers traveling together. The concept of a PNR was first introduced by airlines that needed to exchange reservation information in case passengers required flights of multiple airlines to reach their destination

5

Page 6: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

1.4)REFERNCES

IEEE SRS format google.com wikipeidia.com software engineering pressmen Approach to Object-oriented by James ram bough

1.5)TECHNOLOGIES

IIS: Web Server

SQL Server: Database

Visual C#: developing .NET applications

ASP.NET: developing dynamic websites

HTML: designing web pages

6

Page 7: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

OVERALL DESCRIPTION

Describe the general factors that affect the product and its requirement.

2.1)PRODUCT PERSPECTIVE

The web pages (Html/asp.net) are presented to provide the user interface of

staff client side. The communication between customer and server is provided

through HTTP/HTTPS protocols.

On the server side, web server IIS is used and database SQL server 2.0 is used for storing information

7

Page 8: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

The software will rely on a database and web server that can remotely be accessed from any web browser. There are 4 main types of user on the project:

the guests the registered users (which could be divided into several groups) the moderators the admins.

Users can search by keywords and username. They can join keywords with AND, OR to help define the search. It will also be possible to limit the search to certain categories or imposing a date limit. The search result will be ordered on date , ranking or username. Everyone can access the forum , view posts and search. Guests can register in order to become registered user if they want to submit posts. Registered users can also logout , login , edit their own posts , request their password , mail another user , upload a file , rank a post , edit their personal data , request public user data , request e-mail notification and set-up dialy/weekly/monthly digest for certain categories. Moderators can edit , delete , move and close threads ; move posts ; create user accounts (no confirmation needed) ; ban and unban user accounts ; change the usertype or group of a registered forum member. (moderators can't make admins) The highest user level is the admin , beside the rights of the moderator , he can make/edit/delete/close categories and make/restrict/delete usertypes.

8

Page 9: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.2)SOFTWARE INTERFACE

Client on internet: web browser, operating system (if any)

Web server: IIS, operating system (any)

Database server: SQL server, operating system (any)

Development End: visual C#, asp.net, html, JavaScript, sql server, IIS

2.3)HARDWARE INTERFACE

Client side:

Web browser: Internet explorer 6.0 and above

Processor: Pentium2 at 500 MHz

RAM: 64 MB

Disk space: 1 GB

Server side:

Web server: IIS 5.0

Processor: Pentium 3 at 1 GHz

RAM: 512 MB

Disk Space: 1 GB

Database: SQL Server2000

2.3)COMMUNICATION INTERFACE

Client on internet will be using HTTP/HTTPS protocol. The “guest”, “registered user” and “moderators” side of the board will be

accessible from any operating system with a web browser and a network connection to the server running the project.

No special hardware is required for the end-user. The communication between the forum users and the project will be using a

normal HTTP v1.0 or v1.1 communication (TCP/IP port80). The project will work with several separated modules that will communicate

with each other with a specific protocol/format.

9

Page 10: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.5)PRODUCT FUNCTION

Flight Reservation:This module is divided into two, Domestic flights and

International flights. User has to select the desired one, sign in and fill the form for reservation in the desired flight. For the help of the customer, flight fares are shown along with the availability of seats. When the seats are allotted to the customer, PNR number is issued.

Cancellation: Customer can cancel the reservation which he had done

before.For cancellation he has to fill the form by mentioning its PNR Number.

Flight Schedule: This module contains the detail of flights i.e. the flight

number, timings, flight source and destination point.With the help of this schedule, customer can go for reservation as per the requirements.

Staff: This module of our project deals with every details of our employee

pertaining to salary, their leaves and their shifts of working. This module provides us information about the people working on airport. You can easily add a new entry and delete the existing entry along with updating if needed. This module is only for staffers and administrator as only administrator and staff members are concerned with the details of the staff.

Customer Space: This module shows the customer detail which contains the

customer information, reservations done by that customer in past and also it shows the future scheduled flight for the customer.

Contact: The most important module we have is the contact. Here we will provide all the contact numbers and addresses of airline partners and the booking agents.

Feedback: We will also take feedback from the customers in order to improve and fulfil all the requirements of the customer.

10

Page 11: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.6)USER CHARACTERISTICS

Every user must be comfortable of working with computer. He must have to

possess basic knowledge of how to operate the computer. He should also be

comfortable with net browsing. He should understand the basic terms related

with the computer. He must have basic knowledge of English too.

2.7)CONSTRAINTS

GUI is only in English.

There is no facility for general public to view all the details of the staff.

This system is working for single server.

There is no availability of back up so availability will get affected.

Limited to HTTP/HTTPS.

No staff member, government official, administrator can have access

to the site without username and verified password.

11

Page 12: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.8)LIFECYCLE MODEL

A software life cycle model (also called process model) is a descriptive and diagrammatic representation of the software life cycle. A life cycle model represents all the activities required to make a software product transit through its life cycle phases. It also captures the order in which these activities are to be undertaken. In other words, a life cycle model maps the different activities performed on a software product from its inception to retirement. Different life cycle models may map the basic development activities to phases in different ways. Thus, no matter which life cycle model is followed, the basic activities are included in all life cycle models though the activities may be carried out in different orders in different life cycle models. During any life cycle phase, more than one activity may also be carried out. For example, the design phase might consist of the structured analysis activity followed by the structured design activity.

12

Page 13: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.9) USECASE MODEL SURVEY

A use case is a description of a system’s behaviour as it responds to a request

that originates from outside of that system. Use Case Model is a model that

describes a system’s functional requirements in terms of use cases. Consists of

all the actors of the system and all the various use cases by which the actor

interact with the system, thereby describing the total functional behavior of the

system.

Use-case diagram

USECASE DIAGRAM FOR RESERVATION

13

Page 14: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

USECASE DIAGRAM FOR STAFF

14

Page 15: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.10)SEQUENCE DIAGRAM

SEQUENCE DIAGRAM

Sequence Diagram for login

Sequence Diagram for user

15

Page 16: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

Sequence diagram for reservation

16

Page 17: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.11)ARCHITECTURE DIAGRAM

APPLICATION LAYER BUSINESS LAYER DATABASE LAYER

17

Page 18: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

2.12)DATABASE DESIGN

 An entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs.

ERD OF AIRLINE RESERVATON

18

Page 19: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

ERD OF STAFF

2.13)ASSUMPTIONS AND DEPENDENCIES

User wants the reservations to be made at the lowest cost. User is an authenticated one. Information entered by the user is correct and valid. Staff details are managed easily. The schedule and details of all airlines are provided accurately.

19

Page 20: Arun Mini Project

AIRPORT MANAGEMENT SYSTEM

3)SPECIFIC REQUIREMENTS

3.1)USECASE REPORTS

Administrator: Responsible for creating and managing profiles, managing

scdedule details, maintaining logs, generating reports, maintaining in-out

registers.

.

Maintain logs: Responsible for checking the logs of different system user for

auditing and maintaining the integrity of the system.

ii)Staff: Responsible for many functions like:

Maitaing flight records.

Maintain the logs having user details.

There are different functions in different departments.

These staff members are assigned to different departments.

It can be accounts department,luggage management,ticket counter, in flights,

maintaining shifts and payments methods.

Manage staff

iii)Users:

User makes reservation.

cancel reservation.

check his flight schedule

20

staff

Creates and add details of staff

Updates staff profile

Maintain visitors record

Page 21: Arun Mini Project

Enter login name, password details &check

User created successfully

AIRPORT MANAGEMENT SYSTEM

checks his past and the current flights

can also give feedback of the website services.

Creates a login account.

After logging in with the ID and Password, the user can make reservations for the desired flight and date.

Here the user can choose the flights, class of seats and other facilities. When the reservation is made, PNR is issued to the user on the tickets.

If the user wants to cancel his reservation made for his future flight, he

can use his PNR number to cancel the reservation made. Money will

be refunded to him.

Name of use case: create user login

Description: to create users (giving them names, passwords, assign

roles, task and permissions to them).

Precondition: none.

Normal flow of events:

New login name, passwords will be entered.

Save the details.

Duplicate login name

21

Page 22: Arun Mini Project

Ask for details of user

Store new data

Store add information user data base

Create profile of user

AIRPORT MANAGEMENT SYSTEM

Alternate flow of events:

A message appears for the duplicate login name.

The user has to enter the details again.

Post condition: a login id is generated with its details.

Name of use case: create and add details to user profile

Description: The registered user can create his user profile adding his details

such as name, address, contact etc

Preconditions: user is logged in.

Normal flow of events:

The details of the user is entered

Save the details.

Alternate flow of events: A message appears for the unfilled fields.

The admin has to enter the fields in correct format again.

22