1,240 research outputs found

    Embedding Requirements within the Model Driven Architecture

    Get PDF
    The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

    A Process Modelling Framework Based on Point Interval Temporal Logic with an Application to Modelling Patient Flows

    Get PDF
    This thesis considers an application of a temporal theory to describe and model the patient journey in the hospital accident and emergency (A&E) department. The aim is to introduce a generic but dynamic method applied to any setting, including healthcare. Constructing a consistent process model can be instrumental in streamlining healthcare issues. Current process modelling techniques used in healthcare such as flowcharts, unified modelling language activity diagram (UML AD), and business process modelling notation (BPMN) are intuitive and imprecise. They cannot fully capture the complexities of the types of activities and the full extent of temporal constraints to an extent where one could reason about the flows. Formal approaches such as Petri have also been reviewed to investigate their applicability to the healthcare domain to model processes. Additionally, to schedule patient flows, current modelling standards do not offer any formal mechanism, so healthcare relies on critical path method (CPM) and program evaluation review technique (PERT), that also have limitations, i.e. finish-start barrier. It is imperative to specify the temporal constraints between the start and/or end of a process, e.g., the beginning of a process A precedes the start (or end) of a process B. However, these approaches failed to provide us with a mechanism for handling these temporal situations. If provided, a formal representation can assist in effective knowledge representation and quality enhancement concerning a process. Also, it would help in uncovering complexities of a system and assist in modelling it in a consistent way which is not possible with the existing modelling techniques. The above issues are addressed in this thesis by proposing a framework that would provide a knowledge base to model patient flows for accurate representation based on point interval temporal logic (PITL) that treats point and interval as primitives. These objects would constitute the knowledge base for the formal description of a system. With the aid of the inference mechanism of the temporal theory presented here, exhaustive temporal constraints derived from the proposed axiomatic system’ components serves as a knowledge base. The proposed methodological framework would adopt a model-theoretic approach in which a theory is developed and considered as a model while the corresponding instance is considered as its application. Using this approach would assist in identifying core components of the system and their precise operation representing a real-life domain deemed suitable to the process modelling issues specified in this thesis. Thus, I have evaluated the modelling standards for their most-used terminologies and constructs to identify their key components. It will also assist in the generalisation of the critical terms (of process modelling standards) based on their ontology. A set of generalised terms proposed would serve as an enumeration of the theory and subsume the core modelling elements of the process modelling standards. The catalogue presents a knowledge base for the business and healthcare domains, and its components are formally defined (semantics). Furthermore, a resolution theorem-proof is used to show the structural features of the theory (model) to establish it is sound and complete. After establishing that the theory is sound and complete, the next step is to provide the instantiation of the theory. This is achieved by mapping the core components of the theory to their corresponding instances. Additionally, a formal graphical tool termed as point graph (PG) is used to visualise the cases of the proposed axiomatic system. PG facilitates in modelling, and scheduling patient flows and enables analysing existing models for possible inaccuracies and inconsistencies supported by a reasoning mechanism based on PITL. Following that, a transformation is developed to map the core modelling components of the standards into the extended PG (PG*) based on the semantics presented by the axiomatic system. A real-life case (from the King’s College hospital accident and emergency (A&E) department’s trauma patient pathway) is considered to validate the framework. It is divided into three patient flows to depict the journey of a patient with significant trauma, arriving at A&E, undergoing a procedure and subsequently discharged. Their staff relied upon the UML-AD and BPMN to model the patient flows. An evaluation of their representation is presented to show the shortfalls of the modelling standards to model patient flows. The last step is to model these patient flows using the developed approach, which is supported by enhanced reasoning and scheduling

    Process-Based Design and Integration of Wireless Sensor Network Applications

    Get PDF
    Abstract Wireless Sensor and Actuator Networks (WSNs) are distributed sensor and actuator networks that monitor and control real-world phenomena, enabling the integration of the physical with the virtual world. They are used in domains like building automation, control systems, remote healthcare, etc., which are all highly process-driven. Today, tools and insights of Business Process Modeling (BPM) are not used to model WSN logic, as BPM focuses mostly on the coordination of people and IT systems and neglects the integration of embedded IT. WSN development still requires significant special-purpose, low-level, and manual coding of process logic. By exploiting similarities between WSN applications and business processes, this work aims to create a holistic system enabling the modeling and execution of executable processes that integrate, coordinate, and control WSNs. Concretely, we present a WSNspecific extension for Business Process Modeling Notation (BPMN) and a compiler that transforms the extended BPMN models into WSN-specific code to distribute process execution over both a WSN and a standard business process engine. The developed tool-chain allows modeling of an independent control loop for the WSN.

    Identifying and addressing adaptability and information system requirements for tactical management

    Get PDF

    Quality measures for ETL processes: from goals to implementation

    Get PDF
    Extraction transformation loading (ETL) processes play an increasingly important role for the support of modern business operations. These business processes are centred around artifacts with high variability and diverse lifecycles, which correspond to key business entities. The apparent complexity of these activities has been examined through the prism of business process management, mainly focusing on functional requirements and performance optimization. However, the quality dimension has not yet been thoroughly investigated, and there is a need for a more human-centric approach to bring them closer to business-users requirements. In this paper, we take a first step towards this direction by defining a sound model for ETL process quality characteristics and quantitative measures for each characteristic, based on existing literature. Our model shows dependencies among quality characteristics and can provide the basis for subsequent analysis using goal modeling techniques. We showcase the use of goal modeling for ETL process design through a use case, where we employ the use of a goal model that includes quantitative components (i.e., indicators) for evaluation and analysis of alternative design decisions.Peer ReviewedPostprint (author's final draft

    Business process modelling and visualisation to support e-government decision making: Business/IS alignment

    Get PDF
    © 2017 Springer-Verlag. The final publication is available at Springer via https://doi.org/10.1007/978-3-319-57487-5_4.Alignment between business and information systems plays a vital role in the formation of dependent relationships between different departments in a government organization and the process of alignment can be improved by developing an information system (IS) according to the stakeholders’ expectations. However, establishing strong alignment in the context of the eGovernment environment can be difficult. It is widely accepted that business processes in the government environment plays a pivotal role in capturing the details of IS requirements. This paper presents a method of business process modelling through UML which can help to visualise and capture the IS requirements for the system development. A series of UML models have been developed and discussed. A case study on patient visits to a healthcare clinic in the context of eGovernment has been used to validate the models

    Toward Semantics-aware Representation of Digital Business Processes

    Get PDF
    An extended enterprise (EE) can be described by a set of models each representing a specific aspect of the EE. Aspects can for example be the process flow or the value description. However, different models are done by different people, which may use different terminology, which prevents relating the models. Therefore, we propose a framework consisting of process flow and value aspects and in addition a static domain model with structural and relational components. Further, we outline the usage of the static domain model to enable relating the different aspects

    Adaptive Process Management in Cyber-Physical Domains

    Get PDF
    The increasing application of process-oriented approaches in new challenging cyber-physical domains beyond business computing (e.g., personalized healthcare, emergency management, factories of the future, home automation, etc.) has led to reconsider the level of flexibility and support required to manage complex processes in such domains. A cyber-physical domain is characterized by the presence of a cyber-physical system coordinating heterogeneous ICT components (PCs, smartphones, sensors, actuators) and involving real world entities (humans, machines, agents, robots, etc.) that perform complex tasks in the “physical” real world to achieve a common goal. The physical world, however, is not entirely predictable, and processes enacted in cyber-physical domains must be robust to unexpected conditions and adaptable to unanticipated exceptions. This demands a more flexible approach in process design and enactment, recognizing that in real-world environments it is not adequate to assume that all possible recovery activities can be predefined for dealing with the exceptions that can ensue. In this chapter, we tackle the above issue and we propose a general approach, a concrete framework and a process management system implementation, called SmartPM, for automatically adapting processes enacted in cyber-physical domains in case of unanticipated exceptions and exogenous events. The adaptation mechanism provided by SmartPM is based on declarative task specifications, execution monitoring for detecting failures and context changes at run-time, and automated planning techniques to self-repair the running process, without requiring to predefine any specific adaptation policy or exception handler at design-time

    Aligning business processes and IT of multiple collaborating organisations

    Get PDF
    When multiple organisations want to collaborate with one another they have to integrate their business processes. This requires aligning the collaborative business processes and the underlying IT (Information Technology). Realizing the required alignment is, however, not trivial and is the subject of this thesis. We approached the issue of alignment in three steps. First, we explored business-IT alignment problems in detail in a real-life business case. This is done in order to clarify what alignment of business processes and IT systems across a collaboration network entails. Second, we provided a business-IT alignment framework called BITA* (pronounce bita-star). The framework provides modelling abstractions for alignment. Third, we applied the framework in two real-life case studies, including the real-life business case used in step one. By applying the framework in practice we showed that the framework can, in fact, help to address the business-IT alignment problems that we identified in the first step. The work presented in this thesis is conducted over a number of years in the context of four large EU sponsored research projects. The projects focused on alignment problems in two very distinct application areas. Two projects were about realizing transparency systems for meat supply chains and constitute the first case study. The other two projects were about realizing multidisciplinary modelling collaboration systems and constitute the second case study. Although the projects were conducted sequentially the research questions were addressed iteratively over the years. The research methodology that shows how the framework is designed and how the case studies are applied is discussed in detail in chapter 2. In chapter 3 we present BITA*, a Business-IT Alignment framework for multiple collaborating organisations. The main challenges in designing BITA* have been what models to consider for alignment and how to compare them in order to make explicit statements about alignment. We addressed this problem by introducing allocation and alignment modelling constructs to help the alignment process, and the concept of business collaboration model to represent the models that have to be aligned. We identified three groups of stakeholders for whom we designed explicit design viewpoints and associated allocation and alignment models. The Business Process to Business Process (BP2BP) alignment viewpoint is designed for business analysts who have to align diverse business collaboration process models. The IT to IT (IT2IT) alignment viewpoint is designed for software architects to align the distribution of data and IT systems across a collaboration network. The Business Process to IT (BP2IT) alignment viewpoint is designed for an interdisciplinary team of business analysts and software architects who have to align the different ways of supporting business collaboration processes with distributed IT system. An essential element of this thesis has been elaborating how business-IT alignment problems occur in the context of multi-organisational collaboration. The case studies were used to demonstrate business-IT alignment concerns. Particularly, the details of the first case study presented in chapters 4 and 5 were used in chapter 3 to help derive the alignment framework. The case study presented an ideal problem scenario since realizing transparency across supply chains is intrinsically a collaborative effort. The second case study was used to enhance the validity of our approach. The results of the second case study are presented in chapter 6. The alignment framework was designed during the iterative process we followed when realizing a generic transparency system for meat supply chains. To realize the required generic transparency system we needed a reference architecture. To derive the reference architecture we adapted an already existing and broadly-accepted generic reference architecture. We have to adapt the generic reference architecture in order to address specific requirements of the meat sector that were not considered in the generic reference architecture. The adaptation process made it clear that we needed models for representing business collaborations. We, therefore, introduced the notion of business collaboration model, which we used both to model reference architectures and to adapt them. Adaptation required aligning the generic reference architecture with the diverse business collaboration models adopted by the organisations that have to collaborate. The alignment framework is thus used for adapting a generic reference architecture in order to create a reference architecture that the collaborating organisations can, and are willing to, adopt. We identified three types of business collaboration models: business collaboration process model, business collaboration IT model, and a model for representing the relationship between these two. A business collaboration process model is a business process model that spans a collaboration network. A business collaboration IT model is a model of the distribution of the IT across the collaboration network. A business collaboration process-IT model is a model of the relationships between the elements of the business collaboration processes and the elements of the distributed IT. Each organisation is considered to adopt its own business collaboration models. For instance, different actors in meat supply chains have different views on how chain-wide transparency should be realized. Which business processes and IT systems each organisation has to deploy and use depends on the business collaboration models each food operator adopts. If two different food operators adopt the same set of business collaboration models, they are aligned; otherwise they are misaligned. Hence, alignment entails comparing the different business collaboration models adopted by the participating organisations. The results of the alignment process are explicit statements about how convergent or divergent the organisations are from the chosen generic reference architecture. The explicit statements of alignment guide how best the generic and the corresponding organisational business collaboration models can be adapted to create a better state of alignment. To further enhance the validity of the overall approach the second case study was conducted. The second case study was a retrospective investigation of two past research projects focusing on aligning environmental modelling processes and IT systems. A retrospective case study was chosen because launching a new business-IT alignment project involving multiple collaborating organisations was not feasible. The projects were undertaken to support the European Water Framework Directive, which mandated, among other things, participatory, multidisciplinary, river-basin wide and model-based studies to manage the water resources of Europe. The directive particularly required a collaborative approach to building environmental decision support systems and to deriving methodologies for applying existing decision support systems. We applied BITA* to aligning environmental modelling processes and IT systems in order to evaluate the suitability of the framework to addressing alignment problems in other application areas. The contributions of the thesis are summarized in chapter 7. The contributions include a number of design artefacts, which can be grouped into four categories: constructs, models, methods, and instantiations. The contribution in the first category includes the conceptualization of allocation and alignment. The contributions in the second category include allocation and alignment models, and reference architectures. Allocation models are representations of business collaboration models in a form that can be compared and are the basis for alignment modelling. The main contribution in the third category is the BITA* systematic approach to alignment modelling. The contributions in the fourth category are the software systems developed with the help of the reference architectures.</p
    corecore