Service-Oriented Business Process Modeling and Performance Evaluation based on AHP and Simu

合集下载

百世物流科技公司及业务介绍

百世物流科技公司及业务介绍

网络引擎 集成供应链
物流合作伙伴 网络引擎
干线运输
区域配送
HUB
城市配送
百世物流资源网
住宅配送
我们的客户(Our Customers)
电子产品类(Electronics)
汽车行业类(Automotive)
BEST Logistics Technology
我们的客户(Our Customers)
机电设备家居(Mechanical Equipment & Home Products)
承运商发展 承运商管理 卡车采购部 新业务发展
公司使命Mission
百世物流科技
依靠在物流和供应链领域的服务创新和强大的信 息处理技术优势,发展成为全球领先的面向企业、社区和电子
商务的综合物流服务创新品牌。
因而,我们投资于“人”和“技术”!
因而顾客至上、优质的服务、 技术及管理上的优越性、
员工的奉献精神以及对所在地社区和环境的奉献 推动公司的不断发展。
BEST Create Value for Customer
百世中国概况 BEST China Overview
公司名称:百世物流科技有限公司
(BEST Logistics Technology Co., Ltd.)
公司性质:外资企业 注册资金:500万美金 总投资额:2000万美金
服务范围:
运输配送、仓储管理、包装、货代、供应链解决方 案设计咨询等一体化物流服务,百世物流拥有所有 从事物流服务所必需的营业执照和许可证。
• 成本意识
Cost control
• 安全意识
Safety control
• 环保新理念
Environment protection

程炜面向Web服务的业务流程管理系统的研究和实现

程炜面向Web服务的业务流程管理系统的研究和实现

程炜面向W e b服务的业务流程管理系统的研究和实现Standardization of sany group #QS8QHH-HHGX8Q8-GNHHJ8-HHMHGN#分类号_______ 密级_______ U D C _______硕士学位论文面向Web服务的业务流程管理系统的研究和实现学位申请人:程炜学科专业:通信与信息系统指导教师:杨宗凯教授论文答辩日期 2003年5月10日学位授予日期答辩委员会主席刘文予评阅人刘文予谭运猛A Thesis Submitted in Partial Fulfillment of the Requirementsfor the Degree of Master of EngineeringResearch and Implementation of Web Service-Oriented BusinessProcess Management SystemCandidate: Cheng WeiMajor: Communication & Information SystemSupervisor : Prof. Yang ZongkaiHuanghzong University of Science & technologyMay 2003摘要近几年,随着电子商务的深入发展,对企业信息化程度提出了更高的要求,如何利用现代网络技术来帮助企业管理各类业务流程,实现业务流程自动化已成为企业关注的热点。

所谓业务流程(Business Process,BP),是指为了在一定时期内达到特定的商业目标,而按照各种商业规则连接起来的业务功能的集合。

这些业务功能是抽象定义的:业务功能的具体实现受限于业务功能运行所需的可用资源。

业务功能的构成由商业目标决定。

业务流程中商业规则的目的是为了业务管理决策的实现。

而业务流程管理(Business Process Management,BPM)是理解、系统化、自动化以及改进公司业务运作方式的一门艺术,它可以看作是文档工作流和企业应用集成的紧密结合。

J2EE常见术语及缩写

J2EE常见术语及缩写

J2EE常见术语及缩写RMIRmote Method Invocation(远程方法调用)用于Java平台中的远程方法调用。

它具有分布式垃圾收集、可自动下载类文件等功能。

位于java.rmi包中。

注意:RMI只能在Java平台中使用。

通过RMI传输的参数必须可以序列化CORBACommon Object Request Broker Architecture(公共对象请求代理体系结构)用于实现独立于平台及编程语言的分布式应用ORBObject Request Broker(对象请求代理)负责具体的网络通信,是构建分布式应用的基础。

STUB与SKELETON存根与骨架无论是RMI还是ORB,其实现本质都是采用了代理模式。

其中存根为客户端使用的代理,拥有通过网络访问远程对象的能力;骨架为远程对象的代理,用来接受存根的调用,并返回结果。

附:在CORBA和JAVA 5中也支持动态调用,即存根不是必须存在的。

RMI-IIOPRemote Method Invocation over the Internet-ORB Protocol(基于互联网的对象请求代理协议实现的远程方法调用)J2EE和EJB事实上的网络通信标准,基于RMI,同时又兼容CORBA,使得EJB组件可以被Java 之外的客户端调用。

