S. Popic, Vanja Komadina, Ranka Arsenovic, Mia Stepanovic
{"title":"在V-Model开发生命周期中实现用于系统测试的简单领域特定语言","authors":"S. Popic, Vanja Komadina, Ranka Arsenovic, Mia Stepanovic","doi":"10.1109/ZINC50678.2020.9161781","DOIUrl":null,"url":null,"abstract":"This paper presents easy to use domain-specific language for system testing in V-model development lifecycle. The systematic approach offered by the domain-specific language for system testing eliminates miscommunications between testers and requirement engineers making the testing closer to the requirement engineers. This concept enables automation in the generation of the tests based on given System Requirements in the future. As many would argue on V-Model’s difficulty to align system requirements and system tests, this approach enables better mapping between those two parts of the V-diagram. This will make no functional requirement missing its counterpart in testing and vice-versa.","PeriodicalId":6731,"journal":{"name":"2020 Zooming Innovation in Consumer Technologies Conference (ZINC)","volume":"20 1","pages":"290-294"},"PeriodicalIF":0.0000,"publicationDate":"2020-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Implementation of the simple domain-specific language for system testing in V-Model development lifecycle\",\"authors\":\"S. Popic, Vanja Komadina, Ranka Arsenovic, Mia Stepanovic\",\"doi\":\"10.1109/ZINC50678.2020.9161781\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"This paper presents easy to use domain-specific language for system testing in V-model development lifecycle. The systematic approach offered by the domain-specific language for system testing eliminates miscommunications between testers and requirement engineers making the testing closer to the requirement engineers. This concept enables automation in the generation of the tests based on given System Requirements in the future. As many would argue on V-Model’s difficulty to align system requirements and system tests, this approach enables better mapping between those two parts of the V-diagram. This will make no functional requirement missing its counterpart in testing and vice-versa.\",\"PeriodicalId\":6731,\"journal\":{\"name\":\"2020 Zooming Innovation in Consumer Technologies Conference (ZINC)\",\"volume\":\"20 1\",\"pages\":\"290-294\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2020-05-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2020 Zooming Innovation in Consumer Technologies Conference (ZINC)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ZINC50678.2020.9161781\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2020 Zooming Innovation in Consumer Technologies Conference (ZINC)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ZINC50678.2020.9161781","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Implementation of the simple domain-specific language for system testing in V-Model development lifecycle
This paper presents easy to use domain-specific language for system testing in V-model development lifecycle. The systematic approach offered by the domain-specific language for system testing eliminates miscommunications between testers and requirement engineers making the testing closer to the requirement engineers. This concept enables automation in the generation of the tests based on given System Requirements in the future. As many would argue on V-Model’s difficulty to align system requirements and system tests, this approach enables better mapping between those two parts of the V-diagram. This will make no functional requirement missing its counterpart in testing and vice-versa.