5 Stage modeling of information systems The main Idea is to use modeling systematically to form a 5-layer datamodel.

The information layers needed in this would be as following: High-level of structure Process level Business Intelligence (BI) level Reporting level Data models

More information about the levels would be defined in separate topics - Basic High-level structure of the Information system - Advanced usages of the information system with more details of the separate systems - Processes defined from the business needs perspective - Processes opened more widely using per business process workflows - Business intelligence among intenal systems and using the workflows of the separate systems defined earlier - Business processes in the integrations within internal separate systems - Integrations and their need for business intelligent when making desicicions and error control - Reporting level in the basic level using the management needs - Reporting in the workflow and daily work within the different user roles in the system - Data models defined using the logical connections and the reference information - Data models in attribute level with the information of their datatypes and GUI appearance information What is still needed for this modeling to work in practise: - We need to define the common tools needed to model each level in detail and in a practical form which can be easily modified and re-defined. - We need a clear process to collect the correct information from the customers and undestandment of their current and future needs. We need to have growth path for the system, since business is never still. There is always a way to do thing more efficiently or more practical. - There has to be way to educate the information cathering and the processes for the consultants - The customers need a understandable view of the information defined, so that they can verify the correctness it. - Future plans should be included in the plans so that the customer can have vision of the possible strategy which we are going to use to get to where we are going with the Information system. - We need to define how we can re-use the models created for different customers and for their processes, so that we can start creating a best-practise DB for the information. Best practise models are usually forgotten since many of us think that information differ from one customer to another. The reason for this is usually different ways used in the past for the same processes, or ways of doing things. - The tools used should be more agile and have possibility to create add-ons, so that when a new tool is needed to understand a new system this could be attached. Thougths about the current ways of modeling Information Systems. - First to point out is that the tools used are not really practical or user friendly when you want to change a advanced model or some of its basic workflows. There is no linkage between the information.

- Most of the modeling tools have been defines for software coding needs and there for lack the most basic business intelligent definitions. - The tools used nowdays consist of different UML, Powerpoint, Excel, Eclipse, Visio tools and some more OSS based software tools or add-ons. These softwar tools can be really complicated to use for the people who dont use them on daily base. Some of them can not produce simple outputs for to print out to the customer. There is always some other tools needed for this. There should be a few step process to extract the information for the customers. The re-use of the previous data models should also be taken into consideration. - The tools used should be more agile and have possibility to create add-ons, so that when a new tool is needed to understand a new system this could be attached. Thoughts about the needs for this kind of modeling - When working with agile process consulting, software modeling, integration development projects or with a new business oportunity. We need to know the fallbacks, pros and cons of the possible new system. The information collection and modeling process should still be so agile that the business can be modeled fully within weeks or months. Like using virtual building blocks of known processes, BI ways, reports and data models. These are specially practical when these are similar among clients. Like most of the business supporting processes which are usually similar within companies in the private, public and global sectors. - There is usually information over-flow when it comes to f.ex SAP projects, this is because of the massive amount of information needed to undestand even the fines levels of the information which is flowing thru the companies processes and infomation system. All this basic level information is required to understad the needs for the worker. In the higher levels of the companys or a public secror office the management requirements can usually be totally different from the actual need when it comes to the products or services which the company is offering. This is because management need information of how the company is performing and its efficiency.