University homepage | Suomeksi | På svenska | In English

Electronics II (MATR335) 2022 – Final project instructions


  • Log (every friday at 16:00)
  • Plans (18.3.)
  • Version 0 (1.4.)
  • Version 1 (15.4.)
  • First draft of presentation materials (29.4.)
  • Presentation materials (8.5.)
  • Demo (13.5.) 12.00 o’clock @ Physicum E204
  • Documentation + Complete log book (31.5.)


In the final project you are to create your own IoT (or other microcontroller based) design. Each group gets an 80 € allowance to order any parts not found in the Arduino kits.

Keep track of your time usage, send it weekly to Julius and compile a complete logbook for the final documentation. Tip: Excel is good for this.

The project is divided to three parts: Planning (25%), Demo (50%) and Final documentation (25%). The deadlines for these can be seen above. There are three “checkpoints” in the planning phase to help you split the workload.

Planning consists of: Preliminary plan, Version 0, and Version 1.

Preliminary plan:

Should include problem specifications, design specifications, a testing plan, and components that need to be ordered.
Problem specifications should explain the problem to be solved with the project.

Design specifications should explain what kind of functionality will be needed and how it will be implemented. Including an annotated block diagram of the device is a good idea.

Testing plan covers what functionality of the device must be tested, in what way, and what is the expected result. Following the testing plan should ensure that your device functions properly during normal usage and edge cases. Identifying absolute maximum/minimum usage cases of your device will help compiling documentation and presentation materials.

You should compile a list of components you need. See below for instructions. You can also include the parts you already have but remember to mark them clearly.

The plan should be about one page long, excluding component list.

Ordering components:

Components are ordered from Make sure that your components are not out of stock.

Components are ordered for you based on the list you attach to the preliminary plan. For each component you should include the link to the component and how many of them are needed. If Farnell doesn’t have what you need and no alternatives are available, you can also use other sites ( If we find an alternative to your non-Farnell component, we will contact you to see if it suits your needs and change your order if it does.

If you have problems finding what you need, or have some other component-related problem before or after this plan, please contact the course assistants as soon as possible. Remember to include detailed specifications on what you need, so we can help you better.

Tip: Digikey has better searching capabilities. You can narrow your search there and then search for the exact parts from Farnell.

“Version 0”:

You are expected to have at least started to work on the critical features.

Submit a report of your progress and possible problems with some pictures of the setup. The pictures can be, for example, clear photos complemented by proper circuit diagrams.

The report should be about one page long.

At this point the weekly exercises have ended but the sessions will still be held to help you with your projects. Consider attending even if you have no immediate problems. You can discuss ideas and solutions with other groups and the course assistants.

“Version 1”:

You are expected to have the MVP (minimum viable product) mostly working. Try to have your device in such shape that you could get a passing grade (working device, IoT implemented) at this point. Once again you should submit a report of your progress and possible problems with some pictures of the setup.The report should be about one page long.

First draft of presentation materials:

The materials (slides, video etc.) you intend to use during your demo. If your device is still in progress present your current setup and use placeholder figures if needed.

These slides should include short technical specs and “marketing material” to showcase the features and convince the audience of your solution.

Calculate how many devices you would need to sell to “break even” with the work hours you used. Compare with commercial products if possible.

There are no limits to the length of the materials. The materials should complement the live demo without exceeding the time limit given to you.

Presentation materials:

The final materials (slides, video etc.) you intend to use during your demo. You can make minor changes to the materials after submitting them, but the materials you submit should be presentable as is.


A working demo is required to pass the course. Structure your work so that you have a fallback if something goes wrong or is too hard to implement.

The demo session is held in person at the university. Details in the “Deadlines” section. Each group has 25-30 minutes to present their project and answer questions regarding the project. The demo should contain these parts in following order: marketing, technical, demo and sales.

  • Marketing: Present your device and convince the audience that your device is worth buying.
  • Technical: Present the technical aspects of your project in detail.
  • Demo: Practical demostration of your project. Interactive if possible.
  • Sales: Short session where you sell your device to your peers and answer questions. Reserve 5 minutes for this.

Rehearse your demo and ensure you don’t exceed the time limit.

Have your device assembled and tested before the start of the demo session. Consider transporting the device in one piece. If your device can’t be used in the classroom for some reason, show what you can in person and use a video to show the device in action.

Final documentation:

This report should cover critical parts of the hardware and the software implementation.

Explain what physical parts and software blocks you are using and why. If you use 3rd party libraries, briefly explain what they do and why you decided to use them.

The documentation should contain enough information so that someone could build a similar device based on the documentation.

You don’t need to provide the complete source code but including some snippets with comments might be helpful.

The report should also include list of contributions by each group member and complete work log (weekly hours + cumulative).

This report doesn’t have length limits. Include everything relevant but be concise.

Grading criteria:

The final project is equal to 50% of the course grade.

Preliminary plan, Version 0, Version 1, and presentation materials are graded with pass/fail, and affect the “deadline” grade of the Demo.
Demo and final documentation are graded separately with the following criteria.

  • Cleanliness/Clarity 4x(2-0)p
  • Following deadlines 5x(1-0)p
  • Correctness 3x(2-0)p
  • “Coolness” 2x(1-0)p
  • Difficulty 1x(2-0)p