← QCE Digital Solutions Unit 3

Structure of a technical proposal

A structured document that sets out the problem, scope, constraints, requirements, criteria, data design and algorithm outlines in order, so a reader can approve the planned solution.

Part of: QCE Digital Solutions Unit 3 — Real-World Problems and Solution Requirements — Module 95

Understanding Structure of a technical proposal in QCE Digital Solutions Unit 3

What it does: Pairing a requirement with a measurable criterion shows how the finished solution will be judged against what was proposed. This ordered list shows the structure of a technical proposal, with each section building on the one before it. Sections run in a logical order. The reader needs to understand the problem and what will be built before they see any algorithms. An IPO chart outlines the data going in, the processing done, and the results produced. It belongs with the design. Pseudocode outlines the planned logic. The solution has not been developed yet at proposal stage. Ordered sections make the proposal easy to follow and easier to approve.

Common mistakes: Algorithm outlines come near the end, after requirements, criteria and data design. Line 3 should be the scope of the solution, so the reader knows what is included before the detail. The problem section describes the need, not a solution. 'Use a SQL database' is a design choice. It should state the issue, such as 'Problem: paper loans are slow'.

Class: _____________________ · Name: _____________________ · Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Structure of a technical proposal to a class →

This module's key terms are also in a printable crossword (Modules 194–250) and word search (Modules 194–337).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning

Duo

Which best describes a technical proposal?

A finished program with the source code handed over to the clientA structured document that sets out the problem, scope, requirements and design so a reader can approve the plan

Matches

Proposal: Algorithms, Data design, Requirements, Problem (no scope or constraints)

↓

The sections are out of order and key sections are missing. The problem should come first, and scope and constraints must be included.

Applying

Meanings

Term

technical proposal

Meaning

A structured document that sets out the problem, scope, constraints, requirements, criteria, data design and algorithm outlines in order, so a reader can approve the planned solution.

Practice

1. Problem and need

Testing

Gaps

2. of the solution

Check Answer

Spots

22. Aspect to develop

33. Algorithm outlines

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy

Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games

Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print

Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. Which best describes a technical proposal?

A. A structured document that sets out the problem, scope, requirements and design so a reader can approve the plan ✓

B. A finished program with the source code handed over to the client

A technical proposal comes before development. Its job is to get the planned solution approved.

2. Which order makes the most sense for the start of a technical proposal?

A. Problem, then aspect to develop, then scope ✓

B. Pseudocode, then problem, then scope

Sections run in a logical order. The reader needs to understand the problem and what will be built before they see any algorithms.

3. Where should the constraints section sit in a technical proposal?

A. At the very end, after the algorithm outlines, as an afterthought

B. Before the requirements, so the reader knows the limits the requirements must fit within ✓

Constraints shape what can be required, so they appear early in the ordered sections.

4. A proposal lists the requirement 'The app must respond to a search in under 2 seconds'. How should the evaluation criteria link to it?

A. A criterion states how the response time will be tested against the 2-second target ✓

B. A criterion says the app should look good, with no link to the requirement

Criteria should be linked to requirements so the finished solution can be judged against what was promised.

5. Which section of a technical proposal shows the inputs, processes and outputs of the planned solution?

A. The stakeholder list in the problem section

B. The IPO chart in the design section ✓

An IPO chart outlines the data going in, the processing done, and the results produced. It belongs with the design.

Match the Pairs

1. Problem and need → The opening section: it states the problem or opportunity and the aspect chosen to develop, so the reader knows why the solution is needed.

IPO chart + pseudocode outline → The design section: it shows the planned inputs, processes and outputs, plus a rough algorithm outline, without a full program.

Each requirement is linked to an evaluation criterion so the reader can see how success will be judged → Req F3: Calculate total cost -> Criterion C2: Totals are correct for 10 test orders

Sections appear in a logical order, moving from the problem to constraints, requirements, criteria and then design → Problem > Scope > Constraints > Requirements > Criteria > Data design > Algorithms

Proposal: Algorithms, Data design, Requirements, Problem (no scope or constraints) → The sections are out of order and key sections are missing. The problem should come first, and scope and constraints must be included.

Requirements: Fast and easy. Criteria: (none listed) → The requirements are vague and not linked to any evaluation criteria, so the reader cannot judge whether the solution will succeed.

Key Term

technical proposal

A structured document that sets out the problem, scope, constraints, requirements, criteria, data design and algorithm outlines in order, so a reader can approve the planned solution.

Fill in the Blanks

1. 1. Problem or opportunity 2. Scope of the solution 3. Constraints

Hint: Type the section name that states what the solution will and will not cover.

2. 4. Constraints 5. Requirements 6. Evaluation criteria

Hint: Type the section that lists what the solution must do and how well, placed after constraints.

3. FR1: Show a list of overdue books Criterion 1: Overdue list matches FR1

Hint: Type the requirement ID that this criterion is written to measure.

4. Input: temperature Process: compare temperature to 30 Output: warning message

Hint: Type the IPO chart label for the step that works on the input data.

5. total <- 0 for i from 1 to 5 total <- total + mark[i]

Hint: Type the keyword that begins a loop repeating a set number of times in this pseudocode outline.

Spot the Error

Question 1

A 1. Problem or opportunity

B 2. Aspect to develop

C 3. Algorithm outlines

D 4. Constraints

Line C — Algorithm outlines come near the end, after requirements, criteria and data design. Line 3 should be the scope of the solution, so the reader knows what is included before the detail.

Question 2

A Proposal: Library Loans App

B Problem: use a SQL database

C Scope: loans and returns only

D Constraint: budget of $500

Line B — The problem section describes the need, not a solution. 'Use a SQL database' is a design choice. It should state the issue, such as 'Problem: paper loans are slow'.

Question 3

A R1: Show due date on receipt

B C1: Staff like the colours

C R2: Search books in 2 seconds

D C2: Search time is under 2 secs

Line B — Each criterion must be linked to a requirement and used to judge it. 'Staff like the colours' does not test R1. It should check that the receipt shows the due date, as in 'C1: Receipt shows R1 correctly'.

Question 4

A Data design

B Table: Book(bookId, title)

C Table: Loan(loanId, bookId)

D Link: Loan.bookId=Book.title

Line D — A foreign key must link to the matching primary key. Loan.bookId has to link to Book.bookId, not to the title field.

Question 5

A Algorithm outline: Late fee

B Input: days late

C Output: fee = days * 0.20

D Output: show the fee

Line C — Calculating the fee is a process step, not an output. Line 3 should start with 'Process:'. Output is only what is shown to the user.

Student with a class code? Join your class →