0% found this document useful (0 votes)
18 views16 pages

Minor SRS

Uploaded by

anshtyagi142536
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views16 pages

Minor SRS

Uploaded by

anshtyagi142536
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Software

Requirement
s
Specification
For
PathFinder

21-10-2024

Prepared by
Ansh Tyagi 500105272 R2142220033
Aditya Tomar 500106015 R2142221060
Ujjwal Chauhan 500105692 R2142220994
Ankur Sharma 500110541 R2142221433

Page 1
School Of Computer Science UNIVERSITY OF

PETROLEUM & ENERGY STUDIES, DEHRADUN- 248007.

Uttarakhand

Table of Contents

Topic Page No

4
Revision History

5-6
1 Introduction

5
1.1 Purpose of the Project

5
1.2 Target Beneficiary

5
1.3 Project Scope

6
1.4 References

6-10
2 Project Description

6
2.1 Reference Algorithm

6
2.2 Data/ Data structure

6
2.3 SWOT Analysis

7
2.4 Project Features

7
2.5 User Classes and Characteristics

Page 2
7
2.6 Design and Implementation Constraints

7-10
2.7 Design diagrams

10
2.8 Assumption and Dependencies

10-11
3 System Requirements

10
3.1 User Interface

10
3.2 Software Interface

11
3.3 Database Interface

11
3.4 Protocols

11-14
4 Non-functional Requirements

11
4.1 Performance requirements

11
4.2 Security requirements

12-13
4.3 Software Quality Attributes

5 Other Requirements

14
Appendix A: Glossary

Appendix B: Analysis Model

Appendix C: Issues List

Page 3
Revision History

Date Change Reason for Mentor Signature


Changes

Page 4
1 INTRODUCTION

The purpose of this project is to develop a GPS Navigation System that enhances the user’s travel experience
1.1
by providing real-time, efficient navigation. The goal is to assist users in reaching their destination
Purpose of through the shortest possible route, while offering real-time updates on traffic conditions, displaying
the Project nearby essential services such as restaurants, hospitals, and petrol pumps, and continuously tracking
the user’s current location. By utilizing open-source APIs and advanced algorithms based on graph
data structures, the system aims to offer a reliable, accurate, and user-friendly solution for daily
navigation needs. This platform will help users make informed travel decisions, avoid traffic delays, and
find essential services conveniently, ultimately improving the overall journey experience.

1.2 Target The primary beneficiaries of this GPS Navigation System are daily commuters, travelers, and drivers who rely on
Beneficiary accurate and efficient navigation to reach their destinations. Additionally, individuals seeking real-time traffic
updates and nearby services such as restaurants, hospitals, and petrol pumps will greatly benefit from the
platform. Delivery services, ride-sharing companies, and logistics businesses can also utilize the system to
optimize routes and improve operational efficiency. Furthermore, developers and tech enthusiasts can take
advantage of the open-source nature of the project to customize and extend the functionality for various use cases.

•User-friendly Interface: A clean and intuitive interface for users to easily navigate and access route information.
1.3 Project Scope
•Shortest Path Calculation: Implementation of graph data structures and shortest path algorithms to provide users with the most
efficient routes from their starting point to their destination.

•Current Location Tracking: Continuous GPS tracking to display the user’s current location in real-time.

•Nearby Services Display: Integration with open-source APIs to show nearby restaurants, hospitals, and petrol pumps based on
the user’s location.

•Real-time Traffic Updates: Display of live traffic conditions through open-source APIs, allowing users to adjust their routes
accordingly.

•Customizable Route Options: Users can select alternate routes based on their preferences, such as avoiding toll roads or
congested areas.

Page 5
1.4 References • • Google Maps API Documentation: https://developers.google.com/maps/documentation

• OpenStreetMap API Documentation: https://wiki.openstreetmap.org/wiki/API

• Dijkstra’s Algorithm Overview: https://brilliant.org/wiki/dijkstras-short-path-finder/

• Open Traffic Data Sources: https://opentraffic.io/documentation

• Graph Data Structures and Algorithms: https://www.geeksforgeeks.org/graph-data-structure-and-algorithms/

