Definisi Analysis Checklist

Checklist analysis adalah salah satu teknik analisis bahaya untuk mengidentifikasi risiko yang terjadi dari sebuah proses kerja. Checklist analysis dapat
menyediakan gagasan-gagasan mengenai risiko selama pekerjaan berlangsung. Analisis ini dapat dikembangkan berdasarkan informasi sejarah,
pengetahuan dari proyek-proyek serupa sebelumnya dan dari sumber lain. Hal ini juga memungkinkan untuk menggunakan tingkat terendah Struktur
Breakdown Risk (RBS) sebagai daftar periksa.
Checklist analysis cepat dan sederhana, dapat digunakan oleh anggota tim yang memiliki pengalaman relatif kurang dalam proyek serupa. Tapi, manajer
proyek harus memahami bahwa tidak mungkin untuk membangun sebuah daftar lengkap. Jadi, perawatan harus dilakukan untuk juga mengeksplorasi
risiko yang tidak muncul di daftar, karena bahkan proyek yang sangat mirip akan memiliki perbedaan sendiri, unik dan risiko yang berbeda.
Checklist harus ditinjau ulang selama penutupan proyek untuk menggabungkan setiap pelajaran baru yang dipelajari dan juga untuk meningkatkan
checklist untuk proyek-proyek masa depan.

Pedoman Analysis Checklist

Checklist pada checklist analysis diberikan sebagai bagian dari proses evaluasi untuk Analisis Risiko . Checklist analysis membantu pengulas yang
ditunjuk dalam menentukan apakah spesifikasi memenuhi kriteria yang ditetapkan dalam HUD Pengembangan Sistem Metodologi ( SDM ) . Tujuan
dari evaluasi ini adalah untuk menentukan apakah dokumen tersebut memenuhi persyaratan metodologi pengembangan HUD .

Di bawah ini terdapat document review checklist.,Tujuannya adalah untuk memastikan bahwa dokumen mencapai standar tertinggi baik format ,
konsistensi , kelengkapan , kualitas , dan presentasi .
Submissions harus mencakup tiga dokumen berikut , dan harus disajikan dalam urutan sebagai berikut : ( Pertama ) Dokumen Checklist , ( Second )
Checklist Analisis Risiko , dan ( Ketiga ) Analisis Risiko .
Penulis dokumen yang diperlukan untuk menyelesaikan dua kolom diindikasikan sebagai " PENULIS X - REFERENCE Halaman # / Bagian # " dan "
PENULIS KOMENTAR " sebelum pengajuan. Jangan menyelesaikan dua kolom terakhir ditandai sebagai COMPLY and REVIEWER
COMMENTS " karena ini adalah untuk pengulas yang ditunjuk .
Pengulas Dokumen akan berkonsultasi dengan HUD SDM dan SDM template ketika meninjau dokumen dan menyelesaikan bagian-bagian resensi
terhadap checklist ini
Berikut ini contoh dari checklist analysis:
AUTHOR REFERENCE (Project Identifier):
Designated Reviewers:
1:
2:
3:
4:
Summary Reviewer:

Start Date:

Completed Date:

Area Reviewed:

Comments:

The determination of the type of risk assessment to be performed relates to the decision made during the determine category process described in section 1.3 of
the System Development Methodology. The level of effort required to perform a risk analysis will be much greater for a new development effort than for an
enhancement project.

TABLE OF CONTENTS
1.0

2.0

3.0

General Information
1.1 Purpose
1.2 Scope
1.3 System Overview
1.4 Project References
1.5 Acronyms and Abbreviations
1.6 Points of Contact
1.6.1
Information
1.6.2
Coordination
Project and System Description
2.1 Summary
2.1.1
Project Management Structure
2.1.2
Project Staffing
2.2 Risk Management Structure
2.3 Periodic Risk Assessment
2.4 Contingency Planning
System Security
3.1 Baseline Security Requirements
3.2 Baseline Security Safeguards
3.3 Sensitivity Level of Data
3.4 User Security Investigation Level and Access Need

4.0

5.0

6.0

Risks and Safeguards

*4.x [Risk Name]
4.x.1
Risk Category
4.x.2
Risk Impact
4.x.3
Potential Safeguards
4.x.3.y
[Safeguard Name]
Cost and Effectiveness of Safeguards
*5.x Potential Safeguards
5.x.1
Lifecycle Costs for Acceptable Safeguards
5.x.2
Effects of Safeguards on Risks
5.x.3
Economic Feasibility of Safeguards
Risk Reduction Recommendations

* Each risk or safeguard should be under a separate header. Generate new

sections and subsections as necessary for each risk from 4.1 through 4.x, and for
each safeguard from 5.1 through 5.x.

REQUIREMENT

To be completed by Author
AUTHOR
X-REFERENCE
AUTHOR COMMENTS
Page #/Section #

To be completed by Reviewer
COMPLY
Y

1.0 GENERAL INFORMATION

1.1 Purpose: Describe the purpose of the Risk Analysis.
1.2 Scope: Describe the scope of the Risk Analysis as it
relates to the project.
1.3 System Overview: Provide a brief system overview
description as a point of reference for the remainder of
the document, including responsible organization,
system name or title, system code, system category,
operational status, and system environment or special
conditions.
1.4 Project References: Provide a list of the references
that were used in preparation of this document.
1.5 Acronyms and Abbreviations: Provide a list of the
acronyms and abbreviations used in this document and
the meaning of each.
1.6 Points of Contact:
1.6.1
Information: Provide a list of the points of
organizational contact that may be needed
by the document user for informational and
troubleshooting purposes.
1.6.2
Coordination: Provide a list of
organizations that require coordination
between the project and its specific support
function (e.g., installation coordination,
security, etc.). Include a schedule for
coordination activities.

