knitr::opts_chunk$set( collapse = TRUE, comment = "#>" )
Working notes for building a risk assessment process using the Evaluator toolkit. This vignette details the basic flow used at some organizations to maintain reproducability of inputs and results. While other technologies and solutions may be employed, this workflow is intended to be easy to implement for users familiar with source control principles.
create_templates()
domains.csv
file to include the domains (and their abbreviations) which are appropriate for your
risk domain and organization.survey.xlsx
spreadsheet to include the risk scenarios and the threats
for each scenario which you wish to monitor on an ongoing basis.If using the sample workflow, you will have two subdirectories located under
a parent evaluator
directory in your home folder. inputs
contains the
qualitative scenarios and input data files, while results
stores the
simulation results, including the summarized data files. Both directories
together represent an analysis snapshot.
When using create_templates()
a run_analysis.R
file will be placed at the base
of the evaluator
directory. A sample ultra-quick workflow looks like:
evaluator::create_templates("~/evaluator")
base_dir <- "~/evaluator" source("~/evaluator/run_analysis.R")
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.