Srs Swe Final

Software Requirements Specifications Document
CS330 Software Engineering
Software Requirements Specification (SRS) Template
Items that are intended to stay in as part of your document are in bold;
explanatory comments are in italic text. Plain text is used where you might
insert wording about your project.
The document in this file is an annotated outline for specifying software

requirements, adapted from the IEEE Guide to Software Requirements
Specifications (Std 830-1993).
Tailor this to your needs, removing explanatory comments as you go along.

Where you decide to omit a section, keep the header, but insert a comment
saying why you omit the data.
Q:\IRM\PRIVATE\INITIATI\QA\QAPLAN\SRSPLAN.doc Page 1 of 20
01/15/20
f
(University Mapping 3D)

SR.NO ROLL NO. TEAM MEMBER
1 22IT1079 VIRAJ MUZUMDAR
2 22IT1107 ANVESH MULGIR
3 22IT1061 SAMEER MULANI
Software Requirements Specification
Document
Version: (n) Date:
01/15/20
f
Table of Contents
1. Introduction 6
1.1 Purpose 6
1.2 Scope 6
1. Campus Visualization: 6
Creating accurate and detailed 3D models of university campuses, including buildings, landscapes, and key
landmarks. 6
2. Interactive Exploration: 6
Implementing user-friendly interfaces and navigation controls for seamless exploration of the virtual campus
environment. 6
3. Accessibility and Integration: 6
Developing cross-platform compatibility to ensure accessibility across various devices and VR headsets. 6
1.3 Definitions, Acronyms, and Abbreviations. 6
1.5 Overview 7
The Overall Description 7

2.1 Product Perspective 8
System Interfaces 9
2.1.2 Interfaces 9
2.1.3 Hardware Interfaces 10
2.1.5 Communications Interfaces 10
Headset Display & Audio 10
Motion Controller Inputs 10
Room-Scale Tracking 10
Gesture Recognition 10
Voice Commands 10
Haptic Feedback 10
2.1.6 Memory Constraints 11
2.1.7 Operations 11
2.1.8 Site Adaptation Requirements 11
Product Functions 12
2.3 User Characteristics 12
2.4 Constraints 13
2.5 Assumptions and Dependencies 14
2.6 Apportioning of Requirements. 15
3. Specific Requirements 16
3.3 Performance Requirements 17
3.6 Software System Attributes 19
1.1 Purpose
01/15/20
f
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. The Overall Description

2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirements
3. Specific Requirements
3.1 External interfaces
3.2 Functions
3.3 Performance Requirements
3.4 Logical Database Requirements
3.5 Design Constraints
3.5.1 Standards Compliance
3.6 Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing the Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3.7.6 Response
3.7.7 Functional Hierarchy
01/15/20f
3.8 Additional Comments
4. Change Management Process
5. Document Approvals
6. Supporting Information
01/15/20
f
1. Introduction
University Mapping in 3D utilizes cutting-edge technology to create immersive virtual
replicas of university campuses. This innovative approach allows users to explore campus
environments in detail, offering a dynamic and interactive experience that enhances
engagement and accessibility.
1.1 Purpose
The purpose of University Mapping in 3D is to provide an immersive and detailed virtual

representation of campus environments, facilitating remote exploration, decision-making,
and engagement for students, educators, and the wider community.
1.2 Scope
1. Campus Visualization:
Creating accurate and detailed 3D models of university campuses, including buildings,
landscapes, and key landmarks.
2. Interactive Exploration:
Implementing user-friendly interfaces and navigation controls for seamless exploration of
the virtual campus environment.
3. Accessibility and Integration:

Developing cross-platform compatibility to ensure accessibility across various devices
and VR headsets.
1.3 Definitions, Acronyms, and Abbreviations.
[1] Retrieved October 28, 2013, From

http://www.android.com/kitkat/index.html

