SRS Mess Management

MESS MANAGEMENT SYSTEM
Introduction
● Purpose:
The purpose of this document is to provide a detailed description of the Mess
Management System. It outlines the requirements, features, and functionality
expected from the system.
● Scope:
The Mess Management System aims to streamline and automate various
aspects of managing a mess in an educational institution. It includes features
such as upcoming mess meeting details, current active members, responsible
faculty in charge, QR-based complaint registration, mess menu displaying, mess
timings, total staff in mess, and relevant contacts for problem resolution.
Overall Description
Product Framework:
The Mess Management System is a comprehensive platform serving the entire campus
community, including all students, mess committee and faculty in charge of mess. This
system is designed to facilitate efficient communication, streamline operations, and
enhance the overall dining experience for everyone involved. It will interact with user
interfaces for both administrators and end-users.
Product Features
● QR-Based Complaint Registration:
Allow users to register complaints by scanning QR codes placed in the mess.
Include details such as complaint type, description, and date.
● Mess Menu Displaying:

Show the daily or weekly mess menu to the users, including breakfast, lunch,
and dinner. It also displays if there is any modification on the current day.
● Status of Complaints: Users can track their complaint status via a unique
reference number.
● Concerned Authority for Problems:
Display contact information for the relevant authority to address any issues or
concerns related to the mess.
User Classes and Characteristics:

● Administrator (Faculty-in-Charge): Responsible for managing meeting details,
member information, and system settings.
● Mess Committee Member: Access to meeting details and mess-related issues.
● End User (Students): Access to mess menu, timings, and complaint registration.
Functional Requirements
User Management
● User Registration and Authentication:
Allow users to register with the system.
Authenticate users securely for system access.
● Role-based Access Control:

Implement role-based access to ensure appropriate permissions for
administrator, mess committee members, and end-users.
Mess Meeting Management

● Upcoming Mess Meeting Details:
Display information about the date, time, and agenda of upcoming mess
committee meetings.
● Responsible Faculty In Charge:

Identify and display the faculty member in charge of overseeing mess
management.
Complaint Handling
● QR-Based Complaint Registration:
Allow users to register complaints by scanning QR codes in the mess. Include
details such as complaint type, description, and date. Provide a confirmation of
complaint registration.
Mess Information Display
● Mess Menu Displaying:
Show the daily or weekly mess menu to the users, including breakfast, lunch,
and dinner.
● Mess Timings:
Clearly state the operational timings of the mess for each meal.
Display contact information for the relevant authority to address any issues or
concerns related to the mess.
System Administration
● System Configuration and Settings:
Allow administrators to configure system settings.
Provide options for customizing mess-related parameters.
● Log and Audit Trails:

Maintain detailed logs and audit trails for system activities.
Enable tracking and review of changes made to the system.
Non - Functional Requirements
● Performance:
The system should work fast and not make users wait. When you click on
something, it should happen quickly, like opening a mess menu or raising
complaints.
● Security:
The system needs to keep information safe. Only the right people should be able
to see and change things, like menu details or user data.
● Scalability:
The system should be able to handle more users and information without slowing
down or breaking. It should grow smoothly if more people start using it.
● Usability:
The system should be easy for everyone to use. Buttons and options should
make sense, and it shouldn't be confusing to find things like mess menu or
complaint history.
System Requirements
● Operating System:
The Mess Management System is compatible with Windows, macOS, and Linux.
● Web Browser:
Developers should use the latest versions of major browsers.
● Database Management System:

The system is built on MongoDB, serving as the primary database system.
● Frontend Development:
HTML, CSS, JavaScript, React.
● Server Requirements:
Node.js and Express.js are required components for the server-side
implementation, ensuring an efficient backend infrastructure.
● Programming Language:
JavaScript is the core programming language, with React.js utilized for the
frontend and Node.js for the backend development.
● Framework/Library Dependencies:
Developers should utilize npm packages for Express.js middleware and utility
libraries, ensuring efficient development practices.
● Security Protocols:
HTTPS must be implemented for secure data transmission.
● Authentication Mechanism:
User authentication is implemented using JWT (JSON Web Token) or Google
Auth.
Constraints:
● Capacity limit of database.
● Varying internet speeds and connectivity issues in different regions may affect
the user experience.
Future Implementation:
● Transaction Integration:
Integrate a secure transaction system to facilitate payments within the Mess
Management System. This feature would enable users to seamlessly make
transactions for meal orders in normal mess or night canteen through the
platform.
● Automated Notifications:
Implement a notification system to alert users about upcoming events,
announcements, and important updates by the mess committee.
● Feedback Form/Food Review:

Introduce a comprehensive feedback form and food review system within the
Mess Management System. This feature allows users to provide detailed
feedback on their dining experiences, including dining cleanliness, meal
satisfaction, menu suggestions, mess hygiene, and overall service quality.

SRS Mess Management

Uploaded by

Copyright:

Available Formats

SRS Mess Management

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 Mess Management

Uploaded by

Copyright:

Available Formats

MESS MANAGEMENT SYSTEM

● Mess Menu Displaying:

User Classes and Characteristics:

● Mess Committee Member: Access to meeting details and mess-related issues.

● Role-based Access Control:

Mess Meeting Management

● Responsible Faculty In Charge:

● Log and Audit Trails:

Non - Functional Requirements

● Database Management System:

● Feedback Form/Food Review:

You might also like