Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Was sollte in Prozessbeschreibung stehen, was in SSP-Traceability Manual #3

Open
tabbertpeter opened this issue Jan 13, 2020 · 2 comments
Assignees
Milestone

Comments

@tabbertpeter
Copy link
Contributor

tabbertpeter commented Jan 13, 2020

Page 20 Gilt für alle steps
• Was sollte in Prozessbeschreibung stehen was in SSP-Traceability Manual
• Wo Doppelung Überlapp sinnvoll Klärung: sollen Dokumente für sich (selbsterklärend) lesbar sein oder nur zusammen verständlich

@DrCaFr
Copy link
Contributor

DrCaFr commented Jan 17, 2020

Decision:
Document shall be self-contained. References to results of other projects are to be omitted.
However, redundancy needs to be minimized, inconsistencies to be prevented.

Idea:
Establish regular reviews for consistency.

@tabbertpeter tabbertpeter changed the title Page 20 Gilt für alle steps • Was sollte in Prozessbeschreibung stehen was in SSP-Traceability Manual • Wo Doppelung Überlapp sinnvoll Klärung: sollen Dokumente für sich (selbsterklärend) lesbar sein oder nur zusammen verständlich Was sollte in Prozessbeschreibung stehen, was in SSP-Traceability Manual Feb 17, 2020
@pmai pmai added this to the 1.0-RC1 milestone Mar 20, 2023
@pmai
Copy link
Collaborator

pmai commented Mar 20, 2023

Specifically the exact reference for the CSP shall be defined, and merged (e.g. via #42), and wording in the document to point to it shall be devised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants