SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q1. Select and write down the problem statement for a real time system of relevance.

AIRLINE RESERVATION

The existing airline reservation system lacks real-time capabilities, resulting in inefficiencies
and inconvenience for both airlines and passengers. The system fails to provide up-to-date
information on flight availability, schedules, and seat reservations, leading to frequent errors,
overbooking, and customer dissatisfaction. Furthermore, the lack of real-time
synchronization between various airline systems and online platforms makes it difficult for
customers to make informed decisions and for airlines to efficiently manage their operations.
The objective is to develop a real-time airline reservation system that ensures accurate and
timely information exchange between airlines, reservation agents, and customers. The system
should enable customers to view real-time flight availability, book and manage their
reservations instantly, and receive immediate confirmation. It should also provide airlines
with a centralized platform to update flight schedules, manage seat inventory, and handle
reservations in real-time.
Key challenges to address include:
 Real-time synchronization: Developing a robust and efficient system that
synchronizes information in real-time between the airline's internal systems,
reservation agents, and online platforms to ensure consistent and accurate data
across all channels.
 Scalability and Performance: Designing a system that can handle a high volume
of concurrent transactions and user requests without compromising performance.
It should be capable of processing and responding to requests quickly to minimize
delays and provide a seamless user experience.
 Inventory Management: Implementing an efficient inventory management system
that accurately tracks seat availability, handles overbooking scenarios, and ensures
that customers receive accurate and up-to-date information about seat availability at
all times.
 Security and Data Privacy: Implementing robust security measures to protect
sensitive customer information, including personal details and payment data, from
unauthorized access or breaches.
 User-Friendly Interface: Creating an intuitive and user-friendly interface for
customers and reservation agents that allows easy navigation, quick booking, and
seamless management of reservations, reducing the complexity associated with
the reservation process.

By addressing these challenges, the proposed real-time airline reservation system aims to
enhance customer satisfaction, streamline airline operations, improve efficiency, and
ultimately increase revenue for airlines.

1 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q2. Analyze the requirement for a system and develop Software Requirement
Specifications sheet(SRS) for suggested system.
Introduction:
The purpose of this document is to provide a detailed Software Requirement Specifications
(SRS) for an Airline Reservation System. The system will allow users to book and manage
flight reservations, check flight availability, and perform other related tasks. The SRS defines
the functional and non-functional requirements of the system.
Scope:
The Airline Reservation System will cover the following functionalities:
 User registration and authentication
 Flight search and availability
 Flight booking and ticketing
 Seat selection
 Payment processing
 Flight cancellation and rescheduling
 Booking management (view, modify, and cancel bookings)
 Notification and alert system (e.g., flight delays,
cancellations) Functional Requirements:
3.1 User Management:

 The system shall provide user registration and login functionality.

 The system shall authenticate users based on their credentials.
 The system shall allow users to update their profile information.
3.2 Flight Search and Availability:
 The system shall allow users to search for flights based on various criteria,
including date, time, source, and destination.
 The system shall provide real-time flight availability information.
 The system shall display a list of available flights with relevant details, such as
flight number, departure/arrival time, and ticket prices.
3.3 Flight Booking and Ticketing:
 The system shall enable users to select a flight and book tickets.
 The system shall allow users to choose their seat preferences (e.g., window, aisle).
 The system shall calculate the total fare based on the selected flights and the
number of passengers.
 The system shall generate electronic tickets for confirmed bookings.
3.4 Payment Processing:
 The system shall integrate with a secure payment gateway to process payments.
 The system shall support multiple payment methods (credit card, debit card,
online banking, etc.).

2 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

 The system shall provide a payment confirmation receipt to users upon

successful transaction.
3.5 Flight Cancellation and Rescheduling:

 The system shall allow users to cancel their booked flights.

 The system shall follow the airline's cancellation policy and process
refunds accordingly.
 The system shall enable users to request flight rescheduling and provide
alternative flight options, if available.
3.6 Booking Management:
 The system shall provide a dashboard for users to view and manage their bookings.
 The system shall allow users to modify their booking details, such as passenger
names or contact information.
 The system shall enable users to cancel their bookings and initiate refund requests.
3.7 Notification and Alert System:
 The system shall send notifications and alerts to users regarding their bookings,
such as flight delays, gate changes, or cancellations.
 The system shall notify users of any changes to their scheduled
flights. Non-Functional Requirements:
4.1 Usability:
 The system shall have a user-friendly interface with intuitive navigation.
 The system shall provide clear instructions and feedback to users during the
booking process.
4.2 Performance:
 The system shall be capable of handling a large number of concurrent users.
 The system shall respond to user requests within an acceptable response time.
4.3 Security:
 The system shall ensure the confidentiality and integrity of user data.
 The system shall implement appropriate measures to prevent unauthorized access
to user accounts and sensitive information.
 The system shall encrypt sensitive data, such as user passwords and
payment information.
4.4 Reliability:
 The system shall be highly available and minimize downtime.
 The system shall have a backup and recovery mechanism to prevent data loss in
