BB_Learning unit 3__xid-125860_1.pdf

BB_Learning unit 3__xid-125860_1.pdf - Learning Unit 3...

This preview shows 1 out of 2 pages.

Learning Unit 3 Represention and modeling You may be wondering why representation and modelling are important for understanding enterprise information systems. The general answer to this question is that we can’t understand enterprise information systems without models that serve as representations of the systems and their underlying reality. The systems are too large and complex for most people to comprehend in their entirety. The creation and use of models to help build and understand complex things in life is common. Engineers who build automobiles create models before they create the real cars. Automotive repair persons use models to help them understand the cars on which they work. Architects create models of the buildings they design; Once the building is built, other users may need to refer to the model to understand some aspect of the building (such as where the support beams are located). To design and understand enterprise information systems, we must be able to develop and understand representations (models) of the enterprise’s reality. Representations are surrogates for the real constructs; in other words, they are symbols of those constructs. To design an information system that closely resembles the underlying reality of the enterprise about which the information is stored, we must build a set of symbols that represent that reality. In modeling enterprise systems, our symbol representations must not only map as directly as possible to the underlying reality but they must also be convertible into a computerized format. In the case of designing enterprise databases, that means we must be able to create paper-based representations of the enterprise reality and then convert the paper models into a format compatible with a database software package. Representations (models) may be created at different levels of abstraction. More specificall y, a representation may symbolize individual objects or categories of objects, In database design, individual objects are sometimes referred to as tokens, and categories of objects are known as types. For example, see the picture below:
Image of page 1

Subscribe to view the full document.

Image of page 2
You've reached the end of this preview.
  • Spring '18
  • Kimbu
  • Ontology, Business process modeling

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern