Derive "Characteristics of Intended Reader" and "User Characteristics"

[smiths]

@JacquesCarette had the neat idea that rather than explicitly write the sections on reader and user characteristics this information could be derived from the model itself. If each new theory, definition, equation etc had a class and level of knowledge associated with it, then this information could be combined to automatically fill in the "characteristics" sections of the template. The user characteristics might be derived only from the instance models, whereas the reader (reviewer) characteristics would depend on all parts of the SRS.

This isn't something to worry about in the short term, but a nice idea for the longer term.

[JacquesCarette]

Should go in a 0.3.0 milestone.

[JacquesCarette]

The longer term may be this summer. I think this is a great example for illustrating "what this sentence means" kind of knowledge capture. I'll assign this to myself right now, but with the intent to get various people to tag (using our shiny new attributes) various pieces of information with class/level, so that this can be derived.

[smiths]

Discussed this issue in a weekly meeting: https://github.com/JacquesCarette/Drasil/discussions/2923.

If we had the data where we knew for each "fragment" of knowledge the required education background, we could calculate the education background needed for every artifact that we generate (not just for the SRS and the executable program).