International Journal of Cooperative Information Systems

Effective execution of collaborative tasks during enterprise architecture creation helps to increase stakeholders' involvement and awareness in the architecture effort. However, enterprise architecture approaches lack detailed support for collaborative tasks. In an effort to address this, an exploratory survey was conducted among enterprise architects to investigate issues associated with executing collaborative tasks during enterprise architecture creation. Accordingly, this paper discusses mainly three aspects. First, it discusses how issues that were reported in the survey can be addressed by adopting the design science research methodology to guide the development of a process or method that supports the execution of collaborative tasks in architecture creation. The developed process is principally rooted in collaboration engineering and soft systems methodology (SSM). Second, the paper discusses how the developed method can be used to supplement enterprise architecture approaches that are used in practice (e.g. TOGAF) with support for executing collaborative tasks. Third, the paper discusses key findings from evaluating the developed process in two real organizations.

Business process execution language (BPEL) does not provide a native support for defining data and metrics, required to perform business activity monitoring (BAM). Existing industry solutions are vendor-specific while platform-independent scientific approaches separate tightly coupled monitoring definitions from the core BPEL processes into external descriptors, thus increasing the complexity of the development, packaging and deployment processes. Furthermore, existing monitoring solutions reuse platform-specific audit trail events. This requires monitor model developers to be familiar with the details of the process implementation and the custom BPEL engine meta-model. To overcome these issues, this paper presents bpelx4bam — a new approach to defining monitoring data and metrics within BPEL processes, based on BPEL extensions. The bpelx4bam promotes these definitions into the first class citizens of the BPEL specification in order to unify and fully integrate BAM into the BPM lifecycle. It enables a cross-platform migration of BAM-enabled business processes, removes the need for separate models and specifications, eases development, packaging and deployment processes, aligns the separation of concerns with actual process roles and introduces BAM-specific and optimized events. Therefore, it presents a solid ground for a future specification or a standard in this area.

Business process (BP) models are usually defined manually by business analysts through imperative languages considering activity properties, constraints imposed on the relations between the activities as well as different performance objectives. Furthermore, allocating resources is an additional challenge since scheduling may significantly impact BP performance. Therefore, the manual specification of BP models can be very complex and time-consuming, potentially leading to non-optimized models or even errors. To overcome these problems, this work proposes the automatic generation of imperative optimized BP models from declarative specifications. The static part of these declarative specifications (i.e. control-flow and resource constraints) is expected to be useful on a long-term basis. This static part is complemented with information that is less stable and which is potentially unknown until starting the BP execution, i.e. estimates related to (1) number of process instances which are being executed within a particular timeframe, (2) activity durations, and (3) resource availabilities. Unlike conventional proposals, an imperative BP model optimizing a set of instances is created and deployed on a short-term basis. To provide for run-time flexibility the proposed approach additionally allows decisions to be deferred to run-time by using complex late-planning activities, and the imperative BP model to be dynamically adapted during run-time using replanning. To validate the proposed approach, different performance measures for a set of test models of varying complexity are analyzed. The results indicate that, despite the NP-hard complexity of the problems, a satisfactory number of suitable solutions can be produced.

Some works on the researchers cooperation's literature provide the key lines for building research networks and propose new protocols and standards for business to business (B2B) data exchange, but none of them explains how researchers should contact and the procedure to select the most appropriate partner of a research enterprise, institute or university. In this paper, we propose a B2B architecture and protocol between research entities, that uses ebXML protocol. The contacts for cooperation are established based on some defined parameters and an information retrieval system. We explain the information retrieval system, the researcher selection procedure, the XML-based protocol and the workflow of our proposal. We also show the information that has to be exchanged to contact other researchers. Several simulations demonstrate that our proposal is a feasible architecture and may be used to promote the research cooperation. The main purpose of this paper is to propose an efficient procedure for searching project partners.

Defining complex system dynamics (SD) models in complex organizational settings is hard. This is so because the numbers of variables to consider are many and the question of causation is complicated to untangle. Second, SD models are ambiguous and hard to conceptualize. In this paper, we explore the use of a domain modeling method object-role modeling (ORM) in the process of developing SD models. We do so, because domain modeling methods help to identify relationships among entities within the scope of the problem domain and provide a structural view of the domain. The addition of a domain modeling method to the process of developing SD models is to improve SD model conceptualization, enable transformation and reuse of information plus underpin SD with a domain modeling method that allows creation of database. To realize this, we come up with a procedure in our overall research which we refer to as grounded system dynamics (GSD) a combination of ORM and SD. To reason about the combination of SD with a domain modeling method (ORM), we identify and evaluate relationships between their constructs. Basing on the identified relations, ORM to stock and flow diagram (SFD) steps are defined and applied to a real-life case study national medical stores (NMS) situated in Uganda. On completion, we draw conclusions.