Let's talk about software requirements and why they're (maybe) useful.
We'll see when software requirements need to be documented in your software development process by briefly walking through it and skipping to the relevant step.
When writing software requirements, we'll talk about their content regarding:
- IEC 62304 categories (functional, security, usability, etc.)
- Risk control measures
- Associated risks
Next, we'll try to understand what the purpose of writing software requirements was in the first place. Firstly, reading them should enable an outsider to understand your software, and secondly, in theory, if you specify things better, your developers don't have to come up with ad-hoc decisions. And developers shouldn't be trusted to make any decisions, right?