See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/314774122

An Integrated Information Management System for Barangay 1-A Davao:

Profiling, Incident Recording, Project/Program Monitoring and Document
Request

Research Proposal · September 2015

DOI: 10.13140/RG.2.2.12966.52807

CITATION READS

1 22,734

3 authors, including:

Jonathan Chavez Javellana John Joven D Cainong

Ateneo de Davao University Ateneo de Davao University
3 PUBLICATIONS   2 CITATIONS    1 PUBLICATION   1 CITATION   

SEE PROFILE SEE PROFILE

All content following this page was uploaded by Jonathan Chavez Javellana on 13 March 2017.

The user has requested enhancement of the downloaded file.

 ATENEO DE DAVAO UNIVERSITY

Barangay 1-A Incident Recording, Document Request, Profiling, and

Project/Program Monitoring System

4:45-5:40 / Wednesday September 9, 2015

Cainong, John Joven

Galvez, Danielle Dara

Javellana, Jonathan

Members

Mr. John Roy Geralde

Adviser

Mr. Dominique Cimafranca

Mr. Yancy Vance Paredes

Ms. Novie Joy Pellobello

Panelists
Table of Contents
I. Introduction ................................................................................................................... 3

A. Background and Problem Definition ...................................................................... 3

B. System Objectives ................................................................................................. 4

C. System Benefits .................................................................................................... 4

D. System Scope ....................................................................................................... 4

E. Glossary ................................................................................................................ 5

II. Existing System ........................................................................................................... 6

A. Data Flow Diagram ................................................................................................ 6

i. Context Level ..................................................................................................... 6

ii. Level 0 ............................................................................................................... 7

B. Events List ............................................................................................................. 8

C. Activity Diagram .................................................................................................... 9

III. Proposed System ..................................................................................................... 13

A. Events table ......................................................................................................... 13

B. Use case diagram ............................................................................................... 18

i. Essential use case list ...................................................................................... 22

ii. Use Case Specifications .................................................................................. 23

C. Sequence Diagram /Interaction Diagram............................................................. 30

D. Domain Class Diagram........................................................................................ 37

E. Mock-up screens ................................................................................................. 38

IV. References .............................................................................................................. 48

 INTRODUCTION

A. Background and Problem Definition

Barangay 1-A Poblacion is a local barangay area located at Bolton

Extention, Davao City, Philippines. Barangay 1-A was established by the former
Brgy. Captain Hon. Benjamin M. Manggubat. It is a small community that houses
a population of 3,420 as of 2015. It sustains itself through its established vision
and mission. The barangay hall is accessible and it opens around 7 am to 5 pm.
The current Punong Barangay is Hon. Elpidio J. Alicaway.
It is recognized for its transformative and participatory governance serving
its constituents and the community. Their mission is to provide a dynamic and
supportive political and socio-economic environment through the highest standard
of public administration, bureaucratic system committed to democratizing to public
service. They currently have services on accepting complaints, requesting
barangay clearance, cedula (community tax certificate), and certification.
The barangay personnel heavily relies on papers and use the computer for
encoding barangay accounts and other information through office application.
Most of their records and documents are located in their physical file cabinets.
Whenever a request is made, the procedure is heavily relied upon the Brgy.
Secretary and Brgy. Treasurer.
During regular days, every request made by the client would take minutes,
but there is a possibility of longer waiting time for the client in order to process
because of tedious search on records found in their cabinets which paralyzes client
service.
The project/program monitoring of the Barangay rely on papers. All of the
relevant information are encoded to a spreadsheet application. These are placed
on a long folder.
The proponents would like to introduce the system of document
management and keeping track of records in a modern approach where computers
are primarily the medium that reduces the consumption on paper.
B. System Objectives

The proponents aim to complete this system in order to

● Organize barangay records, requests, and projects for accessible lookup

● Reduce paper dependency
● Produce forms on each request
● Client requests transactions are prioritized
● Input resident’s profile electronically
● Effectively manage projects and programs

C. System Benefits

The proponents would like to propose a system for the Barangay in order to

● Reduce client request waiting time

● Verify client request faster
● Easy lookup on records

D. System Scope

The Barangay 1-A Document Request System implements the procedure of

