Skip to content

Solution Brief Template

Use this page to structure the brief students submit at the start of the SAT.

How to use this template

Copy the heading structure into a Word or Google Docs document. Replace all prompt text with writing that is specific to the student's own project.

Cover Information

Field Student entry
Project title
Student name
Class
Teacher
Date
Version

1. Problem, Need or Opportunity

Write a short paragraph that clearly explains:

  • what the real-world problem, need or opportunity is
  • where it exists
  • who is affected by it
  • what is currently inefficient, missing or frustrating
  • why it is worth solving

Student writing prompt

Describe the problem, need or opportunity in specific terms. Avoid vague statements such as "there is no good system". Explain the current situation and the gap that your software will address.

2. Why a Software Solution Is Needed

Write a short explanation of why software is an appropriate response.

You should address points such as:

  • how a software solution could improve productivity or efficiency
  • how it could reduce time, duplication or errors
  • how it could improve access to information
  • why a software solution is more suitable than the current process

Student writing prompt

Explain why software is the right kind of solution for this situation, not just why the problem exists.

3. Intended Users and Client

Identify the people who will use, benefit from or approve the solution.

Primary user or client

  • Who is the main user?
  • What do they need the software to help them do?
  • What is their current level of technical skill?

Secondary users

  • Who else may use the software?
  • What role will they have?
  • What do they need from the solution?

Student writing prompt

Describe the users in enough detail that someone reading the brief can understand who the software is being designed for and what they need from it.

4. Proposed Software Solution

Write a short overview of the type of software you plan to create.

Include:

  • what the software will broadly do
  • the main tasks it should support
  • the kind of interface or interaction it will have
  • the main benefit it should provide to the user

Student writing prompt

This is not the full SRS. Keep it high level. Focus on the general direction of the solution.

5. Programming Language and Software Tools

State the programming language or languages you plan to use.

Include:

  • the main language
  • any additional languages, frameworks or tools if relevant
  • why this choice is appropriate for the project
  • whether the language matches the software tools and functions requirements

Student writing prompt

Explain why this language is suitable for the proposed solution, not just that it is the language used in class.

6. Relevant Programming Language Features

Briefly identify the programming features you expect the solution to use.

This could include items such as:

  • classes and objects
  • functions or methods
  • variables and data structures
  • file handling or data sources
  • validation
  • interface components

Student writing prompt

Link the language features to the kind of solution you are planning to build.

7. Feasibility

Technical feasibility

Address:

  • whether the software can be built with the available tools
  • whether the required hardware and software are available
  • whether the student's skill level is suitable
  • any technical risks or limitations

Time feasibility

Address:

  • whether the project is realistic within the SAT timeline
  • which parts may take the longest
  • any areas that may need to be simplified to stay achievable

Operational feasibility

Address:

  • whether the user will be able to use the solution in practice
  • whether the environment where it will be used suits the software
  • whether training or instructions may be needed

Resource feasibility

Address:

  • what equipment, software, files, data sets or support will be needed
  • whether those resources are available now

Student writing prompt

Be honest here. A feasible project is better than an over-ambitious one that cannot be finished.

8. Originality

Explain what makes the proposed solution different from, or better suited than, existing options.

You could address:

  • features tailored to a specific user or setting
  • simplification of an existing process
  • a gap in current solutions
  • a more suitable interface, workflow or delivery method

Student writing prompt

Originality does not have to mean something never seen before. It can also mean a better fit for a particular client, community or context.

9. Brief Summary Statement

Finish with a short summary paragraph that brings the brief together.

It should restate:

  • the problem, need or opportunity
  • who the solution is for
  • what kind of software is proposed
  • why it is feasible and worth developing

Final Check Before Submission

  • [ ] The problem, need or opportunity is real and clearly explained.
  • [ ] The users or client are clearly identified.
  • [ ] The proposed software direction is clear.
  • [ ] The programming language choice is justified.
  • [ ] Relevant language features are mentioned.
  • [ ] Feasibility is addressed realistically.
  • [ ] Originality is addressed.
  • [ ] The document is concise and readable.
  • [ ] Dates and version number are included.