compliance/tech-file
4
0
Fork 0
Code Pull Requests Packages Projects Releases Wiki Activity

drafts started

Browse Source
This commit is contained in:
Markus Thielen 2023-01-31 22:57:05 +01:00
parent 1357c110d0
commit 8f1f1d29d8
4 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
DIN EN 62304/software-development-maintenance-plan.md
View File

@ -1,5 +1,11 @@
# Software Development and Maintenance Plan
**Document Change History**
| Version | Date | Author | Change Comment |
|---------|------------|----------------|----------------|
| 0.1 | 2023-02-01 | Markus Thielen | Draft |
> This document is related to your product. You somehow need to associate it with it. The easiest way would be
> to just put all product-related documents into a folder in your QMS so that the association is
> clear. Alternatively, you could mention the related product and version here, but then you'd have to update

2
DIN EN 62304/teschd.md
View File

@ -1,2 +0,0 @@
# Regulation

6
General documents/instructions-for-use.md
View File

@ -4,9 +4,11 @@
# User Manual [enter Product Name]
Version: [enter content]
Date: [enter content]
**Document Change History**
| Version | Date | Author | Change Comment |
| ------- | ---------- | -------------- | -------------- |
| 0.1 | 2023-02-01 | Markus Thielen | Draft |
[Placeholder Company Address]
Email: [enter content]

7
General documents/intended-use.md
View File

@ -1,5 +1,12 @@
# Intended Use
**Document Change History**
| Version | Date | Author | Change Comment |
|---------|------------|----------------|----------------|
| 0.1 | 2023-02-01 | Markus Thielen | Draft |
## Mapping of Requirements to Document Sections
> Only relevant if you're aiming for MDD (and not MDR) compliance: