all- Integrated fixture design and analysis system based on service-oriented architecture [manufacturing]

Author(s): Fan Liqing; Kumar, A.S.; Jagdish, B.N.; Anbuselvan, S.; Bok Shung-Hwee

Source: 2008 IEEE International Conference on Automation Science and Engineering (CASE 2008) Pages: 656-61  Published: 2008

Conference Information: 2008 IEEE International Conference on Automation Science and Engineering (CASE 2008) Arlington, VA, USA, 23-26 August 2008

Abstract: Distributed collaborative design and manufacture enables manufacturing organizations in maintaining competitiveness in the fiercely competitive global industry. A collaborative design system should be able to transfer information with the various other systems in order to realize a seamless product design and manufacturing environment. This paper addresses the development of an integrated fixture design and analysis system. Web services and service-oriented architecture (SOA) are employed in this system in order to facilitate the advantages of interoperability, platform -independence and language-neutrality. The use of XML as a file format provides a means for the transfer of information and knowledge between design and analysis.

 

 

 

A model for semantic service matching with leftover and missing information

 

Author(s): Sanchez, C.; Sheremetov, L.

Source: 2008 8th International Conference on Hybrid Intelligent Systems (HIS) Pages: 198-203  Published: 2008

Conference Information: 2008 8th International Conference on Hybrid Intelligent Systems (HIS) Barcelona, Spain, 10-12 September 2008

Abstract: One of the challenges of SOA is to deal with service matching which is uncertain and ambiguous. A service requester must be prepared to cope with situations where no required services are found or, on the other hand, multiple matching services are found. The paper proposes a formal model of service matching with incomplete information. The model is defined using set theory and description logics. Fuzzy logic is used to calculate the degrees of semantic matching of services and their ranking. This matching is defined by its type (exact, leftover and missing information) and service functional properties specified by OWL-S. The model is illustrated by example from a case study.     Service-oriented architectures and software product lines: putting both together 更多选项 Author(s): Krut, R.; Cohen, S. Source: 2008 12th International Software Product Line Conference (SPLC) Pages: 383  Published: 2008   Conference Information: 2008 12th International Software Product Line Conference (SPLC) Limerick, Ireland, 8-12 September 2008 Abstract: Service-oriented architecture (SOA) and software product line (SPL) approaches to software development share a common goal. They both encourage an organization to reuse existing assets and capabilities, rather than repeatedly redevelop them for new systems. Their distinct goals may be stated as: 1) SOA: enable assembly, orchestration, and maintenance of enterprise solutions to quickly react to changing business requirements. 2) SPL: systematically capture and exploit commonality among a set of related systems, while managing variations for specific customers or market segments.     Toward Web service dependency discovery for SOA management 更多选项 Author(s): Basu, S.; Casati, F.; Daniel, F. Source: 2008 IEEE International Conference on Services Computing (SCC) Pages: (vol.2) 422-9  Published: 2008   Conference Information: 2008 IEEE International Conference on Services Computing (SCC) Honolulu, HI, USA, 7-11 July 2008 Abstract: The service-oriented architecture (SOA) has become today's reference architecture for modern distributed systems. As SOA concepts and technologies become more and more widespread and the number of services in operation within enterprises increases, the problem of managing these services becomes manifest. One of the most pressing needs we hear from customers is the ability to "discover", within a maze of services each offering functionality to (and in turn using functionality offered by) other services, which are the actual dependencies between such services. Understanding dependencies is essential to performing two functions: impact analysis (understanding which other services are affected when a service becomes unavailable) and service-level root-cause analysis (which is the opposite problem: under-standing the causes of a service failure by looking at the other services it relies on). Discovering dependencies is essential as the hope that the enterprise maintains documentation that describe these dependencies (on top of a complex maze and evolving implementations) is vane. Hence, we have to look for dependencies by observing and analyzing the interactions among services. In this paper we identify the importance of the problem of discovering dynamic dependencies among Web services and we propose a solution for the automatic identification of traces of dependent messages, based on the correlation of messages exchanged among services. We also discuss our lessons learned and results from applying the techniques to data related to HP processes and services.