Web Services Workflows—Composition, Co-Ordination, and Transactions in Service-Oriented Computing

Web services can be seen as a newly emerging research area for Service-oriented Computing and their implementation in Service-oriented Architectures. Web services are self-contained, self-describing modular applications or components providing services. Web services may be dynamically aggregated, composed, and enacted as Web services Workflows. This requires frameworks and interaction protocols for their co-ordination and transaction support. In a Service-oriented Computing setting, transactions are more complex, involve multiple parties (roles), span many organizations, and may be long-running, consisting of a highly decentralized service partner and performed by autonomous entities. A Service-oriented Transaction Model has to provide comprehensive support for long-running propositions including negotiations, conversations, commitments, contracts, tracking, payments, and exception handling. Current transaction models and mechanisms including their protocols and primitives do not sufficiently cater for quality-aware and long running transactions comprising loosely-coupled (federated) service partners and resources. Web services transactions require co-ordination behavior provided by a traditional transaction mechanism to control the operations and outcome of an application. Furthermore, Web services transactions require the capability to handle the co-ordination of processing outcomes or results from multiple services in a more flexible manner. This requires more relaxed forms of transactions—those that do not strictly have to abide by the ACID properties—such as loosely-coupled collaboration and workflows. Furthermore, there is a need to group Web services into applications that require some form of correlation, but do not necessarily require transactional behavior. The purpose of this paper is to provide a state-of-the-art review and overview of some proposed standards surrounding Web services composition, co-ordination, and transaction. In particular the Business Process Execution Language for Web services (BPEL4WS), its co-ordination, and transaction frameworks (WS-Co-ordination and WS-Transaction) are discussed.

基于SPEM2XPDL模型转换的软件过程执行

SPEM(software process engineering metamodel)是国际标准化组织制定的标准元模型,正日益成为软件过程建模领域的行业标准,但在过程执行方面,SPEM还存在不足.将软件过程看作是一种特殊的工作流,提出了一种应用工作流运行机制支持软件过程执行的方法.通过将SPEM模型转换为XPDL(XML process definition language)模型,利用XPDL引擎支持SPEM模型的执行.制定了SPEM和XPDL之间的映射规则,设计了转换算法并开发了转换引擎.该方法被应用在SoftPM项目中,成功地基于XPDL引擎Shark实现了对软件过程模型的执行支持.

移动对象数据库模型、查询语言及实时交通流分析

提出一种移动对象数据库模型——Dynamic Transportation Network Based Moving Objects Database(简称DTNMOD),并给出了DTNMOD中基于移动对象时空轨迹的网络实时动态交通流分析方法.在DTNMOD中,交通网络被表示成动态的时空网络,可以描述交通状态、拓扑结构以及交通参数随时间的变化过程;网络受限的移动对象则用网络移动点表示.DTNMOD模型包含了完整的数据类型和查询操作的定义,因此可以在任何可扩充数据库(如PostgreSQL或SECONDO)中实现,从而得到完整的数据库模型和查询语言.为了对相关模型的性能进行比较与分析,基于PostgreSQL实现了一个原型系统并进行了一系列的实验.实验结果表明,DTNMOD提供了良好的区域查询及连接查询性能.

事件驱动的BPEL引擎架构设计与实现

WS-BPEL(Web Service Business Process Execution Language，简称BPEL)是Web服务规范族中服务复合层的重要标准。BPEL支持通过对Web服务的编制(Orchestration)来构建业务流程，从而使编程人员能够集中关注业务逻辑。BPEL引擎系统是一个支持BPEL语言描述的业务流程运行的服务器中间件系统，使用BPEL引擎可以执行BPEL语言编写的业务流程。作为一个网络服务器系统，BPEL引擎将不可避免的处理大量的并发请求。如何设计实现BPEL引擎使之能高效的处理并发将是高性能BPEL引擎设计的关键问题。 并发服务器系统通常采用多线程和事件驱动两种并发模型。传统上大多数服务器软件都建立在多线程(或多进程)模型的基础上。但在高负载条件下，过多的线程和线程间的上下文切换会造成系统较大的开销，这些开销是导致系统性能下降的主要原因。事件驱动模型是一种只采用少量固定数量线程的并发模型，一般说来，它的伸缩性更好，并且有更高的处理效率。 本文对高并发服务器系统中所使用的事件驱动模型进行了分析和研究，并且结合BPEL语言规范的特点，提出了事件驱动的BPEL引擎实现技术方案。论文重点研究了BPEL事件结构和有限状态机(Finite State Machine，简称FSM)刻画BPEL流程和活动行为的原理，针对BPEL语言语法特点，构造了完整的BPEL FSM模型，包括了状态空间和基于ECA(Event-Condition-Action)模式的状态转移规则。 在基于事件驱动模型的BPEL引擎架构原理的指导下，我们设计并实现了基于事件驱动模型的OnceBPEL2.0引擎系统。并且，我们对采用多线程模型实现的OnceBPEL1.0系统和采用事件驱动模型实现的OnceBPEL2.0系统进行了性能测试和分析比较。从我们的测试数据和分析结果可以看出，采用事件驱动模型的OnceBPEL2.0系统比采用多线程模型的OnceBPEL1.0有了较大的性能提升。

An Integrated Solution for Software Process Improvement

Since 1990s, the software industry in China has been developed very rapidly and the total revenue in recent three years of 2005, 2006 and 2007 were 390.0, 480.0, and 583.4 billions RMB respectively, increased by 28.3% annually on an average basis [1]. By the end of 2007, there were about 18,000 software enterprises in China, and the population of software professionals was 1.48 millions roughly. In the global software market, China, with annual revenue about 82.2 billions USD (8.74% of the total: 940 billions USD), currently ranks on the fourth after USA, EU and Japan. However, the software industry in China is still comparatively weak. Most software enterprises have only tens of employees and millions RBM of revenue. And the software development productivity in China varies highly across the software industry in terms of organization, development type, business area, region, language, project size and team size [2]. Co-operative efforts from the government, the industry and the academy are needed [3]. Continuous software process improvement is an effective way to change the challenging situation of the software industry in China.