Scribd
Upload
8 views4 pages

SE242__ProjectDesc__S3-MRS_v2

The document outlines the Smart Study Space Management and Reservation System (S3-MRS) at HCMUT, aimed at enhancing student learning experiences through efficient study space management using IoT technology. It details project guidelines, team collaboration, submission requirements, and evaluation criteria for the software engineering project. Students are expected to participate in all stages of development, from requirement specification to final demonstration, with a focus on quality and teamwork.

Uploaded by

xvjtfy947p
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views4 pages

SE242__ProjectDesc__S3-MRS_v2

The document outlines the Smart Study Space Management and Reservation System (S3-MRS) at HCMUT, aimed at enhancing student learning experiences through efficient study space management using IoT technology. It details project guidelines, team collaboration, submission requirements, and evaluation criteria for the software engineering project. Students are expected to participate in all stages of development, from requirement specification to final demonstration, with a focus on quality and teamwork.

Uploaded by

xvjtfy947p
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Engineering - 242 Project description Page 1/4

Smart Study Space Management and Reservation System at HCMUT


(S3-MRS)
In the context of a modern university, the demand for self-study, reasearch and group study
spaces among students is increasing. To meet this demand, the Ho Chi Minh City University
of Technology – VNU (HCMUT) has established Smart Study Spaces in various buildings on
campus. The goal is to enhance students' learning experiences by enabling them to easily
find and effectively use study spaces. At the same time, the system contributes to smart
resource management, optimizing the use of study spaces and equipment, and promoting
the modernization of the educational environment through the integration of IoT technology
and smart management solutions, creating a competitive advantage in education.
In addition to building modern self-study spaces, HCMUT is also implementing a Smart
Study Space Management and Reservation System. These spaces are designed to meet the
diverse learning needs of students, including individual study, group study, and one-on-one
mentoring sessions. Depending on the requirements, the self-study spaces will provide
essential equipment such as lighting, power outlets, projectors, whiteboards or interactive
screens, online meeting devices, air conditioning, etc.
Students can easily access the system via web and mobile apps to make flexible
reservations and receive reminder notifications when their study time is approaching or
when the status of the study spaces changes. The university management can monitor the
usage of each study space and gather reports on the system’s activities. IT staff will ensure
that the centralized authentication system operates smoothly and securely protects user
information, while the technical team will maintain the sensors and devices in the self-study
spaces.
The system will be developed on web and mobile app platforms, allowing users to easily
access it from anywhere and conveniently use services related to study spaces. User
authentication will be conducted through HCMUT’s centralized authentication system,
HCMUT_SSO, ensuring security and accurate access control.
Additionally, the system is required to integrate IoT technologies to support the criteria for
smart study spaces. Specifically, the system will monitor and update the status of each
study space (e.g., available/occupied) via state sensors. Students can use the app or scan
QR codes to check-in and unlock space. Devices such as lights and air conditioning will
automatically turn on when the room is in use, and the system will automatically release
spaces that are reserved but not used.

Note: Students can explore or assume the designs of the self-study spaces and use these
assumptions to create appropriate software designs.
Software Engineering - 242 Project description Page 2/4

Project guidelines

1. Team & teamwork


a. Teams are formed randomly by the lecturer.
b. Each team member has to perform all works, including requirement specification,
architectural design and detail design.
c. At the end of the semester, team members have to give feedback to each others and
evaluation the individual and team performace.

2. Team meeting & meeting minus


a. Team meetings should be carried out once a week
b. The first meeting should be focus on the team communication, commitment, common
problems/risks and solving mechanisms …
c. Meeting minutes are used to keep track of all works.

3. Submissions
a. There are 04 individual documents:
i. #1- requirement document: Functional/Non-Functional requirement and Use-case
diagram-scenario.
ii. #2- design document: Sequence/Activity or State-chart diagrams & UI design.
iii. #3-design document: Architectural design, Class and Method design, Class diagram.
iv. #4-finall document.
b. All submissions are in .doc/.docx/.pdf format.
c. Deadlines will be announced on the LMS site.

4. Demonstration

Develop MVP. Demonstrate the whole project.


You are free to choose the programming language (HTML, Javascript, Python, C#, etc). It is not
required to implement a database in the backend. Data can be hard coded in code files.
(a presentation slide shall be prepared. Each team should practice the demonstrations many times
in advance. The presentation should be straight to the point, contains lessons learned for the team.
The demonstration should be prepared, correct, brief and has good quality.)

Warning: The objective of the Project Assignment is to ensure that each team member fully
participates in all stages of the software development process, including general tasks such as
describing the system context, defining functional, and non-functional requirements, etc., as well
as specific tasks like describing use cases, drawing activity, sequence, and component diagrams,
and designing user interfaces. The outcomes must meet both Quality and Quantity standards.
Additionally, team members are responsible for evaluating each other's contributions.
Software Engineering - 242 Project description Page 3/4

Project Submission Detail

1. Submission #1 detail
Students have to submit the following contents:

- Project details specification:


Students are required to thoroughly describe the project context based on the basic information
provided. This includes clearly identifying the relevant stakeholders, understanding their roles and
expectations, and outlining the objectives and scope of the project. The goal is to ensure a
comprehensive understanding of the project’s context, its key players, and its boundaries.
- Functional requirements:
+ List all functional requirements of the system
+ Use-case diagram for the whole system
+ Use-case detail/scenario for use-case
+ Other non-interactive functional requirement (bonus)
- Non-functional requirements:
+ General non-functional requirements for the whole system

2. Submission #2 detail
Students have to submit the following contents:
- UI design: Mockup
- Sequence diagrams
- Activity diagrams
- State-chart diagrams (bonus)

3. Submission #3 detail
Students have to submit the following contents:
- Deployment view
- Development/Implementation view
- Class diagram and Method descriptions (for all methods in the class diagram).

4. Submission #final
Students have to submit the following contents by only 01 pdf file:
- All contents from (#1, #2, #3)
- A working demonstration (by sequence of screens)
And the source code (zip file)
Software Engineering - 242 Project description Page 4/4

Rubric
No Content %
1 Quiz 10%
2 Report (Final submission) 30%
3 Demonstrate (presentation) 10%
4 Final exam 50%

You might also like