MIDTERM

1. Identify your target organization as well as its specific stakeholders.

a. Key people who will be affected by the project.
 Faculty
 Teacher
 Student
b. Project’s Sponsors
 School Principal
 Parents Teacher Association
c. The scope of the project will be limited only on the computerized enrollment
system and record keeping of the school. Focused in gathering relevant data
such as data of students, computation of necessary fees, handling of student
grades, preparing reports, and generate student’s credentials. The database
maintenance feature of the proposed system will focus on adding, and editing
students’ records, students’ grades, maintaining and managing table entries of
users and user’s log; and monitoring of the changes done by authorized users in
the system. Library management and inventory management will not be included
in the said project.
d. The solution, product, or service will be use by:
 Cashier - One who have processed the payments of the student’s ledger
and receive payments and issue receipts.
 Administrator - One who manage the whole system.
 Registrar – One who can input and validates grades of students and
generates report and student’s credentials
2. Identify each of the stakeholders’ problems and translate them to your system
requirements.
a. .
 Problem. Redundancy of information, unmanage statement of accounts
of the students. Slow enrollment process due to its manual activity.
 Solution
1. Cashier Module - This module will handle all the payments and
ledger of every student and will generate receipts.
2. Administrator Module - This module will maintain and
managing the table entries of every file; keeps the server up,
running, and secure; keeps track of the log; updates the database
and provides access to authorized users of the system.
3. Registrar Module - This module will validate all the inputted
grades of the student and generates reports and credentials
3. Methodology
a. Release Plan
 The client is having a hard time in terms of the process flow of their
school enrollment, especially in student data, validation, data security,
data storage, and process payments.
1. A user stated that since gathering student data is performed
manually, and it takes a lot of time for them to finish one input of
a student. Searching for info is complicated because redundancy
of information is too high, and they don't know what the updated
student data is. The programmers are planning to create a
verification process that verifies if the student already has a record
or not in the system. By having this kind of solution, a zero-
redundancy data in the enrollment system is rest assured and to
minimize the effort of the teacher-in-charge or the enrolling
officer in updating student’s record. Since it is automated, it will be
 80% faster than manual operation, it takes two weeks to integrate
to the system.
2. A user once said that data validation is getting more challenging,
especially at times when the data of the student is gathered at the
same time, it takes a lot of time to validate and makes the process
slower. The programmers are planning to have user friendly
monitoring of every student that can easily validates student
information especially the grades and it can also generate reports
that is fast, reliable and accurate. It takes four weeks to create the
automated validation process to the system.
3. The user’s way of securing the files of the student is very slow,
since all the files is being kept in a room the chance for having a
file lost is very high and very vulnerable for others. To make the
files more secure, the programmers are planning to create
database which stores the data digitally and more manageable.
Doing some querying to the system make easier to search a data
and to provide a database for student’s files so that the enrolling
officers would easily update records. By having database driven
system it saves up to 85% of paper works.
4. In terms of student payment, the user is having difficulties in
matching the data of the student and payment details. The
programmers are planning to have a module that handles all the
payment of every student and since there will be a database, the
information within the system flows trouble-free. it manages all
the connected data-entry of the student along with their payment
so that it can provide right payments for every enrollee.
b. Iteration Plan
 The client will be attending the meeting along with the project team for
every iteration that will be conducted and will be discussing also about
requirements for the projects.
1. Data Entities and Analyzation
 The programmers will interview the client to have a better
understanding of the enrollment process. Analyze all forms
that are being used in the enrollment process to have the
right entities for the system.
 Use right entities for verification process.
 Coding the gathered data.
 It takes two weeks to integrate to the system.
2. Validation and Data Visualization
 Conducting an interview for the validation process.
 Analyze the process of validation in order to come up with
a good solution for the process.
 Create a user-friendly interface for easy validation.
 Coding the gathered data.
 It takes three weeks to create the automated validation
process to the system.
3. Data storage and Security
 Conducting an interview for the database structure.
 Analyzing user/client story on how they manage their
student information.
 User’s verification for database entities and table
relationship.
 Create database structure.
 It takes three weeks to integrate to the system.
 4. Payment Details
 Conducting an interview for the payment process.
 Analyzing payment process to create a module that utilize
the payments of every enrollee.
 Create sample payment report for succeeding enrollee.
 User’s verification for the automated payment.
 It takes three weeks to integrate to the system.
c. Acceptance Test
 The user / client will decide whether the functionality of the user stories is
