@rse/specbook 1.5.1 → 1.5.2

package/dst/specbook-format.yaml

@@ -751,26 +751,54 @@
     file: 07-REQS-NR-Non-Functional-Requirements.md
     desc: >
         The quality attributes and constraints the solution must satisfy, such as performance,
-        security, scalability, reliability, and usability.
+        security, scalability, reliability, and usability. The requirements are optionally grouped
+        into the project-specific quality goals they refine (the upper levels of a quality attribute
+        utility tree), which the overview diagram draws as boxes around their requirements.
     optional: true
     refs: >
         -   ISO/IEC 25010:2023: Systems and software engineering -- Systems and software Quality Requirements and Evaluation (SQuaRE) -- Product quality model (2023),
             https://www.iso.org/standard/78176.html
         -   ISO/IEC/IEEE 29148:2018: Systems and software engineering -- Life cycle processes -- Requirements engineering (2018),
             https://www.iso.org/standard/72089.html
+        -   Bass/Clements/Kazman: Software Architecture in Practice, 4th ed.: Quality Attribute Utility Tree (2021),
+            https://www.informit.com/store/software-architecture-in-practice-9780136886099
         -   DSDM: MoSCoW Prioritisation, DSDM Agile Project Framework (2014),
             https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html
         -   Doran: There's a S.M.A.R.T. Way to Write Management's Goals and Objectives, Management Review 70(11) (1981)
     diagram:
         type: grid
         nodes: "[[NR.REQUIREMENT:*]]"
+        nest:
+            properties:
+                -   GROUP
         properties:
             -   PRIORITY
             -   CATEGORY
         config:
             size-node-width-max: 440
-            grid-columns-max: 4
+            grid-columns-max: 2
     children:
+        -   kind: GROUP
+            desc: >
+                A named group of requirements jointly refining one project-specific quality goal,
+                carrying a short (1-3 word), per-artifact unique name distinct from the names of its
+                requirements (e.g. `Observability` for the completeness, causality, integrity, and
+                availability of the recorded traces, `Data Protection` for the lawful, minimal, and
+                guarded processing of personal data), and described by a 1-sentence description
+                ("what") of the quality goal the requirements add up to plus a 1-sentence rationale
+                ("why") of the cohesion. A group is a quality goal in the sense of a quality
+                attribute utility tree: unlike the fixed `CATEGORY` of a requirement, which
+                classifies it for comparability, it names the quality the project itself strives
+                for and may span requirements of several categories. It is distinct from a
+                Functional Requirements group, which bundles the functions and mechanisms
+                realizing such a quality. A group carries no obligation of its own: it has no
+                priority, no metric, and is verified through its requirements alone, so it
+                affects the overview diagram only, where its requirements are drawn next to each
+                other inside a box. The groups are listed before the requirements, and every
+                requirement belongs to at most one group.
+            optional: true
+            referenced:
+                -   "[[NR.REQUIREMENT:*]]"
         -   kind: REQUIREMENT
             desc: >
                 A single non-functional requirement, named with a short (3-8 word) summary and
@@ -797,8 +825,8 @@
             diagram:
                 type: hub
                 center: self
-                nodes: "[[NR.REQUIREMENT:*]], [[FR.REQUIREMENT:*]], [[PREMISE:*]], [[RULE:*]],
-                    [[TACTIC:*]], [[DECISION:*]], [[CONCERN:*]], [[TEST-CASE:*]]"
+                nodes: "[[NR.GROUP:*]], [[NR.REQUIREMENT:*]], [[FR.REQUIREMENT:*]], [[PREMISE:*]],
+                    [[RULE:*]], [[TACTIC:*]], [[DECISION:*]], [[CONCERN:*]], [[TEST-CASE:*]]"
                 labeled: true
                 qualified: true
                 config:
@@ -826,6 +854,14 @@
                         e.g. a hosting, budget, or technology mandate, as opposed to a constraint
                         on the domain, which is a Domain Rule).
                     value: enum(Performance,Compatibility,Usability,Reliability,Security,Safety,Maintainability,Flexibility,Compliance,Constraint)
+                -   name: GROUP
+                    desc: >
+                        Reference to the NON-FUNCTIONAL-REQUIREMENTS group (the quality goal) the
+                        requirement belongs to, placing it next to the other requirements of the
+                        group in the overview diagram, independent of its `CATEGORY`; omitted for a
+                        requirement standing on its own.
+                    value: "[[NR.GROUP:*]]"
+                    optional: true
                 -   name: QUALIFIES
                     desc: >
                         Comma-separated references to the FUNCTIONAL-REQUIREMENTS objects whose

package/package.json

@@ -1,6 +1,6 @@
 {
     "name":                                "@rse/specbook",
-    "version":                             "1.5.1",
+    "version":                             "1.5.2",
     "publishConfig":                       { "access": "public" },
     "description":                         "Markdown-based Specification Format (API, CLI and MCP service)",
     "license":                             "Apache-2.0",
@@ -31,7 +31,7 @@
         "@d2lang/d2":                      "0.1.34",
         "shiki":                           "4.5.0",
         "pdfjs-dist":                      "6.4.299",
-        "@napi-rs/canvas":                 "1.0.10",
+        "@napi-rs/canvas":                 "1.0.11",
         "@toon-format/toon":               "4.4.0",
         "valibot":                         "1.5.0",
         "nunjucks":                        "3.2.4",