Professional Documents
Culture Documents
NOV 2018
BONAFIDE CERTIFICATE
Internal Examiner
Total
Ex. Page Signature
Date Title of the Experiment Marks (Staff
No. No. Incharge)
(10)
1 / / Problem Statement
Software Requirements
3 / /
Specification
5 Software Design
6 / / Prototype
8 / / Implementation
10 / / User Manual
Total
Ex. Page Signature
Date Title of the Experiment Marks (Staff
No. No. Incharge)
(10)
1 / / Problem Statement
Software Requirements
3 / /
Specification
5 Software Design
6 / / Prototype
8 / / Implementation
10 / / User Manual
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.
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:
Outputs:
Not Applicable.
Estimation Techniques:
FORMULA:
Technique 3:
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
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
KDLOC= 0.954
Technique 2: (COCOMO)
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:
b) Hardware:
c) Software:
Windows 98 or any higher version.
d) Tools:
Rational Rose.
3. RISK MANAGEMENT:
c) Schedule Risks: The degree of uncertainty that the project schedule will
be maintained and the product will be delivered on time.
4 PROJECT SCHEDULE:
a) Project Scoping
b) Project Planning
c) Risk Analysis
d) Implementation
e) Customer Reaction.
The major tasks are refined or decomposed to form the sub-tasks. They
include:
a) Project Scoping:
b) Project Planning:
C.) Implementation
Release the software after implementation of the individual modules
and their integration
D)Customer Evaluation:
Integrate
Project Behavior Impleme Implement
Planning Issues ntation module2
Cost Implement
Estimation module3 Customer
Reaction
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:
Not Applicable.
Not Applicable.
Only authorized persons must have the right to access and modify a
particular object.
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.
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.
2.2.ALTERNATIVE FLOW:
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.
2.6.EXTENSION POINT:
once the personel account is created it goes to check the flights and other
facilities .
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.
2.2.ALTERNATIVE FLOW:
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.
2.6.EXTENSION POINT:
After choosing the suitable flights they can confirm their booking in next
page.
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.
2.2.ALTERNATIVE FLOW:
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.
2.6.EXTENSION POINT:
Booking is confirmed and proceed to make payment.
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.
2.2.ALTERNATIVE FLOW:
1.If verification or validation fails suitable retry options are available.
2.And an error message is displayed stating'Payment cancelled'.
2.3.SPECIFIC RECQUIREMENTS:(UI RECQUIREMENTS)
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.
2.6.EXTENSION POINT:
Not applicable.
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.
2.2.ALTERNATIVE FLOW:
1.The cancellation is confirmed.
2.the feedback is also fetched from the passenger.
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.
2.2.ALTERNATIVE FLOW:
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.
2.6.EXTENSION POINT:
Not applicable.
5. SOFTWARE DESIGN
5.1 ACTIVITY DIAGRAM
5.2.CLASS DIAGRAM
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