From 1a3475c135fff12e37600a783bc9b58329cf45ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=8Dtalo=20Oliveira?= <42980181+italojsoliveira@users.noreply.github.com> Date: Fri, 15 Dec 2023 22:35:54 +0100 Subject: [PATCH] update --- docs/Terminology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Terminology.md b/docs/Terminology.md index a1fe501..050f5e8 100644 --- a/docs/Terminology.md +++ b/docs/Terminology.md @@ -74,7 +74,7 @@ In ArchiMate, a *Control Measure* is represented by a *Requirement* with the ste **Examples:** Enforcing no-logs policy within a VPN company. Autoupdate feature of a piece of software. Warning signs nearby dangerous places inside a factory. -**Note:** A *Control Measure* is a *Requirement* and, as such, a proposition or statement. It is not a concrete thing. For example, the warning signs above correspond to the proposition regarding employing them; the warning signs themselves can be seen as *Security Mechanism*, placed by an implementation event assigned to a *Security Designer*. +📝 **Note:** A *Control Measure* is a *Requirement* and, as such, a proposition or statement. It is not a concrete thing. For example, the warning signs above correspond to the proposition regarding employing them; the warning signs themselves can be seen as *Security Mechanism*, placed by an implementation event assigned to a *Security Designer*. ### 4. Control Objective