Need relationship to capture assumption of use

[kestewart]

In working through requirements, the concept of assumption of use needs to be captured, in order to express the necessary information.

We need a relationship, so that "Assumptions" can be linked to Code & Requirements.

[kestewart]

@nicpappler - for discussion on FuSA call.

[kestewart]

Here is a breakdown of the definition according to SWEBOK-aligned literature:
Nature of Assumptions: Assumptions are considered in the light of insufficient or unavailable information, vague requirements, or to manage uncertainty, allowing development to progress without waiting for complete information.
Artifact Type: Assumptions are treated as a type of software artifact (like requirements or design decisions) that need to be documented and managed.
Distinction from Proof: Unlike specifications or requirements, assumptions are not given to a developer as part of a finalized, verified list. They represent beliefs that may or may not come true.
Types of Assumptions: SWEBOK-aligned literature characterizes these into several types:

• Control Assumptions: Expectations on control flow or order of operations.
• Environment Assumptions: Expectations about the operating environment (e.g., database versions, hardware).
• Data Assumptions: Expectations regarding the format, range, or nature of input/output data.
• Usage Assumptions: Expectations about how the user will interact with the system