Objectives

1. Enhance your analytical skills:

a. Individual: Develop critical thinking through independent problem-solving.

b. Group:

i.      Group discussions and brainstorming sessions help analyse problems from different perspectives.

ii.      Peer reviews and collaborative problem-solving enhance critical thinking.

2. Build your technical writing skills:

a. Individual: Improve clarity and precision in writing technical documents.

b. Group:

i.     Collaborative report writing ensures clarity and thoroughness.

ii.      Group feedback improves overall writing quality.

3. Build your coding skills:

a. Individual: Enhance coding proficiency through practice and self-study.

b. Group:

i.      Pair programming and code reviews facilitate learning and knowledge sharing.

ii.     Collaborative coding projects tackle complex problems effectively.

4. Build your circuit design skills:

a. Individual: Gain expertise in designing and troubleshooting circuits independently.

b. Group:

i.      Collaborative projects and group discussions lead to more innovative and effective designs.

ii.     Collaborative projects allow sharing of knowledge about different components and techniques.

5. Build your design skills using 3D CAD modelling:

a. Individual: Develop proficiency in 3D CAD software through practice and studying the lessons.

b. Group:

i.     Team projects and collaborative design reviews refi ne models and share efficient design tips.

ii.      Collaborative design reviews refi ne models to meet project requirements.

6. Build your presentation skills:

a. Individual: Improve public speaking and presentation abilities through practice.

b. Group:

i.     Group presentations improve coordination and public speaking abilities.

ii.      Practising within the group provides constructive feedback and confidence.

7.   Build your project and time management skills:

a. Individual: Develop effective time management and organisational skills independently.

b. Group:

i.     Working in groups enhances task division and organisational skills.

ii.      Managing group deadlines and milestones develops effective project management techniques.

Ard ui no Circuit Design (10%):

Your prototype will utilise multiple components and your circuit configuration must include the following:

● An Ard ui no Microcontroller

● A 16x2 LCD (Note: the I2C LCD cannot be used)

●    An RGB LED

● A Temperature Sensor (TMP36)

● A Pushbutton

● Breadboards, resistors, and wires as required

Please note:

❖ All of your components and their configurations must comply with the design

guidelines and practices taught in this unit, for example, all wiring must be

traceable, organised, and colour code as specified in the relevant lessons.

❖  Any modification to the component requirements of this assessment must be approved by your teacher at least a week prior to the due date.

❖  Your circuits must be completed using Tinkercad. You need to ensure that the circuit name meets the submission requirements and is correctly shared with  your teachers.

Coding (30%):

The coding of your Ard ui no microcontroller is a crucial part of this assignment. Your code design must provide the following minimum functionalities:

●    Upon start display the temperature to the LCD screen in Fahrenheit, Celsius and Kelvin.

●   Take and respond to user commands via the serial monitor and via the pushbutton

○    Display the average temperature (in all units) on LCD Screen, once the button is pressed and then

○ Display a menu on serial monitor with the following 4 options and

functionalities (Note: You need to display the relevant information based on the user’s choice)

■ Display the temperature in fahrenheit

■ Display the temperature in celsius

■ Display the temperature in kelvin

■ Display the average temperature (in all units)

●    Utilise an RGB LED to react the temperature changes based on the following criteria:

○    Use the colour blue if the temperature is less than 20 degrees celsius, with the brightness increasing as the temperature decreases.

■   The maximum brightness will be achieved at 0 degrees celsius or lower.

○    Use the colour green if the temperature is between 20 to 30 degrees celsius (inclusive)

○    Use the colour red if the temperature is higher than 30 degrees celsius, with the brightness increasing as the temperature increases.

■   The maximum brightness will be achieved at 40 degrees celsius or higher.

Please note

❖ You must follow proper coding conventions and guidelines as taught in this unit.

This includes applying proper naming conventions, consistent code alignment etc.

❖  Any coding concepts learned from the outside sources must be referenced using code comments in your code. Please note that this does not mean you can copy  code from those sources.

