Software Development Process
Requirements, feasibility, development models, project management and maintenance.
- Software Development Approaches
- Major Software Project
- Requirements Gathering
NSW Software Design and Development Stage 6 structure, expressed in Dux teaching language.
Dux tracks each dot point separately, so “I did Software Design and Development” becomes a list of specific things you can already do and specific things you have never been asked. Open a module for all of its dot points, written out.
Requirements, feasibility, development models, project management and maintenance.
Control structures, modularity, data structures, algorithms and the paradigms used to express them.
Testing strategy, debugging, documentation, interface design, security and performance.
Professional responsibility, legal obligations, and the effect of software on the people who use it.
A Software Design and Development paper is not one question type repeated. Each command word asks for a different shape of answer, and each is worth a different number of marks.
| Command word | Question type | Marks |
|---|---|---|
| analyse | Short answer | 3–5 |
| apply | Short answer | 2–5 |
| assess | Short answer | 3–5 |
| compare | Short answer | 3–5 |
| design | Short answer | 3–6 |
| develop | Short answer | 3–6 |
| evaluate | Short answer | 3–5 |
| evaluate | Extended response | 8–10 |
| explain | Short answer | 2–4 |
| identify | Multiple choice | 1 |
| justify | Short answer | 3–6 |
| recommend | Short answer | 3–5 |
| solve | Short answer | 3–5 |
HSC Software Design and Development - Examination Shape — 100 marks, 180 minutes. Practice papers in Dux are assembled to this shape rather than invented, so the timing is training too.
Diagnostic first, then questions written in the shape this course uses. Written answers come back marked against the bands, not just scored.