Question

求助，那位好心人帮我翻译一下

The formal analysis of the WS-Coordination and WSBusinessActivity
specifications led to determination of ambigous
areas in the described frameworks. The TLA+
paradigm helped us perform this analysis. During the analysis
phase we uncovered a limitation of the specifications
in terms of applicability to real world scenarios. In our understanding
of SOA this limitation violates the black box
approach to the behaviour of the participants. We accepted
this limitation for the cause of overall interoperability of
our implementation. Further we discovered a structural dependancy
between introduced entities. This also violates
the SOA paradigm. This dependancy could be resolved by
sophisticated design of the WS-BA framework implementation.
The introduction of transactional middleware forms
a loosly-coupled transactional system according to WS-C
and WS-BA specifications. To allow for the mapping between
incoming messages and their corresponding BAs we
took advantage of the extensibility of elements descibed
in WS-C and WS-BA specifications. The easy integration
into existing Web Service scenarios is enabled by the usage
of Proxy System and Decision Engine, whose functionality
is described in the Sec. 5 The communication protocol
defined between the Initiator and Transactor is needed to
guarantee the loose-coupling of system components. The
insights gained during the proof-of-concept implementation
emphasize our analysis and design decisions. The proof-ofconcept
implementation has been exposed to an extended
validation phase using data gathered during the test runs of
an example scenario. The overall experience shows, that the
usage of formal methods during an implementation of Web
Service protocols in SOA helps clarify the protocols under
consideration and raises the confidence of the implementors
into their understanding of the protocols.

Answer 1

WS-协调的正式的分析和 WSBusinessActivity
规格导致了 ambigous 的决心
区域在那描述结构。 TLA+
例帮助了我们运行这一项分析。 在分析期间
状态我们无遮盖的规格的限制
在适用性的期限中对真正的世界情节。 在我们的理解方面
SOA 这限制违犯黑盒子
达成叁加者的行为的$$1方式。 我们一般承认的
为因素的这限制全部的互通性
我们的落实。 更远的我们发现了结构的 dependancy
在介绍实体之间。 这也违犯
SOA 例。 这一 dependancy 可能是下定决心的被
WS-学士学位结构落实的复杂的设计。
交易中间设备表格的介绍
loosly-对 WS-C 根据加倍了交易的系统
而且 WS-学士学位的规格。 考虑到那个映射在
收入信息和他们的对应学士学位我们
利用了元素 descibed 的可延长性
在 WS-C 和 WS-学士学位的规格。 容易的整合
进入现有的网络服务情节之内是根据用法能够
代理系统和决定引擎, 功能性
在 5 段中被描述沟通记录
在创始者和处理者之间定义是不可或缺的到
保证那解放-系统成份的联结。 那
洞察力在证明期间得到--观念落实
强调我们的分析和设计决定。 证明-ofconcept
落实有是暴露的到一广大的
确认状态使用数据聚集在测试期间奔跑
一个例子情节。 全部的经验表演, 哪一那
正式方法的用法在网络的落实期间
在 SOA 的服务记录帮助澄清记录在
考量和举起 implementors 的信心
进入他们的记录的理解之内。