Re: DMR (Device Master Record): What is meant by these words - Software Specification
Generally good information so far. I don't know if your question as related to the DMR has been answered yet.
The DMR is the "recipe" for how the product is manufactured. The QSR specifically notes that software specifications are to be included. As pointed out in previous posts, this can include (references to) requirements specs, design specs, etc.
The QSR goes on to talk about more 'hardware-centric' items. But there are certainly some important items to consider for software. I'm just brainstorming here so this isn't necessarily a comprehensive list but consider it a starter:
- Presuming you have the software under change/version control (and PLEASE say you do!!), a snapshot of the configuration at the time of build (typically companies tag each module (version) in the build at the time of the build).
- While probably binaries (executables) are provided to production, the build procedure could be considered for identification. This might even include an identification of the build environment (compiler version, etc.).
- Identification of any equipment and instructions on how to install the software. If not embedded, you'd probably want to identify any installation parameters and dependencies (OSs (and versions), DB (versions), browsers (and versions) supported, etc.). If there are other aspects to the installation, such as setting up databases or installing support libraries, these would be detailed. If embedded, the equipment and procedures to burn or load. If there might be options as to, say, board levels supported (or not supported), these could be specified.
- Any instructions for ensuring the software (and data) is installed properly. For example, there may be a CRC that can be used to confirm the 'bits' are correct. There may be a procedure to run to ensure it's operational.
- If there are procedures to set up the software specific for a site, these should be referenced.
- If there are User's Guides, Management Guides, User Configuration Guides, etc., delivered with the software these should be referenced.
- If you're maybe burning software onto a CD or DVD for delivery to the customer, the burn procedures (and as I mentioned above, CRC checks to confirm the right bits are burned), labeling procedures, etc. should be identified.
That's all I can think of at the moment. And besides, the post is getting rather long. Hope it helps.