{"title":"灰盒软件测试方法:嵌入式软件测试技术","authors":"A. Coulter","doi":"10.1109/DASC.1999.822089","DOIUrl":null,"url":null,"abstract":"The Graybox Methodology is a full software life-cycle testing methodology used to functionally verify Ada, 'C', FORTRAN and assembly language software developed for embedded applications. The Graybox methodology reduces the cost and the time of software development by automatically creating all test unique software. It has been estimated that one line of unique test code is developed for every ten lines of application code (a 10% reduction in SW test time). Previous studies have shown that what used to take two days now takes less than four hours to thoroughly test a unit of software (a 75% reduction in test time). Since the cost of maintaining and upgrading this test-use only code is high, it is simply discarded after testing thereby receiving the name \"throw-away\" code.","PeriodicalId":269139,"journal":{"name":"Gateway to the New Millennium. 18th Digital Avionics Systems Conference. Proceedings (Cat. No.99CH37033)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1999-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"17","resultStr":"{\"title\":\"Graybox software testing methodology: embedded software testing technique\",\"authors\":\"A. Coulter\",\"doi\":\"10.1109/DASC.1999.822089\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The Graybox Methodology is a full software life-cycle testing methodology used to functionally verify Ada, 'C', FORTRAN and assembly language software developed for embedded applications. The Graybox methodology reduces the cost and the time of software development by automatically creating all test unique software. It has been estimated that one line of unique test code is developed for every ten lines of application code (a 10% reduction in SW test time). Previous studies have shown that what used to take two days now takes less than four hours to thoroughly test a unit of software (a 75% reduction in test time). Since the cost of maintaining and upgrading this test-use only code is high, it is simply discarded after testing thereby receiving the name \\\"throw-away\\\" code.\",\"PeriodicalId\":269139,\"journal\":{\"name\":\"Gateway to the New Millennium. 18th Digital Avionics Systems Conference. Proceedings (Cat. No.99CH37033)\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1999-10-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"17\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Gateway to the New Millennium. 18th Digital Avionics Systems Conference. Proceedings (Cat. No.99CH37033)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/DASC.1999.822089\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Gateway to the New Millennium. 18th Digital Avionics Systems Conference. Proceedings (Cat. No.99CH37033)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/DASC.1999.822089","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The Graybox Methodology is a full software life-cycle testing methodology used to functionally verify Ada, 'C', FORTRAN and assembly language software developed for embedded applications. The Graybox methodology reduces the cost and the time of software development by automatically creating all test unique software. It has been estimated that one line of unique test code is developed for every ten lines of application code (a 10% reduction in SW test time). Previous studies have shown that what used to take two days now takes less than four hours to thoroughly test a unit of software (a 75% reduction in test time). Since the cost of maintaining and upgrading this test-use only code is high, it is simply discarded after testing thereby receiving the name "throw-away" code.