REVIEWER
COMMENTS

REQUIREMENT

To be completed by Author
AUTHOR
X-REFERENCE
AUTHOR COMMENTS
Page #/Section #

To be completed by Reviewer
COMPLY
Y

2.0 PROJECT AND SYSTEM DESCRIPTION

2.1 Summary: Provide basic information about the
project and the application system for which a risk
analysis is being conducted.
2.1.1
Project Management Structure: Identify
the project sponsor, sponsoring office
project leader, and the estimated or actual
start and end dates of a new or modified
system project.
2.1.2
Project Staffing: Determine the
approximate number of staff hours required
(HUD personnel and contractors) and
identify the expertise, knowledge, skills,
and abilities needed by the project team to
develop and/or maintain a quality
application system.
2.2 Risk Management Structure: Identify organizations
responsible for managing identified risks and
maintaining countermeasures.
2.3 Periodic Risk Assessment: Describe the frequency of
periodic risk assessments of the operational system.
2.4 Contingency Planning: Determine the level of
contingency planning needed and identify the
responsible personnel involved.

REVIEWER
COMMENTS

REQUIREMENT

To be completed by Author
AUTHOR
X-REFERENCE
AUTHOR COMMENTS
Page #/Section #

To be completed by Reviewer
COMPLY
Y

3.0 SYSTEM SECURITY

Assess the security requirements and specifications
necessary to safeguard the system and its
corresponding data.
3.1 Baseline Security Requirements: Analyze the
processes and procedures required of the new system
or the system to be replaced and the sensitivity of the
data the system will be processing to determine
inherent security risks.
3.2 Baseline Security Safeguards: Describe the securityrelated technology that is currently available or
projected to be available at the time the system is
scheduled for operation.
3.3 Sensitivity Level of Data: Evaluate the data being
processed to determine whether the level of sensitivity
requires safeguards, such as the application of security
controls.
3.4 User Security Investigation Level and Access Need:
Analyze the systems end users, including those
having direct access to the system and those who will
indirectly receive output from the system.

REVIEWER
COMMENTS

REQUIREMENT

To be completed by Author
AUTHOR
X-REFERENCE
AUTHOR COMMENTS
Page #/Section #

To be completed by Reviewer
COMPLY
Y

4.0 RISKS AND SAFEGUARDS

Evaluate the proposed system and its operational
environment for potential risks (physical,
communication, hardware, and software) and
safeguards. Identify the potential security risks and
provide the following information for each.
4.x [Risk Name]: (Each risk in the following subsections
should be under a separate header. Generate new
subsections as necessary for each risk from 4.1
through 4.x.) Provide a risk name and identifier here
for reference in the remainder of the subsection.
4.x.1
Risk Category: Identify the category of
risk (physical, communications, hardware,
software).
4.x.2
Risk Impact: Provide an assessment of the
magnitude of the risk's impact in the event
of an occurrence.
4.x.3
Potential Safeguard(s)
4.x.3.y
[Safeguard Name]: (Each safeguard in this
subsection should be under a separate
header. Generate new subsections as
necessary for each safeguard from 4.1.3.1
through 4.x.3.y.)Provide a name and
identifier here for the potential safeguard
for reference in the corresponding
subsection of 5.x and describe the
safeguard.

REVIEWER
COMMENTS

REQUIREMENT

To be completed by Author
AUTHOR
X-REFERENCE
AUTHOR COMMENTS
Page #/Section #

To be completed by Reviewer
COMPLY
Y

5.0 COST AND EFFECTIVENESS OF SAFEGUARDS

5.x Potential Safeguards: (Each safeguard in this section
should be under a separate header. Generate new
sections as necessary for each safeguard from 5.1
through 5.x.)Review each of the safeguards identified
in the corresponding subsection of 4.x.3.y and
determine whether it is appropriate for use within the
systems operational environment.
5.x.1
Lifecycle Costs for Acceptable
Safeguards: Estimate the cost to develop,
install, and operate each of the proposed
system safeguards.
5.x.2
Effect of Safeguards on Risks: Estimate
the extent to which the recommended
safeguard will be effective in preventing or
minimizing that threat or vulnerability for
each of the proposed systems identified
risks and vulnerabilities.
5.x.3
Economic Feasibility of Safeguards:
Contrast the lifecycle costs of each of the
potential safeguards against the financial
impact of the security risks they are
designed to prevent.
6.0 RISK REDUCTION RECOMMENDATIONS
Outline the potential security risks to the system to be
developed or replaced and provide a detailed
description of the security safeguards that are being
recommended to counteract those risks.

REVIEWER
COMMENTS

Setelah mendapatkan dokumen checklist maka selanjutnya adalah mendapatkan checklist analisis resiko, table ini akan berupa pertanyaan yang harus
diisi apaakah ya atau tidak, dan ditambah kolom komentar, ini akan sangat membantu project manager dan tim yang akan menganalisis resiko yang
akan terjadi, contoh dari checklist analysis resiko:

Jika sudah mendapatkan jawaban dari pertanyaan-pertanyaan yang diajukan maka selanjutnya adalah menganalisis dari data-data yang sudah ada untuk
meminimalisir terjadinya kecelakaan kerja.

Daftar Pustaka

http://www.google.com/url?q=http://portal.hud.gov/hudportal/documents/huddoc%3Fid
%3DDOC_15130.doc&sa=U&ei=3_BkU8jdI9edugT714CgDA&ved=0CCgQFjAB&usg=AFQjCNEoR88EBski34qyRU_w1rgVVvaeFQ
http://www.justgetpmp.com/2012/02/checklist-analysis-is-one-of-tools-and.html