http://www.autodesk.com/products/autodesk-3ds-max/overview
01/15/20
f
http://unity3d.com/unity
1.4 References
1. Aggarwal, P., Anand, A., & Rai, R. (2020). Virtual Reality Based Campus Navigation
System. In 2020 International Conference on Artificial Intelligence and Virtual Reality
(AIVR) (pp. 209-213). IEEE.
2. Alrajhi, M., Ismail, M. A., & Alsaeed, M. (2020). A Review of Virtual Reality
Technologies in Campus 3D Mapping. International Journal of Emerging Technologies in
Learning (iJET), 15(07), 168-183.
3. Gao, Y., Cheng, Z., Shao, Z., & Zhou, C. (2021). Construction of 3D Virtual Campus
Based on VR Technology. In 2021 IEEE International Conference on Computational
Science and Engineering (CSE) (pp. 645-650). IEEE.
4. Liu, L., Chen, D., Liu, L., & Xiong, H. (2020). Design and implementation of a virtual
reality campus navigation system based on WebGL. In 2020 IEEE 6th International
Conference on Computer and Communications (ICCC) (pp. 3185-3189). IEEE.
5. Wang, J., & Chen, M. (2020). Design and Implementation of VR Campus Navigation
System Based on Unity3D. In 2020 IEEE International Conference on Mechatronics and
Automation (ICMA) (pp. 978-983). IEEE.
1.5 Overview
Description of Contents:
For customers and potential users, Section 2 delves into the system
requirements, outlining functionalities, constraints, and user expectations.
On the other hand, developers will find Section 3 particularly valuable, as it
focuses on the technical specifications, architectural design, and
implementation details.
The Overall Description

The Overall Description section of the University Mapping 3D project
provides a contextual background for the product and its requirements.
01/15/20
f
It outlines the key factors influencing the development and usage of the
system without specifying detailed requirements.
This section aims to present a clear understanding of the project's purpose,
scope, and target audience in plain language for the customer's consumption.
2.1 Product Perspective
In comparison to other related products in the marketplace, University

Mapping 3D offers unique features tailored specifically for university
campus exploration.
While there may be general mapping or navigation applications available,
they often lack the detailed campus-specific information and immersive 3D
experience provided by University Mapping 3D.
Additionally, existing virtual tour platforms may not offer the level of
customization and interactivity required to effectively showcase the diverse
facilities and amenities of university campuses.
In a research-oriented context, University Mapping 3D may draw parallels
with studies focusing on virtual reality (VR) applications in education and
immersive learning environments.
University Mapping 3D aims to contribute to this body of research by
providing a specialized VR platform for exploring university campuses,
thereby potentially improving prospective students decision-making
processes and increasing engagement with higher education institutions.
01/15/20
f
External Systems
(University APIs, Web
Services, etc)
User Interface | | (VR
Headset, Web
Interface, etc)
Database (Campus Data,
User Profiles)
System Interfaces
University Database:
Functionality: The software retrieves campus information such as building layouts,
facilities, landmarks, and campus events from the university's database.
Geolocation Services:
Functionality: To enable real-time navigation and location tracking, the software
interfaces with geolocation services to determine the user's position on the campus map.
User Authentication System:

Functionality: The software requires user authentication to access personalized features
such as saved preferences, favorites, and personalized tours.
External Content Providers:

Functionality: To enrich the mapping experience, the software may integrate with
external content providers for additional information such as historical facts, virtual tours,
or multimedia content related to specific campus locations.
2.1.2 Interfaces
01/15/20
f
System
Interfaces
Logical Optimization
Characteristics Aspects
Graphical User Interaction Accessibility User-Friendly Customization

Clear Navigation
Interface (GUI) Modes Considerations Design Options
2.1.3 Hardware Interfaces
SR.NO HARDWARE
1 VR Headset
2 Motion Controllers
2.1.5 Communications Interfaces
Headset Display & Audio

Motion Controller Inputs
Room-Scale Tracking
Gesture Recognition
Voice Commands
Haptic Feedback
01/15/20f
2.1.6 Memory Constraints
Market research indicates target machines have between 256-512 MB of

RAM.
Target design footprint should not exceed 256 MB of RAM.
Optimize textures and models to minimize RAM usage.
Implement level-of-detail techniques to reduce memory usage for distant
objects.
Utilize streaming and caching mechanisms for efficient memory
management.
Consider dynamic memory allocation and deallocation for optimal resource
utilization.
Ensure compatibility with systems having limited RAM capacity, aiming for
optimal performance within memory constraints.
2.1.7 Operations
Mode of Operation Data Processing Backup and

Support Funtion Recovery Operation
• Explorarion • Rendering • Regular Backup
• Guided Tour Mode • Spatial Data • Disaster Recovery
• Annotation Mode Mangement
• User Data
Management
2.1.8 Site Adaptation Requirements
Customizable user interfaces to reflect the university's branding and design

guidelines.
Integration with existing university systems such as student databases,
scheduling software, and campus management platforms.
Support for multiple languages or localization to accommodate diverse user
populations.
01/15/20
f
Compatibility with various VR hardware setups to ensure accessibility

across different devices.
Training and support documentation tailored to the university's staff and user
base. needs to be done so that your system will install and operate correctly
should be documented here.
Product Functions
Explore •Allows users to navigate and explore the university

