Mandatory Should

Generally in specification documents RFC2119 [1] is used to define how the words must, should, may, etc are used.

In section 2.1.2.1 of http://streamreasoning.github.io/RSP-QL/RSP_Requirements_Design_Document/, we state mandatory requirements with should. This is not standard practice and implies that the mandatory requirement is not necessary. We should consider tightening up our language here. I would suggest the use of RFC2119 terminology and make this explicit.

Alasdair

[1] http://www.ietf.org/rfc/rfc2119.txt

Alasdair J G Gray
Fellow of the Higher Education Academy
Assistant Professor in Computer Science,
School of Mathematical and Computer Sciences
(Athena SWAN Bronze Award)
Heriot-Watt University, Edinburgh UK.

Email: A.J.G.Gray@hw.ac.uk<mailto:A.J.G.Gray@hw.ac.uk>
Web: http://www.macs.hw.ac.uk/~ajg33
ORCID: http://orcid.org/0000-0002-5711-4872
Office: Earl Mountbatten Building 1.39
Twitter: @gray_alasdair

________________________________

Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With campuses and students across the entire globe we span the world, delivering innovation and educational excellence in business, engineering, design and the physical, social and life sciences.

The contents of this e-mail (including any attachments) are confidential. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system.