Nicely formalised. :) This is the sort of thing that I was suggesting for a **Design Requirements Specificatio****n** and a **How it works** document in the section on: **General Forum etiquette** in: [https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a](https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a) and in (2.1) in (2) in the same document. There's also a reference to the same ideas under: **What are the inputs to a Schematic Design Review?** in: [https://docs\.google\.com/document/d/e/2PACX\-1vRhMMBzCZ\_orIFr56QyqYI8HcWsFA00evgh1cQ\_069MJRU2YUJXGWzyX3mMVnxT\-SNz1mydEicu6Bfh/pub](https://docs.google.com/document/d/e/2PACX-1vRhMMBzCZ_orIFr56QyqYI8HcWsFA00evgh1cQ_069MJRU2YUJXGWzyX3mMVnxT-SNz1mydEicu6Bfh/pub)

I have just read your documents. Many points were covered by both, and the main difference remains the narratives. I also had looked at the Schematic Design Review: it is really good and detailed, but maybe too heavy for a maker/hobbist, who has limited amount of free time. However thanks for sharing :)