No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
The process map as an instrument to standardize processes: Design and application at a financial service provider
Abstract
The standardization of processes and the identification of shared business services in a service-oriented architecture (SOA) are currently widely discussed. Above all in practice, however, there still is a lack of appropriate instruments to support these tasks. In this paper an approach for a process map is introduced which allows for a systematic presentation—as complete as possible—of the processes in an enterprise (division). After a consistent refinement of the process has taken place by means of aggregation/disaggregation respectively, generalization/specialization relations, it is possible to identify primarily functional similarities of the detailed sub-processes. The application of the process map at a financial service provider (FSP) highlights how these similarities can be taken as a basis to standardize processes and to identify shared services.
... In BPM, a model describing (part of) the business process architecture is commonly, though not uniquely referred to as a process map [5]. The concept of process map as a holistic and abstract representation of an organisation's interrelated business processes, has only recently been investigated [6], while being in use for many years in different shapes and forms. ...
... In other examples of process maps also organizational units or business functions are identified as being involved in process execution, see e.g., [1,2,5]. Physical persons or organizational units (e.g., departments, project teams) having certain functions and responsibilities in the organization are typically included in enterprise architecture models, hence linking them explicitly with processes according to specific roles towards business processes (i.e., as actor or resource) connects or even integrates business process architecture models with(in) enterprise architecture models. ...
... To eventually get outputs delivered to external customers, some decomposition relation between externally triggered processes and internally triggered processes is needed (not shown in Figure 2). We come back to relations between business processes in section 8. Representing customers of process outputs on process maps is not uncommon, see e.g., [5,8], though it depends again on the desired abstraction level at which the business process architecture is described, which is, apart from [9], not explicitly defined in the BPA literature that we reviewed. ...
Process maps provide a high-level overview of an organisation's business processes. While used for many years in different shapes and forms, there is little shared understanding of the concept and its relationship to enterprise architecture. In this report we position the concept of business process map within the domain of enterprise architecture. Based on literature, we provide a conceptualisation of the process map as a business process architecture model that can be integrated with the broader enterprise architecture model. From our conceptualisation we derive requirements for designing a meta-model of a modelling language for process maps. The design of this meta-model is the subject of a research paper, entitled Architecting Business Process Maps, for which this report acts as a complement that details the underlying process map conceptualisation.
... The technological advantages listed above led to an almost unanimous belief that SOA enables never-before-seen advances in enterprise architecture (Woodley and Gagnon 2005). SOA was believed to facilitate the alignment of existing IT infrastructure and systems to achieve end-to-end enterprise connectivity by removing redundancies, generating unified collaboration tools, and streamlining IT processes (Bieberstein et al. 2005), while providing greater flexibility and quicker implementation of future requirements (Heinrich et al. 2009). With SOA, information system ( " IS " ) was thus believed to be more flexible and agile for alignment with a dynamic business environment (Li et al. 2007). ...
... SOA theoretically provides a mechanism for integrating applications that seamlessly support cross-enterprise (business-to-business) and intra-enterprise application integration (Curbera et al. 2003). If services are shared, not only the number of redundant services but also the costs of their operation, administration, and development could be reduced (Heinrich et al. 2009). To summarise the above claims: SOA has been marketed as an ultimate answer to the eternal challenges of IS development; namely, to enable the flexible alignment of business needs and IT capabilities. ...
... In this phase, an organisation " s success with SOA depends on its ability to define its processes and the relationships between them; thus, on the improvement of BPMa (Harmon and Wolf 2007). The identification of services should be preceded by the optimisation of a process because otherwise it will end up in the " electronification " of inefficient processes (Groznik et al. 2008; Heinrich et al. 2009). Namely, an often-cited reason for SOA failure is the non-existence of quality process models that can be used to identify business services (Heinrich et al. 2009). ...
The paper argues that attitudes to SOA follow a typical hype cycle from Technological Trigger, Peak of Inflated Expectations, and a Trough of Disillusionment to the more recent realization that SOA is a concept that may offer certain benefits but has several limitations. The main research question studies how the attitude to SOA changes in various phases of the hype cycle, how the SOA implementation cycle and an increase in business process maturity (BPMa) are interconnected and which factors influence the transition between the hype cycle phases. The paper shows that an organization’s success with implementing SOA depends on its ability to match the SOA implementation with an increase in BPMa. The dual purpose of implementing SOA is shown in the first framework: to assure the coherence of IT assets and to assure business/IT alignment. In the second framework, the interconnection of SOA and BPMa and its role in transiting through the hype cycle phases is outlined. The findings are analyzed using a longitudinal case study of a large Slovenian company.
... Die erwähnten technischen Fortschritte führten zu der nahezu einstimmigen Ansicht, dass SOA Fortschritte in der Unternehmensarchitektur in zuvor unbekanntem Ausmaß ermöglichen könnte (Woodley und Gagnon 2005). SOA sollte die Anpassung der bestehenden IT-Infrastruktur und Systeme ermöglichen, um eine durchgehende Unternehmenskonnektivität zu erreichen, indem Redundanzen behoben, Unified-Collaboration-Tools generiert und IT-Prozesse gestrafft werden (Bieberstein et al. 2005), während sie gleichzeitig eine größere Flexibilität und schnellere Umsetzung künftigen Anforderungen bietet (Heinrich et al. 2009). Mit einer SOA wurden Informationssysteme (IS) für flexibler und wendiger hinsichtlich ihrer Anpassung an eine dynamische Unternehmensumwelt gehalten (Li et al. 2007). ...
... Eine SOA bietet theoretisch einen Mechanismus zur Integration von Anwendungen, die nahtlos eine unternehmensübergreifende (Business-to-Business) und unternehmensinterne Anwendungsintegration unterstützen (Curbera et al. 2003). Bei gemeinsamer Nutzung von Services könnte nicht nur die Anzahl von redundanten Services reduziert werden, sondern auch die Betriebs-, Verwaltungsund Entwicklungskosten (Heinrich et al. 2009). ...
... von der Verbesserung der GPR (Harmon und Wolf 2007). Der Identifizierung der Services sollte eine Prozessoptimierung vorausgegangen sein, da dies ansonsten mit einer "Elektronisierung" ineffizienter Prozesse endet (Groznik et al. 2008;Heinrich et al. 2009). Ein oft genannter Grund für das Scheitern von SOA ist dem folgend das Nicht-vorhandensein von qualitativen Prozessmodellen, die dazu genutzt werden können, betriebliche Services zu identifizieren (Heinrich et al. 2009). ...
Zusammenfassung Der Beitrag beweist, dass die Haltung gegenüber SOA dem typischen Hypezyklus folgt. Er reicht vom technologischen Auslöser
über den Gipfel der überzogenen Erwartungen bis in das Tal der Enttäuschungen und führt zu der neueren Erkenntnis, dass SOA
ein Konzept ist, das zwar Vorteile bringen kann, aber auch mehrere Einschränkungen aufweist. Es wird der Hauptforschungsfrage
nachgegangen, wie sich die Haltung gegenüber SOA in verschiedenen Phasen des Hypezyklus ändert, wie der SOA-Implementierungszyklus
und eine Erhöhung der Geschäftsprozessreife miteinander verbunden sind und welche Faktoren den Übergang zwischen einzelnen
Phasen des Hypezyklus beeinflussen. Die doppelte Zielsetzung der SOA-Implementierung hängt von deren Fähigkeit ab, die SOA-Implementierung
mit der Erhöhung der Geschäftsprozessreife abzustimmen. Diese doppelte Zielsetzung wird im ersten Framework dargestellt: die
Kohärenz der IT-Ressourcen und ein erfolgreiches Business/IT-Alignment zu gewährleisten. Im zweiten Framework wird die Verbindung
von SOA und Geschäftsprozessreife sowie dessen Rolle beim Übergang der Hypezyklus-Phasen dargestellt. Die Feststellungen werden
mithilfe einer Längsschnitt-Fallstudie eines slowenischen Großunternehmens analysiert.
... While some provide a basic overview and others include detailed relationships between multiple sequences, some authors argue the importance of the completeness of the process map and recommend the inclusion of additional elements like actors, resources and data flow relations (Malinova et al., 2015). This view of completeness is echoed by additional authors who argue for the higher degrees of detail (Heinrich et al., 2009). The authors say that the more detailed the map, the easier it is to adjust when new products are introduced or when the process is redesigned (Heinrich et al., 2009). ...
... This view of completeness is echoed by additional authors who argue for the higher degrees of detail (Heinrich et al., 2009). The authors say that the more detailed the map, the easier it is to adjust when new products are introduced or when the process is redesigned (Heinrich et al., 2009). As this research looks to replace a portion of the process map with a different method of transportation, i.e. a rover, the process maps will include a high degree of detail and incorporate both primary and subsidiary paths. ...
Purpose
The purpose of this research is to explore the utility of autonomous transport across two independent airframe maintenance operations at a single location.
Design/methodology/approach
This study leveraged discrete event simulation that encompassed real-world conditions on a United States Air Force flight line. Though the Theory of Constraints (TOC) lens, a high-demand, human-controlled delivery asset is analyzed and the impact of introducing an autonomous rover delivery vehicle is assessed. The authors’ simulations explored varying numbers and networks of rovers as alternative sources of delivery and evaluated these resources’ impact against current flight line operations.
Findings
This research indicates that the addition of five autonomous rovers can significantly reduce daily expediter delivery tasks, which results in additional expertise necessary to manage and execute flight line operations. The authors assert that this relief would translate into enhancements in aircraft mission capable rates, which could increase overall transport capacity and cascade into faster cargo delivery times, systemwide. By extension, the authors suggest overall inventory management could be improved through reduction in transportation shipping time variance, which enhances the Department of Defense’s overall supply chain resilience posture.
Originality/value
When compared against existing practices, this novel research provides insight into actual flight line movement and the potential benefits of an alternative autonomous delivery system. Additionally, the research measures the potential savings in the workforce and vehicle use that exceeds the cost of the rovers and their employment.
... And when doing so, authors usually balance advantages and disadvantages of different functional scopes of IT services qualitatively and deduce on this basis general recommendations for the optimal functional scope of IT services, whereas a quantitative formalisation and trade-off has been missing until now. Furthermore, reuse is most often addressed as an abstract design principle, but often fails to occur in business practice (Heinrich et al., 2009). One explanation for this may be the lack of methods for the evaluation of IT service candidates with regard to their reuse potential. ...
... The BU thus has to estimate how far a certain bundling matches the demand of other BUs. As a BU is hardly able to estimate the demand of other BUs for a specific IT service for several future periods accurately, we instead suggest to estimate for every IT service solely a mean expected FEU over all periods 1, … , and state the following assumption: We suggest the following procedure to estimate this mean expected FEU : starting with the company-wide process map (see Heinrich et al. (2009)), which provides an overview of a company's business processes as a whole and the actions used in it, we analyse which other business processes require the atomic functionalities , … , , . Based on this, we group atomic functionalities with a similar reuse potential into a cluster and extrapolate in this way 1, … , clusters , … , , of atomic functionalities (for example this can be a classification as is " low FEU " , " middle FEU " , and " high FEU " ). ...
Unternehmen müssen im Hinblick auf die Einbindung Web-basierter Dienste in ihre Geschäftsabläufe sehr genau abwägen, welche Nutzungspotentiale bestehen und welche Risiken damit einhergehen. Dies gilt sowohl für Grundsatzentscheidungen hinsichtlich des Geschäftsmodells, der Geschäftsprozesse, der Anwendungssysteme und der unterstützenden Infrastruktur, wie z. B. den Umbau der Unternehmens- und IT-Architektur in Richtung SOA, als auch für darauf aufbauende Einzelmaßnahmen, wie z. B. die Implementierung neuer IT-Services. Dabei stehen Unternehmen einerseits vor der Herausforderung, die erforderlichen Voraussetzungen für eine sinnvolle Nutzung Web-basierter Dienste zu schaffen. In diesem Zusammenhang gilt es sowohl Überlegungen hinsichtlich der notwendigen technischen Basis anzustellen als auch entsprechende Konzepte zu entwickeln, wie die Einbindung z. B. von Online Communitys oder IT-Services in der betrieblichen Praxis konkret vonstattengehen kann. Andererseits ist für eine effiziente Allokation finanzieller Ressourcen eine sorgfältige Abwägung der aus unterschiedlichen Gestaltungsmöglichkeiten für Web-basierte Anwendungen resultierenden Erträge, Aufwendungen und Risiken erforderlich. Vor diesem Hintergrund ist es Ziel der vorliegenden kumulativen Dissertationsschrift, sowohl zur ökonomisch optimalen Gestaltung von Web-basierten Diensten als auch zur Schaffung der notwendigen Voraussetzungen für eine sinnvolle betriebswirtschaftliche Nutzung solcher Anwendungen beizutragen. Dabei erfolgt eine Fokussierung auf zwei zentrale Fragestellungen, nämlich einerseits auf die ökonomisch optimale Gestaltung von IT-Services und andererseits auf die Identifikation von zentralen Akteuren in Web-basierten sozialen Netzwerken als Ausgangsbasis für die Einbindung solcher Communitys in ausgewählte betriebswirtschaftliche Fragestellungen. Diese Fragestellungen werden in drei Einzelaufsätzen behandelt.
... And when doing so, authors usually balance advantages and disadvantages of different functional scopes of IT services qualitatively and deduce on this basis general recommendations for the optimal functional scope of IT services, whereas a quantitative formalisation and trade-off has been missing until now. Furthermore, reuse is most often addressed as an abstract design principle, but often fails to occur in business practice (Heinrich et al. 2009). One explanation for this may be the lack of methods for the evaluation of IT service candidates with regard to their reuse potential. ...
... We suggest the following procedure to estimate this mean expected FEU λ j : starting with the company-wide process map (see Heinrich et al. 2009), which provides an overview of a company's business processes as a whole and the actions used in it, we analyse which other business processes require the atomic functionalities F 1 ,…,F G. Based on this, we group atomic functionalities with a similar reuse potential into a cluster A k and extrapolate in this way K Є {1,…,G} clusters A 1 ,…,A K of atomic functionalities (for example this can be a classification as is " low FEU " , " middle FEU " , and " high FEU " ). Next, we estimate a mean expected FEU μ k for each of these clusters A k , k = 1,..,K. ...
The current financial crisis forces companies to allocate IT budgets more effectively and thus increases the demand for suitable methods to evaluate the financial impact of IT investments. This especially applies to service-orientation, a design paradigm which facilitates the standardisation and flexibilisation of business processes and IT applications, topics that currently are very much in vogue in science and practice. This paper focuses on the realisation of a new functionality by IT services and presents a methodology to determine their financially optimal functional scope on the continuum between realising just one IT service providing the whole functionality and realising many IT services each providing only a small share of functionality. This approach allows for a multi-period financial valuation of an uncertain demand for the new functionality, as well as of an uncertain company-wide reuse of the corresponding IT services. Finally, the methodology is evaluated by an example from a financial services provider.
... To understand business processes and their interactions in the big picture, a process architecture diagram is necessary for development and maintenance. In the literature, BPA are referred to as clusters [14], process maps [15,16], or process landscapes [17][18][19]. Despite the crucial role of blood banks and transfusion in health systems and services, the literature lacks a blueprint that presents the entire blood banking and transfusion processes and their relationships. ...
Background
Blood banks are an important part of healthcare systems. They embrace critical processes that start with donor recruitment and blood collection, followed by blood processing to produce different types of blood components used in transfusions, blood storage, blood distribution, and transfusion. Blood components must be generated at high quality, preserved safely, and transfused in a timely manner. This can be achieved by operating interrelated processes within a complex network. There is no comprehensive blueprint of Blood Banking and Transfusion (BB&T) processes and their relationships; therefore, this study aims to develop and evaluate a BB&T process architecture using the Riva method.
Research design
This research adopts a design science research methodology process (DSRM) that aims to create artifacts for the purpose of serving humanity through six phases: identifying problems, identifying solutions and objectives, designing and developing artifacts, demonstrating and evaluating the artifacts, and communicating the work. The adapted DSRM process is used to build a process architecture in the BB&T unit to improve the quality and strategic planning of BB&T processes. Applying the adapted DSRM process generated four increments before the outcomes were communicated as a highly comprehensive BB&T process architecture (BB&TPA) blueprint for virtual organizations. Finally, the generated BB&TPA is tested and validated at a reference hospital.
Results
A Riva-based process architecture diagram was successfully developed, acting as a reference model for virtual BB&T organizations. It is a novel output in the domain of BB&T and can also be considered as a reference model to evaluate the existing processes in BB&T real-world units. This assists domain experts in performing gap analysis in their BB&T units and paths for developing BB&T management information systems and can be incorporated in the inspection workflow of accreditation organizations.
... In Sect. 5.4 we suggest to investigate whether these prescriptions can be further generalized to other generic Enterprise Architecture artifacts [e.g., reference process architectures (Heinrich et al. 2009)]. Besides researchers, consultants in strategy, management, and Enterprise Architecture can use the prescriptions to guide their search for industry/sector-specific capability maps, which they can reuse in their consultancy practice. ...
Capability-based management is an approach for strategy formulation and implementation that is rooted within the enterprise architecture discipline and founded on managerial theories. The main instrument of capability-based management is the capability map, which provides a structured and hierarchical overview of an organization’s capabilities. At a sufficiently high level of abstraction, organizations within the same industry or societal sector are managed based on capabilities that can be described using a generic capability map. While industry/sector-specific capability maps are used in consultancy practice, knowledge of how to develop such generic capability maps is lacking in the academic literature. Therefore, the paper addresses the question of how a generic capability map for organizations within the same industry/sector can be developed. Professional sport clubs were used as the application field for the design science research. The research was executed in collaboration with three major, premier league Belgian clubs that operate in the highest tier of their respective professional sport competition. After different iterations of joint development and evaluation activities with these clubs, the final design of a generic capability map was successfully obtained. Through reflection and learning from this process, the paper formulates the procedural knowledge that was gained in the study as prescriptions that can be used as general steps of a method for creating other industry/sector-specific capability maps. This outline of a method for developing generic capability maps is an original contribution to the enterprise architecture discipline.
... As shown in Figure 1, a BPA is expressed by a BPA description, which, in turn, is composed of one or more BPA views; each of which, in turn, is composed of one or more BPA models. A key BPA view is the one that is concerned with the high-level structure of the system of business processes known as process map [15][16][17][18], process landscape [2,9,19], process cartography [20,21], or process architecture (model) [10,[22][23][24]. The remainder of this paper refers to it as the BPA model. ...
A business process architecture (BPA) model depicts business processes in an organization and their relations. An artifact for generating BPA models is proposed as the outcome of a design science research project. The proposed artifact consists of a method (i.e., a set of concepts, a proposed notation, and a detailed procedure), which is termed the domain-based BPA (dBPA) method due to using domain models as a starting point. The dBPA method tackles issues of currently available approaches: lack of structured inputs, limited consideration of process relations types, and restricted use of industry-standard modeling languages. The paper formalizes the dBPA method and illustrates its application in the manufacturing industry. Evaluation of the dBPA method revealed that practitioners perceived it as useful to achieve its goal with the benefits of being objective and clear and allowing to create complete and understandable BPA models that enable the integration of processes and the software that automates them.
... Models of business process architecture are referred to as process maps [8] or process landscape models [1]. To analyze the fit for purpose of an organization's business processes, the following requirements must be met: ...
We present a mapping of a previously designed Business Process Architecture (BPA) meta-model onto ArchiMate, i.e., the de facto standard Enterprise Architecture (EA) modelling language. This construct mapping allows developing process maps, i.e., descriptions of (views of) the business process architecture of an organization. We demonstrate the development of these process maps using the Signavio Business Process Management (BPM) modelling platform. The developed process maps are part of the organization’s enterprise architecture model and are linked to BPMN process diagrams that detail the functional, control-flow, data and resource aspects of the business processes included in the process map. Our research contributes to the integration of BPM and EA by researching BPA as a concept common to both disciplines.
... During Research Phase 2 we applied these suggestions for improvement in form of organizational interventions within two additional companies who followed a modified piloting process, educated by the research team based on the experiences from the first research phase (Peffers et al. 2007). We then compared the outcomes of both processes (a similar two-step design science approach has been followed by Heinrich et al. (2009a, b), investigating the piloting and implementation of customer relationship management software). ...
... By placing the process map on the company's intranet site, it will likely facilitate understanding of the company from a process perspective among the company's senior executives, the management and the rest of the staff, consequently providing focus for BPM within the organization [45]. Researchers state that process redundancy could be avoided through process standardization and a process map facilitates process standardization [102]. Another study argues that by clearly identifying the interfaces of the processes, sources of inefficiencies would be avoided [46]. ...
Organizations are leaning towards becoming more processoriented in order to better serve their customers. An approach that enables achieving such process orientation is business process management (BPM). In this context business process modeling is used to graphically represent business processes. As a result organizations are faced with large collections of process models. The process models are typically organized in a process architecture which comprises a number of levels. The most top level is commonly the process map where all processes of one organization and the relations between them are depicted in a very abstract manner. Whereas there are well-defined languages for modelling the details of singular processes (e.g. BPMN, EPC), such a language for supporting the design of process maps is still missing. As a result, we are faced with a vast variety of process map designs from practice, as practitioners typically rely on their own creativity when undertaking this task. This study addresses this gap by using various methods to develop a language for process map design which will support practitioners to design their process maps in a standardized manner.
... In addition, transitioning from a third to fourth level of operating maturity (as defined by Ross et al., [7]) requires the identification of business services that may be shared among different organisational entities. Heinrich et al. [16] believe that the identification of business services requires a consistent representation of the enterprise's processes. ...
To stay competitive, enterprises of today need to rely on a sound foundation for execution that incorporates the infrastructure and digitised processes for automating a company's core capabilities. Once this foundation has been established, management could move their attention away from focusing on lower-value activities to innovative ways to increase profits and growth. The Business-IT Alignment Framework (BIAF) defines business-IT alignment in terms of a paradigm of alignment, three dimensions for alignment, and mechanisms and practices. The BIAF could provide a business-IT alignment perspective on the foundation for execution approach. Using the BIAF perspective, this paper comments on some of the deficiencies related to the foundation for execution approach regarding the systematic identification of opportunities for enterprise-wide process standardisation. The goal is to define a list of requirements that should direct the design of appropriate mechanisms and practices to address the identification of process re-use opportunities for multiple levels of operating maturity.
... During Research Phase 2 we applied these suggestions for improvement in form of organizational interventions within two additional companies who followed a modified piloting process, educated by the research team based on the experiences from the first research phase (Peffers et al. 2007). We then compared the outcomes of both processes (a similar two-step design science approach has been followed by Heinrich et al. (2009a, b), investigating the piloting and implementation of customer relationship management software). ...
Despite the growing popularity of web-supported brokering services, management literature still lacks a comprehensive understanding of the cooperative modes between intermediaries and their customers (seeker companies). The aim of our study is to develop a framework for the interaction between seeker companies and technology brokers. This framework should serve as a guideline for practitioners in order to increase the efficiency of this novel mode of cooperation. An explorative and qualitative multi-case research methodology was applied to extract the longitudinal data analyzed in this study. Based on Open Innovation projects using the Broadcast Search approach and conducted with German seeker companies in cooperation with the web-based intermediary platform NineSigma, we describe seven phases of an ideal-typical broadcast search process. In addition we focus on the challenges that seeker companies face when outsourcing parts of their problem-solving activities to a broad and undefined network of experts via innovation intermediaries.
... The reference process model for MDM groups processes in main processes based on their purpose-oriented and task-oriented relationships. The visual representation of the reference process model follows the principles of process maps, which in general aim at identifying and representing similar processes, sub-processes and functions [36] in a tabular format. ...
The management of master data (MDM) plays an important role for companies in responding to a number of business drivers such as regulatory compliance and efficient reporting. With the understanding of MDM’s impact on the business drivers companies are today in the process of organizing MDM on corporate level. While managing master data is an organizational task that cannot be encountered by simply implementing a software system, business processes are necessary to meet the challenges efficiently. This paper describes the design process of a reference process model for MDM. The model design process spanned several iterations comprising multiple design and evaluation cycles, including the model’s application in three participative case studies. Practitioners may use the reference model as an instrument for the analysis and design of MDM processes. From a scientific perspective, the reference model is a design artifact that represents an abstraction of processes in the field of MDM.
... During Research Phase 2 we applied these suggestions for improvement in form of organizational interventions within two additional companies who followed a modified piloting process, educated by the research team based on the experiences from the first research phase (Pfeffers et al. 2007). We then compared the outcomes of both processes (a similar two-step design science approach has been followed by Heinrich et al. (2009aHeinrich et al. ( , 2009b, investigating the piloting and implementation of customer relationship management software). ...
Crowdsourcing has been demonstrated to be an effective strategy to enhance the efficiency of a firm’s innovation process. In this paper, we focus on tournament-based crowdsourcing (also referred to as “broadcast search”), a method to solve technical problems in form of an open call for solutions to a large network of experts. Based on a longitudinal study of six companies piloting this application of crowdsourcing, we identify barriers and sources of resistance that hinder its implementation in firms. Our paper contributes to the state of research by analyzing crowdsourcing on the level of pilot projects, hence providing a workflow perspective that considers the creation of dedicated processes and operations of crowdsourcing. This project level analysis enables the identification of specific challenges managers face when implementing crowdsourcing within an established R&D organization. Following a design science approach, we derive suggestions for organizational interventions to overcome these barriers. We find that dedicated promoter roles strongly contribute to a successful implementation of crowdsourcing, turning pilot projects into an organizational routine.
... During Research Phase 2 we applied these suggestions for improvement in form of organizational interventions within two additional companies who followed a modified piloting process, educated by the research team based on the experiences from the first research phase (Peffers et al. 2007). We then compared the outcomes of both processes (a similar two-step design science approach has been followed by Heinrich et al. (2009a, b), investigating the piloting and implementation of customer relationship management software). ...
Open Innovation has been demonstrated to be an effective strategy to enhance the efficiency of a firm's innovation process. In this paper, we focus on broadcast search (also called tournament-based crowdsourcing), a method in the later stages of an innovation project directed to solve technical problems in form of an open call. Based on a design science approach and a longitudinal study of six companies engaged in piloting of open innovation, we identify barriers and sources of resistance that hinder its implementation in firms. Our paper contributes to open innovation research by analyzing crowdsourcing on the level of pilot projects, hence providing a workflow perspective that considers the creation of dedicated processes and operations of crowdsourcing. This project level analysis of crowdsourcing enables the identification of specific challenges managers face when implementing crowdsourcing within an established R&D organization. Following a design science approach, we also derive suggestions for organizational interventions to overcome these barriers. We find that dedicated promotor roles strongly contribute to a successful implementation of crowdsourcing, turning pilot projects into an organizational routine.
... Often, they refer to process maps as an important step of the BPM initiative. A study by Heinrich et al. ( 2009) suggests some requirements for developing a process map. They claim that process redundancy could be avoided through process standardization, and a process map facilitates process standardization. ...
... Often, they refer to process maps as an important step of the BPM initiative. A study by Heinrich et al. ( 2009) suggests some requirements for developing a process map. They claim that process redundancy could be avoided through process standardization, and a process map facilitates process standardization. ...
Process maps are intensively used by organizations to provide a holistic view of all processes and the relationships between them. They assist in easier navigation through the processes and enable an understanding of the company’s operations without necessarily going into process depth. Regardless of their apparent significance, hardly any research has been done in conceptualizing process map design. In this paper, we bring awareness to this topic, by assessing the compliance of 15 process maps to the nine principles for cognitively effective design of visual notations introduced by Moody (2009). In addition, we employ the cognitive fit theory to verify if the process maps are designed in accordance to the goals companies planned to achieve through BPM. By this means, we were able to reach conclusions, such that a process map that does not comply with the criteria stated by the principles is difficult to interpret, and thereby yields unwanted, unanticipated or no beneficial effects.
... With the goal of providing an intuitive graphical representation of the functional reference model -the so-called MES function map (see for example Figures 3 and 4) -we followed existing approaches that are used to create and visualize process maps (cf. [13]). ...
Being confronted with IT strategic questions of how to constantly reduce IT operating costs and at the same time live up to ever increasing manufacturing demands, automobile manufacturers are encountering problems to find appropriate IT support for production planning and execution. Moreover, they are facing the challenge to clearly define and demarcate Enterprise Resource Planning (ERP) and Manufacturing Execution Systems (MES) functionality. Despite the existence of a number of standardization efforts addressing MES functionality, automobile manufacturers are still struggling to reach a common understanding for the term MES and a clear functional design. The paper addresses this need by developing a functional reference model for MES in the
automotive industry based on a multiple case study approach. The case studies examine the design and implementation of manufacturing-related functionality in four leading automotive manufacturing companies.
... The reference model for MDQM uses process criteria, grouping functions in function groups and sub-functions in functions, based on their purpose-oriented and task-oriented relationships. The visual representation of the reference model follows the principles of process maps, which in general aim at identifying and representing similar processes, subprocesses and functions (Heinrich et al. 2009) in a tabular form. This concept is also widely used in the practitioners' community, for example in SAP's business maps. ...
The quality of master data has become an issue of increasing prominence in companies. One reason for that is the growing number
of regulatory and legal provisions companies need to comply with. Another reason is the growing importance of information
systems supporting decision-making, requiring master data that is up-to-date, accurate and complete. While improving and maintaining
master data quality is an organizational task that cannot be encountered by simply implementing a suitable software system,
system support is mandatory in order to be able to meet challenges efficiently and make for good results. This paper describes
the design process toward a functional reference model for master data quality management (MDQM). The model design process
spanned several iterations comprising multiple design and evaluation cycles, including the model’s application in a participative
case study at consumer goods manufacturer Beiersdorf. Practitioners may use the reference model as an instrument for the analysis,
design and implementation of a company’s MDQM system landscape. Moreover, the reference model facilitates evaluation of software
systems and supports company-internal and external communication. From a scientific perspective, the reference model is a
design artifact; hence it represents a theory for designing information systems in the area of MDQM.
KeywordsData quality management–Master data management–Design science research–Reference model
Este artículo presenta el mapa de procesos para el diseño del sistema de gestión de información en la facultad de Informática, Universidad de Camagüey ¨Ignacio Agramonte Loynaz¨. Los procesos de formación profesional, ciencia y técnica y extensión universitaria fueron analizados para confeccionar el mapa de proceso, además se revisó toda la documentación y se realizaron entrevistas con directivos, profesores y estudiantes. Los procesos se clasificaron en tres tipos (estratégicos, clave y de apoyo). Esta clasificación finalmente se representa en un diagrama con la secuencia e interacción de los procesos.
Process maps provide a high-level overview of an organization’s business processes. While used for many years in different shapes and forms, there is little shared understanding of the concept and its relationship to business process architecture. In this paper, we position the concept of process map within the domain of architecture description. By ‘architecting’ the concept of business process map, we identify and clarify diverging views of this concept as found in the literature and set requirements for describing process maps. A meta-model for a process mapping language is produced as a result. The proposed meta-model allows investigating the suitability of EA modelling languages as a basis for defining a domain-specific language for process mapping along with the creation of a better understanding of business process architecture in relation to enterprise architecture, which can be beneficial for both BPM and EA professionals.
Purpose
The purpose of this paper is to describe the current state of the research field of business process architecture (BPA) and its design methodologies.
Design/methodology/approach
A systematic literature review (SLR) was conducted using meta- and content-based perspectives.
Findings
From over 6,000 candidate studies, 89 were selected. A fifth of these primary works corresponded to BPA design methodologies. Though the BPA research field remains in an early stage of development, it bears promising growth potential. Regarding BPA design methodologies, the following aspects susceptible for further research were detected: identification and modeling of business process relationships; specification of inputs; standardization of models, notations and tool support; consideration of managerial concerns; integration of knowledge from other areas; and validation of methodological and product quality aspects.
Research limitations/implications
The main limitation of the work lies in not being fully reproducible due to the fixed number of data sources and their digital nature, together with subjective decisions in work selection, data extraction and data analysis.
Originality/value
To the best of the authors’ knowledge no study has yet analyzed the BPA research field by means of an SLR. This study will benefit practitioners and research groups working on this topic by allowing them to get a rigorous overview of the BPA research field with an emphasis on available BPA design methodologies, and become aware of research gaps within the BPA field to position further research.
Prozessverbesserung gehört zum täglich Brot von Unternehmen. Bestehende Prozessverbesserungsansätze
konzentrieren sich vornehmlich auf die detaillierte Analyse von Einzelprozessen und greifen daher oftmals zu kurz. In der Praxis lassen sich Prozesse kaum isoliert voneinander betrachten. Sie sind eng miteinander verflochten und hängen unter anderem in Bezug auf Mitarbeiter und Anwendungssysteme voneinander ab. Vor diesem Hintergrund haben die Deutsche Bank und die Projektgruppe Wirtschaftsinformatik des Fraunhofer-Instituts für Angewandte Informationstechnik FIT im Rahmen eines angewandten Forschungsprojekts einen Ansatz zur Ende-zu-Ende-Prozessverbesserung (E2E-Prozessverbesserung) auf Betriebsmodellebene entwickelt. Die Pilotierung dieses Ansatzes erfolgte im Rahmen eines Integrationsprojekts bei Steuerabwicklungsprozessen in der Wertpapierabwicklung.
Full-text: http://www.fim-rc.de/Paperbibliothek/Veroeffentlicht/489/wi-489.pdf
The main objective of this paper is to show the process map for introducing the Accessibility Management System in the Saragossa city council web service. This map is a requirement of the Spanish Association for Standards and Certification (Aenor) for the "N" certification of ICT Accessibility, which guarantees users that an internet page is accessible. All public sector organizations are required by law to achieve this norm and display the "N" mark of certification. To identify the processes and design the process map, an expert reviewed documents and interviewed managers and staff. The processes were classified into strategic, key and support categories and so identified on the process map, which indicates sequences and the relationships between inputs and tasks. The results section describes the main activities and analyzes their inter-relationship.
The benefits of decomposing process models are widely recognized in literature. Nevertheless, the question of what actually constitutes a "good" decomposition of a business process model has not yet been dealt with in detail. Our starting point for obtaining a "good" decomposition is Wand and Weber's decomposition model for information systems which is specified for business process modeling. In the investigation at hand, we aim to explore in how far modeling languages support the user in fulfilling the decomposition conditions according to Wand and Weber. An important result of the investigation is that all investigated business process modeling languages (BPMN, eEPC, UML AD) can meet most of the requirements.
Many articles discuss the design of fine- or coarse-grained IT services without defining what granularity exactly means. However, this is important to know since the granularity influence e.g. the reusability or the composition effort of services and thus the development, maintenance and composition costs of a service realization. Therefore, we present different metrics to evaluate and compare the granularity of various service realizations of a process where each metric represents a different perspective on service granularity. In addition, we discuss the advantages and disadvantages of these metrics and argue that a reasonable measurement of service granularity can usually be obtained by the combination of the metrics. Furthermore, we illustrate that the proposed metrics may constitute a first step towards the evaluation of the total costs of various service realizations. The application of the metrics as well as the discussion of the practical benefits is illustrated by a real world case.
The main objective of this paper is to show the process map for introducing the Accessibility Management System in the Saragossa city council web service. This map is a requirement of the Spanish Association for Standards and Certification (Aenor) for the "N" certification of ICT Accessibility, which guarantees users that an internet page is accessible. All public sector organizations are required by law to achieve this norm and display the "N" mark of certification.To identify the processes and design the process map, an expert reviewed documents and interviewed managers and staff. The processes were classified into strategic, key and support categories and so identified on the process map, which indicates sequences and the relationships between inputs and tasks. The results section describes the main activities and analyzes their inter-relationship.
Management of the enterprise architecture has become increasingly recognized as a crucial part of both business and IT management. Still, a common understanding and methodological consistency seems far from being developed. Acknowledging the significant role of research in moving the development process along, this article employs different bibliometric methods, complemented by an extensive qualitative interpretation of the research field, to provide a unique overview of the enterprise architecture literature. After answering our research questions about the collaboration via co-authorships, the intellectual structure of the research field and its most influential works, and the principal themes of research, we propose an agenda for future research based on the findings from the above analyses and their comparison to empirical insights from the literature. In particular, our study finds a considerable degree of co-authorship clustering and a positive impact of the extent of co-authorship on the diffusion of works on enterprise architecture. In addition, this article identifies three major research streams and shows that research to date has revolved around specific themes, while some of high practical relevance receive minor attention. Hence, the contribution of our study is manifold and offers support for researchers and practitioners alike.
Whereas the benefits of decomposing process models are obvious, the question what actually characterizes a “good” decomposition of a business process model has been given little attention to date. In addition, the process of decomposition itself is considered as being an “art” in literature. Our approach for achieving a “good” decomposition is Wand and Weber’s decomposition model for information systems. As a first step in our investigation we aim to explore in how far the decomposition model can be adapted for business process modeling at all. The potential this model might bear for evaluating decompositions of process models has been promoted in literature quite often, while a corresponding investigation is still missing. We address this gap by the following research. In the long term, we intend to establish guidelines for decomposing business process models in a structured way.
Obwohl die Vorteile der Dekomposition bei der Prozessmodellierung hinlänglich bekannt sind, ist nach wie vor unklar, durch welche Eigenschaften sich eine „gute“ Zerlegung eines Prozessmodells auszeichnet. In der Literatur wird die Dekomposition meist pragmatisch interpretiert, wobei ein strukturiertes Vorgehen fehlt. Aus diesem Grund zieht die vorliegende Arbeit das Dekompositionsmodell nach Wand und Weber heran und spezifiziert dieses für die Geschäftsprozessmodellierung. Dabei gilt es, zunächst zu hinterfragen, inwiefern das Dekompositionsmodell überhaupt auf die Prozessmodellierung übertragen werden kann. In der Literatur finden sich bisher keine entsprechenden Untersuchungen, auch wenn dieser Ansatz in mehreren Publikationen als sehr vielversprechend eingeschätzt wird. Mit vorliegender Arbeit wird ein Beitrag geleistet, diese Lücke zu schließen. Langfristig wird die Entwicklung von Handlungsanweisungen angestrebt, welche den Anwender bei der zielgerichteten Dekomposition von Prozessmodellen unterstützen.
Abstract
Whereas the benefits of decomposing process models are obvious, the question what actually characterizes a “good” decomposition of a business process model has been given little attention to date. In addition, the process of decomposition itself is considered as being an “art” in literature. Our approach for achieving a “good” decomposition is Wand and Weber’s decomposition model for information systems. As a first step in our investigation we aim to explore in how far the decomposition model can be adapted for business process modelling at all. The potential this model might bear for evaluating decompositions of process models has been promoted in literature quite often, while a corresponding investigation is still missing. We address this gap by the following research. In the long term, we intend to establish guidelines for decomposing business process models in a structured way.
Business Process Management (BPM) acceptance requires a modeling framework in which all abstraction layers (from the high-level enterprise view to the low-level task view) are unified and kept consistent at all times. This paper presents a simple yet effective multi-layered multi-view business process modeling framework that integrates organizational aspects, behavioral aspects, and input and output of business processes. The ultimate goal of this framework is to structure modeling efforts and to improve the usability of business process models in day-to-day decision making. A set of relationships between the layers are defined to support round-tripping as much as possible. A financial services based example is presented as a proof-of-concept in which the modeling framework was tested and assessed.
A significant challenge that faces IT management is that of aligning the IT infrastructure of an enterprise with its business goals and practices, also called business-IT alignment. A particular business-IT alignment approach, the foundation for execution approach, was well-accepted by practitioners due to a novel construct, called the operating model (OM). The OM supports business-IT alignment by directing the coherent and consistent design of business and IT components. Even though the OM is a popular construct, our previous research detected the need to enhance the OM, since the OM does not specify methods to identify opportunities for data sharing and process reuse in an enterprise. In this article, we address one of the identified deficiencies in the OM. We present a process reuse identification framework (PRIF) that could be used to enhance the OM in identifying process reuse opportunities in an enterprise. We applied design research to develop PRIF as an artefact, where the development process of PRIF was facilitated by means of the business-IT alignment model (BIAM). We demonstrate the use of the PRIF as well as report on the results of evaluating PRIF in terms of its usefulness and ease-of-use, using experimentation and a questionnaire.
In today's highly competitive financial markets, financial innovation and bank's merge and acquisition activities are growing much. How to quickly construct business process upon IT infrastructure becomes the kernel of competition. As one of the classic application of service-oriented architecture, the grid technology can considerably help banks to improve the efficiency of constructing business process. In this paper, a tag-based processing model upon service-oriented grid is proposed. Through the practical scenario, the efficiency and security are demonstrated. Compared with traditional methods, the proposed solution has three advantages: (i) it is general enough to apply to banking applications without modifying upper business logic; (ii) with minor cost on processing normal request, it can provide high security and facility for reconstruction of banking business; (iii) it can help bank construct the new business process in the mean time.
What is the interplay between business process management (BPM) and service-oriented architecture (SOA) in achieving high
business process quality? In this paper, we empirically investigate the impact of both SOA and BPM on business process quality
in terms of straight-through processing, business-to-business integration, quality control, as well as standardization and
consolidation of business processes. For the empirical evaluation of our model, we use the data of 157 German service firms.
The results show that the SOA paradigm has still received rather low adoption rates in the industry. However, SOA, BPM, and
related information technologies have a direct positive impact on business process quality and the analysis provides evidence
for the complementarities of BPM and SOA since interaction effects between them have an additional significant impact on business
process quality. Consequently, firms having adopted SOA can more effectively apply BPM.
Business intelligence (BI) is often seen as a combined business and IT function. As such, the operational structure of BI is not always clearly defined. In this paper, we present an overview of typical BI operational structures and elaborate their characteristics. Based on this analysis, we will (in future work) design a reference process map for BI which can be used as a template to define organization-specific BI operational structures.
Die systematische Entwicklung und Modellierung der Unternehmensarchitektur wird von der Praxis wie auch der Wissenschaft als ein bedeutendes aber auch umfassendes Aufgabengebiet angesehen. Der vorliegende Beitrag greift die Modellierung der Prozessarchitektur im Ist-Zustand als Themenstellungen heraus und begründet, dass durch Integration von manuell konstruierten und automatisch generierten Modellen die Aktualität, Korrektheit und Vollständigkeit der Architektur erhöht und der Aktualisierungsaufwand reduziert werden kann.
Das Ziel des Beitrags ist es, Herausforderungen der Integration von manuell konstruierten und automatisch generierten Prozessmodellen zu untersuchen sowie Ansätze zur Lösung zu geben. Hierzu werden die beiden Modellierungsansätze (manuelle Konstruktion und automatische Generierung) vorgestellt und die Vorteilhaftigkeit der Integration sowie ihr Beitrag im Rahmen der Unternehmensarchitektur begründet. Darüber hinaus werden Herausforderungen bei der Integration identifiziert und deren Grundlagen in einem Morphologischen Kasten zusammengestellt. Die Analyse bestehender Ansätze zeigt, dass keine der untersuchten Methoden die Problemstellung vollständig lösen kann. Darüber hinaus wird für ein ausgewähltes Integrationsszenario ein erster Ansatz entwickelt.
An abstract is not available.
Process Landscaping is a method, which supports modelling of related processes. These processes can be modelled on different levels of abstraction. Interfaces between processes are considered as first class process entities. It prevents loosing an overview of the whole framework of processes and ensures that decisions about processes are not burdened out by an overwhelming amount of details. In this article we discuss the approach of Process Landscaping by developing a real-world software process.
Service Oriented Architectures (SOA) are rapidly emerging as the premier integration and architectural approach in contemporary, complex, heterogeneous computing environments. SOA is not simply about deploying software: it also requires that organisations evaluate their business models, come up with service-oriented analysis and design techniques, deployment and support plans, and carefully evaluate partner/customer/supplier relationships. Since SOA is based on open standards and is frequently realised using Web Services (WS), developing meaningful WS and business process specifications is an important requirement for SOA applications that leverage WS. Designers and developers cannot be expected to oversee a complex service-oriented development project without relying on a sound design and development methodology. This paper provides an overview of the methods and techniques used in service-oriented design and development. The aim of this paper is to examine a service development methodology from the point of view of both service producers and requesters and review the range of elements in this methodology that are available to them.
The elements of an enterprise are managed more and more model-based. The state-of-the-art in the area of modelling of organisations is based on fixed metamodels. Product models are created by using product modelling environments, process models are created in business process modelling tools and organisational models are realised in personnel management tools. Web service models link these business models to information technology. They are created by using standardised languages and common ontologies. Information technology is modelled in tools supporting notions such as workflow or object-orientation. The models of the company’s strategy, goals and the appropriate measurements are described and monitored by using tools supporting management concepts such as Balanced Scorecard.
Major requirements to an enterprise modelling platform are flexibility and adaptability. These are fulfilled by environments providing flexible metamodelling capabilities. The main characteristic of such environments is that the formalism of modelling—the metamodel—can be freely defined. This raises research issues on how to design, manage, distribute and use such metamodels on a syntactic as well as on a semantic level and how to integrate, run and maintain a metamodelling platform in a corporation’s environment.
Platforms based on metamodelling concepts should support the following topics:
1.
Engineering the business models & their web services
2.
Designing and realizing the corresponding information technology
3.
Evaluating the used corporation resources and assets
This paper presents a framework for metamodelling platforms and gives some answers to the research issues stated above. As part of the framework flexible metamodel integration mechanisms, using meta-metamodels (meta2-models) and semantical mapping, are discussed. Additionally, a system architecture and the building blocks of a corporate metamodelling platform are described. Finally, best practices from three EU funded projects—REFINE, ADVISOR, and PROMOTE—all realised with industrial partners, are presented.
The full version of the paper can be downloaded from http://www.dke.univie.ac.at/mmp
Due to rapid changing business requirements the complexity in developing enterprise-spanning applications is continually growing.
A vital field of delivering technical concepts and technologies for integrating heterogeneous applications and components
to support inter-organisational business processes is the area of Enterprise Application Integration (EAI). A common characteristic
of all EAI approaches is their focus on technical and runtime aspects of integration. From our project experiences in developing
large B2B applications, it is necessary to integrate applications on the business and conceptual level as well. Because of
the diversity of models and modelling languages for developing enterprise applications, we propose the Enterprise Model Integration (EMI) approach. In this paper we describe basic concepts of EMI, a pattern system for metamodel integration, and a case study applying
EMI for developing B2B applications. The EMI approach is compatible with the MDA infrastructure and implemented within the
meta model management tool ADONIS.
One of the fundamental principles of the database approach is that a database allows a nonredundant, unified representation of all data managed in an organization. This is achieved only when methodologies are available to support integration across organizational and application boundaries.
Methodologies for database design usually perform the design activity by separately producing several schemas, representing parts of the application, which are subsequently merged. Database schema integration is the activity of integrating the schemas of existing or proposed databases into a global, unified schema.
The aim of the paper is to provide first a unifying framework for the problem of schema integration, then a comparative review of the work done thus far in this area. Such a framework, with the associated analysis of the existing approaches, provides a basis for identifying strengths and weaknesses of individual methodologies, as well as general guidelines for future improvements and extensions.
This paper describes a novel theoretical and empirical approach to tasks such as business process redesign and knowledge management. The project involves collecting examples of how different organizations perform similar processes, and organizing these examples in an on-line “process handbook.” The handbook is intended to help people: (1) redesign existing organizational processes, (2) invent new organizational processes (especially ones that take advantage of information technology), and (3) share ideas about organizational practices.
A key element of the work is an approach to analyzing processes at various levels of abstraction, thus capturing both the details of specific processes as well as the “deep structure” of their similarities. This approach uses ideas from computer science about inheritance and from coordination theory about managing dependencies. A primary advantage of the approach is that it allows people to explicitly represent the similarities (and differences) among related processes and to easily find or generate sensible alternatives for how a given process could be performed. In addition to describing this new approach, the work reported here demonstrates the basic technical feasibility of these ideas and gives one example of their use in a field study.
Das Buch behandelt die Transformation von Unternehmen des Industriezeitalters in erfolgreiche Organisationen des Informationszeitalters. Es geht auf die fachliche wie auf die politische und kulturelle Dimension dieses Wandels ein. Im ersten Teil wird der St. Galler Ansatz des Business Engineering vorgestellt. Im zweiten Teil werden verschiedene Forschungsansätze des Business Engineering zusammengefasst, die Geschäftsmodelle des Informationszeitalters analysieren, Indikatoren und Treiber des Wandels identifizieren sowie Methoden und Instrumente für Veränderungsprozesse entwickeln. Der dritte Teil umfasst ausgewählte Berichte aus der Praxis, in denen die Konzepte des Business Engineering auf konkrete Fragestellungen in Grossunternehmen angewendet werden.
For many companies, the strategic as well as the organizational fit of their information systems is a pivotal factor for staying competitive. At the same time, there is an increasing demand for integrating business processes and informations systems with those of customers and suppliers. The resulting need for organizational changes and the introduction of corresponding information systems is a challenging task. The complexity of the task requires a separation of concerns. At the same time it causes language barriers between various stakeholders, especially between business people and information technology professionals. Enterprise models provide various abstractions that help with the design of corporate information systems which are in line with a company's organization and its long term strategy. They also promise to provide a common conceptual foundation to foster the communication between people with different professional backgrounds. In this paper we introduce a model for enterprise modelling that is based on an extendable set of special purpose modeling languages, e.g. for describing corporate strategies, business processes, resources or information. The visual languages provide intuitive abstractions for various observers. The languages are defined in metamodels which in turn are specified through a common meta-metamodel. Similar to a specialized technical language, they provide concepts that help with structuring and analyzing a domain according to specific objectives. Since the languages are specified in a semi formal way, the models allow for the generation of software prototypes. The languages share common concepts which allow for a tight integration of the various parts of an enterprise model. In addition to offering specialized modeling languages, the modeling method also includes examples, case studies and reference models - to promote the re-use of concepts and artefacts. The use of the method is illustrated by an example, where two different partial models are being integrated.
Das Buch behandelt die Transformation von Unternehmen des Industriezeitalters in erfolgreiche Organisationen des Informationszeitalters. Es geht auf die fachliche wie auf die politische und kulturelle Dimension dieses Wandels ein. Im ersten Teil wird der St. Galler Ansatz des Business Engineering vorgestellt. Im zweiten Teil werden verschiedene Forschungsansätze des Business Engineering zusammengefasst, die Geschäftsmodelle des Informationszeitalters analysieren, Indikatoren und Treiber des Wandels identifizieren sowie Methoden und Instrumente für Veränderungsprozesse entwickeln. Der dritte Teil umfasst ausgewählte Berichte aus der Praxis, in denen die Konzepte des Business Engineering auf konkrete Fragestellungen in Grossunternehmen angewendet werden.
During the past decade, the software industry has begun a significant transformation often referred to as the industrialisation of software development. This evolution takes place in two main areas: The transformation of the products themselves and the transformation of the industry's processes towards increased productivity. Main innovations concern model-driven development, service engineering, and development of composite applications on top of service-oriented architectures. This paper discusses the main aspects of this transformation from the view of a provider of business software and shows implications for customers and suppliers as well as promising research areas for the future.
On the one hand, data models decrease the complexity of information system development. On the other hand, data models causes additional complexity. Recently structural analogies are discussed as instruments reducing the complexity of data models, this piece of research presents a procedure to identify structural analogies in data models and demonstrates its performance by analyzing Scheer's reference model for industrial enterprises (Y-CIM-model). The proposed procedure is based on formalizing data models within set theory and uses a quantitative similarity measure. The obtained results show both identical and very similar information structures within the Y-CIM-model. Furthermore, ways of dealing with the identified structural analogies are discussed from an analysis and software design perspective.
On the one hand, data models decrease the complexity of information system development. On the other hand, data models causes additional complexity. Recently structural analogies are discussed as instruments reducing the complexity of data models. This piece of research presents a procedure to identify structural analogies in data models and demonstrates its performance by analyzing Scheer’s reference model for industrial enterprises (Y-CIM-model). The proposed procedure is based on formalizing data models within set theory and uses a quantitative similarity measure. The obtained results show both identical and very similar information structures within the Y-CIM-model. Furthermore, ways of dealing with the identified structural analogies are discussed from an analysis and software design perspective.
Wandelnde Geschäftsprozesse erfordern von den unterstützenden Informationssystemen die Fähigkeit, sich flexibel an Änderungen anpassen zu können. Während dies bei Workflow-Managementsystemen durch ihre spezielle Architektur gewährleistet ist, sind operative Anwendungssysteme in der Regel verhältnismäßig starr in den unterstützten Abläufen. Der Beitrag beschreibt ein Konzept, das eine einfache Adaption von operativen Informations-systemen ermöglicht. Das Konzept basiert auf generischen Strukturen, die mit Geschäftsprozeß-modellen instantiiert werden. Dadurch wird erst bei der Installation das Informationsmodell des Anwendungssystems festgelegt. Das Prinzip der generischen Strukturen wird anhand statischer und dynamischer Aspekte von Prozeßstrukturen sowie am Beispiel konkreter Anwendungen beschrieben.
http://my.uni.li/i3v/publikationen/00065700/01749067.PDF
Two paradigms characterize much of the research in the Information Systems discipline: behavioral science and design science. The behavioral-science paradigm seeks to develop and verify theories that explain or predict human or organizational behavior. The design-science paradigm seeks to extend the boundaries of human and organizational capabilities by creating new and innovative artifacts. Both paradigms are foundational to the IS discipline, positioned as it is at the confluence of people, organizations, and technology. Our objective is to describe the performance of design-science research in Information Systems via a concise conceptual framework and clear guidelines for understanding, executing, and evaluating the research. In the design-science paradigm, knowledge and understanding of a problem domain and its solution are achieved in the building and application of the designed artifact. Three recent exemplars in the research literature are used to demonstrate the application of these guidelines. We conclude with an analysis of the challenges of performing high-quality design-science research in the context of the broader IS community.
Kernpunkte Vor dem Hintergrund aktueller Positionierungsdebatten ist eine genaue Kenntnis des Methodenprofils der Wirtschaftsinformatik
zunehmend von Bedeutung. Der Beitrag zeigt anhand einer Literaturanalyse, dass
–
sich das aktive Methodenspektrum der Wirtschaftsinformatik mit argumentativ-, konzeptionell- und formal-deduktiven Analysen,
Prototyping, Fallstudien und quantitativen Querschnittanalysen aus sechs Kernmethoden zusammensetzt, die in 91% der Beiträge
zum Einsatz kommen
–
die WI in den letzten Jahren zunehmend auch quantitativ-empirische Methoden einsetzt, während gleichzeitig der Anteil argumentativ-deduktiver
Arbeiten zurückgeht
–
Fallstudien, konzeptionelle und formal-deduktive Analysen von WI und IS etwa in gleichem Umfang eingesetzt werden, Prototyping
und argumentativ-deduktive Arbeiten das methodologische Spezifikum der Wirtschaftsinformatik und quantitativ-empirische Querschnittstudien
sowie Laborexperimente das methodologische Spezifikum des Information Systems Research sind.
Kernpunkte An einen Service, der in einer Serviceorientierten Architektur eines Unternehmens zur Verfügung gestellt werden soll, werden
oftmals die folgenden fachlichen Anforderungen gestellt:
–
Er soll übergreifend über mehrere Ausprägungen einer Problemstellung einsetzbar sein.
–
Er soll die redundante Implementierung von Funktionalitäten weitgehend vermeiden.
–
Er soll möglichst schnell und unkompliziert genutzt werden können.
Diesen Anforderungen kann bei der Entwicklung eines Service wie folgt entsprochen werden:
–
Einen wichtigen Beitrag leistet die Identifikation der Services, d. h. die Beantwortung der Frage, welche Aktionen der Geschäftprozesse
eines Unternehmens durch einen Service realisiert werden sollten.
–
Des Weiteren trägt dazu die geeignete fachliche Gestaltung der identifizierten Services bei.
In this article we describe the method of business process landscaping. It is developed by the experience we made in several process modeling projects dealing with a huge amount of details. A process landscape shows the relations between the processes and serves as a starting point to refine process models on different levels of abstraction. Process landscaping allows to add all details, but it avoids to loose the overview about process models and their interfaces. We discuss the method in the light of an example from the telecommunications industry, we formalize some of the most important terms around the notion of a process landscape and we use this formalization to formulate some consistency conditions for process landscapes.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus, and branding interests. For more information, please contact: U. S. Corporate and Government Sales
This article discusses building a computable design process model, which is a prerequisite for realizing intelligent computer-aided design systems. First, we introduce general design theory, from which a descriptive model of design processes is derived. In this model, the concept of metamodels plays a crucial role in describing the evolutionary nature of design. Second, we show a cognitive design process model obtained by observing design processes using a protocol analysis method. We then discuss a computable model that can explain most parts of the cognitive model and also interpret the descriptive model. In the computable model, a design process is regarded as an iterative logical process realized by abduction, deduction, and circumscription. We implemented a design simulator that can trace design processes in which design specifications and design solutions are gradually revised as the design proceeds.
Due to the growing importance of alignment, compliance and manageability issues, increased attention is being paid to architectures and architecture management recently. A holistic approach to enterprise architecture requires business related and information systems related artifacts to be equally treated. This paper describes the extension of an existing approach to enterprise architecture and its implementation using a commercial metamodeling platform. In addition to the approach metamodels in general, special attention is paid to the linkages between different architecture layers, both in the underlying model and in its implementation.
This paper describes a novel theoretical and empirical approach to tasks such as business process redesign, enterprise modeling, and software development. The project involves collecting examples of how different organizations perform similar processes, and organizing these examples in an on-line "process handbook". The handbook is intended to help people: (1) redesign existing organizational processes, (2) invent new organizational processes (especially ones that take advantage of information technology), (3) learn about organizations, and (4) automatically generate software to support organizational processes. A key element of the work is an approach to analyzing processes at various levels of abstraction, thus capturing both the details of specific processes as well as the "deep structure" of their similarities. This approach uses ideas from computer science about inheritance and from coordination theory about managing dependencies. A primary advantage of the approach is that it allows people to explicitly represent the similarities (and differences) among related processes and to easily find or generate sensible alternatives for how a given process could be performed. In addition to describing this new approach, the work reported here demonstrates the basic technical feasibility of these ideas.
Process modeling becomes more and more an important task not only for the purpose of software engineering, but also for many other purposes besides the development of software. Therefore it is necessary to evaluate the quality of process models from different viewpoints. This is even more important as the increasing number of different end users, different purposes and the availability of different modeling techniques and modeling tools leads to a higher complexity of information models. In this paper the Guidelines of Modeling (GoM) , a framework to structure factors for the evaluation of process models, is presented. Exemplary, Guidelines of Modeling for workflow management and simulation are presented. Moreover, six general techniques for adjusting models to the perspectives of different types of user and purposes will be explained.
Conditional planning of process activities—towards a semantic-based approach. Working paper Design science in information systems
- B M Bewernik
- M Bolsinger
- M Henneberger
- A Krammer
- F S Lautenbacher
- J Park
B, Bewernik M, Bolsinger M, Henneberger M, Krammer A, Lautenbacher F (2007) Conditional planning of process activities—towards a semantic-based approach. Working paper, University of Augsburg Hevner A, March S, Park J, Ram S (2004) Design science in information systems. Res MIS Quat 28(1):75–105 IDS Scheer AG (2000) ARIS method, Version 5.0, 2000
A comprehensive enterprise architecture metamodel and its implementation using a metamodeling platform Enterprise modeling and information systems architectures, proceedings of the workshop in Klagenfurt, GI-Edition Lecture Notes (LNI) Service-oriented architecture—concepts, technology, and design
- N S Bose
- Fiammante
N, Bose S, Fiammante M (2005) Service-oriented architecture compass—business value, planning and enterprise roadmap. IBM Press, Armonk Braun C, Winter R (2005) A comprehensive enterprise architecture metamodel and its implementation using a metamodeling platform. In: Desel J, Frank U (eds) Enterprise modeling and information systems architectures, proceedings of the workshop in Klagenfurt, GI-Edition Lecture Notes (LNI), Klagenfurt, 24.10.2005, Gesellschaft fü Informatik, Bonn, p 75 Buck-Emden R, Zencke P (2004) mySAP CRM—Kundenbezogene Geschä mit SAP CRM 4.0. SAP Press, Bonn Erl T (2005) Service-oriented architecture—concepts, technology, and design. Prentice Hall, Boston Fettke P, Loos P (2005) Zur Identifikation von Strukturanalogien in Datenmodellen -Ein Verfahren und seine Anwendung am Beispiel des Y-CIM-Referenzmodells von Scheer. WIRTSCHAFTSINFOR-MATIK 47(2):89–100
Modeling of business systems using the semantic object model (SOM)—a methodological framework Handbook on architectures of information systems
- Ok
- Sinz
- Ej
OK, Sinz EJ (1997) Modeling of business systems using the semantic object model (SOM)—a methodological framework. In: Bernus P, Blazewicz J, Schmidt G, Shaw M (eds) Handbook on architectures of information systems. International handbooks on information systems, vol I. Springer, Heidelberg, pp 339–358
Tools for inventing organizations: toward a handbook of organizational processes Business Engineering: Prozess-und Systementwicklung, Band 1 Entwicklungstech-niken Service-oriented computing
- Tw
- K Crowston
- J Lee
- Dellarocas B C Pentland
- G Wyner
- J Quimby
- Cs Osborn
- A Bernstein
- G Herman
- O M Klein
- Donnell
TW, Crowston K, Lee J, Pentland B, Dellarocas C, Wyner G, Quimby J, Osborn CS, Bernstein A, Herman G, Klein M, O'Donnell E (1999) Tools for inventing organizations: toward a handbook of organizational processes. Manage Sci 45(3):425–443 O ¨ sterle H (1995) Business Engineering: Prozess-und Systementwicklung, Band 1 Entwicklungstech-niken, 2nd edn. Springer, Berlin O ¨ sterle H, Winter R (2003) Business Engineering -Auf dem Weg zum Unternehmen des Informations-zeitalters. Springer, Berlin Papazoglou MP, Georgakopoulos D (2003) Service-oriented computing. Commun ACM 46(10):25–28
Komplexitä in Prozessmodellen: methodenspezifische Gesta-ltungsempfehlungen fü die Informationsmodellierung, Wiesbaden SAP (2007) SAP Business Maps: Solution Maps
- Rosemann
Rosemann M (1996) Komplexitä in Prozessmodellen: methodenspezifische Gesta-ltungsempfehlungen fü die Informationsmodellierung, Wiesbaden SAP (2007) SAP Business Maps: Solution Maps. Available online http://www.sap.com/solutions/ businessmaps/solutionmaps/index.epx, accessed 2007–09–20
Service-oriented design and development methodology The process map as an instrument to standardize processes 101
- Mp
MP, van den Heuvel W-J (2006) Service-oriented design and development methodology. Int J Web Eng Technol 2(4):412–442 The process map as an instrument to standardize processes 101
Redefining core banking—worldwide survey
- T Balgheim
- J-M Ollagnier
Strukturanalogien in Informationsmodellen - Ihre Definition, ihr Nutzen und ihr Einfluss auf die Bildung von Grundsätzen ordnungsmässiger Modellierung (GoM)
- J Becker
Guidelines of business process modeling Business process management, models, techniques, and empirical studies
- J Becker
- M Rosemann
- C Von Uthmann
Conditional planning of process activities-towards a semantic-based approach. Working paper
- B Heinrich
- M Bewernik
- M Bolsinger
- M Henneberger
- A Krammer
- F Lautenbacher
ARIS method, Version 5
- A G Ids Scheer
Serviceorientierte Architekturen bei Finanzdienstleistern, ibi research an der Universität Regensburg GmbH
- M Koch
- M Rill
Den großen Schritt wagen
- L Lochmaier