Chapter 3

ST.
VINCENT COLLEGE OF CABUYAO

College of Information Technology
SVCC Complex Mamatid, City of Cabuyao, Laguna
Bachelor of Science in Information Technology

Chapter III
Research Methodology
3.1 Software Methodology
xxThis study made use of the project to design and create the operational,
testing, and evaluation procedure. As advancing the development process generally
tends to be less controlled and structured, the researchers used the Rapid Application
Development (RAD) process to outline their goals in requirements of a system for those
that provide higher flexibility design, productivity, and quality. The procedures used in
the entire study, titled Digital Marriage Registration System in St. John the Baptist
Parish Church, are presented in this chapter. These include gathering the important data,
organizing the data, and formulating the analysis.
Figure 3.1 Rapid Application Development Model
1
ST. VINCENT COLLEGE OF CABUYAO
3.1.1 The Process Steps
 Requirements Planning - The researchers' initial phase involves gathering all
the data and requirements that will be required to further the investigation. The
researchers used a survey questionnaire to identify the manual filing system
used in the office and the lack of a reminder to notify the people a day after the
request was made.
 User Design - The suggested system will be developed in the second phase,
along with an analysis of the user's needs and expectations. The administrators
and users provided the researchers with information about the system's intended
use and the researchers used that information to create the system.
 Construction - Coding the system itself is the third stage. The system's code
was created by the researchers based on functionalities that transform the
system's design into code, making it so that only administrators and students
may access it and use its various capabilities.
 Implementation - After the coding is finished, the deployment is the fourth
phase. In order to identify the system and ensure that it is error-free and
completely complies with the requirements, the researchers conducted the
system's implementation and testing in order to determine whether there are any
issues.
2
3.2 Project Design
3.2.1 Use Case Diagram
Figure 3.2 Use Case Diagram for the Users Account
The users account's use case diagram is shown in Figure 3.2. It shows how the
user account will enter the system, create an account, log in, and log out. The user will
also have access to the system's main feature, which displays the representations of the
registration form, view marriage application, and search.
3
Figure 3.3 Use Case Diagram for the Admin Account
In Figure 3.3 depicts the use case diagram for the admin account, which will use
the system to access and create accounts. The administrator will also be able to view
user accounts' registered marriage applications as well as new, verified, and rejected
user applications. Moreover, the administrator has the ability to report and search for
registered marriages.
4
3.3 Software Development
For planning and development tasks, the researchers used Sublime Text as a
platform source code editor. Sublime Text provides in-depth idea coverage.
3.4 Project Development
The following step by step process finished during the implementation of the
system.
3.4.1 Hardware Development
1. Made a system for Digital Marriage Registration System.
1.1 Made the Case Activity Diagram illustrated in Figure 3.2 and 3.3.
2. Server
2.1 Google Chrome
2.2 Version
5
3.4.2 System Development
1. Sublime Text and XAMPP Control Panel was used in the software
development to program and design the system.
2. The use case diagram shown in Figure 3.2 and Figure 3.3.
3. The flowchart diagram illustrated in Figure 3.4.
6
3.5
Flowchart
Figure 3.4 Flowchart Model for User
7

In Figure 3.4, the flowchart diagram model for user is illustrated above,
beginning from registration and log in. If the user wants to fill up the registration form.
After the marriage registration completion, the user can view and download the
certificate of marriage.
8
Figure 3.5 Flowchart Model for Admin
In Figure 3.5, the flowchart diagram model for admin is illustrated above,
beginning from log in. If the admin wants to check marriage application then view
marriage registration completion, the admin can edit the marriage application status
then will view the marriage application status is verified / rejected. The admin can
monitor again if there’s a new marriage application.
3.6 Activity Diagram
9
Figure 3.6 Activity Diagram for User and Admin Account
In Figure 3.6, the activity diagram for the registration account of the user
accounts and admin accounts is illustrated above, beginning from log in and submitting
it for validation then saved to the database of a system.
10
Figure 3.7 Activity Diagram of Marriage Registration for User Account
11

In Figure 3.7, the activity diagram of marriage registration for the user accounts
is illustrated above, beginning from logging in to the system, filling out registration
form for the marriage registration if the user wants to view their marriage application,
then proceed to verified marriage application then there they can see if their marriage
registration is verified or rejected, the user will wait for the update status until the
update of the admin. Once the marriage registration completion, the user can download
the certificate of marriage.
12
Figure 3.7 Activity Diagram of Marriage Registration for Admin Account
13

