{"title":"On mathematical foundations for business modeling","authors":"Z. Diskin","doi":"10.1109/TOOLS.2000.891368","DOIUrl":null,"url":null,"abstract":"Presents sketch-answers to the following three questions. (1) What is a business domain, mathematically? (2) What is a business model of business domain, mathematically? (3) What is the mathematical machinery suitable for building and manipulating business models? These questions may be answered as follows. (1) Any given business domain D is (mathematically) a topos, i.e. a particular case of a quite general mathematical structure. Probably, even the following more refined picture is valid. Each specific kind of business B (banking, insurance, telecom industry, etc.) determines its own kind of toposes, Top(B), so that any business domain D in B is a topos of sort Top(B), (2) Normally, toposes D are infinite and, given such a topos (domain) D, the task of business modeling is to find a finite yet complete presentation of D. Syntactically, this presentation is specified by a (generalized) sketch, i.e. a directed graph with diagrams marked by labels taken from a predefined signature corresponding to Top(B). (In fact, setting Top(B) amounts to nothing but setting some signature of a legitimate predicate and operations). (3) So, thinking semantically, business specifications are sketches, whatever visualization superstructures (ER, OMT, UML) are built over them. Then, a natural mathematical apparatus for managing and manipulating business specifications is the machinery of deriving and rewriting sketches. In essence, the latter is nothing but a counterpart of ordinary logical derivation and algebraic term rewriting for the graph-based situation.","PeriodicalId":198043,"journal":{"name":"Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Pacific 2000","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2000-11-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"5","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Pacific 2000","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TOOLS.2000.891368","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 5
Abstract
Presents sketch-answers to the following three questions. (1) What is a business domain, mathematically? (2) What is a business model of business domain, mathematically? (3) What is the mathematical machinery suitable for building and manipulating business models? These questions may be answered as follows. (1) Any given business domain D is (mathematically) a topos, i.e. a particular case of a quite general mathematical structure. Probably, even the following more refined picture is valid. Each specific kind of business B (banking, insurance, telecom industry, etc.) determines its own kind of toposes, Top(B), so that any business domain D in B is a topos of sort Top(B), (2) Normally, toposes D are infinite and, given such a topos (domain) D, the task of business modeling is to find a finite yet complete presentation of D. Syntactically, this presentation is specified by a (generalized) sketch, i.e. a directed graph with diagrams marked by labels taken from a predefined signature corresponding to Top(B). (In fact, setting Top(B) amounts to nothing but setting some signature of a legitimate predicate and operations). (3) So, thinking semantically, business specifications are sketches, whatever visualization superstructures (ER, OMT, UML) are built over them. Then, a natural mathematical apparatus for managing and manipulating business specifications is the machinery of deriving and rewriting sketches. In essence, the latter is nothing but a counterpart of ordinary logical derivation and algebraic term rewriting for the graph-based situation.