{"title":"集成的可追溯性","authors":"L. R. Gieszl","doi":"10.1109/ICSI.1992.217299","DOIUrl":null,"url":null,"abstract":"Software traceability (as required by DOD STD 2167A for software developed for the Department of Defense) sound like a good idea from the sponsor's point of view, and it seems like a natural (and even useful) task for the developer. The author takes a closer look at how you do it and whether it is helpful or it is simply another documentation chore. The article is derived from lessons learned in practice and from reviewing the research work of the students from several semesters of a Johns Hopkins University graduate course on software engineering.<<ETX>>","PeriodicalId":129031,"journal":{"name":"Proceedings of the Second International Conference on Systems Integration","volume":"285 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1992-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"14","resultStr":"{\"title\":\"Traceability for integration\",\"authors\":\"L. R. Gieszl\",\"doi\":\"10.1109/ICSI.1992.217299\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Software traceability (as required by DOD STD 2167A for software developed for the Department of Defense) sound like a good idea from the sponsor's point of view, and it seems like a natural (and even useful) task for the developer. The author takes a closer look at how you do it and whether it is helpful or it is simply another documentation chore. The article is derived from lessons learned in practice and from reviewing the research work of the students from several semesters of a Johns Hopkins University graduate course on software engineering.<<ETX>>\",\"PeriodicalId\":129031,\"journal\":{\"name\":\"Proceedings of the Second International Conference on Systems Integration\",\"volume\":\"285 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1992-06-15\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"14\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the Second International Conference on Systems Integration\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICSI.1992.217299\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the Second International Conference on Systems Integration","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSI.1992.217299","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Software traceability (as required by DOD STD 2167A for software developed for the Department of Defense) sound like a good idea from the sponsor's point of view, and it seems like a natural (and even useful) task for the developer. The author takes a closer look at how you do it and whether it is helpful or it is simply another documentation chore. The article is derived from lessons learned in practice and from reviewing the research work of the students from several semesters of a Johns Hopkins University graduate course on software engineering.<>
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
