chap002 - Chapter 2 Representation and Patterns: An...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 2 Representation and Patterns: An Introduction to the REA Enterprise Ontology Review Questions R1. What is a model? Why do we create models of systems? The chapter is based on the concept of modeling a system before you build and implement it. The chapter discusses modeling approaches, thus it is important to think about what a model is and how it benefits you in building systems. A model is a pattern or scaled object that represents some existing object. Modeling a system before building allows you to better understand the phenomenon you are trying to support with an information system. In our case, those phenomena are business processes, the related information processes, and the decisions associated with them. You can use your model as a blueprint or roadmap for developing the actual system. Modeling is wonderful if you choose the proper phenomenon to model and if your model is well constructed and represents a thorough understanding of the phenomenon. Modeling is not so beneficial if you model the wrong phenomenon or if you model is poorly constructed. R2. What is a business process? Business processes are the activities associated with providing goods and services to customers. Sample business processes include acquiring and paying for various resources (e.g. financing, human skills, materials and supplies, and plant and equipment); converting resources acquired into goods and services for customers; and delivering goods and services to customers and collecting payment. Just like a play that is comprised of four separate acts, business processes are comprised of a discrete, related series of business events that management wants to plan, execute (control), and evaluate. Thus the term business process implies a group of business events. R3. Is it better to make one model of an entire organization or several smaller models of individual processes? Organizations are complex entities. Thus, when you are developing a model of an organization, initially trying to develop one model would prove difficult and overwhelming. It is less burdensome if you divide the organization into manageable chunks, taking care to incorporate an understanding of how the chunks relate, then merge or synthesize the pieces later. 16 Solutions Manual to accompany Dunn, Enterprise Information Systems: A Pattern Based Approach, 3e
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 2 R4. What is the difference between token and type level representation? The difference is in the level of aggregation in the representation. A token is an individual instance of something, thus token level representation includes a separate representation for each individual instance. A type is a category of instances that have something in common with each other, thus type level
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 6

chap002 - Chapter 2 Representation and Patterns: An...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online