Definition:
Concept Number: *296
English Master: Editor-Advice-Log
Synonyms, Variations & Acronyms: Issue Log, Author Advice Log
Detailing
none
Illustrations
Illustration: none
Type
Process-Output specification
SQC
Examples
none
Notes
An Editor-Advice-Log contains three types of items: Issues, improvement suggestions,
and questions of intent for the Specification-Writer. The log is written with no debate,
discussion or consensus, irrespective of other teammates” opinions. It is written in a
“brainstorming” mode (volume now, analysis later).
The log is the primary input to the Edit Sub-Process, where the Editor (usually the Writer
and owner of the specification) seriously evaluates each Item. The Editor makes all possible
corrections to their specification, according to best available Rules and sources, in all parts
of the specification, not just the Sample or Chunk reported on during the Specification-Meeting.
An Editor-Advice-Log is only written when the Specification-Meeting Entry-Process decides
it is worthwhile. It would not be worthwhile if too many or too few Major-Defects were found
in Checking. Nor would it be worthwhile if the Checking Process had not been done properly,
such as at “too fast a Checking-Rate.” In cases, where “no logging” is chosen, there is the option
of giving the Specification-Writer/editor the “scratchings” (informal Notes made by Checkers
during their Checking Work). This is a practical way of giving the Specification-Writer /editor some
advice without taking any time for writing a formal log. There is even an additional option of doing
a partial log as a Sample of Issues for the writer/editor, without necessarily logging all the discovered
Issues. This can then be supplemented by the “scratchings”.
Keyed-Icons
none
Drawn-Icons
none
Related-Concepts
none
History-of-Concept
none
This Concept entered by Soheir Ghallab.
;){kind=link}
;){kind=link}