Project

Table of contents

1. Project overview
2. Timeline
3. Proposal (Due Friday, Oct 16 at 11pm)
4. Progress milestone (Nov 13)
5. Final deliverables

---

Project overview

Design and implement an embedded project using one or more Arduinos and some external electronic components.

Your project must:

• Use PWM, ADC, or DAC
• Have a watchdog timer
• Have at least one interrupt service routine (watchdog timer doesn’t count)

It must also use at least one of:

• Serial communication
• WiFi
• Bluetooth
• Timer/Counter (other than WDT. Arduino delay doesn’t count)

The scope of the project must be complex enough to demonstrate design skills and creativity but realistic enough to culminate in a functioning deliverable (feedback for this will be given during the proposal and milestone).

To be updated as we cover these topics in class The final writeup and demonstration will also feature documentation of process (requirements writing, testing plan, modeling)

Timeline

• Thursday, Oct 8: Project groups assigned

• Friday, Oct 16: Proposal due

• Week of Oct 19: Proposal feedback received, parts ordering begins

• Friday Nov 13: Milestone artifacts and demo video due

• Week of Nov 16: Peer reviews (in class)

• Reading period (date TBD): Final demo; deliverables due

Proposal (Due Friday, Oct 16 at 11pm)

Write a project proposal (about 1 page) that has the following sections:

1. High-level overview of what the project will be.

2. Explanation of how the project will fulfill the requirements above.

3. Proposed final deliverable for the project: what physical object will you demo, and what is the criteria by which we will know that the demo is successful?

4. For each sensor/actuator you plan to use, a short (1-2 sentence) description of how you will know that the component is working. Before building the final project, you should get to know your hardware, and this section should explain how you will do that. For example, if you’re ordering a stepper motor, a valid answer would be “getting the stepper motor to rotate by 1/8 turn, pause, and repeat until it goes all the way around.” If you can, include a link to the Arduino library (e.g. Stepper) that pertains to the component.

5. Discussion of uncertainties, such as challenges you anticipate in implementing the project, timeline considerations, faulty components, etc. You don’t have to provide a contingency plan for each uncertainty, but you should offer some idea of what a scaled-back project would look like.

6. Preliminary list of parts to be ordered, with links. For complex components, include a PDF of the datasheet with the Gradescope submission, if possible (to make Milda’s life easier). We will give initial feedback for this before ordering parts. The course is providing each group a budget of about $25-$30 for parts ordered with us through this process (you are welcome to use your own parts, especially if you have some lying around! Milda also has a selection of parts from previous years).

7. Any resources (tutorials, libraries, videos) you’ve consulted in writing this report.

We’re aiming for parts orders to be placed by October 22. Factor in about a week of processing and shipping time to receive the hardware.

Progress milestone (Nov 13)

For the project milestone, you will turn in a short video demoing your progress on getting your sensors/actuators to interface with the Arduino. You will also produce a report that is composed of artifacts from the left/design side of the software engineering V-model. More info to come after you receive proposal feedback!

Final deliverables

This section will get updated after the milestone. You’ll be working towards:

• A report that shows evidence of your process in accordance of the V-model of software engineering
• Evidence of individual contribution and understanding
• Project implementation and testing code that is traceable to the report
• A final demo that serves a celebration of all of the hard work you put into the project and shows it off to your classmates