Software design
Connect requirements, UML and UI design
Apply analysis artefacts and design representations to change scenarios.
Make requirements testable
Replace vague language with input, processing, output and quality conditions.
Choose UML by purpose
Use structural diagrams for architecture, sequence for interaction and activity for flow.
5 subjects · 100 itemsWritten response · 150 min40 each · 60 average
Read cohesion and coupling as change cost
A useful module boundary limits how far one change spreads.
Turn UI principles into checks
Test consistency, error prevention, feedback and accessibility screen by screen.