Online Airline Ticket Reservation Complete

ITB3105.
CASE TOOLS LAB
Record of Laboratory/ Practical Course Work
ITB3105 CASE Tools Lab
NAME : MISHAL FATHIMA S.H

REG. NO. : 160081601023
SEMESTER :V
BRANCH : INFORMATION TECHNOLOGY
NOV 2018
S.H. Mishal Fathima 160081601023

ITB3105. CASE TOOLS LAB
BONAFIDE CERTIFICATE
Certified that this is the bonafide record work done by MISHAL
FATHIMA S.H RRN.160081601023 of V Semester, B. Tech. -
Information Technology programme in the course of ITB3105 CASE
Tools Lab during the year 2018 – 19.
Course Teacher Head of the Department

[Dr. N. Prakash]
Submitted for the practical examination held on ______________________
Internal Examiner

Record of Laboratory / Practical Course Work
Name of the Student : Mishal Fathima s.h Programme : B.Tech., - IT

RRN No. : 160081601023
Code No. & Name : ITB3105 CASE Tools Lab
Academic Year : 2018 – 19 Semester :V
Total
Ex. Page Signature
Date Title of the Experiment Marks (Staff
No. No. Incharge)
(10)
1 / / Problem Statement
2 / / Use Case Diagram
Software Requirements
3 / /
Specification
4 / / Software Project Plan
5 Software Design
5.1 / / Activity Diagram
5.2 / / Class Diagram
5.3 / / Sequence Diagram
5.4 / / Collaboration Diagram
5.5 / / Statechart Diagram
5.6 / / Component Diagram
5.7 / / Deployment Diagram
6 / / Prototype
7 / / Test Case Specification
8 / / Implementation
9 / / Testing and Test Report
10 / / User Manual
Observation (50) Internal Signature of the

Record (10)
Ex1 Ex2 Mark (60) Course Teacher

Total
Ex. Page Signature
Date Title of the Experiment Marks (Staff
No. No. Incharge)
(10)
1 / / Problem Statement
2 / / Use Case Diagram
Software Requirements
3 / /
Specification
4 / / Software Project Plan
5 Software Design
5.1 / / Activity Diagram
5.2 / / Class Diagram
5.3 / / Sequence Diagram
5.4 / / Collaboration Diagram
5.5 / / Statechart Diagram
5.6 / / Component Diagram
5.7 / / Deployment Diagram
6 / / Prototype
7 / / Test Case Specification
8 / / Implementation
9 / / Testing and Test Report
10 / / User Manual
Observation (50) Internal Signature of the

Record (10)
Ex1 Ex2 Mark (60) Course Teacher

1. PROBLEM STATEMENT
BMV company have come up with the Airline reservation software with new
features which help the customers to book the ticket for Airlines easily . The
customer have been provided with there own account and a login ID and
password to manage their account. Customer can check for the flight and the
seats availability according to the cost and time. It is also and user friendly
software which is easy to handle by the customer. This software will be released
on May 2019 and the customer can start the bookings. Clients have to sign up a
new account with their Gmail or any other account for security reasons. The ticket
will be reserved and will be sent directly to their corresponding mail account for
a safer copy. Contact and help icon show also available for any enquiry therefore
it will be on of the comfortable software to all types of users to make people more
easier the registration form is available for no cost although there is a change in
classes almost the comfort details are also given for each classes they select their
own extra decide facilities also in their way of travel like food and other
Electronic usages with specific charges for emergency needs the facilities that are
provided in our Airways also listed in the software for safety measures. the user
can also cancel the ticket at any moment within the 24 hours of booking otherwise
the money will not be refunded. the Transaction ID and bank details given by the
user for payment will be in a secured form so the so that the user have not worried
about the they personal details provided for payment. Admin can update the
airline details instantly by their login ID and password .admin can also generate
a report on the daily basis to know the improvement of the software. the software
will be updated for every 6 months according to the daily needs of the users.



2. USE CASE DIAGRAM

Software Project Plan

1. INTRODUCTION:
The goal of this software is to provide online reservation of airlines

ticket . we're multiple flight companies inside one software . It allows the
users to view availability of each flight transporters in that City along with
the place,rate, timings and then reserve the tickets.
1.1 Project Scope:
The software developed here lists the names of all the airline
transporters in that particular city for the next 6 days and also
displays the seat availability thus enabling online reservation.
Inputs:
1. Starting place and destination place for booking the

