Shri Ramdeobaba College of Engineering & Management, Nagpur
Department of Electronics Engineering
ECSP 4003
SOFTWARE ENGINEERING LAB
IV SEMESTER SECTION B 2024-2025
Experiment No: Title of Experiment:a. Explore the perspectives and
notations of the Unified Modeling Language (UML) in
Star
UML.
b. Study the IEEE SRS standard and prepare SRS for
the conceptualization of the identified
systems
Name Prahlad Saraf
Roll. No. /Batch
26 / B3
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 1
Experiment No: 1
Title of Experiment:
a. Exploring UML Perspectives and Notations in StarUML
b. Studying the IEEE SRS Standard and Preparing SRS for an
Identified System
Part A: Exploring UML Perspectives and Notations in
StarUML
StarUML is a powerful tool for designing Unified Modeling Language
(UML) diagrams. UML provides a standardized method for visualizing,
specifying, constructing, and documenting software system components.
Using StarUML, various UML perspectives can be represented, including
functional, structural, and behavioral aspects.
1. Use Case Diagram
A Use Case Diagram represents the functional requirements of a system by
depicting user interactions and system functionalities.
Notations:
● Actors: Represented by stick figures, indicating users or external
systems interacting with the system.
● Use Cases: Represented as ovals containing text, describing system
functions.
● Relationships:
○ Solid lines connect actors to use cases.
○ Arrows indicate interaction direction.
○ Dashed lines represent dependencies between use cases.
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 2
2. Class Diagram
A Class Diagram represents the structural elements of a system, including
classes, attributes, methods, and relationships among them.
Notations:
● Classes: Represented as rectangles divided into three sections:
○ Top: Class name
○ Middle: Attributes (variables)
○ Bottom: Methods (functions)
● Relationships:
○ Solid lines: Represent associations.
○ Dashed lines: Indicate dependencies.
○ Triangle-headed lines: Show inheritance
(generalization-specialization relationship).
3. Component Diagram
A Component Diagram represents the system's physical components and
their dependencies, often used for architectural and deployment modeling.
Notations:
● Components: Represented as rectangles labeled "component."
● Interfaces: Depicted as circles (lollipop notation) to indicate exposed
functionalities.
● Relationships: Lines connecting components with arrows to represent
dependencies and data flow.
Part B: IEEE SRS Standard for "Make My Trip" Application
The IEEE Software Requirements Specification (SRS) standard provides
structured guidelines for documenting system requirements to ensure clarity,
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 3
completeness, and consistency. Below is a conceptualized SRS for the "Make
My Trip" mobile application.
1. Introduction
1.1 Purpose
This document defines the Software Requirements Specification (SRS) for
"Make My Trip," a mobile application designed for seamless travel planning,
booking, and itinerary management.
1.2 Scope
The application allows users to:
● Plan and book flights, hotels, transportation, and tour packages.
● Access the platform on both iOS and Android devices.
● Manage travel itineraries and receive real-time updates.
1.3 Definitions, Acronyms, and Abbreviations
● SRS: Software Requirements Specification
● API: Application Programming Interface
● UI: User Interface
1.4 References
● IEEE Standard 830-1998:
Recommended Practice for Software
Requirements Specifications
● Android & iOS Development Guidelines
2. Overall Description
2.1 Product Perspective
"Make My Trip" operates as a standalone application that integrates with
external APIs for real-time bookings, payments, and customer support.
2.2 Product Features
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 4
● Search and book flights, hotels, and travel services.
● Create and manage travel itineraries.
● Receive trip-related notifications and alerts.
● Secure payment processing with encryption.
● Integration with loyalty programs and user accounts.
2.3 User Classes and Characteristics
● Travelers: Users booking and managing trips.
● Administrators: Platform managers overseeing operations.
● Customer Support Representatives: Assisting users with bookings
and queries.
2.4 Operating Environment
● Compatible with: iOS and Android devices.
● Backend Infrastructure: Cloud-hosted for scalability and reliability.
3. System Features
3.1 Flight Search and Booking
Users can search and book flights based on locations, dates, and
Description:
preferences.
Functional Requirements:
● Users input travel details (departure/arrival locations, dates,
passengers).
● System fetches and displays available flight options (sorted by
price/duration).
● Users select flights, proceed to secure payment, and receive booking
confirmation.
3.2 Hotel Booking
Description: Users can search and book hotels.
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 5
Functional Requirements:
● Users filter hotels by location, price, and rating.
● System displays hotel details, images, and user reviews.
● Users can reserve hotels through a secure payment gateway.
4. External Interface Requirements
4.1 User Interfaces
The application features an intuitive and responsive UI with key screens,
including:
● Home Page: Search options for flights and hotels.
● Search Results Page: Displays available bookings with sorting and
filtering.
● Booking Confirmation Page: Displays successful reservations.
● User Account Page: Allows profile and itinerary management.
4.2 Hardware Interfaces
● Compatible with iOS and Android devices.
● Requires mobile devices with internet connectivity.
4.3 Software Interfaces
● Integration with third-party APIs for real-time data (flights, hotels,
payments).
● Secure payment gateway supporting multiple payment methods.
5. System Attributes
5.1 Reliability
● Application uptime must be 99.9% with scheduled maintenance
periods.
5.2 Security
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 6
● Sensitive user data (e.g., payment details) must be encrypted using
industry-standard protocols.
5.3 Performance
● Search results must load within three seconds.
● The system must handle high traffic loads, especially during peak
booking times.
6. Other Requirements
6.1 Legal and Regulatory Compliance
● The application must comply with data privacy laws, including GDPR
for European users.
6.2 Documentation
● The system must include user manuals, technical documentation,
and maintenance guides.
Conclusion
This SRS document follows the IEEE standard, ensuring clear, structured,
and well-defined requirements for the "Make My Trip" application. By
adhering to these guidelines, development efforts are streamlined, user
expectations are met, and legal and security regulations are complied with.
ECSP4003_Software Engineering Lab, RCOEM, Nagpur
Page | 7
