MESS MANAGEMENT

SYSTEM

AUTHORS:
K PAVAN KUMAR - 23U41A0584
K GIRISH - 23U41A0587
B S G L N MURTHY - 23U41A0564
P SAMPREETH - 23U41A05A5
K G S THARUN - 23U41A0589
JNANESH - 23U41A0572
M MOHAN KRISHNA VIJAY - 23U41A05A8
TABLE OF CONTENTS
SUMMARY __________________________________________________________________________________ 2
SDLC ______________________________________________________________________________________ 2
USER AND SYSTEM REQUIREMENTS _____________________________________________________________ 3
FUNCTIONAL AND NONFUNCTIONAL REQUIREMENTS _______________________________________________ 4
CONTEXT DIAGRAM __________________________________________________________________________ 5
USE CASE DIAGRAM__________________________________________________________________________ 6
SEQUENCE DIAGRAMS _________________________________________________________________________7
CLASS DIAGRAM ____________________________________________________________________________ 10
PROCESS/STATE MODEL______________________________________________________________________ 11
CONCLUSION _______________________________________________________________________________ 12

TABLE OF FIGURES
Figure 1 Agile Method SDLC ___________________________________________________________________ 3
Figure 2 Context Diagram ____________________________________________________________________ 5
Figure 3: Use Case Diagram __________________________________________________________________ 6
Figure 4: Student Sequence Diagram ___________________________________________________________7
Figure 5: Admin Sequence Diagram ____________________________________________________________ 8
Figure 6: Mess Supervisor Sequence Diagram___________________________________________________ 9
Figure 7: Class Diagram______________________________________________________________________ 10
Figure 8: Process State Diagram ______________________________________________________________ 11

1
SUMMARY

To solve the mess management problem at the GIKI institute, the institute has contracted our business to
create a comprehensive mess management system. The system will be set up so that students can quickly
sign up, pay their bills online, pick the days they want to dine at the mess, and mess in or mess out
whenever they want. The students can schedule the days they wish to mess in or out, in addition to these
essential features, and they can also vote to alter the mess menu each month. The initial phase in the
software development process will be to gather requirements, comprehend user expectations, and
identify system constraints. Interviews, surveys, and other ways of getting customer feedback can be used
for this. It is crucial to specify the project's parameters and the functional and non-functional
requirements that the system must satisfy. We will use the Agile model once the requirements for the
mess management system have been gathered because it promotes flexibility and calls for ongoing
product improvement, which speeds up development and delivery. The system design process will come
once the SDLC model has been determined. To visualize the user interface and the system's underlying
architecture, diagrams and prototypes will need to be made. In conclusion, a thorough and organized
process of requirement collecting, selecting an acceptable SDLC model, designing and executing the
system, and deploying and maintaining the system will be required to construct the mess management
system for the GIKI institute. We can make sure the system is of good quality and satisfies the needs of
the users by taking a planned and methodical approach.

SDLC

It is crucial to choose a software development lifecycle (SDLC) model that is well-suited to the project's
needs and restrictions when creating the mess management system for the GIKI institute. We have
decided to use the Agile software development lifecycle approach for this project after extensive
deliberation. The Agile model is an incremental and iterative method for creating software that places a
focus on adaptability and cooperation between the stakeholders and the development team. The
development process is broken down into manageable chunks, or "sprints," in the Agile approach, during
which the team focuses on a defined set of tasks. Each sprint is followed by a review and feedback session,
during which the team discusses what has been accomplished and what needs to be done next. This allows
for frequent adjustments and adaptations to be made as the project progresses. The Agile model's
emphasis on continuous delivery and testing is one of its main advantages. Instead of waiting until the
conclusion of the project to release a finished system, the team now regularly produces and evaluates
smaller portions of the system. With this method, the team can receive input more quickly and make
changes and advancements as necessary. Overall, the Agile model's emphasis on flexibility and
cooperation, as well as its concentration on continuous delivery and testing, make it a good fit for the
mess management system project. These features will aid in ensuring that the system is timely supplied
and satisfies user requirements.

2
Figure 1 Agile Method SDLC

USER AND SYSTEM REQUIREMENTS

