Embedding Requirements within the Model Driven Architecture

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

Method for Business Process Management System Selection

In recent years business process management (BPM) and specifically information systems that support the analysis, design and execution of processes (also called business process management systems (BPMS)) are getting more attention. This has lead to an increase in research on BPM and BPMS. However the research on BPMS is mostly focused on the architecture of the system and how to implement such systems. How to select a BPM system that fits the strategy and goals of a specific organization is largely ignored. In this paper we present a BPMS selection method, which is based on research into the criteria that are important for organizations, which are going to implement a BPMS

BPMS implementations in SMEs: Exploring the creation of a situational method

Small and Medium Enterprises (SME) comprise 99% of the European-economy, though, most research and implementation methods concerning Business Process Management Systems (BPMS) focus on large enterprises. We create a BPMS implementation method that is suitable for SMEs. Based on three existing BPMS implementation methods and by incorporating differentiators of SMEs and large enterprises a BPMS implementation method is constructed. The constructed method is validated through a series of interviews with BPMS implementation experts. Experts agree with the constructed method though discussion arise on a more detailed level of activities in the method

A Situational Implementation Method for Business Process Management Systems

For the integrated implementation of Business Process Management and supporting information systems many methods are available. Most of these methods, however, apply a one-size fits all approach and do not take into account the specific situation of the organization in which an information system is to be implemented. These situational factors, however, strongly determine the success of any implementation project. In this paper a method is provided that establishes situational factors of and their influence on implementation methods. The provided method enables a more successful implementation project, because the project team can create a more suitable implementation method for business process management system implementation projects

A Context Dependent Implementation Method for Business Process Management Systems

For the implementation of Business Process Management and supporting information systems there are many methodologies available. However, most of these methods consist of an one-size fits all approach and do not take into account the specific situation of the organization in which an information system is to be implemented. These situational factors, however, strongly determine the success of any implementation project. In this paper, a method is provided that establishes situational factors of and their influence on implementation methods. The provided method enables a more successful implementation project, because the project team can create a more suitable implementation method for business process management system implementation projects