Summary: Architecture And Modelling Of Management Information Systems

Read the summary and the most important questions on Architecture and Modelling of Management Information Systems

• 1 Introduction to Enterprise modelling

  This is a preview. There are 3 more flashcards available for chapter 1
  Show more cards here

• What is enterprise engineering?

  Goal = ensuring coherence & consistency and manageability
  
  Foundations
  - philosophical theories
  - ontological theories
  - ideological theories
  - technological theories
  - methodology

• What does modelling for requirements engineering contribute to?

  - Content: obliges one to gather requirements, and obtain clarifications to ensure correct translation to models
  - Agreement: obliges the stakeholders to agree on a common understanding of business concepts and business rules
  - Documentation: provides a semi formal notation for requirements and specifications
  
  Beware: not all requirements are captured by models (non functional, business rules, etc)

• 2 From Demand to Supply

  This is a preview. There are 5 more flashcards available for chapter 2
  Show more cards here

• What are the pros of enterprise modelling?

  Through Enterprise modeling we disentangle the user requirements. Exactly defines what the problems are, in order to find lasting future proof solutions. 
  
  Creates a common language
  - allows long term plan
  - avoids fragmentation
  - facilitates alignment
  
  Seperation of DEMAND and SUPPLY

• What are the steps of Req gathering and engineering

  Gathering = Top Down
  - interview, find processes, use casses, objects & rules
  
  Engineering = Bottem up (with MERODE)
  - First define domain model, second find services, third create business process model
  
  Layering helps for better synergies. Benefit of higher modularity and resulting flexibility. Better insight in the costs. Facilitates the development of a product line

• What is the Semiotic triangle?

  Referent: existing or conceived object
  Symbol: an atomic construct of language
  Reference: the image a person has in mind about the referent and symbol

• How is quality guaranteed in MERODE?

  - Class Diagram
  - Finite State Charts
  - Proprietary modelling of Interaction
  - Has a mathematical foundation which allows for consistency checking
  - Cross diagram consistency checking contributes to better syntactic quality, but also significantly more to semantic quality compared to default UML ools 
  - Content is more concrete and complete and documentation is more formal. Creating consolidated views

• What modelling languages are discussed?

  - Extended Entity Relationship Modelling: used in database management
  - Class diagram: part of UML. Originates from objected oriented programming. Can be used to represent data aspect of classes 
  - UML: not very good at assisting model quality. Is purely textual.

• 3 Merode Overview

  This is a preview. There are 7 more flashcards available for chapter 3
  Show more cards here

• What are the 3 modelling phases?

  Domain Modelling Phase
  - identification of business object types and business event types
  - specification of sequence constraints
  - specification of attributes and methods
  - construction EDG and OET
  
  IS Service Modelling Phase
  - identifcation of required information services
  - identification of information object typed
  
  Business Process Modelling Phase
  - identification of business processes
  - BPM

• What are the road map signs?

  Domain modelling: blue
  IS service modelling: yellow
  BP modelling: green
  MDE & Transformations: brown toolbox

• What are the 3 domain model views?

  EDG (existence dependency graph)
  - is a class diagram, refinement of UML
  - is a dependency graph
  
  OET (object event table)
  - is a CRUD matrix (create, read, update, delete)
  
  FSM (Finite State Machines)
  - state diagram