Campus campus virtually
Interactive
Maps: •Provides interactive 3D maps of the campus.
Building •Displays detailed information about
Information buildings and facilities.
Classroom •Helps users locate specific classrooms or
Locator lecture halls within buildings.
Virtual Tours
•Offers guided virtual tours of the campus
Information •Provides informational points throughout
Points the campus.
2.3 User Characteristics
Users can move around freely to discover various buildings, landmarks, and
facilities
Users can view different sections of the campus and obtain information
about buildings, departments, and points of interest.
Users can access information such as building names, departments housed
within, operating hours, and contact details
01/15/20
f
Users can search for rooms by name, number, or department, and receive
directions to their destination.
Users can embark on pre-designed tours or customize their own route to
explore specific areas of interest.
Users can interact with these points to access additional details, historical
information, or multimedia content.
2.4 Constraints
Regulatory Policies: Compliance with laws and regulations regarding data

privacy, accessibility, and content restrictions.
Hardware Limitations: Adhering to the technical specifications and

performance capabilities of VR hardware devices.
Interface to Other Applications: Ensuring compatibility and seamless

integration with existing university systems or third-party applications.
Parallel Operation: Managing concurrent tasks and processes efficiently to

optimize performance and resource utilization.
Audit Functions: Implementing logging and tracking mechanisms to monitor

user interactions and system activities for auditing purposes.
Control Functions: Incorporating mechanisms for user controls, navigation,

and interaction within the VR environment.
Higher-Order Language Requirements: Utilizing programming languages

and frameworks suitable for developing complex 3D VR applications.
Signal Handshake Protocols: Implementing communication protocols for

exchanging data and commands between hardware components and software
modules.
01/15/20
f
Reliability Requirements: Ensuring consistent performance, stability, and

availability of the VR application for users.
Criticality of the Application: Assessing the importance and impact of the

VR application on university operations and user experience.
Safety and Security Considerations: Addressing potential risks related to

user safety, data security, and system vulnerabilities in the VR environment.
2.5 Assumptions and Dependencies
Certainly, here are some assumptions and dependencies for a university

mapping 3D VR system:
1. Hardware Availability: Assumption that compatible VR hardware, such as

headsets and motion controllers, will be available for users to access the
virtual environment.
2. Operating System Compatibility: Assumption that the software will be

compatible with common operating systems used in VR devices, such as
Windows Mixed Reality, Oculus, or Steam VR.
3. Internet Connectivity: Dependency on stable internet connectivity for

streaming high-resolution 3D maps or accessing cloud-based resources if
applicable.
4. User Familiarity with VR: Assumption that users will have basic
familiarity with VR technology and its interaction methods, which may
influence the complexity and intuitiveness of the user interface.
5. Data Accuracy and Updates: Dependency on the accuracy and timely

updates of university mapping data, including building layouts, room
assignments, and campus landmarks.
01/15/20
f
6. Security and Privacy Concerns: Assumption that appropriate security

measures will be implemented to protect user data and ensure privacy,
especially if the system involves user accounts or personalized features.
9. Software Development Tools and Libraries: Assumption that the

development team will have access to necessary software development tools,
libraries, and frameworks to implement features efficiently and effectively.
2.6 Apportioning of Requirements.
Here's a brief outline of how you can apportion the requirements for the
university mapping 3D VR project:
Essential Requirements (Must-Haves):

These are the core functionalities necessary for the initial release of
the system.
Prioritize requirements that directly contribute to the primary
objectives of the project, such as basic navigation, campus
visualization, and user interaction.
Desirable Requirements (Nice-to-Haves):

Features that enhance the user experience but are not critical for the initial
release.
Consider including features like advanced interaction mechanisms,
additional campus information overlays, or immersive effects.
Future Iteration Requirements (Deferred):

Requirements that can be postponed to future iterations or versions of
the system.
Identify functionalities that are less critical or require more
development time, such as advanced AI-driven interactions, complex
simulation elements, or extensive customization options.
Customer Prioritization:
01/15/20
f
Consult with the customer to prioritize requirements based on their

needs and expectations.
Obtain feedback on which features are essential for the initial release
and which can be deferred or included in later iterations.
Resource Constraints:
Take into account the project plan and available hours to determine
the feasibility of implementing all requirements.
If there are limitations in resources or time, focus on delivering the
essential requirements within the allocated timeframe while
considering options for future enhancements.
Iterative Development Approach:

Plan to iteratively deliver features in successive releases or sprints.
Use customer feedback and evolving project requirements to guide the
selection of requirements for each iteration, ensuring flexibility in
adapting to changing priorities and constraints.
3. Specific Requirements
High-Quality 3D Models:
Acquire or create detailed 3D models of university buildings, landmarks, and important
structures.
Ensure the accuracy of dimensions and proportions for realistic representation.
Geospatial Data Integration:
Use geospatial data to accurately position buildings and features within the university
campus.
Integrate geographical information system (GIS) data for accurate terrain representation.
Texture Mapping:
Apply high-resolution textures to the 3D models to enhance realism.
Capture and use real textures from the university buildings to make the models visually
accurate.
User Interface (UI):
Develop an intuitive user interface for navigation and interaction within the 3D map.
Include features like zoom, pan, and rotation controls for easy exploration.
Interactive Elements:
Add interactive elements such as clickable buildings, information hotspots, or links to
relevant data or websites.
Implement pop-up information windows for specific locations.
01/15/20
f
Multi-Platform Compatibility:
Ensure that the 3D mapping application is compatible with various devices and platforms
(desktop, mobile, virtual reality, etc.).
Navigation System:
Implement a user-friendly navigation system that allows users to easily move around the
campus.
Include features like search functionality, route planning, and pathfinding.
Accessibility:
Consider accessibility features to accommodate users with disabilities.
Ensure compatibility with screen readers and provide alternative navigation options.
Real-time Updates:
If applicable, integrate a system for real-time updates, especially if there are ongoing
construction projects or changes in the campus layout.
Security:
Implement security measures to protect sensitive data, especially if the 3D mapping project
includes information on restricted areas or facilities.
Scalability:
Design the project to be scalable for future additions or modifications to the campus layout.
Collaboration and Sharing:
Provide options for users to collaborate or share specific views or information from the 3D
map.
Performance Optimization:
Optimize the performance of the application to ensure smooth rendering and responsiveness,
even on lower-end devices.
Legal and Privacy Compliance:
Ensure that the project complies with legal and privacy regulations, especially when it
involves capturing and displaying real-world data.
Feedback Mechanism:
Include a feedback mechanism for users to report inaccuracies or suggest improvements.
3.3 Performance Requirements
Rendering Speed:
Ensure that the 3D models render quickly and smoothly to provide a seamless user
experience.
Optimize rendering techniques and consider level of detail (LOD) models for distant objects.
Frame Rate:
Aim for a consistent and high frame rate to avoid laggy or jittery movements.
Consider optimizing textures, shaders, and rendering settings to maintain a smooth frame
rate.
01/15/20
f
Load Time:
Minimize the time it takes to load the 3D map initially.
Implement techniques such as asynchronous loading of assets or progressive loading to
prioritize essential elements.
Resource Usage:
Optimize resource usage, including CPU, GPU, and memory, to ensure the application runs
efficiently.
Implement techniques like texture compression and efficient memory management.
Compatibility:
Ensure compatibility with a range of devices, including various computer specifications and
mobile devices.
Implement adaptive rendering settings based on the user's device capabilities.
Network Performance:
If the 3D mapping project requires data from the internet, optimize network requests to
minimize latency.
Implement caching mechanisms for frequently accessed data.
Scalability:
Design the system to scale gracefully as the number of users and the complexity of the map
increase.
Consider load balancing for server-side components to distribute the workload efficiently.
Real-time Updates:
If the project includes real-time updates, ensure that the system can handle and display
changes promptly without causing disruptions.
User Interaction Responsiveness:
Optimize response times for user interactions such as panning, zooming, and clicking on
interactive elements.
Implement efficient algorithms for pathfinding and route planning if these features are
included.
Cross-Browser Compatibility:
Ensure compatibility with various web browsers to provide a consistent experience for users.
Error Handling:
Implement effective error handling to gracefully manage unexpected issues and provide
meaningful error messages to users.
Security Measures:
Implement security features without compromising performance, such as encryption and
secure data transmission.
Testing and Profiling:
Regularly conduct performance testing and profiling to identify bottlenecks and areas for
improvement.
Use profiling tools to analyze resource usage and optimize accordingly.
Continuous Monitoring:
Implement monitoring tools to detect performance issues in real-time and provide insights for
ongoing optimization efforts.
01/15/20
f
Documentation:
Maintain comprehensive documentation on performance considerations, optimizations made,
and guidelines for future development to ensure consistency.
3.6 Software System Attributes
Accessibility:
Detail accessibility requirements, ensuring the 3D mapping project is usable by individuals with
disabilities.
Specify compatibility with assistive technologies and alternative navigation options.
Availability and Reliability:

