- work in progress -

Skip to end of metadata
Go to start of metadata

Requirements are used to check the buildings blocks in iteraplan for compliance. Every requirement defines a data filter that determines which building blocks it affects. After the requirement creation security surveys are sent out to building block owners.

Requirements List View

The toolbar for the list contains different categories (2-6) for a better overview.

  1. List view tab
  2. Filter Category:
    1. Number of filtered elements to maximum elements
    2. Quick search
    3. Show only active requirements filter switch
    4. Reset button to reset only the Filter Category (only visible if the list is filtered)
  3. View Category:
    1. Add a column
    2. Reset button in the right upper corner to reset only the View Category (only visible if the view is not the default state)
  4. Edit Data Category:
    1. Create new requirement
  5. Use for Category:
    1. Export the current list  
  6. Reset Category:
    1. Resets Filter- and View-Category and resets the selected Query

Create a New Requirement

  1. General information 
  2. Status of the requirement
  3. Affected building block
  4. Responsibility for affected building block
  5. Save and cancel buttons

The affected building block sections allow you to specify which building blocks should be checked in the scope of this requirement. It is possible to add entire building block types and further refine the selection using the filter button. It is also possible to preview which building blocks would currently be affected by the entered filter. However this is just a preview - the affected building blocks are selected using the defined filters, and change and adapt should the building block data change. 

The responsibility for affected building block types requires you to select a responsibility attribute for each affected building block type. This attribute is then used to determine the building block owner for each affected building block. The building block owner is the user that will receive the security survey. 

It is also possible to create requirement without building blocks and/or responsibility attributes selected. In this case, no risk identifications and no surveys will be created for a new requirement.

Requirement Single View

In single requirement view the user may observe all information related to the requirement

  1. Single requirement tab
  2. Risk identification objects
  3. Activate/deactivate button
  4. Delete button
  5. Create new button

The risk identification section (2) lists all affected building blocks related to the current requirement. This section is selected on the create new requirement page and is not editable.

Requirement Single View

  1. Resulting risks of the requirement
  2. Affected building blocks
  3. Responsibility for affected building block type
  4. Download button (CSV or Excel)

  • No labels