Requirements, feasibility, development models, project management and maintenance.
These are the statements the Software Design and Development syllabus makes about Software Development Process. 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.
Waterfall, iterative and agile approaches, and the project conditions under which each is appropriate.
Carrying a project from requirements to implementation, and the documentation that evidences each decision.
Interviews, observation and prototyping, and writing requirements that can be tested.
Technical, economic, schedule and operational feasibility, and why a technically possible project can still be infeasible.
Scheduling, milestones, risk and scope control in a project with a fixed deadline.
Corrective, adaptive and perfective maintenance, and the version control that makes change safe.
What each audience needs from documentation, and the cost of documentation written after the fact.
HSC Software Design and Development - Examination Shape is 100 marks in 180 minutes. Questions on Software Development Process 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.
Software Development Process opens the Software Design and Development course. 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.