Indian Institute of Information Technology, Bhopal
Lab File
Software Engineering (CSE - 223)
BTech 2nd year
4th Semester (Section-1) Computer
Science Engineering
Submitted By: Submitted To:
Agrim Agarwal Dr. Vikram Garg
Scholar no.: 23U02052 Department of CSE
Indian Institute of Information Technology, Bhopal
Lab File
Software Engineering (CSE - 223)
BTech 2nd year
4th Semester (Section-1)
Computer Science Engineering
Submitted By: Submitted To:
Adesh Mishra Dr. Vikram Garg
Scholar no.: 23U02048 Department of CSE
INDEX
S. No. Contents Page Date
1 E-R Diagram 1 13/02/25
2 Use Case Diagram 2 20/02/25
3 Sequence Diagram 3 27/02/25
4 State Diagram 4 13/03/25
5 Activity Diagram 5 20/03/25
6 Software Requirements Specification (SRS) 6 03/04/25
7 Data Flow Diagram (DFD) 9 10/04/25
8 Testing Report 10 17/04/25
INDEX
S. No. Contents Page Date
1 E-R Diagram 1 13/02/25
2 Use Case Diagram 2 20/02/25
3 Sequence Diagram 3 27/02/25
4 State Diagram 4 13/03/25
5 Activity Diagram 5 20/03/25
6 Software Requirements Specification (SRS) 6 03/04/25
7 Data Flow Diagram (DFD) 9 10/04/25
8 Testing Report 10 17/04/25
Decomposed Data Flow Diagram
Processes
0.1 Event Browsing
0.2 Ticket Booking
0.3 Payment Processing
0.4 Event Management
0.5 Admin Analytics
Data Stores
D1 Event Database
D2 Ticket Database
D3 Payment Records
D4 Analytics Reports
External Entities:
User
Event Manager
Admin
Payment Gateway
Decomposed Data Flow Diagram
Processes
0.1 Event Browsing
0.2 Ticket Booking
0.3 Payment Processing
0.4 Event Management
0.5 Admin Analytics
Data Stores
D1 Event Database
D2 Ticket Database
D3 Payment Records
D4 Analytics Reports
External Entities:
User
Event Manager
Admin
Payment Gateway
Decomposed Data Flow Diagram
Testing is an essential phase in the software development life cycle to ensure that the developed
system meets the specified requirements and functions correctly. It helps in identifying defects or
errors in the software and ensures its quality, reliability, and performance before deployment.
The following types of testing were performed:
• Unit Testing: Individual modules or components were tested independently to verify their
correctness.
• Integration Testing: Multiple modules were combined and tested to ensure they work
together as intended.
• System Testing: The complete system was tested as a whole to validate end-to-end
workflows and to confirm that it meets the specified requirements.
• User Acceptance Testing (UAT): Testing was done from the user's perspective to verify that
the system fulfills the business needs.
Testing activities focused on ensuring that all core functionalities performed correctly without
critical errors.
Performance Testing using JMeter
Apache JMeter was used for basic performance testing. It simulated multiple users accessing
different functionalities to observe system behavior under load.
The testing checked:
• Response time of pages
• Load handling capacity
• Performance bottlenecks
This helped ensure that the system remains stable and responsive even under moderate traffic
conditions.
Conclusion:
Testing confirmed that the system performs its intended functions correctly and can handle user load
within acceptable response times. Minor improvements were suggested for performance
optimization.
Decomposed Data Flow Diagram
Testing is an essential phase in the software development life cycle to ensure that the developed
system meets the specified requirements and functions correctly. It helps in identifying defects or
errors in the software and ensures its quality, reliability, and performance before deployment.
The following types of testing were performed:
• Unit Testing: Individual modules or components were tested independently to verify their
correctness.
• Integration Testing: Multiple modules were combined and tested to ensure they work
together as intended.
• System Testing: The complete system was tested as a whole to validate end-to-end
workflows and to confirm that it meets the specified requirements.
• User Acceptance Testing (UAT): Testing was done from the user's perspective to verify that
the system fulfills the business needs.
Testing activities focused on ensuring that all core functionalities performed correctly without
critical errors.
Performance Testing using JMeter
Apache JMeter was used for basic performance testing. It simulated multiple users accessing
different functionalities to observe system behavior under load.
The testing checked:
• Response time of pages
• Load handling capacity
• Performance bottlenecks
This helped ensure that the system remains stable and responsive even under moderate traffic
conditions.
Conclusion:
Testing confirmed that the system performs its intended functions correctly and can handle user load
within acceptable response times. Minor improvements were suggested for performance
optimization.
