{"title":"通过通信Petri网快速原型","authors":"G. Bucci, E. Vicario","doi":"10.1109/IWRSP.1992.243916","DOIUrl":null,"url":null,"abstract":"The design and implementation of a tool for the construction of distributed systems are described. This tool is based on a specification model which extends ordinary Petri nets to include functional and structural concepts. Functional extensions give the model specification completeness, whereas structuring extensions support the organization of the system under development into a set of message passing modules. The augmented model is named communicating Petri net (CmPN). After an introduction to communicating Petri nets, an outline of the software lifecycle activities enforced by the tool under development is given. Two different methods for automatic code generation are expounded and compared in terms of both computational run-time overhead and code dimension (in the case of an example comprised of four CmPNs).<<ETX>>","PeriodicalId":210681,"journal":{"name":"[1992 Proceedings] The Third International Workshop on Rapid System Prototyping","volume":"11 2 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1992-06-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"11","resultStr":"{\"title\":\"Rapid prototyping through communicating Petri nets\",\"authors\":\"G. Bucci, E. Vicario\",\"doi\":\"10.1109/IWRSP.1992.243916\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The design and implementation of a tool for the construction of distributed systems are described. This tool is based on a specification model which extends ordinary Petri nets to include functional and structural concepts. Functional extensions give the model specification completeness, whereas structuring extensions support the organization of the system under development into a set of message passing modules. The augmented model is named communicating Petri net (CmPN). After an introduction to communicating Petri nets, an outline of the software lifecycle activities enforced by the tool under development is given. Two different methods for automatic code generation are expounded and compared in terms of both computational run-time overhead and code dimension (in the case of an example comprised of four CmPNs).<<ETX>>\",\"PeriodicalId\":210681,\"journal\":{\"name\":\"[1992 Proceedings] The Third International Workshop on Rapid System Prototyping\",\"volume\":\"11 2 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1992-06-23\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"11\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"[1992 Proceedings] The Third International Workshop on Rapid System Prototyping\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/IWRSP.1992.243916\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"[1992 Proceedings] The Third International Workshop on Rapid System Prototyping","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/IWRSP.1992.243916","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Rapid prototyping through communicating Petri nets
The design and implementation of a tool for the construction of distributed systems are described. This tool is based on a specification model which extends ordinary Petri nets to include functional and structural concepts. Functional extensions give the model specification completeness, whereas structuring extensions support the organization of the system under development into a set of message passing modules. The augmented model is named communicating Petri net (CmPN). After an introduction to communicating Petri nets, an outline of the software lifecycle activities enforced by the tool under development is given. Two different methods for automatic code generation are expounded and compared in terms of both computational run-time overhead and code dimension (in the case of an example comprised of four CmPNs).<>