{"title":"从早期到晚期的正式需求:过程控制案例研究","authors":"E. Dubois, Michaël Petit, Eric Yu","doi":"10.1109/IWSSD.1998.667917","DOIUrl":null,"url":null,"abstract":"In this paper we consider three distinct and connected modelling activities at the Requirements Engineering (RE) level. Within the context of reactive systems, we suggest how these three activities can be supported by the use of appropriate formal languages, namely Kaos, AlbertII and Timed Automata. The i* framework is used for linking the various formal models and for providing a \"high level\" model in terms of which organizational issues are captured. A small process control example is used to illustrate the proposed approach.","PeriodicalId":431074,"journal":{"name":"Proceedings Ninth International Workshop on Software Specification and Design","volume":"10 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1998-04-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"54","resultStr":"{\"title\":\"From early to late formal requirements: a process-control case study\",\"authors\":\"E. Dubois, Michaël Petit, Eric Yu\",\"doi\":\"10.1109/IWSSD.1998.667917\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In this paper we consider three distinct and connected modelling activities at the Requirements Engineering (RE) level. Within the context of reactive systems, we suggest how these three activities can be supported by the use of appropriate formal languages, namely Kaos, AlbertII and Timed Automata. The i* framework is used for linking the various formal models and for providing a \\\"high level\\\" model in terms of which organizational issues are captured. A small process control example is used to illustrate the proposed approach.\",\"PeriodicalId\":431074,\"journal\":{\"name\":\"Proceedings Ninth International Workshop on Software Specification and Design\",\"volume\":\"10 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1998-04-16\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"54\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings Ninth International Workshop on Software Specification and Design\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/IWSSD.1998.667917\",\"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 Ninth International Workshop on Software Specification and Design","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/IWSSD.1998.667917","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
From early to late formal requirements: a process-control case study
In this paper we consider three distinct and connected modelling activities at the Requirements Engineering (RE) level. Within the context of reactive systems, we suggest how these three activities can be supported by the use of appropriate formal languages, namely Kaos, AlbertII and Timed Automata. The i* framework is used for linking the various formal models and for providing a "high level" model in terms of which organizational issues are captured. A small process control example is used to illustrate the proposed approach.