SOFTENGFINAL

Republic of the Philippines
BOHOL ISLAND STATE UNIVERSITY

Magsija, Balilihan, 6342, Bohol, Philippines
Office of Instruction
Balance I Integrity I Stewardship I Uprightness
College of Computing and Information Sciences

Computing and Information Sciences Department
1st Semester, A.Y. 2024 - 2025
IT 311
(Software Engineering)
GROUP 1
STUDENT ENROLLMENT SYSTEM
SUBMITTED BY:
Agad, Cristine
Avenido, John Kenith
Gulle, Mary Joanna May
Langamen, Jenet
Lamatan, Giovanni Fidel
BSIT 3A
SUBMITTED TO:
ENGR. CATHERINE LEAH GABO
F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 1 of 11

PROJECT PLAN
The aim of this project is to design and implement a user-friendly student enrollment system that
streamlines the registration process, enhances data accuracy, and improves administrative efficiency
in managing student records.
Scope:
Functionalities:
1. Student Registration: Allow new students to create accounts and submit required information (e.g.,
personal details, documents).
2. Course Enrollment: Enable students to select and enroll in courses based on availability.
3. Administrative Features: Facilitate record management for staff, such as approvals and updates.
4. Reporting: Generate real-time reports on enrollment statistics.
5. Notifications: Send automated updates to students regarding enrollment status.
Limitations:
1. The system will initially support only a specific institution or school.
2. Advanced analytics or integrations with external systems are not included.
3. Limited to web-based access in phase 1 (mobile optimization planned for future phases).
Methodology:
1. Requirements Gathering: Collaborate with stakeholders to define system requirements.
2. Design: Develop user interface prototypes and database schema.
3. Development: Follow agile principles for iterative coding, testing, and refinement.
4. Testing: Conduct unit, system, and user acceptance testing to ensure functionality and reliability.
5. Deployment: Launch the system and provide training for end-users.
6. Maintenance: Address post-launch issues and implement feedback-driven improvements.
Timeline:
1. Week 1: Requirements Gathering & Analysis
2. Week 2: System Design (UI, Database)
3. Weeks 3-6: Development Phase (Front-end, Back-end, Database Integration)
4. Week 7: Testing & Debugging
5. Week 8: Deployment & Training

GANTT CHART

SYSTEM REQUIREMENTS
1. Functional Requirements.
The system shall allow students to create, update, and delete their profiles.
The system shall enable students to view and update their course enrollments.
The system shall provide a student dashboard to display course status, grades, and schedules.
The system shall allow students to enroll in courses during the enrollment period.
The system shall check for course prerequisites before enrollment.
The system shall notify students of conflicts in their schedules.
The system shall allow administrators to create, update, and delete courses.
The system shall support viewing of available courses by category, instructor, or schedule.
The system shall maintain a maximum enrollment limit for each course and notify when the limit is
reached.
The system shall allow students to view and pay tuition fees.
The system shall support multiple payment methods (e.g., credit card, bank transfer, online wallets).
The system shall generate payment receipts for successful transactions.
The system shall generate reports for administrators showing enrollment statistics.
The system shall provide faculty members with class rosters and attendance lists.
The system shall allow students to download transcripts and grade reports.
The system shall require students, faculty, and administrators to log in using unique credentials.
The system shall implement role-based access control to restrict access to features based on user
type.
Non-Functional Requirements
The system shall support up to 1,000 concurrent users with no significant degradation in
performance.
Page load time for any action should not exceed 2 seconds under normal usage.
The system shall have a responsive user interface compatible with both desktop and mobile devices.
The system shall provide user-friendly error messages for invalid actions.
The system shall enforce data encryption for all sensitive information (e.g., passwords, payment
details).
The system shall implement two-factor authentication for administrators..
The system shall include a disaster recovery mechanism to restore functionality within 1 hour of
failure.
The system shall scale to support up to 10,000 users within a single institution without architectural
changes.
3. Domain Requirements
The system shall enforce institutional policies regarding credit limits, prerequisites, and course
grading.
The system shall accommodate different academic calendars (e.g., semester, trimester).
The system shall allow administrators to define enrollment start and end dates for each term.
The system shall automatically restrict changes to enrollment after the defined deadline.
The system shall allow faculty to post grades, course materials, and announcements.
Faculty shall be able to track student performance and attendance.

The system shall support multiple languages, including English, for user interfaces and
documentation.

DATA FLOW DIAGRAM

HIPO DIAGRAM

USE CASE DIAGRAM

CLASS DIAGRAM

SEQUENCE DIAGRAM


SOFTENGFINAL

Uploaded by

Copyright:

Available Formats

SOFTENGFINAL

Uploaded by

Document Information

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

SOFTENGFINAL

Uploaded by

Copyright:

Available Formats

Republic of the Philippines

BOHOL ISLAND STATE UNIVERSITY

College of Computing and Information Sciences

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 1 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 2 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 3 of 11

Faculty shall be able to track student performance and attendance.

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 5 of 11

DATA FLOW DIAGRAM

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 6 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 7 of 11

USE CASE DIAGRAM

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 8 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 9 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 10 of 11

F-AQA-INS-003 | Rev. 2 | 07/01/24 | Page 11 of 11

You might also like