1. Introduction
    1. Licensing
    2. System Requirements
    3. Setup and Installation
  2. Getting Started
    1. Creating the Database
    2. RM Studio Users/Contacts
    3. Email Configuration
    4. Web Module Setup
    5. Web Module Update
  3. Navigating RM Studio
    1. Main Menu
      1. Save Function
      2. Import External Data
        1. Import Assets
      3. Clear User Cache
      4. Security
      5. Properties
      6. Languages
      7. Registration
      8. User Manual
      9. Manage Checkouts
      10. About
      11. Application Style
    2. Navigation Tree
    3. Tabs
    4. The Grid
    5. Context & Flow
  4. Common Entities
    1. Business Entities
      1. Asset Details - Basic Information tab
      2. Asset Details - Risks tab
      3. Asset Details - Categories tab
      4. Asset Details - Business Entities tab
    2. Contacts
    3. Teams
    4. Categories
    5. Assets
    6. Threats
    7. Standards/Controls
      1. How to: Standards, Regulations, Controls
      2. Standards Implementation Comparison
    8. Documents
  5. Gap Analysis
    1. How to: Gap Analysis
    2. Reporting
  6. Risk Assessment
    1. How to: Risk Assessment
      1. Working with Assets
      2. Evaluation Values
      3. Evaluating Risks
      4. Various Definitions
      5. Risk Assessment Reporting
    2. Evaluation Templates
    3. Risk Owner Web Solution
  7. Web Module
    1. Dashboard
    2. My Tasks
    3. Reports
    4. Standards/Regulations
    5. Documents
    6. Incidents
    7. Risk Owner Web Solution
  8. Control Maturity and Effectiveness Assessment
    1. Control Assessment Templates
    2. Reporting
  9. Risk Treatment
    1. How to: Risk Treatment
      1. Risk Treatment Templates
      2. Risk Criteria
      3. Asset Level
      4. Controls Tab
      5. Scheduling a Future Control
      6. Future Controls Tab
      7. Overview
      8. Reload Assets, Threats and Controls
    2. Risk Treatment Reports
  10. STPA
    1. Intro to Models, Diagrams, Analyses
    2. STPA Projects
    3. Models and Diagrams
      1. How to: Create HCS Models
      2. How to: Create HCS Diagram
        1. Diagram Elements
    4. Performing the Analysis
      1. Setting up the Analysis
      2. System Level Hazards and Losses
      3. Step 1
    5. Reporting
  11. Business Continuity Management Module
    1. Organization
      1. New Organization
      2. Stakeholders
      3. Resources/Processes
        1. Impact Analysis
        2. Requirements
    2. Incident Response/Recovery
      1. Associated Threats
      2. Plans
        1. Steps
      3. Maintenance
        1. Test plans
        2. Test Results
    3. Templates
    4. Maintenance
    5. Reports BCM
  12. Database Settings
    1. Database Upgrade
    2. Add Existing
    3. Remove
    4. Migrate
    5. Backup
    6. Restore
  13. Glossary
  14. Calculations

10.1.Intro to Models, Diagrams, Analyses

One very important feature that is important to note is the STPA Module differentiates between models, diagrams and analyses.

The starting point of any STPA project is the Hierarchical Control Structure (HCS), which represents an explicit model of the system under analysis. Usually the HCS is represented as a diagram. However, a single HCS diagram does not represent the complete information of the model:

  • Descriptions accompanying the modelling elements are not shown on the HCS diagram,
  • In certain cases, more than one diagram can be used to represent the system under analysis.

The STPA Module differentiates between the HCS Model and the HCS Diagram belonging to this model. The STPA Module also provides different ways of viewing the model information. The most common is certainly to view the HCS by viewing the respective diagrams. However, the STPA Module allows users to view the model also in the form of listings.

Besides the HCS model and HCS diagrams the STPA Module allows creating an analysis featuring STPA Steps 1 and 2. Every analysis references one or multiple HCS models.

In the above illustration the STPA project (called “my STPA Project”) contains two HCS models labelled “Model 1” and “Model 2” and one analysis labelled “Analysis 1”. The analysis references the “Model 1,” which features two diagrams, “Diagram 1a” and “Diagram 1b”. For the second model, featuring only one diagram, no analysis exists.

The differentiation between models, diagrams, and analyses is made to provide maximum flexibility to the analyst:

  • A project may contain multiple models and/or analyses
  • A model may be represented by multiple diagrams
  • An analysis may refer to one single model or multiple model
  • Multiple (separate) analyses may be performed for the same model

The STPA Project Overview panel in the STPA Module displays the structure of models, diagrams, and analyses as shown here:

Help Guide Powered by Documentor
Suggest Edit