Existence dependency-based domain modeling for improving stateless process enactment.

In a process-enabled service oriented architecture, a process engine typically stores the state of the process instances during enactment. As an alternative, stateless process enactment entails that process state is derived from the state of business objects, which are organized in a domain model. The business objects are referred to in pre- and post-conditions of activities, which determine when the activity is enabled and completed, respectively. Despite the fact that the latter approach has multiple benefits compared with the former, the repeated state (re)calculations deteriorate performance and the formulation of clear conditions is not self-evident if typical domain modeling techniques (e.g. UML or ER) are adopted. In this paper we show that by adopting a specific domain modeling technique, which is based on the notion of existence dependency between the business objects, the performance and comprehensibility issues can proficiently be dealt with. We illustrate the technique using a real-world case from the insurance domain and analyze the emerging duality between process modeling and domain modeling.

Ontological Map of Service Oriented Architecture Based on Zachman

Service orientation is an approach in the field of enterprise architecture, business information systems and software application that its main element is the service. Shared services is an organization model of sharing, across an organization. It enables collaboration among the functions/departments. Main motivations for shared services are sharing, promote efficiency, reduce cost, and support scalability. Despite of the widespread use of these two approaches in information technology, there is no tool to optimize the management of them. The aim of this study is Ontological map of service oriented architecture based on zachman framework to adapt it in the reference enterprise architecture framework through implementation ontology views on system architect software and as well as equivalent ontology component with UML diagrams. After the implementation of the suggested model, the results showed that ontology is a formal description and explicit display of objects, concepts and other entities in the relationship between them. In other words, there is a model that describe all that is in fact in to understandable language for the system. Thus the proposed establishes have association between all aspects of zachman framework, also to create a clear description of business concepts in the management of shared services and is effective to provide a unified platform for enterprise modeling

Actor perception in business use case modeling

Mainstream literature recognizes the validity and effectiveness of use cases as a technique for gathering and capturing system requirements. Use cases represent the driver of various modern development methods, mainly of object-oriented extraction, such as the Unified Process. Although the adoption of use cases proliferated in the context of software systems development, they are not as extensively employed in business modeling . The concept of business use case is not a novelty, but only recently did it begin to re-circulate in the literature and in case tools. This paper examines the issues involved in adopting business use cases for capturing the functionality of an organization and proposes guidelines for their identification, packaging, and mapping to system use cases. The proposed guidelines are based on the principle of actor perception described in the paper. The application of this principle is exemplified with a worked example aimed at demonstrating the utility of the proposed guidelines and at clarifying the application of the principle of actor perception. The worked example is based on a series of workshops run at a major UK financial institution