Dictionary
Some concepts of verinice.veo have different names depending on the context, e.g. depending on whether one interacts with the user interface, uses the Web-API or works with the source code. One possible reason for deviating terms can be that a word already has connotations in a certain technical context (e.g. “object” in object-oriented programming) and has therefore been replaced with another term. It is also possible that in the course of the agile development process, a term proves to be unintuitive or not appropriate and is then renamed, but the old term continues to be used in certain software components.
| User Interface | Documentation | Web API | Code (veo-web) | a.k.a. |
|---|---|---|---|---|
| asset | asset | asset | asset | |
| catalog | catalog | catalog | catalog | |
| catalog element | catalog element | catalog item | catalog item | |
| control | control | control | control | |
| criterion | - | risk category | protection goal | |
| document | document | document | document | |
| domain | domain | domain | domain | |
| form / form schema | form | form | form / form schema | |
| impact | - | impact | impact | |
| incident | incident | incident | incident | |
| object | specialist object | element | object | entity |
| object schema | - | element type definition | object schema | |
| person | person | person | person | |
| process | process | process | process | |
| probability | - | probability | probability | probability |
| risk | risk | risk | risk | |
| risk value | - | risk value | risk value | |
| risk definition | risk definition | risk definition | risk analysis type | |
| scenario | scenario | scenario | scenario | |
| scope | scope | scope | scope | |
| target object | risk-bearer (see risk) | risk-affected | risk-affected | |
| unit | unit | unit | unit | |
| {control subtype} assignment | - | control implementation | control implementation | CI |
| - | composite | composite | composite | |
| - | - | requirement implementation | requirement implementation | RI |