Digitec Specification Process

I'm being asked to give a quote on a job, now what?

The first step you must take as a developer BEFORE starting any project, job, or task, and BEFORE writing down any code, is to correctly identify the requirements that need to be fulfilled in order to satisfy the project, job, or task.

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

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:

REF - Key words for use in RFCs to Indicate Requirement Levels

REF - OGS Design Procedures Manual - Specifications Language

Specifications are printed documents that establish procedures and requirements for a particular project. Specifications are legally enforceable as contract documents and must be prepared with concern and respect of their legal status. Specifications should include the correct use of words and grammar with properly constructed sentences and paragraphs. Specifications must be clear, correct, complete, and concise using these guidelines:

1. Clear: Use correct grammar and simple sentences to avoid ambiguity. Carefully selected words to convey exact meanings.
2. Correct: Present information accurately and precisely.
3. Complete: Do not leave out important information.
4. Concise: Eliminate unnecessary words, but not at the expense of clarity, correctness, or completeness.

The process:

1. Discovery: gather as much information about the project as you can. Your goal is to