Students experience the complete engineering lifecycle – from initial concept through to working prototype. The integration challenges they face mirror real industry projects, and seeing their machines actually work in sequence as a museum exhibit is incredibly rewarding for everyone.<\/span><\/span>\u201d<\/p>\nFaculty of Science and Engineering<\/span><\/span><\/strong><\/p>\n<\/p>\n \n \n <\/article>\n <\/div>\n <\/mimas-block>\n\n\n\nCesar’s example assessment<\/h3>\n\n\n\n About my unit:<\/strong> Faculty of Science and Engineering | 50-100 students | In-Person | Group work<\/p>\n\n\n\nMy Advanced Digital Design students work in teams to create Crazy Machine modules – automated contraptions designed as museum exhibits that receive a steel ball, manipulate it through various mechanisms for exactly 45-60 seconds, then deliver it seamlessly to the next team’s module. Each 40x40x40cm module must demonstrate sophisticated integration of FPGA programming, sensor networks, actuator control, and creative mechanical design using primarily recycled materials. <\/p>\n\n\n\n
The project spans 12 weeks with four major deliverables that mirror professional engineering workflows. Teams submit progress reports outlining system architecture and detailed project planning, create professional demonstration videos showcasing technical design decisions and current functionality, perform live machine demonstrations proving full operational capability, and produce comprehensive final reports documenting their complete engineering design process. <\/p>\n\n\n\n
Teams must balance technical sophistication with reliability – modules need multiple unique mechanisms, innovative sensor integration, creative reuse of waste materials, precise timing control, and fully autonomous reset capability. The assessment evaluates both technical achievement and professional engineering communication skills. <\/p>\n\n\n\n
My advice<\/strong> <\/p>\n\n\n\nStructure the project around early system integration rather than last-minute assembly panic. Encourage teams to prototype and test individual subsystems thoroughly before attempting full integration and emphasise that mechanical reliability is just as important as software sophistication. The peer evaluation component is crucial for maintaining individual accountability – set crystal-clear expectations about personal contributions and team dynamics from day one. Most importantly, remind students that their modules will be interconnected, so interface requirements are non-negotiable – one team’s failure affects everyone downstream. <\/p>\n\n\n\n
Suggested marking criteria<\/h3>\n\n\n\n\n \n\n \n
\n Progress report (25%)<\/div>\n
<\/div>\n <\/button>\n
\n
Machine description, system block diagrams, requirements and specifications, project planning with Gantt charts, task allocation justification, <\/span>component<\/span> lists, progress documentation, and professional writing quality<\/span><\/span>\u00a0<\/span><\/p>\n\n \n \n <\/div>\n<\/div>\n \n
\n Demonstration video (25%)<\/div>\n
<\/div>\n <\/button>\n
\n
Team introduction, technical machine description using <\/span>appropriate terminology<\/span>, clear demonstration of working elements, and professional production quality<\/span><\/span>\u00a0<\/span><\/p>\n\n \n \n <\/div>\n<\/div>\n \n
\n Live demonstration (20%)<\/div>\n
<\/div>\n <\/button>\n
\n
Machine completeness, ball receiving\/delivery capability, precise timing (60\u00b15 seconds), hardware\/software complexity, mechanical sophistication, innovative use of recycled materials, autonomous reset functionality, and aesthetic presentation<\/span><\/span>\u00a0<\/span><\/p>\n\n \n \n <\/div>\n<\/div>\n \n
\n Final report (30%)<\/div>\n
<\/div>\n <\/button>\n
\n
Professional documentation, clear problem statement, comprehensive specifications, detailed planning, system architecture diagrams, design decisions and assumptions, implementation details, verification testing, integration challenges, and adherence to word limits<\/span><\/span>\u00a0<\/span><\/p>\n\n \n \n <\/div>\n<\/div>\n \n<\/mimas-block>\n\n\nNote: Marking criteria and weighting are suggested guidelines. Specific descriptions should be adapted to relevant content and learning objectives.<\/p>\n","protected":false},"excerpt":{"rendered":"
Overview Crazy Machines are collaborative design-build projects where student teams follow authentic workflows to create […]<\/p>\n","protected":false},"author":9,"featured_media":0,"parent":161,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":true,"_oasis_is_in_workflow":0,"_oasis_original":0,"_oasis_task_priority":"","footnotes":""},"tags":[],"class_list":["post-602","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/pages\/602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/comments?post=602"}],"version-history":[{"count":0,"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/pages\/602\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/pages\/161"}],"wp:attachment":[{"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/media?parent=602"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.curtin.edu.au\/assessment2030\/wp-json\/wp\/v2\/tags?post=602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}