Aerospace Systems Engineer

2005

Review and Coordination



Review process-


What does it mean to review a document? Are these formal document reviews of a baselined product or more casual peer level courtesy reviews? The first could benefit from a structured and formal DR type process (at the expense of time), the later can, and should be, more casual.

Does the author want a “rubber stamp” of approval, or a critical review and comments, or a redlined re-write? And with what level of formality?


What is the mechanism for providing “review” comments? Should functional areas (i.e., conops, test, etc.) coordinate input to make sure they are internally consistent?


If one is forwarded a product to review do you provide your review to the author, or the person who forwarded you the product?