Phased inspections and their implementation
Phased inspections and their implementation
复制标题
阶段性检查及其实施
DOI：
10.1145/127099.127101
复制
发表时间：
1991
期刊：
影响因子：
--
通讯作者：
E. Myers
中科院分区：
文献类型：
--
作者：
John C. Knight;E. Myers
软件审查并不是一个新概念，它几乎和软件一样长。检查某事是否正确的最自然的方法之一就是看它。巴贝奇和冯·诺伊曼都定期要求同事检查他们的程序。在20世纪50年代和60年代，大型软件项目通常包括某种类型的软件审查，在20世纪70年代，这些审查机制开始出现在出版物中。到20世纪70年代中后期，各种评审方法以不同的名称出现了：软件评审、技术评审、正式评审、演练、结构化演练和代码评审。每种评审方法都需要填写不同的表格，不同的评审团队规模和组成，等等，但是除了查看和讨论之外，没有人建议任何评审软件或其他工作产品的方法。
Software reviews are not a new idea, they have been around almost as long as software. One of the most natural ways to check if something is correct is to look at it. Babbage and von Neumann both regularly asked colleagues to examine their programs [5]. In the 1950's and 1960's, large software projects often included some sort of software reviews, and in the 1970's these review mechanisms began appearing in publications. By the mid to late 1970's, various review methods had emerged with different names: software reviews, technical reviews, formal reviews, walkthroughs, structured walkthroughs, and code inspections. Each review method had different forms to fill out, different review team sizes and makeup, etc., but none suggested any approach for reviewing the software or other work product other than just looking at it and discussing it.