CHAPTER III
METHODOLOGY
In order to create the Barangay Portal System for Abar 1 st , the proponents followed five
phases of System Development Life Cycle(SDLC) to establish the following: Planning, Analysis,
Design, Implementation and Maintenance.
MAINTENANCE
PLANNING
IMPLEMENTATION ANALYSIS
DESIGNING
Figure 1. SDLC with five Phases
A. PLANNING
In order to solve the problems that are currently being experienced in the
Barangay Abar 1st , the development team will gather data and information from the said
barangay. The development team will interview the barangay secretary about managing
certificates of their residents, giving certificates and disseminating information. Also, the
residents will be an interview about the process of requesting certificates and the
problems they encounter. The development team will also observe the barangay on how
they process and manage transactions within their residents. As a result, the development
team will build the needed functionalities and features by gathering facts that will be used
in creating the proposed system.
The following questions will be asked to the Barangay staff:
1. In what ways do you manage handing request of certificates to your residents?
2. How do you schedule to come and take their request, especially during this time
of pandemic?
The following questions will be asked to the residents:
1. Tell me about the last time you requested a document from the barangay.
2. How often do you request?
3. Tell me your experience in requesting documents.
4. How do you manage your time in going to your barangay?
The feasibility of the barangay will be asked by the development team that will
support the proposed system. The barangay still used a face-to-face transaction or
requesting certificates. The development team will create a digitalized system that will
help to serve their residents more easily.
Fishbone Diagram
The development team will create a fishbone diagram to visualize and categorize
the cause of the problems that the residents of Barangay Abar 1st are encountering.
Gantt Chart
The development team will create a Gantt chart to follow and note the course of
progress of the proposed system.
B. ANALYSIS
After gathering data from the Barangay Abar 1st Officers and Residents, the
development team will analyze it. The analysis includes passivity studies, technical,
operational, and economical. The development team will then determine if the proposed
system is technically, operationally, and economically feasible.
Flow chart (manual process)
The development team will make a flow chart to graphically represent the current
manual system of requesting a certificate used by the Abar 1st.
Feasibility Studies
Feasibility studies analyze a proposed project to determine if it is technically,
operationally, and economically feasible. It is used to determine if the organization can
see the project completed. It also allows the development team to gather data to decide if
the project can be feasible.
Technical Feasibility
This method relates to the practical use of any technology or a machine
which finds out whether the development of the proposed system is possible,
given the current technical resources, the development team will conduct a study
to assess the ability of Abar 1st to handle resources such as the needed hardware
and software.
Operational Feasibility
The development team will conduct a study to determine if Barangay Abar
1st is willing to handle the operation of the proposed system.
Economic Feasibility
The development team will analyze the proposed project’s costs and
revenues to determine whether or not it is logical and possible to complete. In this
study, the development team will evaluate if Barangay Abar 1 st can support the
hardware and software requirements of the operation of the proposed system.
C. DESIGN
During this phase, the development team will create diagrams such as context
diagram, Level 0 data flow diagram(DFD), Level 1 DFD, use case diagram, entity-
relationship diagram(ERD) and relational data model.
Context Diagram
The development team will create a context diagram of the proposed
system to define the boundary between the system, part of a system, and its
environment, showing the entities that interact with it.
Data Flow diagram
The development team will create a data flow diagram to graphically
represent the data flowing in and out of the processing data in the proposed
system.
Use Case Diagram
The development team will create a use case diagram to represent an
interaction of the users with the system that shows a relationship between the
users and the different use cases in the user involved.
Entity-Relationship Diagram
The development team will create an ERD to provide a visual starting
point for the proposed system that will be used to help determine information
system requirements. In addition, it shows and specifies relationships that can
exist between different entities.
Relational Data Model
The development team will create a relational data model of the proposed
system where all data is created in tuples and collects a group of elements into
relation.
User Interface Design
The development team will create a user interface design to show how the
user will interact with the system output, screens, menus, and functions.
D. DEVELOPMENT AND IMPLEMENTATION
In this phase, the development team will begin coding and testing the system. By
testing the system, the analyst and the developers will be able to the tech if there are
problems within the system or a need for improvement. The software/s that the
development team will use in creating the system is Php Laravel and Xampp. The
development team will also provide training to the users of the system.
E. SYSTEM SUPPORT AND MAINTENANCE
The maintenance of the system includes the supervision of the functionalities.
This is important to ensure the system runs smoothly. Problems and error take in this
phase. The development team will fix errors and bugs that the user may find while
operating the system. The development team can also perform corrective maintenance in
hardware failure. the development team can also perform adaptive maintenance to ensure
that the system can follow any changes in the environment, policies and processes.