Software Specification Review Check List

· Do stated goals and objectives for software remain consistent will system goals and objectives.
· Have important interfaces to all system elements been described?
· " Is information flow and structure adequately defined for the problem?
· Are diagrams clear? Can each stand alone without supplementary text?
· Do major functions remain within scope and has each been adequately described?
· Is the behaviour of the software consistent with the information it must process and the functions it must perform?
· Are design constraints realistic?
· Have the technological risks of development been considered?
· Have alternative software requirements been considered?
· Have validation criteria been stated in detail? Are they adequate to describe a successful system?
· Do inconsistencies, omissions, or redundancies exist?
· Is the customer contact complete?
· Has the user reviewed the preliminary user's manual or prototype?
· How are planning estimates affected?
· Be on the lookout for persuasive connectors (e.g., certainly, therefore, clearly, obviously, it follows that), and ask 'why?"
· Watch out for vague terms (e.g., some, sometimes, often, usually, ordinarily, most, mostly); ask for clarification.
· Watch lists are given, but not completed, be sure all items are understood. Keys to look for: 'etc., and so forth, and so on, such as."
· Be sure stated ranges don't contain unstated assumptions (e.g., Valid codes range from 10 to 100. Integer? Real? Hex?).
· Beware of vague verbs such as "Handled, rejected, processed, skipped, eliminated.' They can be interpreted in many ways.
· Beware ambiguous pronouns (e.g., The I/O module communicates with the data validation module and its control flag is set. Whose control flag?)
· Look for statements that imply certainty (e.g., always, every, all, none, never), then ask fur proof.
· When a term is explicitly defined in one place, try substituting the definition for other occurrences of the term.
· When a structure is described in words, draw a picture to aid in understanding.
· When a calculation is specified, work at least two examples.