❖  Your code should include an appropriate header comment section, containing all the relevant details. You must include appropriate inline comments where necessary.

Prototype Housing (Case) Design - Using 3D CAD Software (20%):

As mentioned previously, as part of this project you are required to create a simple housing for your prototype.

Your model should meet the following minimum requirements:

● Designed to be portable

●    Has accurate measurements based on the electronics components that it will contain:

○   At a minimum must be able to hold the LCD screen, t he Ard ui no, the pushbutton, the temperature sensor and the usb port for serial connection

○   Considering any of the other required components is optional. Examples include wiring and 4 x AA batteries (and/or a power supply port)

●    Designed to be functional and practical. For example, is the LCD considered to be easily visible to the user?

●    Designed to be assembled and suitable for production using 3D printing technology

Please note

❖  All your measurements must be in the metric system (i.e. millimetres, centimetres etc.)

❖  You are only required to model the housing and are not required to model the LCD, t he Ard ui no and other components of your circuit.

❖  Your work must comply with the design guidelines and practices taught in this unit.

❖ You must comply with the submission requirements when submitting your

model.

❖ You must use only the approved 3D CAD application taught in this unit.

❖  It is recommended that you only start your model after your circuit, code and report are at a healthy progression.

❖  Avoid spending extensive amounts of time adding extra features to your model, if you are behind in other parts of the project.

Technical Report (20%):

Documenting your work is a very important part of this project. You will need to provide a report on various aspects of your project.

Your report must contain the following:

● Title Page

● Table of contents

● Abstract/Executive Summary: A summary of the entire report in a few paragraphs.

● Introduction: outlines the purpose of this project and provides a valid justification

● Background research: a brief summary on existing similar products and how your prototype compares against them

● 3D Design Analysis, entailing the following:

○   A brief on the evolution of the designs you created prior to your fi nal design

○ A justification for your fi nal design.

○    Images/drawings of your work at a minimum must include a technical drawing, multiple (at least 2) views of your fi nished design with relevant measurements

● Circuit and Code Analysis, documents the following:

○   A screenshot of your circuit, properly labelled and laid out with all the components clearly visible and recognisable.

○   A list of the functions that you have completed

○   A list of the functionalities you have not completed or are incomplete

○ The main code concepts used

○   any issues that you faced during development and how you resolved them

○ Highlight of anything special or unique about your approach

○   Only provide snippets of the code as necessary without copy and pasting long portions of your code

● Device User Guide, a clear explanation of:

○    How to operate the device for a novice user. It can contain step by step instructions, images and optionally videos.

● Conclusion: Summarises the project achievements and outlines current issues and shortcomings of the submitted project as well as any ideas for future improvement.

● References/Bibliography: A list of references in a consistent format using a standard referencing style.

● Appendices: Any extra documentation that need not be included in the main report. Examples: Entire code, supporting documentation, data sets, generative AI prompts and responses etc.

Please note

❖  Your work must comply with the report writing guidelines and practices taught in this unit. For example, you must use a table of contents, appropriate heading styles, title page, etc.

❖  You must comply with the submission requirements when submitting your model.

❖  Update your report regularly as you progress through other sections of this project.

Presentation (20%)

Presentation Material (5%)

Your presentation material consists of the slides you use during your presentation. It must:

●    Be consistently formatted.

● Be clear and readable with excellent quality content.

● Have a logical flow from one topic to the next.

Please note:

●   Google Slides is the preferred application. However, if you choose to use other applications, the presentation slides must still be available and shared on Google Drive with all team members and your instructors throughout the entire process  as you complete and update it.

●   Your presentation slides must be submitted by the end of the presentation session on Moodle.

●   You must submit the slides in either .pptx or .pdf formats.

●    Late submission or failure to submit will result in a penalty to the overall presentation grade.

Presentation Delivery (15%)

You will have 5 minutes (subject to change) to present your work in a professional presentation to a target audience of potential executives, competitors, and investors.

