Keywords: Web Scraper, Crawler, Evaluation
Astract: The WWW grows to one of the most important communication and informa- tion medium. Companies can use the Internet for various tasks. One possible application area is the information acquisition. As the Internet provides such a huge amount of information it is necessary to distinguish between relevant and irrelevant data. Web scrapers can be used to gather defined content from the Internet. A lot of scrapers and crawlers are available. Hence we decided to accomplish a case study with a company. We analyze available programs which are applicable in this domain.
The company is the leading provider of online gaming entertainment. They offer sports betting, poker, casino games, soft games and skill games.
For the sports betting platform they use data about events (fixtures/results) which are partly supplied by extern feed providers. Accordingly, there is a dependency on providers. Another problem is that smaller sports and minor leagues are not covered by the providers. This approach requires cross checks which are manual checks with websites if provider data differs and the definition of a primary source (source which is used in case of different data from providers) have to be done by data input user. Data about fixtures and results should be delivered by a company owned application.
This application should be a domain-specific web crawler. It gathers information from well defined sources. This means bwin will not depend on other providers and they can cover more leagues. The coverage of the data feed integration tool will increase. Furthermore, it eliminates the cross checks between different sources. The first aim of this master thesis is to compose a functional specification for the usage of robots to gather event data via Internet and in- tegrate the gathered information into the existing systems. Eight selected web scrapers will be evaluated and checked based on a benchmark catalogue which is created according to the functional specification. The catalogue and the selection are conceived to be reused for further projects of the company. The evaluation should result in a recommendation which web scraper fits best the requirements of the given domain.

Keywords:
Astract: This chapter concentrates on the modeling and analysis of enterprises that collaborate in a service oriented world. According to the idea of model-driven development, modeling of service-oriented enterprises collaborating in a networked configuration must address three different layers. The first layer is concerned with business models that describe the exchange of economic values among the business partners. An appropriate methodology on this level of abstraction is e3-value [1, 2]. The second layer addresses the inter-organizational business processes among business partners. The third layer addresses the businesses processes executed at each partner´s side, i.e., what each partner implements locally to contribute to the business collaboration.

Keywords:
Astract: Service-oriented architectures (SOA) aim at the alignment of business and IT by having a clear business process-centric focus. In order to reach that goal, real-world business processes are captured by business process models. These models serve as the basis for the declarative configuration of a SOA using appropriate deployment artifacts - i.e., XML-based process languages. Consequently, requirements engineering for SOAs must focus on business processes and on their integration into systems using interoperable services, which is not the case for most conventional requirements engineering approaches. In this paper we present a requirements engineering approach specifically designed for the engineering of SOAs. Requirements are captured using a unified process, based on phases and iterations eventually leading to a formalized and unambiguous requirements specification. The final requirements specification can be used in succeeding development phases - i.e. for the model-driven generation of deployment artifacts for SOAs. The presented solution is called [vem:xi:] and is successfully used in the IT department of a Mobile Network Operator (MNO) in Austria. In the highly volatile world of mobile communication the presented approach enables faster application development and faster integration of solutions, thus leading to a competitive advantage over other market participants.

Keywords:
Astract: In the field of business document standardization a multitude of different standardization efforts exist. Unfortunately, most of the developed standards are designed for a specific application domain or industry and do not consider cross-standard interoperability. This results in several incompatible standard definitions. Without the provision of a common semantical basis for business document definitions, cross-domain interoperability cannot be achieved. In this paper we provide a methodology for building a global reference ontology based on the Core Components Technical Specification (CCTS) and Web Ontology Language (OWL). Using our approach a common semantic business document basis is developed. New document definitions may be derived from this basis and existing document definitions may be aligned to it. Using our 'derivation-by-restriction' mechanism, instances derived from a common semantical basis are interoperable to each other. Thus, mapping mechanisms between different standard definitions may be implemented in an easier and semantically correct manner.

Keywords:
Astract: Business documents exchanged in a service-oriented context play a crucial role in the definition of service interfaces. Only if both partners have a common agreement on the data exchanged, automated business interactions are possible. The United Nations Center for Trade Facilitation and Electronic Business (UN/CEFACT) provides a reliable and interoperable solution for conceptual business document definitions with UN/CEFACT's Core Components Technical Specification. However, document definitions aren't available in a centralized manner to all interested business partners. In order to allow for an easy search and retrieval of core component business document definitions, a registry is needed. Business partners may retrieve service interface definitions from the registry and adapt their software accordingly in order to engage in automated business interactions. We specify a registry meta model on top of ebRIM, registering core component artifacts and defining their inter-dependencies.