issuing document request that satisfies client’s requirements and is based on the
Barangay Citizen’s Charter. This gives priority to the client’s request.
The Barangay 1-A Incident Recording System is where the complaints of the client
is kept record in a local computer.
The Barangay 1-A Project Monitoring System is where the effective monitoring of
projects are taken into consideration. It plays a role on preventing overspending or
underspending in implementing barangay projects. This system promotes
transparency and accountability in the barangay.
The Barangay 1-A Profiling System is where the collecting, analyzing and
documenting necessary information that defines the current barangay profile. It
covers the census, organizational chart, vision and mission and barangay status.
This proposal doesn’t mention about closing an incident case (hearing), payroll
and healthcare.
E. Glossary

Activity Diagram – are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency.

Document Request – a process where a client wants to secure a barangay

document like cedula, certification, and clearance.

Incident recording – it records and presents complaints on blotter.

Cedula – a community tax certificate for a client that is needed for a document
request system.

Profiling – a process of gathering and recording residents in a community.

Project and Program Monitoring – a collection of projects and programs containing

crucial information such as budget, expenditures, participants and status.

Barangay Committee – responsible for initiating barangay projects, keeps track of

the project activity.
 EXISTING SYSTEM
A. Data Flow Diagram
i. Context Level

PROJECT REPORT
PROJECT DETAILS Barangay
COMPLAINANT COMPLAINT ENTRY PROJECT PROPOSAL Development
Council Committee
PROJECT/PROGRAM
FOLLOW-UP DETAILS

BARANGAY CLEARANCE
BARANGAY CERTIFICATION

SIGNED DOCUMENT
PUNONG
BARANGAY
RESIDENT REQUEST FORM Barangay Document Request, DOCUMENT DETAILS
FEE Project/Program Monitoring,
INCIDENT DETAILS
Incident, Profiling System
OFFICIAL RECIEPT

INCOME DETAILS
CEDULA EXPENDITURE DETAILS
BUDGET DETAILS
OFFICIAL RECIEPT
SEARCHED COMPLAINT
CEDULA TREASURER
RESIDENT DETAILS CEDULA DETAILS
UPDATED RESIDENT PROFILE PAYMENT DETAILS
SECRETARY
BARANGAY RESIDENT INFO
UPDATED PROJECT/PROGRAM INFO
 ii. Level 0

11
PROJECT/PROGRAM UPDATE
FOLLOW-UP DETAILS
PROJECT
12 8 9 DETAILS
PREPARE UPDATE
FINED
PROJECT UPDATED RESIDENT
COMPLAINT
REPORT PROFILE PROFILE
INFO
PROJECT
BARANGAY 10
DETAILS UPDATED
DEVELOPMENT PROJECT/PROGRAM PREPARE
COMMITTEE SEARCHED COMPLAINT INFO INCIDENT
PROJECT RESIDENT DETAILS REPORT
PROPOSAL SECRETARY

BARANGAY INCIDENT DETAILS

COMPLAINANT RESIDENT
COMPLAINT ENTRY
INFO

2
1 REQUEST DOCUMENT PUNONG
PREPARE
FORM REQUESTED DETAILS BARANGAY
REQUEST FORM/SLIP IDENTIFY AND
RESIDENT DOCUMENT
VALIDATE

RESIDENT INFO
CLIENT INFORMATON PROJECT SIGNED DOCUMENT
PROPOSAL BLOTTER INFO

REQUESTS BLOTTER
LOGBOOK PROJECT 4
RESIDENT
FINALIZE
DOCUMENT
OFFICIAL RECEIPT
BUDGET
FEE 3 5
DETAILS
PAYMENT DETAILS TREASURER
PAYMENT CEDULA DETAILS SET BUDGET 7

PRODUCE
CEDULA INCOME
INCOME DETAILS
BARANGAY CLEARANCE

BARANGAY CERTIFICATION
6
EXPENDITURE DETAILS SET
EXPENDITURES
B. Events List

Barangay Document Request System

● Resident requests for a document
● Secretary verifies request
● Resident provides requirements
● Secretary prepares the document
● Resident pays document fee
● Secretary issues an official receipt for payment
● Authorized official approves the document
● Secretary gives the document

Barangay Incident Record System

