开放式分布式处理(面板)

Oscar Nierstrasz, A. Snyder, A. S. Williams, W. Cook
{"title":"开放式分布式处理(面板)","authors":"Oscar Nierstrasz, A. Snyder, A. S. Williams, W. Cook","doi":"10.1145/260303.260322","DOIUrl":null,"url":null,"abstract":"The computer industry is facing a software crisis. To remain competitive, organizations need to continually improve the computer solutions they use to run the enterprise. However, constructing and maintaining enterprise wide application systems running in a heterogeneous distributed environment is too expensive and time consuming, resulting in a large backlog of unfulfilled needs. One of the most promising approaches to resolving this software crisis is the idea of constructing software systems by interconnecting software component products developed by a wide variety of commercial software vendors and in-house developers. This approach allows customers to better leverage the work of others, reducing development costs. It offers maximum freedom of choice to the customer, enabling more flexible and configurable enterprise solutions. It encourages competition among software developers to produce innovative components that maximize the value to customers. It enables the rapid evolution of software systems to meet fast changing business requirements. For this component-based approach to be successful, several requirements must be satisfied. It must be possible to interconnect components developed independently, using different programming languages, running on different kinds of machines in a distributed environment. It must be possible to replace individual components, again where the new component might be implemented by a different developer, using a different programming language, running on a different machine, possibly of a different kind than the original component. It must be possible to introduce or replace existing components with new components that provide extended capabilities without breaking existing software. Adding or replacing components must be possible without stopping the system. It should be possible to validate component interconnections for compatibility based on component attributes. Components should be isolated from each other so that software errors can be confined and tracked to a particular component. It must be possible to incorporate existing \" legacy \" applications with minimal or no modification. These capabilities should apply not just to traditional application programs, but also to smaller functional units, such as a file selection dialog, and even to basic system components, such as file systems and virtual memory managers. At a higher level, it must be possible to interconnect data, not just programs. For example, it must be possible to connect a specific invoice with a specific customer record. It must be easy for system administrators and users to make interconnections and reconfigure components. For example, it should be possible to move a collection of data to a different …","PeriodicalId":297156,"journal":{"name":"Addendum to the proceedings on Object-oriented programming systems, languages, and applications","volume":"42 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Open distributed processing (panel)\",\"authors\":\"Oscar Nierstrasz, A. Snyder, A. S. Williams, W. Cook\",\"doi\":\"10.1145/260303.260322\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The computer industry is facing a software crisis. To remain competitive, organizations need to continually improve the computer solutions they use to run the enterprise. However, constructing and maintaining enterprise wide application systems running in a heterogeneous distributed environment is too expensive and time consuming, resulting in a large backlog of unfulfilled needs. One of the most promising approaches to resolving this software crisis is the idea of constructing software systems by interconnecting software component products developed by a wide variety of commercial software vendors and in-house developers. This approach allows customers to better leverage the work of others, reducing development costs. It offers maximum freedom of choice to the customer, enabling more flexible and configurable enterprise solutions. It encourages competition among software developers to produce innovative components that maximize the value to customers. It enables the rapid evolution of software systems to meet fast changing business requirements. For this component-based approach to be successful, several requirements must be satisfied. It must be possible to interconnect components developed independently, using different programming languages, running on different kinds of machines in a distributed environment. It must be possible to replace individual components, again where the new component might be implemented by a different developer, using a different programming language, running on a different machine, possibly of a different kind than the original component. It must be possible to introduce or replace existing components with new components that provide extended capabilities without breaking existing software. Adding or replacing components must be possible without stopping the system. It should be possible to validate component interconnections for compatibility based on component attributes. Components should be isolated from each other so that software errors can be confined and tracked to a particular component. It must be possible to incorporate existing \\\" legacy \\\" applications with minimal or no modification. These capabilities should apply not just to traditional application programs, but also to smaller functional units, such as a file selection dialog, and even to basic system components, such as file systems and virtual memory managers. At a higher level, it must be possible to interconnect data, not just programs. For example, it must be possible to connect a specific invoice with a specific customer record. It must be easy for system administrators and users to make interconnections and reconfigure components. For example, it should be possible to move a collection of data to a different …\",\"PeriodicalId\":297156,\"journal\":{\"name\":\"Addendum to the proceedings on Object-oriented programming systems, languages, and applications\",\"volume\":\"42 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1993-04-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Addendum to the proceedings on Object-oriented programming systems, languages, and applications\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/260303.260322\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Addendum to the proceedings on Object-oriented programming systems, languages, and applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/260303.260322","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

计算机行业正面临着软件危机。为了保持竞争力,组织需要不断改进他们用来运行企业的计算机解决方案。然而,构建和维护在异构分布式环境中运行的企业级应用程序系统过于昂贵和耗时,导致大量未满足的需求积压。解决这种软件危机的最有希望的方法之一是通过连接由各种各样的商业软件供应商和内部开发人员开发的软件组件产品来构建软件系统。这种方法允许客户更好地利用他人的工作,从而降低开发成本。它为客户提供了最大的选择自由,实现了更灵活和可配置的企业解决方案。它鼓励软件开发人员之间的竞争,以生产对客户价值最大化的创新组件。它使软件系统能够快速发展,以满足快速变化的业务需求。要使这种基于组件的方法取得成功,必须满足几个要求。使用不同编程语言、在分布式环境中不同类型的机器上运行的独立开发的组件必须能够相互连接。必须能够替换单个组件,同样,新组件可能由不同的开发人员实现,使用不同的编程语言,运行在不同的机器上,可能与原始组件的类型不同。必须能够在不破坏现有软件的情况下,用提供扩展功能的新组件引入或替换现有组件。必须能够在不停止系统的情况下添加或更换组件。应该可以根据组件属性验证组件互连的兼容性。组件之间应该相互隔离,这样软件错误就可以限制并跟踪到特定的组件。必须能够合并现有的“遗留”应用程序,而无需修改或修改最少。这些功能不仅应该适用于传统的应用程序,还应该适用于较小的功能单元,例如文件选择对话框,甚至适用于基本的系统组件,例如文件系统和虚拟内存管理器。在更高的层次上,必须能够互连数据,而不仅仅是程序。例如,必须能够将特定发票与特定客户记录连接起来。系统管理员和用户必须易于进行互连和重新配置组件。例如,应该可以将一组数据移动到不同的…
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Open distributed processing (panel)
The computer industry is facing a software crisis. To remain competitive, organizations need to continually improve the computer solutions they use to run the enterprise. However, constructing and maintaining enterprise wide application systems running in a heterogeneous distributed environment is too expensive and time consuming, resulting in a large backlog of unfulfilled needs. One of the most promising approaches to resolving this software crisis is the idea of constructing software systems by interconnecting software component products developed by a wide variety of commercial software vendors and in-house developers. This approach allows customers to better leverage the work of others, reducing development costs. It offers maximum freedom of choice to the customer, enabling more flexible and configurable enterprise solutions. It encourages competition among software developers to produce innovative components that maximize the value to customers. It enables the rapid evolution of software systems to meet fast changing business requirements. For this component-based approach to be successful, several requirements must be satisfied. It must be possible to interconnect components developed independently, using different programming languages, running on different kinds of machines in a distributed environment. It must be possible to replace individual components, again where the new component might be implemented by a different developer, using a different programming language, running on a different machine, possibly of a different kind than the original component. It must be possible to introduce or replace existing components with new components that provide extended capabilities without breaking existing software. Adding or replacing components must be possible without stopping the system. It should be possible to validate component interconnections for compatibility based on component attributes. Components should be isolated from each other so that software errors can be confined and tracked to a particular component. It must be possible to incorporate existing " legacy " applications with minimal or no modification. These capabilities should apply not just to traditional application programs, but also to smaller functional units, such as a file selection dialog, and even to basic system components, such as file systems and virtual memory managers. At a higher level, it must be possible to interconnect data, not just programs. For example, it must be possible to connect a specific invoice with a specific customer record. It must be easy for system administrators and users to make interconnections and reconfigure components. For example, it should be possible to move a collection of data to a different …
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信