Software Requirements Brief: What to Include

Commencez par un flux de travail, pas une liste de fonctionnalités.

Décrivez qui doit faire quoi, où le processus actuel devient difficile et quelles informations sont requises. Parcourez une tâche représentative du début à la fin. Capturez les exceptions ainsi que le chemin habituel. Cela donne à l’équipe une image partagée du travail avant de discuter des interfaces ou des plateformes.

Rendre visibles les décisions et les dépendances.

Identifiez les systèmes qui doivent se connecter, les personnes qui approuvent les modifications et les propriétaires de données qui doivent participer. Enregistrez les hypothèses qui doivent encore être vérifiées. Un dossier utile distingue les exigences connues des questions ouvertes, de sorte que les estimations ne dépendent pas silencieusement d'attentes non testées.

Définir un premier jalon révisable.

Convenez de la plus petite portée qui produit quelque chose que les parties prenantes peuvent inspecter : un prototype de flux de travail, un contrat d'interface ou une tranche de travail d'une application. Précisez ce qui rend cette étape acceptable. Incluez la personne chargée de l’examiner et les informations dont elle aura besoin pour prendre la décision.

Planifier au-delà de la démonstration.

Discutez du déploiement, de l'accès, de la documentation et de la maintenance avant la fin de la livraison. Une démonstration de travail est un point de contrôle ; l'équipe a également besoin d'une compréhension claire de la propriété et de la prochaine étape. Incluez ces décisions dans le mémoire plutôt que de les laisser au transfert.

Turn a request into testable requirements

Begin with a named user and one job they need to complete. Write the normal sequence, then walk through a missing input, a rejected request and an interrupted session. For each step, identify the information required and the system responsible for it. Separate essential behaviour from preferences about colours or layout.

Next, write acceptance criteria that a reviewer can demonstrate. For example: when a booking slot is unavailable, the user sees available alternatives and no duplicate appointment is created. Record the assumptions behind that behaviour, especially where another system controls availability. Discuss performance, accessibility and support expectations as explicit requirements rather than treating them as implied extras.

A reusable software brief outline

Use this outline in a shared document. Give each unresolved item an owner and a decision date; “to be confirmed” is useful only when someone is responsible for confirming it.

• Business problem: the workflow, affected users and reason a change is needed now.
• First-release scope: essential actions, excluded features and the boundaries of the proposed milestone.
• Data and integrations: source systems, record owners, permissions and external dependencies.
• Acceptance examples: a normal journey, an exception and the evidence required for approval.
• Delivery constraints: budget assumptions, timing dependencies, environments and stakeholder availability.
• Handover: documentation, operational ownership, support arrangements and outstanding decisions.

Common briefing mistakes

A list of screens can hide the business rules connecting them. “Add a dashboard” does not explain who uses it, how figures are calculated or what decision it supports. Ask those questions before estimating the feature.

Another mistake is treating an estimate as a fixed commitment while requirements remain unresolved. Keep assumptions attached to the estimate and review the effect of changes. Do not include passwords, customer records or confidential datasets in a first enquiry; describe their structure and arrange any necessary access separately.

Can a small project use a shorter brief?

Yes. A focused project may need only a concise document, but it still needs users, scope, acceptance examples and ownership. Reduce paperwork by removing irrelevant sections, while keeping the decisions that determine what will be delivered and how it will be accepted.

ILLUSTRATIVE PLANNING EXAMPLE

Example: an appointment-booking application

A clinic needs staff to book appointments and send confirmations. Write the brief around booking, rescheduling and cancellation, including who can see each record. Identify the existing calendar and the person who approves changes. For a first milestone, ask stakeholders to review one booking journey, including a fully booked time slot.

A useful output is a short brief with a workflow map, scope boundaries, unresolved integration questions and acceptance criteria. Keep patient records out of an initial enquiry.

FURTHER READING

Official resources to explore

Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.

• GOV.UK Service Manual: how discovery works