ticket.
2. User valid details to create account in the system
3. Username and password to enter into the system and
to book and modify the details in the system.
Outputs:
1. Printable acknowledgement form that is acceptable in the

airport as tickets.
2. Error messages if the function to be performed fails and
suitable retry options.
1.2 Major Software Functions:
Modularizing the software into different major functions to

be performed plays a vital role in the project development.

i) Search for availability of transportation services

to book tickets by date and place.
ii) Modification of the starting place with
destination place and date.
iii) Reservation of tickets.
1.3 Performance/ behavior issues:
The required input files must be present. The details entered

by the user must be within a valid range. Also, once a ticket is
booked, it can be cancelled.
1.4 Management and Technical Constraints:
The software must be flexible enough to implement any changes.

Since the automation of online airlines ticket reservation is planned
in another 3 months, the system must be developed in two and a
half months by adopting optimum number if people for the
successful completion of the project on time. The software should
be portable and not accessible to authorized people. It should not
occupy more than 1 GB space.
2. PROJECT ESTIMATES:
Historical data used for estimates:
Not Applicable.
Estimation Techniques Applied and Results:
Estimation Techniques:
Technique 1: (Function Point Analysis)
Function oriented software metrics measure the

functionality delivered by the application as a normalization
value. Function oriented metrics were first proposed by
Alberchet, who suggested a measure called function point.
Function points are derived by using an empirical
formula relationship based on countable measure of
software’s information domain assessment of software
complexity.
FORMULA:

Function Point=Count total [0.65 + 0.01 Fi]
Technique 2: (COCOMO Model)
The Constructive Cost Model provides detailed

formulae for determining the overall development time
schedule and the developmental effort. Since the system
under consideration mainly deals with processing data it is
considered to be an organic system.
Effort=2.4*(KDLOC^1.05) for organic system.
Where KDLOC= Thousands of delivered lines of code.
The developmental schedule, M=2.5 *(Effort ^0.38)
Technique 3:
The cost of developing the software is given as,
Cost= ((Number of person)*(Number of months)*(Pay for each

person per month))
Estimation Techniques:
Technique 1: (Function Point Analysis)
Fi General System description Value

Characteristics
F1 Data Communication Application 0
is pure batch
processing or
astandalone
PC
F2 Distributed Data Processing Application 1
prepare data
for end user
processing
on another
component
of the system

F3 Performance No special 0
performance
requirements
was stated by
the user.
F4 Heavily Used Configuration No explicit 0
or implicit
operational
restrictions
are included
F5 Transaction Rate Weekly pick 2
transaction
period is
anticipated
F6 Online Data Entry 1 % to 7 1
percentage of
transactions
or interactive
data entry
F7 End User Efficiency Four to five 2
of the above
F8 Online Update None 0
F9 Complex Processing None of the 0
above
F10 Reusability Less than 10 1
% of the
application
considered
more than
one users
needs
F11 Installation Ease No special 0
consider
rating was
stated by the
user and no
special setup
is required
for
installation
F12 Operational Ease No special 0
operational
conditions

F13 Multiple Sites Need for 0

multiple sites
were
considered in
the design
and the
application is
designed to
operate only
under the
identical
hardware and
software
environments
F14 Facilitate Change Any one of 1
the above
Thus, Fi amounts to 8.
Count total:
Types Of Complexity of Value
Components Components
External Inputs 3*3 9
External Outputs 2*4 8
External Inquiries 0*3 0
External Logical 1*7 7
Files
External Interface 0*5 0
Files
24
Total
Function
Point=24*[0.65+0.01*8]
=18
Lines of code= Function point*constant

=18*53
=954 lines.
KDLOC= 0.954
Technique 2: (COCOMO)

Effort= 2.4 *(0.954^1.05)

= 2 person-months.
Months= 2.5*(2^0.38)
= 3 months.
Technique 3:
Cost= 2*3*10000
= Rs. 60000/-
Reconciled Estimate:
The final estimate for the development of the project after finding
out the effort, time and cost needed is
Effort= 2 person-months.
Time= 3 months.
Cost= 60000/- rupees.
Project Resources:
a) People:
i) Programmers: Deliver technical skills by writing the necessary

