Design and the multimedia development process: HSC Industrial Technology Multimedia Technologies
“Describe the design and development process for multimedia products, including the brief, target audience, storyboarding, structure charts, prototyping and the integration of media elements”
Multimedia development moves from a clear brief and defined target audience, through planning the content, structure and navigation with storyboards and structure charts, to prototyping, building and testing. The product integrates media elements such as text, images, audio, video and animation into a coherent interactive whole. Designing for the audience and planning structure before building is what keeps a multimedia project on track and usable.
Jump to a section
What this dot point is asking
In the Multimedia Technologies focus area, the design and development process is the framework that turns an idea into a finished interactive product. NESA expects you to describe how a multimedia product is planned and developed: defining the brief and audience, planning content and structure with storyboards and structure charts, designing navigation and interface, prototyping, and integrating the media elements. This process underpins your Major Project, where the folio documents the same stages, and it is examined in the written paper.
The brief and target audience
Every multimedia product starts with a brief that states its purpose, message and constraints, and a clear picture of the target audience. Who will use the product, what do they need, what devices and skills do they have, and what should they be able to do? Defining the audience drives every later decision about content, tone, interface and media, just as identifying a need anchors a practical project. A product designed without a clear audience pleases no one.
The development process
Multimedia is developed in recognisable stages, much like any design process:
- Analysis: clarify the brief, audience and requirements.
- Design: plan the content, structure, navigation and look using storyboards and charts.
- Development: create and assemble the media elements and build the product.
- Testing: check that it works, is usable and meets the brief.
- Evaluation: judge the finished product against the brief and audience needs.
Documenting these stages in the folio shows the logical thread from brief to product that the markers reward.
Storyboards and structure charts
Two planning tools are central to multimedia design:
- Storyboards sketch each screen or scene in sequence, showing the layout, content and what happens, like a comic strip of the product. They let you plan and review the experience before any building.
- Structure charts map how the screens or sections connect, showing the navigation paths through the product, whether linear, hierarchical or web-like.
Planning structure and screens on paper first is far cheaper than discovering problems after building, which is why these tools are emphasised.
Navigation and interface design
A multimedia product is only as good as a user's ability to move through it. Navigation design decides how users get from place to place, using consistent menus, buttons and links, while interface design decides how the screens look and feel. Good design is consistent, intuitive and clear, so users always know where they are and what they can do. Designing for usability, not just appearance, is a key theme of the focus area.
Prototyping and integrating media
A prototype is an early, partial version used to test ideas, navigation and look before full production, letting you fix problems cheaply. The finished product then integrates the media elements, text, images, audio, video and animation, into a single coherent whole, with attention to consistency, file sizes and how the elements work together. Integration is where careful planning pays off, because well-planned elements assemble smoothly while poorly planned ones clash.
A student is developing an interactive information kiosk product and wants the process to be planned and documented.
Step 1: Analyse the brief and audience
Clarify the purpose, message and constraints, and define the target audience (who they are, their needs, devices and skills, and what they should be able to do).
Step 2: Storyboard the screens
Sketch each screen in sequence, showing the layout, content and what happens on each, so the experience can be reviewed before any building.
Step 3: Chart the structure and navigation
Map how the screens connect with a structure chart (linear, hierarchical or web-like), and design consistent menus, buttons and links so users always know where they are.
Step 4: Prototype and test
Build an early, partial prototype to test navigation, look and usability, fixing problems cheaply before full production.
Step 5: Integrate media and evaluate
Assemble the media elements (text, images, audio, video, animation) into a coherent whole with attention to consistency and file sizes, test against the brief, then evaluate the finished product against audience needs.
Planning structure and screens before building is the core discipline of multimedia development. Storyboards plan each screen and structure charts plan how screens connect, so problems are found and fixed on paper, where change is cheap, rather than after the product is built, where change is costly.
- Skipping audience analysis
- A product built without a defined audience fits no one; define who it is for first.
- Building before planning
- Jumping into authoring without storyboards and structure charts leads to disorganised, hard-to-navigate products.
- Designing for looks over usability
- A beautiful interface that users cannot navigate fails; design navigation and usability deliberately.
- Ignoring the folio process
- The folio must document analysis, design, development, testing and evaluation, not just present the finished product.
Exam-style questions
Questions in the style of NESA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
HSC 2022-style3 marksDistinguish between a storyboard and a structure chart, and explain why both are used when planning a multimedia product.Show worked answer →
A storyboard sketches each screen or scene in sequence, showing the layout, content and what happens on each, like a comic strip of the product, so the experience can be planned and reviewed before building. A structure chart maps how the screens or sections connect, showing the navigation paths through the product (linear, hierarchical or web-like). Both are used because they plan different things: the storyboard plans what each screen looks like and contains, while the structure chart plans how the user moves between screens. Planning both on paper first is far cheaper than discovering layout or navigation problems after building. Markers reward a clear definition of each tool, the layout-versus-navigation distinction, and the plan-before-build justification.
HSC 2024-style6 marksAssess the importance of defining the target audience and planning structure to the success of a multimedia product.Show worked answer →
A strong response argues that defining the target audience (who will use it, their needs, devices and skills, and what they should be able to do) drives every later decision about content, tone, interface and media, so a product designed without a clear audience pleases no one. Planning structure with storyboards and structure charts before building lets layout and navigation problems be found and fixed on paper, where change is cheap, producing a coherent, usable product rather than a disorganised one. The assessment should weigh the time spent on analysis and planning against the cost of rework and poor usability, and conclude that audience definition and structure planning are decisive to a product that is fit for purpose, supported by the point that the folio must document these stages. Markers reward a sustained judgement linking audience, planning, usability and the finished product.