{"title":"奥斯卡的经历","authors":"C. Boldyreff, D. Nutter, S. Rank","doi":"10.1109/ICSM.2004.1357871","DOIUrl":null,"url":null,"abstract":"Evolutionary development of a large software component by a small team within a larger research project has many problems in common with industrial software development as well as giving rise to its own unique problems. We reflect on these problems based on our experience developing OSCAR within the GENESIS project. Key issues are identified and possible ways to overcome or ameliorate these problems are suggested.","PeriodicalId":348668,"journal":{"name":"20th IEEE International Conference on Software Maintenance, 2004. Proceedings.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"The experience of OSCAR\",\"authors\":\"C. Boldyreff, D. Nutter, S. Rank\",\"doi\":\"10.1109/ICSM.2004.1357871\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Evolutionary development of a large software component by a small team within a larger research project has many problems in common with industrial software development as well as giving rise to its own unique problems. We reflect on these problems based on our experience developing OSCAR within the GENESIS project. Key issues are identified and possible ways to overcome or ameliorate these problems are suggested.\",\"PeriodicalId\":348668,\"journal\":{\"name\":\"20th IEEE International Conference on Software Maintenance, 2004. Proceedings.\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2004-09-11\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"20th IEEE International Conference on Software Maintenance, 2004. Proceedings.\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICSM.2004.1357871\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"20th IEEE International Conference on Software Maintenance, 2004. Proceedings.","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSM.2004.1357871","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Evolutionary development of a large software component by a small team within a larger research project has many problems in common with industrial software development as well as giving rise to its own unique problems. We reflect on these problems based on our experience developing OSCAR within the GENESIS project. Key issues are identified and possible ways to overcome or ameliorate these problems are suggested.