programs to ensure.
ii) Testers: Tests the software so that it performs its functions correctly
without errors.
b) Hardware:
40 GB Hard Disk, 128 MB RAM.
c) Software:
Windows 98 or any higher version.
d) Tools:
Rational Rose.
3. RISK MANAGEMENT:
3.1 Project Risks:

a) Project Complexity: Lack of identifying modules and functions in

detail.
b) Support Risks: The degree of uncertainty that the resultant software

will be easy to correct, adapt and enhance.
c) Schedule Risks: The degree of uncertainty that the project schedule will
be maintained and the product will be delivered on time.
d) Involvement: Lack of customer’s full involvement in the definition of

requirements and their commitment to the project.
3.2 Risk Table:
Name of Risks Probability Impact

Project Complexity 30 2
Support Risks 20 3
Schedule Risks 10 4
Involvement 10 4
3.3 Overview of Risk Mitigation, Monitoring and Management (RMMM):
The RMMM plan documents all the work performed as a part

of risk analysis and is used by the project manager as part of the overall
project plan. Risk mitigation is a problem avoidance activity and risk
monitoring attempts to allocate the origin of risks.
In case of risk monitoring, the project manager monitors factors that
may provide an indication of whether the risk is becoming more or less
likely. In addition, the project manager should also monitor the
effectiveness of risk mitigation steps.
Risk management assumes that the mitigation efforts have failed and
that the risk has become a reality. RMMM steps incur additional costs.
4 PROJECT SCHEDULE:
4.1 Project Task Set:
The major tasks include
a) Project Scoping
b) Project Planning
c) Risk Analysis
d) Implementation
e) Customer Reaction.

4.2 Functional Decomposition:
The major tasks are refined or decomposed to form the sub-tasks. They
include:
a) Project Scoping:
i) Identify needs and project constraints

ii) State Problem Domain
b) Project Planning:
i) Performance and behavior issues

ii) Software Functions
C.) Implementation
Release the software after implementation of the individual modules
and their integration
D)Customer Evaluation:
iii) Evaluation by customers

iv) Feedback from them.
4.3 Task Network:

Project Risk Implement

Scoping Analysis module1
Integrate
Project Behavior Impleme Implement
Planning Issues ntation module2
Cost Implement
Estimation module3 Customer
Reaction
4.4 Time line Chart:
Work Tasks Month 1 Month 2 Month 3

1. Project Scoping
a) Identify needs
and constraints
b) Problem
Definition
2. Project Planning
a) Risk Analysis
b) Software
features
c) Cost Estimation
3. Implementation
Module 1
Module 2
Module 3
4. Customer
Reaction.
5. STAFF ORGANISATION:
5.1 Team Structure:
Not Applicable.
5.2 Management Reporting and Communication:
Not Applicable.
6. TRACKING AND CONTROL MECHANISM:
6.1 Quality Assurance and Control:
Quality assurance is an essential activity that is a planned sequence

of actions required to ensure high quality software. Quality can be assured
by:
i. Ensuring conformance to requirements.

ii. Tight change management.

iii. Close contact with clients.
6.2 Change Management Control:
Only authorized persons must have the right to access and modify a
particular object.
3. SOFTWARE RECQUIREMENT SPECIFICATION:
A. USE CASE SPECIFICATION:<LOGIN>

1.USE CASE NAME:LOGIN
1.1.DESCRIPTION:This feature is used to enable the user to login into airline

reservation system.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.The user will enter the username and password.
2.If the entered details are correct then the user is allowed to access the
software.
3.Then user is allowed to create account for reservations.
2.2.ALTERNATIVE FLOW:
1.If login fails suitable retry options are available
2.And an error message is displayed stating'invalid username or password'.
2.3.SPECIFICRECQUIREMENTS:(NON-FUNCTIONAL
RECQUIREMENTS)
The username and password should be at length of atleast 8 characters.The
password should contain special characters numbers and alphabets.
2.4.PRE CONDITION:
The user should login only using theii ID and password.
2.5.POST CONDITION:
Now the software validates the entered username and password.If incorrect
it will show a error message as incorrect.
2.6.EXTENSION POINT:
Not applicable.
B.USE CASE SPECIFICATION:<CREATE ACCOUNT>
1.USE CASE NAME:CREATE ACCOUNT

