| ... | ... | @@ -7,7 +7,7 @@ The first step you must take as a developer BEFORE starting any project, job, or |
|
|
|
### The Guidelines:
|
|
|
|
---
|
|
|
|
For large projects we use an abbreviated form of the IEEE SRS standard which relies on the functional requirements section. This document is also a great overall reference for learning about software specifications.
|
|
|
|
###### REF - [830-1998 - IEEE Recommended Practice for Software Requirements Specifications](https://vc.digitec.local/digitec/digitec-wiki/blob/master/wiki-assets/files/IEEE%20830-1998-SRS-template.pdf)
|
|
|
|
###### REF - [830-1998 - IEEE Recommended Practice for Software Requirements Specifications](https://vc.digitec.local/digitec/digitec-wiki/blob/master/wiki-assets/files/specification/IEEE%20830-1998-SRS-template.pdf)
|
|
|
|
---
|
|
|
|
In every specification, unambiguous language is of paramount importance and to that end it is useful to reference the Key words RFC which clearly specifies the use of the words:
|
|
|
|
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
|
| ... | ... | |