You need to highlight your device’s features and benefits in a bid to win the investment opportunity to take your product into production, aiming to beat competitors to the market.

As a general guide, you can follow the items of the technical report; however, make it appropriate for an oral presentation format. Consider the following:

●    It is a formal business presentation. Identify, understand, and be mindful of the target audience.

●   All team members must coordinate, practice, and present in a professional manner.

● Business attire is optional but ideal.

What to present

● Brief introduction: Introduce who you are and what are your roles.

● Outline of the presentation: Provide a brief overview of what you will cover.

● Design choices: Explain and justify your choices (e.g., code, 3D model, circuit, etc.).

● Design process: Outline the design process, problems encountered, and how you addressed them.

● Prototype functionalities: Focus on the features and abilities of the device, not a device guide.

● Code and circuit highlights: Demonstrate proficiency and technical robustness without including large segments of code. Convince the audience that the product is functional and technically sound.

● Selling points: Explain why your team is the best to make it happen, why your product is better than the competition, and highlight any unique features or key selling points of your design.

● List of Issues: Identify any challenges or setbacks encountered during the project.

● Potential Future Improvements: Discuss potential enhancements or developments for the product.

● Q/A: Be prepared to answer questions from the audience.

● References: Provide a list of sources or references used in your presentation.

Please note:

●    Presentations must take place in the selected labs during week 6. Additional instructions will be provided by your teachers closer to the due date.

●    Failure to attend (without approved special consideration) will result in receiving zero marks. All team members must present. In the event of a team member’s absence, the team must still proceed with the presentation.

● Presentation slides must be submitted by the end of the presentation session.

Individual Tasks

You all are required to individually complete all the following tasks:

1.   Create an individual assignment folder on Google Drive. Name it

MCD1160_A1_StudentID_FullName(Preferred Name) and share it with your teacher(s).

2.  Ard ui no Circuit Design  on Tinkercad. Each member of the team must have their own completed circuit on TinkerCad and must name it

MCD1160_A1_StudentID_FullName(Preferred Name).

3.   Coding the entire circuit based on the specifications.

4.   Prototype Housing (Case) Design - This is your individual design. Your .f3d files from the CAD software Fusion 360 with the file name

TeamID_Name_A1_CAD.f3d must be uploaded to your individual Google folder.

Group Tasks

You will participate in a group of 3-4 members. Group members will be allocated by your teachers during weeks 2-3.

Your group will submit one fi nal completed submission. All group members MUST contribute to the completion of the project.

Each group will need to complete the following tasks:

1. Choose a team name

2. Create a Team Google Drive:

○ Name the drive: TeamID_A1.

○ Share the drive with all group members and your teacher(s).

○   Store all parts of your assignment in this drive as you complete them.

3. Technical Report:

○ Create one fi nal version of the entire report.

○   The report must include details of all team members.

4. 3D CAD Model:

○ Create one fi nal, optimised version of the 3D CAD model.

○   This should be based on the best-optimised versions of individual group members' models.

5. Tinkercad Circuit and Code:

○ Create one fi nal, optimised version of the circuit and code.

○ Name the circuit: TeamID_A1.

○ Share the circuit with all group members and your teacher(s).

○   This should be based on the best-optimised versions of individual group members' codes and circuits.

6. Group Work Documentation:

○ Document all group work activities and contributions.

Task Allocation and Trello Usage:

●   Tasks will be allocated by the team members. You must ensure a balanced distribution of work.

● Each group is required to use Trello to manage and track tasks.

○ Create a Trello Board: Set up a board specifically for your group project.

○ Task Lists: Create task lists such as "To Do," "In Progress," and "Completed."

○ Task Cards: Add cards for each task, detailing the specific requirements and deadlines.

○ Assign Members: Assign tasks to individual group members, ensuring clarity in responsibilities.

○ Monitor Progress: Use Trello to track the progress of tasks, providing updates and feedback within the platform.

●    Using Trello will help keep the project organised, ensure accountability, and facilitate communication among group members.

