Testing strategy, debugging, documentation, interface design, security and performance.
These are the statements the Software Design and Development syllabus makes about Implementation, Testing and Documentation. Dux records each one against the questions you answer, so you can see which of them you have actually been tested on and which have never been asked.
Unit, integration and acceptance testing, test data selection, and systematic debugging.
User guides, technical manuals and training, and what makes documentation usable.
Connecting an application to a database, and the transaction and integrity issues that follow.
Consistency, feedback and error prevention, and evaluating an interface against a real task.
Deployment strategies, migration of data, and rolling back a failed release.
Matching a solution to the platform it must run on, and the constraints that imposes.
Authentication, authorisation, encryption and input handling, and the vulnerabilities each addresses.
Measuring before optimising, and the trade-offs between speed, memory and clarity.
HSC Software Design and Development - Examination Shape is 100 marks in 180 minutes. Questions on Implementation, Testing and Documentation are not one shape repeated: the command word decides what the marker is looking for, and the mark value decides how much of it. These are the ones Software Design and Development uses.
Dux writes practice for this module in exactly these shapes, so the drill is the same task the paper sets — not a general knowledge quiz with the module name on it.
Implementation, Testing and Documentation is module 3 of 4 in Software Design and Development. Students routinely lose marks because a question spans two modules, so the neighbouring modules are worth reading next to this one.
Dux diagnoses Software Design and Development dot point by dot point, then writes questions in the shape this course marks. Written answers come back marked against the bands.