You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this issue starts the 2nd part of the first Internal Assessment review session.
What has been done so far:
review of the Quality Assurance documents by the internal Assessors (Frédérique Vallée & Norbert schäffer).
the issues have been assigned to the Quality task leader in OenETCS, and to the document author.
What is to be done now:
Answer by the documents authors to the internal assessors for each issue related to their document.
define the kind of issue, and how they will be considered in the document.
The issue can be considered according two different ways:
the remark is light, and addresses small changes/ cosmetic/ punctuation... Then it can be transformed into a "standard" remark, and the issue can be transferred to another one in the current documentation review process. The issue will be closed in the Internal Assessment repos if accepted by the author/ project quality leader. The link from this internal assessment issue to the normal review process issue created has to be realized by the document author or the project quality task leader.
the remark is more important, and addresses potential significative changes on the document (CENELEC compliance issue, document structure). In this case, your comment on the issue will be sent back to the Internal Assessor concerned, and the issue will be assigned to the Internal Assessment review session1 wrap up label. This issue will then be presented to the next Workshop on Safety Assessment in February 2014 in Nürnberg: https://github.com/openETCS/validation/wiki/First-Workshop-on-Safety-Assessment.
Dear assessors, dear all,
this issue starts the 2nd part of the first Internal Assessment review session.
What has been done so far:
What is to be done now:
Answer by the documents authors to the internal assessors for each issue related to their document.
define the kind of issue, and how they will be considered in the document.
The issue can be considered according two different ways:
@FrederiqueVallee @MarcBehrens @idelatorre @openETCS/management
The text was updated successfully, but these errors were encountered: