Sabot employs our structured Knowledge Acquisition Process (KAP) to discover and document functional and technical requirements. In consideration of the complexity of today’s business practices and technology environments, well-written requirements are key to project success.

Our requirements are written to be:

  • Necessary – Each requirement has a purpose and describes a critical function or attribute.
  • Unambiguous – Has one and only one interpretation.
  • Concise – Includes only one requirement, stating what must be done and only what must be done, stated simply and clearly. It is easy to read and understand.
  • Implementation-Free – Describes what is required, not how the requirement should be met.
  • Unique – Requirement is not redundant with another requirement.
  • Complete – Includes all information and references, conforms to documentation standard, and includes a unique identifier. Also refers to the completeness of the aggregate set of requirements completely describing the system.
  • Verifiable – Each requirement is testable to know that it has been met.
  • Consistent – Has no internal conflicts and no conflicts with other requirements.
  • Modifiable – Structure and style facilitate making and tracking changes.
  • Traceable – Rationale and origin are included or referenced. Structure facilitates referencing in design, development, and test scripts.

Our specifications are written to be included in bids and contract documents. We support active requirements management (RM) practices including the use of RM tools.