CASE STUDY:
SATELLITE-BASED NAVIGATION SYSTEM
- SYSTEM ARCHITECTURE IN OOAD
INTRODUCTION
A Satellite-Based Navigation System like
GPS provides
real-time location and route guidance.
Navigation systems like GPS, GLONASS,
Galileo use
satellites to determine precise positions.
Core components: Space segment, Control
segment,
and User segment.
Our goal: Apply Object-Oriented Design to
analyze and
OBJECTIVES
Understand the components of a satellite
navigation system.
Apply OO concepts to model the
architecture.
Design class and sequence diagrams.
Use appropriate design patterns for
better modularity.
SYSTEM OVERVIEW
Space Segment: Constellation of satellites
continuously sending signals.
Control Segment: Ground stations manage
satellite
orbits and time synchronization.
User Segment: GPS-enabled devices
(e.g., smartphones, vehicles).
Integrates real-time map data, location
tracking,
and voice-guided routing
FUNCTIONAL & NON-FUNCTIONAL
REQUIREMENTS
Functional:
Fetch coordinates from satellites.
Calculate optimal route (shortest/fastest).
Display turn-by-turn navigation with audio
support.
Provide dynamic traffic alerts.
Non-Functional:
High availability & fault tolerance.
Support for multi-language & regional
settings.
Secure data transmission.
Real-time responsiveness even in low signal
conditions.
LAYERED SYSTEM ARCHITECTURE
1. Presentation Layer
Interface for users
(maps, directions,
alerts).
2. Application Layer
Core logic: routing,
traffic handling,
location updates.
[Link] Layer
APIs: map service, weather updates, traffic feeds.
[Link] Layer
Stores map data, user preferences, navigation
history.
Key Insight: Layered architecture promotes
separation of concerns.
USE CASE DIAGRAM
Actors:
User
Satellite
Ground Station
Use Cases:
Get Current Location
Calculate Route
View Navigation Directions
Receive Real-Time Alerts
CLASS DIAGRAM
Models classes and their relationships
Show associations between:
NavigationDevice → GPSReceiver,
RoutePlanner
RoutePlanner → MapService
GroundStation ↔ Satellite
1. Satellite: Sends coordinates
2. GPSReceiver: Receives satellite
signals
3. RoutePlanner: Calculates optimal path
4. NavigationDevice: Central logic for
route & display
SEQUENCE DIAGRAM
– NAVIGATION REQUEST
Steps:
1. User initiates navigation.
2. GPSReceiver fetches signal.
3. Satellite sends coordinate data.
4. RoutePlanner generates path using MapService.
5. Device shows path and begins voice guidance
DESIGN PATTERNS USED
Observer: Traffic data updates users in real-
time.
Strategy: Different route planning algorithms
(e.g., avoid tolls, fastest route).
Facade: Simplifies complex subsystems for
user interface.
Singleton: Only one instance of map and
traffic services for consistency.
Example: [Link]() for
Singleton.
OBJECT ORIENTED DESIGN
Encapsulation:
PRINCIPLES APPLIED
Each class handles its
own
data & behavior.
Abstraction: Hide satellite calculations
behind
getCoordinates().
Modularity: Independent components like
GPS,
Routing, Map service.
Reusability: Same RoutePlanner logic can
work
BENEFITS OF OO DESIGN
Easier to maintain and extend
(e.g., add new map layers, update
routing).
Better testability through isolated
units.
Scalability for millions of users.
Cross-platform deployment
(smartphones, cars, smartwatches).
CONCLUSION
A Satellite-Based Navigation System can be
effectively modeled using OOAD.
Architecture ensures accuracy, efficiency, and
modularity.
Using OO principles improves system clarity
and development speed.
THANK YOU
Presented by : (Group 1)
B. Aishwarya Ananda Kamala [23031A0504]
A. Syam Nirmal [23031A0501]
A. Nikhil Dutt [23031A0502]
B. Sai Ram [23031A0503]
B.K.S.V. RAMCHARAN [23031A0505]
B. Lahya Sree [23031A0506]
B. Sunanda [24035A0501]
B. Mohan Sri Krishna [24035A0502]