ENTERPRISE MODELING:MODELING TOOLS
MODELING TOOLS
Benefits of Computerized Enterprise Modeling
Modeling tools are computerized instruments used to support the application of modeling methods. Support in designing enterprise models through the use of computerized tools can play a crucial role in increasing the efficiency of the development process. The general benefits of computer support are:
• All relevant information is entered in a structured, easy-to-analyze form, ensuring uniform, complete documentation. The incorporation of a user-friendly graphical interface offers a com- fortable means of creating and modifying the necessary diagrams. Changes in one part of the documentation are automatically updated in other locations and thus need only be performed once.
• Referencing stored design to its creation date enables the different versions to be managed in a comfortable fashion. Versions are overwritten only if the user expressly wishes it; otherwise, each modification is maintained as an independent version.
• The use of a tool facilitates conformance to a fixed procedural model. Consistency checks ensure that modeling activities are not permitted until the preceding level has been completely pro- cessed.
• The internal consistency of the draft model can be validated by using rule-based systems. The general system requirements must also be entered within the framework of tool application in order to ensure external consistency. This necessitates the use of a powerful tool that provides structured support for the entire life cycle.
• Generation algorithms enable graphical representations to be derived from existing database structures. Likewise, the graphical tool interface enables the information objects to be catego- rized in a meaningful, content-related manner. However, since the aim of providing application- oriented data structuring is again based on content-related perspectives, it would be difficult for a tool to provide further support. In particular, reclassifying basic information units such as attributes into information objects that are more meaningful from a subject-oriented perspective is the virtual equivalent of redesigning the model.
Characterization of Modeling Tools
We can distinguish different groups of tools for enterprise modeling (see Figure 23). In relation to the different tasks of enterprise modeling, each group shows its special support profile.
The first group that can be seen as modeling tools in a broader sense are programming environ- ments. Programming environments such as Borland JBuilder and Symantec Visual Cafe´ for Java clearly emphasize the phase of implementation description. They describe a business process by the language of the software application that is used to support the process performance. In few cases, programming languages provide limited features for design specification.
CASE tools such as ADW, on the other hand, support a specific design methodology by offering data models and function models (e.g., the entity relationship method (ERM) and structured analysis and design technique [SADT]). Their metastructure has to reflect this methodology. Thus, they au- tomatically provide an information model for the repository functionality of this system. Because CASE tools cannot really claim to offer a complete repository, they are also called encyclopedias.
In contrast, drawing tools such as VISIO and ABC FlowCharter support the phases of documen- tation and, to a certain extent, analysis of business structures and processes. The emphasis is on the graphical representation of enterprises in order to better understand their structures and behavior. In most of the cases, drawing tools do not provide an integrated meta model, that is, repository. Con- sequently, drawing tools cannot provide database features such as animating and simulating process models, analyzing process times, and calculating process costs.
Business process improvement (BPI) frameworks such as ARIS offer a broader set of modeling methods, which are described together in one consistent metamodel. As a result, each model is stored in the framework’s repository and thus can be retrieved, analyzed, and manipulated and the model history can be administered (see Section 4.1).
The last group encompasses standard software systems, such as enterprise resource planning (ERP) systems like those from SAP, Baan, or Oracle. ERP systems offer greater flexibility with respect to customization, provide support for data management, and include functionality for creating and managing a (sub)repository. The main weakness is in active analysis of business structures—that is, ERP tools typically do not offer tools for simulation process alternatives.
Because all the modeling tools presented focus on different aspects, none of the systems is suitable for handling the entire systems development process. However, ERP systems are opening up more and more to the modeling and analysis level, endeavoring to support the whole system life cycle.
The integration between ARIS and SAP R / 3, for example, demonstrates seamless tool support from the documentation to the implementation phase. In an excerpt from the SAP R / 3 reference model, Figure 24 shows a customizing example with the ARIS Toolset. For clarification purposes, the four windows are shown separately. In a real-world application, these windows would be displayed on one screen, providing the user with all the information at once.
The upper-right window shows an excerpt from the business process model in the ARIS modeling tool, illustrating the part of the standard software process that can be hidden. An additional process branch, not contained in the standard software, must be added.
The function ‘‘create inquiry’’ asks users which screen is being used in SAP R / 3. Using the process model as a modeling tool and by clicking on the function (or starting a command), users can seamlessly invoke SAP R / 3. This screen is shown at the bottom left.
The Implementation Management Guide (IMG) customizing tool is activated for customizing the function. In the upper-left hand window, it depicts the function parameters that are available.
With the modeling tool, results of discussions, parameter decisions, unresolved issues, and the like are stored in the function, as depicted in the bottom-right window. This enables detailed docu- mentation of business and IT-specific business process engineering. This documentation can be used at a later point in time for clarifying questions, using this knowhow for follow-up projects, and monitoring the project.
Comments
Post a Comment