位于javax.rmi包中。

话题1:为何J2EE要兼容CORBACORBA是OMG(对象管理组织)推出的成功的分布式对象通信标准,为了占领企业级市场,EJB必须考虑和遗留系统的集成,以及为异构系统提供服务,这都需要采用更加通用的CORBA,而不是只能在Java平台下使用的RMI。

话题2:引入CORBA之后面临的问题1,分布式垃圾收集:并非所有支持CORBA的语言都有垃圾收集机制。

2,窄化(Narrowing):当通过RMI或RMI-IIOP获取一远程对象时,实际上获取的是其存根(Stub)。

在RMI中,会自动下载此存根;而CORBA没有这个机制,必须用额外的方法解决(其实是通过javax.rmi.PortableRemoteObject的narrow方法解决的)。

工业4.0总体方案架构

工业4.0总体方案架构

应用场景 Application Scenario
1. 流程质量管理 (Process Quality Manager) 2. 远端服务管理 (Remote Service
Manager) 3. 预测维护 (Predictive Maintenance)
1. 提出定制化车型要求 2. 连接相关服务 3. 根据定制化数据,进行生产
数据源
探源
传感器、系统
跨部门联盟,未 来将起决定性的 实时数据计数器 作用,例如工业 公司与软件及供 应商联盟
事件处理和不同的可视化异构来源
事件处理、数据集成
智慧社区
统计分析和事件的相关性和历史来源、 决策支持
互联
集成 分析
数据分析、建模
智慧城市 智慧家庭 智慧工厂 智慧能源
可视化、规则、定制
信息可视化 基于角色与门户网站中 存储的业务规则
9
3.2 1.3
发货 校验、调整
IBM Smarter Planet | IBM“智慧地球”与工业4.0
IBM“智慧地球”密切关联并支撑工业4.0
智慧地球
工业 4.0的5个核心能 力
数据
探源

传感器、系统
跨部门联盟,未 来将起决定性的 实时数据计数器 作用,例如工业 公司与软件及供 应商联盟
事件处理和不同的可视化异构来源
安筱鹏:工业和信息化部电子信息司副司长
技术与资本将成为工业4.0时代的两大驱动力。高度自动 化、高度信息化和高度网络化将成为工业4.0时代的特征。
4
Industry 4.0 Viewpoints | 工业4.0全息视角
• 德国提出了工业4.0 • 美国提出了产业互联网 • 日本的复活方程式

面向服务概述

面向服务概述

Basic Profile, Basic Security Profile
SOA Standards Organizations
23
几个面向服务的原则源自面向对象的原则
◦ abstraction
-- decomposition
◦ Encapsulation
-- Reusability
◦ Interface first
Organization X
Organization Y
Organization Z
2021/3/6
9
Research & Development
Accounting
Marketing
Distributed Data Distributed Computation Distributed users …..
节约成本
◦ 通过削减整体花费降低成本。
敏捷业务
◦ 由于恶性竞争,每一个错过的商业机会的企业职位低于其竞争对手。 有能 力的企业能够快速应对各种业务的刺激将是关键的生存。
◦ 更快的上市时间,提高客户满意度,还客户的忠诚度。这样的结果是增加 了商业和更高的收入。
◦ 能够提供按需服务,实时24 / 7 。 ◦ 无缝协作的合作伙伴和客户有助于提高服务质量和上市时间。
任务的具体IT构件 1:1 影射。
SOA的定义仍在发展变化.
◦ 一组能够被调用的构件,并且其接口描述能够被 发布和发现 (W3C).
◦ SOA是一种client/server 设计方法,其中的应
用程序由软件服务和软件服务消费者组成 (also known as clients or service requesters). SOA 不同于一般的client/server 模式,其定义 强调软件构件中的松耦合,并且采用分离的接 口 (Gartner).

面向服务设计模式下工作流系统平台论文

面向服务设计模式下工作流系统平台论文

面向服务设计模式下的工作流系统平台摘要:随着网络技术的发展以及高校图书馆信息量的增大,传统模式下的工作流系统暴露出诸多问题,通过分析传统模式下的工作流系统的优缺点,并针对其不足,提出了面向服务设计模式下的工作流系统平台,阐述了该平台的结构,并通过对比,详细分析面向服务设计模式下的工作流系统平台的优势以及其重要性。

