Enterprise Modelling and Information Systems Architectures (EMISAJ)
Total Page:16
File Type:pdf, Size:1020Kb
Enterprise Modelling and Information Systems Architectures Vol. 9, No. 1, June 2014 22 Ulrich Frank Ulrich Frank Enterprise Modelling: The Next Steps Enterprise modelling is at the core of Information Systems and has been a subject of intensive research for about two decades. While the current state of the art shows signs of modest maturity, research is still facing substantial challenges. On the one hand, they relate to shortcomings of our current knowledge. On the other hand, they are related to opportunities of enterprise modelling that have not been sufficiently addressed so far. This paper presents a personal view of future research on enterprise modelling. It includes requests for solving underestimated problems and proposes additional topics that promise to promote enterprise models as more versatile tools for collaborative problem solving. In addition to that, the paper presents requests for (re-) organising research on enterprise modelling in order to increase the impact of the field. 1 Introduction at least one conceptual model of an organisa- tional action system with at least one conceptual It has been a wide-spread conviction for long model of a corresponding information system. that the complexity of large information systems Usually, but not necessarily, the various mod- recommends the use of models. Information sys- els that constitute an enterprise model are cre- tems are aimed at representing domains through ated with domain-specific modelling languages data that is accessible by prospective users. Rep- (DSML). To emphasise that enterprise models are resenting a–factual or aspired–domain cannot be intended to provide a medium both for fostering accomplished by modelling it directly. Instead, analysis and design tasks and for communication it comprises a twofold abstraction: We perceive across traditional professional barriers, the term a domain primarily through language, which in “multi-perspective enterprise model” has been turn reflects an abstraction over “objective” fea- introduced (Frank 1994). A multi-perspective en- tures of a domain. At the same time, using an terprise model is an enterprise model that em- information system requires an interface that cor- phasises accounting for multiple perspectives. responds to the language spoken in the targeted A perspective represents a specific professional domain. Therefore, the construction of informa- background that corresponds to cognitive dis- tion systems recommends the design of concep- positions, technical languages, specific goals and tual models. They do not only promise to reduce capabilities of prospective users (Frank 2013b). complexity by abstracting from ever changing pe- culiarities of technical infrastructures; they also In recent years, the term “enterprise architec- allow for getting prospective users involved in ture” has gained remarkable attention (Buckl et the analysis and design process. Exploiting the al. 2010; Land et al. 2009; Lankhorst 2005). The potential of information systems will often re- differences between enterprise model and enter- quire reorganising existing patterns of action— prise architecture are mainly related to the inten- sometimes in a radical way. Therefore, analysis ded audience. Enterprise modelling is aimed at and design of information systems should usually various groups of stakeholders that are involved be done conjointly with analysing and designing in planning, implementing, using and maintain- the organisational action system. The conception ing information systems. Therefore, enterprise of an enterprise model was developed to address models are supposed to offer a variety of cor- this demand. An enterprise model integrates responding abstractions. These include models Enterprise Modelling and Information Systems Architectures Vol. 9, No. 1, June 2014 Enterprise Modelling: The Next Steps 23 that serve as a foundation of software develop- At first, it represents a renunciation of the ori- ment. Therefore, the development of respective ginal approach to enterprise modelling, which DSML is a particular characteristic of enterprise was aimed at developing information systems modelling. Different from that, enterprise archi- from scratch. With respect to the complexity of tecture mainly targets IT management. There- today’s IT infrastructures and the fact that most fore, it puts less emphasis on the specification organisations will not develop substantial parts of DSML. Nevertheless, there is no fundamental of their information system on their own any- difference between both approaches. Instead, the more, this additional focus is certainly reasonable. abstractions used in enterprise architectures can Secondly, it is not only aimed at supporting the be seen as an integral part of more comprehens- design of IT infrastructures that are in line with ive enterprise models. In Information Systems, the corporate action system, but also at providing enterprise modelling has been a pivotal field of an instrument for IT management. Figure1 illus- research that has evolved over a period of more trates the representation of an enterprise model than 20 years (CIMOSA: Open system architec- through a set of interrelated diagrams that cor- ture for CIM 1993; Ferstl and Sinz 1998; Group respond to the current state of the art. To ensure 2009; Scheer 1992; Zachman 1987). It has produced integration, the partial models that are repres- various modelling frameworks, DSML as well as ented by the diagrams should be created with corresponding tools. The field has achieved a modelling languages that were specified with the remarkable degree of maturity which is indicated same meta modelling language and that share by the fact that enterprise modelling is part of common concepts (Frank 2011). many IS curricula—even though to different ex- While the abstractions covered by today’s en- tent. Nevertheless, there is still need for further terprise modelling methods arguably represent research to exploit the potential of enterprise relevant perspectives on an enterprise, a compre- modelling. In this paper I will point at relevant hensive representation of all aspects that may be shortcomings of the current state of the art in relevant for analysing, designing and managing order identify core elements of a future research a company together with its information sys- agenda. tem requires accounting for more context. While such a demand may look like an exaggeration to 2 The Need for More Context some, it is actually the consequent continuation of current practice: All professional activities in At the beginning, approaches to enterprise mod- a company are characterised by the use of con- elling were mainly focussed on developing high- ceptual abstractions, i.e., by a specific technical level frameworks to provide a common structure terminology and corresponding language games. or architecture of an enterprise and its informa- Reconstructing these terminologies through ad- tion system (CIMOSA: Open system architecture ditional DSML would not only enable further use for CIM 1993; Scheer 1992; Zachman 1987). Apart scenarios, it would also enrich existing models from using general purpose modelling languages with additional context. Context does not only (GPML) like the ERM and the UML, the devel- refer to the topics that are represented in an en- opment of DSML was mainly aimed at business terprise model. It also refers to the context in process modelling. Later, DSML were created for which the development and use of models occur. modelling strategies, organisational structures On the one hand, this kind of context includes or generic resources. In recent years, some ap- specific methods for enterprise modelling. On proaches have evolved that are aimed at DSML the other hand, it refers to organisational and for modelling IT infrastructures and IT architec- managerial arrangements to foster an adequate tures. This focus is remarkable for two reasons. handling of enterprise models. Enterprise Modelling and Information Systems Architectures Vol. 9, No. 1, June 2014 24 Ulrich Frank Goal System Diagram Sustainable sales Labor costs 1 3 Value Chain Diagram Increase Keep sustainabl labor e sales costs Inbound Outbound Marketing stable Services Logistics Operations Logistics Sales Customer Number of satisfaction sales agents 2 4 Sustainable Sustainable sales sales 1 1 Increase Increase customer number of satisfactio sales n Increase Increase agents sust. sales sust. in region sales in A region B Organizational Chart Business Process Map Board of Directors <Customer <Sales> <IT Service> Service> Marketing Finance Accounting Sales Order Management Technical Support Complaint Product A Handling Product Asset Market Private A Manageme Systems Research Customers nt <Sales> <Customer Service> Product Corporate Corporate Order Management Complaint Controlling Planning Credits Customers Product B <Sales> Handling Product B Customer <Customer Investor Decisions Sales <Sales> Akquisition Service> Promotion Relations Support Forecast Order Complaint Management Handling Product Product C C < Agent > amount not Inform Customer Order < Agent > < Agent > available declined Order Check Delivery Delivery Confirm Order < Fleet Manager > recieved Capacity possible Business Process Diagram amount Check Logistics < Agent > available Delivery at Decline Order IT Resource Diagram desired date not possible Object Model Scan Order Invoice SAP CO SAP FI SAP R&D PLM 3.7 Customer Engine 5.1 created: Date issued: Date P10 6.0 P10 6.0 P20 custID: String issues 0,* no: String