capture requirements with traceability

[capsulecorplab]

stakeholder concerns & requirements page should be represented as both a collection of permalink-able statements, as well as a graphical requirements traceability diagram (as shown https://tetrabiodistributed.github.io/tetra/references/stakeholder-concerns-and-requirements/)

[capsulecorplab]

Capturing stakeholder needs in this manner will require a modeling language, s/a m30ml, for modeling stakeholder needs, user stories, supporting references, and their relationships https://github.com/Mach30/m30ml

[capsulecorplab]

The DOF repo itself already modeled in m30ml for modeling requirements in the form of stakeholder needs & user stories with metadata that includes derivedFrom elements for enabling requirements traceability

[mmroden]

Need to write requirements as a set of user stories, which may take some time, ie, four hours or so.