Sam Crawford

The same information is in the _current_ Output-Values requirement, but isn't in the new one generated by the existing commented-out code. My comment above also assumes that we want the...

Yes, but the issue I'm having is where to put it so that it can be "pulled out" and generated automatically, instead of manually being supplied by the user when...

That makes sense - an initial look makes me think that `InstanceModel`s can be used as the outputs in `SystemInformation`, but this has consequences in terms of the definitions attached...

@smiths If there is only one output, should we change the generated requirement's text from "values" to "value" or do something else?

@smiths Some questions about SWHS: 1. Some examples have the calculations of values grouped as one requirement (same with their output), like Projectile:  However, SWHS has a separate requirement...

> an initial look makes me think that `InstanceModel`s can be used as the outputs in `SystemInformation` And it was just as easy as that!  However, it leads to...

Just noting that the above change was made in 05f9eb3, along with "fixing" the term/definition of `offset`, which I think improves the generated documentation. Would we want a custom constructor...

@balacij While working on this issue, I noticed some changes to the stable JSONs for seeds and the DOTs for traceability matrices. It seems like there are new dependencies (?)...

Interestingly, none of the seeds/dependencies were changed for generating the requirement for GlassBR 🤔

In response to the first paragraph: As far as I understand, specifying the outputs identifies which quantities should be output by the output module during code generation. The design that...