Software project planning

How to Write Software Requirements

Turn a business process into a brief your team can build and test. Use the software requirements template and a worked approval example to define scope, permissions and acceptance criteria.

What goes into a software requirements brief?

A requirements brief describes the business outcome, the people doing the work, the steps they follow and how your team will accept the result. Start with a real record or request. Follow it from the first action to the point where everyone who depends on it has the information they need.

Define the first release

Pick one workflow the team can complete end to end. Name its owner, users and success measure. For example, track how long a valid discount request waits for a decision. Record requests such as mobile notifications or extra reports under a later release if the first workflow can run without them.

Map the roles and rules

Give each action a responsible role and list the records that role can see or edit. A manager might approve a discount while sales owns the order. Specify thresholds, cancellation, reassignment and what happens when someone acts on an outdated version.

Plan data, integrations and quality

Identify which system owns each identifier and which records must move into the new system. Capture availability, response time and audit history needs as measurable targets where practical. Decide what a user sees when an integration is delayed and how the team confirms recovery.

Worked example: a sales discount approval workflow

Suppose sales can quote a discount of up to 10% without finance approval. A larger discount needs an approval decision before the order is sent. The threshold and permissions below are illustrative. Agree the actual rules with sales and finance before estimating development.

  1. Sales submits the requestCapture the order reference, proposed discount and reason. Keep the original order values with the request.
  2. Finance reviews and decidesFinance can approve or decline the request and add a decision note. Sales can withdraw a pending request.
  3. Sales sees the outcomeShow the status and decision history. A change after approval requires a new revision and another decision.

Acceptance criteria your team can test

Boundary and approval

Given an eligible salesperson prepares an order, when they submit a 10% discount, then the order can proceed without a finance task. A discount of 10.01% creates one pending approval and prevents sending the order until it is approved.

Permissions and rejection

Given a pending request, when finance declines it, then sales can see the decision and reason. The original order stays unchanged and the discounted order cannot be sent.

Revision and audit history

Given a request has been approved, when sales changes the requested discount, then the system retains the original approval and sends the new revision for review. Both versions record who acted and when.

Software requirements template

Copy these prompts into your project brief. Use realistic sample inputs and identify who can answer each open question.

Goal and success measure
What should improve? Record a baseline if you have one, such as the current time from submission to approval.
Users and permissions
Who submits, reviews, edits or exports? Note branches, approval limits and alternate owners.
Workflow and exceptions
Describe a normal case, a rejected case and a correction. Mark what starts and ends each status.
Data and integrations
List required fields, source systems, import decisions and how users handle missing or delayed records.
Release boundaries
Put first-release items, later items and open questions in separate lists. Assign an owner to each dependency.
Acceptance and handover
Write testable outcomes and name the reviewer. Include reporting, account ownership and operational handover.

Scope your software project with CESAWS

Share your current process, a sample record and what the first release needs to do.

Discuss your requirements