• Leaflet.js Documentation: https://leafletjs.com/reference.html

PROJECT DESCRIPTION
2

2.1 Reference
Algorithm The GPS Navigation System leverages an algorithm to enhance its functionality. A shortest path
algorithm such as Floyd-Warshall algorithm is used to calculate the most efficient route between the
starting point and destination. A location-tracking algorithm is implemented to continuously update the
user’s current location via GPS. Additionally, API calls are used to retrieve real-time data on nearby
restaurants, hospitals, and petrol pumps. A traffic optimization algorithm processes real-time traffic data
to provide alternate routes in case of congestion. Secure authentication algorithms ensure user privacy
and access to personalized navigation features.

The GPS Navigation System will utilize structured data to manage various aspects of navigation, location, and user preferences. For instance:

2.2 Characteristic •User Data: Stores personal information such as name, preferred routes, and frequently visited locations.
of Data
•Location Data: Tracks GPS coordinates for current location, destination, and nearby points of interest like restaurants, hospitals,
and petrol pumps.

•Route Data: Contains structured information about different routes, including distance, estimated travel time, traffic conditions,
and alternate paths.

•Traffic Data: Gathers real-time traffic updates, road closures, and congestion information from open-source APIs to optimize
route suggestions.
•Service Data: Provides details of nearby services such as restaurant names, types, ratings, and distance from the user’s
current location.

Page 6
Page 7
User Student State diagram

Page 8
•• Interactive Navigation Interface: Users can interact with the map interface, input their starting point and destination, and
view the shortest path in real-time. The interface also displays important details like nearby restaurants, hospitals, petrol
2.4 Project Features pumps, and live traffic updates, enhancing the overall navigation experience.

• API Integration for Location & Traffic Data: The system leverages various open-source APIs to fetch real-time traffic details,
nearby points of interest (e.g., restaurants, hospitals, petrol pumps), and accurate location tracking, ensuring up-to-date and
reliable navigation information.

•• Graph-based Shortest Path Algorithms: The system uses graph data structures and shortest path algorithms (like
Dijkstra’s or A* algorithms) to efficiently calculate and display the optimal route from the starting point to the destination,
factoring in current traffic conditions and road networks.

2.5.
•General Users/Drivers: Individuals using the navigation system to find the shortest route between their starting point and destination. They benefit
User from real-time traffic updates, nearby services like restaurants, hospitals, and petrol pumps, as well as accurate location tracking.

Classes
•Travelers/Tourists: Users who need to explore unfamiliar areas. They rely on the system to locate nearby points of interest, such as restaurants
& and hospitals, while ensuring they follow the most efficient route during their journey.

Characte
•Logistics and Delivery Personnel: Professionals who depend on the system to optimize their routes for timely deliveries. They use the shortest
ristics path feature to minimize travel time and stay informed about real-time traffic conditions and fuel stops.

2.6
•• Hardware: The system requires devices with GPS capability and a minimum of 2 GB RAM to smoothly run real-time
Design navigation features. Reliable internet connectivity is essential for fetching real-time traffic updates and nearby location data.
and • Software: The platform relies on up-to-date versions of mobile frameworks like Android SDK or iOS, as well as open-
• source mapping and navigation libraries (e.g., Google Maps API, OpenStreetMap). Compatibility with current versions of these
Implemen tools is crucial for seamless integration.

tation
Constrain
ts

2.7 Design Class Diagram


diagrams

Page 9
User Recruiter State diagram

Page 10
Sequence diagram

2.8 • Assumptions: It is assumed that users have basic knowledge of smartphone or GPS-
enabled device usage, including the ability to input locations, understand map interfaces, and follow
Assumptio navigation instructions. Users are also expected to have access to an internet connection for real-
n and time traffic updates and location services.
• Dependencies: The system depends on open-source APIs such as Google Maps API or
Dependenci
OpenStreetMap for map rendering, real-time traffic data, and nearby service information (e.g.,
es restaurants, hospitals, petrol pumps). It also relies on graph algorithm for calculating the shortest
path. Availability and accuracy of real-time data from third-party services are crucial for optimal
performance. Additionally, device GPS capabilities are necessary for precise location tracking.

3 SYSTEM REQUIREMENTS
•• Interactive Map Dashboard: A dynamic map interface that allows users to input their starting
point and destination, view the shortest route, and track their current location in real-time. The
3.1 User Interface dashboard also displays nearby services such as restaurants, hospitals, and petrol pumps along the
route.
•• Real-time Traffic Overlay: A customizable layer on the map that provides real-time traffic updates,
allowing users to visualize traffic congestion and suggested alternative routes.

Page 11
3.2 Software Interface Communication between the frontend and backend will be facilitated through RESTful APIs, allowing
seamless data exchange for user authentication, project uploads, and search functionalities. Data
management will utilize a structured schema in MongoDB to ensure efficient storage and retrieval of
user and project information.

Page 12
Location, user, and route data will be stored in a relational or
3.3 Database Interface
NoSQL database, such as PostgreSQL or MongoDB, to manage
structured and real-time data efficiently. The database will include
user profiles with preferences, saved routes, and location history.
Additionally, it will store metadata for places of interest (e.g.,
restaurants, hospitals, petrol pumps), traffic data, and map details
for quick retrieval and filtering during navigation.

3.4 Protocols The platform will support standard communication protocols for
dataexchange.

4 NON-FUNCTIONAL REQUIREMENTS
• The platform should support simultaneous user access for up to
4.1 Performance 500 concurrent users without performance degradation.
requirements
• Loading times for project data should not exceed 10 seconds to
ensure a seamless user experience.

• User data must be securely stored in the database, employing


4.2 Security encryption for sensitive information such as passwords and
requirements personal details.
• Access to the platform will require authentication through JWT
tokens to ensure that user sessions are secure and protected against
unauthorized access.

Page 13
4.3 Software Quality Adaptability
Attributes In the context of Pathfinder, adaptability refers to the platform's
ability to accommodate new features, user requirements, and
evolving technologies without extensive code alterations.

Availability
The platform must ensure high availability, meaning Pathfinder
should be accessible and responsive for users whenever needed.

Correctness
Correctness in Pathfinder refers to the accurate execution of core
functionalities as designed.

Page 14
Flexibility
Pathfinder flexibility ensures that new features, such as additional
project categories, user functionalities, or advanced filtering options,
can be integrated without extensive rework.
Interoperability
Pathfinder may require integration with third-party services, such as
job boards, social media platforms, or analytics tools. Interoperability
ensures that the platform can seamlessly connect with these external
services.
Maintainability
Maintainability is crucial for the long-term success of Pathfinder, as it
allows for efficient updates and bug fixes. The platform's codebase
should be modular and well-documented, enabling developers to
address issues (e.g., bugs in project submissions or filtering errors) or
introduce new features, like enhanced user dashboards, without
extensive investigation into unrelated parts of the system. This
approach facilitates ongoing support and feature enhancements.

Portability
Given the potential for Pathfinder to expand to different devices or
platforms, portability ensures that the system can be easily adapted
for various environments, such as mobile or tablet use. The
application should be designed to function on different operating
systems with minimal modifications, allowing users to access the
platform and manage their projects across various devices.

Reliability
Reliability is critical for ensuring that Pathfinder operates smoothly
and consistently. It should maintain stable performance without
crashes or data loss, even during peak usage times. This reliability
fosters trust among users, ensuring a positive experience as they
engage with the recruitment process.

5 OTHER-REQUIREMENTS

NA

Page 15
• API: Application Programming Interface, a set of tools and
Appendix A: Glossary protocols for building software applications.
• Frontend: The user interface and experience part of the application
that users interact with directly.
• GitHub: A web-based platform for version control and
collaboration that allows developers to host and review code.
• Backend: The server-side part of the application that handles data
storage, processing, and logic, which users do not interact with
directly.
• User Experience (UX): The overall experience a user has when
interacting with the application, encompassing ease of use and
satisfaction.
• JSON: JavaScript Object Notation, a lightweight data interchange
format that is easy for humans to read and write and for machines
to parse and generate.

Appendix B: Analysis Model N/A

Appendix C: Issues List N/A

Page 16

You might also like