Software Requirements Specification

for
Jamia Hamdard Application
Version 1.0 approved
Prepared by Group-3
24/10/2024

Copyright © 2023 by Group 3. Permission is granted to use, modify, and distribute this document.
SRS for Jamia Hamdard Application Page ii

Table of Contents
Table of Contents ...........................................................................................................................ii
1.Introduction.................................................................................................................................1
1.1.Purpose................................................................................................................................................1
1.2.Project scope .......................................................................................................................................1
1.3.Document Conventions.......................................................................................................................1
1.4.References ...........................................................................................................................................1
2.System Overview.........................................................................................................................1
2.1.Current System....................................................................................................................................1
2.2.Proposed System .................................................................................................................................1
2.3.Target Audience...................................................................................................................................2
3.System Features ..........................................................................................................................3
3.1.Canteen Information............................................................................................................................3
3.2.Fee-Related Transaction Problem Solution.........................................................................................3
3.3.Library Information.............................................................................................................................3
4.Functional Requirements ...........................................................................................................3
4.1.Library Information.............................................................................................................................3
4.2.Canteen Information............................................................................................................................4
4.3.Fee-Related Transaction Problem .......................................................................................................4
5.Non-Functional Requirements...................................................................................................4
5.1.Usability ..............................................................................................................................................4
5.2.Performance ........................................................................................................................................4
5.3.Security ...............................................................................................................................................4
5.4.Compatibility.......................................................................................................................................4
5.5.Scalability............................................................................................................................................4
6.Hardware Components ..............................................................................................................5
6.1.Server Infrastructure............................................................................................................................5
6.2.End-User Devices................................................................................................................................5
6.3.Security Hardware...............................................................................................................................6
7.User Interface ..............................................................................................................................6
7.1.Library Information:............................................................................................................................6
7.2.Canteen Information: ..........................................................................................................................7
7.3.Fee-Related Transaction Problem Solution.........................................................................................7
7.4.Overall Design Principles ...................................................................................................................8
8.High-Level System Architecture................................................................................................8
8.1.Client-Side Architecture......................................................................................................................8
8.2.Server-Side Architecture .....................................................................................................................8
8.3.Component Interaction........................................................................................................................9
8.4.Security Measures ...............................................................................................................................9
8.5.Environmental Requirements............................................................................................................10
9.Testing ........................................................................................................................................10
9.1.Test Scenarios....................................................................................................................................10
9.2.Test Cases ..........................................................................................................................................11
10.Maintenance and Support ......................................................................................................11
10.1.Maintenance ....................................................................................................................................11
10.2.Support ............................................................................................................................................12
SRS for Jamia Hamdard Application Page 1

1.Introduction

1.1.Purpose

The purpose of this Software Requirement Specification (SRS) document is to outline the features and
requirements of the Jamia Hamdard University Application. The aim is to enhance user engagement, provide
easy access to information, and optimise functionality for a diverse user base.

1.2. Project scope

This SRS covers the development of new features related to library information, canteen information, and
fee-related transaction problem solutions within the Jamia Hamdard University Application.

1.3. Document Conventions

• N/A: Not Applicable

• TBD: To Be Determined

1.4. References

http://jamiahamdard.edu/

2. System Overview

2.1. Current System

The current Jamia Hamdard University Application provides basic information about the university, its
courses, and academic calendar.

2.2. Proposed System

The proposed system will include the following new features to enhance user engagement and access to
information:
- Library Information: Provides real-time updates on book availability, borrowing status, and research
resources.
- Canteen Information: Offers menu updates, operating hours, and user reviews for the on-campus
canteens.
- Fee-Related Transaction Problem Solution: Provides a platform for students to resolve fee-related
issues, view transaction history, and make payments.
SRS for Jamia Hamdard Application Page 2

2.3.Target Audience

The application is designed for use by students, faculty, and staff of Jamia Hamdard University, as well as
prospective students and visitors.
 SRS for Jamia Hamdard Application Page 3

3. System Features

3.1.Canteen Information

The Canteen Information feature will enable users to:

- View menus and prices for on-campus canteens.
- Check operating hours and locations.
- Read and submit reviews of canteen services.
- Receive noti cations about special offers and promotions.

3.2. Fee-Related Transaction Problem Solution

The Fee-Related Transaction Problem Solution feature will allow users to:
- View their transaction history.
- Request support for fee-related issues.
- Make fee payments securely.
- Receive reminders for payment deadlines.

3.3. Library Information

The Library Information feature will allow users to:

- Browse the library catalog.
- Check the availability of books and their locations.
- View their current borrowed items and due dates.
- Receive noti cations for overdue items.
- Access research resources and digital libraries.

4. Functional Requirements

4.1. Library Information

- User Authentication: Users must log in with their university credentials to access library information.
- Catalog Search: Users can search the library catalog by title, author, or subject.
- Availability Check: Users can check the availability of books and their due dates.
- Borrowing and Renewal: Users can borrow and renew books online.
- Overdue Noti cations: The system will send overdue noti cations to users.
fi
fi
fi
fi
SRS for Jamia Hamdard Application Page 4

- Resource Access: Users can access digital libraries, research papers, and other resources.

4.2. Canteen Information

- Canteen Listings: The system will list all on-campus canteens, including menus, prices, and operating
hours.
- User Reviews: Users can read and submit reviews for canteens.
- Special Offers: Users will receive noti cations about special offers and promotions.

4.3. Fee-Related Transaction Problem

- Transaction History: Users can view their transaction history related to fees.
- Support Requests: Users can raise support tickets for fee-related issues.
- Fee Payments: Users can make secure fee payments through the application.

5. Non-Functional Requirements

5.1. Usability

- The application must have an intuitive and user-friendly interface.

- Response times for queries and actions should be fast to ensure a smooth user experience.>

5.2. Performance

- The system should be able to handle a large number of concurrent users.

- Response times should be within acceptable limits, even during peak usage.

5.3. Security

- User data, including login credentials and transaction details, must be securely stored and transmitted.
- The application should implement appropriate security measures to protect against unauthorised access.

5.4. Compatibility

The application should be compatible with various devices and browsers to ensure accessibility for all users.

5.5. Scalability

The system should be easily scalable to accommodate future feature expansions and increased user demand.
fi
SRS for Jamia Hamdard Application Page 5

6. Hardware Components

6.1. Server Infrastructure

The server infrastructure is responsible for hosting the application, databases, and associated services. The
following hardware components are necessary:

Web Server:
- High-performance web servers capable of handling concurrent user requests.
- Recommended hardware: Dual-core or quad-core processors, 16GB RAM, SSD storage.

Database Server:
- A dedicated database server to manage application data.
- Recommended hardware: Multi-core processors, 32GB RAM, and RAID-con gured hard drives for data
redundancy.

Load Balancer (for scalability):

- Load balancers distribute incoming network traf c across multiple web servers to ensure high availability
and distribute the load.
- Recommended hardware: Specialised load balancing appliances or software running on high-end servers.

Backup and Recovery System:

Hardware components for data backup and recovery, including backup storage devices, tape libraries, and
off-site storage solutions.

6.2. End-User Devices

The application should be accessible from various end-user devices, and thus should be compatible with a
wide range of hardware components:

Desktops and Laptops: Users accessing the application from desktops and laptops should have modern
hardware to ensure a smooth experience. This includes CPU, RAM, and suf cient storage space.

Mobile Devices: The application should be optimised for mobile devices, including smartphones and tablets.
Compatibility with both iOS and Android devices is essential.
fi
fi
fi
SRS for Jamia Hamdard Application Page 6

Network Infrastructure: Users should have access to a stable internet connection to access the application
effectively. The application should be designed to perform well even with low bandwidth connections.

Printers and Scanners: If the application involves printing or scanning documents, ensure compatibility
with various models and brands of printers and scanners commonly used within the university.

6.3. Security Hardware

Security hardware components are crucial to protect user data and application integrity:

Firewalls:
- Firewalls to protect the application from unauthorised access and potential threats.
- Intrusion detection and prevention systems (IDS/IPS) can also be used.

Security Tokens and Two-Factor Authentication (2FA) Devices:

If the application requires enhanced user authentication, hardware tokens or 2FA devices should be
supported.

Secure Sockets Layer (SSL) Certi cates:

Hardware security modules (HSMs) to store and manage SSL certi cates for secure data transmission.

7. User Interface

7.1. Library Information:

Home Screen: Upon launching the app, users are greeted with a clean and welcoming home screen. It
displays key navigation options to access library-related features.

Catalog Search: Users can easily search for books, research papers, and digital resources using a search bar.
Autocomplete suggestions and advanced lters make searching ef cient.

Book Availability: When a user selects a book, they can view its availability status, location in the library,
and due dates if checked out.

Borrowing and Renewal: Users can check out books directly from the app with a simple click. Renewal
options are easily accessible.
fi
fi
fi
fi
 SRS for Jamia Hamdard Application Page 7

Noti cations: The app sends push noti cations to alert users about due dates, overdue items, and library
announcements.

7.2. Canteen Information:

Canteen Listings: The canteen feature provides an organised list of all on-campus canteens. Each listing
displays the canteen's name and a thumbnail image.

Menu Exploration: Users can explore the menu of each canteen. A clean layout with images, descriptions,
and prices makes it easy to make choices.

Operating Hours: Users can check the canteen's operating hours, ensuring they don't miss a meal.

User Reviews: The app allows users to read and submit reviews. Ratings, comments, and user-generated
images provide valuable insights into the canteen experience.

Special Offers: Special promotions and offers are highlighted with eye-catching banners and timely
noti cations.

7.3. Fee-Related Transaction Problem Solution

Transaction History: Users can view a comprehensive history of their fee-related transactions. Each
transaction entry provides details such as date, amount, and description.

Support Requests: A dedicated section allows users to submit support requests related to fee issues. They
can describe the problem, attach documents, and receive case numbers for tracking.

Fee Payments: Users can make secure fee payments directly through the app. Payment options include
various methods like credit cards, bank transfers, or digital wallets.

Payment Reminders: The application sends reminders for upcoming payment deadlines, helping users stay
on top of their nancial obligations.

Secure Authentication: Secure login and authentication processes are integrated into the UI, ensuring the
protection of nancial and personal data.
fi
fi
fi
fi
fi
SRS for Jamia Hamdard Application Page 8

7.4. Overall Design Principles

Consistency: The UI maintains a consistent design theme, colour scheme, and typography throughout the
application.
Responsive Design: The app is responsive, adapting to various screen sizes and orientations for both mobile
and desktop users.
Intuitive Navigation: The navigation is user-friendly, with clear menu options, buttons, and a
straightforward hierarchy.
Accessibility: The design considers accessibility standards, making it usable for all users, including those
with disabilities.
Feedback: Users receive immediate feedback for actions taken within the app, ensuring a responsive and
interactive experience.
User Personalization: Users may customise their pro les, preferences, and settings to personalise their
experience.
User Assistance: The application provides tooltips, guides, and onboarding for new users to help them
become acquainted with the app.

8. High-Level System Architecture

8.1.Client-Side Architecture

The client-side architecture, responsible for rendering the application's user interface, primarily consists of:
• Mobile and Desktop Applications: Native or cross-platform applications (iOS, Android, Web) that
allow users to interact with the application from their devices.
• User Interface (UI): The UI layer, where the graphical user interface is designed to provide an
intuitive and visually appealing user experience.
• User Authentication: Secure user authentication mechanisms to ensure user data protection.

8.2.Server-Side Architecture

Web Server
- The web server handles HTTP requests from clients, serving as an intermediary between the client-side and
the server-side.
- It includes the application's business logic and data processing components.
fi
SRS for Jamia Hamdard Application Page 9

Database Server
- The database server stores and manages data related to library information, canteen information, and fee
transactions.
- It includes the database management system, which can be a relational database like MySQL or
PostgreSQL.

Application Logic
- This component manages the core application logic, including handling user requests, processing data, and
managing user sessions.
- It communicates with the database server to retrieve and update data.

Load Balancer (For Scalability)

- In cases of high traf c or the need for scalability, a load balancer may distribute incoming requests across
multiple web servers for load distribution.

8.3.Component Interaction

Client-Server Interaction:
- Clients (mobile and web applications) send HTTP requests to the web server.
- The web server processes these requests and communicates with the application logic and the database
server.
- It sends responses back to the client with the requested information.

Database Interaction:
- The application logic communicates with the database server to retrieve and store data.
- Data such as book availability, canteen listings, transaction records, and user pro les are managed in the
database.

Load Balancer (For Scalability):

- If there is a load balancer, it distributes client requests across multiple web servers to ensure optimal
performance during high traf c periods.

8.4. Security Measures

- Firewalls: Security rewalls are in place to protect the system from unauthorised access and potential
threats.
fi
fi
fi
fi
SRS for Jamia Hamdard Application Page 10

- Data Encryption: Sensitive user data, such as login credentials and transaction details, is encrypted to
ensure secure storage and transmission.
- User Access Control: User authentication and access control mechanisms are implemented to restrict
unauthorised access to certain system functions.
- Secure Sockets Layer (SSL): SSL certi cates are used to secure data transmission between clients and the
server, with the potential use of hardware security modules (HSMs) to manage SSL certi cates securely.

8.5. Environmental Requirements

The server infrastructure should be housed in a controlled environment with considerations for
power backup, temperature control, and physical security. Data centre facilities or hosting providers
should adhere to industry best practices for environmental control.

9.Testing

9.1.Test Scenarios

Library Information Feature:

1. Catalog Search Test: Verify that users can search for books and resources effectively.
2. Book Availability Test: Check if users can view the availability status of books.
3. Borrowing and Renewal Test: Ensure users can borrow and renew books without errors.
4. Notifications Test: Confirm that users receive due date and overdue item notifications as expected.

Canteen Information Feature:

1. Menu Exploration Test: Verify users can explore canteen menus and make selections.
2. Operating Hours Test: Ensure users can access accurate information about canteen operating hours.
3. User Reviews Test: Confirm that users can submit and read canteen reviews.
4. Special Offers Test: Check if users receive special offer notifications on time.

Fee-Related Transaction Problem Solution Feature:

1. Transaction History Test: Verify the accuracy of transaction history displayed to users.
2. Support Requests Test: Confirm that users can submit support requests with proper case tracking.
3. Fee Payments Test: Ensure that fee payments can be made securely through the app.
4. Payment Reminders Test: Check if users receive reminders for upcoming payment deadlines.
fi
fi
SRS for Jamia Hamdard Application Page 11

9.2.Test Cases

For each test scenario, define specific test cases that provide step-by-step instructions on how to conduct the
tests. These test cases should include the following elements:
- Test Case ID: A unique identifier for the test case.
- Test Case Title: A descriptive title summarising what the test case is meant to accomplish.
- Preconditions: Conditions that must be met before the test can be conducted.
- Test Steps: Detailed step-by-step instructions on how to perform the test.
- Expected Results: The expected outcomes or behaviours when the test is executed.
- Actual Results: The actual outcomes observed during testing.

Test Steps:
- Launch the application.
- Navigate to the Library Information feature.
- In the search bar, type "Computer Science."
- Click the "Search" button.
- Review the search results.
Expected Results: The search returns a list of books and resources related to "Computer Science." The list is
accurate and relevant to the search query.
Actual Results: The search results displayed relevant books and resources related to "Computer Science."
The test case passes.

10. Maintenance and Support

10.1.Maintenance

Maintenance activities are essential to address bugs, enhance features, and keep the application running
smoothly. The maintenance plan includes the following components:

Corrective Maintenance:
- Addressing and fixing software defects, errors, and issues as they are reported or identified through testing.
- Promptly resolving critical issues that affect the application's functionality or security.
Adaptive Maintenance:
- Adapting the application to accommodate changes in the operating environment, such as updates to
operating systems or databases.
- Ensuring that the application remains compatible with new devices, browsers, and platforms.
Perfective Maintenance:
- Enhancing existing features and improving the user experience based on user feedback and evolving needs.
SRS for Jamia Hamdard Application Page 12

- Optimising performance, usability, and responsiveness.

Preventive Maintenance:
- Proactively identifying and addressing potential issues to prevent future software failures or security
vulnerabilities.
- Regularly applying security patches and updates to maintain data and system security.

10.2. Support

User support is an integral part of ensuring a positive user experience. The support plan includes the
following components:

User Help Desk:

- Maintaining a dedicated help desk or support team to address user queries, issues, and technical assistance.
- Providing users with a reliable point of contact for reporting problems and seeking help.

User Training and Documentation:

- Offering user training sessions or creating documentation to help users understand and use the application
effectively.
- Providing guides, FAQs, and knowledge base articles to address common user questions.

Issue Tracking and Resolution:

- Implementing a ticketing system for tracking and prioritising user-reported issues.
- Ensuring timely resolution of user-reported problems and regular communication with users about issue
status.

Feedback Collection:
- Continuously collecting user feedback to identify areas for improvement and feature requests.
- Encouraging users to provide feedback through surveys, in-app feedback forms, and user community
forums.

Updates and Feature Releases:

- Planning and executing updates and feature releases in response to user feedback and evolving
requirements.
- Communicating updates to users through release notes and announcements.

Data Backup and Recovery:

- Regularly backing up application data and implementing data recovery procedures to prevent data loss in
case of failures.