Describe the task before looking for a model
A useful brief explains the task: receiving and observing a signal, generating one, controlling equipment or integrating existing parts into an instrument. Start with the current system, the problem and the desired output. A reference model is helpful, but it should not replace the purpose.
Separate known facts from open questions
Record known interfaces, supply conditions, available space and environment. List unresolved bands, input levels, outputs or evaluation conditions separately. Rather than guessing a number, explain what is missing and how the decision should be made.
Attach conditions to every target
Requirements such as power, gain, bandwidth or response time need their signal type, load, supply, operating mode and measurement conditions. For existing data, retain the original file, equipment settings and version. A screenshot should include its source and the operating state it represents.
Include the delivery files
Besides the component, module or software, specify configuration files, interface documents, connection drawings, instructions and check records. For software or licensing, distinguish usage rights, executable files and source-code scope before delivery.
Use these points to prepare your project, or start with the blank checklist.
Download checklist