Project Requirements Brainstorming
Thought for 15 sec
Great, we’ll do this as a 5-question structured brainstorming flow, one question at a time, and I’ll turn your answers into:
- a system block diagram
- a full component list covering both active and passive parts
- a clear set of requirements and trade-offs
Pick the option that best matches what you want to build, or combine them:
Table
| Option | System Type | Pros | Cons |
|---|---|---|---|
| A | Sense / measure something | Usually lower power, simpler architecture, easier validation | May need careful analog design and calibration |
| B | Control / actuate something | Clear practical value, strong real-world utility | Often needs higher power stages and protection circuitry |
| C | Communicate / gateway data | Good for connected products and logging | Adds protocol, firmware, and power complexity |
| D | Portable device | Battery-powered, compact, flexible use cases | Power budget and charging architecture become critical |
| E | Fixed installed device | Easier power design, fewer battery constraints | Less portable, installation may add connector/mechanical constraints |
| F | Mixed-function system | Most capable, can combine sensing + control + communications | Highest design complexity and more trade-offs |
- What the product does in one sentence
- Who uses it / where it is used
- Whether it is mainly:
- measurement
- control
- communications
- portable
- fixed
- or a combination
If you want, you can reply in this format:
Text
Product: Primary function: Environment: Portable or fixed: Must-have features: Nice-to-have features:
Fill project template
Portable sensor device
Fixed control node