User requirements:
• Ease of use: The system should be easy to use for all students, regardless of their level of technical
expertise. This may involve designing a user-friendly interface and providing clear instructions for
how to use the system.
• Registration: Students should be able to easily register for the mess management system by
providing their personal and contact information. This may include their name, student ID, room
number, hostel number, email address, and phone number.
• Payment options: Students should be able to pay their bills online using a variety of payment
methods, such as credit cards, debit cards, and online payment platforms. The system should also
support offline payment options, such as cash and check payments.
• Mess options: Students should be able to choose the days they want to eat at the mess, as well
as whether they want to mess in or out anytime and allow the students to schedule the days they
want to mess in or out. The system should provide clear options for students to make these
selections, and it should allow students to change their choices as needed.

3
 • Mess menu: Students should be able to view the menu for the current week or upcoming weeks,
as well as any special meals or events that may be planned.
• Notifications: The system should provide students with timely notifications regarding their mess
status, payment due dates, and any other important information. These notifications may be sent
via email, text message, or in-app notifications.
• Security: The system should be secure to protect student data, such as their personal and financial
information. This may involve the use of secure servers and encryption, as well as regular security
audits and updates.
• Report generation: Students should be able to view and download reports of their mess usage
and payment history.

System requirements:
• Data storage: The system should be able to store and manage large volumes of data, including
student registration information, payment records, and mess selection data.
• Data security: The system should be secure to protect student data from unauthorized access or
tampering.
• Payment gateway: The system should integrate with a secure payment gateway to process online
payments.
• User interface: The system should have a user-friendly interface that is easy to navigate and use.
• Compatibility: The system should be compatible with a variety of devices, such as computers,
tablets, and smartphones.
• Performance: The system should have good performance to ensure a smooth user experience.
• Reliability: The system should be reliable and always available when needed.
• Maintenance: The system should be maintainable, with easy updates and upgrades as needed.

FUNCTIONAL AND NONFUNCTIONAL REQUIREMENTS

Functional requirements:
• Student registration: The system should allow students to create an account and provide their
personal and contact information.
• Bill payment: The system should allow students to pay their bills online using a secure payment
gateway.
• Mess selection: The system should allow students to choose the days they want to eat at the mess
and any special dietary requirements they may have.
• Mess in/out: The system should allow students to choose to mess in or out anytime and be able
to schedule the days of the week they want to keep the mess in or out.
• Reports: The system should generate reports on student attendance, billing, and other relevant
data.

4
Non-functional requirements:
• Security: The system should protect student data and financial information from unauthorized
access and ensure compliance with relevant regulations and laws.
• Reliability: The system should always be available and responsive to ensure that students can
access it when needed.
• Performance: The system should have good performance to ensure a smooth and efficient user
experience.
• Usability: The system should be easy to use for all students, with a clear and intuitive interface.
• Scalability: The system should be able to handle large volumes of data and transactions as the
number of students and transactions increases.
• Compatibility: The system should be compatible with a variety of devices, including computers,
tablets, and smartphones.

CONTEXT DIAGRAM

Figure 2 Context Diagram

5
USE CASE DIAGRAM

Figure 3: Use Case Diagram

6
SEQUENCE DIAGRAMS

Figure 4: Student Sequence Diagram

7
Figure 5: Admin Sequence Diagram

8
Figure 6: Mess Supervisor Sequence Diagram

9
CLASS DIAGRAM

Figure 7: Class Diagram

10
PROCESS/STATE MODEL

Figure 8: Process State Diagram

11
 CONCLUSION

In conclusion, GIKI’s mess management system has the potential to simplify the mess management
process and enhance the overall dining experience for students. Students can register, pay bills online,
select the days they want to eat at the mess, and choose whether to mess in or out at any moment using
the system. The project used an agile methodology for the software development lifecycle, beginning with
requirement gathering and high-level design generation. The installation of the numerous features and
functionalities mentioned above was part of the development phase. This was followed by extensive
testing to make sure the system was dependable and user-friendly. The software development lifecycle
for the project started with requirement gathering and high-level design generation, using an agile
methodology. The development phase included the implementation of the several features and
functionalities stated above. The system was then put through a rigorous testing process to ensure that it
was reliable and user-friendly.

12

View publication stats