{"title":"流程重用中的实际问题","authors":"D. Perry","doi":"10.1109/ISPW.1996.654357","DOIUrl":null,"url":null,"abstract":"The author discusses two rather different approaches to process reuse: the first is the use of generic processes, and the second is the use of requirements for best in class processes. The first approach aims at providing a generalized approach that allows for as much commonality across projects while supporting the necessary customization and tailoring for each individual project. The second approach is one that is perhaps more realistic for company-wide process reuse where the differences between projects may be too great to be accommodated by generic processes.","PeriodicalId":126787,"journal":{"name":"Proceedings 10th International Software Process Workshop","volume":"33 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1996-06-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"22","resultStr":"{\"title\":\"Practical issues in process reuse\",\"authors\":\"D. Perry\",\"doi\":\"10.1109/ISPW.1996.654357\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The author discusses two rather different approaches to process reuse: the first is the use of generic processes, and the second is the use of requirements for best in class processes. The first approach aims at providing a generalized approach that allows for as much commonality across projects while supporting the necessary customization and tailoring for each individual project. The second approach is one that is perhaps more realistic for company-wide process reuse where the differences between projects may be too great to be accommodated by generic processes.\",\"PeriodicalId\":126787,\"journal\":{\"name\":\"Proceedings 10th International Software Process Workshop\",\"volume\":\"33 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1996-06-17\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"22\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings 10th International Software Process Workshop\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ISPW.1996.654357\",\"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 10th International Software Process Workshop","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISPW.1996.654357","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The author discusses two rather different approaches to process reuse: the first is the use of generic processes, and the second is the use of requirements for best in class processes. The first approach aims at providing a generalized approach that allows for as much commonality across projects while supporting the necessary customization and tailoring for each individual project. The second approach is one that is perhaps more realistic for company-wide process reuse where the differences between projects may be too great to be accommodated by generic processes.