case of failures.
4.5 Scalability:

3 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

 The system shall be scalable to accommodate

future growth in user traffic and database size.
4.6 Compatibility:
 The system shall be compatible with popular web browsers and
mobile devices.
 Constraints:
 The system shall comply with relevant industry regulations
and standards.
 The system development shall adhere to the allocated budget
and timeline.
 Assumptions:
 It is assumed that the system will be developed
using modern web development technologies.
 It is assumed that the necessary APIs for flight
availability, ticketing, and payment processing will be
available.
This SRS document provides a comprehensive overview of the requirements for an Airline
Reservation System. It serves as a blueprint for the development team to design and implement the
system while ensuring that it meets the desired functionality, performance, security, and usability
standards.

4 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q3. Make Entity-Relationship Diagram of the following:

 Library Management System
 Hospital Management System
 Grocery Inventory Management System

LIBRARY MANAGEMENT SYSTEM

Book_id
Author
Pub_id
Title Address

Price
Published
BOOKS PUBLISHER
by

Available
Name

Name

Exp_date
Address

Due_date

Borrowed
by MEMBER

Return_date Mem_id Mem_type

Issue
Mem_date

5 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

HOSPITAL MANAGEMENT SYSTEM

PName

Hos_Name

PDiagnosis P_id
Hos_id Hos_address

Admitted
PATIENT in HOSPITAL

Hos_City
PAddress

has has

Salary

MEDICAL RECORD DOCTOR

Record_id Problem Qualification D_Id

DName
Record_date

6 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

GROCERY INVENTORY MANAGEMENT SYSTEM

Manager_id Sid

D_Name Semail
Manager_sdate Saddress
Sdealer
D_id
SUPPLIER Sname
DEPARTMENT

Sphone

Supplies

Works
for
Prod_id Price

PRODUCT

Prod_name Quantity

E_Name
Address

Pur_id Profit
E_id
EMPLOYEE Buy

Salary Pur_date Total_amt

Phone_no

CUSTOMER
LOGIN

Admin C_id
Password Address
Id
C_Name
Username C_phoneno

7 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q4. To create the function-oriented diagram: Data Flow Diagram (DFD)

 Library Management System
 Hospital Management System
 Grocery Inventory Management System

DATA FLOW DIAGRAM

LIBRARY MANAGEMENT SYSTEM

(Level-0)

(Level-1)

8 KRISH RAI BHALLA

35390302022
SOFTWARE ENGINEERING LAB FILE (BCA 274)

HOSPITAL MANAGEMENT SYSTEM

(Level-0)

(Level-1)

9 KRISH RAI BHALLA

35390302022
SOFTWARE ENGINEERING LAB FILE (BCA 274)

(Level-2)

10 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

GROCERY INVENTORY MANAGEMENT SYSTEM

(Level-0)

(Level-1)

11 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q5. To perform the user’s view analysis for the suggested system: Use Case Diagram.

12 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q6. To draw the structural view diagram for the system: Class diagram.

13 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q7. To draw the behavioral view diagram: State-chart diagram or Activity diagram

14 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q8. To perform the behavioral view diagram for the suggested system: Sequence diagram.

15 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q9. Draw the component diagram.

16 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q10. Draw the Deployment diagram.

17 KRISH RAI BHALLA

35390302022
 SOFTWARE ENGINEERING LAB FILE (BCA 274)

Q11. Perform Measurement of complexity with Halstead Metrics for Chosen System.

Solution:

To perform the measurement of complexity with Halstead Metrics for a chosen system, we
need to:
1. Identify the system or program for which you want to measure complexity.
2. Count the total number of operator occurrences (N1), operand occurrences
(N2), distinct operator types (n1), and distinct operand types (n2) in the
program.
3. Calculate the metrics using the formulas mentioned above.

Here's a simplified example:

Let's say we have a simple Java program with the following code:

public class Example {

public static void main(String[] args)
{ int a = 5;
int b = 10;
int sum = a + b;
System.out.println("Sum: " + sum);
}}

Now, let's calculate the Halstead Metrics for this program:

1. Total Operator Occurrences (N1):
 =: 3 occurrences
 +: 1 occurrence
 ;: 3 occurrences
 (: 1 occurrence
 ): 1 occurrence
 .: 1 occurrence Total N1 = 10

2. Total Operand Occurrences (N2):

 Variables a, b, sum: 3 occurrences
 Literal 5, 10: 2 occurrences
 Method main, System.out.println: 2 occurrences Total N2 = 7

3. Distinct Operator Types (n1):

 =, +, ;, (, ), . Total n1 = 6

4. Distinct Operand Types (n2):

 Variables a, b, sum
 Literal 5, 10
 Method main, System.out.println Total n2 = 7

5. Program Length (N) = 10 + 7 = 17

6. Program Vocabulary (n) = 6 + 7 = 13
7. Program Volume (V) = 17 * log2(13) ≈ 61.51
8. Program Difficulty (D) = (6 / 2) * (7 / 7) = 3.0

18 KRISH RAI BHALLA

35390302022