Traditional technology modeling approaches concentrated primarily on two kinds of systems viz. data and process modeling. Traditionally these two approaches were kept distinct from each other (Haag, Baltzan, & Phillips, 2006). Object-oriented modeling is a more recent method of designing or modeling business information systems (IS). In this paper, we discuss the three different approaches to IS and trace their differences. This paper also tries to analyze which modeling style is a better approach to manage and design IS i.e. data and process modeling and/or object-oriented modeling.
In order to embark on a discussion that evaluates the different modeling styles, it is essential to understand what these models actually mean and how they are made and used. The first part of the essay deals with interpreting the three models and then we do comparative pros and con analysis in order to understand which is a more effective and viable model.
Data is the key characteristic stored in a system. A data modeling theory establishes a system that stores customer information, the key characteristics to be included in such as system are name, phone number, etc. (Haag et al. 2006). The data model includes all the information stored within a system. To manage a large quantity of “structured or unstructured” data is the main function of IS used in businesses. The purpose of data models is to describe the storage of structured data in a data management system such as relational databases. This illustrates the movement of information or data between external entities and the processes and data stores within the system.
A process modeling involves a graphical representation of the processes that capture, manipulate, store, and distribute information between a system and its environment. Process and data modeling flow diagrams establish the specifications of the system (Haag et al., 2006). The computer-sided software engineering (CASE) tools are software suites that automatic system analysis, design, and development. Process modeling and data flow diagrams provide the basis for automatic generation of the system if they are developed using the CASE tool. Process modeling is an important and commonly used approach within software engineering in developing information systems for managing a business, which emphasizes on separation of the overall software development task into a series of dedicated subtasks (Haag et al. 2006).
Object-oriented modeling is a process that is used to combine data and processes into a single view. This has become a widely used and accepted system in use for IS modeling. The idea is formed in two ways:
- First, it extracts details from real situations which are not relevant for the development and usage of the new IS.
- Second, ideas are also derived from the implementation process of the IS and hence an implementation planning is done prior to the process of implementation of the IS.
These two methods are followed to form the Entity-Relationship diagrams (Chen, 1976) which are used to model the data aspect of a system, and then data flow diagrams or functional decomposition techniques are used to model the functional, behavioral aspect of the IS.
The limitations of an object-oriented system are that there is a lack of horizontal homogeny between the data used and the behavioral part of the IS within the overall system model. Further, there is an observed vertical mismatch of concepts between the exterior real-world domain and the model which affects the implementation of the model in reality.
Even with the above limitation, the object-oriented method is a better model for IS modeling because they provide a combined view and model to utilize the data in-store and apply them to the relevant process. In the earlier method, there was a disparity in the usage of data and processes and they could not be modeled in a single diagram, which had to be dealt with separately. This primary problem of data and process modeling is removed while using object-oriented modeling.
Presently, object-oriented modeling has become the standard approach throughout the IS development process. Object-oriented languages like C++ or Java have become the essential standard for systems programming. The usage of this type of modeling is also widely used in the analysis and design phases in an IS development process.
Priory there used to be a problem of standardization of object-oriented modeling due to numerous models available. The validity of the models was difficult which led to the so-called “method war” in the 90s. This led to the development of a standardized object-oriented modeling language UML (Unified Modeling Language) (Booch, Rumbaugh, & Jacobson, 1999). But even though the standardization of the modeling has been done, there still exists the horizontal and vertical inconsistencies as discussed above:
- UML in its current form is not real world-specific, i.e., domain-specific. This is so because UML is developed for general-purpose modeling of IS.
- Certain sections of the syntax which are context-sensitive have not been defined properly. This leads to several different interpretations of the UML.
- Apart from the above problems, there are still ambiguity and debate regarding the implementation of the UML model. (Booch et al. 1999)
Clearly, object-oriented modeling is a better approach to IS modeling. But there are still certain problems in using object-oriented modeling for specific purposes and there are existing implementation problems with the model. But being a more recent model it did away with the prevalent problems of data and process models. The above discussion shows that the object-oriented method of modeling is a more useful tool for modeling.
Works Cited
Booch, G., Rumbaugh, J., & Jacobson, I. (1999). The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley.
Chen, P. (1976). The Entity-Relationship Model – Toward a Unified View of Data. ACM Transactions on Database Systems, 1(1), 9-36.
Haag, S., Baltzan, P., Phillips, A. (2006). Business Driven Technology (2nd Eds.). New York: MaGraw-Hill.