arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv cs/0204036cs.SE
收藏

语义成分合成

Semantic Component Composition

Joseph R. Kiniry

摘要:

构建复杂的软件系统需要使用基于组件的体系结构。从理论上讲,在设计所需的组件集中,只有一小部分是“定制的”;其余的都是重用或重构现有的软件。不幸的是,这是一种理想化的情况。仅仅因为两个组件应该一起工作并不意味着它们将一起工作。将组件粘合在一起的“胶水”不仅仅是技术。将复杂系统绑定在一起的契约隐式地定义了比显式类型更多的东西。这些“概念契约”描述了系统外语义的基本方面:例如,对象模型、类型系统、数据表示、接口操作语义、法律和合同义务等等。设计人员和开发人员花费大量的时间在技术上对系统进行管道录音以实现这些概念契约,因为系统范围的语义尚未被严格地描述或编码。本文描述了一个正式的表征问题,并讨论了初步实施所产生的理论体系。

英文摘要:

Building complex software systems necessitates the use of component-based architectures. In theory, of the set of components needed for a design, only some small portion of them are "custom"; the rest are reused or refactored existing pieces of software. Unfortunately, this is an idealized situation. Just because two components should work together does not mean that they will work together. The "glue" that holds components together is not just technology. The contracts that bind complex systems together implicitly define more than their explicit type. These "conceptual contracts" describe essential aspects of extra-system semantics: e.g., object models, type systems, data representation, interface action semantics, legal and contractual obligations, and more. Designers and developers spend inordinate amounts of time technologically duct-taping systems to fulfill these conceptual contracts because system-wide semantics have not been rigorously characterized or codified. This paper describes a formal characterization of the problem and discusses an initial implementation of the resulting theoretical system.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