We consider services as units in interorganizational business processes. Following trends in the business process management community, we switch from an activity-centric description of processes to artifact-centric descriptions. In the interorganizational setting, unique problems arise. For instance, an artifact hub that is crucial for present-day enactment of artifact-centric processes, can h...

We describe the prototype of an interactive, web-based, museum artifact search and information service. Mo Músaem F́ıorúil clusters and indexes images of museum artifacts taken by visitors to the museum where the images are captured using a passive capture device such as Microsoft’s SenseCam [1]. The system also matches clustered artifacts to images of the same artifact from the museums official...

Several authors have claimed the need of the IS community to theorize the IT-artifact. Additionally, phenomena of ‘change’ in all its facets assume a prominent role in information systems research. This paper is targeting at the intersection of research on change and the IT-artifact. The lack of longitudinal studies in the IS-literature has obscured the challenges of theorizing the IT-artifact ...

The existing method of task mapping between process models is mostly based on the similarity of labels to get the similarity between tasks, which is affected by a single factor and easy to cause errors. This paper proposes a task mapping method for Artifact-Centric business process analyzes the data operation in business process execution. At first we add the description of data operation to EZ...

The goal of this work is to improve the efficiency and the reliability of the automatic artifact rejection, in particular from the Electroencephalographic (EEG) recordings. Artifact rejection is a key topic in signal processing. The artifacts are unwelcome signals that may occur during the signal acquisition and that may alter the analysis of the signals themselves. A technique for the automati...

The development of IT-enabled product service systems (PSS) – a combination of physical technological elements (products) and service elements – poses various challenges because of their complexity and the involvement of multiple domains. Classical requirements engineering (RE) addresses these problems only insufficiently. This paper proposes an artifact model for the requirements to PSS, which...

Artifact-centric services are stateful service descriptions centered around “business artifacts”, which contain both a data schema holding all the data of interest for the service, and a lifecycle schema, which specifies the process that the service enacts. In this paper, the data schemas are full-fledged relational databases, and the lifecycle schemas are specified as sets of condition-action ...

Classical notations for service collaborations focus either on the control flow of participating services (interacting models) or the order in which messages are exchanged (interaction models). None of these approaches emphasizes the evolution of data involved in the collaboration. In contrast, artifact-centric models pursue the converse strategy and begin with a specification of data objects. ...

Today, software developers utilize different general-purpose (GPL) and domain-specific languages (DSL) to implement multi-language software applications (MLSA). MLSAs, thus, contain artifacts of different GPLs and DSLs, e.g., sourcecode files and configurations. In a recent study we found that refactoring an artifact can break artifact interaction and that interaction cannot be re-established b...