Escolar Documentos
Profissional Documentos
Cultura Documentos
Barbin, Nikka J.
Intia, John Alfred D.
Martizano, Jerico Alexis V.
Roldan, Jerome Adrian S.
March 2019
TABLE OF CONTENTS
LIST OF FIGURES 4
LIST OF TABLES 9
CHAPTER 1 – INTRODUCTION 10
1.1. PROJECT CONTEXT 10
1.2. TECHNICAL BACKGROUND 12
1.2.1. Equipment / Hardware 12
1.2.2. Software 12
1.2.3. Peopleware / Manpower 12
1.2.4. Network Infrastructure / Architecture 13
1.2.5. Storage, Backup, and Recovery Procedures 13
1.2.6. Security Procedures 13
1.2.7. Policies and Procedures 14
1.2.8. Data and Process 27
1.3. PROBLEM ANALYSIS 28
1.3.1. Fishbone Diagram 28
1.3.2. Problem and Solution Statement 29
1.3.3. Problem – Requirement Matrix 30
1.4. PURPOSE DESCRIPTION 30
1.5 SPECIFIC OBJECTIVES 31
1.6. SCOPE AND LIMITATIONS 31
CHAPTER 2 - REVIEW OF THE RELATED LITERATURE / SYSTEMS 33
CHAPTER 3 – METHODOLOGY 35
3.1 REQUIREMENT ANALYSIS 36
3.1.1. Requirements – Features Matrix 36
3.1.2. Use Case Diagram 38
LIST OF FIGURES
No Title Page
1 Organizational Chart 11
2 Context Flow Diagram 14
3 Data Flow Diagram Level 1 15
4 Data Flow Diagram Level 1 16
5 Data Flow Diagram Level 2 (Applicant Registration) 17
6 Data Flow Diagram Level 2 (Application Evaluation) 18
7 Data Flow Diagram Level 2
(Evaluating Inspection Order for Recommend Approval) 19
8 Data Flow Diagram Level 2
(Evaluating Inspection Order for Approval) 20
9 Data Flow Diagram Level 2
(Evaluates AIR for Recommend Approval) 21
10 Data Flow Diagram Level 2
(Evaluating AIR for Approval) 22
11 Data Flow Diagram Level 2
(Signing FSIC for Recommend Approval) 23
12 Data Flow Diagram Level 2
(Signing FSIC for Approval) 24
13 Data Flow Diagram Level 2
(Releasing FSIC) 25
14 Entity Relationship Diagram 27
15 Fishbone Diagram 28
16 Waterfall Model 35
17 Use Case Diagram 38
LIST OF TABLES
No Title Page
1 Equipment / Hardware 12
2 Software 12
3 Peopleware / Manpower 12
4 Business Requirements 26
5 Business Requirements 26
6 Business Policies 26
7 Problem – Requirements Matrix 30
8 Requirements – Features Matrix 36
9 Use Case Report 39
10 Data and Process (Forms) 105
11 Data and Process (Reports) 105
CHAPTER 1 – INTRODUCTION
The inspectors will check the common areas, stairways, utility rooms, storage rooms
and the exterior of the building for issues that could threaten the life safety of the
occupants. However, the TCFS encountered complexity because of the current process
of recording the information of every business. The records can be burned, lost,
duplicated and accessed by unauthorized person and redundancy of information.
“Business Record Management and Certification Issuance System of Taguig
City Fire Station” is a secure system that will manage the client records and will give
notification to the administrator if the client is nearly or already expired. The
administrator can view the status of the application of the client that can
releaseprintable certificates and clearance.
1.2.2. Software
Table 2: Software
Particulars Specifications
Report (AIR).
(AIR) or FSIC.
(AIR).
No.
Page 29 Difficulty in generating FSIC and Module that can generate reports of
The system needs internet for the Google Maps and notification thru Gmail.
The system can only use in TCFS due to lack of resources like servers.
The system can only be access in TCFS.
All the businesses in Taguig can apply the FSIC permit.
The Barangay Resident Record Management and Certificate Issuance System, study of
John Edmar L. Caubang (2015) will enable process and prints Barangay permits and certificates
like Community Tax Certificate, Barangay Clearance, etc. It helps the client to give fast
response to the user by using this system because this system has a readymade
permits/certificates that the user needed. Consultation using this system the users can get and
see the schedule and the time.
The Parish Information System (PIS) is an integration of subsystems intended to cater
the record-keeping of parishes. It is basically a computerization of the Canonical book, which
they use in their manual recording. It has subsystems for Matrimony, Baptism, Death and
Confirmation. In each subsystem, it provides consolidation of records in a database.
Shepherd and Yeo (2003) Records Management is the field of management responsible
for the efficient and systematic control of creation, receipt, maintenance, use and disposition of
records.
In the study of Jhonson D. Dulpina, the Record Information System of Bureau of Fire
Protection Sorsogon, manages the client records, and give notification to the administrator if
client FSIC or FSEC is nearly or already expired. The administrator can view the status of the
application of the client that can release printable certificates and clearance. The purpose of this
study is to automate the record management initiative of Bureau of Fire Protection Sorsogon.
The proposed system is a Web-based application that will cater request of certificate and
monitor the submission of compliance for Fire Safety Inspection.
In the study of ShelaLajer (2010) Centralize Baptismal Certification Record
Management and Information System for Catholic Churches in the Diocese of Bayombong.
When a person is trying to acquire a baptismal certificate for her children from the parish
secretary, he/she needs to fill in the necessary information required by the form.
For issuance of certification, the parish secretary type in the information on the
readymade form using the typewriter. Certain improvements and changes shall be made when
the system is implemented.
According the Bearman (1996) records are at one and the same time the carries,
products, and evidence of business transactions. Business must create records which logically
metadata encapsulated objects.
3. CHAPTER 3 – METHODOLOGY
The modelling technique used in this project is Waterfall Model which introduces
sequential design approach for certain areas consisting of series of tasks, wherein the
outcome of one phase acts as the input for the next phase sequentially which means that
any phase in the development process begins only if the previous phase is complete and
there is no overlapping of the phases.
Requirement Analysis is the first phase that is to be fulfilled in the project. To properly
make plan, the requirements to be considered in the development of the system must be
documented and analyzed by the researchers. The next phase will be the design
requirements where the researchers need to plan for the methods to be used such as the
programming language, physical and logical design in order to meet the requirements. The
next phase will be the development of the system where the development or the actual
coding depends on the design phase. As soon as the design phase is already completed, the
development starts where the design will be develop based on the actual plan of the
document. The phase for testing starts when the system is already completed to ensure that
the system function well in accordance to the requirement of the client. After the testing
phase is completed, the last phase which is to deploy the project where the system will now
be used and available to the users.
Applicants
Registration
Applications
Business
Management
Inspection
Order
After Inspection
Report
P a g e | 37
Inspection for
NTC
Inspection for
FSIC
Inspectors
Performance
Generate
Reports
Backup
Database
Table 8: Requirement - Features Matrix
P a g e | 38
DESCRIPTION
Use case name: Application Request
Applicants – the one who create
application request.
Actors:
Clerks – the one who manage the
Application Request.
Purpose: Creating Application Request
To manage all the Application
Brief Description:
Request
The Applicants will create
application request and give the
Pre-Condition:
business information and the clerks
evaluate the application.
The system will save & update
Business Info and save application
Post-Condition:
request and show & update the
Application Request
Application Request
Application Request
DESCRIPTION
Use case name: Manage Business Information
Clerks, FSES and FCM – Manage
Actors:
the Business Information.
Add, Edit and view the Business
Purpose:
Information
Brief Description: Managing the Business Information
The Clerks, FSES and FCM must
Pre-Condition:
provide Business Information
The system will save, show and
Post-Condition:
update the Business Information.
Manage Business Information
DESCRIPTION
Use case name: Evaluates Inspection Report
Actors: Inspectors – View for Inspection
for NTC.
35. If the recommendation is for
Re Inspection the system
will create a record in
Inspection Order.
DESCRIPTION
Use case name: Manage Notice to Comply & FSIC
FSES – View the Inspection for
FSIC
FCM – View and Edit Inspection for
Notice to Comply and view
Inspection for FSIC
Actors:
Inspectors – View, print & edit
Approved Inspection for Notice to
Comply.
Clerks – View, Edit & print
Inspection for FSIC
View, Edit and Evaluate Inspection
Purpose: for Notice to Comply.
View and Edit Inspection For FSIC
Managing the Notice to Comply and
Brief Description:
FSIC
The FCM must update and evaluate
the Notice to Comply and Clerks
Pre-Condition:
must print and edit Inspection for
FSIC
The system will show and update
the Notice to Comply and the
Post-Condition:
system will show and update the
FSIC.
Manage Notice to Comply
Comply to Inspectors.
DESCRIPTION
Use case name: Generate Reports
Inspectors, FSES & FCM – They
Actors:
Generate Reports
Purpose: Generate Reports
Generate Reports
DESCRIPTION
Use case name: Backup Database
Actors: FCM – The one who backup database.
3.2.2
Figure 25:
Class
Diagram
P a g e | 54
Applicants Interface
Clerks Interface
FCM Interface
Inspector Interface
APPENDICES
An authorization to an inspection
Figure 2 Application Form the business for the records of the TCFS TCFS Staff
staff.
Figure 3 Checklist for applicant such as the building name, TCFS Staff
Figure 2 Monthly Report on the reports will send to clerks. TCFS Staff