Define the acceptable level of system uptime and reliability to ensure consistent user access.
Specify redundancy and failover mechanisms to maintain functionality in case of system failures.
Security Measures:
Specify security requirements for protecting sensitive data related to the university's
infrastructure and facilities.Define user authentication and authorization mechanisms to control
access.
Usability and User Experience:

Establish usability requirements, including an intuitive and user-friendly interface for easy
navigation.Detail user experience considerations such as clear labels, tooltips, and contextual
information.
Scalability:
Specify the scalability requirements to accommodate an increasing number of users or additional
features.Consider scalability regarding the addition of new buildings or modifications to the
campus layout.
Mobile Compatibility:
Define requirements for mobile compatibility, ensuring the 3D mapping project functions
optimally on various devices, including mobile phones and tablets.
Collaboration Features:
Specify collaboration features, such as the ability for users to share specific views or information
from the 3D map.Define requirements for multiple users to interact with the map simultaneously.
Feedback Mechanism:
Establish requirements for a user-friendly feedback system to gather input, bug reports, and
improvement suggestions.
01/15/20
f
Compliance:
Detail compliance requirements with data privacy regulations, university policies, and any
applicable standards or guidelines.
Real-time Updates:
If relevant, specify requirements for real-time updates, especially for dynamic changes in campus
structures or events.
Customization and Configuration:

Define options for users to customize their experience, such as adjusting map preferences or
saving personalized views.
Documentation:
Specify documentation requirements for users, administrators, and developers to facilitate
understanding, troubleshooting, and maintenance
01/15/20
f

Srs Swe Final

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Srs Swe Final

Uploaded by

Copyright:

Available Formats

Software Requirements Specifications Document

CS330 Software Engineering

Software Requirements Specification (SRS) Template

The document in this file is an annotated outline for specifying software

Tailor this to your needs, removing explanatory comments as you go along.

(University Mapping 3D)

Software Requirements Specification

Version: (n) Date:

The Overall Description 7

2. The Overall Description

3.8 Additional Comments

4. Change Management Process

The purpose of University Mapping in 3D is to provide an immersive and detailed virtual

3. Accessibility and Integration:

1.3 Definitions, Acronyms, and Abbreviations.

[1] Retrieved October 28, 2013, From

[2] Retrieved October 28, 2013, From

[3] Retrieved October 28, 2013, From

The Overall Description

2.1 Product Perspective

In comparison to other related products in the marketplace, University

User Authentication System:

External Content Providers:

Graphical User Interaction Accessibility User-Friendly Customization

2.1.3 Hardware Interfaces

2.1.5 Communications Interfaces

Headset Display & Audio

2.1.6 Memory Constraints

Market research indicates target machines have between 256-512 MB of

Mode of Operation Data Processing Backup and

2.1.8 Site Adaptation Requirements

Customizable user interfaces to reflect the university's branding and design

Compatibility with various VR hardware setups to ensure accessibility

Explore •Allows users to navigate and explore the university

2.3 User Characteristics

Regulatory Policies: Compliance with laws and regulations regarding data

Hardware Limitations: Adhering to the technical specifications and

Interface to Other Applications: Ensuring compatibility and seamless

Parallel Operation: Managing concurrent tasks and processes efficiently to

Audit Functions: Implementing logging and tracking mechanisms to monitor

Control Functions: Incorporating mechanisms for user controls, navigation,

Higher-Order Language Requirements: Utilizing programming languages

Signal Handshake Protocols: Implementing communication protocols for

Reliability Requirements: Ensuring consistent performance, stability, and

Criticality of the Application: Assessing the importance and impact of the

Safety and Security Considerations: Addressing potential risks related to

Certainly, here are some assumptions and dependencies for a university

1. Hardware Availability: Assumption that compatible VR hardware, such as

2. Operating System Compatibility: Assumption that the software will be

3. Internet Connectivity: Dependency on stable internet connectivity for

5. Data Accuracy and Updates: Dependency on the accuracy and timely

6. Security and Privacy Concerns: Assumption that appropriate security

9. Software Development Tools and Libraries: Assumption that the

2.6 Apportioning of Requirements.

Essential Requirements (Must-Haves):

Desirable Requirements (Nice-to-Haves):

Future Iteration Requirements (Deferred):

Consult with the customer to prioritize requirements based on their

Iterative Development Approach:

3.3 Performance Requirements

3.6 Software System Attributes

Availability and Reliability:

Usability and User Experience: