Software Requirements

Specification
for

COLLEGE ASSOCIATION
MANAGEMENT SYSTEM

Version 1.0 approved

Prepared by <Kushal\1032222230>
<Gulshan\1032221889>
<Akash\1032222240>
<Shivalika\1032222188>
<Manas\1032222281>

<MIT-WPU>

<28/08/2023>
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 System Feature 1 4
4.2 System Feature 2 (and so on) 4
5. Other Nonfunctional Requirements 4
5.1 Performance Requirements 4
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5
5.5 Business Rules 5
6. Other Requirements 5
Appendix A: Glossary 5
Appendix B: Analysis Models 5
Appendix C: To Be Determined List 6
Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 Purpose
The purpose of the CAMS is to provide a comprehensive software solution that simplifies the management of
college associations' activities. This document serves as a blueprint for the system's development, ensuring
that all stakeholders have a clear understanding of the system's functionality, requirements, and constraints.

1.2 Document Conventions

CAMS: College Association Management System
IEEE: Institute of Electrical and Electronics Engineers
SRS: Software Requirements Specification

1.3 Intended Audience and Reading Suggestions

The SRS document is intended to be a comprehensive reference for various stakeholders involved in the
development, implementation, and utilization of the College Association Management System (CAMS). The
primary audience includes:
● Development Team: Software engineers, programmers, designers, and other technical
personnel responsible for developing and implementing the CAMS.
● Project Managers: Individuals responsible for overseeing the project's progress, ensuring that it
adheres to requirements, timelines, and budget.
● Quality Assurance Team: Testing and quality assurance professionals responsible for
verifying that the system meets specified requirements and performs as intended.
● College Administrators: Officials responsible for managing college associations, events,
memberships, and related activities.

1.4 Product Scope

The CAMS will include modules for membership management, event planning, communication, document
sharing, financial tracking, and reporting. It will provide an intuitive user interface for both administrators and
members, fostering engagement and streamlining operations within college associations.

1.5 References
● IEEE Std 830-1998, "IEEE Recommended Practice for Software Requirements
Specifications."
● IEEE Std 1016-2009, "IEEE Recommended Practice for Software Design Descriptions."
 ● ISO/IEC/IEEE 29148:2018, "Systems and Software Engineering - Life Cycle Processes -
Requirements Engineering."

2. Overall Description
2.1 Product Perspective
The College Admin Chaos project aims to create a standalone college management system that integrates
student, faculty, and administrative processes into a cohesive platform. The College Association System is an
independent web-based application that operates within the college's IT infrastructure. It interacts with the
college's database system for user authentication and integrates with external social media platforms for event
promotion. The system is designed to streamline administrative tasks and enhance student engagement in
campus activities.

2.2 Product Functions

The system shall allow users to create and manage profiles, which will be used for authentication and
personalized interactions within the system. Users can register with their college email addresses.Users can
log in using their credentials.Users can update their profiles, including personal information and profile
pictures.Users can reset their passwords through a secure process

2.3 User Classes and Characteristics

Students: They engage in associations, register for events, and participate in discussions. Faculty
Members: They might lead or participate in associations, and they require access to association-
related information.
Administrators: They manage association creation, monitor activities, and generate reports. Guests:
They can view basic association information without logging in.>

2.4 Operating Environment

The system is designed to operate on common web browsers such as Chrome, Firefox, and Edge. It requires a
stable internet connection. The back-end of the system interacts with the college's existing database system for
user authentication.

2.5 Design and Implementation Constraints

The system should be designed with a user-friendly interface, prioritizing ease of use and
navigation. Security measures should be in place to protect user data and prevent unauthorized
access. The system must adhere to data privacy regulations and accessibility guidelines.
2.6 User Documentation
The system should provide user documentation, including guides for students, faculty members,
administrators, and event organizers. This documentation should cover registration, event creation,
resource sharing, and reporting. Comprehensive user manuals and tutorials will be provided.

2.7 Assumptions and Dependencies

Assumptions
● User Hardware and Connectivity: It is assumed that users accessing the College Association System
have access to compatible hardware (computers, smartphones, tablets) and a stable internet
connection.
● User Proficiency: Users are assumed to have a basic understanding of using web-based
applications and are capable of navigating through different interface elements.
● System Compatibility: It is assumed that the system will be compatible with standard web
browsers such as Chrome, Firefox, and Edge, with no major compatibility issues.

Dependencies
● Database System: The College Association System relies on the college's existing user database
system for user authentication. Any changes or updates to the database structure or access
mechanisms may affect the functionality of the system.
● External APIs: Integration with social media platforms for event promotion depends on the
availability and functionality of the respective social media APIs. Any changes to these APIs may
require adjustments to the system.
● Hosting Environment: The system's hosting environment should provide the necessary resources
(e.g., server space, bandwidth, security protocols) to ensure its proper functioning and accessibility.

3. External Interface Requirements

3.1 User Interfaces
The user interfaces of the College Association Management System are designed to provide a user-
friendly and intuitive experience for administrators, association members, and other
stakeholders. These interfaces include login screens, dashboards, profile management pages, event
registration forms, and communication tools. The user interfaces are crafted to simplify tasks, facilitate
engagement, and enhance collaboration within the association.

3.2 Hardware Interfaces

