Structure of a technical proposal
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. Which best describes a technical proposal?
2. Which order makes the most sense for the start of a technical proposal?
3. Where should the constraints section sit in a technical proposal?
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?
5. Which section of a technical proposal shows the inputs, processes and outputs of the planned solution?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 11. Problem and need | AThe design section: it shows the planned inputs, processes and outputs, plus a rough algorithm outline, without a full program. | |
| 2IPO chart + pseudocode outline | BReq F3: Calculate total cost -> Criterion C2: Totals are correct for 10 test orders | |
| 3Each requirement is linked to an evaluation criterion so the reader can see how success will be judged | CThe requirements are vague and not linked to any evaluation criteria, so the reader cannot judge whether the solution will succeed. | |
| 4Sections appear in a logical order, moving from the problem to constraints, requirements, criteria and then design | DProblem > Scope > Constraints > Requirements > Criteria > Data design > Algorithms | |
| 5Proposal: Algorithms, Data design, Requirements, Problem (no scope or constraints) | EThe opening section: it states the problem or opportunity and the aspect chosen to develop, so the reader knows why the solution is needed. | |
| 6Requirements: Fast and easy. Criteria: (none listed) | FThe sections are out of order and key sections are missing. The problem should come first, and scope and constraints must be included. |
C
Definitions
technical proposal
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
1. Problem or opportunity
2. _____ of the solution
3. Constraints
2.
4. Constraints
5. ____________
6. Evaluation criteria
3.
FR1: Show a list of overdue books
Criterion 1: Overdue list matches ___
4.
Input: temperature
_______: compare temperature to 30
Output: warning message
5.
total <- 0
___ i from 1 to 5
total <- total + mark[i]
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
1. Problem or opportunity
B
2. Aspect to develop
C
3. Algorithm outlines
D
4. Constraints
Question 2
A
Proposal: Library Loans App
B
Problem: use a SQL database
C
Scope: loans and returns only
D
Constraint: budget of $500
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
Question 4
A
Data design
B
Table: Book(bookId, title)
C
Table: Loan(loanId, bookId)
D
Link: Loan.bookId=Book.title
Question 5
A
Algorithm outline: Late fee
B
Input: days late
C
Output: fee = days * 0.20
D
Output: show the fee
Answer Key
Structure of a technical proposal
Section A: Quick Questions
Q1
A — A structured document that sets out the problem, scope, requirements and design so a reader can approve the plan
Q2
A — Problem, then aspect to develop, then scope
Q3
B — Before the requirements, so the reader knows the limits the requirements must fit within
Q4
A — A criterion states how the response time will be tested against the 2-second target
Q5
B — The IPO chart in the design section
Section B: Match the Pairs
Q1
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.
Q2
IPO chart + pseudocode outline → The design section: it shows the planned inputs, processes and outputs, plus a rough algorithm outline, without a full program.
Q3
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
Q4
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
Q5
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.
Q6
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.
Section C: Definitions
Q1
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.Section D: Fill in the Blanks
Q1
1. Problem or opportunity
2. Scope of the solution
3. ConstraintsQ2
4. Constraints
5. Requirements
6. Evaluation criteriaQ3
FR1: Show a list of overdue books
Criterion 1: Overdue list matches FR1Q4
Input: temperature
Process: compare temperature to 30
Output: warning messageQ5
total <- 0
for i from 1 to 5
total <- total + mark[i]Section E: Spot the Error
Q1
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.
Q2
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'.
Q3
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'.
Q4
D — A foreign key must link to the matching primary key. Loan.bookId has to link to Book.bookId, not to the title field.
Q5
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.