● Secretary receives a complaint
● Secretary records a complaint
● Secretary updates a follow-up to the complaint
● Secretary finds a complaint entry

Barangay Profiling System

● Secretary gathers resident information
● Secretary records a resident profile in a computer
● Secretary update profile information for follow-up

Barangay Project/Program Monitoring System

 Committee proposes a Program/Project design
 Treasurer allocates budget for the Program/Project design
 Secretary encodes actual Program/Project expenditures
 Secretary encodes the Program/Project Proposal details
 Secretary looks up for the Project/Proposal details
 Committee updates the Program/Project details
 Secretary prints the Program/Project information summary
 Treasurer produce financial reports
C. Activity Diagram

Document Request

Resident Secretary Official

request document
verifies request

Verified?

provide
yes approve document
requirements
no

check requirements

prepare document

pays fee issues receipt

issuance of
document
Phase
Incident Record

Secretary

receives complaint

records incident

Follow ups?

no review complaint

yes

update complaint
Phase
Profiling

Secretary

gather resident info

verify resident

record a new
resdient profile
entry
Any
changes?

no keep the record

yes

update profile
Phase
Project/Program Monitoring System

Committee Treasurer Secretary

proposes a new
sets budget
program/project
sets expenditures

Exceeds budget?

yes
cancel or hold
project/program

no

record project/
program details

update project/
looks up details
program status

produce financial prints project/

reports program summary
Phase
 PROPOSED SYSTEM
A. Events table

1.) INCIDENT RECORDING SUBSYSTEM

Event Trigger Source Use Case Response Destination

Secretary New Secretary Add new Complaint Database

encodes complaint Complaint added
complaint
complaint
details

Secretary Incident Database View Selected Secretary

looks up for the Data complaint Incident
incident record Record
details

Secretary Complaint Secretary Update Complaint Database

updates the update Complaint updated
complaint

Secretary End of the Database Produce Incident Punong

generate Month incident Details Barangay
reports on report
incident
 2. Profiling Subsystem

Event Trigger Source Use Case Response Destination

Barangay 1-A New Secretary Create Created

secretary will Resident resident residents Database
create a new profile profile
resident profile

Barangay 1-A Resident’s Database View a Selected

secretary wants to profile data resident resident’s Secretary
look up for existing profile profile
resident profiles details

Barangay 1-A Revised Secretary Update Updated

secretary will Resident resident Resident Database
update residents Profile Profile
profile list

Barangay 1-A Report Secretary Produce Resident’s Punong

secretary generate Generation Profile Profile Barangay
reports on current request Report Report
profiles
 3. Project/ Program Monitoring Subsystem

Event Trigger Source Use Case Response Destination

Barangay A new project/ Brgy. Add new The new Database

Secretary program Officials project/ project/progra
records a new proposed program m has been
project/program created
plan

Barangay Budget Treasurer Set budget The budget has Brgy.

Treasurer sets allocation been indicated Captain
budget
Budget Details

Barangay Actual project/ Treasurer Create actual Actual project/ Secretary

Secretary program expenditures program
encode actual expenditures project
project/program expenditures
project created
expenditures
Actual
Expenditures
details

Brgy. Officials Project/ Brgy. Cancel Cancelled Database

cancel a Program Officials Project/Program project/progra
Plan
project/program Cancellation m Plan
Design (lack of
budget)

Barangay 1-A Project/Progra Brgy. View project/ Selected Brgy.

personnel wants m Data Officials program project/progra Officials
to look up for m Project
Project/Program Details
details.

Brgy Personnel Project/ Brgy. Update the Project / Project/

updates Program may Officials project/ Program Program
project/program have program information is Database
information undesired updated.
changes
Event Trigger Source Use Case Response Destination

Punong Project/ Database Approve Approved Brgy.

Barangay Program project/ project/ Official
evaluates Design Details program program
program/project Design
Design for
approval

Barangay 1-A Project/ Secretary Produce Project/ Brgy.

personnel Program project report Program Officials
generates Report reports
reports on Request
projects/
programs

Barangay End of period Database Produce An expenditure Brgy.

Treasurer expenditures report is Officials
generates report presented
expenditures
report
 4.) Document Request SUBSYSTEM

Event Trigger Source Use Response Destination

Case

