Object Oriented Information Modelling
INTRODUCTION
The object oriented information modeling started in the early 1960’s, but at the time it was not very popular. It is only recently that object oriented programming has become popular. It was designed for the purposes of creating simulations and was developed by Kristen Nygaard and Ole-Johan Dahl in Norway. The term “object oriented information modeling” was first used by Xerox PARC in their Smalltalk programming language. The term was used to refer to the process of using the objects as the foundation for computation. The object could be changed, created, or deleted and this was different from the static systems that were commonly used.
Object oriented information modeling is part of creators that make as awesome results in knowledge findings. It is an explicit and systematic process of managing vital knowledge and fits associated processes of creating, gathering, analyzing, organizing and exploitation to create the implication of the program. It was using an object that is data structure consisting of data fields and methods together with their interactions that to design application and computer programs. They are two types in object oriented information that are business items and data items. Business objects represent parts or parts assemblies. Business object attributes include its name and revision.
This object oriented also applying knowledge continuum that firstly using a product data management system to allow data managers and engineers build a product structure. All the information they gain such as component’s drawings and documents are kept up to date as the objects representing each components. Data items are describe by Metadata. As a research been made by increasing of knowledge, Metadata is separate from the data files so when the possibility of the wrong data file being associated still it permits data files to be reused. After that by creating a new drawing number creates a new business object to which a
The object oriented information modeling started in the early 1960’s, but at the time it was not very popular. It is only recently that object oriented programming has become popular. It was designed for the purposes of creating simulations and was developed by Kristen Nygaard and Ole-Johan Dahl in Norway. The term “object oriented information modeling” was first used by Xerox PARC in their Smalltalk programming language. The term was used to refer to the process of using the objects as the foundation for computation. The object could be changed, created, or deleted and this was different from the static systems that were commonly used.
Object oriented information modeling is part of creators that make as awesome results in knowledge findings. It is an explicit and systematic process of managing vital knowledge and fits associated processes of creating, gathering, analyzing, organizing and exploitation to create the implication of the program. It was using an object that is data structure consisting of data fields and methods together with their interactions that to design application and computer programs. They are two types in object oriented information that are business items and data items. Business objects represent parts or parts assemblies. Business object attributes include its name and revision.
This object oriented also applying knowledge continuum that firstly using a product data management system to allow data managers and engineers build a product structure. All the information they gain such as component’s drawings and documents are kept up to date as the objects representing each components. Data items are describe by Metadata. As a research been made by increasing of knowledge, Metadata is separate from the data files so when the possibility of the wrong data file being associated still it permits data files to be reused. After that by creating a new drawing number creates a new business object to which a
References: Frost, A. (2010). Knowledge Management System. Retrieved June. 6, 2012, from the World Wide Web: http://www.knowledge-management-tools.net/knowledge-management-systems.html Engels, G. & Groenewegen, L. (2000). Object-Oriented Modeling: A Roadmap. Department of Computer Science. Finkelstein, A. (2000). The Future of Software Engineering. ACM Press. Gazis, B. Generic object-oriented information models for reconfigurable communication subsystems in beyond 3G mobile systems. Department of Informatics and Telecommunications. Tamara, W. (2005). Object Oriented Information Models and Product Data Management. Retrieved June. 6, 2012, from the World Wide Web: http://tamarawilhite.hubpages.com/hub/The-object-oriented-information-model-and-its-components Pillay, A. (2007). Object Oriented Programming using Java. School of Computer Science. (5)1-221. (2006). Object Oriented Programming Issues. Retrieved June. 6, 2012, from the World Wide Web: http://www.exforsys.com/tutorials/oops/object-oriented-programming-issues.html