{"title":"有时候质量是火箭科学:哥伦比亚大学给软件质量专业人员的课程","authors":"T. Rivera, A. Tate, S. Will","doi":"10.1109/SECON.2004.1287932","DOIUrl":null,"url":null,"abstract":"Software quality professionals can learn lessons from many sources, some seemingly unrelated to software. NASA¿s painstaking approach to learning from their mistakes in the field of aerospace is a shining example of the quest to find errors with finding fault. Especially in the areas of quality inspections and testing, software professionals can learn from the Columbia tragedy and the NASA approach in general.","PeriodicalId":324953,"journal":{"name":"IEEE SoutheastCon, 2004. Proceedings.","volume":"28 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2004-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Sometimes Quality is Rocket Science: Columbia~s Lessons for Software Quality Professionals\",\"authors\":\"T. Rivera, A. Tate, S. Will\",\"doi\":\"10.1109/SECON.2004.1287932\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Software quality professionals can learn lessons from many sources, some seemingly unrelated to software. NASA¿s painstaking approach to learning from their mistakes in the field of aerospace is a shining example of the quest to find errors with finding fault. Especially in the areas of quality inspections and testing, software professionals can learn from the Columbia tragedy and the NASA approach in general.\",\"PeriodicalId\":324953,\"journal\":{\"name\":\"IEEE SoutheastCon, 2004. Proceedings.\",\"volume\":\"28 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2004-03-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"IEEE SoutheastCon, 2004. Proceedings.\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SECON.2004.1287932\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE SoutheastCon, 2004. Proceedings.","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SECON.2004.1287932","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Sometimes Quality is Rocket Science: Columbia~s Lessons for Software Quality Professionals
Software quality professionals can learn lessons from many sources, some seemingly unrelated to software. NASA¿s painstaking approach to learning from their mistakes in the field of aerospace is a shining example of the quest to find errors with finding fault. Especially in the areas of quality inspections and testing, software professionals can learn from the Columbia tragedy and the NASA approach in general.