Your SlideShare is downloading. ×
09   trends in information modelling
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

09 trends in information modelling


Published on

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Trends in Information ModellingConfigurable Reference Models &ProcessBuilding Blocks
  • 2. Idea: Streamlining Information Modeling
    CostandComplexityReductionthroughConfigurative Reference Modeling
    CostandComplexityReductionthroughProcessBuilding Blocks
  • 3. ConfigurativeReference Modelling
  • 4. Configurative Reference Modeling
    Warehousing & 3rd-Party-Deal
    Warehousing & 3rd-Party-Deal
    Idea: Generating modelvariants automatically
    Starting point:integrated totalmodel
    Dependent onuser‘s requirements
    ConfigurativeReference Modeling
    Non-Skilled Person
    Non-Skilled Person
  • 5. Introduction – Reuse of Information Models
    Reuse of information models implies complying with needs of different user groups
    company-specific user groups
    companies as user groups  “reference models”
    varying requirements
    to be considered within information models
  • 6. Example: Requirements of Different Companies
    Business characteristics (e. g. type of trade business)
  • 7. Example: Requirements of Company Specific User Groups
    Modeling Purpose
    Further Influences
  • 8. Resulting Problems
    Problems: Redundancies
    Increased modeling and maintenance costs
    Danger of Inconsistencies within the model base
  • 9. Solution: Configurative Information Modeling
    Constructionof an integrated total modelthatcontains all perspective-specificinformations
    Model elementsthatare relevant formorethanoneperspectivehavetobemodeledandmaintainedonlyonce
  • 10. Basic Concept: Model Projection
    Specific models for specific perspectives are provided via model projection
    Model elements that are not relevant for a specific perspective are hidden
    Models for specific perspectives are reprensented by viewson the integrated total model
  • 11. Configuration Mechanisms
    Model Type Selection
    Selection of different model types for different perspectives
    (e. g. ERM vs. Technical Term Model)
    Element Type Selection
    Variation of model types for different perspectives
    (e. g. annotation of organizational units in the EPC)
    Element Selection
    Hiding of non relevant, single model elements
    Synonym Management
    Perspective-specific exchange of synonyms
    Representation Variation
    Variation of symbols
    Variation of model topologies
    Representation variation of configuration points
  • 12. Model Layers
    Model that-describessimilaritiesoftheusedmodelinglanguages-allowsmodificationsofthemeta model language-isusedtospecifyconfigurationmechanisms
    Models oftheusedmodelinglanguage(s)
    Models oftheregardedissue(s)
    Issue(s) tobemodeled
  • 13. E. g. Organizational Design
    Configuration Mechanisms: Model Type Selection
    Model Types: resulttypesof a modelinglanguage:EPC, ERM etc.
    MetaMeta Model Layer:assignmentofperspectivesto model types
    Meta Model Layer: Language specificationsof non selected model typesdisappear
    Model Layer: Modeling with „forbidden“ languagesisnolongerpossible
  • 14. Configuration Mechanisms: Element Type Selection
  • 15. Configuration Mechanisms: Element Type Selection
    Meta Meta Model Layer:Reduction of model types by element types
  • 16. Configuration Mechanisms: Element Type Selection
    Meta Model Layer:Element types disappear from the specifications of model types
  • 17. ProcessBuilding Blocks
  • 18. Problem of Governmental Processes
  • 19. Firefighters
    Citizens Office
    Environment Office
    Building Office
    Process in an inter-administrational View
  • 20. Traditional Process Modelling
    Traditional Modelling Approaches:
    Use of generally applicable modelling languages
    Not domain specific (harder to understand)
    High/varying level of detail (not always required)
    High degree of freedom (difficult to analyse)
    Syntactically complex (requires expert knowledge)
    Time consuming
  • 21. Process Building Blocks
  • 22.
  • 23. PICTURE Language Constructs (II)
  • 24. Example for PICTURE Language Constructs
  • 25. Objectives and Challenges
    Objectives of PICTURE
    Get an overview of the whole process landscape of a public body
    Efficient identification and analysis of possible reorganisation activities (organisational and technical)
    Many interdependent processes
    Huge amount of functional process know-how of employees
    Limited time of employees
    Handling and presentation of a huge amount of processes
    Maintenance and reutilisation of existing processes
  • 26. Potential of the Building Block-Based Process Modelling
    Higher comparability of particular types of model elements to present activities
    Increased impact of individual elements on the meaning of the whole model
    If possible: immediate use of domain-specific terminology within the process building blocks to increase the comprehensibility (e.g. “Undertake formal check”)
    Highlighting function for relevant issues (e.g. “Transfer data in computer system”)
    Limiting function for non-relevant issues (e.g. no graphical representation of complex checks of content as it is enclosed in the building block “Check content”)
     Result: Better comparability between models
  • 27. Trends in Information ModellingConfigurable Reference Models &ProcessBuilding Blocks