Führungsinformationssysteme:historische Entwicklung und Konzeption

Führungsinformationssysteme gelten als Instrumente zur erforderlichen Verkürzung von Managemententscheidungen zur Bewätligung von kürzer werdenden Reaktionszeiten. Sie werden begrifflich eingeordnet und entsprechend im fortschreitenden Entwicklungsprozeß der Informations- und Kommunikationstechnologien positioniert. Zur Konzeption von Führungsinformationssystemen werden mittels eines Vorgehensmodells verschiedene Aspekte herausgearbeitet, die schließlich zur Herleitung einer FIS-Architektur verwendet werden. Beispielhaft werden einige FIS-Generatoren, die der Umsetzung der vorgestellten Konzepte dienen können, skizziert.<br

Fachkonzeption von Führungsinformationssystemen:Instanziierung eines FIS-Metamodells am Beispiel eines Einzelhandelsunternehmens

Bei der derzeitigen Diskussion von OLAP und Data Warehouse wird die technische Umsetzung von Führungsinformationssystemen (FIS) in den Mittelpunkt gestellt. Dennoch bleibt der Inhalt, den entsprechende Softwaresysteme transportieren sollen, die entscheidende Qualitätsdeterminante. Deshalb wird hier gezeigt, wie für ein Handelsunternehmen die inhaltliche Komponente seines FIS modelliert wurde. Kapitel 1 erläutert die Motivation des Unternehmens zur Umgestaltung seines FIS. Kapitel 2 führt grundlegende Begriffe zur Beschreibung des Inhalts von FIS ein. In Kapitel 3 wird gezeigt, wie auf Basis dieses Metamodells und im Rahmen eines Ordnungsrahmens ein adressatengerechtes und unternehmensweit konsistentes Fachkonzept für FIS entwickelt werden kann. Das abschließende vierte Kapitel gibt einen Ausblick auf Fragen der technischen Umsetzung des Modells.<br/

Procedure Model for the Analysis and Design of Reporting Systems – A Case Study in Conceptual Modelling

A structured conceptual design of reporting systems is a crucial task that has to precede implementation and monitoring. A basic challenge can be seen in information requirements engineering. On the one hand, users need certain information to successfully accomplish their tasks. On the other hand, it has to be avoided to supply them with too much and potentially irrelevant information. Information requirements engineering has to support the conceptual specification of information requirements. Thus, there is need for conceptual languages and appropriate procedure models. We propose a procedure model for the analysis and conceptual design of reporting systems as well as a conceptual modelling language that can be used for both as-is analysis and to-be modelling. It has been developed in an iterative approach based on multiple case studies. Due to the fact that different projects and different basic conditions require the use of different approaches of information requirements engineering, within the procedure model different approaches can be used. In this paper we introduce both procedure model and conceptual modelling language and present findings of a case study in which they were used

Conceptual Modeling in Law: An Interdisciplinary Research Agenda

The article describes how different approaches from the IS field of conceptual modeling should be transferred to the legal domain to enhance comprehensibility of legal regulations and contracts. It is further described how this in turn would benefit the IS discipline. The findings emphasize the importance of further interdisciplinary research on that topic. A research agenda that synthesizes the presented ideas is proposed based on a framework that structures the research field. Researchers from both disciplines, IS and Law, that are interested in this field should use the research agenda to position their research and to derive new and innovative research questions

Developing Maturity Models for IT Management – A Procedure Model and its Application

Maturity models are valuable instruments for IT managers because they allow the assessment of the current situation of a company as well as the identification of reasonable improvement measures. Over the last few years, more than a hundred maturity models have been developed to support IT management. They address a broad range of different application areas, comprising holistic assessments of IT management as well as appraisals of specific subareas (e. g. Business Process Management, Business Intelligence). The evergrowing number of maturity models indicates a certain degree of arbitrariness concerning their development processes. Especially, this is highlighted by incomplete documentation of methodologies applied for maturity model development. In this paper, we will try to work against this trend by proposing requirements concerning the development of maturity models. A selection of the few well-documented maturity models is compared to these requirements. The results lead us to a generic and consolidated procedure model for the design of maturity models. It provides a manual for the theoretically founded development and evaluation of maturity models. Finally, we will apply this procedure model to the development of the IT Performance Measurement Maturity Model (ITPM3)