监控需求:一个案例研究

Proceedings 17th IEEE International Conference on Automated Software Engineering, Pub Date : 2002-09-23 DOI:10.1109/ASE.2002.1115035

S. Fickas, T. Beauchamp, Ny Aina Razermera Mamy

{"title":"监控需求:一个案例研究","authors":"S. Fickas, T. Beauchamp, Ny Aina Razermera Mamy","doi":"10.1109/ASE.2002.1115035","DOIUrl":null,"url":null,"abstract":"In our study of composite systems, we found a class of requirements that could not be guaranteed to hold. Specifically, these requirements required the environment of the overall system to behave in ways that could not be controlled. The best we could do in such cases was to note the assumptions placed on the environment for the requirements to be met, and then monitor the environment at runtime to detect deviations from our assumptions about its behavior. This paper discusses a short example of carrying out this type of monitoring. It introduces three tools to support requirements monitoring: (1) a tool to capture a requirement formally, (2) a tool to translate that requirement into a runtime specification, and (3) a tool to actually do the runtime monitoring.","PeriodicalId":163532,"journal":{"name":"Proceedings 17th IEEE International Conference on Automated Software Engineering,","volume":"47 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2002-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"16","resultStr":"{\"title\":\"Monitoring requirements: a case study\",\"authors\":\"S. Fickas, T. Beauchamp, Ny Aina Razermera Mamy\",\"doi\":\"10.1109/ASE.2002.1115035\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In our study of composite systems, we found a class of requirements that could not be guaranteed to hold. Specifically, these requirements required the environment of the overall system to behave in ways that could not be controlled. The best we could do in such cases was to note the assumptions placed on the environment for the requirements to be met, and then monitor the environment at runtime to detect deviations from our assumptions about its behavior. This paper discusses a short example of carrying out this type of monitoring. It introduces three tools to support requirements monitoring: (1) a tool to capture a requirement formally, (2) a tool to translate that requirement into a runtime specification, and (3) a tool to actually do the runtime monitoring.\",\"PeriodicalId\":163532,\"journal\":{\"name\":\"Proceedings 17th IEEE International Conference on Automated Software Engineering,\",\"volume\":\"47 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2002-09-23\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"16\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings 17th IEEE International Conference on Automated Software Engineering,\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ASE.2002.1115035\",\"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 17th IEEE International Conference on Automated Software Engineering,","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ASE.2002.1115035","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 16

摘要

在我们对复合系统的研究中，我们发现了一类不能保证满足的需求。具体来说，这些需求要求整个系统的环境以无法控制的方式运行。在这种情况下，我们所能做的最好的事情就是注意要满足需求的环境上的假设，然后在运行时监视环境，以检测与我们对其行为的假设的偏差。本文讨论了实施此类监测的一个简短示例。它引入了三种工具来支持需求监控:(1)正式捕获需求的工具，(2)将需求转换为运行时规范的工具，以及(3)实际执行运行时监控的工具。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

查看原文本刊更多论文

Monitoring requirements: a case study

In our study of composite systems, we found a class of requirements that could not be guaranteed to hold. Specifically, these requirements required the environment of the overall system to behave in ways that could not be controlled. The best we could do in such cases was to note the assumptions placed on the environment for the requirements to be met, and then monitor the environment at runtime to detect deviations from our assumptions about its behavior. This paper discusses a short example of carrying out this type of monitoring. It introduces three tools to support requirements monitoring: (1) a tool to capture a requirement formally, (2) a tool to translate that requirement into a runtime specification, and (3) a tool to actually do the runtime monitoring.

求助全文

通过发布文献求助，成功后即可免费获取论文全文。去求助

来源期刊

Proceedings 17th IEEE International Conference on Automated Software Engineering,

自引率

0.00%

发文量