1.1.DESCRIPTION:passengers can give their personnel details in this page.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.The passenger can fill up a form to provide there details.
2.The passenger should provide infromation which are compulsory in the
form.
3.Personel account is created with the corresponding details.
4.Then user is taken to check the availability of flights.
1.If any compulsory infromation are not filled a pop message will appear
on the screen.
2.The user should fill up the left area.
3.And now an account is created with the provided details and takes to next
page.
2.3.SPECIFIC RECQUIREMENTS:
Not applicable
2.4.PRE CONDITION:
The provided details should be true and valid.
2.5.POST CONDITION:
The submitted details will be saved and a success message is displayed in a
popup dialogue box.
once the personel account is created it goes to check the flights and other
facilities .
C.USE CASE SPECIFICATION:<CHECK FLIGHT SEATS>
1.USE CASE NAME:CHECK FLIGHT SEATS
1.1.DESCRIPTION:Flight seats and cost of flights are available in this page.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.The passenger can give the date and check with the flight seats available.
2.the passenger can also check with their respective classes.
3.the passenger can check the cost of flight seats.
4.they can check with their needed extra facilities.
5.Then user can confirm their booking in the next page.

1.An error message is displayed if there is no flight in the provided date.
2.And shows other options available.
2.3.SPECIFIC RECQUIREMENTS:(NON-FUNCTIONAL
RECQUIRMENTS)
Provide a valid date.
2.4.PRE CONDITION:
The flight detail for which the availability is viewed has to be already
prescent in the database.
2.5.POST CONDITION:
if any option is unsuccessfull then suitable retry options are available.
After choosing the suitable flights they can confirm their booking in next
page.
D. USE CASE SPECIFICATION:<BOOK TICKETS>
1.USE CASE NAME:BOOK TICKETS
1.1.DESCRIPTION:This feature is to confirm reservation of tickets.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.the passenger can enter the start and destination place.
2.the passenger can also provide the date and time of flight.
3.the passenger can also select the number of respective seats wanted.
3.Now the availability is checked and booking can be confirmed.
4.if user have any inconveniences they can cancel their ticket in next page.
1.If booking fails suitable retry options are available.
2.And an error message is displayed stating'booking is not confirmed'.
2.3.SPECIFIC RECQUIREMENTS:(UI RECQUIREMENTS)
The input details should be valid.
2.4.PRE CONDITION:
review of the booking ticket is shown to the passenger before booking is
confirmed and then the ticket is booked.
2.5.POST CONDITION:
An error message is displayed if the ticket is not booked.
Booking is confirmed and proceed to make payment.
E. USE CASE SPECIFICATION:<MAKE PAYMENT>

1.USE CASE NAME:MAKE PAYMENT
1.1.DESCRIPTION:This feature is used to make payment for airline

reservation.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.Many payment methods are shown to the passenger to make there
payment.
2.Passenger should give the bank details for the respective payment method.
3.An OTP pin is send through the phone number or Email id to confirm the
payment.
4.And the payment is validated with the bank.
4.The payment is made after the verification and validation.
1.If verification or validation fails suitable retry options are available.
2.And an error message is displayed stating'Payment cancelled'.
Provided payment details should be valid.
2.4.PRE CONDITION:
Payment should be make with correct details.A messsge is sent to the email
after payment is done and a report is generated.
2.5.POST CONDITION:
Now the software validates the entered details to make payment.If incorrect
it will show a error message as incorrect.
Not applicable.
F. USE CASE SPECIFICATION:<CANCELLATION OF TICKET>

1.USE CASE NAME:CANCELLATION OF TICKET
1.1.DESCRIPTION:This feature is used for cancellation of ticket.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.The booking is cancelled by the passenger .
2.The corresponding reason for cancellation is asked to the passenger.
3.And the reason of cancellation is send to the admin.
1.The cancellation is confirmed.
2.the feedback is also fetched from the passenger.

3.The money is refunded to the passenger.

The ticket details for cancellation should be given correctly.
2.4.PRE CONDITION:
The passenger should enter a valid feedback to cancel the ticket.
2.5.POST CONDITION:
Now the software validates the entered details and feedback.And the ticket
is cancelled.
Not applicable.
G. USE CASE SPECIFICATION:<GENERATE REPORT>

