{"title":"软件维护培训:过渡经验","authors":"T. Pigoski, C. Looney","doi":"10.1109/ICSM.1993.366931","DOIUrl":null,"url":null,"abstract":"When large software systems make the transition from a developer to a separate maintenance organization, system-specific software maintenance training becomes an issue. However, in most cases the maintenance organization is left with the problem of training its people to perform maintenance on the new system. This paper addresses the training issue, discusses how one maintenance organization attacked the problem, and provides lessons learned.<<ETX>>","PeriodicalId":228379,"journal":{"name":"1993 Conference on Software Maintenance","volume":"1132 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"10","resultStr":"{\"title\":\"Software maintenance training: Transition experiences\",\"authors\":\"T. Pigoski, C. Looney\",\"doi\":\"10.1109/ICSM.1993.366931\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"When large software systems make the transition from a developer to a separate maintenance organization, system-specific software maintenance training becomes an issue. However, in most cases the maintenance organization is left with the problem of training its people to perform maintenance on the new system. This paper addresses the training issue, discusses how one maintenance organization attacked the problem, and provides lessons learned.<<ETX>>\",\"PeriodicalId\":228379,\"journal\":{\"name\":\"1993 Conference on Software Maintenance\",\"volume\":\"1132 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"10\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"1993 Conference on Software Maintenance\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICSM.1993.366931\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"1993 Conference on Software Maintenance","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSM.1993.366931","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
When large software systems make the transition from a developer to a separate maintenance organization, system-specific software maintenance training becomes an issue. However, in most cases the maintenance organization is left with the problem of training its people to perform maintenance on the new system. This paper addresses the training issue, discusses how one maintenance organization attacked the problem, and provides lessons learned.<>
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
