Skip to content
⁨NDDev Dev⁩, home page
Community
Language: English
Display
Theme
Motion

Software requirements specification

NDDev writes the software requirements specification for the projects we build, and writing it is part of the project price. The specification has ten sections, from goals and user roles to acceptance criteria and a list of what the project leaves out. Experience from our team’s 100+ projects helps us spot gaps before work begins.

Who it is for

Companies ordering software for the first time, or that have seen vague requirements push timelines and prices off course. Public-sector clients who need a specification to GOST 34.602.

  • Part of the project price
  • Numbered requirements by module
  • Acceptance criteria before work starts
  • GOST 34.602 structure for public clients

Specification sections and the rules for requirements

We write requirements to ISO/IEC/IEEE 29148: each one unambiguous, verifiable, singular, feasible and necessary. They are numbered and grouped by module, and each follows the pattern “condition, system action, object, constraint”. For example: “When the form is submitted, the system saves the request to the database within 2 seconds.”

  • project goals and a glossary of terms
  • user roles
  • numbered functional requirements by module
  • non-functional requirements: load, security, devices
  • integrations and each side’s responsibilities
  • design requirements
  • stages, timelines and acceptance criteria
  • a list of what the project leaves out

Every requirement links to an acceptance criterion, and every criterion to an item on the handover checklist. At handover you check the finished product against the same document you ordered it by. The section on what the project leaves out protects the timeline and price from scope creep.

For public-sector clients we put the same content into the GOST 34.602 structure, and the work follows a waterfall model with fixed requirements.

How a specification comes about

We go through the questions together on a call: a live conversation clears up the ambiguities a written questionnaire leaves behind.

  1. Talking about your business

    Twelve questions in four blocks: your business, what already exists, budget and timeline, and who accepts the work. We write the answers down straight away.

  2. Draft

    We put together a draft specification, describe roles and modules and mark the open questions.

  3. Agreement

    We go through the document with you and refine the requirements and acceptance criteria.

  4. Proposal

    Together with the specification you receive a proposal with MVP and full version options, each with its price and timeline.

Questions about the specification

How much does a specification cost?

For projects we build, the specification is part of the project price. If you need only the document, describe the task and we will name the scope of work and the price separately.

We already have a specification. What now?

Send it over. We will check the requirements for clarity and completeness, mark the gaps and suggest additions before the estimate.

Do we need to understand the technical side?

Knowing your business is enough. We ask the technical questions and turn your answers into requirements.

Can requirements change after the specification is approved?

Yes, through a change request: we assess how the change affects the timeline and price and record it in writing.

How long does writing a specification take?

The size of the product sets it, and we give the timeline after the first conversation.

Software consulting

Start your specification with one call

Describe the task in a few sentences. We will suggest a time to talk about your business and the next step.

We reply within 24 hours

Assistant

Loading the assistant…