Upload the cfr.json for Wallet specification v1.0.0 #4
Description
What:
To get a machine-readable version of Chapter 5: Cross Functional Requirements for Wallet BB, Produce a cfr.json for wallet v1.0.0 that echoes the structure in functionalities.json where there is a container to functionalities and requirements that belong to each functionality.
Why:
Data structures on other specs expect requirements to be standalone, where the Heading is the requirement with the requirement level at the send of the sentence and any paragraphs below it are informational. See example on Payments BB:
However, Wallet BB uses Headings as containers and denotes requirements inside each. See screenshot below. This structure mirrors the way Chapter 4: KDF and Chapter 6: FR work. Therefore this task requires a machine-readable version of cfr.json to be produced for wallet spec in this form.
Context:
On the Testing Web App, the script for extracting Cross-Cutting requirements failed for the Wallet specification, as the parser expected requirements to be denoted using Headings (see: the relevant parser line) however the WG chose to organize the CFRs using Headings for containers and bullet points for requirements. This means that we needed to define a way to denote CFRs in a machine readable way that was compatible. This conversation led to discuss on arch-WG how to distinguish CFRs from FR. (see this proposal) and then commit 33a9f5bd9318837b50329589f4b0760c46311293 on CFR-Architecture.
On this version of wallet CFRs will be denoted to be compatible to the testing-web app, but as GovStack CFR-Architecture goes into version 2.0 the data structure should change to reflect that.