{"title":"A Bottom Up Approach for Modeling Business Process using Time Petri Nets","authors":"Danillo Siqueira Ramos, F. G. Rocha, M. S. Soares","doi":"10.1145/3535511.3535539","DOIUrl":null,"url":null,"abstract":"Context: UML is an important modeling language for software development in industry, considered a de facto standard for specifying a variety of models, including business processes, data models, and user scenarios that represent software at a high level of abstraction. Problem: Although UML provides the user with several diagrams for software modeling, the language still leaves gaps, such as a poor capacity for modeling time constraints, and simulating the desired behaviour of software. Thus, using only UML to model distributed systems developed using microservices, and also modeling time constraints and system’s behaviour becomes an issue that has been identified by many researchers. Proposed solution: Seeking to mitigate UML gaps, an Electronic Document Management System (SGED) modeled using UML was transcribed to Petri nets with time, using a bottom-up approach. In addition, formal verification and analysis of the model’s properties were performed. Results: Through the Petri Nets model with time, it was possible to analyze the behaviour of the modelled system, as well as analyze the systems’ properties, and then detect and prevent possible unwanted behaviour. Contributions: As for conclusion, it is clear the importance of using formal methods in practice, specially Petri nets, in systems with microservices where time constraints are crucial for their correct behaviour. In addition, it is feasible to construct large models by composing Petri nets, using a bottom-up approach, which corresponds nicely with the architecture of microservices, with independent, loosely coupling services.","PeriodicalId":106528,"journal":{"name":"Proceedings of the XVIII Brazilian Symposium on Information Systems","volume":"17 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2022-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the XVIII Brazilian Symposium on Information Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3535511.3535539","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
Context: UML is an important modeling language for software development in industry, considered a de facto standard for specifying a variety of models, including business processes, data models, and user scenarios that represent software at a high level of abstraction. Problem: Although UML provides the user with several diagrams for software modeling, the language still leaves gaps, such as a poor capacity for modeling time constraints, and simulating the desired behaviour of software. Thus, using only UML to model distributed systems developed using microservices, and also modeling time constraints and system’s behaviour becomes an issue that has been identified by many researchers. Proposed solution: Seeking to mitigate UML gaps, an Electronic Document Management System (SGED) modeled using UML was transcribed to Petri nets with time, using a bottom-up approach. In addition, formal verification and analysis of the model’s properties were performed. Results: Through the Petri Nets model with time, it was possible to analyze the behaviour of the modelled system, as well as analyze the systems’ properties, and then detect and prevent possible unwanted behaviour. Contributions: As for conclusion, it is clear the importance of using formal methods in practice, specially Petri nets, in systems with microservices where time constraints are crucial for their correct behaviour. In addition, it is feasible to construct large models by composing Petri nets, using a bottom-up approach, which corresponds nicely with the architecture of microservices, with independent, loosely coupling services.