In Figure 3.7, the activity diagram for the admin’s marriage registration service
is illustrated above, beginning from logging in to the system, the admin will monitor if
they’re user registering marriage and select to verified or rejected until approval and
marriage registration service will also be made. Once the completion of a service, the
admin will monitor when anyone else register a marriage.
14

3.7 Hierarchy Diagram
Figure 3.9 Hierarchy Diagram
In Figure 3.9, the hierarchy diagram of the website system is illustrated above,
beginning from logging in, the user will access either the admin account or the user
account, for the admin account the user will access marriage registration, profile and
dashboard, then the user account the user will be access in functions for registration and
profile.
15

3.8 Gantt Chart for Implementation Plan
The system's installation plan is displayed in a Gantt chart. It is anticipated that
it will take the researchers thirteen weeks to identify a target date for finishing their
investigation. The communication plan is anticipated to take the first three weeks, while
data collection and research are being done. The following fourth to fifth week is
dedicated to the modeling plan, during which data flow diagrams and requirements are
explained. Following that, the construction and deployment plan is implemented, during
which the system is built, tested, and debugged, and on the thirteenth week, the research
is completed.
3.9 Operation Procedure
16
The following step by step process in producing the website system for digital
marriage registration:
Admin Account
1. Visit the website and click sign in.
2. Enter a valid username and password.
3. The dashboard will show where the admin account have access to the following
functions:
a. Application
i. New Application
ii. Verified Application
iii. Rejected Application
iv. All Application
b. Report
c. Search
Student Account
17
1. Visit the website and click sign in
2. Enter a valid mobile number and password.
3. The dashboard will show where the student account have access to the following
functions:
a. Registration Form
b. View Marriage Application
c. Search
3.10 Testing Procedure
18
The researchers conducted testing procedures to assure the performance of the
website system for digital marriage registration. Alpha test or initial testing and Beta
test which is the final testing is conducted appropriately to specify that the website is
functioning as intended by the researchers.
Alpha Test
During alpha testing, the website system is examined and its flaws and errors are
fixed. The researchers checked for input mistakes, made sure that records were
stored correctly, that the application worked as intended, and checked for any
potential design flaws. All of the website's buttons will also be checked to see if
they respond and function as intended. If real-time data appears in MySQL as a
digital database of the website system, phpMyAdmin can easily interact with it.
Beta Test
19
The final test, known as beta testing, involves actual user and admin account
testing for the newly developed website system. A specific the researchers do
representation to ensure that the functions are operating as intended. The researcher
verified that the buttons for the user account were functioning as intended and checked
to see if the data had been saved in the database by creating an account, logging in and
out, and registering a marriage. The researchers found that for the admin account, the
marriage registration completed during the previous procedure is indicated to the
system's registration function, and the admin may see how many people are approved
and denied.
20

3.11 Evaluation Process
The researchers prepared a survey questionnaire to determine and evaluate the
characteristics of the website system in terms of functionality, content, aesthetic, and
security. Pertains to the methods on how to gather data and research techniques will
give information about the result of the survey questionnaire that help in analyzing and
improving to consider content and functionalities of the website system and under a
study by the researchers. In table 4.1 illustrated below, the researchers used the 5-point
Likert Scale System to interpret items in the survey questionnaire, rate the effectiveness
of implementing, and evaluate the website system.
Table 4.1 Likert Scale Measurement
Scale Range Interpretation
5 4.51 5 Excellent
4 3.51 4.5 Very Good
3 2.51 3.5 Good
2 1.51 2.5 Fair
1 0 1.5 Poor
21

The formula for weighted mean will be used in evaluation to measure the
response of the survey samples whether they agree to a given statement or not, as for
the researchers will be able to determine the average through opinions of the
respondents.
Formula:
Where:
22