Secretary encodes Resident Resident Add Resident’s Document

Resident’s Document request request is Requests
Document Request Request created. Database
(Barangay
Clearance,
Certificate, Cedula)

Punong Barangay Document Database Approve Approved Secretary

approves Document Request Request document
Request (Barangay request
Clearance,
Certificate, Cedula) Signed
document
request

Secretary issues Member’s Secretary Set Payment Income

receipt for payment Payment payment Details Database /
Treasurer

Treasurer produce End of Database Produce Income Treasurer

income report period Income Details
Report
 B. Use case diagram

Add new complaint

View Complaint

Personnel <<include>>

update complaint

Produce incident report

 Add request

Approve request

<<include>>

Secretary
Set Payment

Treasurer

Produce Income Report

…
 Create resident profile

View resident profile

Personnel <<include>>

Update resident profile

Produce profile report

…
 Add project/program

Set budget

Secretary

Create actual
expenditures

<<extend>> Treasurer

Cancel project/program plan

View projects
<<include>>
Update project/program

Approve project/
program

Produce Expenditrures
Report

Produce project/
program reports
i. Essential use case list

Profiling
 Gather resident info
 Create resident profile
 View resident profile

Project/Program Monitoring
 Add project/program
 Set budget
 Create actual project expenditures
 View projects

Documents Request
 Add request
 View request
 Approve request
 Set payment

Incident Record
 Add incident complaint entry
 Update complaint
 Read incident records
 ii. Use Case Specifications

PROFILING SUBSYSTEM
Use Case Name: Create Resident Profile
Scenario: Personnel will conduct interview.
Triggering Event: New Resident
Brief Description: When the resident already fill-up the form, his/her profile is evaluated by the
secretary and then is added to the Client database if qualified.
Actors: Secretary
Related Use Cases: View a resident’s profile
Extends: Update Profile
Preconditions: 1. A Resident must exist.
2. A Resident must be residing in the barangay within 6months.
3. A Resident must passed the interview.
4. The Resident application must be approved by the secretary.
Post-conditions: The Resident profile has been created.
Flow of Events: Actor System
1. Secretary verifies the
requirements of the
applicant. 2.1. Look-up existing Client’s profile
2. Secretary looks up if the
Client already exists. 3.1. Create New Client Profile
3. Secretary encodes the
Clientship application.
Exceptions:
Use Case Name: Update Resident Profile
Scenario: Resident wants to update his/her Client profile.
Triggering Event: A revised application form is submitted.
Brief Description: Resident submits his/her revised application form and the secretary encodes
changes to the resident’s profile.
Actors: Secretary
Related Use Cases: View a resident’s profile
Preconditions: 1. The person whose profile is being updated must be a resident.
Post-conditions: Resident’s Profile is updated.
Flow of Events: Actor System
1. Secretary looks up if the 1.1. View a Client’s profile
resident exists in the
Barangay Resident’s
Database. 2.1. Update Profile
2. Secretary update the
profile of the resident.
Exceptions:

Use Case Name: View a resident’s profile

Scenario: Secretary queries a resident’s profile
Triggering Event: Report Generation request
Brief Description: When a resident’s profile information is requested, the secretary looks up in
the barangay resident’s database.
Actors: Secretary
Related Use Cases:
Preconditions: 1. A resident’s profile must exist in the Barangay Resident Database.
Post-conditions: A resident’s profile is shown
Flow of Events: Actor System
1. Secretary looks-up for 1.1. View a resident’s profile
resident’s profile in the
Barangay Clients Database.
Exceptions:

Use Case Name: Produce a profile report

Scenario: Secretary queries a resident’s profile
Triggering Event: Report Generation request
Brief Description: When a resident’s profile information is requested, the secretary looks up in
the barangay resident’s database.
Actors: Secretary
Related Use Cases:
Preconditions: 2. A resident’s profile must exist in the Barangay Resident Database.
Post-conditions: A resident’s profile is shown
Flow of Events: Actor System
2. Secretary looks-up for 2.1. View a resident’s profile
resident’s profile in the
Barangay Clients Database.
Exceptions:

PROJECT/PROGRAM MONITORING SUBSYSTEM

Use Case Name: Add Project/Program Design

