- Development ships a feature. QA tests it.
- Someone outside the sprint writes the Software Requirements Specification (SRS) and test documentation later.
- By submission, your IEC 62304 records and your code can describe different versions.
Software development and IEC 62304 software quality assurance (SQA)
Your code and your IEC 62304 records, at the same version.
We develop with your team, run senior software QA down to low-level testing, and write the IEC 62304 documentation set as the code changes.
In short
What does IEC 62304 software quality assurance cover?
It covers the software lifecycle records IEC 62304 asks for, from the software development plan and Software Requirements Specification (SRS) to architecture, detailed design, and traceability from requirements to risk controls to tests, and the testing that produces the evidence.
MedDev Solutions develops and tests SaMD and embedded firmware with your team and writes those records as the code changes, designed to support compliance with IEC 62304:2006/AMD1:2015.
Sound familiar?
You shouldn't have to manage five different teams just to get one product submitted.
Here is one requirement change, with the records written later and with the records written alongside the code.
The handoffRequirement change to release
- Requirements enter your backlog with an ID. Tests trace to those IDs.
- When a requirement changes, the SRS, the tests, and the risk file change in the same sprint.
- The aim: at release, the records already match the build.
How we work with your team
In your sprints, with the records written alongside the code.
Your device needs working, tested software. Your submission needs the IEC 62304 records for that same software. Here is who does what.
01What IEC 62304 asks for
Lifecycle records, from the plan to traceability.
From the software development plan and Software Requirements Specification (SRS) to traceability from requirements to risk controls to tests, plus the testing that produces the evidence.
02What we build and write
Code, tests, and records, as the code changes.
We develop and test SaMD and embedded firmware with your team, run senior SQA down to low-level testing, and write the IEC 62304 records as the code changes.
03What your team owns
Your developers keep ownership of the product code.
Your developers get requirements they can test. Your company remains the manufacturer and keeps responsibility for its design controls and submission.
What we deliver
What do we deliver: the software, or the records?
Your device needs working, tested software. Your submission needs the IEC 62304 records for that same software. One team handles both, including embedded firmware.
Development and testing
Code, tests, and quality work done alongside your developers.
- Software as a Medical Device (SaMD) and digital health software development
- Embedded firmware, developed and tested as embedded software
- Senior SQA: low-level QA and testing
- Verification and validation (V&V) of medical device software
- Secure Software Development Lifecycle (SSDLC) built into the work
The IEC 62304 documentation set
The software records your Design History File needs, written as the code changes. Designed to support compliance with IEC 62304:2006/AMD1:2015.
- Software development plan
- Software Requirements Specification (SRS)
- Software architecture and detailed design
- Management of software of unknown provenance (SOUP) and off-the-shelf (OTS) software
- Traceability from requirements to risk controls to tests
- Software risk analysis inside your ISO 14971 process
How an engagement runs
How does an engagement run?
In five phases, from records gap review to sustaining engineering. How long each phase takes depends on your codebase and your current records. We agree the scope of each phase together before work starts.
Assess
We compare your code, tests, and IEC 62304 records, and list where they disagree, starting with what your submission needs first.
Plan
Your software lifecycle process and documentation set, structured to IEC 62304 and fitted to how your team already works.
Build and test
Development and low-level testing alongside your developers, with records written as the code changes.
Verify and validate
V&V of your medical device software, with each result traced to a requirement and a risk.
Sustain
Sustaining engineering after release, with records kept current for every change.
Questions we get
Software and SQA FAQ
Answer
MedDev Solutions
We add senior SQA that knows what IEC 62304 asks for in the records, low-level testing, and documentation written as the code changes. Your team knows the product, and your developers keep ownership of the product code. Your company remains the manufacturer and keeps responsibility for its design controls and submission.
MedDev Solutions
Both. We develop SaMD and digital health software with your team, run SQA, and write the IEC 62304 documentation set.
MedDev Solutions
Yes. We treat firmware as embedded software: development, testing, and IEC 62304 records. We don't do hardware design, electronics, or hardware testing.
MedDev Solutions
We provide sustaining engineering: changes, fixes, and the IEC 62304 records that go with them, kept current for each release.
Something else? Ask us directly on a 30-minute call
Next step
Bring your code and your records.We'll look at them with you.
In 30 minutes, we'll walk through your software, your IEC 62304 records, and your submission plan. We'll suggest a first step.