1.USE CASE NAME:GENERATE REPORT
1.1.DESCRIPTION:This usecase is used for process of generating report.
2.FLOW OF EVENTS:
2.1.BASIC FLOW:
1.Name of the flight,date and time has to be entered by the employee.
2.The report is generated and displayed.
1.If task fails suitable retry options are available.
2.And an error message is displayed stating'report generation failed'.
2.3.SPECIFIC RECQUIREMENTS:
The input details should be valid.
2.4.PRE CONDITION:
The available number of seats and booking details after reservation has to
be updated in the database for the flight.
2.5.POST CONDITION:
Now the software validates if successful,generated report is displayed.Error
message and suitable retry options are provided if generation of report fails.
Not applicable.
5. SOFTWARE DESIGN
5.1 ACTIVITY DIAGRAM
1.REGISTER AND LOGIN ACTIVITY

2.FLIGHT RESERVATION AND CANCELLATION ACTIVITY


4.GENERATE REPORT ACTIVITY

5.2.CLASS DIAGRAM

Fig 5.2.1 Class diagram for Airlines Reservation

5.3 SEQUENCE DIAGRAM
5.3.1 Sequence Diagram for User Registeration
Fig.5.3.2 Sequence Diagram for Member Login

Fig.5.3.3 Sequence Diagram for booking flight .

Fig.5.3.4 Sequence Diagram for Flight Cancellation

Fig.5.3.5 Sequence Diagram for updation and generating report.

5.4 Collaboration Diagrams
Fig.5.4.1 Collaboration Diagram for User Registration
Fig.5.4.2 Collaboration Diagram for Member Login

Fig.5.4.3 Collaboration Diagram for booking of flight
Fig.5.4.4 Collaboration Diagram for Flight Cancellation

Fig.5.4.5 Collaboration Diagram for generating report

5.5. STATE CHART DIAGRAM
State transition diagram for Airlines Reservation System.

5.6 COMPONENT DIAGRAM
Fig; Component diagram for Airlines Reservation System.
8. 5.7 DEPLOYMENT DIAGRAM :
Deployment diagram for Airlines Reservation System

6.TEST CASE SPECIFICATION
TES TEST CASE TEST CASE TEST EXPECT ACTUA PAS

T DESCRIPTION INPUT PROCEDU ED L S
CAS RE OUTPUT OUTPU OR
E ID T FAI
L
1 LOGIN:Test for an USERNAME: MANUAL System System Pass
invalid username or abc LY shows shows
password PASSWORD: message message
××× as invalid .
username
or
password
2 LOGIN:Test for an USERNAME: MANUAL Login Login is Pass
valid username or abc LY successful successf
password . PASSWORD: and ul and
××× shows reservati
reservatio on page
n page appears
3 LOGIN:Test for the Click "forget MANUAL Page to Reset Pass
user forgot the password" LY create passwor
password. new d screen
password appears
4 LOGIN:Test for user Click "forget MANUAL Page to Userna Purs
forgets the username username" LY know me is e
your shown
username to the
custome
r by
providin
g their
email ID
5 USER NAME:abc MANUAL Thesyste Shows Pass
REGISTRATION:Te AGE:a1 LY m message
st for Wrong format PLACE:INDI prompts a s wrong
entered in the input A message format
fields of the to the Hindi
registration page user input
saying
that he
has
entered a
wrong
format in

the input
fields.
6 USER NAME:abc MANUAL The System Pass
REGISTRATION:Te AGE:a1 LY system shows
st if Passwords and PLACE:INDI generates the
Confirm Password A a message message
fields do not match in CONFIRM to the
the registration page PASSWORD: user
××× saying
“please
enter the
confirm
password
field”
again.
7. USER NAME:abc MANUAL The The Pass
REGISTRATION:Da AGE:27 LY . system system
ta Fields left out PLACE:INDI prompts a shows
empty in the A message the
registration page. DOB: to the message
user
asking
him to fill
the empty
fields he
has left
out.
8 USER NAME:abc MANUAL The
REGISTRATION:Co AGE:27 LY system
rrect data entered into PLACE:INDI accepts
the fields in the A the details
register page of the
customer
and then
logs him
onto the
system
and
displays
the page
where he
can
search
and book
for
flights.
9. BOOK FLIGHTS:12 MANUAL The
FLIGHTS:Wrong FLIGHT LY system
format of information NO:1× generates
entered into the data an error