Scenario: Barangay Officials proposes a new Project Plan
Triggering Event: A new proposed project plan
Brief Description:
Actors: Barangay Officials , Secretary
Related Use Cases: View a Project
Includes: Approve Budget for Project
Preconditions: 1. A proposed project must exist.
Post-conditions: New project plan is created and sent to the Project Database.
Flow of Events: Actor System
1. Barangay Officials verifies if 1.1. View a Project
the program/project
already exist. 2.1. Add a New Project Plan
2. Secretary encodes the new
program/project design.
Exceptions:

Use Case Name: Set budget for Project Design

Scenario: Treasurer checks for pending budget request.
Triggering Event: A Project Budget Details pending for approval.
Brief Description: The required budget appropriation is being recorded.
Actors: Treasurer
Related Use Cases: View a Project
Includes: Approve Project Plan Details
Extends:
 Edit Project Plan Details
 Cancel Project Design
Preconditions: 1. A project design must exist.
2. A project design budget details must exist.
Post-conditions: The budget for Project Design is approved.
Flow of Events: Actor System
1. Treasurer looks for the 1.1. View a Project
pending Project Budget
Details.
2. Treasurer verifies the 3.1. Approve Budget for Project
Project Budget Details. Design
3. Treasurer approves budget
for project design.
Exceptions:

Use Case Name: Update Project Design Details

Scenario: Project Committee revises Project plan details.
Triggering Event: Changes in details of a Project Plan
Brief Description: Secretary will keep note on necessary updates on the ongoing project
Actors: Barangay Officials
Related Use Cases: View a Project
Preconditions: 1. A project design must exist.
Post-conditions: Program/Project Design is updated.
Flow of Events: Actor System
1. Barangay Officials looks for 1.1. View a Project
the Project Plan in the
Project Database.
2. Barangay Officials edits the 2.1. Project Design Details
project details.
Exceptions:

Use Case Name: Create actual project expenditures

Scenario: Secretary encodes actual project expenditures
Triggering Event: Actual project expenditures are provided.
Brief Description: Necessary expenditures involves costing of needed materials are recorded
that supports the program/project endeavour.
Actors: Secretary
Related Use Cases: None
Preconditions: 1. A project must exist.
2. A project budget details must exist and approved.
3. A project must be approved.
Post-conditions: Actual expenditures for the project are sent to the Project Database.
Flow of Events: Actor System
1. Secretary looks-up project. 1.1. View a Project
2. Secretary encodes the
actual expenditures for the 2.1. Create actual project
project. expenditures
Exceptions:
Use Case Name: View Programs/Projects
Scenario: Punong Barangay, Treasurer, Secretary, Program/Project Committee wants to
look up for Program/Project details
Triggering Event: A program/project Data is requested.
Brief Description: The program is being looked up by the barangay personnel.
Actors: Punong Barangay, Treasurer, Secretary, Program/Project Committee
Related Use Cases:
Preconditions: 1. A program/project must exist.
Post-conditions: Selected Program/Project details are shown.
Flow of Events: Actor System
1. Punong Barangay, 1.1. View a Program/Project
Treasurer, Secretary,
Program/Project
Committee looks-up for a
program/project.
Exceptions:

Use Case Name: Produce Program/Project Report

Scenario: Secretary produces program/project design report by schedule, by tasks, by
progress, by participants, by location, etc.
Triggering Event: A report for a given period of time is requested.
Brief Description:
Actors: Secretary
Related Use Cases:
Preconditions: 1. A program/project must exist.
Post-conditions: Program/Project details for the given period of time is produced.
Flow of Events: Actor System
1. Secretary inputs a given 1.1. Produce Program/Project
period of time. Report.
2. Print or Save produced
Program/Project Report.
Exceptions:

Use Case Name: Produce Expenditures Report

Scenario: Treasurer produces expenditures report
Triggering Event: A report for a given period of time is requested.
Brief Description:
Actors: Treasurer
Related Use Cases:
Preconditions: 1. A program/project must exist.
2. A program/project must be approved.
3. A program/project budget must exist.
4. A program/project budget must be approved.
 5. Actual expenditures for program/project must exist.
