Improvement #664
Updated by Carlos Rodriguez del Castillo about 3 years ago
1. In general there are no controls (Revision/Approval tables), figures/table descriptors, etc. May be worth considering it to be a “controlled” document similar to other IEC documents 2. See the attached image and below for comments on current TISSUE DB state machine. Generally speaking they are the “Discussion” and “Agreement” parts of the diagram. Understanding the problem is the most important phase of resolving it, and direct/open communication is most effective/efficient. a. Consider breaking down the “Discussion” item showing communication/notifications (auto and manual) to key stakeholders, including TISSUE Reporter. How are each of the communications facilitated (e.g. how are the arrows implemented, and with whom? Comment thread on TISSUE, editor emails, public emails, IEC CTS, WG10 plenaries, etc.?) b. Adding more Decision/Agreement milestones so it’s clear when the decision is made and by whom. c. Adding more involvement from TISSUE Reporter, particularly on backwards/forwards compatibility issues. These are key decisions that influence the outcome of the TISSUE. d. What criteria is used during Triage to determine if there is backwards/forwards compatibility issues? e. Missing Yes/No criteria on Agreement milestone f. Actors/Roles g. Who are the nominated namespace delegates, WG delegates, and Maintenance Team? h. Why are these contact details (per TISSUE) not publicly available (e.g. business email, or generic IEC email) for communication purposes, etc.? i. Some of these stakeholder roles appear to be used interchangeably? Are there this many unique stakeholder? j. Who is “Conformance Body”? UCA or Test Labs or Both? k. May be useful to show these different actors in the state machine. l. In general the process is quite brief (10 pages), and could incorporate aspects from other QA standards (ISO 9001, etc.) that have continual improvement aspects, etc. m. “Precedent has already been set in other standards development organizations, which have been successful in creating open and transparent “discussions” and “agreements. This isn’t just in concept, but in practicality as well. Suggest they consider something similar.” See w3c SVG’s github site as one of many examples.