关键词:面向服务;工作流系统;图书馆;应用信息系统中图分类号:tp391文献标识码:a文章编号:1007-9599 (2011) 24-0000-02workflow systemplatform under service-oriented design mode—the application of information systems in the university librarywang lun,liu mingyue,chen jingru(huazhong normal university,wuhan430079,china)abstract:with the development of network technology and the increasing amount of information in university libraries,the traditional mode of workflow system revealed many problems,by analyzing the traditional mode of workflow system’s advantages and disadvantages,for its disadvantages,it proposes service-oriented workflow design mode platform.it explains the structure of the platform,andby comparing the two workflow systems and the detailed analysis of the advantages of the service-oriented workflow design mode,it analyzes the importance of theservice-oriented workflow design mode platform.keywords:service-oriented;workflowsystem;libraries;application information system一、引言随着计算机网络的高速发展,网络成为推动信息化建设的重要载体。

Oracle BPM 套件:一份关于 Oracle Corporation 的商业流程管理工具的介绍

An Ontological Approach to Oracle BPMJean Prater, Ralf Mueller, Bill BeauregardOracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065, USA **********************,***********************,*****************************The Oracle Business Process Management (Oracle BPM) Suite is composed oftools for Business Analysts and Developers for the modeling of BusinessProcesses in BPMN 2.0 (OMG1 standard), Business Rules, Human Workflow,Complex Events, and many other tools. BPM operates using the commontenants of an underlying Service Oriented Architecture (SOA) runtimeinfrastructure based on the Service Component Architecture (SCA). OracleDatabase Semantic Technologies provides native storage, querying andinferencing that are compliant with W3C standards for semantic (RDF/OWL)data and ontologies, with scalability and security for enterprise-scale semanticapplications.Semantically-enabling all artifacts of BPM from the high-level design of aBusiness Process Diagram to the deployment and runtime model of a BPMapplication promotes continuous process refinement, enables comprehensiveimpact analysis and prevents unnecessary proliferation of processes andservices. This paper presents the Oracle BPM ontology based upon BPMN 2.0,Service Component Architecture (SCA) and the Web Ontology Language(OWL 2). The implementation of this ontology provides a wide range of usecases in the areas of Process Analysis, Governance, Business Intelligence andSystems Management. It also has the potential to bring together stakeholdersacross an Enterprise, for a true Agile End-to-End Enterprise Architecture.Example use cases are presented as well as an outlook of the evolution of theontology to cover the organizational and social aspects of Business ProcessManagement.1.IntroductionIn the 1968 film, 2001: A Space Odyssey, the movie’s antagonist, HAL, is a computer that is capable not only of speech, speech recognition, and natural language processing, but also lip reading, apparent art appreciation, interpreting and reproducing emotional behavior, reasoning, and playing chess, all while maintaining the systems on an interplanetary mission. While the solution we present in this paper does not possess all of the capabilities of HAL, the potential benefits of combining semantic technology with Oracle BPM provides the ability to define contextual relationships between business processes and provides the tools to use that context so that ‘software agents’ (programs working on behalf of people) can find the right1 Object Management Group, see 2 Jean Prater, Ralf Mueller, Bill Beauregardinformation or processes and make decisions based on the established contextual relationships.Organizations can more efficiently and effectively optimize their information technology resources through a service-oriented approach leveraging common business processes and semantics throughout their enterprise. The challenge, however, with applications built on Business Process Management (BPM) and Service Oriented Architecture (SOA) technology is that many are comprised of numerous artifacts spanning a wide range of representation formats. BPMN 2.0, the Service Component Architecture Assembly Model, Web Service definitions (in the form of WSDL), XSLT transformations, for example are all based on well defined but varying type models. To answer even simple queries on the entire BPM model, a user is left with a multitude of API’s and technologies, making the exercise difficult and highly complicated. Oracle has developed an ontology in OWL that encompasses all the artifacts of a BPM application and is stored in Oracle Database Semantic Technologies that provides a holistic view of the entire model and a unified and standardized way to query that model using SPARQL.Oracle is actively involved in the standards process and is leading industry efforts to use ontologies for metadata analysis. Oracle is also investigating the integration of organizational and social aspects of BPM using FOAF2. BPMN 2.0 task performers can be associated with a FOAF Person, Group or Organization and then used in Social Web activities to enable Business Users to collaborate on BPM models.1.1 BenefitsThe benefits of adding semantic technology to the database and to business process management in the middleware, driven by an underlying ontology are three fold:1.It promotes continuous process refinement. A less comprehensive processmodel can evolve into a complete executable process in the same model.2.It makes it easy to analyze the impact of adding, modifying or deletingprocesses and process building blocks on existing processes and webservices.3.It helps prevent unnecessary proliferation of processes and services. Combining semantic technology and business process management allows business users across organizational boundaries to find, share, and combine information and processes more easily by adding contextual relationships.1.2 Customer Use CaseThe US Department of Defense (DoD) is leading the way in the Federal Government for Architecture-driven Business Operations Transformation. A vital tenet for success is ensuring that business process models are based on a standardized representation, thus enabling the analysis and comparison of end to end business processes. This will lead to the reuse of the most efficient and effective process patterns (style guide), comprised of elements (primitives), throughout the DoD Business Mission Area. A key principle in DoD Business Transformation is its focus on data ontology. The 2 The Friend of a Friend (FOAF) project, see An Ontological Approach to Oracle BPM 3 Business Transformation Agency (BTA), under the purview of the Deputy Chief Management Officer (DCMO), has been at the forefront of efforts to develop a common vocabulary and processes in support of business enterprise interoperability through data standardization. The use of primitives and reuse of process patterns will reduce waste in overhead costs, process duplication and building and maintaining enterprise architectures. By aligning the Department of Defense Architecture Framework3 2.0 (DoDAF 2.0) with Business Process Modeling Notation 2.0 (BPMN 2.0) and partnering with industry, the BTA is accelerating the adoption of these standards to improve government business process efficiency.2.The Oracle BPM OntologyThe Oracle BPM ontology encompasses and expands the BPMN 2.0 and SCA ontologies. The Oracle BPM ontology is stored in Oracle Database Semantic Technologies and creates a composite model by establishing relationships between the OWL classes of the BPMN 2.0 ontology and the OWL classes of the SCA runtime ontology. For example, the BPMN 2.0 Process, User Task and Business Rule Task are mapped to components in the composite model. Send, Receive and Service Tasks, as well as Message Events are mapped to appropriate SCA Services and References and appropriate connections are created between the composite model artifacts. Figure 1 illustrates the anatomy of the Business Rule Task “Determine Approval Flow” that is a part of a Sales Quote demo delivered with BPM Suite.Figure 1: Anatomy of a BPMN 2.0 Business Rule Task4The diagram shows that the Business Rule Task “Determine Approval Flow” is of BPMN 2.0 type Business Rule Task and implemented by a SCA Decision Component that is connected to a BPMN Component “RequestQuote”. Also of significance is that the Decision Component exposes a Service that refers to a specific XML-Schema, which is also referred to by Data Objects in the BPMN 2.0 process RequestQuote.bpmn.3See /products/BEA_6.2/BEA/products/2009-04-27 Primitives Guidelines for Business Process Models (DoDAF OV-6c).pdf4 Visualized using TopBraid Composer TM4 Jean Prater, Ralf Mueller, Bill Beauregard3.An Ontology for BPMN 2.0With the release of the OMG BPMN 2.0 standard, a format based on XMI and XML-Schema was introduced for the Diagram Interchange (DI) and the Semantic Model. Based on the BPMN 2.0 Semantic Model, Oracle created an ontology that is comprised of the following5:•OWL classes and properties for all BPMN 2.0 Elements that are relevant for the Business Process Model.6The OWL classes, whenever possible,follow the conventions in the BPMN 2.0 UML meta model. OWL propertiesand restrictions are included by adding all of the data and object propertiesaccording to the attributes and class associations in the BPMN 2.0 model.7•OWL classes and properties for instantiations of a BPMN 2.0 process model. These OWL classes cover the runtime aspects of a BPMN 2.0process when executed by a process engine. The process engine createsBPMN 2.0 flow element instances when the process is executed. Activitylogging information is captured, including timestamps for a flow elementinstance’s activation and completion, as well as the performer of the task. The implicit (unstated) relationships in the Oracle BPM ontology can be automatically discovered using the native inferencing engine included with Oracle Database Semantic Technologies. The explicit and implicit relationships in the ontology can be queried using Oracle Database Semantic Technologies support for SPARQL (patterns matching queries) and/or mixed SPARQL in SQL queries. [6] Example SPARQL queries are shown below:Select all User Tasks in all Lanesselect ?usertask ?lanewhere {usertask rdf:type bpmn:UserTask .usertask bpmn:inLane lane}Select all flow elements with their sequence flow in lane p1:MyLane (a concrete instance of RDF type bpmn:Lane)select ?source ?targetwhere {flow bpmn:sourceFlowElement source .flow bpmn:targetFlowElement target .5 All of the classes of the BPMN 2.0 meta model that exists for technical reasons only (model m:n relationship or special containments) are not represented in the ontology6 The work in [2] describes an ontology based on BPMN 1.x for which no standardized meta model exists7 Oracle formulated SPARQL queries for envisioned use cases and added additional properties and restrictions to the ontology to support those use casesAn Ontological Approach to Oracle BPM 5 target bpmn:inLane p1:MyLane}Select all activities in process p1:MyProcess that satisfy SLA p1:MySLA select ?activity ?activityInstancewhere {activity bpmn:inProcess p1:MyProcess .activityInstance obpm:instanceOf activity .activityInstance obpm:meetSLA p1:MySLA}A unique capability of BPMN 2.0, as compared to BPEL, for instance, is its ability to promote continuous process refinement. A less comprehensive process model, perhaps created by a business analyst can evolve into a complete executable process that can be implemented by IT in the same model. The work sited in Validating Process Refinement with Ontologies[4] suggests an ontological approach for the validation of such process refinements.4.An Ontology for the SCA composite modelThe SCA composite model ontology represents the SCA assembly model and is comprised of OWL classes for Composite, Component, Service, Reference and Wire, which form the major building blocks of the assembly model. Oracle BPM ontology has OWL classes for concrete services specified by WSDL and data structures specified by XML-Schema. The transformation of the SCA assembly model to the SCA ontology includes creating finer grained WSDL and XML-Schema artifacts to capture the dependencies and relationships between concrete WSDL operations and messages to elements of some XML-Schema and their imported schemata.The SCA ontology was primarily created for the purpose of Governance and to act as a bridge between the Oracle BPM ontology and an ontology that would represent a concrete runtime infrastructure. This enables the important ability to perform impact analysis to determine, for instance, which BPMN 2.0 data objects and/or data associations are impacted by the modification of an XML-Schema element or which Web Service depends on this element. This feature helps prevent the proliferation of new types and services, and allows IT to ascertain the impact of an XML-Schema modification.5.The TechnologiesAs part of the customer use case, as referenced in section 1.2 above, we implemented a system that takes a BPM Project comprised of BPMN 2.0 process definitions, SCA assembly model, WSDL service definitions, XML-Schema and other metadata, and created appropriate Semantic data (RDF triples) for the Oracle BPM ontology. The6 Jean Prater, Ralf Mueller, Bill Beauregardtriples were then loaded into Oracle Database Semantic Technologies [3] and a SPARQL endpoint was used to except and process queries.6.ConclusionOracle BPM ontology encompasses and expands the generic ontologies for BPMN 2.0 and the SOA composite model to cover all artifacts of a BPM application from a potentially underspecified8process model in BPMN 2.0 down to the XML-Schema element and type level at runtime for process analysis, governance and Business Intelligence. The combination of RDF/OWL data storage, inferencing and SPARQL querying, as supported by Oracle Database Semantic Technologies, provides the ability to discover implicit relationships in data and find implicit and explicit relationships with pattern matching queries that go beyond classical approaches of XML-Schema, XQuery and SQL.7.AcknowledgementsWe’d like to thank Sudeer Bhoja, Linus Chow, Xavier Lopez, Bhagat Nainani and Zhe Wu for their contributions to the paper and valuable comments.8.References[1] Business Process Model and Notation (BPMN) Version 2.0,/spec/BPMN/2.0/[2] Ghidini Ch., Rospocher M., Serafini L.: BPMN Ontology,https://dkm.fbk.eu/index.php/BPMN_Ontology[3] Oracle Database Semantic Technologies,/technetwork/database/options/semantic-tech/[4] Ren Y., Groener G., Lemcke J., Tirdad R., Friesen A., Yuting Z., Pan J., Staab S.:Validating Process Refinement with Ontologies[5] Service Component Architecture (SCA), [6] Kolovski V., Wu Z., Eadon G.: Optimizing Enterprise-Scale OWL 2 RL Reasoning in aRelational Database System, ISWC 2010, page 436-452[7] “Use of End-toEnd (E2E) Business Models and Ontology in DoD Business Architectures”;Memorandum from Deputy Chief Management Office; April 4, 2011, Elizabeth A.McGrath, Deputy DCMO.[8] “Primitives and Style: A Common Vocabulary for BPM across the Enterprise”; DennisWisnosky, Chief Architect & CTO ODCMO and Linus Chow Oracle; BPM Excellence in Practice 2010; Published by Future Strategies, 20108A BPMN 2.0 model element is considered underspecified, if its valid but not all attribute values relevant for execution are specified.。

SOA学习笔记

面向服务的体系结构SOA学习笔记一、SOA概述1.SOA(Service-Oriented Architecture)定义SOA是指为了解决在Internet环境下业务集成的需要,通过连接能完成特定任务的独立功能实体实现的一种软件系统架构。

•SOA不是一种语言,也不是一种具体的技术而是一种软件系统架构,它尝试给出在特定环境下推荐采用的一种架构, 面向不同的应用场景,用来满足不同的特定需求• SOA的使用范围:需求决定同时也限制功能.主要的应用场合在于解决在Internet环境下的不同商业应用之间的业务集成问题.SOA 架构具有一些典型特性,主要包括松耦合性,位置透明性以及协议无关性。

松耦合性要求SOA 架构中的不同服务之间应该保持一种松耦合的关系,也就是应该保持一种相对独立无依赖的关系;位置透明性要求SOA 系统中的所有服务对于他们的调用者来说都是位置透明的,也就是说每个服务的调用者只需要知道他们调用的是哪一个服务,但并不需要知道所调用服务的物理位置在哪里;而协议无关性要求每一个服务都可以通过不同的协议来调用。

soa 就是使用xml的描述语言来描述接口的技术,SOA架构体系正是软件工程发展一个有标志性里程碑也是开关原则的必然出现的架构.SOA其实体现的是:分离关注点他和J2EE(JavaEE5)的JDBC/JDNI思路是一样的,而WebService只是他的一种行业标准化的结果而已,而并不是SOA就是SOAP(只是SOAP只是SOA的一种体现),概括的说就是一个总线上用标准插件的方式去实现业务的脱耦。

二、SOA三大基本特征1 独立的功能实体SOA架构中提供服务的功能实体的完全独立自主的能力,实体自我管理和恢复能力.常见自我恢复的技术:事务处理(Transaction),消息队列(Message Queue),冗余部署(Redundant Deployment)和集群系统(Cluster)理解:完全独立自主的能力,不同与传统的组件技术,如.NET Remoting,EJB,COM或者CORBA,都需要有一个宿主(Host或者Server)来存放和管理这些功能实体;当这些宿主运行结束时这些组件的寿命也随之结束。

Java专业术语


C:
22.C2B:Consumer-to-Business(客户对业务)
23.CAD:ComputerCAM:Computer Aided Modeling(计算机辅助建模)
25.case-insensitive:大小写不敏感
26.case-sensitive:大小写敏感
116.procedural:过程的
117.profiling:配置
118.prototype:原型
Q:
119.queue:队列
R:
120.RAD:Rapid application development(快速应用开发)
121.RCS:Revision Control System(修订控制系统)
131.SPI:Service Provider Interface(服务提供接口)
132.Spring:
133.SQL:Structured Query Language(结构化查询语句)
134.Struts:一种基于MVC模式的Web应用程序框架
135.surrogate keys:替代键
108.node:节点
O:
109.ODMG:Object Data Management Group(对象数据管理组织)
110.OGNL:Object Graph Navigation Language(对象图导航语言)
111.OODBMS:Object-Oriented Database Management System(面向对象数据库管理系统)
44.Declarative Programming:声明是编程
45.delegate:委托

