Software Engineering › Learn step by step › Y11 Programming Fundamentals
Item 49 of 426 · Year 11: Programming Fundamentals, 3 of 69
Determining specifications
Process
Jump to a topic
- Exam format, question types and command words (46)
- Year 11: Programming Fundamentals (69)
- Year 11: The Object-Oriented Paradigm (33)
- Year 11: Programming Mechatronics (29)
- Year 12: Secure Software Architecture (57)
- Year 12: Programming for the Web (59)
- Year 12: Software Automation (35)
- Year 12: The Software Engineering Project (47)
- Diagrams and modelling tools (18)
- Python, SQL, pseudocode and CSS patterns (33)
Definition
Turning requirements into a detailed description of what the software will do: inputs, processes, outputs, data, performance, technical needs and compliance. Tools include IPO charts, data dictionaries and Gantt charts.
Example: Requirements say WHAT the client wants; specifications say exactly HOW WELL and in WHAT FORM the software will deliver it.
Found in: syllabus, school notes.
Where you'll use it in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Fill in the blanks: Choose this term to complete a statement or table.
- Short answer: Describe how specifications differ from requirements
Where it has appeared in the paper
Secure Software Architecture (Part C). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q1 (1 mark): Development steps Secure Software Architecture (Part C) · 1 mark
How to use it
A model sentence
“Turning requirements into a detailed description of what the software will do: inputs, processes, outputs, data, performance, technical needs and compliance.” Then apply it: Requirements say WHAT the client wants; specifications say exactly HOW WELL and in WHAT FORM the software will deliver it.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
No linked question shows the command word for this term. Across the past short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
Go deeper
- Flashcard: Determining specifications in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Notes: Interpret and apply fundamental software development steps to develop secure code,… (Secure Software Architecture (Year 12))
- Notes: Fundamental software development steps for secure code (Secure Software Architecture (Year 12))
- Notes: Software development steps and algorithm design (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Full term page: every question, note and marking comment for Determining specifications
Check yourself
Say the steps or stages of “Determining specifications” in order.
Reveal the answer
Turning requirements into a detailed description of what the software will do: inputs, processes, outputs, data, performance, technical needs and compliance. Tools include IPO charts, data dictionaries and Gantt charts.
Example: Requirements say WHAT the client wants; specifications say exactly HOW WELL and in WHAT FORM the software will deliver it.
Could be tested as: Multiple choice, Fill in the blanks, Short answer.