The College Association Management System is designed to be accessible through standard hardware devices,
such as desktop computers, laptops, tablets, and smartphones. Users can engage with the system using familiar
input devices such as keyboards, mice, and touchscreens. This compatibility ensures that users can access the
system's functionalities seamlessly from a variety of devices.

3.3 Software Interfaces

The system interfaces with software components to enable various functionalities. It interacts with web
browsers, allowing users to navigate and interact with the system's features. Additionally, the system
integrates with the college's existing databases to access member information, event details, and other relevant
data. The integration ensures that the system has accurate and up-to-date information for effective
management.

3.4 Communications Interfaces

Communication interfaces are essential for the College Association Management System to facilitate interactions
between users and the system. The system employs HTTP/HTTPS protocols to communicate with users' web
browsers securely. RESTful APIs enable integration with external systems, such as email services for sending
notifications and announcements to association
members. Authentication and authorization interfaces ensure secure access to system features and protect
sensitive data.

4. System Features
4.1 Streamlined Communication
4.1.1 Description and Priority
With the college management system, communication between students, faculty, and
administration becomes seamless. Stay connected through announcements,
notifications, and messaging, enhancing overall coordination.
4.1.2 Stimulus/Response Sequences
It leads to faster decision-making, reduced miscommunication, and a more connected
campus community. Additionally, streamlined communication fosters a more
transparent and collaborative environment, allowing stakeholders to work together
seamlessly towards common goals.
4.1.3 Functional Requirements:
REQ-1: Real Time Messaging:

The system should enable real-time messaging between students, faculty, and
administrators, allowing for instant communication and updates.

REQ-2: Announcement and Notifications:

The ability to create and broadcast announcements and notifications to specific groups
or the entire campus community, ensuring important information reaches the intended
recipients promptly.

REQ-3: Customized Communication Channels:

The system should support various communication channels such as text messages,
emails, in-app notifications, and social media integration, catering to the preferences of
different users.

REQ-4: Mobile Accessibility:

Ensuring that the communication features are accessible through mobile devices,
allowing users to stay informed even when they are on the go.
 REQ-5: Multi-Language Support:

Offering multi-language capabilities to accommodate diverse language preferences

within the campus community.

4.2 Time and Resource Saving

4.2.1 Description and Priority

This system optimizes tasks that used to take significant time and resources.
Automate processes like class scheduling, attendance tracking, and report generation,
freeing up staff to focus on more important tasks.

4.2.2 Stimulus/Response Sequences

Automated processes such as class scheduling, attendance tracking, and report

generation lead to quicker completion of tasks, reducing turnaround times and
enhancing overall operational speed.

4.2.3 Functional Requirements

REQ-1: Automated Class Scheduling:

Develop a module that automates the creation and management of class schedules,
considering faculty availability, room availability, and student preferences.

REQ-2: Attendance Tracking System:

Implement an automated attendance tracking system that records student attendance

and generates reports, reducing the need for manual attendance taking.

REQ-3: Online Registration and Enrollment:

Create an online registration and enrollment process that allows students to register
for courses, pay fees, and submit necessary documents digitally, reducing paperwork
and long queues.

REQ-4: Task Automation:

Incorporate workflow automation to streamline administrative tasks, such as sending reminders,

processing forms, and updating records, saving time and minimizing errors.

REQ-5: Self-Service Portals:

Create self-service portals for students to access course materials, check grades, and view their
academic progress, reducing the need for manual inquiries.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
● The system shall load the dashboard within 3 seconds for 90% of users
accessing the system under normal load conditions.
● Event registration shall be completed within 5 seconds for up to 200
simultaneous users.
● Search queries for events and member profiles shall provide results within 2
seconds.

5.2 Safety Requirements

● The system shall have automated data backups conducted daily, and a
recovery plan in place to restore the system in case of data loss.
● The system shall not cause harm or compromise the integrity of user devices or data.

5.3 Security Requirements

● User passwords shall be stored using strong encryption algorithms.
● Access to sensitive functions (event creation, user management) shall be
restricted to authorized administrators through role-based access controls.
● Personal data transmission shall be secured using HTTPS.

5.4 Software Quality Attributes

● The system shall undergo thorough testing, including unit testing, integration
testing, and user acceptance testing, to ensure functionality and quality.
● Code reviews and quality assurance processes shall be conducted to maintain a high
standard of software quality.
5.5 Business Rules
● Users can belong to multiple associations but can only be an administrator of one
association.
● Only event organizers and administrators can modify event details and attendee lists.
● Members can cancel event registration up to 24 hours before the event.
● Notifications shall be sent to members for upcoming events and
announcements.

6. DATA FLOW DIAGRAM

LEVEL 0:
LEVEL 1:
LEVEL 2:
7. USE CASE DIAGRAM
8. CLASS DIAGRAM
9. OBJECT DIAGRAM
10. ACTIVITY DIAGRAM
11. SEQUENCE DIAGRAM
12. TIMING DIAGRAM
13. COMMUNICATION DIAGRAM
14. STATE MACHINE DIAGRAM
 15. GANTT CHART

For better image quality of gantt chart you can vist: https://drive.google.com/file/d/1EZGj0m1i6FT_ubQLi6wPoJMe9qViA_hD/view?
usp=drive_link
16. BLACKBOX AUTOMATION TESTING - SELENIUM