G. Lucassen, F. Dalpiaz, J. V. D. Werf, S. Brinkkemper
{"title":"跨越双峰——软件行业的案例","authors":"G. Lucassen, F. Dalpiaz, J. V. D. Werf, S. Brinkkemper","doi":"10.1109/TWINPEAKS.2015.13","DOIUrl":null,"url":null,"abstract":"We review the relationship between software architecture and requirements in the context of software products. Based on empirical evidence from a comparative case study, we promote four positions: (1) the requirements/architecture alignment problem for software products is inherently different than the same problem for tailor-made software, (2) bridging the Twin Peaks corresponds to defining and enacting a stepwise evolution of the product architecture, (3) communication tasks are ascribed to the product manager rather than the architect, and (4) integrated and cross-disciplinary tools are key to maintain requirements/architecture alignment. We argue that these positions motivate and characterize future research in the field.","PeriodicalId":112329,"journal":{"name":"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture","volume":"2675 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"9","resultStr":"{\"title\":\"Bridging the Twin Peaks -- The Case of the Software Industry\",\"authors\":\"G. Lucassen, F. Dalpiaz, J. V. D. Werf, S. Brinkkemper\",\"doi\":\"10.1109/TWINPEAKS.2015.13\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"We review the relationship between software architecture and requirements in the context of software products. Based on empirical evidence from a comparative case study, we promote four positions: (1) the requirements/architecture alignment problem for software products is inherently different than the same problem for tailor-made software, (2) bridging the Twin Peaks corresponds to defining and enacting a stepwise evolution of the product architecture, (3) communication tasks are ascribed to the product manager rather than the architect, and (4) integrated and cross-disciplinary tools are key to maintain requirements/architecture alignment. We argue that these positions motivate and characterize future research in the field.\",\"PeriodicalId\":112329,\"journal\":{\"name\":\"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture\",\"volume\":\"2675 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2015-05-16\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"9\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/TWINPEAKS.2015.13\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TWINPEAKS.2015.13","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Bridging the Twin Peaks -- The Case of the Software Industry
We review the relationship between software architecture and requirements in the context of software products. Based on empirical evidence from a comparative case study, we promote four positions: (1) the requirements/architecture alignment problem for software products is inherently different than the same problem for tailor-made software, (2) bridging the Twin Peaks corresponds to defining and enacting a stepwise evolution of the product architecture, (3) communication tasks are ascribed to the product manager rather than the architect, and (4) integrated and cross-disciplinary tools are key to maintain requirements/architecture alignment. We argue that these positions motivate and characterize future research in the field.