UNIT CODE INSPECTION CHECKLIST Unit Name_________________________System___________Build/Release_______________________ Task Number_________________________________________Initial Inspection Date_______________ Inspection Moderator______________________________________________________________________ KEY INSPECTION QUESTIONS Yes No Corrected 1. Is any input argument unused? Is any output argument not produced? [ ] [ ] [ ] 2. Is any data type incorrect or inconsistent? [ ] [ ] [ ] 3. Is any coded algorithm inconsistent with an algorithm explicitly stipulated in PDL or in requirements/specifications? [ ] [ ] [ ] 4. Is any local variable used before it is initialized? [ ] [ ] [ ] 5. Is any external interface incorrectly coded? That is,is any call statement or file/database access incorrectly coded? Also, for an Ada unit, is any external interface not explicitly eferenced / with'd-in? [ ] [ ] [ ] 6. Is any logic path incorrect? [ ] [ ] [ ] 7. Does the unit have multiple entry points or multiple, normal (non-error) exits? [ ] [ ] [ ] ADDITIONAL INSPECTION QUESTIONS 8. Is any part of the code inconsistent with the unit design specified in the prolog and PDL? [ ] [ ] [ ] 9. Does the code or test plan contain any unauthorized deviations from project standards? [ ] [ ] [ ] 10. Does the code contain any error messages that might be unclear to the user? [ ] [ ] [ ] 11. If the unit was designed to be reusable, has any hindrance to reuse been introduced in the code? [ ] [ ] [ ] ACTION ITEMS AND COMMENTS (List on a separate sheet. Refer to questions above by number.) INSPECTION RESULTS 1. If all answers to 1-11 were "No, " the unit's code passes. Check here and sign below. [ ] 2. If there are serious deficiencies in the code (e.g., if more than one key question was answered "Yes") the author must correct the unit design and the moderator must schedule a re-inspection. Scheduled date for re-inspection:__________________________________________________ 3. If there are minor deficiencies in the code, the author must correct the unit design and hold a follow-up meeting with the moderator Scheduled date for follow-up meeting:_________ Moderator's signature certifies that this unit meets all applicable standards and satisfies its requirements, and that any identified deficiencies have been resolved (applicable at initial inspection, follow-up meeting, or re-inspection). Moderator Signature:____________________________________ Date:_______________________
本文档为【代码检查单_NASA】，请使用软件OFFICE或WPS软件打开。作品中的文字与图均可以修改和编辑，
图片更改请在作品中右键图片并更换，文字修改请直接点击文字进行修改，也可以新增和删除文档中的内容。
该文档来自用户分享，如有侵权行为请发邮件ishare@vip.sina.com联系网站客服，我们会及时删除。
[版权声明] 本站所有资料为用户分享产生，若发现您的权利被侵害，请联系客服邮件isharekefu@iask.cn，我们尽快处理。
本作品所展示的图片、画像、字体、音乐的版权可能需版权方额外授权，请谨慎使用。
网站提供的党政主题相关内容(国旗、国徽、党徽..)目的在于配合国家政策宣传，仅限个人学习分享使用，禁止用于任何广告和商用目的。
浙公网安备 33021202002483