Ulrik Eklund, Niklas Jonsson, J. Bosch, Anders Eriksson
{"title":"一个用于软件密集型嵌入式系统的参考体系结构模板","authors":"Ulrik Eklund, Niklas Jonsson, J. Bosch, Anders Eriksson","doi":"10.1145/2361999.2362022","DOIUrl":null,"url":null,"abstract":"The paper presents a document template for reference architectures for the domain of software-intensive embedded systems. The template addresses the somewhat conflicting needs when documenting a reference architecture of readability, overview, details, evolution and different background of the stakeholders. The first novel idea is the template prescribes two separate documents describing a reference architecture beside the product architecture documentation. The information in the two documents concern different stakeholders and evolve at different paces. The other novelty in describing reference architectures is to introduce a perspective of time, in the form of horizons, rather than focusing on a snapshot a release date. In addition, a case is presented giving an example of how a reference architecture was documented according to the template, how stakeholder needs were captured, and how the different types of information was identified or recovered from existing product architectures.","PeriodicalId":116686,"journal":{"name":"Proceedings of the WICSA/ECSA 2012 Companion Volume","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-08-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"17","resultStr":"{\"title\":\"A reference architecture template for software-intensive embedded systems\",\"authors\":\"Ulrik Eklund, Niklas Jonsson, J. Bosch, Anders Eriksson\",\"doi\":\"10.1145/2361999.2362022\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The paper presents a document template for reference architectures for the domain of software-intensive embedded systems. The template addresses the somewhat conflicting needs when documenting a reference architecture of readability, overview, details, evolution and different background of the stakeholders. The first novel idea is the template prescribes two separate documents describing a reference architecture beside the product architecture documentation. The information in the two documents concern different stakeholders and evolve at different paces. The other novelty in describing reference architectures is to introduce a perspective of time, in the form of horizons, rather than focusing on a snapshot a release date. In addition, a case is presented giving an example of how a reference architecture was documented according to the template, how stakeholder needs were captured, and how the different types of information was identified or recovered from existing product architectures.\",\"PeriodicalId\":116686,\"journal\":{\"name\":\"Proceedings of the WICSA/ECSA 2012 Companion Volume\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-08-20\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"17\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the WICSA/ECSA 2012 Companion Volume\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/2361999.2362022\",\"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 WICSA/ECSA 2012 Companion Volume","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/2361999.2362022","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A reference architecture template for software-intensive embedded systems
The paper presents a document template for reference architectures for the domain of software-intensive embedded systems. The template addresses the somewhat conflicting needs when documenting a reference architecture of readability, overview, details, evolution and different background of the stakeholders. The first novel idea is the template prescribes two separate documents describing a reference architecture beside the product architecture documentation. The information in the two documents concern different stakeholders and evolve at different paces. The other novelty in describing reference architectures is to introduce a perspective of time, in the form of horizons, rather than focusing on a snapshot a release date. In addition, a case is presented giving an example of how a reference architecture was documented according to the template, how stakeholder needs were captured, and how the different types of information was identified or recovered from existing product architectures.