Publish log entry

1 files changed, 48 insertions, 0 deletions

diff --git a/blog/2019/09/22/subplot_and_requirement_tracking.mdwn b/blog/2019/09/22/subplot_and_requirement_tracking.mdwn
new file mode 100644
index 0000000..312d9d0
--- /dev/null
+++ b/blog/2019/09/22/subplot_and_requirement_tracking.mdwn
@@ -0,0 +1,48 @@
+[[!meta title="Subplot and requirement tracking"]]
+[[!tag planning]]
+
+This is an idea, and not planned to be implemented any time soon. It's
+saved here to inform futur discussions.
+
+# Tracking requiremens in Subplot
+
+First, assign each requirement a unique mnemonic id. In this example,
+it is the word in the definition list below. The "Req" suffix is just
+a convention.
+
+**SecureReq**
+: System must be sequre.
+
+**FastReq**
+: The system must be fast.
+
+# First scenario tests SequreReq only {#first .SequreReq}
+
+Second, mark each scenario with the requirements it tests. First
+scenario test the SequreReq requirement.
+
+~~~{.subplot .SequreReq}
+given a system
+when it is attacked
+then it is unharmed
+~~~
+
+# Second scenario also tests FastReq {#second .SequreReq .FastReq}
+
+~~~{.subplot .SequreReq .FastReq}
+given a system
+when it is DDoSsed
+then it is unharmed
+and it still serves all legitimate users
+~~~
+
+# Output
+
+Subplot will then annotate the output so that each requirement has
+links to the scenarios that test them, something like this: 
+
+**SecureReq** ([first](#first), [second](#second))
+: System must be sequre.
+
+**FastReq** ([second](#second))
+: The system must be fast.