Struct Requirement

pub struct Requirement {
    id: String,
    text: String,
    method: VerificationMethod,
}

Each Requirement struct represents a formal “shall” statement whose evidence of verification is produced in a Step of a Process

Fields

id: String

Unique ID for the requirement

text: String

Full text of the requirement, which includes the word “shall.”

Example of good requirement wording:

(When [SUB/SYSTEM or VARIABLE] is [MODE/STATE or VALUE or RANGE],) [AGENT] shall [BEHAVE] (within [TOLERANCE]). (Note: [CLARIFYING NOTES OR REFERENCES])

method: VerificationMethod

Method of verification–how is this requirement to be verified? This is important for processes, because steps to produce evidence of verification should be steps that somehow resemble this verificaiton method.

Implementations

impl Requirement

Since Requirement structs are created directly in a function outside the struct at read-time, we just need “get” functions

pub fn get_id(&self) -> &String

Return reference to the Requirement ID string

pub fn get_text(&self) -> &String

Return reference to the Requirement Text string

pub fn get_method(&self) -> String

Return reference to the Verification Method as a string, even though that’s not how’s it’s stored