UML案例研究、工具和业务视图

关于本系列本系列详细地介绍了使用IBM® Rational® Software Architect 工具为面向服务的体系结构(service-oriented architectures,SOA)建模。

虽然本教程主要面向软件架构师,但是也应该有助于软件开发过程中的其他角色。

这些角色可能包括业务分析人员(特别是对于第 1 部分),或者将架构作为输入来执行他们的活动(架构分析、设计,和实现)的软件设计人员和开发人员。

本系列还涵盖了许多有益于广大读者的核心的 SOA 概念。

本系列教程教您如何做以下三种东西:∙架构:描述架构是由什么组成的,以及它适合用在整个软件开发过程中的哪个地方。

∙服务:用 SOA 构架系统。

服务是该架构的中心。

∙模型:说明 Rational Software Architect 工具如何支持面向服务体系结构的规范的模型驱动开发(Model-Driven Development,MDD)方法。

本系列开始将介绍软件架构,并确定服务在软件架构中的位置。

然后将展示Rational Software Architect 及其基于 SOA 和与架构相关的特性。

本系列将通过虚构的在线 DVD 租赁案例研究,进行以下工作:∙说明作为服务架构活动的输入的工作产品,包括组件业务模型、业务过程模型、系统用例模型,和设计模型的外部系统部件。