functional or not and if its correctly implemented.
1. Data entries and Analyzation
 First Iteration
a.Misunderstanding about how the system process
flow should be.
b.Erroneous entity naming conventions.
c. There is some data redundancy
 Second Iteration (accepted)
a.Correct process flow
b.Correct entity conventions
c. Redundancy fixed
2. Validation and Data Visualization
 First iteration
a.Too much input data to validate.
b.Excessive design.
c. Complicated reports.
 Second Iteration
a.Complicated process for validation
 Third Iteration (Accepted)
a.Corrected input validation
b.Minimalist design
c. Correct data for generating reports
3. Data storage and Security
 First Iteration
a.Complicated database structured
b.Erroneous database entities
 Second Iteration
a.Complicated database structured
b.Not normalized table
 Third Iteration
a.Complicated database structured
b.Not normalized table
 Fourth Iteration (Accepted)
a.Completed database structured
b.Normalized table
c. Appropriate database entities
4. Payment Details
 First Iteration
a.Complicated payment process
b.Too much data for payment report
c. Erroneous table relationship
d.Inaccurate payment report
 Second Iteration (Accepted)
a.Completed payment process
b.Appropriate data for payment report
 c. Correct table relationship
d.Detailed payment report
d. Stand – up Meeting
 A daily meeting is executed between the user/client and the project team
to discuss all requirement for the project. Our regular discussion is more
about how to improve the user experience in utilizing the system. We are
open for the user/client’s suggestion and future changes to the system so
that we can flexibly adapt.
e. Pair Programming
 Since the programmers are diligent to their work, they make sure that the
goals and target will not be delayed. The programmers are focusing to
the important part of the project, from major priority to least priority that
makes the work well organized. Using the power of two in one task will
give flexibility to the project that provide results to the user/client. Pair
programming gives less time from identifying the problem within the
project and it can also improve each other skills and have improve
communication to present the best idea for the project.
f. Unit Test
 We create a first unit testing for the user/client before the programmers
begin their main coding for the system is to make them decide what
would be the flow and design of the system. Using this kind of unit
testing makes the system more flexible from user/client desire changes. In
order to pass the unit testing we let them conclude the first testing that
will be followed by the programmers.
g. Code
 Programming Language
1. Front – End
 HTML
 CSS
 JavaScript
2. Back – End
 PHP
 Database Language
1. MySQL
4.
5. Functional Requirements
a. System can store student information
b. The user can monitor/modify student information
c. The data are safe and secured by the system
d. The user can generate payment receipts
e. The user can generate student reports
f. The user can input student grades

6. Technical Requirements

Hardware Requirements
Component Minimum Recommended
Intel® Core™ i3-9100F Intel® Core™ i5-9400F
Processor Processor 6M Cache, up to Processor 9M Cache, up to
4.20 GHz 4.10 GHz
Motherboard Gigabyte GA-H170M-D3H Gigabyte B365M AORUS Elite
Memory 4 GB DDR4 (3200Mhz) 8 GB DDR4(3200Mhz)
240GB SSD (OS), 2TB HDD 240GB M.2 (OS), 2TB HDD
Storage Device
(Storage) (Storage)
a. Processor: we recommend i5 – 9400f because of the high core and thread counts, and
because of the clock speed which is 4.10 GHz that is good for the system to run
smoothly.
b. Motherboard: we recommend Gigabyte brand known its durability compared to any
other motherboard and it has M.2 slots and PCIE slots.
c. Memory: we recommend 8GB DDR4 with clock speed of 3200Mhz that are good enough
to run the system smoothly.
d. Storage Device: we recommend 240GB M.2 because its faster than the typical SSD
storage. It has read and write speed of up to 3,500 M/bs which is good for OS storage
that will fasten the boot up of the server. 2TB HDD is enough for data storage of the
system.
 Software Requirements
Component Recommended
Operating System Windows 10 64 – bit
Apache HTTP Server Version 2.4.41
PHP Version 7 and up
MySQL Version 8 and up
PhpMyAdmin Version 4.9.1 and up
a. Operating System: we choose Windows 10 64 – bit because of stable and continuous
upgrade for better performance.
b. Apache Server: we choose Apache Server v2.4.41 because its stable and for http server
that powers online base system.
c. PHP: we choose PHP v7 and up because of the better code standard and faster
compared to lower version of PHP
d. MySQL: we choose MySQL because of the exceptional data security and protection.
e. PhpMyAdmin: we choose PhpMyAdmin because the default way of administering
MySQL and makes it easy to test the database structure and queries.