Lesson 1: Application
1. As the system analyst of the group, what should Luzviminda do after performing
project planning activities?
After completing the project planning activities, Luzviminda should proceed to the
System Analysis phase. As the system analyst, she should start by gathering detailed
information from the users through interviews and observations. This will help her
understand the current enrollment process, identify user needs and prepare for defining
the system requirements.
2. Do you think the information that Luzviminda's group gathered in the project planning
activities is enough to start developing the system? Why?
No, the information gathered during the project planning is not yet enough to start
developing the system. Project planning only identifies the problem, scope and
objectives. System development should begin only after completing system analysis
where detailed functional and non-functional requirements are identified and validated
to ensure that the system meets the user needs.
APPLICATION
System Analysis Results
Activities
1. Gathered ● The current enrollment process is mostly manual
information and paper based.
● Students need to line up for registration and
document submission.
● Enrollment takes a long time due to manual
checking and approval.
● Staff manually encode student information,
which increases errors and delays.
● Students experience confusion due to lack of
real time enrollment status updates.
2. Define System Functional Requirements:
Requirements ● The system allows students to register online.
● The system allows students to submit required
enrollment documents online.
● The system generates enrollment confirmation
for students.
● The system allows staff to view, verify and
approve enrollment records.
● The system stores and updates student
enrollment data.
Non-functional Requirements:
Technical Requirement
● The system should be accessible on desktop
and mobile devices.
Usability Requirement
● The system should be easy to use and
user-friendly for students and staff.
Performance Requirement
● The system should process enrollment requests
within a reasonable time.
● The system should support multiple users
accessing it simultaneously.
Security Requirement
● Only authorized users should be allowed to
access the system.
● Students data should be protected and
accessible only to authorized personnel.
Reliability Requirement
● The system should handle invalid inputs properly
and display error messages.
● The system should ensure data accuracy and
consistency.
Lesson 2: Application
1. Enumerate the different potential users of your enrollment system and specify each of
their roles/operations in the system.
● Student – The main user. They log in to choose their subjects, enroll, check their
enrollment status, and print their registration form.
● Registrar/Enrollment Officer – The one who manages the enrollment. They approve or
reject student enrollments and keep student records updated.
● Cashier – Handles money matters. They compute the fees students need to pay and
record payments.
● Department Chair/Adviser – Reviews and approves the subjects chosen by students,
especially those with special cases.
● System Administrator – Takes care of the system itself. They create user accounts,
control who can access what, and make sure everything runs properly.
2. What do you think is the contribution of students and/or parents in the design and
overall model of your enrollment system?
Students and parents help the developers understand what the system should look like and how
it should work from a user's point of view. Since they are the ones who will actually use or be
affected by the system, their opinions matter a lot. For example, they can point out what
features they need, like being able to check enrollment status easily or see how much they need
to pay. Their input helps make the system easier to use and more helpful for everyone involved.
3. Once the enrollment system is finished developing, do you think the task of the
developer ends there? How does an automated system need to be maintained overtime?
Should it include only the software side or also the hardware aspect?
No, the developer's job does not stop once the system is done. The system still needs to be
looked after over time. On the software side, the team needs to fix problems that come up,
improve features, and keep the system secure. On the hardware side, the computers and
equipment running the system also need to be checked and maintained so the system keeps
working without interruption. Both sides are equally important — if one breaks down, the whole
system can stop working. So maintenance should cover both.