Post-conditions: A Program/Project Expenditures detail for the given period of time is
produced.
Flow of Events: Actor System
1. Treasurer inputs a given 1.1. Produce Program/Project
period of time. Expenditures Report.
2. Print or Save produced
Expenditure Report.
Exceptions:

DOCUMENTS REQUEST SUBSYSTEM

Use Case Name: Add a New Request

Scenario: Resident wants to acquire a Document Request (Clearance, Certificate,
Cedula).
Triggering Event: A resident request for a Document Request (Clearance, Certificate, Cedula)
Brief Description: Resident requests for a Document Request (Clearance, Certificate, Cedula) to
the secretary, who then encodes the request in the system.
Actors: Secretary
Related Use Cases: View a resident’s Profile
Includes: Approve resident’s request
Preconditions: 1. A resident must exist.
2. Resident must fill-up a request form and bring right requirements.
Post-conditions: Request status is sent to the Document Requests Database for approval.
Flow of Events: Actor Actor
1. Secretary looks up resident 3. Secretary looks up resident
from the Barangay from the Barangay residents
residents Database. Database.
2. Secretary encodes the 4. Secretary encodes the
resident’s request resident’s request
Exceptions: Entity requesting is not a resident

Use Case Name: Approve Request

Scenario: Punong Barangay approves the requested Document Request (Clearance,
Certificate, Cedula)
Triggering Event: A pending resident’s request in the Document Requests Database.
Brief Description: When a Document Request (Clearance, Certificate, Cedula) is requested, the
resident requesting is evaluated and then approved (if qualified) by the
barangay captain.
Actors: Punong Barangay approves the requested Document Request(Clearance,
Certificate, Cedula)
Related Use Cases: View resident’s profile
Preconditions: 1. A resident must exist.
2. A resident’s request must exist.
Post-conditions: The resident’s request is approved.
Flow of Events: Actor System
1. Punong Barangay looks up 1.1. View a resident’s profile
resident for evaluation.
2. Punong Barangay verifies
request
3. Punong Barangay approves 3.1 Approve resident’s Request
resident’s request.
Exceptions:

Use Case Name: Document Request (Clearance, Certificate, Cedula) Payment

Scenario: Resident pays to the Secretary for the Document Request(Clearance,
Certificate, Cedula)
Triggering Event: Resident pays for the requested Document Request(Clearance, Certificate,
Cedula)
Brief Description: When the Document Request(Clearance, Certificate, Cedula) is approved, the
resident pays for the Document Request(Clearance, Certificate, Cedula) to the
secretary,
Actors: Secretary
Related Use Cases: Includes: Approve resident’s Request
Preconditions: 1. The Request must be approved.
2. resident must pay the right amount for Document Request(Clearance,
Certificate, Cedula)
Post-conditions: 1. Payment information is sent to the Income Database
Flow of Events: Actor Actor
1. Secretary receives payment 4. Secretary receives payment
from the resident from the resident requesting a
requesting a Document Document Request (Clearance,
Request (Clearance, Certificate, Cedula).
Certificate, Cedula). 5. Secretary confirms payment
2. Secretary confirms 6. Secretary gives change to the
payment resident
3. Secretary gives change to
the resident
Exceptions:

Use Case Name: Produce Income Report

Scenario: Treasurer looks up for the income report for a time period
Triggering Event: A report for a given period of time is requested.
Brief Description: An income report for the Document Request (Clearance, Certificate, Cedula)
and other documents is produced when the treasurer queries for it.
Actors: Treasurer
Related Use Cases:
Preconditions: 1. Income must exist.
Post-conditions: Income details for the given period of time must be produced.
Flow of Events: Actor Actor
1. Treasurer inputs a given 3. Treasurer inputs a given period
period of time. of time.
2. Print or Save produced 4. Print or Save produced Income
Income Report. Report.
Exceptions:

INCIDENT RECORDING SUBSYSTEM

Use Case Name: Add new complaint

Scenario: Resident will file a complaint
Triggering Event: New incident report
Brief Description: The resident’s complaint will be entertained
Actors: Secretary
Related Use Cases: View complaint

Preconditions: A reported incident must exist.

Post-conditions: New incident report is created and sent to the Database.
Flow of Events: Actor System
1. Secretary verifies if the 1.1. View a Incident Report
incident report already exist.
2. Secretary encodes the new
incident report. 2.1. Add a New Incident Report
Exceptions:

Use Case Name: View complaint

Scenario: Punong Barangay, Secretary wants to look up for Incident Report
Triggering Event: An Incident Report Details has been requested.
Brief Description: The complaint is reviewed.
Actors: Punong Barangay, Secretary
Related Use Cases:
Preconditions: An incident report must exist.
Post-conditions: Selected incident report details are shown.
Flow of Events: Actor System
 1. Punong Barangay or 1.1 View an Incident Report
Secretary looks-up for an
Incident Report.
Exceptions:

Use Case Name: Update complaint

Scenario: Secretary revises Incident report details.
Triggering Event: Changes in details of an Incident Report
Brief Description: View complaint
Actors: Secretary

Related Use Cases: View a Incident Report

Preconditions: A incident report must exist.
Post-conditions: Incident report is updated.
Flow of Events: Actor System
1. Secretary looks for the 1.1. View a Incident Report Details
incident report in the
Database. 2.1 Incident Report Details
2. Secretary edits the Incident
report details.
Exceptions:

Use Case Name: Produce Incident Report

Scenario: Secretary produces Incident report by complainant, by plaintiff, by case, by
description, by location, etc.
Triggering Event: A report for a given period of time is requested.
Brief Description: Reports of barangay complaints are summarized
Actors: Secretary
Related Use Cases:
Preconditions: An Incident report must exist.
Post-conditions: Project/Program details for the given period of time is produced.
Flow of Events: Actor
1. Secretary inputs a given
period of time.
2. Print or Save produced
Incident Report.
Exceptions:
 C. Sequence Diagram /Interaction Diagram

DOCUMENT REQUEST SUBSYSTEM

DOCUMENT PUNONG
RESIDENT SECRETARY REQUEST SYSTEM TREASURER
BARANGAY

Document request information

Create request
(brgy clearance/certification/ cedula)

Approve member request

approved document request

give payment Payment Information Payment Information

Generate Official Receipt

Release Approved Document
Give document
(brgy clearance/certification/cedula)
 INCIDENT RECORDING SUBSYSTEM

INCIDENT
RECORDING PUNONG
COMPLAINANT SECRETARY
SYSTEM BARANGAY

report incident information

add new complaint

show complaint detail

update complaint

view an incident record

selected incident record details

Read incident record

Incident record details

PROFILING SYSTEM
 PROJECT/PROGRAM MONITORING SUBSYSTEM

PROJECT/PROGRAM
BRGY MONITORING
SECRETARY TREASURER
COMMITTEE SUBSYSTEM
send project proposal
information
add project

set budget amount

create actual
expenditures
expenditures review
present project expenditure details

opt

expenditures > budget

pending project request

cancel project plan

opt

expenditures==budget

Approve project/program proposal

View program/project entry

Details (project_information)

updateProgram(project_name, contractor, duration)

Produce project/program reports

project/program details
D. Domain Class Diagram
E. Mock-up screens
The following are the screenshots of each proposed system.
DOCUMENT REQUEST
INCIDENT
PROJECT / PROGRAM
PROFILING
 REFERENCES

• Apc.csf.ph,. (2015). BIMS (Barangay Database Management System) - Asia

Pacific College Project Based Learning Wiki. Retrieved 26 August 2015, from
http://apc.csf.ph/wiki/index.php/BIMS_(Barangay_Database_Management_Syste
m)

• Interpointinc.com,. (2015). Barangay Management System (BMS). Retrieved 26

August 2015, from http://interpointinc.com/it-solutions/barangay-management-
system-bms/

• Profile, V. (2005). A Wonderful World: BARANGAY FILE MANAGEMENT

SYSTEM. Wonderworldblog.blogspot.com. Retrieved 26 August 2015, from
http://wonderworldblog.blogspot.com/2005/07/barangay-file-management-
system.html

• Scribd,. (2015). Philippines: The Barangay System. Retrieved 26 August 2015,

from http://www.scribd.com/doc/6369850/Philippines-The-Barangay-
System#scribd

• Systems Analysis and Design, Kendall, et.al.

• Barangay 1-A Poblacion, Davao City. (n.d.). https://barangay1a.wordpress.com/

Retrieved September 7, 2015.

View publication stats