Syllabus Point
- Propose an additional innovative solution using a prototype and user interface (UI) design
Add your teaching notes, worked examples, and classroom activities here.
Prototype
Prototype is a simplified version of the software that demonstrates core functionality and design - used for early feedback
Types of prototypes
- Low-fidelity: paper sketches or basic wireframes to test layout and flow
- High-fidelity: interactive mockups that closely resemble the final product
- Throwaway prototype: built to explore ideas, then discarded
- Evolutionary prototype: incrementally refined into the final product
Purpose of prototyping
- Gather early stakeholder feedback before full development
- Identify usability issues and missing requirements early
- Reduce risk by validating assumptions before committing to full build
- Communicate design intent to developers and clients
User interface (UI) design
UI design focuses on how users interact with the software - layout, navigation, visual elements
UI design principles
- Consistency: uniform layout, colour, and typography across all screens
- Simplicity: avoid clutter - only show what the user needs
- Feedback: system responds visibly to user actions (loading indicators, confirmations)
- Accessibility: design for a range of users including those with disabilities (contrast, font size, keyboard navigation)
UI design tools
- Wireframing tools: Figma, Balsamiq, draw.io
- Storyboards: sequence of screens showing user journey
- Style guides: document colour palettes, typography, and component standards
Related Resources
Keep Progressing
Use the lesson navigation below to move through the module sequence.
Previous: Strategies to Respond to Difficulties When Developing a Software Engineering SolutionLast content page in topic