● Your teacher(s) may request access to your Trello board at any time.

Milestones:

● Establish clear deadlines and milestones for each part of the project.

○ Milestone 1: Initial research and planning completed by week 2-3.

○ Milestone 2:

■    Draft versions of the technical report, CAD model, and Tinkercad   circuit and code completed by the end of week 3 or the beginning of week 4.

■ Start your presentation preparation.

○ Milestone 3:

■ Prepare and practise your group presentation.

■    Final review and optimisation of all project components by the end of week 4 or the beginning of week 5.

○ Milestone 4: Final submission of the complete project by the due date specified in the due date section.

○ Milestone 5: Presentation of your fi nal work in week 6.

●   Adhering to these deadlines will ensure timely progress and allow sufficient time for review and adjustments. You will need to provide evidence of these

milestones to your teachers during the class sessions.

Communication Protocols:

● Establish and maintain clear communication channels within the group.

○ Primary Communication Tool: Use Google Chats and student emails  for daily communication and updates.

○ Task allocation and progress tracking: Use Trello.

○ Regular Meetings: Schedule regular meetings (e.g., weekly) to discuss progress, address issues, and plan next steps.

○ Meeting Minutes: Document key points and decisions made during meetings and share them with all group members.

●    Effective communication is essential for coordinating efforts, resolving issues, and ensuring everyone is on the same page.

●   Your teachers may request access to evidence of this communication at any time.

Peer Evaluation:

●    By the end of the project, each group member will complete a peer evaluation form.

●   This form will assess the contribution of each member to the project, focusing on factors such as participation, cooperation, and the quality of work.

● Peer evaluations will contribute to the individual grades for the project.

●    It is important to provide honest and constructive feedback to ensure fairness and recognise each member's effort.

Group Work Learning Material on Moodle:

●   All group members are required to utilise the group work learning material available on Moodle.

●   This material includes resources on effective collaboration, conflict resolution, and best practices for project management.

●    Reviewing these materials will help improve the efficiency and effectiveness of your group work.

●    Ensure that all members are familiar with these resources and apply the recommended strategies throughout the project.

Contribution and Accountability:

●   All group members are expected to contribute equally to the project.

●    Each member’s contributions should be documented and shared within the group.

● If a group member is not sufficiently contributing:

○ Initial Discussion: Address the issue within the group to understand any underlying reasons and encourage the member to improve their participation.

○ Set Expectations: Clearly outline the tasks and expectations for each member, ensuring everyone understands their responsibilities.

○ Monitor Progress: Regularly monitor the progress of each member and provide feedback.

○ Escalation: If the issue persists, involve the teacher to discuss the lack of contribution and seek a resolution.

○ Adjustments: The teacher may reallocate tasks or, in extreme cases, adjust individual grades based on the level of contribution.

●    Ensuring all members contribute fairly is crucial for the success of the project and for maintaining a balanced workload.

In the event if individual team members do not contribute, you are still responsible for submitting the project within the expected due date.

Conflict Resolution:

● In the event of a conflict within the group, the following steps should be taken:

○ Identify the Issue: Clearly defi ne the problem and ensure that all members understand it.

○ Open Communication: Discuss the issue openly and respectfully, allowing all members to express their viewpoints.

○ Seek Solutions: Brainstorm possible solutions as a group, considering the pros and cons of each option.

○ Reach a Consensus: Aim to reach a mutually agreeable solution. If necessary, compromise to fi nd the best outcome for the group.

○ Escalate/Involve a Mediator: If the conflict cannot be resolved internally, seek assistance from your teacher or a designated mediator to help facilitate a resolution.

●    It is important to address conflicts promptly and constructively to maintain a positive and productive group dynamic.

Referencing Requirements

Please refer to the referencing guidelines and sources that we covered in the unit. All sources must be referenced i n an officia l referencing format.

Please include a bibliography at the end of your work.

Any coding concepts learned from outside sources must also be referenced using code comments in your code. Please note that this does not mean you can copy code from   those sources.