{"title":"使用抽象为企业模型构建标准化组件","authors":"B. Work, A. Balmforth","doi":"10.1109/SESS.1993.263954","DOIUrl":null,"url":null,"abstract":"Architectural methods, such as information engineering, are the most comprehensive and intellectually rigorous means of information systems planning. Despite their many virtues though, there remain difficulties with both their theory and their practice. In particular, there are numerous problems associated with enterprise modeling which is at the heart of these methods. Current techniques are inflexible, cumbersome, and lack theoretical underpinning. But, most of all, they are laborious and time-consuming. One reason why enterprise modeling takes so long is that traditional techniques begin with 'a blank sheet of paper'. Instead it might be possible to use standardized components in order to compile a draft model. Since these components may be used again and again, they need a rigorous basis. Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance.<<ETX>>","PeriodicalId":145783,"journal":{"name":"Proceedings 1993 Software Engineering Standards Symposium","volume":"34 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Using abstractions to build standardized components for enterprise models\",\"authors\":\"B. Work, A. Balmforth\",\"doi\":\"10.1109/SESS.1993.263954\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Architectural methods, such as information engineering, are the most comprehensive and intellectually rigorous means of information systems planning. Despite their many virtues though, there remain difficulties with both their theory and their practice. In particular, there are numerous problems associated with enterprise modeling which is at the heart of these methods. Current techniques are inflexible, cumbersome, and lack theoretical underpinning. But, most of all, they are laborious and time-consuming. One reason why enterprise modeling takes so long is that traditional techniques begin with 'a blank sheet of paper'. Instead it might be possible to use standardized components in order to compile a draft model. Since these components may be used again and again, they need a rigorous basis. Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance.<<ETX>>\",\"PeriodicalId\":145783,\"journal\":{\"name\":\"Proceedings 1993 Software Engineering Standards Symposium\",\"volume\":\"34 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-08-30\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings 1993 Software Engineering Standards Symposium\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SESS.1993.263954\",\"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 1993 Software Engineering Standards Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SESS.1993.263954","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Using abstractions to build standardized components for enterprise models
Architectural methods, such as information engineering, are the most comprehensive and intellectually rigorous means of information systems planning. Despite their many virtues though, there remain difficulties with both their theory and their practice. In particular, there are numerous problems associated with enterprise modeling which is at the heart of these methods. Current techniques are inflexible, cumbersome, and lack theoretical underpinning. But, most of all, they are laborious and time-consuming. One reason why enterprise modeling takes so long is that traditional techniques begin with 'a blank sheet of paper'. Instead it might be possible to use standardized components in order to compile a draft model. Since these components may be used again and again, they need a rigorous basis. Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance.<>