Keywords:
Astract: In the development process of a B2B system, it is crucial that the business experts are able to express and evaluate agreements and commitments between the partners, and that the software engineers get all necessary information to bind the private process interfaces to the public ones. UN/CEFACT's modeling methodology (UMM) is a Unified Modeling Language (UML) profile for developing B2B processes. The formalisms introduced by UMM's stereotypes facilitate the communication with the software engineers. However, business experts-who usually have a very limited understanding of UML-prefer expressing their thoughts and evaluating the results by plain text descriptions. In this paper,we describe an approach that presents an equivalent of theUMMstereotypes and tagged values in text-based templates called worksheets. This strong alignment allows an integration into a UMM modeling tool and ensures consistency. We show how a specially designed XML-based worksheet definition language allows customization to special needs of certain business domains. Furthermore, we demonstrate how information kept in worksheets may be used for the semi-automatic generation of pattern-based UMM artifacts which are later transformed to web service definition language and business process execution language code.

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.