∙逐步说明在 Rational Software Architect 中如何指定表现架构的服务模型,包括服务消费者、服务规范、服务划分、原子的和复合的服务提供方、服务、服务协作、服务交互,及服务通道。

∙说明在软件开发过程的后来阶段,例如设计和实现,中如何使用服务模型。

关于本教程本教程,系列的第 1 部分,将介绍贯穿本系列所使用的视频租赁案例研究。

它还介绍了工具 Rational Software Architect(Version 7 和之后的版本),以及您将用于服务架构建模的特性。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

implemented by system simulation in this paper. Our main contribution is that, with profound analyses on the service-oriented process modeling and its performance metrics correlations among service, SOBP, and enterprise, we made a AHP and simulation-based performance evaluation method applicable to evaluating performance of business process in a loosely coupled environment like that of service-oriented computing. The rest of the paper is organized as follows. We analyze the performance attributes of service and SOBP and their modeling method in section 2, and propose their performance metrics in section 3, the corresponding AHP-simulation-based calculation algorithm is presented in section 4 and a full case is illustrated in section 5. Finally, conclusions and promising future work are given in section 6.
With the evolution of Grid technologies and the application of Service-Oriented Architecture (SOA), more and more enterprises are integrated and collaborated with each other in a loosely coupled environment. A business process in that environment, i.e., the Service-Oriented Business Process (SOBP), shows highly flexibility for its free selection and composition of different services. The performance of the business process usually has to be evaluated and predicted before its being implemented. And it has special features since it includes both business-level and IT-level attributes. However, the existing modeling and performance evaluation methods of business process are mainly concentrated on business-level performance. And the researches on service selection and composition are usually limited to the IT-level metrics. An extended activity-network-based SOBP Model, its three-level performance metrics, and the corresponding calculation algorithm are proposed to fulfill these requirements. The advantages of our method in SOBP modeling and performance evaluation are highlighted also. with both the business-level and IT-level attributes of SOBP is needed earnestly. And the method will be used not only to decide the service selection and composition such as [2][3][4][5], but also to assess the suitability about the services selected with the resources, organization structures, business rules, and other activities of the enterprise to which the SOBP belongs. However, the researches of [6]-[10] on service selection and composition based on Quality of Service (QoS) were focused on the IT-attributes mainly and often neglected the business performance being impacted by the services selected. For example, [10] proposed the QoS such as service price, time, reputation, availability, successful rate, and relations among services. But its evaluation almost not concerned with the resources, organization structure, and so on of the enterprise to which it will be used. And the traditional performance evaluations of business process ([11]-[15]) were usually concentrated on the business -attributes only. Business process indexes of Balanced Score Card comprise product demand rate, product sale rate, production flexibility, and order advance [11]. Process performance metrics of SCOR includes reliability, responsiveness, flexibility, cost, and assets [12]. And [13][14][15] analyzed the performance attributes of time, ratio of resources utilization, and cost. They evaluated the business –process’s performance without considering the IT-attributes at all. Reference [6] proposed a simulation-oriented workflow model and with which the simulation engine would calculate parameters predefined in it at the build-time of modeling. And [16] has developed an interactive-event-based workflow simulation in service-oriented computing environment. But they did not deal with the modeling and performance evaluation of SOBP. In order to address the above issues, we will propose a comprehensive performance metrics with corresponding calculation algorithm that can be
helpful to the modeling of SOBP.
Fig.1. Relations between IT application and business process Consequቤተ መጻሕፍቲ ባይዱntly, the modeling process of SOBP would comprise three steps: Step 1: To construct the abstract-process that includes some abstract service (ASV); Step 2: Every ASV will select some candidate physical service (PSV) from UDDI according to the predefined matching algorithms. And the PSVs of an ASV will be ordered by some criteria. Step 3: Select just only one PSV for each ASV, and compose all the selected PSVs with other activities of the abstract-process to form a complete SOBP.
相关文档
最新文档