Possibilities of Business Process Modeling Language and UML 2.0 are analyzed for definition of e-business processes. The advantages and comparison of these new languages are represented using auction process model in UML 1.4, UML 2.0 and BPMN. Lastly, structured process modeling methodology is represented. That will give business users the ability to make activity process model in the shape of a acycle graph, that is easy transformable to business process execution language BPEL4WS.

Because of the advance of Internet and the outsourcing, multi-company cooperation is imperative under this circumstance. In order to monitor states between partners during execution, this thesis develops exception handling mechanisms based on Web service stack. After detecting exceptions, the first step is to make use of the fault handler and compensation handler provided by the BPEL4WS specification to roll back planned or even executed business processes belonging to the same scope to the original state. The second step is to utilize the resources searching mechanism, including BE4WS and BCME, to find suitable substitutes to make a replacement or find fitting partners to cooperate with the original one. The third step is to take advantage of the extensibility, flexibility and scalability of BPEL4WS business process to adjust and re-form a new one to handle this unexpected situation. This study uses the LCD supply chain as an example to evaluate the proposed exception handling mechanisms. The result shows that the proposed methods obtain encouraging performance. The major contribution of this research is the initiation efforts on developing exception handling mechanisms based on Web service technologies to improve the exception handling performance.

Emergency response is a time critical work that needs team work from different organizations with various specialties. It also needs to integrate existing information system to collect and assemble necessary knowledge and resources for critical emerging tasks and use it to plan for collaborative problem solving In this study, we propose the methodology to automate the traditional emergency patient transfer process by connecting different organization¡¦s information systems through Web services with BPEL4WS. Via Web services, the medical resources information can be requested according to patient conditions, and resource reservation decision can be made online. Via BPEL4WS, heterogeneous information systems in different organizations can be connected and executed automatically in any predefined process without limit human intervention. The willingness of hospitals to share various levels of resource availability information to Emergency Operation Center (EOC) to coordinate regional medical resource distribution is critical to make Web service platform work. Therefore, this study examines the correlation of individual hospitals¡¦ performance in terms of resource utilization with hospital¡¦s information sharing with EOC. We investigate the effects from sharing information to EOC which adopts three policies of releasing hospital status information through simulation under different conditions in emergency occurrence and occupied hospital resources. Our findings from the simulations imply that the best policy for EOC to adopt in order to make Web services workable in handling medical emergency is to accord different conditions to adopt different suitable policies. For hospitals, if they want to get the maximum resources utilization, it had better to refer to different condition to adopt different information sharing strategies.

組織扁平化趨勢中最重要的議題之ㄧ，就是如何有效的管理更多的員工與更複雜的流程。目前已經許多新穎的標準與技術規格來解決企業流程自動化與溝通的問題，像是網路服務商業流程執行語言（Business process execution language for web services，以下簡稱BPEL4WS）這樣的標準，不過對於員工與流 程之間的對應關係還是著墨甚少，管理者想要掌握企業流程執行的情況和員工的責任歸屬這樣的需求尚待滿足。 本研究試圖利用延伸標記語言（Extensible markup language，以下簡稱XML）相關技術，建立一紀錄員工與其負責流程的對應檔案。透過圖形化的操作介面，讓管理者可以了解企業經營現況，並能夠依照現況更新對應檔案內的紀錄，帶來對應視覺化、責任追蹤、容易調整及接掌迅速等益處，增加管理上的效率。

<p>This master’s thesis discusses the evolution of DataPartner’s application "Inventera". Inventera is designed to do inventory of stock on handheld computers and integartes with SPCS Administration. Inventera is enhanced with a wireless connection and the SPCS API is wrapped with Web Services. The theoretical part of this thesis examines diffrent possibilities to increase reusability by using web service technology when developing software. A case study of the SPCS API is used in order to study differences between using no Web Services at all, static web services or dynamic web services.</p>

Web Services are self-contained, self-describing, modular applications that can be published, located, and invoked through XML artefacts across the Web. Web services technologies can be applied to many kinds of applications, where they offer considerable advantages compared to the old world of product-specific APIs, platform-specific coding, and other &ldquo / brittle&rdquo / technology restrictions. Currently there are millions of web services available on the web due to the increase in e-commerce business volume. Web services can be discovered using public registries and invoked through respective interfaces. However how to automatically find, compose, invoke and monitor the web services is still an issue. The automatic discovery, composition, invocation and monitoring of web services require that semantics will be attached to service definitions. The focus of this thesis is on the composition of web services. The approach taken is to extend the DAML-S ontology that is used to define the semantics of services to include the &ldquo / succeeding services&rdquo / for any service provided. These definitions for individual service instances are declared by the service providers. They are presented to the users of the service to construct a workflow in a mobile environment. The workflow generated is represented both graphically in the mobile device and in XML-format as a BPEL4WS document. The aim of this thesis is to prove that it is possible to build a semi-automatic web service composition utility incorporating semantic constructs, using a mobile device. The generated workflow is suitable for deployment on an engine where it can be executed multiple times with different configurations.

This master’s thesis discusses the evolution of DataPartner’s application "Inventera". Inventera is designed to do inventory of stock on handheld computers and integartes with SPCS Administration. Inventera is enhanced with a wireless connection and the SPCS API is wrapped with Web Services. The theoretical part of this thesis examines diffrent possibilities to increase reusability by using web service technology when developing software. A case study of the SPCS API is used in order to study differences between using no Web Services at all, static web services or dynamic web services.

Basés sur les protocoles XML, SOAP et WSDL, les Services Web (SW) sont la technologie de base pour le développement d'Architectures Orientées Services (AOS). Ces architectures permettent de mettre en place des applications faiblement couplées avec un fort degré de configuration dynamique. Elles se basent sur la notion de relation de "services" formalisée par un contrat qui unit le client et le prestataire de services. Ce contrat est le point charnière de ce type d'applications. D'un point de vue purement marketing, les Services Web peuvent être développés pour satisfaire les besoins des clients, être facile à maintenir et aussi fournir un haut niveau de qualité de service. Les prestataires de Services Web doivent s'assurer de la fiabilité et de la disponibilité de leur infrastructure individuelle de Services Web. Cependant, les prestataires ne peuvent pas tenir compte de tous les besoins possibles des clients et des contraintes liées au développement de l'application donnée. Cela signifie que des mécanismes additionnels doivent être développés et ciblés pour un contexte d'utilisation donné. C'est exactement le type de problèmes que j'ai examiné dans mes travaux. Les développeurs d'application regardent les Services Web comme des COTS (Component Off-The Shell) et ignorent donc leurs implémentations et leurs comportements en présence de fautes. De ce point de vue, les clients ont besoin de développer des mécanismes de tolérances aux fautes spécifiques bien adaptés à leurs applications. Dans ce but, mes travaux de thèse m'ont conduit à proposer une plate-forme pour aider les clients à réaliser des connecteurs spécifiques de tolérance aux fautes (SFTC - Specifique Fault Tolerance Connectors) qui implémentent des filtres et autres techniques de détection d'erreurs (c.à.d des assertions exécutables) ainsi que des mécanismes de recouvrement qui sont déclenchés quand les Services Web ne satisfont plus les caractéristiques de sûreté demandées. De plus, le même Services Web peut être employé dans plusieurs applications orientées services avec différentes contraintes et peut donc tirer profit de plusieurs connecteurs (SFTCs). Le problème est similaire à l'utilisation des composants COTS dans les systèmes critiques de sûreté, et des travaux précédents ont déjà prouvé que des mécanismes tels que les wrappers étaient une solution possible. La différence dans le contexte des Architectures Orientées Services est que des wrappers prédéfinis ne peuvent pas être spécifiés pour satisfaire tous les besoins possibles. L'approche doit être plus adaptative pour permettre à des mécanismes de sûreté : 1) d'être définis au cas par cas pour une utilisation donnée du Service Web et 2) d'avoir une forte dynamique afin d'être modifiés selon les besoins. Ainsi, mes travaux de recherches ont permis de fournir aux développeurs d'Architectures Orientées Services: 1) un langage nommé DeWeL pour décrire les caractéristiques de sûreté de fonctionnement du connecteur et 2) l'infrastructure IWSD pour dynamiquement contrôler et exécuter les connecteurs dans des applications critiques. L'objectif final est de fournir aux développeurs d' Architectures Orientées Services une infrastructure et des outils capables de les aider à déployer des applications orientées services tolérants les fautes.