{"title":"使用协作业务规则组件进行事务捕获的面向对象框架","authors":"J. Rivett-Carnac","doi":"10.1109/STEP.1997.615471","DOIUrl":null,"url":null,"abstract":"In a dealing-room system at a London bank, the transaction capture programs had been built using a GUI-based prototyping approach. This had led to programs with superficial similarity but inconsistency of internal structure which made maintenance difficult. To re-engineer the programs a control framework was devised separating the GUI interface (presentation layer), business rules and persistent storage. The framework allows business rules to be developed as independent, co-operating components. This makes it easier to develop and add new function or re-use previously-developed function. Business rule components are developed and tested separately, then used as building blocks for development of more complex components. They are re-usable because the same business constraints and calculations apply to many different transaction types.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"An object-oriented framework for transaction capture using co-operating business rule components\",\"authors\":\"J. Rivett-Carnac\",\"doi\":\"10.1109/STEP.1997.615471\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In a dealing-room system at a London bank, the transaction capture programs had been built using a GUI-based prototyping approach. This had led to programs with superficial similarity but inconsistency of internal structure which made maintenance difficult. To re-engineer the programs a control framework was devised separating the GUI interface (presentation layer), business rules and persistent storage. The framework allows business rules to be developed as independent, co-operating components. This makes it easier to develop and add new function or re-use previously-developed function. Business rule components are developed and tested separately, then used as building blocks for development of more complex components. They are re-usable because the same business constraints and calculations apply to many different transaction types.\",\"PeriodicalId\":68622,\"journal\":{\"name\":\"软件\",\"volume\":null,\"pages\":null},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1997-07-14\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"软件\",\"FirstCategoryId\":\"1093\",\"ListUrlMain\":\"https://doi.org/10.1109/STEP.1997.615471\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"软件","FirstCategoryId":"1093","ListUrlMain":"https://doi.org/10.1109/STEP.1997.615471","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
An object-oriented framework for transaction capture using co-operating business rule components
In a dealing-room system at a London bank, the transaction capture programs had been built using a GUI-based prototyping approach. This had led to programs with superficial similarity but inconsistency of internal structure which made maintenance difficult. To re-engineer the programs a control framework was devised separating the GUI interface (presentation layer), business rules and persistent storage. The framework allows business rules to be developed as independent, co-operating components. This makes it easier to develop and add new function or re-use previously-developed function. Business rule components are developed and tested separately, then used as building blocks for development of more complex components. They are re-usable because the same business constraints and calculations apply to many different transaction types.