Design Document Check

updated Fa 2020

Description

The Design Document Check (DDC) is intended to aid your team as it prepares its Design Document. The DDC focuses narrowly upon providing feedback on the preparation of historically problematic Design Document elements. If these elements fall short during your Design Review the following week, precious time is lost.

What are the course staff looking for? i) Evidence that the overall idea of the design is sound; ii) A check of a small subset of required components indicates that the project is on the right track.

Below is a checklist of things to have ready for the design document check. Refer to the design document page and grading rubric for a full description of each item.
  1. Introduction
    1. Start with a brief summary (30 sec) or elevator pitch following this template:

      I will build ___A___ (my core product) for ___B___ (my core customer: the person who pays my company or uses the product).

      My customer has a problem ___C___ (describe the problem your customer has)

      My product solves my customer’s problem by ___D___ (how do you solve the problem?)

    2. Be expected to explain further what the problem is, what’s your idea to solve it, and why your idea is novel.
  2. Visual Aid
  3. High-level Requirements
    1. HL requirements are derived from the problem you are trying to solve (put yourself into the customer's shoes). HL requirements should be the essential features that your customers/users really care about. These features distinguish your product from others (e.g. ones available in the market or previous 445 designs). Be abstract (no tech details, you may come up with different design due to other constraints but still solve this problem), quantifiable (no words like continuously, accurately, etc), and unambiguous. HL&RV slides(P.5) has a good example.
    2. We will look at your HL requirements and check if they are what your customers/users really care about. Be prepared to defend your requirements, so that when you get challenged, you can give a well thought out explanation.
  4. Block Diagram
    1. Block Diagram slides
    2. We will check whether this design appears to solve your problem. 
    3. We will check if formatting is clear (lines, legends, etc). Extra caution is needed as students often make mistakes here (but you shouldn't!).
  5. Requirements & Verification Tables
    1. HL&RV slides: from P. 1-17
    2. Block Module Requirements: Break down your HL requirements into block level requirements. These are the requirements in the RV table (they are not the specs of the parts you have chosen).
    3. Verification: A step-by-step approach allows another 445 student to test if the BL requirement is satisfied. This is like an instruction for your module's unit test (with some surrounding dummy modules, a.k.a, mock object(s)
    4. We will review one piece of it. Show us an important one.
  6. Plots
  7. Circuit Schematics
  8. Tolerance Analysis
    1. Identify an important part that you need to perform some quantitative analysis on. This part should have quantitative values critical to the design and require you do calculations and make trade-offs in order to achieve your best design.
    2. Common mistake: Many students do calculations for tangential parts to pad the space.
  9. Safety & Ethics
  10. Citations

During the DDC, your team will have 5-8 minutes to present an example of each of these elements. Expect to share the 30-minute DDC session with two other design teams. Come prepared to learn from their work - both the good and bad.

Your task is to prepare and upload the above elements in a single PDF document to the course website. During your DDC session, you will present directly from your submission, which will be projected for all to see.

The focus of the DDC is not on the details of your design but rather on the details of your formatting; the design of your project will be covered in-depth during the Design Review. Organize your submission in accordance with the Design Document guidance and the example Design Document.

The course staff will focus on providing feedback on the format of your sample DDC elements - the very limited available time will not afford detailed feedback on your design. Please go to office hours for further guidance.

Requirements and Grading

Upload your DDC submission to your project page on PACE (i.e. ECE 445 web board) before arriving at your DDC session.

As in your Design Document, number pages after the title page in your DDC submission.

Any material obtained from websites, books, journal articles, or other sources not originally generated by the project team must be appropriately attributed with properly cited sources in a standardized style such as IEEE, ACM, APA, or MLA.

The course staff at the DDC will assign individual grades to each student based on:

Submission and Deadlines

Sign-up for the Design Document Check on the ECE 445 course website - specifically at the Sign up for Team Presentation item on the PACE tab. Sign-up will open the Monday one week prior to the DDCs.

Upload your DDC submission (.pdf format) to the ECE 445 course website before your DDC session - specifically at the My Project item on the PACE tab.

While you will not complete peer reviews during the DDC, you are expected to actively contribute to the discussion.

Tech must-know and FAQ for design

Here is the link of "Tech must-know and FAQ for design" which is accessible after logging into g.illinois.edu.

Over semesters, ECE445 course staff have encountered repeated mistakes from students. The document above is designed to provide students with the essential knowledge needed in order to have a good design. Spending 5 min reading it might save you 15 hours later. Also, there might be some quiz questions in your DDC or Design Review. Please help us improve this document. We value your feedback!

Mushroom Growing Tent

Elizabeth Boyer, Cameron Fuller, Dylan Greenhagen

Mushroom Growing Tent

Featured Project

# Mushroom Growing Tent Project

Team Members:

- Elizabeth Boyer (eboyer2)

- Cameron Fuller (chf5)

- Dylan Greenhagen (dylancg2)

# Problem

Many people want to grow mushrooms in their own homes to experiment with safe cooking recipes, rather than relying on risky seasonal foraging, expensive trips to the store, or time and labor-intensive DIY growing methods. However, living in remote areas, specific environments, or not having the experience makes growing your own mushrooms difficult, as well as dangerous. Without proper conditions and set-up, there are fire, electrical, and health risks.

# Solution

We would like to build a mushroom tent with humidity and temperature sensors that could monitor the internal temperature and humidity, and heating, and humidity systems to match user settings continuously. There would be a visual interface to display the current temperature and humidity within the environment. It would be medium-sized (around 6 sq ft) and able to grow several batches at a time, with more success and less risk than relying on a DIY mushroom tent.

Some solutions to home-grown mushroom automation already exist. However, there is not yet a solution that encompasses all problems we have outlined. Some solutions are too small of a scale, so they don’t have the heating/cooling power for a larger scale solution. Therefore, it’s not enough to yield consistent batches. Additionally, there are solutions that give you a heater, a light set, and a humidifier, but it’s up to the user to juggle all of these modules. These can be difficult to balance and keep an eye on, but also dangerous if the user does not have experience. Spores can get released, heaters can overheat, and bacteria and mold can grow. Our solution offers an all-in-one, simple, user-friendly environment to bulk growing.

# Solution Components

## Control Unit and User Interface

The control unit and user interface are grouped together because the microcontroller is central to the design of both, and they are closely linked in function.

The user interface will involve a display that shows measured or set values for different conditions (temperature, humidity, etc) on a display, such as an LCD display, and the user will have buttons and/or knobs that allow the user to change values.

The control unit will be centered around a microcontroller on our PCB with circuitry to connect to the other subsystems.

Parts List:

1x Microcontroller

1x PCB, including small buttons and/or knobs, power circuitry

1x Display module

1x Power supply

## Temperature Sensing and Control

The temperature sensing and control components will ensure that the grow box stays at the desired temperature that promotes optimal growth. The system will include one temperature sensor that will record the current temperature of the box and feed a data output back into our PCB. From here, the microcontroller in our control unit will read the data received and send the necessary adjustments to a Peltier module. The Peltier module will be able to increase the temperature of the box according to the current temperature of the box and set temperature. Cooling will not be required, as maintaining a minimum temperature is more important than a maximum temperature for growth.

Parts List:

1x Temperature Sensor

1x Peltier module

## Humidity Sensing and Control

The humidity sensing and control system will work in a similar way to the temperature system, only with different ways to adjust the value. We will have one humidity sensor that will be continually sending data to our PCB. From here, the PCB will determine whether the current value is where it should be, or whether adjustments need to be made. If an increase in humidity is needed, the PCB will send a signal to our misting system which will activate. If a decrease is needed, a signal will be sent to our air cycling system to increase the rate of cycling, thereby decreasing the humidity within the box.

Parts List:

1x Humidity Sensor

4x Misting heads

Water tubing as needed

## Air Quality Control

The air filtration system is run constantly, as healthy mushroom growth (free of bacteria) needs clean, fresh air, and mycelium requires and uses up oxygen as it grows. Additionally, this unit is connected to the hydration sensing unit- external humidity is in most cases going to be lower than internal humidity, and cycling in new air can be used to decrease humidity. When high humidity is detected, the air filtration system will decrease the internal humidity by cycling in less humid air.

Parts List:

Flexible Air duct length as needed

1x Fan for promoting air cycling

# Criteria For Success

Our demo will show that each of our subsystems functions as expected and described below:

For the control unit and user interface, we will demonstrate that the user can change the set temperature and humidity values through buttons or knobs.

The humidity sensing and control system’s functionality will demonstrate that introducing dry air into the device activates the misting system, which requires functional sensors and a water pump.

The temperature sensing and control system demo will involve showing that the heater turns on when the measured temperature is below the set temperature.

The air quality control system’s success will be demonstrated as air movement coming from the fan enters the tent.

Project Videos