The document outlines the software process model for an airline booking system, detailing user, system, functional, and non-functional requirements. It includes various diagrams such as use case, swim lane, class, and activity diagrams, along with functional point estimation and CRC diagrams to illustrate the interactions and responsibilities of different classes. Key features involve user registration, ticket booking, payment processing, and administrative management of tourist and booking information.

1. .
1

2. At a glance
 Software process model
 Why chosen?
 User requirements
 System requirements
 Functional requirements
 Non functional requirements
 Use Case Diagram
 Swim Lane Diagram
 Class Diagram
 Functional Point Estimation
 CRC Diagram
 Activity Diagram
 ERD
2

3. Software process model
3

4. Why chosen?
4

5. User requirements
5
Admin will login from login page.
Admin will see Tourist,Booking and
Payment Information.
User will can buy flight ticket
booking and Payment.
Admin will manage everythings.

6. System requirements
6
System Need an Admin
Admin Have to login first by Email
and Password
Admin able to see Tourist,Booking
and Payment Information.
User have to registration first.
User have to login by Email and
Password
User can Booking Ticket and
Payment

7. Functional requirements
 Checking Availability
 Booking
 Making Confirmation
 Confirm Ticket
 Payment
 Add Time schedule
7

8. Non functional requirements
 Security.
 Reliability
 Availability
 Performance
8

9. Use Case Diagram for Airline
9

10. Use Case Diagram for Customer/Torist
10

11. Swim Lane Diagram for Airline
11

12. Class Diagram
12

13. Functional Point Estimation
13
Transaction
function
Fields /Files FTRs DETs
Vehicle Fields- Id,name,coach
num,route.
File name - Admin
1 4
Report Fields-Id, st_time , Pr_name,
status, end_time
File name - Admin
1 5
Location Fields- id , name, time ,
counter_no .
File name – Admin,user
2 4
Product Fields- id , name, time,
counter_no.
File name – Admin,user
2 4

14. Functional Point Estimation contd.
14
Data
function
Fields RETs DETs
Admin Fields-
Id,name,pass,email,contact
1 5
User Fields-Id,name, contact,
email, adress,Pr_name
1 6

15. CRC Diagram
Class: Airline
Class type: Role
Class characteristics: Tangible, concurrent, persistent, guarded.
Responsibilities:
1.Log on .
2.Log off with admin menu.
3.View tourist/customer information.
4.View booking information.
5.View payment information.
6.Manage everything.
Collaborate:
Airline
15

16. CRC Diagram cont.
Class: Customer
Class type: Role
Class characteristics : Tangible, Concurrent, persistent, guarded.
Responsibilities:
1.View Flight and Payment.
2.Select and booking flight,seat.
3.Pay payment.
4.View booking information.
5.View payment information.
Collaborate:
Product
Vehicle
Report
16

17. CRC Diagram cont.
 .
17
Class: Flight
Class type: Structure
Class characteristics: Tangible, concurrent, persistent, guarded.
Responsibilities:
1.Tour/Ticket selection
2.Ticket booking
3.Payment
Collaborate:
Admin
Customer

18. Activity Diagram for Airline
18

19. Activity Diagram for Tourist
19

20. ERD
20