Chapter IV
Results and Discussion
This chapter contains the specific content description, structure of the software,
the accomplishment of the system, the evaluation of the system software, and also
presents the use of post-survey evaluation results to determine the functionality,
content, aesthetic, and security of the website system software.
4.1 Software Description and Structure
The website system of the researchers named DMRS is a website digital
marriage registration system and its main function is to help user who need a quick
process about the status and copy of the marriage registration in the system from the
admin who can assist and also help the church to lessen the responsibility regarding
manual usage in marriage registration with the help of the new technology. The goal of
this website system is to allow user to properly register marriage to provide digital
backup in manual marriage registration and enable admin or church to follow and
maintain organization’s guidelines for marriage registration.
23
Figure 4.1 System Front Page, and Sign-in Page
In Figure 4.1, the front and sign-in page is illustrated above, once opening the
website system after the sign-in page for user and admin account a brief front screen
will appear with content features about church and system.
24
Figure 4.2 User Dashboard
In Figure 4.2, the user dashboard is illustrated above, after a successful log-in,
the user can access the dashboard where they can check the status of the marriage
registration if verified or rejected.
25
26
Figure 4.3 Marriage Registration Form
In Figure 4.3, the marriage registration form for the user account is illustrated
above, if the user wants to register their marriage first then click “Registration Form”
option, and then proceed in filling out the form and click register. Once submitting the
registration form, the user can view the registered marriage.
27
Figure 4.4 View Marriage Application
In Figure 4.4, the view marriage application for the user account is illustrated
above, if the user finished filling out marriage registration form then after clicking the
“View Marriage Application” option the user can view their marriage application.
28
Figure 4.5 Search Marriage Application
In Figure 4.5, the search marriage application for the user account is illustrated
above, if the user registration approve or declined by the admin then click “Search
Marriage Application” for the user to search their marriage application.
29
Figure 4.5 Admin Dashboard
In Figure 4.5, the admin dashboard is illustrated above, after a successful log-in,
the admin can access the dashboard where they can check the status total new
application, total verified application, total rejected application are correct based on the
total application.
30
31
Figure 4.6 Application
In Figure 4.6, the application for the admin account is illustrated above, if the
admin finished updating the status of marriage registration, then after clicking the “All
Application” option, the admin can see the application details. They can edit the status
of the application.
32
4.2 Software Capabilities
The website system is designed to enable the users in practical way of
registering marriage to occupy and organize into electronic marriage registration with
the use of the technology, the user will simply register marriage by visiting the system
via website and the admin will be noticed with the registration and through the help of
the system, the entire approach is just easier compared to usual procedure that it’s no
advantage.
33

Chapter 3

Uploaded by

Copyright:

Available Formats

You might also like

Chapter 3

Uploaded by

Document Information

Original Description:

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

Chapter 3

Uploaded by

Copyright:

Available Formats

ST.

VINCENT COLLEGE OF CABUYAO

Bachelor of Science in Information Technology

3.1 Software Methodology

testing, and evaluation procedure. As advancing the development process generally

organizing the data, and formulating the analysis.

Figure 3.1 Rapid Application Development Model

Bachelor of Science in Information Technology

3.1.1 The Process Steps

 Requirements Planning - The researchers' initial phase involves gathering all

researchers used a survey questionnaire to identify the manual filing system

request was made.

was created by the researchers based on functionalities that transform the

may access it and use its various capabilities.

 Implementation - After the coding is finished, the deployment is the fourth

completely complies with the requirements, the researchers conducted the

Bachelor of Science in Information Technology

3.2 Project Design

3.2.1 Use Case Diagram

Figure 3.2 Use Case Diagram for the Users Account

registration form, view marriage application, and search.

Bachelor of Science in Information Technology

Figure 3.3 Use Case Diagram for the Admin Account

Bachelor of Science in Information Technology

3.3 Software Development

3.4 Project Development

3.4.1 Hardware Development

1. Made a system for Digital Marriage Registration System.

2.1 Google Chrome

Bachelor of Science in Information Technology

3.4.2 System Development

development to program and design the system.

3. The flowchart diagram illustrated in Figure 3.4.

Bachelor of Science in Information Technology

Figure 3.4 Flowchart Model for User

Bachelor of Science in Information Technology

Bachelor of Science in Information Technology

Figure 3.5 Flowchart Model for Admin

monitor again if there’s a new marriage application.

3.6 Activity Diagram

Bachelor of Science in Information Technology

Figure 3.6 Activity Diagram for User and Admin Account

it for validation then saved to the database of a system.

Bachelor of Science in Information Technology

Figure 3.7 Activity Diagram of Marriage Registration for User Account

Bachelor of Science in Information Technology

the certificate of marriage.

Bachelor of Science in Information Technology

Figure 3.7 Activity Diagram of Marriage Registration for Admin Account

Bachelor of Science in Information Technology

admin will monitor when anyone else register a marriage.

Bachelor of Science in Information Technology

Figure 3.9 Hierarchy Diagram

Bachelor of Science in Information Technology

The system's installation plan is displayed in a Gantt chart. It is anticipated that

3.9 Operation Procedure

Bachelor of Science in Information Technology

1. Visit the website and click sign in.