fields of the flight START message

booking page PLACE: to the
Chennai user
DESTINATIO indicating
N that the
PLACE:mum wrong
bai format of
data is
entered
and to re-
enter the
data.
10 BOOK FLIGHTS:12 MANUAL The
FLIGHTS:Correct FLIGHT LY system
format of data is NO:1A allows the
entered into the data Start place users to
fields in the flight :Chennai book the
booking page. Destination flight by
place :mumbai providing
details
required
and
directs
them to
the
booking
confirmat
ion page.
11 TICKET PNR MANUAL The
CANCELLATION: NO:01×× LY system
Wrong format of TICKET generates
information entered NO:123 an error
into the data fields of message
the flight cancellation to the
page user
indicating
that the
wrong
format of
data is
entered
and to re-
enter the
data
12 TICKET PNR MANUAL The
CANCELLATION:C NO:01×× LY system
orrect format of data TICKET allows the
is entered into the NO:123 users to
data fields in the cancel the
flight and

flight cancellation shows a

page message
as ticket
cancelled.
13. GENERATE USER MANUAL System
REPORT :An invalid NAME:a LY shows
username or PASSWORD: message
password is entered ×× invalid
by the admin to get username
into system . or
password
14. GENERATE USER MANUAL Login
REPORT :An valid NAME:A LY successful
username or PASSWORD: and
password is entered ×× shows the
by the admin to get history of
into system ticket
reserved.
15. GENERATE "Specified MANUAL The
REPORT:Admin data" LY report is
selects particular data generated
to generate report and
printed

Online Airline Ticket Reservation Complete

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Airline Ticket Reservation Complete

Uploaded by

Copyright:

Available Formats

ITB3105.

CASE TOOLS LAB

Record of Laboratory/ Practical Course Work

ITB3105 CASE Tools Lab

NAME : MISHAL FATHIMA S.H

S.H. Mishal Fathima 160081601023

Certified that this is the bonafide record work done by MISHAL

FATHIMA S.H RRN.160081601023 of V Semester, B. Tech. -

Information Technology programme in the course of ITB3105 CASE

Tools Lab during the year 2018 – 19.

Course Teacher Head of the Department

Submitted for the practical examination held on ______________________

S.H. Mishal Fathima 160081601023

Record of Laboratory / Practical Course Work

Name of the Student : Mishal Fathima s.h Programme : B.Tech., - IT

2 / / Use Case Diagram

4 / / Software Project Plan

5.1 / / Activity Diagram

5.2 / / Class Diagram

5.3 / / Sequence Diagram

5.4 / / Collaboration Diagram

5.5 / / Statechart Diagram

5.6 / / Component Diagram

5.7 / / Deployment Diagram

7 / / Test Case Specification

9 / / Testing and Test Report

Observation (50) Internal Signature of the

S.H. Mishal Fathima 160081601023

2 / / Use Case Diagram

4 / / Software Project Plan

5.1 / / Activity Diagram

5.2 / / Class Diagram

5.3 / / Sequence Diagram

5.4 / / Collaboration Diagram

5.5 / / Statechart Diagram

5.6 / / Component Diagram

5.7 / / Deployment Diagram

7 / / Test Case Specification

9 / / Testing and Test Report

Observation (50) Internal Signature of the

S.H. Mishal Fathima 160081601023

S.H. Mishal Fathima 160081601023

S.H. Mishal Fathima 160081601023

S.H. Mishal Fathima 160081601023

2. USE CASE DIAGRAM

S.H. Mishal Fathima 160081601023

Software Project Plan

The goal of this software is to provide online reservation of airlines

1.1 Project Scope:

1. Starting place and destination place for booking the

1. Printable acknowledgement form that is acceptable in the

1.2 Major Software Functions:

Modularizing the software into different major functions to

S.H. Mishal Fathima 160081601023

i) Search for availability of transportation services

1.3 Performance/ behavior issues:

The required input files must be present. The details entered

1.4 Management and Technical Constraints:

The software must be flexible enough to implement any changes.

Historical data used for estimates:

Estimation Techniques Applied and Results:

Technique 1: (Function Point Analysis)

Function oriented software metrics measure the

S.H. Mishal Fathima 160081601023

Cost= ((Number of person)(Number of months)(Pay for each