3 ms·
Or is it a question of culture and tooling rather than the language itself? Pretty much. I write software for Medical Devices and culture and process is what i
by HeyLaughingBoy 12y ago
Or is it a question of culture and tooling rather than the language itself?
Pretty much. I write software for Medical Devices and culture and process is what it boils down to. Tooling helps. We use C, C++, C# among other languages. Language makes a little difference in reliability, but not much.
What matters in a nutshell:
Know what you're building: need good Requirements
Analyze those Requirements for correctness, clarity and uniqueness (no conflicts)
Make sure your design meets all the Requirements and doesn't add anything: if you add a feature not in a Requirement, how will the testers know it's there? Verify the design: i.e., does it do what you need and does it do it "well." Does it barely function, or will it handle what you expect to be thrown at it or fail gracefully? Separate the concerns: e.g., need to be sure that the temperature is correct? The temperature control code and the temperature verification code should be decoupled from each other.
Code: probably where language makes the most difference, although different languages will influence your design.
Verify all design artifacts: review your Requirements, Designs, and all Code against predetermined quality standards. Reject anything that doesn't meet the standard. Build what you planned to build, and document what you built. Most errors will stem from Requirements problems.
That's Software Quality in a tiny nutshell ;-)