Consider formalizing the priorities of requirements. #51

Although this is not a formal standard, it may nevertheless clarify the document to formalize the different priorities of requirements by (1) consistently using defined terms, e.g., "must", "should" and "may" in sentences; and (2) stating in the introduction that this convention is followed. It is typical (though of course the practice is not obligatory) to use "must", "should" and "may", and to cite the definitions in RFC 2119.

However the formal priorities are implemented, an editorial review of the document would be needed to ensure consistent use of teh chosen terms, and a paragraph would be included in the introduction to describe the convention chosen. Much of the work has been done informally already, thus modest additional work would be needed to formalize the convention used to prioritize the requirements.