JobAid ARIS Method Manual

ARIS Method
November 2003
All rights reserved. Reproduction of this documentation in full or in part only by prior authorization of IDS Scheer AG. Subject to change. The mention of product names is not a guarantee of usability. Copyright (C) 1997 2003 by IDS Scheer AG, Saarbrcken
Contents
Contents
ARIS Method
1 2 Introduction......................................................................................... 1-1 Architecture of integrated Information Systems (ARIS) .............................. 2-1 2.1 2.2 2.3 3 3.1 3.2 4 4.1 Concept of the ARIS Architecture ..................................................... 2-1 Descriptive Views .......................................................................... 2-2 Descriptive Levels.......................................................................... 2-7 Description of Business Problems ..................................................... 3-1 Process Chain Diagrams (PCDs) ....................................................... 3-2 Function View ............................................................................... 4-1 4.1.1 Requirements Definition......................................................... 4-1 4.1.1.1 4.1.1.2 4.1.1.3 4.1.1.4 4.1.2 4.1.3 4.2 4.2.1 Function Tree ............................................................ 4-2 Y Diagram ................................................................. 4-7 SAP Applications Diagram............................................ 4-9 Objective Diagram...................................................... 4-9
Process Chain Analysis .......................................................................... 3-1
Modeling within the Views and Levels of the ARIS Concept.......................... 4-1
Design Specification - Application System Type Diagram........... 4-11 Implementation - Application System Diagram ........................ 4-17 Requirements Definition....................................................... 4-22 4.2.1.1 4.2.1.2 The Basic ERM Model ................................................ 4-22 Extending the ERM - eERM......................................... 4-30 4.2.1.2.1 4.2.1.2.2 4.2.1.2.3 4.2.1.2.4 4.2.1.2.5 4.2.1.3 4.2.1.3.1 Extending Using Design Operators.................... 4-30 Extending Cardinalities ................................... 4-37 Identification and Existential Dependence.......... 4-39 Modeling of Technical Terms of the Company - Technical Term Model................................... 4-40 eERM Attribute Allocation Diagram ................... 4-42 SAP SERM .................................................... 4-44
Data View................................................................................... 4-22
Alternative Forms of Representation............................ 4-44
ARIS Methods
Contents
II
4.2.1.3.2 4.2.1.3.3 4.2.1.4 4.2.1.5
IE Data model ............................................... 4-47 SeDaM model................................................ 4-48
Summary of the Most Important Concepts and Forms of Representation of the eERM ................................... 4-49 Document Type Definition ......................................... 4-51 4.2.1.5.1 4.2.1.5.2 4.2.1.5.3 Element Types .............................................. 4-51 Connection Types .......................................... 4-53 Attribute Types ............................................. 4-54 Data Type of the Attribute Value ............. 4-55 Attribute Default ................................... 4-56
4.2.1.5.3.1 4.2.1.5.3.2 4.2.1.5.4 4.2.1.6 4.2.1.7 4.2.1.8 4.2.1.9
Testing DTDs ................................................ 4-60
Material Flow Modeling - Material Diagram ................... 4-61 Modeling the Data Warehouse Structure ...................... 4-62 Authorization Hierarchy............................................. 4-63 Activity-Based Cost Calculation Data Model .................. 4-64 4.2.1.9.1 4.2.1.9.2 CD Diagram .................................................. 4-64 Cost Category Diagram................................... 4-66 Information Carrier Diagram ........................... 4-68
4.2.1.10 4.2.2
Project Management Data Model................................. 4-68
4.2.1.10.1 4.2.2.1 4.2.2.2 4.2.3 4.3 4.3.1
Design Specification ............................................................ 4-69 Relations Diagram, Attribute Allocation Diagram ........... 4-69 Modeling of System Interface Models - System Attributes, System Attribute Domains.......................... 4-73
Implementation - Table Diagram........................................... 4-75 Requirements Definition....................................................... 4-79 4.3.1.1 4.3.1.2 4.3.1.3 Organizational Form of the Company........................... 4-79 Organizational Chart ................................................. 4-82 Shift Calendar.......................................................... 4-88
Organization View........................................................................ 4-79
4.3.2 4.3.3
Design Specification - Network Topology ................................ 4-91 Implementation .................................................................. 4-94
ARIS Methods
Contents
III
4.3.3.1 4.3.3.2 4.4 4.4.1
Network Diagram ..................................................... 4-94 Material Flow Modeling - Technical Resources ............... 4-96
Process View/Control View .......................................................... 4-100 Requirements Definition..................................................... 4-100 4.4.1.1 4.4.1.2 Combining Functions with Organization - eEPC, Function/Organizational Level Diagram...................... 4-100 Combining Functions with Data ................................ 4-102 4.4.1.2.1 4.4.1.2.2 4.4.1.2.3 4.4.1.2.4 4.4.1.3 4.4.1.3.1 4.4.1.3.2 4.4.1.3.3 4.4.1.3.4 4.4.1.3.5 4.4.1.3.6 4.4.1.4 4.4.1.5 4.4.1.6 4.4.1.4.1 4.4.1.5.1 4.4.1.6.1 4.4.1.6.2 4.4.1.6.3 4.4.1.7 4.4.1.7.1 4.4.1.7.2 4.4.1.7.3 4.4.1.8 Event Control - Event-Driven Process Chain (EPC) ......................................................... 4-102 Function Allocation Diagram (I/O) .................. 4-112 Information Flow Diagrams ........................... 4-117 Event Diagram ............................................ 4-118 eEPC/PCD................................................... 4-119 Value added chain diagram ........................... 4-122 Rule Diagram .............................................. 4-123 Communications Diagram ............................. 4-124 Classification Diagram .................................. 4-124 Input/Output Diagram .................................. 4-125 Class Diagram ............................................. 4-126 Process selection matrix ............................... 4-128 eEPC (material flow) .................................... 4-130 Material Flow Diagram .................................. 4-132 eEPC (Column/Row Display) .......................... 4-132 SAP ALE Filter model .................................... 4-134 SAP ALE Message Flow Model ........................ 4-134 SAP ALE Message Type Model ........................ 4-134
Functions - Organization - Data ................................ 4-119
Object-oriented Modeling ........................................ 4-126 Process Variants..................................................... 4-128 Material Flow Modeling ............................................ 4-130
SAP ALE Models ..................................................... 4-134
Role Allocation Diagram (RAD) ................................. 4-134
ARIS Methods
Contents
IV
4.4.1.9
Other Models ......................................................... 4-136 4.4.1.9.1 4.4.1.9.2 4.4.1.9.3 4.4.1.9.4 4.4.1.9.5 4.4.1.9.6 4.4.1.9.7 4.4.1.9.8 4.4.1.9.9 4.4.1.9.10 4.4.1.9.11 4.4.1.9.12 4.4.1.9.13 Business Controls Diagram............................ 4-136 Data Warehouse Transformation .................... 4-137 E-Business Scenario Diagram ........................ 4-138 Structuring model ........................................ 4-142 Industrial Process and Office Process .............. 4-142 Project Process Chain (PPC) .......................... 4-147 Process instantiation model ........................... 4-149 RAMS......................................................... 4-151 Role Diagram .............................................. 4-153 Quick Model ................................................ 4-156 c3 Method .................................................. 4-156 Screen Design ............................................. 4-158 Screen Navigation........................................ 4-160
4.4.2
Design Specification .......................................................... 4-162 4.4.2.1 Access Diagram ..................................................... 4-162 4.4.2.1.1 4.4.2.1.2 4.4.2.1.3 4.4.2.2 4.4.2.3 4.4.2.4 Combining Functions with Data...................... 4-162 Combining Organization with Data ................. 4-163 Combining Organization with Function ............ 4-165
Program Structure Diagram ..................................... 4-167 Program Flow Chart (PF) ......................................... 4-168 Screen Diagram ..................................................... 4-169 Combining Functions with Data ................................ 4-172 Combining Organization with Data ............................ 4-175 Combining Organization With Functions ..................... 4-177
4.4.3
Implementation - Access Diagram (physical)........................ 4-172 4.4.3.1 4.4.3.2 4.4.3.3
4.5
Product/Service Modeling............................................................ 4-180 4.5.1 4.5.2 4.5.3 4.5.4 Product/Service Exchange Diagram ..................................... 4-181 Product/Service Tree ......................................................... 4-183 Product Allocation Diagram ................................................ 4-185 Product Tree .................................................................... 4-188
ARIS Methods
Contents
4.5.5 4.5.6 5 5.1 5.2
Product Selection Matrix .................................................... 4-189 Competition Model ............................................................ 4-190
Unified Modeling Language in ARIS ......................................................... 5-1 Introduction.................................................................................. 5-1 The UML Models ............................................................................ 5-2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.3 5.3.1 5.3.2 UML Class Diagram ............................................................... 5-2 UML Class Description Diagram ............................................... 5-5 UML Use Case Diagram.......................................................... 5-5 UML Activity diagram............................................................. 5-7 UML Statechart Diagram ...................................................... 5-10 UML Collaboration Diagram .................................................. 5-11 UML Component Diagram..................................................... 5-13 Fundamental Relationships between Models............................ 5-15 Relationships between UML Models ........................................ 5-19 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.2.5 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 5.3.3.4 5.3.3.5 5.3.3.6 UML Class Diagram and UML Class Description Diagram ................................................................. 5-19 UML Class Diagram and UML Activity Diagram .............. 5-19 UML Class Diagram and UML Statechart Diagram .......... 5-20 UML Class Diagram and UML Collaboration Diagram ...... 5-20 UML Use Case Diagram ............................................. 5-20 UML Class Diagram and eEPC..................................... 5-21 UML Statechart Diagram and eEPC.............................. 5-22 UML Use Case Diagram and eEPC ............................... 5-22 UML Activity Diagram and eEPC.................................. 5-22 UML Class Diagram and eERM .................................... 5-23 UML Use Case Diagram and eEPC ............................... 5-23
Integrating UML Diagrams and Other ARIS Models............................ 5-15
Relationships to Other ARIS Models ....................................... 5-21
Using the Object Modeling Technique (OMT) Modeling Method ..................... 6-1 6.1 6.2 Introduction.................................................................................. 6-1 Summary of the OMT Methodology................................................... 6-1
ARIS Methods
Contents
VI
6.3
Using the OMT Diagram Technique in ARIS........................................ 6-2 6.3.1 6.3.2 6.3.3 6.3.4 OMT Object Model................................................................. 6-2 OMT Dynamic Model............................................................ 6-11 OMT Functional Model.......................................................... 6-14 How Objects Can Be Arranged in a Hierarchy .......................... 6-17
Methods for Knowledge Management....................................................... 7-1 7.1 7.2 Introduction.................................................................................. 7-1 Object Types for Modeling Knowledge Processing ............................... 7-2 7.2.1 7.2.2 7.3 7.3.1 7.3.2 7.3.3 Knowledge Category ............................................................. 7-2 Documented Knowledge ........................................................ 7-4 Knowledge Structure Diagram ................................................ 7-6 Knowledge Map .................................................................... 7-7 Representation of Knowledge Processing in Business Processes .......................................................................... 7-10
Model Types for Modeling Knowledge Processing ................................ 7-6
Examples of Applications ....................................................................... 8-1 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 General Company Documentation .................................................... 8-5 Database Management/Data Warehousing ........................................ 8-6 Groupware ................................................................................... 8-7 PC Hardware and Network Management............................................ 8-8 Activity-Based Cost Calculation ........................................................ 8-9 Quality Management .................................................................... 8-10 Reorganization Measures .............................................................. 8-11 SAP R/3 Introduction.................................................................... 8-12 Software Development and Introduction ......................................... 8-13 Knowledge Management ............................................................... 8-14 Workflow Management ................................................................. 8-15 Introduction.................................................................................. 9-1 The Balanced Scorecard Concept ..................................................... 9-1 9.2.1 Key Elements of the BSC Approach.......................................... 9-1
Balanced Scorecard Method.................................................................... 9-1 9.1 9.2
ARIS Methods
Contents
VII
9.2.2
Strategic Management Process and Balanced Scorecard ............. 9-3 9.2.2.1 Formulation and Translation of Vision and Strategy ......... 9-4 9.2.2.1.1 9.2.2.1.2 9.2.2.1.3 9.2.2.2 9.2.2.3 9.2.2.4 The Standard Perspectives of a Balanced Scorecard ....................................................... 9-5 The Cause-and-Effect Chain .............................. 9-6 Defining Leading and Lagging Indicators ............. 9-7
Communication and Derivation of Further Scorecards ...... 9-8 Planning and Guidelines .............................................. 9-8 Strategic Learning and Feedback .................................. 9-9
9.2.3 9.3 9.3.1 9.3.2
Advantages and Uses of the Balanced Scorecard ....................... 9-9 Terms and Abbreviations ..................................................... 9-11 Construction of the Balanced Scorecards with ARIS BSC ........... 9-13 9.3.2.1 9.3.2.2 9.3.2.3 9.3.2.4 9.3.2.5 Establishing Perspectives........................................... 9-13 Establishing the Structure of the Balanced Scorecard System ................................................................... 9-13 Establishing Cause-and-Effect Relationships ................. 9-14 Establishing Initiatives and Key Performance Indicators to Monitor Objectives ................................. 9-16 Describing Key Performance Indicators and Their relationships............................................................ 9-23
Development of a Balanced Scorecard with ARIS BSC ....................... 9-11
9.3.3 10.1 10.2
Relationship to Other Models ................................................ 9-24
10 eBusiness Scenario Diagram................................................................. 10-1 Introduction................................................................................ 10-1 The Method of the E-Business Scenario Diagrams............................. 10-3 The Idea............................................................................ 10-3 The Model and its Objects .................................................... 10-3 Transmission Type Attribute Group........................................ 10-6 Checking Data Security........................................................ 10-6 System Support.................................................................. 10-7 Information Flow ................................................................ 10-7
10.2.1 10.2.2 10.2.3 10.3 10.3.1 10.3.2 10.3.3
Evaluations Using Reports............................................................. 10-6
ARIS Methods
Contents
VIII
10.3.4 10.4 11.1 11.2 11.3 11.4 11.5 11.6 11.7 11.8 11.9
Collaborative Business Maps ................................................. 10-7
Connecting to Other Methods and Components ................................ 10-8 What Will New, Successful Corporate Architectures Have to Look Like?.......................................................................................... 11-2 Organizational Requirements of IT Projects...................................... 11-3 Technological Requirements .......................................................... 11-3 Enterprise Architecture and IT City Planning .................................... 11-3 Which Companies Could Benefit from IT City Planning? ..................... 11-4 IT City Planning with ARIS ............................................................ 11-5 The IS View ................................................................................ 11-7 Functional Clusters and their Data................................................ 11-12 Detailed Description of Clusters ................................................... 11-13
11 IT City Planning .................................................................................. 11-1
11.10 The IT View .............................................................................. 11-14 11.11 IT Elements and their Data ......................................................... 11-16 11.12 Detailed Description of IT Elements .............................................. 11-16 11.13 Organizational Aspects ............................................................... 11-17 11.14 Chronological Procedures within the Architecture............................ 11-18 11.15 Possible Evaluations ................................................................... 11-19 11 Appendix ........................................................................................... 11-1 11.1 Model Types - Specific Object Types ............................................... 11-1 Access diagram .................................................................. 11-1 Access diagram (physical) .................................................... 11-2 Application system diagram.................................................. 11-4 Application system type diagram........................................... 11-5 Attribute allocation diagram ................................................. 11-6 Authorization hierarchy........................................................ 11-6 Authorization map .............................................................. 11-6 BSC Cause-and-effect diagram ............................................. 11-7 Business controls diagram.................................................... 11-7 c3 method ......................................................................... 11-8 11.1.1 11.1.2 11.1.3 11.1.4 11.1.5 11.1.6 11.1.7 11.1.8 11.1.9 11.1.10
ARIS Methods
Contents
IX
11.1.11 11.1.12 11.1.13 11.1.14 11.1.15 11.1.16 11.1.17 11.1.18 11.1.19 11.1.20 11.1.21 11.1.22 11.1.23 11.1.24 11.1.25 11.1.26 11.1.27 11.1.28 11.1.29 11.1.30 11.1.31 11.1.32 11.1.33 11.1.34 11.1.35 11.1.36 11.1.37 11.1.38 11.1.39 11.1.40 11.1.41
CD Diagram ....................................................................... 11-8 Class diagram .................................................................... 11-8 Classification diagram.......................................................... 11-9 Communications diagram..................................................... 11-9 Competition model............................................................ 11-10 Cost category diagram....................................................... 11-10 DTD ................................................................................ 11-10 DW - structure ................................................................. 11-11 DW - transformation ......................................................... 11-11 E-Business scenario diagram .............................................. 11-11 eEPC ............................................................................... 11-12 eEPC (column display) ....................................................... 11-14 eEPC (instance) ................................................................ 11-16 eEPC (material flow).......................................................... 11-17 eEPC (row display)............................................................ 11-20 eEPC (table display) .......................................................... 11-22 eERM .............................................................................. 11-24 eERM attribute allocation diagram ....................................... 11-25 Event diagram.................................................................. 11-25 Function allocation diagram ................................................ 11-27 Function allocation diagram (instance) ................................. 11-29 Function tree.................................................................... 11-31 Function/organizational level diagram .................................. 11-31 IE Data model .................................................................. 11-31 Industrial process ............................................................. 11-31 Information carrier diagram ............................................... 11-33 Information flow diagram................................................... 11-33 Input/Output diagram ....................................................... 11-33 Input/Output diagram (inverse) .......................................... 11-34 Key performance indicator allocation diagram ....................... 11-34 Key performance indicator tree ........................................... 11-36
ARIS Methods
Contents
11.1.42 11.1.43 11.1.44 11.1.45 11.1.46 11.1.47 11.1.48 11.1.49 11.1.50 11.1.51 11.1.52 11.1.53 11.1.54 11.1.55 11.1.56 11.1.57 11.1.58 11.1.59 11.1.60 11.1.61 11.1.62 11.1.63 11.1.64 11.1.65 11.1.66 11.1.67 11.1.68 11.1.69 11.1.70 11.1.71 11.1.72
Knowledge map ................................................................ 11-36 Knowledge structure diagram ............................................. 11-37 Material diagram............................................................... 11-37 Material flow diagram ........................................................ 11-38 Network diagram .............................................................. 11-38 Network topology.............................................................. 11-39 Objective diagram............................................................. 11-39 Office process .................................................................. 11-40 OMT Class description model .............................................. 11-41 OMT Data value decomposition ........................................... 11-41 OMT Dynamic model ......................................................... 11-41 OMT Functional model ....................................................... 11-41 OMT Object model ............................................................ 11-42 Organizational chart .......................................................... 11-42 PCD ................................................................................ 11-43 PCD (material flow)........................................................... 11-45 PPC................................................................................. 11-47 Privileges diagram ............................................................ 11-48 Process instantiation model ................................................ 11-49 Process selection diagram .................................................. 11-49 Process selection matrix..................................................... 11-49 Product allocation diagram ................................................. 11-50 Product selection matrix .................................................... 11-51 Product tree ..................................................................... 11-51 Product/Service exchange diagram...................................... 11-51 Product/Service exchange diagram (graphic) ........................ 11-52 Product/Service tree.......................................................... 11-53 Product/Service tree (graphic) ............................................ 11-53 Program flow-chart (PF)..................................................... 11-53 Program structure chart..................................................... 11-54 Quick model..................................................................... 11-56
ARIS Methods
Contents
XI
11.1.73 11.1.74 11.1.75 11.1.76 11.1.77 11.1.78 11.1.79 11.1.80 11.1.81 11.1.82 11.1.83 11.1.84 11.1.85 11.1.86 11.1.87 11.1.88 11.1.89 11.1.90 11.1.91 11.1.92 11.1.93 11.1.94 11.1.95 11.1.96 11.1.97 11.1.98 11.1.99
RAD ................................................................................ 11-56 RAMS.............................................................................. 11-56 Relations diagram ............................................................. 11-56 Role diagram.................................................................... 11-57 Rule diagram ................................................................... 11-57 SAP ALE filter model.......................................................... 11-58 SAP ALE function model ..................................................... 11-58 SAP ALE message flow model ............................................. 11-58 SAP ALE message type model ............................................. 11-58 SAP applications diagram ................................................... 11-58 SAP SERM........................................................................ 11-59 Screen design .................................................................. 11-59 Screen diagram ................................................................ 11-60 Screen navigation ............................................................. 11-61 SeDaM model ................................................................... 11-61 Shift calendar................................................................... 11-62 Structuring model ............................................................. 11-62 System attribute domain.................................................... 11-62 System attributes ............................................................. 11-62 Table diagram .................................................................. 11-63 Technical resources........................................................... 11-63 Technical terms model....................................................... 11-64 UML Activity diagram......................................................... 11-65 UML Class description diagram............................................ 11-66 UML Class diagram............................................................ 11-66 UML Collaboration diagram................................................. 11-68 UML Component diagram ................................................... 11-68
11.1.100 UML Deployment diagram .................................................. 11-69 11.1.101 UML Sequence diagram ..................................................... 11-70 11.1.102 UML Statechart diagram .................................................... 11-71 11.1.103 UML Use case diagram....................................................... 11-71
ARIS Methods
Contents
XII
11.1.104 Value-added chain diagram ................................................ 11-72 11.1.105 Y diagram ........................................................................ 11-73 11.2 Model Types - Specific Connection Types....................................... 11-74 Access diagram ................................................................ 11-74 Access diagram (physical) .................................................11-113 Application system diagram...............................................11-160 Application system type diagram........................................11-165 Attribute allocation diagram ..............................................11-173 Authorization hierarchy.....................................................11-174 Authorization map ...........................................................11-175 BSC Cause-and-effect diagram ..........................................11-176 Business controls diagram.................................................11-179 c3 method ......................................................................11-180 CD Diagram ....................................................................11-187 Class diagram .................................................................11-188 Classification diagram.......................................................11-191 Communications diagram..................................................11-191 Competition model...........................................................11-192 Cost category diagram......................................................11-192 DTD ...............................................................................11-192 DW - structure ................................................................11-196 DW - transformation ........................................................11-197 E-Business scenario diagram .............................................11-197 eEPC ..............................................................................11-199 eEPC (column display) ......................................................11-254 eEPC (instance) ...............................................................11-315 eEPC (material flow).........................................................11-354 eEPC (row display)...........................................................11-420 eEPC (table display) .........................................................11-482 eERM .............................................................................11-544 eERM attribute allocation diagram ......................................11-547 11.2.1 11.2.2 11.2.3 11.2.4 11.2.5 11.2.6 11.2.7 11.2.8 11.2.9 11.2.10 11.2.11 11.2.12 11.2.13 11.2.14 11.2.15 11.2.16 11.2.17 11.2.18 11.2.19 11.2.20 11.2.21 11.2.22 11.2.23 11.2.24 11.2.25 11.2.26 11.2.27 11.2.28
ARIS Methods
Contents
XIII
11.2.29 11.2.30 11.2.31 11.2.32 11.2.33 11.2.34 11.2.35 11.2.36 11.2.37 11.2.38 11.2.39 11.2.40 11.2.41 11.2.42 11.2.43 11.2.44 11.2.45 11.2.46 11.2.47 11.2.48 11.2.49 11.2.50 11.2.51 11.2.52 11.2.53 11.2.54 11.2.55 11.2.56 11.2.57 11.2.58 11.2.59
Event diagram.................................................................11-550 Function allocation diagram ...............................................11-557 Function allocation diagram (instance) ................................11-616 Function tree...................................................................11-665 Function/organizational level diagram .................................11-665 IE Data model .................................................................11-666 Industrial process ............................................................11-668 Information carrier diagram ..............................................11-712 Information flow diagram..................................................11-712 Input/Output diagram ......................................................11-713 Input/Output diagram (inverse) .........................................11-714 Key performance indicator allocation diagram ......................11-716 Key performance indicator tree ..........................................11-732 Knowledge map ...............................................................11-732 Knowledge structure diagram ............................................11-733 Material diagram..............................................................11-735 Material flow diagram .......................................................11-736 Network diagram .............................................................11-737 Network topology.............................................................11-740 Objective diagram............................................................11-744 Office process .................................................................11-745 OMT Class description model .............................................11-784 OMT Data value decomposition ..........................................11-784 OMT Dynamic model ........................................................11-784 OMT Functional model ......................................................11-785 OMT Object model ...........................................................11-786 Organizational chart .........................................................11-789 PCD ...............................................................................11-796 PCD (material flow)..........................................................11-850 PPC................................................................................11-915 Privileges diagram ...........................................................11-916
ARIS Methods
Contents
XIV
11.2.60 11.2.61 11.2.62 11.2.63 11.2.64 11.2.65 11.2.66 11.2.67 11.2.68 11.2.69 11.2.70 11.2.71 11.2.72 11.2.73 11.2.74 11.2.75 11.2.76 11.2.77 11.2.78 11.2.79 11.2.80 11.2.81 11.2.82 11.2.83 11.2.84 11.2.85 11.2.86 11.2.87 11.2.88 11.2.89 11.2.90
Process instantiation model ...............................................11-924 Process selection diagram .................................................11-924 Process selection matrix....................................................11-925 Product allocation diagram ................................................11-925 Product selection matrix ...................................................11-931 Product tree ....................................................................11-931 Product/Service exchange diagram.....................................11-931 Product/Service exchange diagram (graphic) .......................11-941 Product/Service tree.........................................................11-951 Product/Service tree (graphic) ...........................................11-952 Program flow-chart (PF)....................................................11-953 Program structure chart....................................................11-954 Quick model....................................................................11-996 RAD ...............................................................................11-997 RAMS.............................................................................11-997 Relations diagram ............................................................11-998 Role diagram...................................................................11-999 Rule diagram ................................................................ 11-1006 SAP ALE filter model....................................................... 11-1007 SAP ALE function model .................................................. 11-1007 SAP ALE message flow model .......................................... 11-1008 SAP SERM..................................................................... 11-1008 Screen design ............................................................... 11-1010 Screen diagram ............................................................. 11-1017 Screen navigation .......................................................... 11-1022 SeDaM model ................................................................ 11-1025 Shift calendar................................................................ 11-1026 Structuring model .......................................................... 11-1026 System attribute domain................................................. 11-1027 System attributes .......................................................... 11-1027 Table diagram ............................................................... 11-1029
ARIS Methods
Contents
XV
11.2.91 11.2.92 11.2.93 11.2.94 11.2.95 11.2.96 11.2.97 11.2.98 11.2.99
Technical resources........................................................ 11-1031 Technical terms model.................................................... 11-1035 UML Activity diagram...................................................... 11-1036 UML Class description diagram......................................... 11-1049 UML Class diagram......................................................... 11-1053 UML Collaboration diagram.............................................. 11-1110 UML Component diagram ................................................ 11-1113 UML Deployment diagram ............................................... 11-1123 UML Sequence diagram .................................................. 11-1147
11.2.100 UML Statechart diagram ................................................. 11-1150 11.2.101 UML Use case diagram.................................................... 11-1160 11.2.102 Value-added chain diagram ............................................. 11-1178 11.3 ARIS Object Types .................................................................. 11-1182 Object Types ................................................................. 11-1182 Object Type Specific Attribute Types................................. 11-1264 Action................................................................ 11-1264 Activity graph ..................................................... 11-1264 Actor ................................................................. 11-1264 Application system .............................................. 11-1264 Application system class....................................... 11-1265 Application system type ....................................... 11-1265 Argument........................................................... 11-1267 Artifact .............................................................. 11-1267 Association......................................................... 11-1267 Association class ................................................. 11-1268 Association instance ............................................ 11-1268 Association role................................................... 11-1268 Attribute ............................................................ 11-1269 Attribute link ...................................................... 11-1269 Attribute type ..................................................... 11-1269 Attribute type group ............................................ 11-1269 11.3.1 11.3.2
11.3.2.1 11.3.2.2 11.3.2.3 11.3.2.4 11.3.2.5 11.3.2.6 11.3.2.7 11.3.2.8 11.3.2.9 11.3.2.10 11.3.2.11 11.3.2.12 11.3.2.13 11.3.2.14 11.3.2.15 11.3.2.16
ARIS Methods
Contents
XVI
11.3.2.17 11.3.2.18 11.3.2.19 11.3.2.20 11.3.2.21 11.3.2.22 11.3.2.23 11.3.2.24 11.3.2.25 11.3.2.26 11.3.2.27 11.3.2.28 11.3.2.29 11.3.2.30 11.3.2.31 11.3.2.32 11.3.2.33 11.3.2.34 11.3.2.35 11.3.2.36 11.3.2.37 11.3.2.38 11.3.2.39 11.3.2.40 11.3.2.41 11.3.2.42 11.3.2.43 11.3.2.44 11.3.2.45 11.3.2.46 11.3.2.47
Authorization condition ........................................ 11-1270 Bitmap .............................................................. 11-1270 Break ................................................................ 11-1270 Business object ................................................... 11-1270 Button ............................................................... 11-1272 Class ................................................................. 11-1272 Classification criterion .......................................... 11-1273 Classifier role...................................................... 11-1273 Classifier-in-state ................................................ 11-1273 Cluster instance .................................................. 11-1273 Cluster/Data model ............................................. 11-1274 Collaboration ...................................................... 11-1275 Collaboration instance set..................................... 11-1275 Column.............................................................. 11-1275 Combo box......................................................... 11-1275 Communication................................................... 11-1275 Complex object ................................................... 11-1276 Complex object type ............................................ 11-1276 Component ........................................................ 11-1276 Component instance ............................................ 11-1276 Conditional section .............................................. 11-1277 Connector .......................................................... 11-1277 Constraint .......................................................... 11-1277 Contents ............................................................ 11-1277 Control .............................................................. 11-1278 Cost category ..................................................... 11-1279 Cost driver ......................................................... 11-1279 COT attribute...................................................... 11-1279 COT attribute (instance)....................................... 11-1280 Critical factor ...................................................... 11-1280 Data store.......................................................... 11-1281
ARIS Methods
Contents
XVII
11.3.2.48 11.3.2.49 11.3.2.50 11.3.2.51 11.3.2.52 11.3.2.53 11.3.2.54 11.3.2.55 11.3.2.56 11.3.2.57 11.3.2.58 11.3.2.59 11.3.2.60 11.3.2.61 11.3.2.62 11.3.2.63 11.3.2.64 11.3.2.65 11.3.2.66 11.3.2.67 11.3.2.68 11.3.2.69 11.3.2.70 11.3.2.71 11.3.2.72 11.3.2.73 11.3.2.74 11.3.2.75 11.3.2.76 11.3.2.77 11.3.2.78
Data value ......................................................... 11-1281 DBMS ................................................................ 11-1281 DBMS type ......................................................... 11-1281 Distribution channel............................................. 11-1281 Documented knowledge ....................................... 11-1282 Domain.............................................................. 11-1282 Domain (physical) ............................................... 11-1282 Draft list ............................................................ 11-1282 Element type ...................................................... 11-1283 Employee variable ............................................... 11-1283 Entity ................................................................ 11-1283 Entity type ......................................................... 11-1283 Enumeration....................................................... 11-1285 Enumeration attribute type ................................... 11-1285 Enumeration list occurrence .................................. 11-1286 Enumeration literal .............................................. 11-1286 ERM attribute ..................................................... 11-1286 ERM attribute instance ......................................... 11-1289 ERM domain ....................................................... 11-1289 Event ................................................................ 11-1290 Event instance .................................................... 11-1292 Exception ........................................................... 11-1293 Extension point ................................................... 11-1293 Field.................................................................. 11-1293 Field (specimen) ................................................. 11-1294 Filter object type ................................................. 11-1294 Function ............................................................ 11-1294 Function instance ................................................ 11-1304 General resource................................................. 11-1307 Generalization type ............................................. 11-1308 Graphical user interface type ................................ 11-1308
ARIS Methods
Contents
XVIII
11.3.2.79 11.3.2.80 11.3.2.81 11.3.2.82 11.3.2.83 11.3.2.84 11.3.2.85 11.3.2.86 11.3.2.87 11.3.2.88 11.3.2.89 11.3.2.90 11.3.2.91 11.3.2.92 11.3.2.93 11.3.2.94 11.3.2.95 11.3.2.96 11.3.2.97 11.3.2.98 11.3.2.99
Group................................................................ 11-1308 Hardware component........................................... 11-1309 Hardware component class ................................... 11-1310 Hardware component type.................................... 11-1310 Improvement potential......................................... 11-1310 Index ................................................................ 11-1311 Information carrier .............................................. 11-1311 Information flow ................................................. 11-1311 Instantiation cycle ............................................... 11-1312 Instantiation interval ........................................... 11-1312 Instantiation plan ................................................ 11-1312 Interaction instance set........................................ 11-1313 IT function ......................................................... 11-1313 IT function class.................................................. 11-1313 IT function type .................................................. 11-1313 Key performance indicator instance........................ 11-1315 Knowledge category ............................................ 11-1316 Layout ............................................................... 11-1317 Link object ......................................................... 11-1318 List ................................................................... 11-1318 List control ......................................................... 11-1318
11.3.2.100 Location............................................................. 11-1318 11.3.2.101 Loop start .......................................................... 11-1319 11.3.2.102 Main process ...................................................... 11-1319 11.3.2.103 Marketing instrument........................................... 11-1319 11.3.2.104 Material class...................................................... 11-1319 11.3.2.105 Material flow....................................................... 11-1320 11.3.2.106 Material type ...................................................... 11-1320 11.3.2.107 Measurement unit ............................................... 11-1320 11.3.2.108 Measurement unit number.................................... 11-1321 11.3.2.109 Memory location ................................................. 11-1321
ARIS Methods
Contents
XIX
11.3.2.110 Message flow ...................................................... 11-1321 11.3.2.111 Message type ..................................................... 11-1322 11.3.2.112 Module .............................................................. 11-1322 11.3.2.113 Module class....................................................... 11-1322 11.3.2.114 Module type ....................................................... 11-1322 11.3.2.115 Need ................................................................. 11-1324 11.3.2.116 Network............................................................. 11-1324 11.3.2.117 Network class ..................................................... 11-1324 11.3.2.118 Network connection ............................................. 11-1325 11.3.2.119 Network connection type ...................................... 11-1325 11.3.2.120 Network node ..................................................... 11-1325 11.3.2.121 Network node type .............................................. 11-1325 11.3.2.122 Network protocol................................................. 11-1325 11.3.2.123 Network type...................................................... 11-1326 11.3.2.124 Note.................................................................. 11-1326 11.3.2.125 Object instance ................................................... 11-1326 11.3.2.126 Object type class................................................. 11-1327 11.3.2.127 Objective ........................................................... 11-1327 11.3.2.128 Operating resource .............................................. 11-1327 11.3.2.129 Operating resource class ...................................... 11-1329 11.3.2.130 Operating resource type ....................................... 11-1330 11.3.2.131 Operating system ................................................ 11-1330 11.3.2.132 Operating system type ......................................... 11-1331 11.3.2.133 Operation........................................................... 11-1331 11.3.2.134 Organizational chart ............................................ 11-1331 11.3.2.135 Organizational level ............................................. 11-1332 11.3.2.136 Organizational unit .............................................. 11-1332 11.3.2.137 Organizational unit type ....................................... 11-1334 11.3.2.138 Package ............................................................. 11-1335 11.3.2.139 Packaging material class ...................................... 11-1335 11.3.2.140 Packaging material type ....................................... 11-1336
ARIS Methods
Contents
XX
11.3.2.141 Page.................................................................. 11-1336 11.3.2.142 Parameter .......................................................... 11-1336 11.3.2.143 Partition............................................................. 11-1337 11.3.2.144 Performance characteristic.................................... 11-1337 11.3.2.145 Person ............................................................... 11-1337 11.3.2.146 Person type ........................................................ 11-1339 11.3.2.147 Perspective ........................................................ 11-1340 11.3.2.148 Position ............................................................. 11-1340 11.3.2.149 Process .............................................................. 11-1341 11.3.2.150 Product/Service .................................................. 11-1341 11.3.2.151 Program library................................................... 11-1344 11.3.2.152 Program module ................................................. 11-1345 11.3.2.153 Program module type .......................................... 11-1345 11.3.2.154 Programming language ........................................ 11-1345 11.3.2.155 Quick object ....................................................... 11-1345 11.3.2.156 Radio button/Check box ....................................... 11-1345 11.3.2.157 Reception........................................................... 11-1346 11.3.2.158 Relation ............................................................. 11-1346 11.3.2.159 Relationship ....................................................... 11-1346 11.3.2.160 Relationship type ................................................ 11-1347 11.3.2.161 Risk .................................................................. 11-1348 11.3.2.162 Rule .................................................................. 11-1349 11.3.2.163 Rule instance ...................................................... 11-1350 11.3.2.164 Screen............................................................... 11-1350 11.3.2.165 Screen design ..................................................... 11-1351 11.3.2.166 Screen table ....................................................... 11-1351 11.3.2.167 Section .............................................................. 11-1351 11.3.2.168 Security protocol ................................................. 11-1351 11.3.2.169 Separator........................................................... 11-1352 11.3.2.170 Sequence ........................................................... 11-1352 11.3.2.171 Shift.................................................................. 11-1352
ARIS Methods
Contents
XXI
11.3.2.172 Shift cycle .......................................................... 11-1352 11.3.2.173 Shift plan ........................................................... 11-1353 11.3.2.174 Signal................................................................ 11-1353 11.3.2.175 Solution ............................................................. 11-1353 11.3.2.176 Sp./gen. operator................................................ 11-1354 11.3.2.177 Spin box ............................................................ 11-1355 11.3.2.178 State ................................................................. 11-1355 11.3.2.179 State machine .................................................... 11-1355 11.3.2.180 Strategy ............................................................ 11-1355 11.3.2.181 Structural element .............................................. 11-1355 11.3.2.182 Subsystem ......................................................... 11-1356 11.3.2.183 Subsystem instance............................................. 11-1356 11.3.2.184 System attribute ................................................. 11-1356 11.3.2.185 System attribute domain ...................................... 11-1357 11.3.2.186 System organizational unit ................................... 11-1357 11.3.2.187 System organizational unit type ............................ 11-1357 11.3.2.188 Table................................................................. 11-1358 11.3.2.189 Tables (specimen) ............................................... 11-1358 11.3.2.190 Tech. operating supply class ................................. 11-1358 11.3.2.191 Technical operating supply.................................... 11-1359 11.3.2.192 Technical operating supply type............................. 11-1360 11.3.2.193 Technical term .................................................... 11-1361 11.3.2.194 Technical terms instance ...................................... 11-1362 11.3.2.195 Text .................................................................. 11-1362 11.3.2.196 Text box ............................................................ 11-1362 11.3.2.197 Tool .................................................................. 11-1362 11.3.2.198 Transaction folder ............................................... 11-1362 11.3.2.199 Transport system ................................................ 11-1363 11.3.2.200 Transport system class......................................... 11-1364 11.3.2.201 Transport system type ......................................... 11-1365 11.3.2.202 Tree control........................................................ 11-1365
ARIS Methods
Contents
XXII
11.3.2.203 UML Model ......................................................... 11-1366 11.3.2.204 Use case instance................................................ 11-1366 11.3.2.205 View.................................................................. 11-1366 11.3.2.206 View (physical) ................................................... 11-1366 11.3.2.207 Warehouse equipment ......................................... 11-1367 11.3.2.208 Warehouse equipment class.................................. 11-1368 11.3.2.209 Warehouse equipment type .................................. 11-1368 11.3.2.210 XOR .................................................................. 11-1369 11.4 ARIS Attribute Types............................................................... 11-1370 Possible Attribute Values................................................. 11-1370 Domain: Integer and Floating Point Numbers ..................... 11-1423 Attribute Type Groups .................................................... 11-1424 11.4.1 11.4.2 11.4.3 11.5 11.6 11.7
Hidable/Displayable Model Types .............................................. 11-1429 Number of Possible Assignments............................................... 11-1450 Classification of Models............................................................ 11-1482 Layout Classes .............................................................. 11-1482 Assignment of Models to Layout Classes............................ 11-1483 Implicit Relationships - eEPC as Column/Row Display .......... 11-1488 Implicit Relationships of the Input/Output Diagram............. 11-1492 Implicit Relationships of the UML Activity Diagram .............. 11-1492 Implicit Relationships of the PCD ...................................... 11-1493 Implicit Relationships of the PCD (Material Flow) ................ 11-1493
11.7.1 11.7.2 11.8 11.8.1 11.8.2 11.8.3 11.8.4 11.8.5 11.9
Implicit Relationships in Swimlane Models .................................. 11-1487
Model Types (ModelTypeNum) .................................................. 11-1494
11.10 Object Definitions (ObjTypeNum) .............................................. 11-1500 11.11 Connection Definitions (CxnTypeNum) ....................................... 11-1508 11.12 Object Symbols (SymbolNum) .................................................. 11-1531 11.13 Attribute Number, Length and Data Type (AttrTypeNum).............. 11-1553 11.14 Columns (LaneTypeNum)......................................................... 11-1663 11.15 Enumeration Values (AttrValueType) ......................................... 11-1667 12 Literature List .................................................................................... 12-1
ARIS Methods
Contents
XXIII
12.1 12.2
General Literature List .................................................................. 12-1 Chapter-Related Literature List ...................................................... 12-4 Chapter 5, Unified Modeling Language in ARIS ........................ 12-4 Standard Definitions for UML...................................... 12-4 Using UML............................................................... 12-4 UML and Business Process Modeling ............................ 12-4 12.2.1.1 12.2.1.2 12.2.1.3
12.2.1
12.2.2 12.2.3
Chapter 6, Using the Object Modeling Technique (OMT) Modeling Methods ............................................................... 12-5 Chapter 7, Methods for Knowledge Management ..................... 12-5 Knowledge Management, General ............................... 12-5 Using ARIS for Knowledge Management....................... 12-5 Balanced Scorecard Method ....................................... 12-6
12.2.3.1 12.2.3.2 12.2.3.3 List of Figures Index
ARIS Methods
Introduction
1-1
1 Introduction
Due to an increasing standardization and a dramatic drop in hardware prices the approaches to the development of information systems have changed considerably. In the past, the industry focused mainly on optimizing system design and system integration. In recent years, however, the focus has shifted more and more towards creating solutions for the special demands of individual sectors. Decentralised information systems are increasingly available and these units can be combined into integrated information system environments. This offers new potential for savings in the organizational environment of business processes. Solidifying organizational structures which were functionally divided but had a central orientation and were often dependent on the limited possibilities of centralized host environments led to an increasing inflexibility in the companies. In the beginning, few people realized or paid attention to the new potentials opening up thanks to an increasing decentralization of computers and computer services as well as to the new information system architecture concepts (e.g. client-server, workflow management) that these involved. Today, steadily intensifying competition, however, has turned them into the hottest topic for every single company. Flexible structures which persistently focus on internal business processes will become the decisive competition factor for companies. But only a holistic view of all business processes enables a company to recognize, streamline and support interconnected processes through optimized information system environments. Compared with the management of centralized business environments, however, the management of these new structures is becoming far more complex rather than simpler. In this context, clearly and uniformly defined responsibilities, maximum transparency of structures, a homogenous communication basis integrating all company levels, and streamlined project management which is based on the company objectives, is vital for success. The methods of company modeling offer support for mastering these complex tasks. Business models are a crucial prerequisite for analyzing business processes, bringing projects in line with the overall company objectives, and finally for finding the perfect information structures in the form of a compound of distributed, integrated systems to support these lean organizational structures.
ARIS Methods
Introduction
1-2
Modeling the company's actual situation - and, in doing so, increasingly examining holistic business processes - is coming more and more to the foreground of the discussion. The increasing availability of quite different modeling methods does indeed add impetus to this trend, but the enormous multitude of methods also brings increasing complexity and confusion. Consequently, efforts are being made to define standardized general concepts (architectures) for development and modeling methods. One of these architectures is the Architecture of integrated Information Systems(ARIS) developed by Scheer (see Scheer, Architecture of integrated Information Systems, 1992). This architecture concept enables methods to be evaluated and organized by concentrating on their focal points, and it also serves as an orientation framework for complex development projects because in its structuring elements it contains an implicit procedural model for the development of integrated information systems. An architecture of this kind naturally leads towards standardization in the use of methods. As a result, existing and new modeling methods were merged to create a holistic method for modeling business processes.on the basis of this architecture. This ARIS architecture was then used as the basis for the development of ARIS Toolset a family of tools developed by IDS Scheer AG. ARIS Toolset supports consultants and companies in creating, analyzing, and evaluating company processes for purposes of Business Process Reengineering. ARIS Easy Design provides the necessary functionalities to record and model company processes easily. This handbook gives you your first introduction to the modeling methods provided in ARIS Easy Design. In addition, approaches are provided and methods suggested that require the full range of ARIS Toolset or the use of system add-ons such as ARIS ABC, ARIS Simulation, ARIS Web Publisher or ARIS Lotus Notes Connectivity. Furthermore this handbook is also a useful support for you if you work with modeling methods regardless of the problems of using tools. The second chapter of the manual gives you a short introduction to the structure and structuring elements of the ARIS architecture.
ARIS Methods
Introduction
1-3
Chapters three and four describe the modeling methods based on this structure. The structure of chapter four strictly follows the ARIS architecture structure. This is intended to illustrate the allocation of the individual modeling methods to the structuring elements of the ARIS architecture. First of all, the chapters are subdivided into the different views of the ARIS architecture. These views are again subdivided into the individual phases of the level concept (see Chapter 2). Chapter 5 explains the implementation of the Unified Modeling Language in ARIS, and Chapter 6 presents the Object Modeling Technique (OMT) as a modeling method. Chapter 7 describes knowledge management methods. Chapter 8 provides you with ARIS solutions for specific business management problems. The problems are presented in the form of scenarios, and are handled on a task-by-task basis. Chapter 9 explains in more detail the ARIS Balanced Scorecard method from the original concept to putting it into practical use. This is the foundation for a comprehensive management system that enables company management to set and track its objectives. The significance of the eBusiness Scenario Diagram and cBusiness Maps model types are explained in Chapter 10. In the appendix there is a list of the models and object types available in ARIS with their relationships. You will also see a list of the object types with their assigned symbol and attribute types. All ARIS attribute types with their possible attribute values and attribute type groups are also listed. Lists for model types that can be shown and hidden then follow and the number of possible object assignments as well as the classification of the most important models for layout generation or for an order report. Then the implicit relationships that are created in swimlane models, i.e. in column and row-oriented models, are listed for you as soon as you place the corresponding object types. Finally, a list is given with all models, objects, connections and symbols with type numbers. To this are added the data types of the attributes, columns with column numbers, and the attribute type contents. Then you will find the literature list that also contains a chapter by chapter listing.
ARIS Methods
Architecture of integrated Information Systems (ARIS)
2-1
2 Architecture of integrated Information Systems (ARIS)

2.1 Concept of the ARIS Architecture
The design of Architecture of integrated Information Systems (ARIS) is a based on an integration concept which is derived from a holistic analysis of business processes. The first step in creating the architecture calls for the development of a model for business processes which contains all basic features for describing business processes. The result is a highly complex model which is divided into individual views in order to reduce its complexity. Due to this division, the contents of the individual views can be described by special methods which are suitable for this view without having to pay attention to the numerous relationships and interrelationships with the other views. Afterwards, the relationships between the views are incorporated and are combined to form an overall analysis of process chains without any redundancies. A second approach that also reduces the complexity is the analysis of different descriptive levels. Following the concept of a lifecycle model the various description methods for information systems are differentiated according to their proximity to information technology. This ensures a consistent description from business management-related problems all the way down to their technical implementation. Thus, the ARIS architecture forms the framework for the development and optimization of integrated information systems as well as a description of their implementation. In this context, with the emphasis on the technical descriptive level, the ARIS concept serves as a model for creating, analyzing, and evaluating business management process chains. Scheer describes the architecture of integrated information systems in more detail (see Scheer, Architecture of Integrated Information Systems 1992, and Scheer, ARIS - Business Process Frameworks, 1998).
ARIS Methods
2-2
2.2 Descriptive Views

The analysis starts with a business process like the one shown in Figure 2.2-1. The process is triggered by the Customer order received event. This event in turn initiates the Accept customer order function (procedure). Status descriptions for the relevant procedure environment are necessary in order to execute this procedure. This includes in particular data specific to the customer and the item. The statuses of the environment objects can be changed during workflow processing, for example, if the stock inventory data of the item are updated with the new reservation data. The procedures are carried out by sales employees who can again be assigned to departments. The department uses specific information technology resources (personal computers, printers, etc.) to perform its tasks. Once the Accept customer order procedure is completed, the Order is confirmed event occurs that in turn triggers other procedures, e.g. Track order or Create production plan. The Order object is now in a new state because the Order received object has become an Order confirmed object. Executing the Accept customer order function has resulted in a product/service, which is used together with personnel and technical resources as input for processing the following procedures.
ARIS Methods
2-3
Figure 2.2-1: Model of a Business process
The components necessary to provide a full description of a business process are thus procedures, events, products/services (statuses), processors, organizational units and information technology resources. Considering all the effects on all the elements of the procedure for every event would severely complicate the model and lead to redundancies in the description.
ARIS Methods
2-4
In order to reduce this complexity, the general context is divided into individual views (see Figure 2.2-2) that represent separate modeling and design aspects (see Scheer, Architecture of integrated Information Systems 1992, p. 13 et seqq). These can be processed largely independently of each other. The views are divided in such a way that relationships between the components within a view are very high while those between the views are only relatively loosely linked.
Figure 2.2-2: Process Model Views
ARIS Methods
2-5
Events such as Customer order received or Invoice produced define the point at which a change in the state of information objects (data) occurs. They are described in the data view of the ARIS architecture. The states in the objects' environment, e.g. in the environment of the customer order, are represented by products/services. A product/service can be either a concrete product or an intangible service. Services that generate and provide information are information services. The provision of financial resources is also included in products/services. Relationships among performances are described in the ARIS architecture's product/service view. The functions to be performed (processes) and their interrelationships with each other form a second view, the function view. It contains the description of the function, the enumeration of the individual subfunctions that belong to the overall relationship and the positional relationships that exist between the functions. The organization view represents a combination of the users and the organizational units as well as their relationships and structures. Information technology resources constitute the fourth area of analysis, the resource view. This view, however, is significant for the subject-related view of business processes only insofar as it provides general conditions for describing the other components that are more directly geared towards business. For this reason, the component descriptions of the other views (data, functions and organization) are described on the basis of their proximity to the information technology resources. Thus, the resources are dealt with at the design specification and implementation descriptive levels of the other views (see Chapter 2.3). The lifecycle model defined by the analysis of the different levels thus replaces the resource view as an independent descriptive object. Breaking down the process into individual views reduces its complexity - albeit at the expense of the relationships between the process components of the views. For this reason, the control view is introduced as an additional view in which the relationships between the views are described. The integration of these
ARIS Methods
2-6
relationships within a separate view makes it possible to systematically enter all the relationships without any redundancies. The control view is an essential component of ARIS. This is the fundamental feature that sets the ARIS concept apart from other architecture proposals (for comparison with other architecture proposals see Scheer, Architecture of integrated Information Systems, p. 24 et seqq). This process yields the five ARIS views shown in Figure 2.2-1, which will be also be discussed later in the other method descriptions.
Figure 2.2-3: ARIS Analytical Views of the Process Model
ARIS Methods
2-7
2.3 Descriptive Levels

As was mentioned earlier, the ARIS resource view is structured in accordance with a lifecycle concept of an information system's descriptive levels. Lifecycle models in the form of level or phase concepts describe the lifecycle of an information system. However, the ARIS lifecycle model does not have the significance of a procedural model for the development of an information system. It rather defines the different descriptive levels which are distinguished according to their proximity to the information technology. This distinction is expressed in ARIS by the three-tier division illustrated in Figure 2.3-1 (see Scheer, Architecture of integrated Information Systems 1992, p. 16 et seqq). The starting point of the analysis is the operational business problem. Here, the description encompasses rough facts that are geared very closely to technical objectives and technical language. This step also incorporates the information technology options for the support of business processes and decisions. Therefore, only semi-formal descriptive methods are used to represent this. Because of their lack of detail and their highly technical vocabulary, they cannot serve as a starting point for a formalized translation into the implementation stage. The requirements definition therefore has to describe the business application which is to be supported in a formalized description language so that it can be used as the starting point for a coherent translation into information technology. This process is also referred to as (semantic) modeling. The requirements definition is very closely associated with the operational business problem, as is indicated by the width of the arrow in Figure 2.3-1. The design specification level is reached as soon as the conceptual environment of the requirements definition is transferred to the categories of an IT-oriented conversion. Here, the module or transactions that are to be carried out are defined instead of the technical functions. This level can also be thought of as an adaptation of the requirements description to the general ways of describing information
ARIS Methods
2-8
technology. Thus, the requirements definition and the design specification are only loosely linked. This means that a design specification can be changed without affecting the requirements definition. This, however, should not mean that the requirements definition and the design specification can be developed separately from each other. After completing the requirements definition it is much more important that its contents in terms of business administration be determined in such a way that considerations which are exclusively IT-oriented such as information system performance do not have an influence on the subject contents. At the implementation level, the design specification is transferred to concrete hardware and software components. Thus, the link to information technology is established. The descriptive levels are marked by different update cycles. The updating frequency is lowest at the requirements definition level and highest at the implementation level. The implementation level is closely linked to the development of information technology and is also subject to ongoing revision as a result of the rapid innovation cycles of information technology. The requirements definition level is particularly significant because it is both a repository of the long-term business application and at the same time the starting point for further steps in generating the conversion to the implementation description. The requirements definitions possess the longest lifecycle and - through their close affinity to the description of the business problem - also record the technical benefits of the information system. For this reason, the view of the development of requirements definitions or semantic models has the highest priority. The semantic models form the link between users and the initial implementation of their problem description into an IT-related language.
ARIS Methods
2-9
Figure 2.3-1: Descriptive Levels of an Information System
ARIS Methods
2-10
The development of the views and the descriptive levels, together with the initial operational solution constitute the essence of the ARIS architecture. As shown in Figure 2.3-2, every descriptive view is described on the three levels of requirements, definition, design specification, and implementation.
Figure 2.3-2: ARIS Concept
With the development of the ARIS concept the description fields of the architecture as they are defined by the descriptive views and levels are now fixed. Including the business problem description, which serves as the starting point of the analysis,
ARIS Methods
2-11
they comprise thirteen components. What is now necessary is to select and explain suitable description methods for each area of analysis. The criteria for selecting these methods (see Scheer, Business Process Engineering 1994, p. 18) are as follows: the simplicity and intelligibility of the means of portrayal, the suitability for the subject contents that are specifically to be expressed, the ability to use consistent methods for all applications to be portrayed, the existing or anticipated degree of familiarity with the methods and the degree of independence of the methods from technical developments in information and communication technology. The individual methods used in the description views are described in the following chapters.
ARIS Methods
Process Chain Analysis
3-1
3 Process Chain Analysis

3.1 Description of Business Problems
Before the individual descriptive objects within the ARIS architecture (views and levels) can be modeled, the initial semantic business process, i.e. the business problem, must already exist. In this context, the weak points of the information systems in use are described as far as the support of the business processes and the target concept's essential contents of the projected system are concerned. The weak points thus found also mirror the objectives that new information systems will have to attain. The model expressing this problem description therefore needs to cover as many facts as possible from the data, function and organizational structure views including the interrelationships existing between them. Moreover, the model must allow the target concept to be specified to such an extent that this specification can serve as a starting point for the rest of the modeling process. Thus, the development process of the requirements definitions triggers the division into views corresponding to the ARIS architecture. Due to the requirement that the initial business situation has to be described in a comprehensive way and that the weak points of the existing information systems have to be displayed in condensed form, the use of common modeling methods is limited. Since their main analysis features are focused on different aspects, these methods can only be used for modeling individual views. These interrelationships are recorded in condensed form as process chain diagrams (PCDs) which also provide an overview of the information system that is to be dealt with (see Scheer, EDP-oriented Business Management Studies 1990, p. 39 f.).
ARIS Methods
3-2
3.2 Process Chain Diagrams (PCDs)

In a process chain diagram a process chain is displayed as a closed loop. Thus, the views of a business process established earlier (organization view, data view, function view and resource view) and their interrelationships are still expressed in a cohesive form. In figure Figure 3.2-1 an example of the process chain for Order processing is shown.
Figure 3.2-1: Example of a Process Chain Diagram
The two left columns represent the chronological procedural sequence of the business process analyzed. In order to do this, the individual functions of the procedure are listed in the second column and linked to the events by which they are triggered and created. Functions and events are linked by dotted arrows which define exactly which events trigger functions and which events are themselves created by functions. They thus define the control flow between functions. In the example given the Enter order function is started by the Order received event.
ARIS Methods
3-3
The result of this function is defined by the Order entered end event. This event triggers the next function, Process order. This relationship between events and functions produces a chronological-logical procedural sequence of functions called a process chain. The logical interdependencies of possible branching points and loops of the control flow can be expressed with operators. The input and output data required by the functions are shown in the next column in the form of data clusters. The input data required by the Process order function are the Order data and the Customer Master data. The generated output data is the Customer order. It is not only the information objects themselves that can be displayed. The same may be applied to the information carriers (media) on which the information is located. This can be for example a document, a list, a handwritten receipt or a storage medium such as a hard disk. The right hand column is used to determine the organizational units (departments) that are responsible for carrying out the current function. The Type of processing (Dialog, Batch, Manually) and Application system columns provide additional information about the degree of IT support of a particular function. The application system used or the application system components can be entered in the Application system column. The Type of Processing column is used to specify more closely the way in which a function is to be executed; this may take the form of dialog, batch, or manual processing. When analyzing business processes in a process chain diagram that describes an actual situation, weak points in the current problem solution can be highlighted. These weak points can be either media breaks between IT-related and manual processing or organizational breaks (e.g. the department in charge/organizational unit is changing frequently). The analysis particularly shows data redundancies, multiple entries and time delays within a procedure, making it possible to derive many possible ideas for improving the target procedure that is being defined. In order to describe the initial situation, process chain diagrams are created at a relatively high level of compression. Since they are primarily used for displaying the interplay among all ARIS components, they also serve as a means of representation as part of the ARIS control view (for more information see Chapter 4.4). In the control view not only process chain diagrams but also event-driven process chains (EPCs) are shown (see Chapter 4.4.1.2.1). Event-driven process chains offer the
ARIS Methods
3-4
same modeling capabilities as PCDs but, as they are a free form representation the objects do not have to be positioned in predefined columns. If the procedure model is to be supported by only one model type (PCD or EPC), the target procedure can be displayed as an EPC too. The description of other modeling methods follows the ARIS concept. The description first deals with the views (function view, data view, organization view, control view), and then the description levels (requirements definition, design specification, and implementation) within these views.
ARIS Methods
Function View
4-1
4 Modeling within the Views and Levels of the ARIS Concept

4.1
4.1.1
Function View
Requirements Definition
Modeling methods often display functions in connection with objects from the other descriptive views of ARIS. The relationship between data and functions is displayed for example to specify the transformation process of a function via the input/output data of that function. In the ARIS architecture, however, the various areas of analysis are kept strictly separate (see Scheer, Architecture of integrated Information Systems 1992, p. 62). Within the function view only those representational forms are used which illustrate the connections between the functions. One example is the relationship between functions and data displayed in the control view of ARIS. Definition: A function is a technical task or activity performed on an object in support of one or more company objectives (see Scheer, Architecture of integrated Information Systems 1992, p. 63).
Functions are displayed as rectangles with rounded corners:
Figure 4.1.1-1: Representation of the "Check customer inquiry" function
Usually, the criterion for establishing such a function is an information object such as a customer inquiry or a production order. This should also be expressed in the description of a function. This is shown in Figure 4.1.1-1. Customer inquiry defines the object, and Verify defines the operation that will be performed on this object. On a higher level, only a noun is used to describe functions (e.g. Procurement logistics, production, sales). ARIS Methods
Function View
4-2
4.1.1.1
Function Tree
Functions can be described on different compression levels. At the highest compression level are complex functions in the form of business processes or process chains. An example of this is the processing of a customer order from the customer inquiry to shipping. Such a business process thus represents a complex function that can be divided into subfunctions to reduce its complexity. Hence, the term Function can be used on all hierarchy levels. But other terms are also often used to explain the hierarchy level in a more descriptive way: procedure, process, subfunction or elementary function. Dividing functions can involve several hierarchy levels. Elementary functions represent the lowest level in semantic function trees. Definition: Elementary functions are functions which cannot be reduced any further for the purpose of business process analysis.
Function trees or hierarchy diagrams are used to represent this sub-structuring (see Figure 4.1.1-2).
ARIS Methods
Function View
4-3
Figure 4.1.1-2: Function Tree (Extract)
Different criteria may be adopted for grouping functions in a function tree (see Brombacher/Bungert, Company modeling practice 1992). Frequently used criteria for this purpose include: processing of the same object (object-oriented), reduction according to association with a process (process-oriented) or combination of functions concerned with the same operations (execution-oriented).
ARIS Methods
Function View
4-4
Figure 4.1.1-3 shows an example of an object-oriented breakdown. The superior Process production order function is subdivided into the Create production order, Confirm production order, Update production order, Cancel production order, Release production order and Monitor production order functions. These functions describe different operations (create, update, cancel, etc.) that are performed on one object, the Process production order.
Figure 4.1.1-3: Object-oriented Function Tree
ARIS Methods
Function View
4-5
If function trees represent the results of modeling business processes, it is a natural progression to illustrate process-oriented function trees. Figure 4.1.1-4 shows an example of a process-oriented function breakdown. The Accept customer order, Verify customer order, Create customer data, Verify customer creditworthiness, Verify product availability and Confirm customer order functions belong to the Process customer order business process. Unlike an object-oriented breakdown, the operations here are performed on different objects (customer order, product availability).
Figure 4.1.1-4: Process-oriented Function Tree
ARIS Methods
Function View
4-6
Execution-oriented grouping means that all functions performing the same process (checking, creating, deleting) on different information objects will be grouped together. An example of the Modify operation is shown in Figure 4.1.1-5. The functions shown may occur in different processes and may also be involved in processing different objects. Yet the type of operation they perform on the various objects is always the same.
Figure 4.1.1-5: Execution-oriented Function Tree
On the one hand, representing functions in a function tree reduces complexity, but on the other hand, it is a static representation. In addition to this static representation it might also be of interest to see the procedural sequence of functions chronologically. Chronological-logical procedural sequences are represented in Event-driven Process Chains (EPCs) . They contain not only functions but also events as links between ARIS Methods
Function View
4-7
functions. Events must be assigned to the ARIS data view. Event-driven process chains are described in the ARIS control view - in accordance with the principle of the separation of ARIS views (see Chapter 4.4.1). Describing the functions from a subject-related point of view not only involves the property that a function can be broken down into its elements - other function properties are of interest, too. This is especially true for properties which take part in the design of business processes. Thus, each function draft should include information on whether it requires user input or whether it can run automatically. As a consequence, similar functions that can be executed without user intervention may be bundled and processed in a closed operation (batch run). Information on the quantity structure of a function (e.g. number of enquiries that are processed in a day) and the total length of time it takes to perform the function provide additional points of reference for redesigning business processes. The total time can be further subdivided into individual time elements (orientation time, processing time, waiting time). ARIS saves this information as attributes to the Function object type. In the appendix of this manual you will find a list of all attribute types.
4.1.1.2
Y Diagram
The Y diagram is used to represent the functions (tasks) of a company on a highly aggregated level. These are major functional areas such as Product design, Materials management, Maintenance. The structured representation in the form of the Y-CIM model (see Scheer, A-W Business Process Re-engineering 1994, p. 87) shows one classification of the individual functions. Scheer allocates the primary businessadministrative planning functions of production planning and control to the left branch of the Y, while the right contains the technically-oriented functions of product planning and product realization. The planning functions are arranged in the higher portions of the Y while the control and realization functions can be found in its lower portions. Thus, the Y-CIM model represents a frame for sorting all functions of a production company. Within ARIS, this model type can be used for the function-oriented approach to complex reference models. The objects shown are of the Function object type.
ARIS Methods
Function View
4-8
Arranged in a hierarchy, this object type can be linked, for example, with the Function tree and eEPC model types. An example is shown in Figure 4.1.1-6.
Figure 4.1.1-6: Y Diagram
ARIS Methods
Function View
4-9
4.1.1.3
SAP Applications Diagram

permits an approach to the SAP R/3 reference model
The SAP applications diagram
that is geared to the SAP R/3 application system modules. In the R/3 reference model, a process selection matrix is assigned to every object of that model type. This matrix displays the main processes that are available in the respective R/3 modules and the process scenarios they can be used to map. The SAP R/3 system SAP applications diagram is shown in Figure 4.1.1-7.
Figure 4.1.1-7: SAP Applications Diagram
4.1.1.4
Objective Diagram
Before you start modeling, analyzing or optimizing business processes (business process re-engineering), you should define the objectives that modeling your companys business processes will serve. In the objective diagram you can - among other things - define (company) targets and create target hierarchies. Definition: A target defines future company objectives, which are to be
achieved by supporting critical factors and creating new business processes.
ARIS Methods
Function View
4-10
You can specify possible critical factors for achieving the objective, arrange them in a hierarchy and assign them to the targets that they are helping to attain. Definition: Critical factors specify the aspects which need to be considered in order to achieve a particular company target. They are assigned to company targets in the objective diagram.
This model type is linked to the other model types of the requirements definition by means of the Function object type. For every target, you can display which function (business process) supports the attainment of this target. In the business process modeling and optimizing phase, you should consider the target priority set here and the assigned functions when establishing the process model. An example of an objective diagram is shown on Figure 4.1.1-8.
Figure 4.1.1-8: Example of an Objective Diagram
ARIS Methods
Function View
4-11
4.1.2
Design Specification - Application System Type Diagram
The design specification of the function view contains the specification for the application system and module types, for the modular structure of the, for the draft of the individual transaction steps, and the definition of input and output presentations in the form of lists and screen drafts.
The main questions that are answered by specifying the IT design of the function view are: How can the functions defined in the requirements definition be supported by the use of application system types, module types or IT functions? How are application system types or module types set up in a modular form? Which lists and forms are necessary to perform a function? Which lists can be created with an application system type or a module type and which forms do application system types and module types use? What technological basis (operating systems, user interfaces or database
management systems)) does an application system type have? What company objectives are pursued when using a specific application system type? The main object type of the design specification in the function view is therefore the Application system type. Unlike a specific application system that is not seen until the implementation level of the function view and an individual application system that is identifiable by a license number in the company, an application system type is produced by the typification of all application systems that are on precisely the same technological basis. Definition: An Application system type typifies individual application systems which have exactly the same technological properties.
Example: ARIS Toolset version 4.1 represents an application system type. You can obtain several licenses and therefore several individual application systems from this application system type. ARIS Methods
Function View The following graphic represents application system types:
4-12
Figure 4.1.2-1: Graphic representation of an application system type
Application system types are mainly modular in structure. The application system type diagram enables this modular structure to be displayed. The individual parts of an application system type are module types. Figure 4.1.2-2 shows an example of this:
Figure 4.1.2-2: Modular Configuration of an Application System Type
ARIS Methods
Function View
4-13
In the above example ARIS Toolset version 4.1 is composed of the ARIS Easy Design, ARIS ABC and ARIS Simulation module types. As with the application system types, these are module types that typify individual modules that are based on exactly the same technology. Module types are components of application system types. They represent components that can run to completion on their own. Definition: A module type represents a component of an application system type which can be executed independently. Module types represent the typification of individual modules which have exactly the same technological basis.
Application system types and module types can be organized in any hierarchy. Module types can be divided at the lowest level of the IT function types. Definition: IT function types are the smallest units of a module type for the purposes of a transaction. They are produced by individual program modules and must always be carried out completely to process an individual work step.
Figure 4.1.2-3: Graphical Representation of an IT Function Type
The application system type diagram allows the functions of the requirements definition that are supported by the defined application system types and module types to be specified. This assignment thus forms the link between the requirements definition and the design specification of the function view. An example illustrating this is shown in Figure 4.1.2-4.
ARIS Methods
Function View
4-14
Figure 4.1.2-4: Allocation of Functions to Application System Types
The technological basis of application system types and module types can be defined more precisely by allocating to them the possible types of user interfaces, database management systems and operating systems under which they run, as well as the programming languages from which they are constituted. As this concerns types and not specific examples, multiple relationships are possible. Thus an application system type can be assigned the Windows 3.1 and Windows NT user interface which means that the version of the application system type can run under both user interfaces. A unique relationship is not necessary until the allocation of the graphical user interface to a specific example (an application system) on the implementation level of the function view. This then describes the exact configuration of the individual licenses of the application system type that have been obtained by the company. An example of possible assignments in the application system type diagram is shown in Figure 4.1.2-5.
ARIS Methods
Function View
4-15
Figure 4.1.2-5: Configuring the Application System Type
Processing a technical function with the support of an application system entails using various screens and producing or using various lists that are offered by the corresponding application system. The List and Screen objects are available to represent this and can be assigned either to the technical function or the application system types and module types. If first of all general procedural sequences are to be defined without reference to specific application system types, Draft list and Screen design objects can also be used to specify the necessary screens and lists. Both object types specify first of all generally which type of list or screen is to be used (example Enter customer data) without making a specific reference to application system type lists or screens. Subsequently you can link these list and screen drafts with specific lists and screens. The assignment thus defines the implementation possibilities available. An example illustrating this is shown in Figure 4.1.2-6:.
ARIS Methods
Function View
4-16
Figure 4.1.2-6: Mask and List Assignments
The appendix contains a complete list of the object types of the application system type diagram and their possible relationships.
ARIS Methods
Function View
4-17
4.1.3
Implementation - Application System Diagram
In the application system diagram the specific application systems and modules can be assigned to the application system and module types described in the design specification. This refers to the copies of an application system type present in the company that can be uniquely identified, by their license numbers for example. Definition An application system (module) is a single copy of an application system type (module type) which can be uniquely identified, by its license number for example.
Application systems are displayed graphically as in Figure 4.1.3-1.
Figure 4.1.3-1: Graphical Representation of the Application System and the Module
As a company can have more than one license for an application system type (module type), in the application system diagram, therefore, more than one application system (module) can also be assigned to an application system type (module type). This is illustrated in Figure 4.1.3-2.
ARIS Methods
Function View
4-18
Figure 4.1.3-2: Allocation of Application Systems to their Application System Types
The application system diagram shows the actual modular structure of an application system. If all possible modular components of an application system type have been displayed in the design specification, there is now a single license for the application system so that the modular components of each individual license can be uniquely defined. It follows that the company may house multiple application systems which belong to the same system type but have completely different modular structures (see Figure 4.1.3-3).
ARIS Methods
Function View
4-19
Figure 4.1.3-3:
Different Modular Structure of Two Application Systems of the Same Type
The implementation level not only represents the existing application systems and modules, in the form of individual program files it also enables the technical (physical) conversion of the application systems to be defined. To do this the program module types that are necessary to produce an application system type or module type can be shown in the application system diagram.
ARIS Methods
Function View Definition
4-20 A program module is any program file on a data carrier obtained by the purchase of a license (e.g. an EXE file or a COM file). A program module type is formed by typifying program modules that have exactly the same technological basis.
The assignment of program module types to an application system type and or individual program modules to program module types is shown in Figure 4.1.3-4.
Figure 4.1.3-4: Assignment of Application System Types, Program Module Types and Program Modules
The ARIS Toolset version 4.1 application system type includes the aris.exe, aris.xlm, arisen.dll and merge.exe program module types. There can be several copies of each program module type in the company (program modules) if several licenses are bought or if backup copies are created.
ARIS Methods
Function View
4-21
Program module types and program modules can be put into a hierarchy in any way you like. For a more precise technological specification of the program, access by program module types to program libraries can be represented in the application system diagram. In the appendix you will find a list of all object types and relationships in the application system diagram.
ARIS Methods
Data View
4-22
4.2 Data View

4.2.1 Requirements Definition
The requirements definition of the data view includes a description of the semantic data model of the field which is to be examined. According to the ARIS division principle this description contains both the objects which specify the start and end events of a process chain as well as the status descriptions of a process chain's relevant environment. When comparing the modeling of functions and data, the latter is particularly demanding as far as the method is concerned. In the function view the only object examined is the function. In terms of interrelationships between functions only the super- and subordinations are illustrated. Chen's entity-relationship model (ERM)) is the most widely used designing method for semantic data models (see Chen, Entity-Relationship Model 1976). This modeling method uses a number of specalilized terms such as entity type, relationship type, attribute, etc. The relationships which exist between these objects are numerous and - compared with function modeling - are significantly more difficult to classify. On the following pages, the modeling of entity-relationship models (ERM) is introduced. First of all, the objects and relationships of Chen's original model are explained. In the next chapter, some operators will be added to this original model.
4.2.1.1
The Basic ERM Model
The original model distinguishes between entities, attributes and relationships. Generally, the type level can be differentiated from the occurrence level. Definition: Entities are real or abstract things that are of interest for those tasks in a company that are currently under consideration.
This descriptive object may be a business process, for example. According to the ARIS structural model, the data objects of interest are objects of the environment
ARIS Methods
Data View
4-23
and objects specifying events. Examples of entities in the Processing customer order process are: Customer 1235, Article 471, Order 11. Entities are described more precisely by certain attributes (properties). This means that a customer for example can be specified more precisely by his name, first name and address. Definition: If entities of the same type are grouped into sets, they are called entity types. The individual occurrences of these are entities.
Entities of the same type can be described by the same attributes. Thus customer Maier and customer Mller are grouped under the customer entity type. Article 4710 and article 4712 are grouped under the article entity type. Entity types are displayed in the ER model as rectangles (see Figure 4.2.1-1). In the following text, entity types in the text will be indicated by capital letters.
Figure 4.2.1-1: Examples of Entity Types
Definition:
Attributes are properties describing entity types.
ARIS Methods
Data View
4-24
Attribute occurrences are specific values of attributes of individual entities. For example, customer 1235 can be described by the Miller, Peter, Munich etc. attribute occurrences. The relevant attributes are Name, First name, and Address. Attributes are usually represented by an oval or a circle. On the following pages, attributes are represented by ovals. Figure 4.2.1-2 shows examples of attributes for the CUSTOMER entity type.
Figure 4.2.1-2: Examples of Attributes for the CUSTOMER Entity Type
The difference between entity types and attributes is often hard to find and can sometimes only be determined from the context of the modeling procedure. For example, the customers' addresses can be understood as entities and not as an attribute of CUSTOMER. In this case, a separate entity type, ADDRESS would be modeled which would have a relationship to CUSTOMER. When specifying whether you are dealing with an entity type or an attribute, the fact that entities possess attributes is a helpful criterion. Attributes, on the other hand, cannot have attributes. Thus, if an attribute is created in an ER model which is supposed to be described by further attributes later on, it becomes an entity type. Whether an
ARIS Methods
Data View
4-25
object is to be assigned interrelationships with other entity types or not is another helpful question. If this question can be answered positively the object in question, too, is an entity type. Definition: A relationship is a logical link between entities.
Hence, the existence of relationships directly depends on the existence of entities. Definition: If relationships of the same kind are grouped into sets, they are called relationship types.
A relationship type between SUPPLIER and PART could be SUPPLIES. In the following text, relationship types are also indicated by capital letters. In an ERM, relationship types are displayed as diamonds and are linked with the entity types via connections (see Figure 4.2.1-3).
Figure 4.2.1-3: Example of a Relationship Type
Often, when naming relationship types they can only be read in one direction for the links to make sense. In the above example, the relationship Supplier supplies Part is supposed to be expressed. From right to left this would read Part supplies Supplier which does not make sense. If the correct direction cannot be determined uniquely this difficulty must be avoided by skilful selection of superior terms. We differentiate between a number of relationship types. In this context, the number of entity types they link, on the one hand, and the degree of a relationship's complexity, on the other hand, serve as distinguishing criteria. Relationship types are distinguished according to the number of entity types linked to them, i.e. unary, binary or n-ary relationships. Definition: The complexity or cardinality indicates how many entities of one entity type can be assigned to an entity of the other entity type.
ARIS Methods
Data View
4-26
The relationships that must be distinguished as a consequence of this are illustrated in Figure 4.2.1-4 (see Scheer, Business Process Re-engineering 1994, p. 34). Four different kinds of relationships can be distinguished (cardinalities): 1:1 relationship, 1:n relationship, n:1 relationship, n:m relationship. In a 1:1 relationship, each entity of the first set is precisely assigned to an entity of the second set. In a 1:n relationship, each entity of the first set is assigned to exactly one entity of the second set, but each entity of the second set can be assigned to n entities of the first set. An n : 1 relationship carries out the same task but in the reverse order. In an n:m relationship, several entities of the second set are assigned to one entity of the first set and vice versa.
Figure 4.2.1-4: Cardinalities of Relationships between Two Entity Types
ARIS Methods
Data View
4-27
The cardinalities of this relationship type (Complexity attribute type) are written on the connections of the entity-relationship model (see Figure 4.2.1-5).
Figure 4.2.1-5: Representation of Cardinalities in the ERM
The cardinality currently specifies the maximum number of relationships of the relationship type an entity of the entity type can be part of. In the example the n:1 relationship shown in Figure 4.2.1-5 means that a company of the COMPANY entity type can be ASSIGNED to several relationships because a company consists of several factories; a specific factory can, however, be ASSIGNED to a maximum of one relationship and must therefore be clearly assigned to a company. Chen's original work interpreted cardinality in a different manner. The notation used in this manual, however, allows clearer formulations particularly when illustrating relationships between several entity types. In order to avoid unnecessary confusion, we will not discuss more details of Chen's original work. Due to the fact that relationships can also exist between entities of one entity type, an entity type and a relationship type may also be linked by two parallel
ARIS Methods
Data View
4-28
connections. In order to be able to differentiate between these connections they may be given role names. Recursive relationships are illustrated in the example on Figure 4.2.1-6. A superior part consists of various subordinate parts. On the other hand, a subordinate part may be used as a component in various superior parts as well.
Figure 4.2.1-6: ERM for a Bill of Materials
Both entity types and relationship types can be described by attributes (see Figure 4.2.1-7). Definition: The value ranges of attributes are called domains.
Assignments of elements of the domains to elements of the entity or relationship types are also relationships. They can be represented by a connection which is identified with the name. Definition: A 1:1 relationship must exist between one entity type and at least one domain. The values of this domain uniquely identify the individual entities. Therefore, they are called the key attributes of the entity type.
In the example shown in Figure 4.2.1-7 (see Scheer, Business Process Reengineering 1994, p. 33) the entities of CUSTOMER are uniquely identified by the customer number key attribute. Relationships are identified by fusing the key attributes of the linked entities. Thus, the key attributes of the RESIDES AT relationship type are customer number and address number. The descriptive attributes of the relevant data objects are defined by values deriving from domains having a 1:n relationship with entity or relationship types.
ARIS Methods
Data View
4-29
Figure 4.2.1-7: Assignment of Attributes in the ERM
ARIS Methods
Data View
4-30
4.2.1.2
Extending the ERM - eERM
In the last few years, Chen's basic model has been extended substantially. This manual will only discuss those extended models that are significant for modeling the data view in the ARIS architecture.
4.2.1.2.1
Extending Using Design Operators
Design operators provide formal support in the process of creating a data model. Their use ensures a systematic procedure and provides the viewer of an existing data structure with insights into its design process. Proceeding from existing concepts, new concepts are produced with the help of design operators. The design process is an intellectual procedure largely carried out at the level of business administration knowledge. The investigation of business conditions from the point of view of their data structures is helping either to structure known conditions based on a new view or to create new relationships not considered so far. Of the numerous and various approaches for extending ER modeling, four basic design operators have become established (see Scheer, Business Process Reengineering 1994, p. 35 ff.): classification, generalization, aggregation, grouping.
Classification Definition: In classification, objects (entities) of the same kind are identified and assigned to a concept (entity type). One object is identical to another if it is described by the same properties (attributes).
Thus, classification leads to the previously described identification of entity types (see Figure 4.2.1-8).
ARIS Methods
Data View
4-31
Figure 4.2.1-8: Classification of Customers
Generalization/Specialization Definition: In generalization, similar object together in a superior object type. types are grouped
As is shown in Figure 4.2.1-9, the CUSTOMER entity type and the SUPPLIER entity type are generalized under the generic concept BUSINESS ASSOCIATE. Properties (described by attributes) that are common to both source objects are transferred to the generalized object type. Thus, only those attributes that are different for the initial object types are left to be described. The formation of the new entity type called BUSINESS ASSOCIATE is represented graphically by a triangle which is also called an is-a relationship. Definition: When a generic concept is divided into subconcepts (BUSINESS ASSOCIATE is split into CUSTOMER and SUPPLIER), the result is a specialization.
Specialization is the reverse of generalization. The specialized objects inherit the properties of the generalized object. Apart from these inherited attributes the specialized object types may possess their own attributes as well. Graphically, specialization and generalization are represented in the same way. For this reason, the linking connections in the illustration are not drawn as arrows indicating a direction.
ARIS Methods
Data View
4-32
Figure 4.2.1-9: Generalization/Specialization
Whereas specialization primarily supports a top-down procedure for creating a data model, generalization is used to support a bottom-up procedure. In a specialization, the completeness and disjunctiveness (alternative) of the developing subsets can be specified as they are created. Non-disjunctive subsets occur when the occurrence of one object may be seen in one subset and also in the other subset. For the example given above, this means that a customer can be a supplier at the same time. If an occurrence can only be allocated to precisely one subset, these sets are disjunctive. When all specialized object types which are possible for one specialization criterion are listed for one generalized object type, this is complete specialization. For example, the HUMAN BEING entity type can be specialized into the MAN and WOMAN entity types (see Figure 4.2.1-10). Thus specialization from the Sex view point would be complete.
ARIS Methods
Data View
4-33
Figure 4.2.1-10: Completely Described Specialization
Combining these criteria therefore results in the following four occurrences that are established in order to specify a generalization/specialization more precisely: disjunctive/complete, disjunctive/not complete, non-disjunctive/complete, non-disjunctive/incomplete.
Aggregation Definition: Aggregation describes the formation of new object types by combining existing object types. In this context, the new object type can be a repository of new properties.
Aggregation is expressed in the ERM by the formation of relationship types (see Figure 4.2.1-11). The aggregation of the entity types PRODUCTION ORDER and ROUTING creates the new object ORDER ROUTING.
ARIS Methods
Data View
4-34
Figure 4.2.1-11: Example of Aggregation
The aggregation operator, however, can also be applied to relationships. An existing relationship type is then treated as an entity type and can thus become the starting point for creating new relationships. An example illustrating this is shown in Figure 4.2.1-12. A first aggregation is used to form the ORDER ROUTING relationship type from the PRODUCTION ORDER and ROUTING entity types.The production order number key attributes (PONO) and routing number (RNO) form the complex key to the order routing.Now, multiple operations can be allocated to the order routing. Therefore, the ORDER OPERATION relationship is formed between the ORDER ROUTING and OPERATION relationship types. Since relationships can only be created between entity types, the original ORDER OPERATION relationship type needs to be reinterpreted. In Figure 4.2.1-12 this is illustrated by a boxed-in diamond.Afterwards, this reinterpreted relationship type is treated as a "normal" entity type. To illustrate the origin of the relationship type the connections of the entity types participating in the origin of the relationship type are drawn to the diamond. The connections from the reinterpreted relationship type that form new relationships will only be taken to the edges of the square and will not touch the diamond inside the symbol. Although as a general rule it is possible to replace the complex key creation process traceable. with simple
keys, the complex keys will be included because they make the data model's
ARIS Methods
Data View
4-35
Figure 4.2.1-12: Aggregation with Reinterpreted Relationship Types
In an ERM, a complex structural unit is split into a transparent structure. Since the relation to the overall complex might become obscured, complex objects in the form of data clusters are introduced. Definition: A data cluster describes the logical view onto a number of entity and relationship types of a data model that are needed in the description of a complex object.
Data clusters as well as entity and relationship types can be part of a data cluster. Unlike entity and relationship types, data clusters can be freely arranged in a hierarchy and thus, in the creation process of a data model, mainly support a topdown procedure. In combining and consolidating submodels during a bottom-up approach the formation of data clusters can be very helpful as well. Figure 4.2.1-13 graphically displays a data cluster. As shown in Figure 4.2.1-14, the data cluster represents a logical view onto a number of entity and relationship types. The CUSTOMER, TIME, ORDER HEADER, ARTICLE and ORDER ITEM entity and relationship types are needed to describing the complex CUSTOMER ORDER object.
ARIS Methods
Data View
4-36
Figure 4.2.1-13: Data Cluster (Graphic Symbol)
Figure 4.2.1-14: Data Cluster View of Several Objects
Grouping Definition: Through grouping groups are formed from the elements of an entity set
In Figure 4.2.1-15 for example, all OPERATING RESOURCES are combined into an OPERATING RESOURCES GROUP. The operating resources group is an independent object which can be described more precisely by additional attributes (name of the operating resources group, number of operating resources) not contained in the individual operating resources. Other examples are the grouping of workstations into departments or the combination of order connection items into orders.
ARIS Methods
Data View
4-37
Figure 4.2.1-15: Grouping
4.2.1.2.2
Extending Cardinalities
When referring to cardinalities, we have so far only mentioned the upper limit of possible relationship occurrences. The cardinalities in Figure 4.2.1-16 indicate that a project can be assigned a maximum number (m) of employees and one employee can participate in a maximum number (n) of projects.
Figure 4.2.1-16: Upper/Lower Limit (1)
Besides this information on the upper limit, the lower limit may also be useful for specifying the minimum number of relationship occurrences. For this purpose, the cardinalities can be expressed as a pair of letters (a,b), for example (see Scheer, Business Process Re-engineering). The letter pair (a1, b1) in Figure 4.2.1-17 indicates that every project can participate in at least a1 and at most b1 relationship occurrences of the WORKS IN type, signifying that every project can be assigned at least a1 and at most b1 employees. Letter pair (a2, b2) indicates that one employee can participate in at least a2 and at most in b2 projects.
ARIS Methods
Data View
4-38
Thus, every relationship is expressed by two degrees of complexity (minimum, maximum). The lower limit often receives values 0 and 1, the upper limit's range of values is defined as 1 max * (where * any number). A lower limit of min = 0 indicates that an entity can participate in one relationship, but it is not mandatory. A lower limit of min = 1 indicates that an entity must participate in at least one relationship. The lower limits in Figure 4.2.1-18 indicate that an employee can participate in a relationship but does not have to (min = 0) while a project has to participate in at least one relationship (min = 1). What is expressed here is that there can be employees who are not assigned to a project. On the contrary, however, at least one employee must be allocated to every project.
If minimum values of only 0 or 1 and maximum values of 1 or * are permitted, the following four cases of a (min,max) - notation be distinguished: (1,1), (1,m), (0,1) and (0,m). In this case the following notation can also be used (see Schlageter/Stucky, Database systems 1983, p. 51): 1 c m cm (corresponds to (1,1)), (corresponds to (0,1)), (corresponds to (1,m)), (corresponds to (0,m)).
Figure 4.2.1-19 shows the example of Figure 4.2.1-18 using this notation.
ARIS Methods
Data View
4-39
4.2.1.2.3
Identification and Existential Dependence
Due to extending the cardinalities by means of specifying lower and upper limits as discussed in Chapter 4.2.1.2.2, certain dependencies between data objects can now be defined. By definition, relationship types and reinterpreted relationship types exist because of the existence of the entity types that link them; thus, they do not exist in isolation. This means that they are dependent on other entity types both existentially and in terms of identification. In addition, there are also entity types that, although they have their own key attribute are still dependent on the existence of other entities. These dependencies originate from a grouping operation, for example. Thus, as shown in Figure 4.2.120, a department is only meaningful if it is assigned at least one workstation and in return, the definition of a workstation is only meaningful if it is assigned to a department. As shown in Figure 4.2.1-20, these existential dependencies are expressed by the degrees of complexity. In a (min,max) notation, this is specified by (1,1) and (1,*). The definition of existential dependencies within the data model results in conditions for the referential data integrity following subsequent conversion. In simple terms this means that complying with these conditions will guarantee that the consistency of the database contents can be maintained - even after certain transactions have been carried out. In the example below this means that a department can only be deleted when all workstations assigned to this department are also deleted.
Figure 4.2.1-20: Existential Dependence
ARIS Methods
Data View
4-40
4.2.1.2.4
Modeling of Technical Terms of the Company - Technical Term Model
In modeling, especially in data modeling, we have to deal with one difficulty that occurs frequently. This is the variety of terms defining information objects in larger companies. What is understood by the term Order in the purchasing department is totally different from what people in the production department associate with it. However, acceptance of the information gained can be increased substantially by the consistent use of terminology throughout the company or the department. Accordingly, the method set of ARIS contains technical term models which allow the different terms to be managed in the sense of synonym management for objects, and also enable maintenance of the relationships between the objects of the data model (entity type, relationship type, etc.) and the technical terms in use by the company. For the purpose of illustrating these relationships, the Technical terms object type is introduced. Now, multiple technical terms can be assigned to every information object of the data model. An example illustrating this is shown in Figure 4.2.1-21.
Figure 4.2.1-21: Technical Terms
Technical terms can be related to each other and can be displayed in a hierarchy. Figure 4.2.1-22 explains the usage of the various connection types between technical terms.
ARIS Methods
Data View
4-41
Figure 4.2.1-22: Connections between Technical Terms
ARIS Methods
Data View
4-42
The technical terms defined in the technical term model can also be used in other model types that contain information objects, for example in process chains for illustrating a function's input/output data.
4.2.1.2.5
eERM Attribute Allocation Diagram
Data models in the form of eERM illustrations which only display entity types and relationship types, very often have quite a complex structure. If the ERM attributes were included in these models, they would no longer be legible. By means of eERM attribute allocation diagrams, you can assign the ERM attribute allocations to every entity and relationship type in a separate model. The eERM object type (entity type or relationship type) can be included in this model in the form of an occurrence copy and the relationship to the ERM attributes can be modeled. Distinctions can be made between a key attribute, external key or a descriptive attribute for the linked ERM attribute. An example of this is illustrated in Figure 4.2.1-23.
Figure 4.2.1-23: Allocation of ERM Attributes to an Entity Type
Apart from representing and allocating individual ERM attributes you can also display attribute type groups and their allocations in this model type.
ARIS Methods
Data View
4-43
Definition:
An attribute type group represents the grouping of ERM attributes of an entity type which are semantically related. For example the ERM attributes of an entity type that in their entirety form a secondary key can be combined to form an attribute type group.
Attribute type groups are represented as follows:
Figure 4.2.1-24: Illustration of an Attribute Type Group
In the appendix of this manual, you will find a summary of the possible relationships of the ERM attribute allocation diagram.
ARIS Methods
Data View
4-44
4.2.1.3 4.2.1.3.1
Alternative Forms of Representation SAP SERM
Apart from the representation form described here, other ERM representations are commonly used. Frequently, relationship types are not represented as individual objects; types. One such form of representation is the SERM representation (structured entityrelationship model) developed by Sinz (see Sinz, Entity Relationship Model 1990). The data structure's direction of development becomes visible by displaying the primary and dependent data objects using directional graphs and arranging the model objects from left (strong entity types) to right (weak entity types and relationship types). The main difference between SER models and the modeling based on the eERM method described so far lies in the graphical representation. The modeling technique developed by SAP AG in Walldorf/Germany as part of its modeling methodology links the concepts of the SER approach with the eERM approach presented here (see Keller/Hechler, Information Model 1991). In this context, no graphic distinction is made between entity types and relationship types during object formation. The dependencies between the information objects are expressed by the complex relationships of the arrow representations. A distinction is made, however, between hierarchical, aggregate and referential relationships (see Figure 4.2.1-25) Hierarchical relationships define a unilateral existential dependence between information objects. Aggregate relationships correspond to the formation of relationship types based on the eERM approach. Referential relationships describe logical dependencies between reinterpreted entity types and primary entity types as exemplified by the eERM approach. Specialization is symbolized in the same way as in the ERM approach. rather, they are indicated as connections between entity types. Relationship types that have their own attributes are then shown as (weak) entity
ARIS Methods
Data View
4-45
To clarify this, Figure 4.2.1-25 shows an example of the eERM and the way it appears following SAP ERM conversion (see also: Seubert, SAP data model 1991, p. 94). This clearly shows that the fundamental subject contents can be transferred to this form of representation without any loss of information. The SAP ERM may be considered as a type of representation of data models after the creation process has been completed. Because of the graph-oriented arrangement of the information objects in the SAP ERM, faster navigation and orientation is supported particularly in larger data models.
ARIS Methods
Data View
4-46
Figure 4.2.1-25: eERM and SAP ERM Representations
ARIS Methods
Data View
4-47
4.2.1.3.2
IE Data model
The IE data model matches the data modeling notation employed by the CASE Tools Information Engineering Facility (IE) of Texas Instruments Inc. Just like the SAP SERM notation, the IE notation does not provide separate object types for relationships between entity types. The following Figure 4.2.1-26 gives an example of a data model in IE notation.
Figure 4.2.1-26: Data Model in IE Notation
ARIS Methods
Data View
4-48
4.2.1.3.3
SeDaM model
The SeDaM (semantic data model) data model notation is a BASF AG notation. This notation also does not provide separate object types for relationships between entity types. There is no strict arrangement of entity types from left to right (see SAP SERM notation). The Data cluster and Generalization type object types are also available. Figure 4.2.1-27 shows an example of a data model in SeDaM notation.
Figure 4.2.1-27: Data Model in SeDaM Notation
In the appendix you will find a summary of all possible relationships of the SeDaM model.
ARIS Methods
Data View
4-49
4.2.1.4
Summary of the Most Important Concepts and Forms of Representation of the eERM
The concepts and representation forms of the structural elements and design operators of the extended entity relationship model (eERM) are summarized in Figure 4.2.1-28 (see Scheer, Business Process Re-engineering 1994, p.45).
ARIS Methods
Data View
4-50
Figure 4.2.1-28: eERM: Concepts and Forms of Representation
ARIS Methods
Data View
4-51
4.2.1.5
Document Type Definition
A model of the DTD type (document type definition) describes the rules according to which an XML document of a specific type must be constructed. The description is in the form of element type declarations. You can define the general structure of a document category for example using a DTD. A valid document of a document type defined in the DTD can be created as an XML document. This has the advantage that the document can be processed by various programs together with the corresponding DTD. The model must be constructed from an object of the Element type type in a strict hierarchy. The source object may not have any incoming connections. Furthermore, connections must always run from the superior object to the subordinate object. While you can describe all element types in a DTD model for clear document structures, with complex structures you can also declare an element type in an assigned DTD model. If you work with assignments the assigned model must contain the complete description of the element type. Using the DTDExport.rsm report you can create a DTD file from the basic model covering the entire DTD model structure. If you have document type declaration in the form of a text file, you can use the DTDImport.rsg report to generate a DTD type model from it.
4.2.1.5.1
Element Types
The essential components of a DTD are element types. Instances of element types that occur in the DTD model hierarchy may occur in a valid XML document and are called elements. Each element type is described by its content and its attribute types. Three types of element types can be distinguished by their content: Element types with text as content Element types without content Element types with text and/or other element types as content.
ARIS Methods
Data View
4-52
To describe an element type that only has text as content you place an object of the Element type type with the required name and an element of the Content type with the #PCDATA symbol. Finally you draw a connection of the contains type between the element type and the content.
Figure 4.2.1-29: DTD Element Type with Pure Text Content
To describe an element type that has no content you place an object of the Element type type with the required name and an element of the Content type with the #EMPTY symbol. Finally you draw a connection of the contains type between the element type and the content. A typical example of an element type without content is the <img> day in HTML. The essential benefits of empty element type are that they can have useful attributes such as the SRC, ALIGN, ALT and ISMAP attributes of img day. The most complex form of an element type is an element type with mixed content. In this case text or element types can be assigned to an object of the Element type type. To describe the form in which assignments are linked to each other, operators can be used. The possible connections between the element type and the assignments describe how often an assignment can occur in the element type content. You have the sequence operator and the XOR rule to link assignments. If only one of a specified number of assignments is allowed in the content of the element type described, the assignments must be linked with each other by an XOR rule. If several assignments are allowed in the content of the element type described but only in a certain order, they must be linked with each other by a sequence operator. In order to fix the required order clearly, specify the required position for the assignment on the connection between the operator and the assignment.
ARIS Methods
Data View
4-53
EXAMPLE
(|)
#PCDATA
Figure 4.2.1-30: Element Types with Mixed Content and Conversion in the DTD
Assignments can also be linked to the element described without operators. In this case it is assumed that the sequence link will be in any order.
4.2.1.5.2
Connection Types
Assignments in the content of an element type can occur with varying frequency. The number of permitted occurrences of an assignment in the content of the element type is determined by the connection type between element type and assignment.
ARIS Methods
Data View
4-54
You can choose between the following connection types: has any number of times has at least once has at most once has exactly once The following table explains the various connection types and displays the symbol that is used in the DTD that is produced to clarify the occurrences. Connection Type has any number of times Description
Symbol
The assignment must not necessarily occur in the * content of the element type described. If it occurs it can occur once or a number of times (min = 0, max = any positive whole number).
has at least once
The assignment must occur in the content of the element type described and it can happen more than once (min = 1, max = any positive whole number).
has at most once
The assignment must not necessarily occur in the ? content of the element type described. If it occurs it must only occur once (min = 0, max = 1).
has exactly once
The assignment must occur in the content of the element type described. But it may only occur once (min = 1, max = 1).
no symbol
4.2.1.5.3
Attribute Types
As well as the description of the structure a DTD can also contain declarations of attribute types. Attribute types describe the properties of an element type. They are always assigned to an element type. Simple attribute types and enumeration attribute types can be declared in a DTD.
ARIS Methods
Data View
4-55
To define a simple attribute type, 1. place an object of the Attribute type type with the required name on the model and 2. drag a connection from the element type whose property is described by the attribute type to the new attribute type. 3. then open attribute editing to give further information for the attribute type declaration. This information includes: Data Type of the Attribute Value Attribute Default Default value
4.2.1.5.3.1
Data Type of the Attribute Value
To specify the data type of the attribute value, maintain the Data type attribute. The following table explains the specified data types: Data type CDATA ID Description Strings can be used in the attribute value. A unique identifier can be used in the attribute value. If the value is not unique the XML processor sends an error message. IDREF A reference to an identifier that is defined elsewhere in the document can be used in the attribute value. When an identifier that has not been assigned in the current XML document is used as a value the XML processor sends an error message.
ARIS Methods
Data View
4-56
Data type IDREFS
Description The attribute value can consist of several attribute values of the IDREF type that are separated from each other by spaces. When an identifier that has not been assigned in the current XML document is referred to in the attribute value, the XML processor sends an error message.
ENTITY
A reference to a binary entity that has been removed that is declared within the DTD can be used as an attribute value.
ENTITIES
The attribute value can consist of several attribute values of the ENTITY type that are separated from each other by spaces.
NMTOKEN
Any combination of letters, numbers, periods, dashes, semi-colons or underscores can be used as an attribute type.
NMTOKENS
The attribute value can consist of several attribute values of the NMTOKEN type that are separated from each other by spaces.
NOTATION
A reference to a notation that is declared in the DTD can be used as an attribute value.
The NMTOKEN value is maintained as the default for the data type attribute.
4.2.1.5.3.2
Attribute Default
You can select one of the following values for the Attribute default attribute: #REQUIRED #IMPLIED #FIXED When the attribute default value for an attribute type is set to #REQUIRED and this attribute is maintained in the XML document for an element, a valid value must
ARIS Methods
Data View
4-57
definitely be specified for the attribute. If the value is missing the XML processor sends an error message. When the attribute default value for an attribute type is set to #IMPLIED and this attribute is maintained in the XML document for an element, specifying a value for the attribute is optional. When the attribute default value for an attribute type is set to #FIXED, a fixed value is used for the attribute value. This value must be specified in the Default value attribute. If the attribute is not maintained in the XML document, the XML processor behaves as if it were in the document. The #IMPLIED value is maintained as the default for the Attribute default attribute. To declare an enumeration attribute type, place an object of the Enumeration attribute type type with the required name on the model and drag a connection from the element type whose property is described by the enumeration attribute type to the new attribute type. Then place an object of the Enumeration type and enter the values that the enumeration attribute type can accept as the name. The individual values must be separated by commas. If the list of values contains more than 81 characters, distribute the values among several enumeration objects. Now create a connection between the enumeration attribute type and the enumerations. Finally maintain the value from the enumerations that is to be accepted as a default in the Default value attribute.
Figure 4.2.1-31: Element Type with an Enumeration Attribute Type
ARIS Methods
Data View
4-58
Information on the Description/Definition of DTD models' attribute and the element types contained therein are inserted as comments into the DTD that is generated by the DTDGenerator.rsm report. There are several model attributes available to declare parameter entities, internal or external entities and notation in a DTD. Parameter Entity To declare a parameter entity, enter the following in the specified order: the symbol name, a key word and a uniform resource identifier for the required parameter entity declaration. The symbol name can be used as a parameter entity reference in the current DTD. SYSTEM and PUBLIC can be used as key words. To use the parameter entity to refer to a file that is only known and used within your company enter the key word SYSTEM. But if you refer to a file that is a component of a standard library, enter PUBLIC. An example of a URI that follows the key word PUBLIC is: "-//w3c//ENTITIES Latin//EN//HTML" "http://www.w3.org/DTD/ISOLAT1.ent". Internal Entity To declare an internal entity, enter the following in the specified order: the symbol name and a text that are used to declare a general internal entity. Enter a space between the name and the text and write the text in quotation marks. If an XML document for the current DTD contains an entity reference with the specified symbol name, this name will be replaced by the specified text. External Entity To declare an external entity, enter the following in the specified order: a symbol name, a key word,
ARIS Methods
Data View
4-59
a uniform resource identifier (URI) and a notation that are used to declare a general external entity. The symbolic name can be used as an entity reference in an XML document in the current DTD. SYSTEM and PUBLIC can be used as key words. To use the external entity to refer to a file that is only known and used within your company enter the key word SYSTEM. But if you refer to a file that is a component of a standard library, enter PUBLIC. A URI tells the XML processor where the object that the external entity refers to can be found. An example of a URI, that follows the key word SYSTEM is: "c:\images\test.gif". An example of a URI that follows the key word PUBLIC is: "-//w3c//ENTITIES Latin//EN//HTML" "http://www.w3.org/DTD/ISOLAT1.ent". The notation at the end of the entry tells the XML processor about the type of object the external entity refers to. The notation used must be declared in the current DTD. If, for example, you use the URI of the first example in your entity declaration, first declare a notation for the GIF data format in the DTD and insert NDATA.GIF to complete your entry in this attribute type. Notation To declare a notation, enter the following in the specified order: a symbol name, a key word and a uniform resource identifier (URI). This information tells the XML processor how it should deal with objects of this type that occur in the XML document of the current DTD. The symbol name for the notation can be used in attribute and entity declarations in the current DTD.
ARIS Methods
Data View
4-60
SYSTEM and PUBLIC can be used as key words. For example, if you declare a notation for objects in GIF format and want to tell the XML processor to display objects of this type with the locally available Internet Explorer, enter the key word SYSTEM. If, however, you declare a notation for files of the TEX type and to do this would like to refer the XML processor to a generally accessible resource or source, enter PUBLIC as key word. The uniform resource identifier tells the XML processor where it can find the application or information that contain the instructions for dealing with objects of the specified type. The URI for the GIF notation with the key word SYSTEM could be for example "c:\Program Files\Internet Explorer\Iexplore.exe" while "ISBN 0-20113448-9:://NOTATION TeX//EN" can be entered as the URI for notation with the key word PUBLIC.
4.2.1.5.4
Testing DTDs
When you have created the required DTDs and want to test these in two steps, you can activate or disable parts of the DTD that are not used in the current test using the Specific section object type. If you want to hide element types in a DTD that are subordinate to a specific section, activate the Ignore attribute of the corresponding specific section. If you use the DTDImport.rsg report script to turn a text DTD containing a conditional section into a DTD type model, the content of that section will not be included. A model of the DTD type can be assigned to data items of the ARIS method. The data items include: Cluster/Data model Package Entity type Relationship type Technical term
ARIS Methods
Data View
4-61
4.2.1.6
Material Flow Modeling - Material Diagram
In order to illustrate the material flow in process models(eEPC (material flow), PCD (material flow), the material types are allocated to the individual functions of the business process in the form of function input or output. Just as in the allocation of information objects to functions (the transformation of information is represented by means of functions), this allocation represents the transformation of input material types to output material types. In the material diagram you can define material types, arrange them in hierarchies and classify them in material classes. Definition: A material type typifies individual materials which have exactly the same material characteristics. Similar material types can be combined to form a material class. In doing so, the question of similarity can be considered for various aspects of classification. Thus one material type can be assigned to several material classes.
Definition:
Material types can be allocated to packaging material types. This indicates that certain material types can only be transported in particular packaging material types. Packaging material can also be defined, arranged in hierarchies and classified. This allows, for example, the structure and restrictions of complex packaging trade units to be illustrated. Definition: A packaging material type typifies individual packaging materials which have exactly the same properties (e.g. material characteristics). Similar packaging material types can be combined in a packaging material class In doing so, the question of similarity can be considered for various aspects of classification. Thus, one packaging material type can be assigned to several packaging material classes.
Definition:
Figure 4.2.1-32 illustrates an example of a materials diagram with its hierarchy levels and classifications.
ARIS Methods
Data View
4-62
Figure 4.2.1-32: Example of a Material Diagram
4.2.1.7
Modeling the Data Warehouse Structure
The Data Warehouse structure diagram is used to describe the structure of a Data Warehouse. Primarily, it gives a static description, i.e. the relations of the data to each other and their locations. In the ARIS architecture this type of description is realized in Data view. The relations of the information as well as their layout to each other are considered to be the central aspect. The data dimensions are described by the Info cube. The interplay of the dimensions is presented by the Star scheme (see Figure 4.2.1-33 In the process, one dimension can serve as a key for connecting other dimensions. The objects of the individual dimensions can accept specific values, which are cataloged in the fact tables and are exactly specified through key performance indicators. The dimension tables with their key attributes and their features describe the dependencies. The hierarchical relationships of the features with each other are described by tree structures. Finally, the dimensions can be allocated to master data tables with the aid of the structure diagram.
ARIS Methods
Data View
4-63
Figure 4.2.1-33: Data Warehouse in the Star Scheme
4.2.1.8
Authorization Hierarchy
The authorization hierarchy diagram is used in role modeling and organizational modeling. It depicts the relationships of authorizations that were defined in the role diagram. Superior and subordinate authorizations are defined so that a logical structure is assured and authorization conflictsare avoided. The authorization hierarchy diagram is closely associated with the role diagram. The listed
ARIS Methods
Data View
4-64
authorizations are used in the role description to define the requirement profile. The structure corresponds to that of a function tree.
Figure 4.2.1-34: Authorization Hierarchy
4.2.1.9 4.2.1.9.1
Activity-Based Cost Calculation Data Model CD Diagram
The application area of the CD diagram (cost driver diagram) is the activity-based cost calculation (see ARIS ABC). The hierarchy of the cost drivers is shown in the CD diagram. Definition: A cost driver is a unit of measurement/reference value that provides information on cost sources of a specified process. The reference value should be an operational value that is easily derived from the available information sources and remains proportional to the cost estimation.
ARIS Methods
Data View
4-65
Therefore, cost drivers can only be defined for performance amount variable or induced processes. Cost drivers cannot be defined for performance amount-neutral processes, e.g., "Managing a department". An example of a cost driver would be the "Length of a street" for the "Blacktopping a street" process. The hierarchy of cost drivers is mapped in the CD diagram by directed connections of the "determines volume of" type. The "CD relationship numerator" and "CD relationship denominator" attributes must be maintained on these connections. If "CD relationship denominator" is not maintained a value of 1 is assumed. The quotient of these two attributes determines the quantity relationship between the two cost drivers for the process calculation. Figure 4.2.1-35: shows an example of this. There are two cost drivers, "Number of cars (limousines)" and "Number of doors". In order to show that each limousine has four doors, the "CD relationship numerator" attribute must be set to "4" on the connection from the "Number of cars (limousine)" cost driver to the "Number of doors" cost driver.
Figure 4.2.1-35: Example of a CD Diagram
The cost drivers are allocated to the individual processes in the process view tables. The usage factor for each function in the processes can be determined automatically from the cost driver hierarchy.
ARIS Methods
Data View
4-66
4.2.1.9.2
Cost Category Diagram
The area of application for the cost category diagram is the activity-based cost calculation (ARIS ABC). The hierarchy of cost categories is shown in cost category diagrams. Definition: Cost categories are used in the systematic organization of all costs that arise from the creation and evaluation of cost objects (performances). The question is: What costs have been incurred?
For example, material costs are the cost categories for the use of materials and depreciation the cost category which records the decrease in value of assets. The total costs can be structured according to different criteria. If costs are divided according to the category of the production factors used, this results in a structuring of personnel costs (e.g., salaries, commissions), material costs (e.g., costs of raw materials, depreciation of machines), capital costs, costs for third-party service providers (e.g., transport costs, electricity costs) and costs for taxes, fees and contributions. Cost categories can be further divided according to the most important operating functions such as purchasing costs, warehousing costs, manufacturing costs, administration costs and sales costs. Both structures can be refined even further. The hierarchy of the cost categories is illustrated by directed connections of the "is superior" type. An important attribute for cost categories is the "performance scale". It describes the unit in which cost category performance is measured (e.g., wage hours and square meters for room costs). Figure 4.2.1-36 gives an example of a cost category diagram which corresponds to the above-mentioned structuring using the category of production factors used with a further sub-structuring of the personnel costs.
ARIS Methods
Data View
4-67
Figure 4.2.1-36: Example of a Cost Category Diagram
In ARIS ABC a cost category diagram can be assigned to an activity-based cost calculation instance. A cost center view (overview table) lists all cost centers that are to be analyzed in the activity-based cost calculation instance. Any number of cost categories can be defined there for each cost center and the necessary values set (depending on calculation method, cost rates, cost volumes and/or cost center performance). Other facts can be described for each cost center in the cost center view (overview table) by means of a cost center view (detail table).
ARIS Methods
Data View
4-68
4.2.1.10
Project Management Data Model
4.2.1.10.1 Information Carrier Diagram

The information carrier diagram is an optional Project Management component with ARIS Toolset. It is assigned to the requirements definition of the data view and records incoming and outgoing data in the form of documents, logs, and ARIS models. As an assignment of a cluster occurrence, ARIS models can be described in the PPC (project process chain, see requirements definition of the process view). As a result, data can be generally specified in the associated cluster. The documents that are actually required, e.g., a word processing file, can thus be displayed explicitly and called from ARIS Toolset using the External 1 to External 3 attributes.
Figure 4.2.1-37: Information Carrier Diagram
ARIS Methods
Data View
4-69
4.2.2 4.2.2.1
Design Specification Relations Diagram, Attribute Allocation Diagram
In the design specification, the logical data structures designed in the requirements definition are transformed into a form of description on which concrete database systems can be built. ARIS provides the relational model for this. The relations diagram and the attribute allocation diagram are provided to define existing relations and attributes and their relationships with the information objects introduced in the requirements definition. The necessary relations can first of all be defined in the relational diagram. Definition: A relation describes an entity type using its attributes. It is a subset of the possible combinations of the value ranges of the individual attributes.
Relations are shown in graphic form as follows:
Figure 4.2.2-1: Graphical Representation of the Relation
Every eERM entity type now constitutes a relation in the relational model. When converting the eERM model's relationship types, the cardinality is a very important aspect in deciding whether a separate relation will be created for the relationship type. Unlike 1:n relations, n:m relations need to be illustrated in their own relations. For every single relation, the relational diagram can indicate which entity or relationship types of the eERM model is represented. Apart from this, a relation can be further specified by listing its attributes. Whether the corresponding attribute serves as a key attribute, an external key attribute, or
ARIS Methods
Data View
4-70
as a descriptive attribute may be defined by the choice of the corresponding connection linking the relation and the attribute. In turn, the relationship to the ERM attribute of the requirements definition it maps can be created for every single attribute.
Figure 4.2.2-2: Assignment of Requirements Definition Attributes and Data Objects
In order to reduce the complexity of the figure, the attributes of every relation can be defined in an attribute allocation diagram linked with the relation itself. An example illustrating this is shown in Figure 4.2.2-3.
ARIS Methods
Data View
4-71
Figure 4.2.2-3: Attribute Allocation Diagram
The requirements definition data clusters are converted in the design specification by a separate object type, the view. Based on the definition of the data clusters, the View is defined as follows: Definition: A view describes the logical view onto a number of relations.
The relations assigned to a View can also be illustrated in a relation diagram. An example is shown in Figure 4.2.2-4.
ARIS Methods
Data View
4-72
Figure 4.2.2-4: Definition of a View
1:n relationships in the ER model are not mapped in the relations diagram by separate relations. The relationship is mapped by integrating the key attribute of the superior entity type into the relation of the subordinate entity type. In this process, the original key attribute becomes the relation's external key. Which attribute of the relations model maps the ER model's relationship types, can also be represented by a connection in the relations diagram (see Figure 4.2.2-5).
Figure 4.2.2-5: Allocation of ERM Relationship Type to the Attribute
ARIS Methods
Data View
4-73
In the appendix of this manual you will find a list of all object and relationship types of the relational model.
4.2.2.2
Modeling of System Interface Models - System Attributes, System Attribute Domains
The System attributes model type is primarily designed to perform data exportoriented tasks from the ARIS Toolset. This model type allows you to arrange entity types, events, technical terms, functions, information carriers, organizational units and persons in a hierarchy and to specify them uniquely and completely according to their data processing requirements. These data can be typified according to the usual database requirements as primary and external keys, descriptive and mandatory fields. In order to determine the domain types of these data objects, here again you can assign the System attribute domain model type (see below). In contrast to the ERM attributes, the main feature of the system attributes is the representation and management of interface-oriented data. In order to ensure high flexibility with the contents to be exported, the system attribute objects contain two value fields which can be filled with the relevant information. The following example shows an excerpt from the project header definition of a project defined in ARIS Toolset for transmission to a project management system.
ARIS Methods
Data View
4-74
Figure 4.2.2-6: Example of "System Attributes" Model
The System attribute domain model type defines the system attribute objects according to the data type; it specifies, for example, the domain type (char, int, date,...) and the field length. It is mainly used to provide information when data are exported to external systems.
Figure 4.2.2-7: System Attribute Domain
ARIS Methods
Data View
4-75
4.2.3
Implementation - Table Diagram
A database system's tables and fields can be described in the table diagram. Figure 4.2.3-1: gives a graphic representation of tables and fields.
Figure 4.2.3-1: Graphical Representation of Table and Field
The individual fields assigned to this table can be shown for each table. For further specification, a sorting index and its domain can be assigned to every individual field. An example illustrating this is shown in Figure 4.2.3-2:.
ARIS Methods
Data View
4-76
Figure 4.2.3-2: Field Allocations
Since relations of the relational model are not necessarily converted into tables and fields on a 1:1 basis (e.g. for reasons of database performance), multilateral relationships between tables and relations or entity types may occur. By choosing the respective connections, these relationships can be illustrated in the table diagram. The data clusters defined in the requirements definition or the views defined in the relations model are represented in the table diagram by the View (physical) object. Database tables and fields used in the company do not necessarily have to be converted and documented by defining a relational scheme. That is why the realization relationships can be illustrated not only between relations (or attributes) and tables (or fields) but also between entity types (or ERM attributes) and tables (or fields).
ARIS Methods
Data View
4-77
It can either be shown which relations and attributes are produced by the tables and fields or - leaving out the relational definitions - which entity types, relationship types and ERM attributes are mapped by the tables and fields illustrated. Figure 4.2.3-3: shows examples of the two types of representation.
Figure 4.2.3-3: Allocation of Objects of the Requirements Definition and the Design Specification
In order to define the exact location of certain tables and fields in the company, it must also be possible to define every single specimen of a table. The same applies when organizational unit access privileges to tables and fields are to be determined. The Table object type introduced earlier determines the logical structure of a
ARIS Methods
Data View
4-78
physical table and its fields at the "Type level". Multiple specimens of every table thus defined may be available - stored on different media - at different locations in a company. As a means of illustrating this fact, the Table (specimen) and Field (specimen) object types are introduced. Using these objects, the specimen count of a table or a field can be determined exactly. This connection is illustrated in Figure 4.2.3-4:.
Figure 4.2.3-4: Table Specimens
You will find a list of objects and relationships for the table diagram in the appendix.
ARIS Methods
Organization View
4-79
4.3 Organization View

4.3.1 4.3.1.1 Requirements Definition Organizational Form of the Company
Companies are complex social structures which are divided into handy units. To deal with the complexity, patterns are defined and rules are established. The result of this process is called organization. Until recently, the role of organizational analysis as an aspect of developing information systems has rarely been the object of research. But newer business concepts such as Lean Production, Lean Management or CIM are closely allied with the organizational setup of the area under consideration. For this reason, the ARIS architecture has an independent descriptive view for organization. In a company's organizational configuration a distinction can be made between the organizational structure and the procedural structure. The organizational structure encompasses the rules by which the company is statically structured. The procedural organization contains those rules aimed at the tasks to be fulfilled by the company. This task-related structure in the sense of distributing functions to task performers is dealt with in the control view of ARIS House. Basically speaking, the organization view is the component which allows the analysis of a company's organizational structure. The design of the perfect company organization with the aim of reducing coordination demands to a minimum depends on its business environment and its objectives. Therefore, universally valid perfect organization structures in the sense of reference structures cannot be defined. Exactly how the organizational units are structured may depend on various criteria. The functional structure is very common. Here, one department function
(purchasing, production, finance and accounting, sales) is given responsibility for all products and territories. The advantage of the fact that the employees are highly specialized is balanced by the disadvantage of the enormous demands in communication and coordination between the functional areas.
ARIS Methods
Organization View
4-80
Design and use of information systems has been geared towards this functional dissection of companies for a long time. However, when process chains are considered holistically as the cohesive processing of data objects of the same type, it is difficult to establish the interrelationship between the individual functions for such a structural setup. For this reason, the discussion of integrated data processing resulted in the demand for a consistent database which would support the different functions. The aim of functional integration, however, virtually eliminates our objective inherent in the functional structure to reduce complexity. Therefore, other criteria for breaking down the organization are often used when the objective is functional integration. This can be, for example, a breakdown by criteria such as areas or products. Figure 4.3.1-1 shows a diagram of a breakdown by products (see Scheer, Business Process Re-engineering 1994, P. 26 et seqq). The organizational units of an area-based organizational structure are specified in accordance with the local distribution of the company or of the company division. This kind of structure is particularly suitable for sales functions because regional factors such as varying legislation can be dealt with more appropriately.
Product 1 Function 1 Function 2 Function 3
Product 2
Product 3
Product n
Function n
Figure 4.3.1-1: Organizational Breakdown by Products
ARIS Methods
Organization View
4-81
A product-oriented organizational structure defines organizational units for products or product groups. Within a product group as many functions as possible that are relevant for this particular product group are integrated. The objective of this procedure is to reduce the demands in communication that occur in a functional structure. This, however, results in the necessity to mediate between the product group-based subsystems. In order to counteract these effects often hybrid organizational forms are created. Figure 4.3.1-2 shows an example of Purchasing (see Scheer, Business Process Reengineering 1994, p. 26 et seqq).
Product group 1 Central purchasing
Planning
Product group 2 Supplier selection Terms and conditions
Product group 3
Ordering Checking and auditing invoices

Figure 4.3.1-2: Hybrid Organizational Forms
Using a purely functional structure would indicate that central purchasing were responsible for all product groups. In this organizational form, synergy effects that arise between the product groups can be exploited; but a single purchasing procedure for all sub-functions would result in major coordination problems. When the purchasing functions are split up according to the various product groups, individual purchasing departments must be established for every product group to carry out all purchasing functions. When selecting vendors or negotiating framework contracts, for example, synergy effects can only be obtained at the expense of high coordination efforts.
ARIS Methods
Organization View
4-82
As illustrated in the breakdown in Figure 4.3.1-2 those purchasing functions for which high synergy effects are expected are broken down functionally, i.e. they are carried out by a central purchasing department. Functions which have taken into account particular demands and restrictions of individual project groups are divided by product group in an object-oriented manner. These functions can thus be integrated in the process procedures of the individual project groups immediately. This means that the processes are handled operatively in the decentralized units while the relationships between the decentralized units are considered at the superior and central coordination level. These flexible organizational forms are given special emphasis in the ARIS architecture due to their particular process-oriented approach. Strongly accountingoriented approaches such as the profit center concept require the formation of organizational structures where several division criteria are analyzed at the same time.
4.3.1.2
Organizational Chart
The organizational chart is a typical form of representing organizational structures. A chart of this kind reflects the organizational units (as task performers) and their interrelationships, depending on the selected structuring criteria. Definition: Organizational units are the performers of the tasks that must be performed in order to attain the business objectives.
The relationships are the links between the organizational units. An example illustrating this is shown in Figure 4.3.1-3. A distinction is made between various connection types linking organizational units in order to specify the hierarchical relationships more precisely. In this context, a connection can have one of the following meanings: is technical superior to is disciplinary superior to is a component of
ARIS Methods
Organization View
4-83
Whereas the functional responsibilities are shown in boxes, the organizational chart illustrates the distribution of the business tasks.
Figure 4.3.1-3: Organizational Chart
In order to show the individual positions in the company that have for example job descriptions, the separate Position object type is available. This object type is illustrated in Figure 4.3.1-4. Multiple positions can be assigned to one organizational unit. The meaning of the connections matches that between the organizational units. The positions and organizational units can be assigned to persons who hold those positions. ARIS also contains separate objects for persons which are illustrated in Figure 4.3.1-4 as well. The assignment of a person to an organizational unit indicates that this person is an assigned employee of the organizational unit. The association with an individual position defines the present job cover within the company. An example is shown in Figure 4.3.1-4.
ARIS Methods
Organization View
4-84
Figure 4.3.1-4: Organizational Chart with Position and Person Allocation
Organizational units and persons can also be assigned a type. Accordingly, for example, it can be defined for each organizational unit whether it is a department, a main department or a group; persons can be assigned to the Department head, Group leader or Project manager person types for example. The organizational unit type and person type objects are used to represent this typification. An example of the typification of organizational units and persons is shown in Figure 4.3.1-5.
ARIS Methods
Organization View
4-85
Figure 4.3.1-5: Person Types
Using these object types allows general business rules to be mapped, which are derived from concrete organizational units or persons within the company. In process chains, for instance, it can be specified that only certain person types are allowed to carry out one particular function or to access one particular information object. The modeling of the company's organizational structure is the starting point for the network topologies which are to be defined at the design specification level and which are supposed to support the organizational structure in the best possible manner. Network connections and network nodes that are situated in specified
ARIS Methods
Organization View
4-86
locations in the company are included in the definition of the network topology. Thus, the location of an organizational unit is the most important link between the requirements definition and the design specification in the organization view. Therefore, every organizational unit can be assigned its proper location as early as at the requirements definition level. An example illustrating this is shown in Figure 4.3.1-6.
Figure 4.3.1-6: Location Allocations
Locations can be placed anywhere in a hierarchy. A location can be an entire production plant, one particular building or - when performing a detailed analysis one individual office or even a single workstation in a room. This means that in the design specification, network nodes can be assigned to an organizational unit's individual workstations; accordingly that, for example, a total of 3 network nodes must be available in a particular office (room 202).
ARIS Methods
Organization View
4-87
Figure 4.3.1-7 shows an example of a location hierarchy.
Figure 4.3.1-7: Location Hierarchies
ARIS Methods
Organization View
4-88
4.3.1.3
Shift Calendar
Shift calendars can be assigned to personnel and material resources, and specify when a resource is mainly available. Shift calendars are assigned to resources in the organizational chart or the eEPC. Shift calendars can be assigned to any personnel or material resource. If there is a hierarchy of personnel resources, the calendar used is always the one found on the lowest hierarchy level. The shift calendar is a multi-level object model. On the lowest level are objects of the Break type. A break is the daily time interval within a shift during which no work is performed. The break is indicated by its relative start and its duration. Thus the relative start always relates to the shift to which the break is assigned. For example, if the shift begins at 8:00 a.m. and the break has a relative start of 2 hours, the break begins at 10:00 a.m. The next hierarchy level contains objects of the Shift type. A shift is the daily time interval during which work is performed. The shift is indicated by its relative shift start and its duration. A shift may have more than one break. The relative start times of the breaks must lie within the shift times. Typical examples for shifts are the early, midday, night and day shifts. Each shift is repeated every 24 hours. A shift cycle is the weekly time interval or a time interval extending over several days during which work is performed. The shift cycle thus determines the days on which a certain shift is run or is not run. The shift cycle is specified by its relative cycle start and cycle duration. If a shift cycle is to be repeated continuously, this can be defined using the Cyclical repeat attribute. In addition, the Period attribute can be used to determine how often a cycle is to be repeated. Shift cycles frequently cover a period of one or two weeks. An employee can thus have an early shift one week and a midday shift the next. This sequence can be repeated constantly using shift cycles.
ARIS Methods
Organization View
4-89
Following the example above, two shift cycles may be defined: 1. Shift cycle: (Early shift) Relative cycle start = 0 Cycle duration = 5 days Cyclical repeat = yes Period = 14 days 2. Shift cycle: (Midday shift) Relative cycle start = 7 days Cycle duration = 5 days Cyclical repeat = yes Period = 14 days The individual shifts are repeated in a 14-day rhythm, i.e. the periodicity is 2 weeks. If the same employee were to work an early shift on Saturdays every four weeks, the third shift cycle could be defined as follows: 3. Shift cycle: (Early shift) Relative cycle start = 20 days Cycle duration = 1 day
Cyclical repeat = yes Period = 28 days You will find the above example illustrated once again below as a model. A 1 : n allocation of shifts and shift cycles can be seen.
ARIS Methods
Organization View
4-90
Figure 4.3.1-8: Example of a Shift Calendar
A shift plan
is the set of all shift cycles and associated shifts that describe the
working hours of a resource. This description contains only the portion that is repeated periodically; special rules governing vacation, sickness, holidays, or other days on which no work is performed are not included here. The Shift plan object type includes the Plan start and Plan duration attributes. These attributes specify the timeframe during which the shift plan is valid. The Cyclical repeat and Period attributes also exist for the shift plan.
ARIS Methods
Organization View
4-91
4.3.2 Design Specification - Network Topology

The company's organizational structure as represented in the organizational chart can now be supported using communication and information system landscapes. The structural requirements for these information systems can generally be defined in the design specification in the form of network topologies. Firstly, the network topology model may contain various network types. Definition: A network type represents a typification of individual network examples which are all based on exactly the same technology.
An example of a network type is shown in Figure 4.3.2-1:
Figure 4.3.2-1: Grafical Representation of a Network Type
Network types can be interlinked and, since they are logical constructs, they can also be placed in a hierarchy. Every network type can be assigned to possible network node types and network connection types. Thus, technological restrictions resulting from the choice of one particular network type for a company can be identified immediately. For every network connection type it can be shown which network node types it may end in. When speaking of hardware component types this may either refer to network hardware for realizing the defined network structures or to hardware component types which can be connected to network node types. As with application system or network types, hardware component types do not represent individual pieces of hardware components that can be identified (e.g. by inventory numbers assigned by the company). Instead, they represent a typification
ARIS Methods
Organization View
4-92
of all hardware components based on the same technology. Hardware component types can be placed anywhere in a hierarchy. Definition: A hardware component type represents a typification of individual hardware components which are all based on exactly the same technology.
Together with network node and connection types, a kind of reference model of the network topology can now be created. It displays which hardware component types can be used for realizing certain network connection types or network node types. An example of a connection type might be one particular type of network cable. Apart from this, it is possible to show which hardware component type can be connected to which network node type. Moreover, network node types can have a relationship with hardware component types which are used to create node types. An example illustrating this is shown in Figure 4.3.2-2.
Figure 4.3.2-2: Network Topology
The link between network topology and the objects of the requirements definition is established through two constructs.
ARIS Methods
Organization View
4-93
On the one hand, the organizational unit or position responsible for every hardware component type can be specified. On the other hand, it is possible to define at which location of the company each network type, each network node type and network connection type and hardware component type may be found. Thus, the location is the central link between the organization view's requirements definition and its design specification. In the appendix of this manual you will find a list of all objects and relationship types of the network topology model.
ARIS Methods
Organization View
4-94
4.3.3 Implementation 4.3.3.1 Network Diagram
The network diagram is used to illustrate the actual realization of the network topology determined in the design specification. The company's actual networks are registered using the Network object. The network nodes and network connections that go to make up each network can be specified. The exact location of every network, network node and network connection within the company can specified. In this context, a location can be an entire production plant, one particular building, a building complex, an office or a specific work station.
Figure 4.3.3-1: Network Diagram with Location Allocation
The hardware components for every network connection and network node can be registered. Apart from this, it is also possible to illustrate the structural design of every hardware component. On the one hand, hardware components are used to
ARIS Methods
Organization View
4-95
form network connections and network nodes; on the other hand, they can be connected to network nodes. Even this relationship can be represented in the network diagram. The relationship with the respective object at the design specification level can also be modeled for every object on the example level. It can thus be shown that the network in the Port Str. plant is of the Novell version 4.11 type.
Figure 4.3.3-2: Network Diagram with Hardware Components and Location Allocation
In the network diagram therefore the links to the design specification have been made using the type allocations and the links to the requirements definition established using the allocation of network components to specific locations. In the appendix of this manual you will find a list of object and relationship types of the network diagram.
ARIS Methods
Organization View
4-96
4.3.3.2
Material Flow Modeling - Technical Resources
In order to illustrate the material flow in process models (eEPC (material flow), PCD (material flow), the material types are allocated to the individual functions of the business process in the form of function input or output. Just as in the allocation of information objects to functions (the transformation of information is represented by means of functions), this allocation represents the transformation of input material types to output material types. Additionally, it can be recorded in the process chains which technical resources are necessary for the transformation of materials. In this context we can distinguish operating resources, warehouse equipment, transport systems and technical operating supplies. In the Technical resources model type you can arrange these resources in a hierarchy, assign a type to them and classify them. The following object types are available to do this: Operating resources Definition: Operating resources are examples of different operating resource types that are available for a company to perform its tasks. Operating resources are often identified by assigning inventory numbers (e.g. number of a production plant).
Operating resource type Definition: An operating resource type represents the typification of individual operating resources which have exactly the same technological basis.
Operating resource class Definition: Similar operating resource types can be combined to form an operating resource class. In doing so, the question of similarity can be considered for various aspects of classification. Hence, an operating resource type can also be assigned to several operating resource classes.
ARIS Methods
Organization View
4-97
Warehouse equipment Definition: Warehouse equipment represents examples of various warehouse equipment types that are available for a company in the performance of its tasks. Warehouse equipment is often identified by assigning inventory numbers.
Warehouse equipment type Definition: A warehouse equipment type represents the typification of individual warehouse equipment units which have exactly the same technological basis.
Warehouse equipment class Definition: Similar warehouse equipment types can be combined to form a warehouse equipment class. In doing so, the question of similarity can be considered for various aspects of classification. Hence, a warehouse equipment type can also be assigned to several warehouse equipment classes.
Technical operating supply Definition: A technical operating supply is an example of a technical operating supply type. In general, it can be identified by means of an inventory number.
Technical operating supply type Definition: A technical operating supply type represents the typification of individual technical operating supplies which have exactly the same technological basis.
Technical operating supply class Definition: Similar technical operating supply types can be combined to form a technical operating supply class. In doing so, the question of similarity can be considered for various aspects of classification. Hence, a technical operating supply type can also be assigned to several technical operating supply classes.
ARIS Methods
Organization View
4-98
Transport system Definition: A transport system is an individual example of a transport system type. In general, it can be identified by means of an inventory number or a plant number.
Transport system type Definition: A transport system type represents the typification of individual transport systems which have exactly the same technological basis.
Transport system class Definition: Similar transport system types can be combined to form a transport system class. In doing so, the question of similarity can be considered for various aspects of classification. Hence, a transport system type can also be assigned to several transport system classes.
The different possibilities of arranging the Technical resources model type in a hierarchy enable you to describe the structure of complex technical plants. This enables you to display the components of a complex production plant and the relationships between them, for example. Apart from the possibilities in terms of modeling, described above, you can also define location allocations and organizational responsibilities for technical resources. The Location, Organizational unit, Group, Position and Person object types which are familiar from the Organizational chart model type are available. They can be linked to the Operating resource, Warehouse equipment, Technical operating supply and Transport system object types. An example of a Technical resources model type is shown in Figure 4.3.3-3.
ARIS Methods
Organization View
4-99
Figure 4.3.3-3: Example of a "Technical Resources" Model
ARIS Methods
Process View/Control View
4-100
4.4
4.4.1

Requirements Definition
The relationships between the objects of the data organization and function views are analyzed in the control/ process view. The relationships that must be analyzed result from the connections between the views in figure 2.2-2. First of all, the relationships between two views are examined. This is followed by diagrams which illustrate the relationships between all three views.
4.4.1.1
Combining Functions with Organization - eEPC, Function/Organizational Level Diagram
The link between the function view and the organization view is used to assign the functions defined in the function tree to the task performers (organizational units) in the organizational chart. This assignment defines an organizational unit's responsibility and decision-making power for its allocated functions. Looking at this organizational allocation in the course of a process chain (business processes) the degree of functional integration is defined, i.e. the functional steps within a business process that are to be processed by an organizational unit. Figure 4.4.1-1 shows an example of the allocation of organizational units to functions. In this figure, the function situated on the left hand side is assigned the organizational unit responsible for its execution. The functions' upper or lower position in the hierarchy has been illustrated in the function view (function tree) and the relationships between the organizational units have been shown in the organization view (organizational chart). Thus, there is no longer any need to define them at this point.
ARIS Methods
4-101
Figure 4.4.1-1: Allocation of Organizational Elements to Functions
ARIS Methods
4-102
4.4.1.2 4.4.1.2.1
Combining Functions with Data Event Control - Event-Driven Process Chain (EPC)
The procedural sequence of functions in the sense of business processes is represented in process chains. This means that the start and end events can be specified for each function. Events not only trigger functions but are also results of functions. Definition: An event is the existence of a state of an information object that is pertinent for business management and which controls or influences the subsequent procedure of the business process. Events trigger functions and are the results of functions. Unlike a function, which is a timeconsuming occurrence, an event is related to one point in time.
The change in state of an information object may refer to the first occurrence of this information object (e.g. Customer order received) or to a change in state in the sense of a change in status that is recorded in an attribute occurrence (e.g. Offer is refused). Since information objects and attributes are described in the ARIS data view, the event-driven representation of process chains is the link between the data view and the function view. Hence it is assigned to the ARIS control view. Events are represented graphically as hexagons. The description should not only contain the information object itself (order) but also its status modification (received). Figure 4.4.1-2 illustrates events.
ARIS Methods
4-103
Figure 4.4.1-2: Events (Graphical Representation)
Definition:
Events trigger functions and are the results of functions. By arranging this event to function change in a sequence, so-called event-driven process chains (EPCs) are created. An event-driven process chain (EPC) shows the chronological-logical procedure of a business process.
An example of an EPC is shown in Figure 4.4.1-3. Since events determine which state or condition will trigger a function and which status will define the end of a function, the starting and end nodes of an EPC like this are always events. Several functions can originate simultaneously from one event and conversely, a function can have several events as its result. A link in the form of a circle is used to represent these branches and processing loops in an EPC (see Figure 4.4.1-3). These connections, however, not only serve as graphic operators but define the logical links between the objects they connect.
ARIS Methods
4-104
Figure 4.4.1-3: Example of an EPC
ARIS Methods
4-105
Figure 4.4.1-4: Examples of Rules
In the first example of Figure 4.4.1-4 the starting events are linked by an AND operator . This means that the procedure Release operation procedure is only started if a routing is available and the necessary resources have been verified. Therefore both events must have occurred before the procedure can begin. The second example shows an exclusive OR operator. The Check supplier offer function may either result in accepting or in rejecting the quote. Both results, however, cannot occur at the same time. Besides these two cases and the "Inclusive OR" operator, more complex relationships are also conceivable. In this case, a general rule can be represented in an EPC which will be described later in more detail in the form of a rule diagram. Therefore, we can basically distinguish between two different types of operators: Event operators and Function operators. An overview of all possible event and function operators is listed in Figure 4.4.1-5 (see Hoffmann, Kirsch, Scheer, Modeling with event driven process chains 1993, p. 13).
ARIS Methods
4-106
Figure 4.4.1-5: Operators
ARIS Methods
4-107
In this context, special attention must be paid to the restrictions which exist for function operators. Due to the fact that events cannot make decisions (only functions can do this) a triggering event must not be linked using an OR or XOR operator! Below, possible operators are explained using examples. 1. Linking of triggering events: a. AND operator
Figure 4.4.1-6: AND Operator for Triggering Events
The function can only be started after all events have occurred. b. OR operator
Figure 4.4.1-7: OR Operator for Triggering Events
ARIS Methods
4-108
The function will be executed after at least one of the events has occurred. c. XOR operator (Either/Or operator)
Figure 4.4.1-8: XOR Operator for Triggering Events
The function is started after exactly one and only one event has occurred.
2. Linking of created events a. AND operator
Figure 4.4.1-9: AND Operator for Created Events
ARIS Methods
4-109
The function results in all events occurring. b. OR operator
Figure 4.4.1-10: OR Operator for Created Events
Executing the function results in at least one of the events occurring. c. XOR operator (Either/Or operator)
Figure 4.4.1-11: XOR Operator for Created Events
Executing the function results in one event at the most occurring.
ARIS Methods
4-110
3. Linking of functions with created events a. AND operator
Figure 4.4.1-12: AND Operator of Functions with Created Events
The event occurs only after all functions have been executed. b. OR operator
Figure 4.4.1-13: OR Operator of Functions with Created Events
ARIS Methods
4-111
The event occurs after at least one of the functions has been executed. c. XOR operator (Either/Or operator)
Figure 4.4.1-14: XOR Operator of Functions with Created Events
The event occurs when exactly one and more than one of the functions has been executed. 4. Linking of functions with triggering events a. AND operator
Figure 4.4.1-15: AND Operator of Functions with Triggering Events
ARIS Methods
4-112
The event triggers all functions. b. OR operator Events have no decision-making power! This operator is not possible! c. XOR operator Events have no decision-making power! This operator is not possible! Besides being illustrated in the form of event-driven process chains, these branches can also be represented in table form in the event and function columns (see Chapter 3) of a process chain diagram (see Chapter 3). Since the functions are ordered sequentially in a process chain diagram the branches and processing loops can only be represented in a rather confusing manner.
4.4.1.2.2
Function Allocation Diagram (I/O)
As well as the representation of event control explained in Chapter 4.4.1.2.1, the transformation of input data to output data and the representation of the data flows between functions represent a link between the data view and the function view in the ARIS concept. The transformation of input data into output data can be illustrated in so-called function allocation diagrams (I/O) which basically correspond to pure input/output diagrams used in other methods. An example of a function allocation diagram (I/O) is shown in Figure 4.4.1-16. The input data of the Determine delivery date function are Parts data, Inventory data, Bill of materials data and Shipping data. Inquiry data serve as input data as well as output data. Function allocation diagrams (I/O) thus contain functions of the function view and information objects of the data view. The arrows determine whether an information object is only used as input data, output data or as input/output data. More detailed specifications are possible, indicating for example that the function has created or deleted an information object. Depending on the degree of detail, the information objects can either be data clusters (see Figure 4.4.1-16), entity or relationship types or even attributes of the data view.
ARIS Methods
4-113
Figure 4.4.1-16: Example of a Function Allocation Diagram (I/O)
The example shown above clarifies the actual objective of function allocation diagrams (I/O) which is to represent a function's input/output data. Besides including a function's input/output data and events, all other objects which can be allocated to individual functions in an eEPC are available. The user is thus able to restrict the modeling of process chains in eEPC diagrams to events and functions, and to assign each function a function allocation diagram (I/O) with all additional relationships for the function. This enables business processes to be illustrated much more clearly and also explains the use of a new name for this model type. An example of this more detailed representation in a function allocation diagram is shown in Figure 4.4.1-17.
ARIS Methods
4-114
Figure 4.4.1-17: Function Allocation Diagram.
In addition to the separate representation of data transformation as function allocation diagrams (I/O), this information can also be included in an EPC. This is illustrated in Figure 4.4.1-18. Here, the significance of the operators between functions and information objects is the same as for those within the function allocation diagrams (I/O). If they are included in a process chain with numerous branches, however, a rather confusing representation may result.
ARIS Methods
4-115
Figure 4.4.1-18: EPC with Input/Output Data
ARIS Methods
4-116
In the PCD (process chain diagram) objects have to be arranged according to the column description. The EPC representation permits a free arrangement of objects. However, adding input/output data may result in confusing models. Therefore we recommend a PCD representation especially for business processes executed in sequence. The following figure shows the EPC with input/output data of Figure 4.4.1-18 as a PCD (see also chapter 4.4.1.3.1).
Figure 4.4.1-19: PCD with Input/Output Data
ARIS Methods
4-117
4.4.1.2.3
Information Flow Diagrams
Information flow diagrams are suitable for illustrating the flow of data between functions as mentioned earlier. For this purpose two functions can be interlinked by a data flow object in an information flow diagram. This object shows that there is a data flow from the source function to the target function. In order to specify the data objects flowing between the displayed functions more precisely, this data flow object can be set in a hierarchy which, in turn, allows assigning a data model to that object. This data model represents the information objects which are exchanged between the functions. Depending on the degree of detail of the examined functions, the information objects can be data clusters, entity types or ERM attributes. An example of this type of representation is shown in Figure 4.4.120.
Figure 4.4.1-20: Information Flow Diagram with Open Assignment Wizard
ARIS Methods
4-118
4.4.1.2.4
Event Diagram
Events define the fact that the status of information objects has changed. Thus, every event is a reference to particular information objects of the data model and defines the status of this information object at a given point in time. First of all, events are roughly specified in a top-down procedure (example: Customer order has been processed). The next detailed step of the process modeling level involves specification of the events in more detail. If they are combined in a certain way, the events occur on the roughly defined level. For example, the total of the following events that have occurred: Feasibility checked, Order header registered, Order line items registered and Feasibility checked could define the Customer order status. You can display these event correlations on the rough and detailed modeling levels using the event diagram. For this purpose, you can assign an event diagram to an event on the rough level (hierarchy!), which would, in turn, display the events and the operators between them on the detailed level (by means of rule operators as well). Moreover, you can even include information objects of the data model in this model type and link them to the events. Thus you specify the event which defines the status change of a given information object. Figure 4.4.1-21 gives an example.
Figure 4.4.1-21: Example of an Event Diagram
ARIS Methods
4-119
4.4.1.3 4.4.1.3.1
Functions - Organization - Data eEPC/PCD
The same facts are represented in eEPCs and in PCDs Up to this point we have been dealing with just two views; now a third view is introduced. This means that the process chain's partial views are again combined to form an overall view and that the interactions of all components of the ARIS architecture can be examined. The process chain we originally started out with is again shown in detail. However, this examination does not focus on the details extracted in the individual views for the objects examined, but on the operators between these objects. Figure 4.4.1-22 shows a process chain with all views of a process chain. Events representing data view objects have been placed in the first column. The arrows lead to the process column where the process chain's functions are listed. Thus, the first and second columns define the event control. The data objects are located in the third column where their relations to the individual functions are displayed. The view of the second and third column of the PCD thus defines the data flow of the process chain. Unlike the PCD introduced in Chapter 3.2 the process chain diagram of the requirements definition has no columns for the definition of the processing type and the IT system. These facts are needed to capture the actual situation in a company, but nevertheless they are not part of the subject-related description of a business process. The organizational units of the organization view which are responsible for executing the individual functions of the process chain are defined in the fourth column. The process chain illustrated in Figure 4.4.1-22 can also be expressed as an EPC (see Figure 4.4.1-23).
ARIS Methods
4-120
Figure 4.4.1-22: Example of a Process Chain (Requirements Definition)
ARIS Methods
4-121
Figure 4.4.1-23: eEPC with Functions, Data, Organizational Units and Events
ARIS Methods
4-122
4.4.1.3.2
Value added chain diagram
Above all, the value-added chain diagram is used to identify those functions within a company which are directly involved in the creation of a company's added value. These functions can be interlinked by creating a function sequence and thus a value-added chain. An example of a value-added chain is shown in Figure 4.4.124.
Figure 4.4.1-24: Value-Added Chain
In a value-added chain diagram functions can be arranged hierarchically, similar to a function tree. This representation always includes the process-oriented super and subordinations. A value-added chain diagram not only enables you to express a super- or subordination of functions, it can also display the functions' links to organizational units and information objects. When allocating organizational units to functions we differentiate, as we do in process chains, between a function's subject-related responsibility, its IT responsibility and the actual execution of a function. In the appendix of this manual you will find a list containing the additional relationships available in the value-added chain diagram.
ARIS Methods
4-123
4.4.1.3.3
Rule Diagram
In process chains, you can use rules as operators to specify event and function operators. Frequently, these rule representations for displaying the logical operators are very complex - this is especially the case when rules are linked to each other. To avoid process chains becoming too complex due to representations of this kind, in this case you can use the general rule operator in the eEPC or PCD. You may link this general rule operator to a rule diagram (hierarchy!) which, in turn, illustrates all details of the complex rule.
Figure 4.4.1-25: Illustration of Complex Operators in the Rule Diagram
ARIS Methods
4-124
4.4.1.3.4
Communications Diagram
Large reference models contain a large number of process models. Including the elements of the organization view in these process models illustrates who communicates with whom during the process. The communications diagram allows grouping all processes according to the communication between organizational units. Therefore, the communications diagram displays all organizational units which communicate with each other. The Sales organizational unit, for example, is linked to the Customer organizational unit via an object of the Communication type. Objects of the Communication type can be specified in a hierarchy. They can be linked to the Process selection matrix model type. This process selection matrix displays all processes in which the sales department communicates with the customer.
4.4.1.3.5
Classification Diagram
The Classification diagram provides the opportunity to classify functions by allocating functions to object type classes. Classifications can be made according to different classification criteria. To specify the classification criteria, you can link the Object type class object type with the Classification criterion object type.
ARIS Methods
4-125
4.4.1.3.6
Input/Output Diagram
The input/output diagram provides an overview representation of incoming and outgoing data and information carriers. For this model, only one icon may be placed in each diagram grid, i.e. in a field separated by lines from other fields. The top row contains data or information carriers created by a particular function (output). In the same way, the left column models incoming data or information carrier symbols of a particular function (input). If the function needs to have several input and/or output symbols, they will be created by occurrence copies. The invisible (implicit) provides input for and creates output to relationships will be created automatically during the creation of functions and data or information carrier symbols in the input/output diagram. Below is a simple example of an input/output diagram.
Figure 4.4.1-26: Input/ Output Diagram
ARIS Methods
4-126
4.4.1.4 4.4.1.4.1
Object-oriented Modeling Class Diagram
The object-oriented extended ARIS concept allows you to assign the role of classes to information objects (clusters, entity types, relationship types). This means that all information objects which can be defined in ARIS within the data view can be given class character by assigning class functions (/-methods) and descriptive attributes (data contents) to them. This allocation is performed in so-called class diagrams. When allocating a class diagram to an information object, you assign this information object the role of a class. A class diagram is uniquely allocated to an information object and contains the following items (symbols for object types in the ARIS architecture): the information object described as a class, a list of attributes allocated to the class, a list of events occurring due to a particular class status a list of functions from the function view which are allocated to the class and triggering events or events triggered by them.
Figure 4.4.1-27 shows an example of the Customer order class definition.
ARIS Methods
4-127
Figure 4.4.1-27: Class Diagram for the Customer Order Class
ARIS Methods
4-128
4.4.1.5 4.4.1.5.1
Process Variants Process selection matrix
The process selection matrix displays different process scenarios by allocating main processes to individual scenarios. Afterwards, the user can determine which functions of the scenario processes will occur in the company. For this purpose, all main functions (scenario functions) of an application system or of an industry reference model need to be included as processes. The following symbol types are available for modeling a process selection matrix:
Scenario Process
Main process Definition: A scenario represents a scenario process in the selection matrix which arranges different main processes in groups. The process represents functions of the scenario process which are described in more detail in the reference model by process models. The main process represents the main functions in the function trees to which the processes (functions from the scenario processes) are allocated.
Definition:
Definition:
Figure 4.4.1-28 shows an example of a process selection matrix.
ARIS Methods
4-129
Figure 4.4.1-28: Process Selection Matrix (Extract from the SAP AG R/3 Reference Model)
ARIS Methods
4-130
4.4.1.6
Material Flow Modeling
You can use process models (eEPC and PCD) to illustrate not only the information flow, but also the material transformation. To represent the material flow within business processes, ARIS provides you with a separate model type - an eEPC (material flow) - which is an extension of the eEPC model type.
4.4.1.6.1
eEPC (material flow)
In addition to the eEPC object types, the following object types are also available in the eEPC (material flow): Material type Packaging material type Operating resource type Operating resources Technical operating supply type Technical operating supply Warehouse equipment type Warehouse equipment Transport system type Transport system The Material type object type may be linked to the Function object type by means of an incoming or outgoing connection. For an incoming connection, the materials which are required by a function as input are defined. In this context, you can define - by selecting the corresponding connection type - whether the function consumes none, part or all of the material. An outgoing connection specifies the material types created by the function. Technical resources are required for material transformation. In the process chains, you can also link them to the Function object type. To specify possible available alternative resources, the requires alternatively connection type addition to the requires connection type. is offered in
ARIS Methods
4-131
If materials are to be packaged within a function, certain packaging material types are needed. In order to specify the corresponding packaging material types, you can model a relationship between the function and the necessary packaging material types. Figure 4.4.1-29 shows an eEPC (material flow) and the corresponding technical resource types and packaging material types.
Figure 4.4.1-29: Extract from an eEPC (Material Flow)
ARIS Methods
4-132
4.4.1.6.2
Material Flow Diagram
You can use material flow diagrams to illustrate material flows between functions. They are treated in a similar way to information flow diagrams during the modeling process. In a material flow diagram, you link two functions by means of a material flow connection. This connection shows that there is a material flow from the source function to the target function. If you want to specify the material flowing between the displayed functions in more detail, you may assign a material diagram to this connection by establishing a hierarchy for this material flow connection. This material diagram illustrates the material or material types exchanged between the functions.
4.4.1.6.3
eEPC (Column/Row Display)
The following description also applies to the eEPC (row display). Most of the descriptions given for eEPC are equally valid for the eEPC - Column display model type, with the difference that all symbols in this model are distributed over different columns. The advantage is that this representation makes the eEPC much easier to interpret. Organizational and application system items are placed in the diagram header. All other symbols are placed in the second row of each column. A particular characteristic of all swimlane models, i.e. models which are modeled in columns and/or rows, is the automatic creation of invisible (implicit) relationships. For example, when modeling application systems and functions, the supports implicit relationship will be automatically created in the default columns of the eEPC (column display). The carries out relationship will be created implicitly between organizational elements and functions. The user may also add the following additional columns, which are named according to the implicit relationships:
Contributes to Decides on Is IT responsible for Is technically responsible for Must be informed on cancellation Must inform about result of
ARIS Methods
4-133
Must be informed about Accepts Has consulting role in
The following figure shows an example of an eEPC (column display).
Figure 4.4.1-30: eEPC (column display)
One difference between the eEPC (column display) and the eEPC (row display) is the different modeling direction. Modeling occurs from top to bottom in the eEPC (column display) and from left to right in the eEPC (row display).
ARIS Methods
4-134
4.4.1.7
SAP ALE Models
Models of the SAP ALE type (SAP Application Linking Enabling) are for modeling links between functions and applications.
4.4.1.7.1
SAP ALE Filter model
The SAP ALE Filter Model shows the criteria according to which a function type can be used more than once in a system (in an application). In this regard the Filter Object Type object serves as a separation criterion within a distribution model.
4.4.1.7.2
SAP ALE Message Flow Model
The SAP ALE message flow model uses the Message Flow object type to represent the message flows, including their direction between systems and function types.
4.4.1.7.3
SAP ALE Message Type Model
The SAP ALE message type model uses the Message Type object type to classify the messages being exchanged between distributed systems, depending on the data and transactions involved.
4.4.1.8
Role Allocation Diagram (RAD)
The SAP reference model is illustrated using eEPCs. They illustrate the business processes at different levels of detail. In the eEPCs with the highest level of detail, which the SAP terminology describes as processes, the commercial processes are modeled in the processing of transactions in the R/3 system. These processes can be assigned both roles and transactions. In ARIS this happens in the function allocation diagram where the eEPC that contains the modeled process must be assigned to the corresponding function definition. Thus it can be seen in the function allocation diagram which roles are necessary to execute the transactions. However, since there are no direct
ARIS Methods
4-135
relationships between roles and transactions, with several occurring roles no decision can be made as to which transactions they are responsible for. For this reason the assignment of roles to transactions takes place in the Role allocation diagram (RAD). One role is displayed per column. Transactions are placed in columns which creates implicit relationships. The information can be used during the R/3 introduction to create the necessary user profiles and authorization concepts to operate the R/3 system.
HR Controller
Employee Group
Trip Manager
Travel Calendar
Travel Calendar
Travel Manager
Travel Manager
Import of Credit Card Data
Import of Credit Card Data
Maintain Old Trip Data
Figure 4.4.1-31: Role Allocation Diagram (RAD - Role Allocation Diagram)
ARIS Methods
4-136
4.4.1.9 4.4.1.9.1
Other Models Business Controls Diagram
A Business Controls Diagram displays potential risks of a process or function as well as ways of covering these risks. Definition: A risk represents the possible danger that a set process objective will not be achieved. A risk control is a general way of eliminating or mitigating risks. A risk solution means implementing a risk control in relation to a risk.
Definition:
Definition:
The Business Controls Diagram layout corresponds to a matrix or table. The abscissa shows the potential process risks, and the ordinate shows the possible risk controls. Risk solutions are now inserted as operators between a risk and a risk control. Additionally, organizational units (in the sense of user requirements) and documents, which also support implementation of a risk control regarding a risk, may be added to the model.
Figure 4.4.1-32: Example of a Business Controls Diagram
ARIS Methods
4-137
This model type is generally used to describe SAP standard processes. The model shows the risks and risk controls of a SAP solution for the process being examined.
4.4.1.9.2
Data Warehouse Transformation
The data warehouse data transformation diagram is used to describe data warehouse. Of primary concern is the description of the dynamic aspects that are described in the ARIS architecture in process view. In the model the transfer of general data of the information objects into data formats of the InfoCube is depicted. To ensure that you can proceed efficiently and without loss of data in the transformation, a method specification is required for modeling. The methodology contains transformation rules and procedures, which are graphically portrayed in the model. The transfer occurs in two steps. First the transfer structure items are changed into communication structure items. Then they are transferred to the InfoCube. You have the option of having this procedure run on different levels. On the one hand, you can show which transfer and communication structures are present to fill the InfoCube at a very high (requirements definition) abstraction level. On the other hand, on a very low (implementation) level you can illustrate how the individual data items are transferred to each other.
ARIS Methods
4-138
Figure 4.4.1-33: DW transformation - Data Transformation for a Data Warehouse
4.4.1.9.3
E-Business Scenario Diagram
The smooth sequence of inter-company business processes is steadily gaining in significance. On the one hand the sequence of specific procedures at the interfaces between the companies is in the center of interest, on the other hand there are the interfaces between the companies and their customers. The contacts need to take place in a clear, quick, consistent and direct manner. Also, rapidly finding adequate business partners from the company viewpoint and suppliers from the consumer viewpoint is becoming increasingly more important. An optimum arrangement of these processes means a competitive advantage. The ideal platform for supporting these bilateral relationships is the Internet. As the processes within the environment described above are multi layered, we must define what we mean by the term e-business.
ARIS Methods
4-139
Definition:
The term e-business means all computer supported processes between two business subjects and the attempt to gain added value through new media.
This can be the simple purchase of an article via the Internet, a highly complex project between two companies or the creation of a web site to advertise the company. Definition: Company - Company relationships are called Business - to Business (B2B for short), Customer Company relationships are called Business - to - Customer (B2C for short).
The E-Business scenario diagram has been developed to support e-business. Optimization potential should be developed by the opportunity to view a valueadded chain completely, i.e. from end customer through all the companies involved in the procedure. The objective is, for example, the improvement of the supply chain, the lowering of procurement and distribution costs or the optimization of the architecture of the information system. The contents depicted by the objectives can be modeled by this method. The business objects are arranged in the upper row of the diagram and referred to as Business participant. The participating business can be assigned by an organizational chart. Central objects are the individual processes of the business objects participating in the whole process and their interfaces to each other. An individual process, also termed a business process, is a company process significantly involved in inter-company co-operations that can be assigned to the process model. The business process is supported by the application systems (business components) such as the R/3 system. Even the roles of the staff involved in the process can be defined. These are referred to in the model as Employee role. The features of the interfaces are the transfer of process specific information. They are combined in business documents and can assume the form of an XML or HTML document. The business document can also be assigned as a data model. As well as this object, the Money transaction object (to represent cash flow), the Goods shipment object (to represent the flow of goods), the e-mail, Internet, Intranet,
ARIS Methods
4-140
Extranet and Mobile phone objects (to specify the technological aspect of the data transfer) are also used. All processes relating to a company are modeled in the model in the row under the business participant but in the same column. This means that the column edges form the abstract interfaces. These merit our special attention since they contain the main optimization potential and are therefore especially important for modeling purposes. Explanation of terms: in the sample model below OEM stands for Original Equipment Manufacturer and MRP for Material Resource Planning Controller.
ARIS Methods
4-141
executes Business Participants
executes
executes
OEM
Importer
Dealer
Figure 4.4.1-34: Example of an eBusiness Scenario for the Motor Industry
The sample model shows the interplay of a manufacturer, an importer and a dealer. Each person has his specific processes in the overall picture, which are exchanged at the interfaces to the processes of other business partners via business documents information. The people involved in the business processes are also recorded and allocated with their roles.
ARIS Methods
Vehicle Specification/ Search Request via Internet
Buyer (all purchasing activities)
Vehicle Locating an Allocation
Strategic Purchaser
Reservation Planning
MRPController
Order Processing
Production
Production Planner
Order Tracking
Shipment Tracking
4-142
4.4.1.9.4
The
Structuring model
model is generally used to represent the hierarchy or
structuring Definition:
systematization of facts (specialization). Generalization of facts). A structural item represents a fact (in the direction of the intended systematization).
Models relating to the fact can be assigned to the individual structural items of the fact hierarchy. Structuring models are most frequently used in quality management, especially for certification purposes. There, the structuring model shows a norm in its individual components, and models which help meet the quality criterion are assigned to the individual structural items.
Figure 4.4.1-35: Example of a Structuring Model (Extract from VDA 6.2 Standard)
Using a report, these facts can easily be evaluated, or used for documentation purposes.
4.4.1.9.5
Industrial Process and Office Process
The Industrial Process and Office Process model type represent essentially the same facts as the eEPC model type or eEPC (Material Flow). These two models however, provide only a limited selection of objects, and the symbols are represented in graphical form.
ARIS Methods
4-143
This kind of graphic representation has the advantage that employees in the specialist departments can understand the models without training and are able to adjust and develop them themselves. For example: It is easy for everyone to see that a three person-symbol represents a group; whereas this is not so obvious in the abstract eEPC symbolism (oval with double frame). The goal of these two model types is therefore to introduce process modeling, process optimization and process utilization into the specialist departments. For the best identification of symbols two process types (model types) are distinguished: the industrial process illustrates the production processes (creating material goods/ products) and the office process illustrates the office processes (creating non-material goods./ services). Figure 4.4.1-36 compares the industrial process symbols and office process symbols with eEPC or eEPC (material flow) symbols.
Object type Event eEPC Possible symbols within the model type Industrial process Office process
Function
Event (Manufac.)
Function (Office)
Rule
AND
XOR
OR
Rule
Application system type
Location
Workstation
Location
Organizational unit Group
ARIS Methods
4-144
Object type
eEPC
Possible symbols within the model type Industrial process Office process
Position
Person type
Person type
Position description
Person
Internal person
External person
Person (m)
Person (f)
Person (m)
Person (f)
Knowledge category Documented knowledge
Printer
Bar code File
Document
Diskette
File cabinet
Fax Card file
Notepad
Telephone
Printer
Document
Diskette File bin E-mail Time planner
Information carrier
Magnetic tape
Microfiche
File cabinet
Notepad
Telephone Wastepaper basket Internet Book
Telephone
Document
File bin
E-mail Hard disk CD-ROM Fax
Folder
Expertise
Letter
File
Magnetic tape
Material type
ARIS Methods
4-145
Object type
eEPC
Possible symbols within the model type Industrial process Office process
Transport system type
Airplane
Truck
Transport system
Operating resource type Technical Operating Supply Type Packaging material type Warehouse equipment type
Figure 4.4.1-36:
Machine
Robot
Comparison of symbols for the eEPC, Industrial Process, and Office Process model types.
The models can be displayed in all three model types (if the objects exist in the corresponding model type) by copying the content of one model type to another. When copying, ARIS automatically converts the symbols. Figure 4.4.1-37 gives an example of the same fact displayed in the three model types - eEPC, Industrial Process and Office Process.
ARIS Methods
4-146
Industrial Process
Shift start
Office Process
Shift start
eEPC
Shift start Shift overseer
Shift overseer Inform workers about daily plan

Inform workers about daily plan
Shift overseer Inform workers about daily plan
Daily working plan
Daily working plan
Daily working plan
Shift workers Work start
Work start Shift workers Shift workers
Work start
Figure 4.4.1-37:
Example of facts being represented in the eEPC, Industrial Process, and Office Process model types.
ARIS Methods
4-147
4.4.1.9.6
Project Process Chain (PPC)
The PPC model type is the connecting link between ARIS Toolset and MS Project. ARIS Toolset can represent the procedural sequence of functions in the sense of a business process by using event-driven process chains (eEPCs). However, this abstract level is insufficient for the capacity and time planning purposes of a project. Rather actual event and function instances that specifically occur must be examined and specified. The PPC fulfills this need by providing its own object type on occurrence level instead of the Event and Function object types. Definition: An event instance is an event occurring in an actual process instance. The event instance can be evaluated, i.e. it can be determined whether it is true or false. A function instance is a function occurring in an actual process instance. One can assign to it a unique start and end time, as well as other necessary attributes.
Definition:
Project structural items (function instance, event instance, rule, and connections) serve to represent the chronological sequence of a project. The PPC also contains the Person (internal/external), Operating Resource, and General Resource Definition: A general resource is a resource that is not described in detail and does not have to be either a person or an operating resource. A general resource is for executing procedures. resource objects. They are for date and capacity planning.
You can also specify function instances in more detail within the PPC by using cluster instances. Definition: A cluster instance is an instantiation of the cluster/data model object. It represents a logical view of a cluster of data objects or structures.
The PPC uses cluster instances to represent the relationship between function instances and data. An Information Carrier Diagram model type (see Requirements Definition of the Data View) can be assigned to the Cluster Instance object type. This can show the information carrier where the data are stored.
ARIS Methods
4-148
The figure below shows an example of a project process chain created by converting an eEPC.
Figure 4.4.1-38: Example of a PPC created from an eEPC.
The XOR operator in the example above indicates that in the converted eEPC branches occurred at this location, which have to be interpreted as alternative paths, and which must be uniquely specified for the project. Objects with assigned models are identified with a black dot in the bottom border. In the example above these are the Conception, Quality assurance (both project guidelines) objects and the requirements definition, part B (cluster instance). The PPC model type can be modeled directly in ARIS Toolset by the user as well.
ARIS Methods
4-149
4.4.1.9.7
Process instantiation model
The main aspect of a dynamic simulation is the analysis of process procedures during their dynamic procedure. The processes to be analyzed will be instantiated (started or generated) at start events. In accordance with their respective application areas, users must be able to decide themselves when and how often processes should be instantiated. In addition, it must be possible to prioritize processes, e.g. so that urgent processes can be taken into consideration. The ARIS method prioritizes tasks by maintaining the Priority attribute (Simulation attribute type group) for start events, and all processes instantiated at the corresponding start event retain this priority.. The requirement described is fulfilled by the process instantiation model. This will be developed as a multi-level object model. The Instantiation Interval object is at the lowest level. Such an interval contains the Relative Interval Start, Interval Duration, Number of Process Instances, and Distribution, Cyclical Repeat and Period attributes. An interval duration of 0 is permitted in this case in order to express a certain point in time. While intervals describe shorter periods of time, the process instantiation cycles are used to repeat an ever recurring sequence of intervals. For example, a day can be modeled by using four different intervals, which are repeated as a cycle for the entire simulation time period (e.g. a week). But it is also possible to divide the simulation time period into several cycles (e.g. work days and weekends), each of which can contain different intervals. A process instantiation plan can contain one or more cycles. The following example will explain the object model more clearly: A process model exists as an eEPC with a start event. The following assumptions apply for this process: Weekdays (Mon - Fri) 50 processes are started at 8.00 a.m. at the beginning of the working day. From 8:00 am to 12:00 noon as well as from 1:00 p.m. to 5:00 p.m., 20 processes are started in equal distribution; from 12:00 noon to 1:00 p.m. as well as during the time period outside of work hours, no processes will be started. On Saturday, 60 processes will be started in a triangular distribution from 9:00 a.m. to 3:00 p.m.. Generally, no processes will be started on Sundays. This weekly rhythm applies from January to December, except during the vacation period from July to August. During this period, no one works on Saturdays. Based on the example described above we can generate the following model:
ARIS Methods
4-150
Figure 4.4.1-39: Process Instantiation Model
ARIS Methods
4-151
4.4.1.9.8
RAMS
RAMS (Requirements Analysis for Manufacturing Systems) is a company analysis method developed by Digital Equipment. RAMS is a procedure (or model) for viewing and evaluating the integration potential of information technology and for developing solution scenarios for the requirements of information systems. The result is a "requirements specification" which ensures the coordination of company goals, business procedures, information flows and information systems. The model represents all departments, activities and existing applications to be considered on a diagonal. This diagonal is supplemented in matrix form by the most important information flows between the individual functional units. If applicable, important goods, money or material flows must be added.
Figure 4.4.1-40: Example of a RAMS Diagram
ARIS Methods
4-152
Transaction model of a RAMS study: Step 1: Step 2: The first step is the definition of expected study results, the naming of The second phase starts with the selection of the individual the participants involved, and an initial time schedule. departments, activities, and existing applications that will be examined during the study. They are represented on a diagonal matrix where the most important information flows between individual functional units will then be indicated clearly. If applicable, important goods, money or material flows have to be added and made visible. In addition, the departments or functions for which a detailed requirements analysis is desired must be specified. Step 3: After the scope of the study has been defined the selected departments or function groups will be analyzed in detail with regard to their business aims and processes as well as tasks and related information requirements. The creative use of drawings and illustrations makes complex processes or procedures easier to understand. Frequently, original business forms, reports or screens will be used to make things clearer. An important task of this analysis is to discover possible irregularities in the information flow and business procedures relationships in existing activities and systems. Improvement potentials of existing activities and systems are also examined. During the analysis, problems, questions, and suggestions for the best possible solutions are presented. This information will then be structured and examined in detail in terms of its causes and effects in business activities. If improvement potentials emerge, they will be recorded and their usefulness evaluated. Step 4: The results of this detailed actual situation analysis are now used as a basis for the following requirements specification. The problem areas are now clearly outlined, and new ideas and alternative solutions can be developed for them. It is important to keep suggested solutions - which can range from complex systems to simple process changes - in close relation to the previously recorded initial situation. This comparison with the initial situation must be performed for all functions and activities in the relevant areas. Study results can range from the functionality of generic solutions to creating and comparing user requirements. Step 5: The results collected during each step of the analysis will be incorporated in the formulation of the final requirements specifications. All
ARIS Methods
4-153
information, detailed examinations, and suggestions worked out during the course of the study will be summarized as a final report and will form the basis for future system requirements. In order to implement the stated solutions, the next step will consist of a functional system specification.
4.4.1.9.9
Role Diagram
In general, the role diagram is used to describe processes more precisely. The primary concern is the organizational units that participate in the processes and their roles. The objects and their relationships are characterized by the following properties: A role is participating in processes under the consideration of authorizations. Not just the executability is significant, but also the specification of the authorization type in the process (a role is 'executably involved'). In the execution of a process with a specific authorization, the Role - Participation - Process relationship chain (with Participation - Authorization condition as well as Participation - Authorization value) is established. A role can be occupied by persons, positions or information systems. The role forms the link between the processes and the resources involved in them. It is defined by an aggregation of expectations upon the resources involved in the processes. The execution of a process requires skills that the involved role or the allocated resource must possess. To be able to define roles mainly in a process-oriented manner, the processes must be appraised and the requirements of the processes for the people/ systems involved must be specified. To define people or system requirements more precisely: by requirements we mean here the knowledge and skills the people or systems have. The evaluation of a skill is standardized by an assigned evaluation scale.
Thus, in the role diagram it is possible to depict processes and specific elementary processes, represent the resources involved, record their skills or required skills and show their authorizations.
ARIS Methods
4-154
Figure 4.4.1-41: Role Diagram
ARIS Methods
4-155
The sample model displays the requirements of the elementary process for the role (skills and authorizations) and the requirements of the elementary role resources with regard to skills and authorizations. The respective elementary process and elementary role are assigned to the diagram. By assigning the diagram to the elementary process, the requirements from the underlying process eEPC (corresponds to the process reference model) can be understood. By making the assignment to the elementary role, the requirement of the elementary role for the resource with regard to its skills and authorizations can be understood from the role structure diagram. for the
ARIS Methods
4-156
4.4.1.9.10
Quick Model
The Quick model model type allows you to model without method restrictions. The Quick model contains the Quick object object type with over 30 different symbols. Relationships of the has relation with type can be created between quick objects. Several connections of this type are allowed between two objects. The corresponding standard attributes can be maintained for models, objects and connections. Each object can be assigned several quick models for any object type in the ARIS method. A Quick object can also be assigned any number of models in the ARIS method regardless of model type. You can transform Quick model model types and/or Quick object object types into method based models or objects using the semantic generator in ARIS.
4.4.1.9.11
c3 Method
The c3 method model type can describe the first entry of a process above the process level in a change management project. Here the focus is always on the process to be improved. For each process examined a number of different objects are modeled that illustrate relevant information for the project in list form. This includes information on: organizational aspects, e.g. process responsibility and deputizing rules. tasks that will be carried out to improve the process Indices by which the improvement in the process will be measured. Tools to be used to improve the process Activities planned to change the process in the near future Improvement potential for the process examined the skills needed to carry out the process targets aimed at by the project tools that are currently being used (software, methods, continuous training)
ARIS Methods
4-157
tools that should be used to improve the process and integrate it into the whole system The structure of the c3 method type is shown in the following diagram.
Figure 4.4.1-42: Structure of a c3 Model
ARIS Methods
4-158
You can only draw a connection between process/task and the process owners or managers or those looking after the project. The other relationships are formed from the position of the objects in the model. In the c3 method model type the processes recorded later can be assigned even to the objects of the organizational view. The Description/ definition attribute can be used for a short description of an object. This attribute is evaluated by the c3-ProjectSheet.rsm report.
4.4.1.9.12
Screen Design
You can use a screen design during software design in ARIS to specify the technical requirements for dialog box or Web form. In the Layout column you can determine the structure of the dialog box or Web form. Designing a dialog box is very much like using a resource editor in a development environment. The graphic elements that can be placed in the Layout column include text boxes, spin boxes, option buttons and check boxes, combo boxes, buttons, tree and list controls, and also bitmaps and static text. You can use the Tabindex attribute type to determine the order in which the tab jumps to the various screen elements. You can use the Data and Functions columns to place various data elements and function objects. A represents connection type can be used to link the objects with the data elements and functions that you edit. Each screen design can be assigned to the corresponding screen object that is used in a screen navigation type eEPC or model. In addition, a screen design can be assigned to the entity type, cluster, complex object type, class or the Function/IT Function that works with the screen. The Maskendesign.rsm environment. report can be used to export the screen design information to a text file. The text file can then be edited in the C++ development
ARIS Methods
4-159
Figure 4.4.1-43:
Example of a Screen Design for a Registration Dialog and Implementation in in C++.
ARIS Methods
4-160
4.4.1.9.13
Screen Navigation
In a Screen navigation you can either specify the structure of a screen that comprises several sub-screens, e.g. a Web site with several form fields or frames. Or you can describe the transition between various screens. The transition between the screens can be detailed. Example You want to show that a screen element has to be confirmed before the next screen can be accessed. Assign the triggering screen element (of the screen design model) using the contains connection to the screen. Then drag a calls type connection from the screen element to the following screen. The dependence of navigation on events can also be shown. When leaving a screen various events can occur. If for example a user has completed the registration page of an online shop, then the registration can either completed successfully or it can fail. This will determine whether the user moves to the contents page of the catalog or is returned to the registration page.
ARIS Methods
4-161
Figure 4.4.1-44: Example of Screen Navigation with Events
ARIS Methods
4-162
4.4.2 4.4.2.1
Design Specification Access Diagram
The relationships illustrated below between objects that have been explained in the design specification descriptions of the other views can be included in the access diagram of the control view. In order to make the illustration clearer, the individual dual relationships are dealt with separately.
4.4.2.1.1
Combining Functions with Data
As a first measure, the data flows between application systems types, module types or IT functions can be defined. For this purpose, an information flow object is created between the corresponding application systems or module types. In order to specify the data flow between system types in more detail, an eERM diagram, a relational diagram or a table diagram is linked with the data flow object. Thus, the data flow objects may be located either at the requirements definition level, at the design specification level or at the implementation level. An example is shown in Figure 4.4.2-1.
Figure 4.4.2-1: Information Flow between Application System Types
Besides the data flows, input and output data of every application system type, every module type and every IT function type can be expressed as data objects of the requirements definition or the design specification. The direction of the arrows indicates the whether it is an incoming (input) or outgoing (output) data flow.
ARIS Methods
4-163
An example is shown in Figure 4.4.2-2.
Figure 4.4.2-2: I/O Data at the Design Specification Level
4.4.2.1.2
Combining Organization with Data
The essential tasks to be carried out when linking data views and organization views at the design specification level are to define the responsibilities of organizational units for company data objects and determining the access privileges that essentially define which organizational units may access specific company data. The relationships thus established link the subject-related objects of the
organization view (organizational unit, position, person type, person etc.) with data objects of the relational diagram at the design specification level (relation, attribute, view). Therefore, these relationships are also allocated to the control view's design specification level. In order to define the access authorizations for relations or individual fields the relevant data objects can be assigned either positions or person types. This allows you to stipulate that a certain position is authorized to access particular fields, but also, by allocating person types, you can define business rules such as this field may only be accessed by department heads. An example illustrating this is shown in Figure 4.4.2-3.
ARIS Methods
4-164
Figure 4.4.2-3: Access Privileges
Besides the access authorization a definition of the responsibilities for the contents of a field or an entire relation is equally important. For this reason, a second connection called is responsible for can be drawn between the organizational units and the data objects in the relational diagram. Unlike access authorizations, responsibilities for data objects are mainly only assigned to a position in the company. Here, as well, business rules similar to the ones mentioned earlier can be defined by allocating person types. These rules are thus related to the responsibility for a data object. An example illustrating this is shown in Figure 4.4.2-4.
Figure 4.4.2-4: Definition of Responsibilities
ARIS Methods
4-165
4.4.2.1.3
Combining Organization with Function
The fact that the organizational aspects are linked to the functional aspects which have been defined at the design specification level basically answers the following questions: Who (which organizational units, positions, people, etc.) is responsible for the application system types and module types that have been specified in the function view at the design specification level or who uses these systems? Which locations (organizational view) within the company are using which application system types or module types? Which platforms available in the company (hardware component types
(organizational view)) are suitable to run which application system types? In order to answer the first question, connections can be drawn in the access diagram between the organizational units of the organizational chart (organizational units, positions and persons) and the objects of the application system diagram (application system type, module type, IT function, etc.). While doing this the significance of this relationship can be specified more precisely. We distinguish the following cases: An organizational unit may be responsible for an application system type as far as the subject-related aspects are concerned. An organizational unit may be responsible for the development of an application system type. An organizational unit may be a user of an application system type. The question of location may be addressed by assigning locations from the organization view to application system types, module types and IT function types. In the design specification we are not dealing with individual application systems in the sense of individual licenses but with application system types. Therefore, no actual application system locations are defined by means of this relationship (allocations of this kind are realized at the implementation level) but the possible locations for a particular application system type are pointed out.
ARIS Methods
4-166
The hardware component types available in a company are defined in the design specification of the organization view. In the control view, the relationship between these hardware component types and the application system types can be established. Thus, the hardware platforms which can run certain application system types, module types or IT function types are determined. At this stage, the desktop types, the operating system types and the DBMS types included in the function view can be allocated to the hardware component types as well. In the appendix of this manual you will find a list of all possible relationships occurring in an access diagram. Figure 4.4.2-5 shows examples of relationships.
Figure 4.4.2-5: Access Diagram (excerpt)
ARIS Methods
4-167
4.4.2.2
Program Structure Diagram
In the access diagram, you can create the relationships to the object types of the organization view and the data view for the application system types, module types and IT function types which have been specified in the application system type diagram (see Chapter 4.4.2.1). In this model type, you cannot directly illustrate the allocation of functions of the requirements definition. This allocation is done in the application system type diagram. Similarly, the possible chronological chain of events of the application system types, module types and the IT function types cannot be illustrated directly. Strictly following the ARIS architecture, you can only trace these links by navigating through a number of model types. However, model types (e.g. program flow-charts (PF),, see page 168), have been established that allow an integral view of all aspects of the system design. For this reason, ARIS contains the Program structure chart model type. It allows all relationships to application system types, module types and IT function types provided by the other model types of ARIS to be modeled regardless of the ARIS division into views. Moreover, you can display the chronological chain of events of the object types mentioned. For this purpose, events are also provided in this model type. Just as with assigning functions and events in the eEPC, you can define module sequences in the program structure chart. In this case the event should be understood as a trigger, triggering module types or application system types. To illustrate branching, you can use the familiar linking operators. Unlike an EPC, you can also define procedural sequences in the program structure chart without having to insert additional events.
ARIS Methods
4-168
4.4.2.3
Program Flow Chart (PF)
The program flow chart (PF) is used to show the procedural sequences of a program. The processing sequences are shown by the relationships between the objects. This diagram does not represent any data. The following figure shows a simplified example of the procedural sequence of an automatic teller. A strong implementation orientation is clear from the illustration of the procedure sequences.
Figure 4.4.2-6: Example of a Program Flow Chart (PF)
ARIS Methods
4-169
4.4.2.4
Screen Diagram
A screen diagram is used for describing screens during software development. Here, the goal is an automatic derivation of screen diagrams from the screen diagram. Therefore, screen diagrams display the structure and to a certain degree the functionality of screen diagrams. From left to right and top to bottom the screen diagram's structure corresponds to the geometry of the interface described. The central symbol is the "screen"; it corresponds to a window in Windows terminology. This window can have several tabs (Page symbol). In general, the interface can be divided geographically into areas using a table format (Section symbol for a row, and Column symbol for a column). The Section and Column symbols can be nested as desired in order to form complex interfaces. You can place tables (Screen table symbol), text entry boxes (COT attribute symbol) as well as graphics (Bitmap symbol) and text descriptions (Text symbol) on the interface. Using the Layout symbol you can assign display properties to the Screen, Page, Section, Column, Screen Table, COT Attribute, and Text objects. Additional symbols can be used to describe the screen interface. Figure 4.4.2-7 shows an example of a screen diagram. Figure 4.4.2-8 shows the screen derived from this.
ARIS Methods
4-170
Figure 4.4.2-7:
Example of a Screen Diagram
ARIS Methods
4-171
Figure 4.4.2-8:
Screen derived from the Figure 4.4.2-7 Screen Diagram
ARIS Methods
4-172
4.4.3
Implementation - Access Diagram (physical)
The issues dealt with in the design specification of the control view arise again at the implementation level. Unlike the design specification level, we are not examining the object types but instead real examples of the individual objects. We are addressing such relationships that exist between concrete application systems and organizational units, for example, and not those between application system types and organizational units. The relationships illustrated in the following are modeled in the access diagram (physical).
4.4.3.1
Combining Functions with Data
In order to find out which data flows between application systems occur, data flow objects can be created between the application system objects of the function view. Unlike the design specification level, these application system objects are not equivalent to application system types but to specific items (individual licenses). This means that application systems, modules and program element types can be interlinked by means of data flow connections. If it was defined at the design specification level that the SD Sales system version 2.1 module type could exchange data with the MM Material management system version 1.2, it would be shown at the implementation level that the specifically installed SD module, license number 1234 can exchange data with the MM module license number 2352 and with the MM module license number 34234. Both MM modules are of the MM Material management system version 1.2 module type. This fact is also illustrated in Figure 4.4.3-1.
ARIS Methods
4-173
Figure 4.4.3-1: Data Flow
In order to specify the data objects that are exchanged between the systems in more detail, corresponding model types in the data view are assigned to the data flow objects. Apart from the data flows between application systems, the input/output data of every application system can also be specified. There are two reasons for representing the relationships in an access diagram (physical). In the first case, the data objects are objects of a table diagram (table, field, view (physical)) which are situated in the data view of the implementation level. These data objects may be linked to application system objects of the design specification or the implementation level using the input/ output relationships. In the second case, the application system objects are the concrete application systems or modules of the implementation level which are linked to objects in the data view. Thus, the following general rule can be established: If one of the object types participating in an input/output relationship comes from the implementation level of the respective view, the relationships in the control view are represented at the implementation level (access diagram (physical)) as well. An example illustrating this is shown in Figure 4.4.3-2.
ARIS Methods
4-174
Figure 4.4.3-2: Input/Output Relationships
ARIS Methods
4-175
4.4.3.2
Combining Organization with Data
As before, we are considering the same questions we have dealt with in the design specification: Which organizational units are responsible for data objects? Who has access to which data objects? Which data objects are stored on which hardware components? Unlike the design specification, the relationships are now established to those data objects shown at the implementation level of the data view. This means that the responsibility for data objects is no longer defined for relationships and attributes of the relational diagram but for the physical structures, i.e. tables, fields and their specimens (table (specimen), field (specimen)). In order to represent these dependencies, connections are drawn between the objects of the organization view (organizational unit, position, person, etc.) and the table diagram's objects mentioned earlier (table, field, view (physical), etc.) in the access diagram (physical). When drawing a connection between the organizational units and the tables and fields the meaning of every relationship must be defined separately. Is responsible for means that this particular organizational unit is responsible for the contents of the respective table or field; accesses means that this particular position or person is authorized access to the data objects shown. In addition to the definition of access privileges and responsibilities you can use the hardware component object (organization view/implementation) to define on which hardware components that actually exist - and which can be uniquely identified using the inventory number, for instance - certain information objects of the company are located. For this purpose, the Hardware components object may be linked to information objects at the implementation level (tables, fields, etc.), the design specification level (relations, attributes) or the requirements definition level (entity types, data clusters, etc.) in the access diagram (physical). An example illustrating this is shown in Figure 4.4.3-3.
ARIS Methods
4-176
Figure 4.4.3-3: Assignments to Hardware Components
ARIS Methods
4-177
4.4.3.3
Combining Organization With Functions
The relationships defined in the access diagram (physical) between the objects of the organizational view and the function view enable the following questions to be answered: 1. Which application systems already run on which hardware components and which application system types could run on them? In order to illustrate these dependencies, the is platform of and may be platform of relationships can be modeled between the application system objects of the implementation level (application system, module, program element, etc.) or those of the design specification level (application system type, module type, etc.) and the hardware components object type of the organization view. An example is shown in Figure 4.4.3-4.
Figure 4.4.3-4: Hardware Component as Platform
2. Which organizational unit uses a specific application system? If the users that are accessing certain application system types are defined at the design specification level, we are now able to define this relationship at the implementation level for specific application systems (individual licenses). Thus, it is possible, for example, that in one company multiple licenses of the ARIS Toolset Version 4.1 application system type are available with different configurations. By
ARIS Methods
4-178
using an access diagram (physical) it is possible to show who is using which license. For this purpose, the Organizational unit, Position and Person object types may be linked with the Application system and Module object types with the is user connection. An example illustrating this is shown in Figure 4.4.3-5.
Figure 4.4.3-5: Users and Application System
3. Which application systems are installed at which locations of the company? In the design specification, the Application system type - Location relationship was used to define which application system types may be situated at particular locations of the company. In order to specify exactly where in the company the individual licenses that have been obtained for an application system type are used, it is possible to link locations with the Application system, Module and IT function object types in an access diagram (physical). An example illustrating this is shown in Figure 4.4.3-6.
ARIS Methods
4-179
Figure 4.4.3-6:
Location Allocations
All relationships available in the access diagram (physical) are summarized in the appendix.
ARIS Methods
Product/Service Modeling
4-180
4.5
ARIS provides various model types for describing the products and services performed in a company. A product/service is performed in the course of a value-added process. It is the result of a human act or a technical procedure. A product/service can be either an intangible service or a concrete product. Products can be a consumable product, a material type, an operating resource type, a technical operating supply type or a packaging material type. The trigger for the creation of a product/service is always the need of an organizational unit or a customer. A product is offered to the customer in the form of tangible goods. A service is an intangible product that is produced and consumed simultaneously. Providers of pure services are, for example banks, insurance companies and government agencies. The stronger the customer focus in the market segment of a provider of products, the more important it is for that provider to track and improve services in the product environment. The various model types of ARIS are therefore designed for use in describing not only pure products or services, but also combined products/services. You can use the following model types for product/service modeling: Product/service exchange diagram Product/service tree Product allocation diagram Product tree Product selection matrix Competition model
ARIS Methods
4-181
4.5.1
The
Product/Service Exchange Diagram

exchange diagram is used to map the creation of
product/service
products/services as well as their exchange within the company. A product/service can be either a service or a product and is represented by a corresponding symbol. Products can be material types, operating resource types, technical operating supply types and/or packing material types, that you are familiar with for example from the eEPC (material flow). Products/Services as input and/or output of functions can be connected with the starting or ending events of these functions. This product/service exchange between business functions can be used to advantage at an abstraction level that is situated between the value-added chain diagram and the eEPC. Along with the exchange relationships from a functional viewpoint, the exchange relationships of products/services can be illustrated from an organizational viewpoint. For this purpose, the product/service exchange diagram also offers several modeling options. Figure 4.5-1 gives an example of a product/service exchange diagram.
ARIS Methods
4-182
Figure 4.5-1: Example of Products/Services Exchange in a Software Company
ARIS Methods
4-183
4.5.2
Product/Service Tree
Products/Services can be viewed at different levels of abstraction. It is therefore useful to store these relationships in a model showing the partial products/services that make up a complete product/service. This static aspect is represented in the product/service tree. For example, a complex product often contains many different subassemblies, each of which consists of various components. Each of these items can be understood as a product/service. The has relation with connection, which is also permitted between
products/services in the product/service tree, can be used to describe other kinds of dependencies. These include the relationship between a consumer loan and the current account through which the repayments are effected. Substitution relationships to other products/services such as (potential)
replacement products or services can also be represented. In this static model the relationships of the products/services to the (company) objectives are also represented. Figure 4.5-2 gives an example of a product/service tree.
ARIS Methods
4-184
Figure 4.5-2: Product/Service Tree
ARIS Methods
4-185
4.5.3
Product Allocation Diagram
In addition to the general product/service diagrams which belong to the graphic models, the product models offer the possibility of creating a more abstract representation. The product allocation diagram is primarily used to analyze product creation in public administration. Like the product/service exchange diagram, this model type can be used to show which organizational units provide or use which products, and which functions are required for the creation of the products, or for which functions the products provide an input. In addition, the (legal) order basis of each respective product is shown here. The objectives to be accomplished with the various products can be represented as well. Figure 4.5-3 shows part of a product allocation diagram for a public service.
Figure 4.5-3: Example of a Product Allocation Diagram
The model type can also be used to describe aspects relating to the marketing of the product. These aspects will be described with reference to a simplified example of banking products. The growth of the Internet and the rising number of private Internet users over the past 10 years has been accompanied by the spread of online banking. At the same
ARIS Methods
4-186
time, the spending power of teenagers has increased, making them more important as a target group. As a result, the traditional current account service is now being offered in different forms: For example, it can be offered as a senior citizen account, with the holder being supported by the staff at a branch of the bank. This product is geared particularly to older customers who are less familiar with the new technologies, attach importance to personal support and advice from people they know and are no longer so mobile owing to their age. Above-average fees will probably be charged for such an account. At the other end of the scale, a current account may also be offered as a low-fee online "Teenager account". This product is aimed at teenagers aged between 12 and 20, who feel at home with Internet technology and have a lower budget. The fees must accordingly be at the lower end of the range. The following figures show product allocation diagrams for these two product variants:
Figure 4.5-4: Product Allocation Diagram - Current Account
ARIS Methods
4-187
Figure 4.5-5: Product Allocation Diagrams - Sales Products
The Teenager account and Senior-citizen account services have been created as object variants of the current account and are identified by the Sales product attribute. A sales product is a product/service rendered by a company that is offered under different names in different market segments. As a rule, different marketing instruments are used for the different sales products. The ARIS Variants component can be used to develop any number of sales products from a given product.
ARIS Methods
4-188
4.5.4
Product Tree
The purpose of the product tree is to analyze the composition of products in public administration. This model corresponds essentially to the product/service tree, whereby the possibility of modeling replacement products is dispensed with. The product tree is located at the requirements definition level of the product/service view. Figure 4.5-6 gives an example of a product tree.
Figure 4.5-6: Classification of the "Citizenry and Nationality Affairs" Product Group Using a Product Tree
ARIS Methods
4-189
4.5.5
Product Selection Matrix
In the product selection matrix the focus is on an organizational unit and the products that fall within its responsibility. These products can be allocated to the functions necessary for their production. The model is suitable as a starting point from which organizational charts, product trees and processes relevant to the creation of products can be navigated. An example of a product selection matrix is shown in Figure 4.5-7.
Figure 4.5-7: Product Selection Matrix of the Social Security Office
ARIS Methods
4-190
4.5.6
Competition Model
This model supports the analysis and evaluation of the competitive environment in which the company competes. The industry structure strongly influences the strategies which are potentially available to the company. In this model it is possible to represent relationships within a company, the resulting products and services, and market partners. It is also possible to represent which clients are using which products and services, which products and services are provided by suppliers and which replacement products and services are offered by (potential) competitors. Thus, a window on the competitive situation of the company can be represented. Figure 4.5-8 shows an example of a competition model.
Figure 4.5-8: Competition in the Sports Car Market
ARIS Methods
Unified Modeling Language in ARIS
5-1
5 Unified Modeling Language in ARIS

5.1 Introduction
UML (Unified Modeling Language) is an object-oriented modeling language. An OMG (Object Management Group) working group standardizes the language it constructs. UML is based on the object-oriented approaches of OMT, Booch and OOSE. UML model types in ARIS are based on the definition of the Unified Modeling Language, which consists of the UML Summary, UML Semantics (inc. UML Glossary) and UML Notation Guide documents currently in version 1.1. of September 1997. New releases have incorporated concepts from later UML versions in the ARIS method. Up-to-date information on UML can be found at http://www.omg.org or http://www.rational.com/uml. Because ARIS UML models are oriented to the standard and no official German translation of the standard currently exists, model types (diagrams), object types, relationship types and attribute types taken from UML have English identifiers, even in the German version (interface language: German). The UML model types can be found in the control view of the requirements definition. You will be offered the following model types: UML Activity diagram, UML Class diagram, UML Class description diagram, UML Collaboration diagram, UML Component diagram and UML Use case diagram.
ARIS Methods
5-2
5.2 The UML Models

5.2.1 UML Class Diagram
The UML Class diagram model type maps the static relationships between model items such as class, object, and interface. Classes are defined in the UML Class diagram. These can be assigned with the relevant operations (methods) and attributes using the has member relationship. The quickest way to create has member relationships between a class already placed in the model and a new operation or a new attribute is as follows: Click on the Operation or Attribute symbol in the modeling toolbar. Move the mouse pointer over the desired class and click the left mouse button. The new object will be placed underneath the class. As is usual in UML, the has member relationship created is invisible. Additional important information on UML modeling support Content tab of the ARIS Online Help via the Designer/Valuable Information/Models/UML Models. The relationships that classes have with each other are also modeled in the UML Class diagram with the associates connection. The connection occurs directly between two objects of the Class type for binary relationships. An inserted association depicted as a diamond-shaped symbol is used to connect multiple relationships. If the Association is itself a class, a link can be made with the supplies properties for connection. The multiplicity of associates connections can be specified in the Multiplicity (Src) (= source) and Multiplicity (Trg) (= target) attributes of the associates connection. can be found on the path: ARIS
following
ARIS Methods
5-3
In UML, Aggregation and Composition represent special associates relationships. They are specified via an entry in the Aggregation kind attribute of the associates connection and represented by a small white (aggregation) or black (composition) diamond symbol at the end of the associates connection. Figure 5.2.1-1 shows examples of this. The Association class, which represents an association with class properties, has been adopted from UML 1.4. Objects of the Class type can be assigned to an Association class by means of an associates (multiple) type connection. This concept can be used instead of the association, class and supplies properties for construct described above.
Figure 5.2.1-1: UML Class Diagram - Associations
The inheritance relationships which exist between classes are represented by the generalizes relationship and are expressed as a triangular symbol. Attributes and operations of a superior class will be passed on to subordinate classes. An example of this is shown in Figure 5.2.1-2.
ARIS Methods
5-4
Figure 5.2.1-2:UML Class Diagram - Inheritance Relationships
Additional model items available in the UML Class diagram are Packages, which are used for classifying model items; Notes, for remarks; Objects for Class instances, and Interfaces. An interface depicts a class interface (supports connection). By calling the interface (calls connection), other classes use the class provided by the interface. Other additions from UML 1.4 are: The Enumeration Literal, which defines the possible enumerations of a class. The Parameter, which can be assigned to an operation as an Input/Output parameter. The Constraint object, which can be used to display restrictions on various model items.
ARIS Methods
5-5
5.2.2
UML Class Description Diagram
The UML Class description diagram model type is a supplement to the standard UML models. It allows classes to be specified more exactly. The modeling options in the UML Class description diagram are a subset of the UML Class diagram options, i.e., all UML Class description diagrams modeling options are also available in UML Class diagrams. Attributes, operations, notes, objects, and interfaces can be allocated to the classes in the UML Class description diagrams. These allocations can also be made in a UML Class diagram, but it is recommended that you carry modeling separately in a UML Class description diagram to avoid overloading the UML Class diagram with graphics. In this case, the UML Class description diagram must be defined as an assignment to the class of a UML Class diagram. Attributes, operations, notes, objects and interfaces of the class that are generally relevant, but are not essential in a UML Class diagram, can then be moved to the UML Class description diagram. If you have already described a class in a UML Class diagram and want to move it to an assigned UML Class description diagram, click on the Assignments/Hide menu item of the class object's pop-up menu.
5.2.3
UML Use Case Diagram
In a UML Use case diagram, application cases (use cases) and the actors involved in the use cases are described. Actors represent users who use an application system to perform their tasks. The UML Use case diagram describes a system's external behavior from the users perspective. In ARIS, actors are depicted as special symbols of the following object types: Person type Application system type Person Position Group Organizational unit
ARIS Methods
5-6
Actors and use cases can be associated with each other using communicates with or can support type relationships. Relationships of the communicates with type express the fact that the actor performs the use case. Relationships of the can support type express the fact that the actor's may be called upon to perform the use case. Relationships between use cases are established with a generalizes relationship, whose connections are represented by a triangular arrowhead. The desired semantics can be assigned to the Stereotype attribute of this relationship. The UML standard suggests the Extends and Uses stereotypes to do this. Extends represents an extended relationship in which one use case extends the application of another use case, for example in exceptional situations. Uses represents a uses relationship. In this case, the use case uses the application case description of another use case, so that it can be reused. Figure 5.2.3-1: shows a typical model of a use case diagram. The Package and Note object types are also available in the UML Use case diagram. The following model items have been integrated from UML 1.4: Association, used to show association relationships between use cases and actors. Extension point, used to describe the extension possibilities of a use case in more detail. Constraint , used to display the constraints for various model items.
ARIS Methods
5-7
Figure 5.2.3-1: UML Use Case Diagram
5.2.4
UML Activity diagram
A UML Activity diagram describes the process as a sequence of activities. In UML, activities always refer to objects. Accordingly, activity diagrams are allocated to a class, an operation, or a use case and must describe the respective internal process. Because activity diagrams are considered to be a special form of finite automaton, the sequence of an activity diagram must begin with an Initial state
ARIS Methods
5-8
and end with a Final state. Activities represent a status with an internal action and one or more outgoing transitions. The transitions are represented by connections producing relationships between the activities. Activities may have simple relationships with other activities as well as multiple incoming and outgoing relationships: 1. Several outgoing conditions can be formulated as Decision conditions
(diamond). Modeling a condition with the Decision symbol is optional; alternatively, users could simply model several outbound connections. It is recommended that the condition in the Connection role attribute of the is predecessor of or activates relationship connections be maintained and shown in the model. 2. The Split/Synchro symbol (vertical or horizontal line) can be used to activate several subsequent activities at the same time, or to make the activation of an activity dependent on the transitions of several preceding activities. Activities may assume specific object states and create specific object states as a result. Object states are represented by the Object state object type, which possesses has input or has output connections (dashed arrows) as relationships with activities. UML uses "swimlanes" to represent the organizational responsibility for the performance of activities. A swimlane is a column listing all activities for which an organizational unit is responsible. The ARIS UML Activity diagram includes a predefined table with two rows for this purpose. The responsible organizational unit (an Internal person, a Position, a Person type, an Organizational unit, or a Group) is placed in the top row, and the bottom row is for Decision, Split/Synchro, Object state and Note. Figure 5.2.4-1 shows a UML Activity diagram with the relevant components.
ARIS Methods
5-9
Figure 5.2.4-1: UML Activity Diagram
ARIS Methods
5-10
5.2.5
UML Statechart Diagram
Like UML Activity diagrams, UML Statechart diagrams depict automatic status and describe a similar situation. However, the statechart diagram focuses on object states. It describes the sequence of states that an object can assume in the course of its existence. Furthermore, it can contain actions related to the state. These actions are either prerequisites for the entry of a state (entry/), are executed during the state (do/), or are executed upon leaving the state (exit/). The UML Statechart diagram in ARIS provides the State symbol. State transitions, also called transitions, serve as directed connections (has transition to) to link the states. As with the UML Activity diagram, a statechart must begin with an initial state and end with a final state. Figure 5.2.5-1 shows a UML Statechart diagram.
Figure 5.2.5-1: UML Statechart Diagram
ARIS Methods
5-11
5.2.6
UML Collaboration Diagram
The UML Collaboration diagram represents the interactions between objects that occur in the form of message exchanges. Objects represent specific examples of classes. They are also called instances. Message exchange is modeled using an interacts with relationship. The exact meaning of an interacts with connection is provided by the occurrences of the Condition, Message number, Operation and Parameter attributes. These attributes function as follows: Condition: Indicates a condition in the form of other messages that must have been sent before the current message can be sent. The other messages and their respective message numbers are given in a list format. If no other prerequisite messages exist, the condition becomes unnecessary. Enter a slash (/) at the end to separate the Condition from the Message number. Message number: Is a unique message number in the model. Messages are sorted in ascending order. If an operation currently processing a received message sends several additional messages, the old number will be supplemented with a "sub-number" separated by a full stop (e.g. an operation receives Message 3.4 and sends two messages with the numbers 3.4.1 and 3.4.2). Enter a colon (:) at the end to separate the Message number from the Operation. Operation: Specifies the operation of the class of the object that is to be executed. Parameter: Specifies the parameter list for the called operation. Enclose the parameter list in round brackets. Place these attributes on the connection in the specified sequence.
ARIS Methods
5-12
Figure 5.2.6-1: UML Collaboration Diagram
ARIS Methods
5-13
5.2.7
UML Component Diagram
UML has the capability to depict aspects relevant to implementation such as the code structure (component) and the system runtime structure (deployment) in model form. ARIS makes the UML Component diagram available for this purpose. Components are items that form units, e.g. executables, at the time they are compiled or linked, or at system runtime. The first type of relationship between the components represents the physical structure of the components. A component can be contained in another component. This is shown by a contains connection between the components. The second type of relationship between the components is the call relationship. One component calls another via an interface, shown by a small circle. The component containing an interface is connected with a supports relationship (single dash), and the component using the interface is connected via a calls relationship (dashed arrow). The component configuration can still be specified while the system is running (deployment). For this, the components are grouped and allocated to packages (also called nodes). Assignment is done with a contains connection between a component and its package. It is also recommended to place the components graphically in the Package objects. Figure 5.2.7-1 shows an example of a UML Component diagram.
ARIS Methods
5-14
Figure 5.2.7-1 : Example of a UML Component Diagram
ARIS Methods
5-15
5.3 Integrating UML Diagrams and Other ARIS Models

5.3.1 Fundamental Relationships between Models
The various models in ARIS are related to each other. Modeling and the direct modeling of connections between objects provide two basic mechanisms for depicting these relationships: The first option is that the same objects can be used in different models. For example, the Function object type exists both in the eEPC and the Function tree. The same object types may be depicted with different symbols and symbol names in different models. This is usually the case when the icon depiction and name are required by one method (e.g., UML), but object types with the same semantics also exist in other model types. For example, functions (of the eEPC, Function tree, etc.) and Operations (in the UML Class diagram) have different symbols, but they represent the same object type. Therefore, the same object may occur both as a Function and as an Operation. Its attributes are identical in all models. Identical objects can be created using Copy and Paste or by creating an object with the same name as an existing object (in the Object Selection dialog box). The second option is to assign a model to an object (create the object assignment in the Properties - Object dialog box, Assignment tab). In principle, the object specification can be defined more exactly with the assigned model.
ARIS Methods
5-16
Correspondence between UML and ARIS objects: UML Objects Activity UML Model ARIS Models and Objects etc.) Operation UML Class diagram, diagram Attributes UML Class diagram, diagram Actor UML Use case diagram Actor (tech.) UML Use case diagram ERM attribute (eERM, eERM etc.) Person Type (eEPC, Organizational Chart) Application system type (eEPC, Program structure chart, Access diagrams etc.) Actor (person) UML Use case diagram Actor (position) UML Use case diagram Actor (group) UML Use case diagram Actor (organizational unit) UML Use case diagram Person (eEPC, Organizational chart) Positions (eEPC, Organizational chart) Group (eEPC, Organizational chart) Organizational unit (eEPC, Organizational chart) Function (eEPC, Function tree,
UML Activity diagram Function (eEPC, Function tree,
UML Class description etc.)
UML Class description attribute allocation diagram, eEPC
ARIS Methods
5-17
UML Objects Use Case
UML Model UML Use case diagram
ARIS Models and Objects Function (eEPC, Function tree)
State
Statechart diagram
Object State, Performance (eEPC, etc.)
Object state
Activity diagram
Object State, Performance (eEPC, etc.)
The object type identity of Operation and Activity flows from the identity of the object types for Activity and Function and Operation and Function. The same applies to State and Object state. The relevant objects in the UML diagrams can have the following assignments: UML Objects Class Assignable Models Quick model, eEPC (all forms), eERM, Technical terms model, IEF data model, OMT class description model, OMT dynamic model, SAP SERM, SeDaM model, UML Activity diagram, UML Class description diagram, UML Class diagram, UML Statechart diagram, Access diagram, Access diagram (physical) Operation/Activity/Func Quick model, DW transformation, e-Business scenario tion/Use Case diagram, eEPC (all forms), Function tree, Function allocation diagram, Industrial process, Information flow diagram, Material flow diagram, Office Process, Program structure chart, Process selection matrix, RAD, Role diagram, SAP ALE filter model, SAP ALE function model, SAP ALE message flow model, SAP applications diagram, System attributes, UML Activity diagram, UML
ARIS Methods
5-18
UML Objects
Assignable Models Collaboration diagram, UML Use case diagram, PCD, PCD (material flow), Value-added chain diagram. Objective diagram
Attribute/ERM attribute Quick model State/Object State/Performance eEPC, eEPC (material flow), Function Tree, Industrial Process, Performance Exchange Diagram, Performance Exchange Diagram (graphic), Performance Tree, Performance Tree (graphic), Office Process, Product Selection Matrix, Product Tree, Product Allocation Diagram, Process Selection Matrix, UML Statechart diagram Package UML Activity diagram, UML Class description diagram, UML Class diagram, UML Collaboration diagram, UML Component diagram, UML Statechart diagram, UML Use case diagram Actor/Person type/Application system type/Organizational tion Decision/Split/Synchro/ Rule Diagram Rule Application system type diagram, Quick model, Yearly calendar, Organizational chart, Program structure diagram, Program flow-chart (PF), UML Class diagram, UML Component diagram, System attributes, Shift
unit/Group/Person/Posi calendar, Knowledge map, Access diagram
ARIS Methods
5-19
5.3.2
Relationships between UML Models
This chapter describes the recommended relationships for the possible connections.
5.3.2.1
UML Class Diagram and UML Class Description Diagram
A UML Class description diagram is used to assign the class of a UML Class diagram. When the assignment is created, the Class is automatically inserted in the UML Class description diagram, where it can then be specified further. The same attributes and operations can be used in both the UML Class diagram and the UML Class description diagram. If you have already described a class in a UML Class diagram and want to move it to an assigned UML Class description diagram, click on the Assignments/Hide menu item of the class object's pop-up menu. Packages can be assigned using a UML Class diagram, which allows class affiliations to a package to be modeled. Contains relationships are automatically made to all object types contained in the assigned model.
5.3.2.2
UML Class Diagram and UML Activity Diagram
The class of a UML Class diagram or UML Class description diagram can be assigned using a UML Activity diagram to model an internal process. The operations of the class can then be used as an activity in the UML Activity diagram. A UML Activity diagram can also be assigned to an operation.
ARIS Methods
5-20
5.3.2.3
UML Class Diagram and UML Statechart Diagram
The class of a UML Class diagram or UML Class description diagram can be assigned using a UML Statechart diagram for modeling individual states in which the class may be found. The states of the UML Statechart diagram can be identical to the Object states of a UML Activity diagram that is also assigned to the class. The Operations of the Class or the Activities of the UML activity diagram should be maintained as values for the Connection role attribute of the connections (has transition to) between the states.
5.3.2.4
UML Class Diagram and UML Collaboration Diagram
UML Collaboration diagrams show the interaction between object instances (object). Therefore, modeling the relationships of the objects to the object classes (class) of the UML Class diagrams is recommended. For this purpose, a relationship must be created between a class and the respective objects in the UML Class diagram or UML Class description diagram using a has instance connection. After being allocated between Class and Instance, the object can be used in a UML Collaboration diagram. The names of the operations in the specification of the interacts with connection (Operation attribute) between the objects must be defined as an operation of the associated class in a UML Class diagram or UML Class description diagram.
5.3.2.5
UML Use Case Diagram
The use cases of a UML Use case diagram can be organized hierarchically. They can consist of additional (sub)application cases. To enable this relationship, assign a use case to a UML use case diagram. A UML Activity diagram or UML Collaboration diagram can also be assigned to a use case to model the process.
ARIS Methods
5-21
5.3.3
Relationships to Other ARIS Models
Integrating UML's object orientation and the process orientation of business process modeling was the primary concern in our consideration of relationships to other ARIS models. Therefore, the integration of the UML Class diagram in the eventdriven process chain (eEPC) deserves special emphasis. The eEPC is used for modeling processes, especially in connection with business processes. You will find a detailed description in: IWI vol. 144 - Loos, P., Allweyer, Th.: Process Orientation and Object-Orientation - An Approach for Integrating UML and Event-Driven Process Chains (EPC), Publication of the IWI, Saarbrcken 1998, http://www.iwi.unisb.de/iwi-hefte/heft144.zip.
5.3.3.1
UML Class Diagram and eEPC
The eEPC contains many object types that are also used in UML models. In addition, as described in section 5.3.1, some objects in the eEPC are of the same object type as the UML objects, only different symbols are used. Classes can be used in an eEPC using the is input for and has output connections as an information source and information target for functions. If a less or more detailed description of the input and output is desired, the input and output relationship can also be created from function to package and attributes. Thus no physical reading or writing is depicted but subject related information is created or used. A function can be implemented using one or more operations of a class. To do this, functions and operations may be connected with the calls connection or, because of object type identity, functions may be used directly as operations in the UML Class diagram. An eEPC can be used to describe the processing sequence within a class or an operation. eEPCs can be assigned to both object types for this.
ARIS Methods
5-22
5.3.3.2
UML Statechart Diagram and eEPC
The states in the UML Statechart diagram can be used in an eEPC either as an Object state symbol or as a Performance symbol. These symbols can be assigned to the functions using the has output of and is input for connections. Because events can also represent object states, there may be semantic redundancy if all object states are modeled in an eEPC. If both the event and the object state or performance are to be modeled despite this, semantic equivalency can be represented using a corresponds to connection.
5.3.3.3
UML Use Case Diagram and eEPC
Users who wish to use UML Use case diagrams can make the connection to the eEPC processes in two ways: Describe the process in a use Case with an eEPC that is assigned to the use case. Specify the function of an eEPC in more detail using a UML Use case diagram. The UML Use case diagram is assigned to this function. When modeling actors in a UML Use case diagram, the object type identity of actors with the various organizational elements and the application system type should be used to ensure consistency with the procedural organization in the eEPC organizational structure (e.g., in the organizational chart).
5.3.3.4
UML Activity Diagram and eEPC
The process description contained in a UML Activity diagram can also be described with an eEPC. This has the advantage of allowing the full potential of the eEPC to be exploited. If both model types are used redundantly to represent the same factual information, the redundancy should be kept to a minimum by the use of the same objects in both models (e.g., Organizational unit) or by using object type identity in the case of different symbols (e.g., Activity and Function). Content can be copied (using Copy and Paste) from the eEPC to the UML Activity diagram and vice versa, making it easier to handle both models simultaneously. The symbols
ARIS Methods
5-23
for Activity and Function change automatically when copied. However, model content can be copied only into object types that are available in the other model type. Because the eEPC has a large number of object types, a large portion of its modeled semantics (e.g., all information carriers such as File, Document and Expertise, and the detailed organization allocation of functions, etc.) may be lost in a transfer to a UML Activity diagram.
5.3.3.5
UML Class Diagram and eERM
If information systems for requirements definitions designed with an object-oriented perspective need to be implemented using relational database management systems, the data structures can be modeled most effectively with entity relationship models in the eERM. For this, classes of UML Class diagrams or UML Class description diagrams can be assigned with eERMs and the ERM attributes can be reused as attributes to describe the class.
5.3.3.6
UML Use Case Diagram and eEPC
If UML Use case diagrams must be used in conjunction with an eEPC, the recommended procedure is to model the process within a use case by assignment of an eEPC.
ARIS Methods
Using the Object Modeling Technique (OMT) Modeling Method
6-1
6 Using the Object Modeling Technique (OMT) Modeling Method

6.1 Introduction
ARIS provides an additional option for object-oriented modeling, the Object Modeling Technique graphic notation (OMT) (cf. Rumbaugh, J.; Blaha, M.; Premerlani, W.; Eddy, F.; Lorensen, W.: Object-oriented modeling and designing. Munich et al. 1993). Meanwhile, OMT, along with the Booch and OOSE methods, has been integrated and refined into the Unified Modeling Language (UML), which is also offered in ARIS (see Chapter 5: Unified Modeling Language in ARIS). OMT is still offered to allow compatibility with older versions of ARIS Toolset. However, we recommend using Unified Modeling Language rather than OMT. Below we shall describe the component parts of the OMT methodology. Furthermore you will find out how to use the modeling techniques in ARIS. This description does not replace the detailed description of modeling techniques in the original literature. Its basic objective is to explain the handling of the modeling techniques within ARIS.
6.2
Summary of the OMT Methodology
The OMT methodology has been designed to present different points of view in describing a system. For this purpose, the following methods are used: Object Modeling Dynamic Modeling and Functional Modeling These three views are orthogonal to each other, but cannot be viewed as being entirely independent of one another.
ARIS Methods
6-2
Object Modeling represents the static, structural and data-related aspects of a system. The structure of objects, their relationships to other objects, and their attributes and relationships are illustrated. Dynamic Modeling illustrates the time-, behavior- and control-related aspects of a system. The sequence of operations is described by mapping the sequences of events. Functional Modeling clarifies the transient and functional aspects of a system. The transformation of values is described here. Between them these models contain references to other models: The object model describes, for example, data structures that are used in the dynamic model and functional model. The processes in the Functional Model correspond to the operations in the Object Model. A state diagram of the Dynamic Model describes - in whole or in part - the behavior of a class object in the Object Model.
6.3
Using the OMT Diagram Technique in ARIS
The following pages illustrate how the constructs conceived in the OMT methodology are illustrated, used and related to each other in ARIS. The modeling constructs defined for OMT (e.g. Class, Process, State) do not overlap with other modeling constructs within ARIS (e.g., Event, Function, Entity type, etc.) and thus can only be reused within OMT diagrams. Hence, the OMT model techniques must be seen as an "independent" methodology.
6.3.1
OMT Object Model
Representation of Instances In object-oriented modeling, objects must generally be documented on the type level (i.e., class level). However, it might make sense to model individual instances as well. The respective symbol in ARIS is a blue rectangle with rounded corners (cf. Figure 6.3.1-1):
ARIS Methods
6-3
Figure 6.3.1-1:Representation of Instances
Representation of Classes Classes represent the basic structures of the field of the application to be modeled. They are illustrated in ARIS by a blue rectangle (with horizontal lines, (cf. Figure 6.3.1-2).
Figure 6.3.1-2: Representation of Classes
Assigning Instances to Classes If you need to illustrate instances, you can make the assignment to the respective classes clear. The corresponding connection has the semantic is instance of (cf. Figure 6.3.1-3).
Figure 6.3.1-3: Assigning Instances to Classes
ARIS Methods
6-4
Assigning Attributes to Classes The characteristics of classes are described using attributes. When modeled in ARIS, these are separate objects (and thus also separate symbols) linked to the corresponding classes with connections (with the meaning has attribute, (cf. Figure 6.3.1-4). The separation into two different object types (classes and attributes) is necessary in order to take full advantage of the navigation and report creation capabilities of ARIS. For each attribute, you can specify whether it is a class (the value is relevant for all instances of the class) or instance attribute.
Figure 6.3.1-4: Assigning Attributes to Classes
Assigning Operations to Classes The functionality assigned to classes is described by defining operations (methods). Here too, a separate object type has been defined which can be related to classes (with the semantic has operation, (cf. Figure 6.3.1-5).
Figure 6.3.1-5: Assigning Operations to Classes
ARIS Methods
6-5
Associations between Instances Individual instances can be linked to each other. These links are illustrated in ARIS using non-directional connections of the is linked to type (cf. Figure 6.3.1-6).
Figure 6.3.1-6: Associations between Instances
Associations between Classes Links (associations) can also exist between classes. You are already familiar with these links from the Entity Relationship Model. They are illustrated by their own symbol (yellow diamond), which enables you to illustrate n-relationships in the same way (see below). The connections are drawn from the class symbol to the diamond symbol and can be assigned degrees of complexity, for which the Multiplicity attribute of the connection is used. The following entries are possible for Multiplicity, some of which also result in a corresponding graphic representation of the connection: 1 c cn n
Figure 6.3.1-7: Associations between Classes
ARIS Methods
6-6
N-Associations between Classes Three figure (or even n) associations between classes are illustrated by linking a third class (or fourth, fifth, etc.) with the diamond symbol defining the link (cf. Figure 6.3.1-8).
Figure 6.3.1-8: Ternary Relationship between Classes
Modeling an Association as a Class An association can also be understood as an independent object and interpreted as a class. This can be expressed by drawing a directional connection from the diamond symbol to one of the class symbols where you can then list all attributes and operations (cf. Figure 6.3.1-9). Of course, this "reinterpreted" class can in turn be associated with other classes.
Figure 6.3.1-9: Modeling an Association as a Class
ARIS Methods
6-7
Representing a Qualified Association A qualified association adds qualification information to a normal association. This qualifying information is a labeled attribute that reduces the cardinality of an association. This makes sense for 1:m and n:m associations since the objects on the m side of an association are differentiated in this manner. A qualifying association is illustrated by adding the qualification information on the connection. For this purpose, we have introduced a separate Qualifier attribute that (as with all attributes) can also be displayed in the graphic (cf. Figure 6.3.110).
Figure 6.3.1-10: Illustration of a Qualified Association
Representation of Orders for Associations If the objects on the n side of an association are arranged in a certain order, you can note this explicitly in the graphic (cf. Figure 6.3.1-11). For this purpose there is a separate attribute on the connection between the Class and Association symbols.
Figure 6.3.1-11: Illustration of Orders for Associations
Aggregation between Classes An aggregation represents a "part-whole" relationship and can be understood as a special form of association. This relationship is modeled as a directed relationship
ARIS Methods
6-8
between classes (with the aggregates connection type). In the graphic, a white diamond symbol is used to for the class representing the "Whole" (component group) (cf. Figure 6.3.1-12).
Figure 6.3.1-12: Aggregation between Classes
Generalization and Inheritance One basic construct of object-oriented modeling is the definition of hierarchies between classes, which includes the inheritance of attributes and operations from superior to subordinate classes. In ARIS, there is a separate object type for this (green triangle) linked to the participating classes (cf. Figure 6.3.1-13). Thus, multiple inheritances can also be illustrated. With regard to the generalization operator, you can add an attribute that indicates the aspect used for generalization/specialization and whether the specialization is disjunctive or non-disjunctive.
Figure 6.3.1-13:
Representation of the Generalization/Specialization Relationship between Classes
ARIS Methods
6-9
Restrictions (Constraints) for Classes, Attributes and Associations Restrictions (Constraints) are functional relationships between the classes,
attributes and associations of an OMT Object model. In ARIS, we have defined separate object types (black dot) for the definition of constraints on attributes. Figure 6.3.1-14 shows an example which shows that the height-to-width ratio for windows can take values from 0.7 to 1.7.
Figure 6.3.1-14: Illustration of Constraints on Attributes
You can also define restrictions between associations. Figure 6.3.1-15 shows an example which expresses that the set of persons forming the board of a committee naturally represents a subset of all members. This fact can be expressed by drawing a directional connection between the association symbols.
Figure 6.3.1-15: Illustration of Constraints on Associations
ARIS Methods
6-10
Example of an OMT Object Model Figure 6.3.1-16 shows a typical example of an OMT Object model including the major modeling constructs.
Figure 6.3.1-16: Example of an OMT Object Model
ARIS Methods
6-11
6.3.2
OMT Dynamic Model
The OMT Dynamic model is a set of state transition diagrams where one state transition diagram usually describes the behavior of one class. The states are interlinked by means of directional connections that represent the events. Representation of Initial, Final, and Transition States ARIS contains three symbols to differentiate between initial states, final states and normal states (cf. Figure 6.3.2-1).
Figure 6.3.2-1: Representation of Initial, Final, and Transition States
Transition between States Transitions between states are triggered by events. The connection between two states is of the has transition to type (cf. Figure 6.3.2-2).
Figure 6.3.2-2: Representation of the Transition between States
You can add further information to the states and the transitions. To describe the start, end and internal actions with the state, use the attributes do/action, entry/action, exit/action and event/action. The condition for a transition can also be described in more detail in the connection between two states (cf. Figure 6.3.2-3).
ARIS Methods
6-12
Figure 6.3.2-3: Representation of Additional Information with State Transition
ARIS Methods
6-13
Example of an OMT Dynamic Model The following Figure 6.3.2-4 shows a typical example of an OMT Dynamic model.
Figure 6.3.2-4 Example of an OMT Dynamic Model
ARIS Methods
6-14
6.3.3
OMT Functional Model
With the help of data flow diagrams, the OMT Functional model shows how to derive the output data from the input data during a calculation. Representation of DataStores DataStores are used for passive data storage. In ARIS, they are represented by two horizontal lines (cf. Figure 6.3.3-1).
Figure 6.3.3-1: Representation of DataStores
Representation of Processes Processes transform data and are represented in ARIS as yellow ellipses (cf. Figure 6.3.3-2).
Figure 6.3.3-2: Representation of Processes
Representation of Actors An actor is an object that activates the data flow by creating or consuming data values. Thus, actors can be understood as the sources and sinks of the graph and are represented by a white square (cf. Figure 6.3.3-3).
Figure 6.3.3-3: Representation of Actors
ARIS Methods
6-15
Representation of Data Flows Data flows connect the input of one process or object with the input of another. They are modeled as objects of the Data value type between objects and are generally labeled with a description of the data (cf. Figure 6.3.3-4).
Figure 6.3.3-4: Representation of Data Flows
Splitting Data Flows If a data value is to be sent to different locations, the data flows can be split. ARIS uses its own symbols (connections) to represent such splits (cf. Figure 6.3.3-5).
Figure 6.3.3-5: Representation of Data Flow Splitting
ARIS Methods
6-16
Example of an OMT Functional Model Figure 6.3.3-6 shows a typical example of an OMT Functional model.
Figure 6.3.3-6: Example of an OMT Functional Model
ARIS Methods
6-17
6.3.4
How Objects Can Be Arranged in a Hierarchy
The Class object type can be arranged in a hierarchy with an OMT Dynamic model to document transitions within this class. The Class object type can be arranged in a hierarchy with an OMT Class description model to allocate attributes and operations to this class. The possible relationships in this model represent a subset of the OMT Object model. The State, Final State and Initial State object types can also be represented in more detail with an OMT Dynamic model to enable a state to be described on various hierarchy levels. The Process object type can be represented in more detail with an OMT Functional model to enable data flows to be described on various levels. The DataStore object type can be arranged in a hierarchy with an OMT Object model. The connection types in the OMT Functional model can be represented in more detail with an OMT Object model and an OMT Data value decomposition model to document the details of a data flow.
ARIS Methods
Methods for Knowledge Management
7-1
7 Methods for Knowledge Management

7.1 Introduction
The objective of Knowledge management is the systematic control of knowledge, an increasingly important company resource. It encompasses the development, monitoring, support and improvement of strategies, processes, organizational structures and technologies for effective knowledge processing within a company. This includes all activities relating to the acquisition, preparation, transmission, and utilization of knowledge. These knowledge management activities generally do not occur in isolation; they occur primarily in the operative and directive business processes of the company. Hence, an integrated view of business processes, knowledge processing, organizational structures, information systems, etc. is needed. Most of these aspects can be depicted using older ARIS methods such as eEPCs, organizational charts, function allocation diagrams, eERMs, etc. However, if we want accurate representation, analysis, and improvements to knowledge management, we need additional means of representation to identify and structure the content of relevant knowledge categories, to describe the distribution of knowledge within an organization, and to model knowledge creation and utilization in business processes. For this reason, two new object types, Knowledge Category and Documented Knowledge, and two new model types, Knowledge Structure Diagram and Knowledge Map, have been added. In addition, existing model types for the representation of business processes (eEPC, PCD, Office Process, and other similar items) were expanded to include constructs for handling knowledge creation and utilization. The new object and model types are fully and methodically integrated into the other most important model types of the requirements definition (such as eERM, organizational chart, and function tree models), ensuring an integrated perspective. This would, for example, allow models from a project on business process optimization to be used to analyze and improve knowledge management as well.
ARIS Methods
7-2
The knowledge structure diagram is located in the requirements definition data view. The knowledge map, like the expanded model types for business process modeling, is in the requirements definition control view.
7.2
7.2.1
Object Types for Modeling Knowledge Processing

Knowledge Category
thought bubble
The object type Knowledge category, represented by an oval
(see Figure 7.3.1-1) an object with content referring to specific knowledge. Examples of Knowledge categories are: Project Management Knowledge, Specific Industry Knowledge, Specific Technology Knowledge, Customer and Competitor Knowledge, etc. These categories assist in classifying the knowledge a company possesses or needs. Knowledge placed in a particular knowledge category could be implicit knowledge, that is, knowledge that cannot be fully documented, employee or group knowledge in the form of skills, or explicit knowledge that can be documented in the form of a description or technical drawing. Knowledge categories often contain both. For example, project management knowledge could include both project managers' experiences and tips in a project management handbook. The following specific attributes, in addition to general attributes like Description, Remark, Source, etc. serve to describe knowledge categories in more detail:
ARIS Methods
7-3
Attribute name Updating frequency
Value range Enumeration type: hourly, daily, weekly, monthly, never
Description/Example The updating frequency describes how often the knowledge of the relevant category must be refreshed to be up-to-date. Basic trigonometry knowledge, for example, must never, whereas knowledge of certain stock prices must be updated daily or even hourly. The significance of the knowledge category for the company can range from 0% (totally unimportant) to 100% (extremely important).
annually, rarely, be refreshed rarely or, for practical purposes,
Significance
Percentage: 0..100
Degree of Coverage
Percentage: 0..100
The current degree of coverage for the relevant knowledge in the company can range from 0% (not covered at all) to 100% (maximum possible coverage). If the degree of coverage of a knowledge category must be represented by a particular organizational unit or person, use the appropriate attribute of the disposes of connection type in a knowledge map.
Advantage of knowledge
Percentage: 0..100
The relative headstart of your company over the competition in terms of knowledge can range from 0% (the competition has the greatest possible advantage over your company) to 100% (your company has the greatest possible advantage over the competition).
Knowledge Utilization
Percentage: 0..100
The degree of utilization of a particular knowledge category can range from 0% (relevant knowledge not utilized at all) to 100% (optimal utilization of relevant knowledge).
ARIS Methods
7-4
Attribute name Desired Degree of Coverage
Value range Percentage: 0..100
Description/Example The desired degree of coverage for relevant knowledge can range from 0% (not covered at all) to 100% (maximum possible degree of coverage).
Future Significance
Enumeration type: declining sharply, declining, constant, increasing, increasing sharply
Future significance depicts the expected tendency of a knowledge category to change in significance for the company.
Structural Change Speed
Percentage: 0..100
The structural change speed is a measure of how quickly the methods applied to acquire relevant knowledge must change (0%: no change, 100% maximum change speed).
These attributes are used to assess the relevant Knowledge Category with relation to your own company. They can therefore be used as a basis for identifying important or urgent measures to improve your own knowledge management. It is often helpful to display such values graphically. Copying and pasting the values from the Attribute window into a table calculation program that can create the desired models is a simple way to do so. For example, a bar graph comparing the current and desired Degree of Coverage for the Knowledge Categories under consideration could be generated.
7.2.2
Documented Knowledge
Unlike the Knowledge Category object type, which can include implicit and explicit knowledge, the Documented Knowledge object type concerns itself exclusively with Knowledge Categories that are explicitly documented, or are at least capable of being documented in principle. An example of this type of
ARIS Methods
7-5
knowledge is knowledge on using software that is documented in a manual. When categorizing knowledge into knowledge categories, differentiating between general knowledge categories and documented knowledge helps to identify the possibilities and limitations of information system support for knowledge processing, as only documented knowledge can be electronically stored, transmitted, and processed. The Documented Knowledge object type is indicated by a rectangular thought bubble. It contains the same specific attribute types as the Knowledge Category object type (see page 7-2).
ARIS Methods
7-6
7.3
7.3.1
Model Types for Modeling Knowledge Processing

Knowledge Structure Diagram
Using a knowledge structure diagram, knowledge categories can be placed into subgroups based on their content. An example of this is shown in Figure 7.3.1-1. A knowledge category can include other knowledge categories as well as documented knowledge. Documented knowledge can also be divided into several documented knowledge subcategories. However, it cannot include any general knowledge categories.
Figure 7.3.1-1: Knowledge Structure Diagram
ARIS Methods
7-7
For documented knowledge, a knowledge structure diagram can show the information media on which the knowledge is documented, or which information objects in a data model or classes of an object-oriented system are used to document this knowledge. Finally, the types or classes of application systems that are used to manage the knowledge can also be modeled.
7.3.2
Knowledge Map
A knowledge map depicts the distribution of various knowledge categories within an organization. Various object types in the organizational view (e.g., Organizational Unit, Position, Person, Location, Group) can be connected to knowledge categories using disposes of connections. In addition to the fact that a particular person or organizational unit has knowledge in a particular category, the degree of coverage can also be specified. The disposes of connection contains the Degree of Coverage attribute, which can express in percentage form the degree of knowledge coverage in the selected category for the relevant organizational unit. A value of 100% stands for maximum coverage, and a value of 0% means that absolutely no knowledge in the category mentioned exists. This is equivalent to a completely nonexistent connection. In addition to this quantitative measure, it is possible to view a qualitative evaluation in the form of a graph. This is the purpose of the Coverage Quality connection attribute, which can assume the values of low, medium, high, and maximum. This information can be viewed using graphic symbols on the connections as shown in Figure 7.3.2-1. There is no direct connection between the values for the Degree of Coverage and Coverage Quality attributes. If both attributes are used, it is suggested that the qualification low be used for a degree of coverage of up to 25%, medium for 25-50%, high for 50-75%, and maximum for 75-100%.
ARIS Methods
7-8
Figure 7.3.2-1: Knowledge mapRelating to Organizational Unit
The Knowledge map in example Figure 7.3.2-1 has a structure that is organizational unit-oriented, i.e., all relevant Knowledge categories are given for each organizational unit. Of course, it is also possible to select the Knowledge Categories as the central view and model the relevant organizational units around them. The navigation options in ARIS (Relationships tab in the Properties Object dialog box) make it easy to find the other connections for an organizational unit or Knowledge Category in both cases. A matrix representation is often used for knowledge maps. This can be achieved by arranging several occurrences of the same knowledge category in column format as shown in Figure 7.3.2-2. In this example, only the names of the Knowledge Categories displayed at the top are given, much like in the header of a table. For the other occurrences, the name above the attribute placement is omitted. This figure also shows an alternative visual representation for differing degrees of coverage: the Knowledge Categories are scaled in different sizes.
ARIS Methods
7-9
Figure 7.3.2-2: Knowledge MapMatrix Representation
When allocating knowledge categories to specific employees, be aware that the collection, documentation, and particularly the electronic processing of such employee-related data are subject to many restrictions due to laws and company agreements. These must be complied with when creating, using, or distributing this type of knowledge map.
ARIS Methods
7-10
7.3.3
Representation of Knowledge Processing in Business Processes
The utilization and creation of knowledge in the company's business processes is modeled with the model types for the representation of business processes (eEPC, eEPC (material flow), Office Process, Industrial Process, PCD, PCD (material flow)). The Knowledge Category and Documented Knowledge object types are now available in these model types. It is now possible to specify which kind of knowledge (general or documented) is necessary to perform a function and note which knowledge is created and/or documented when the function is actually performed. This type of representation allows business processes to be studied in terms of the knowledge processing involved. For example, gaps in necessary knowledge can be discovered. Besides, the qualification profile needed to perform a function can be determined.
ARIS Methods
7-11
Figure 7.3.3-1: Knowledge Processing in an eEPC
ARIS Methods
Examples of Applications
8-1
8 Examples of Applications
The purpose of this chapter is to assist with finding the right ARIS support for specific business problems. The chapter has thus been divided into application scenarios (sub-chapters). For each application scenario a short description is given of the meaning of each scenario or which activities are normally performed in the respective scenario. Typical tasks involved in the scenario are then described. For each task it is shown how ARIS can be used to solve the task. The following table gives an overview of the application examples described along with the model types used:
Scenario General company documentation (see page 8-5)
Scenario Tasks Documentation of the company's objectives Documentation of the company's value added Documentation of the organizational structure Documentation of the company functions Process documentation Process warehousing
Model Types Objective diagram Value added chain diagram Organizational chart Function tree Office Process Industrial Process eEPC PCD
ARIS Methods
8-2
Scenario Database management/Data Warehousing (see page 86)
Scenario Tasks Data structuring/database design Database administration/access management
Model Types ERM SAP SERM SeDaM IEF data model Relations diagram Table diagram Class diagram Class description diagram
Groupware (see page 8-7) PC hardware and (see page 8-7)
Integrating Lotus Notes and ARIS
Identification of the IT
Network topology Network diagram
network management infrastructure requirements Documentation of the IT infrastructure Access privileges Activity-based cost calculation (see page 8-8) Description of the process and organizational structures Cost Center Analysis Process calculation
eEPC PCD Organizational chart CD diagram Cost category diagram
ARIS Methods
8-3
Scenario Quality management (see page 8-9)
Scenario Tasks Structure of QM documentation Certification procedure Certification documents
Model Types Product tree Product Selection Matrix eEPC PCD Office Process diagram Industrial Process diagram Value added chain diagram Structuring model Organizational chart
Reorganization measures (see page 8-10)
Project documentation Reorganization implementation
Value added chain diagram eEPC Organizational chart Product model Performance model Objective diagram PCD
Introducing SAP R/3 (see page 8-11)
Phase analysis, specification (project preparation) Phase design (business blueprint); 3 application examples available
eEPC Organizational chart
ARIS Methods
8-4
Scenario
Scenario Tasks
Model Types Value added chain diagram Organizational chart eEPC Use case diagram Application system diagram Application system type diagram Program flowchart Screen diagram
Software development Project documentation and introduction (see page 8-13) Determination of application systems and modules Description of the IT processes Development of the system interface
Knowledge management (see page 8-14)
Knowledge map, or Yellow Page Knowledge categorization Knowledge processing in business processes
Knowledge map Knowledge structure diagram eEPC PCD Office Process Industrial Process Function allocation diagram
Workflow manage-
Process customizing of workflow
Rights diagram eEPC Function allocation diagram Application system diagram Application system type diagram
ment (see page 8-15) management systems
ARIS Methods
8-5
8.1
General Company Documentation
Company characteristics such as processes, structures and data can be documented in suitable form for training, presentation and evaluation purposes of any kind. The most important tasks of company documentation are described briefly below. Task: Documentation of company objectives ARIS support: Objective diagrams can be used for the hierarchical alignment of company objectives and the associated critical factors. Task: Documentation of the company added value The identification of the functions involved in value-adding activities of a company is the basis for many company decisions. ARIS support: The company functions involved in adding value can be displayed using the value-added chain diagram. This model demonstrates the sequential order of subsequent consecutive functions as well as superior and subordinate functions. Task: Documentation of the organizational structure ARIS support: units. Task: Documentation of company functions ARIS support: A function tree can display individual functions of a company in an overview. The functions are divided into either object-oriented, process-oriented and execution-oriented functions. Task: Process documentation ARIS support: Depending on the industry sector or process type, business processes can be recorded in Office Process or Industrial Process diagrams without having to resort to methods knowledge. If methods knowledge exists and for the further utilization of the process models in SAP applications, simulation, workflow, etc., we recommend modeling with an eEPC or, for weak point analysis, with a process chain diagram (PCD). The structure of an enterprise can be documented with
organizational charts which show the hierarchy and relationships of organizational
ARIS Methods
8-6
Task: Process warehousing Process warehousing is the systematic recording, storage and maintenance of business process knowledge in a repository. ARIS support: For the modeling of process knowledge in decentralized units, we recommend the use of Office and Industrial Process diagrams, since the operational employees generally do not usually have methods expertise. On the other hand, for maintenance and administration in the central model repository, we recommend converting the models into eEPCs, enhanced by documents, images and videos, so that they can be used in more demanding evaluations, such as simulation or activity-based cost calculation.
8.2
Database Management/Data Warehousing
By storing company data in databases, redundant data storage is reduced and it becomes possible to gain program-independent access to company-wide data. Data warehousing ensures the quality, integrity and consistency of the underlying data. The term "data warehouse" generally designates a database that is isolated from the operational IT systems and that serves as a company-wide database for all forms of management support systems. It is characterized by a strict separation of operational and decision-supporting data and systems. The focus of the data warehouse concept lies in the efficient provision and processing of large amounts of data to carry out evaluations and analyses in decision-relevant processes. Task: Data structuring/database design The structure of databases is determined by the underlying data models. ARIS support: The most widely used method of data modeling is the entity relationship model (ERM), which serves as the basis for the implementation of a relational database. Product and/or company-specific modifications of the ERM is the SAP-ERM for information modeling by SAP AG, the SeDaM (semantic data model) as a notation by BASF AG, and the IEF data model (Information Engineering Facility) for data modeling of the CASE Tool by Texas Instruments Inc. For a more in-depth description of logical data structures the relations diagram can be used, which is added to the data structures designed in the ERM. The tables and fields of a database system are described by the table diagram.
ARIS Methods
8-7
Object-oriented database systems can be designed using the Unified Modeling Language (UML) or the Object Modeling Technique (OMT). In UML, the class diagram can be used to show the static data relationships, while the class description diagram enables an additional representation of attributes, objects, interfaces, etc. TASK: Database administration/access administration Assignment of users and system administrators to the database systems. ARIS support: The access diagram can be used in conjunction with relations and system components to determine the access privileges that organizational units, positions and people have for the database system.
8.3
Groupware
Groupware is a technology that supports working in a team. An important characteristic of groupware is that a group of users completes jobs jointly and uses software to work on them in an organized way. A distinction is made between workgroup computing (coordination of workgroups), collective writing (compiling of joint documents) and group decision support systems (decision-making support for groups). Task: Integrating Lotus Notesand ARIS ARIS and Lotus Notes are suited to different types of documentation. While the advantage of ARIS lies in its ability to display the connections between different aspects such as processes or organizational structure in a simple and convenient way using graphics, and to provide comprehensive analysis procedures, Lotus Notes allows the user to efficiently manage complex text documents such as work instructions and forms. It makes sense to use and integrate both forms of documentation. ARIS support: Using the ARIS Lotus Notes Connectivity system add-on module, it is possible to refer to a related document, a view, or a database in Lotus Notes using a link from any object, model, group or database in ARIS. For certification and training purposes it is useful to maintain process descriptions in ARIS and work instructions and forms in Lotus Notes.
ARIS Methods
8-8
For managing ARIS models, the cataloging and retrieval functionality of Lotus Notes can be used.
8.4
PC Hardware and Network Management
Network management means the control, monitoring and coordination of all (distributed) resources (data networks, processors, data and applications) that enable communication in a computer network. Task: Identification of IT infrastructure requirements Based on an existing organizational structure it is to be decided which communications and information landscapes can support it efficiently. ARIS support: The requirements of the organizational structure of information systems can be mapped using the Network topology model type. The representation of application systems, network types and hardware components does not consist of individually identifiable specimens (e.g. PC with inventory number 3423), but rather it is a typification according to like technology. Task: Documentation of IT infrastructure The task is to map an existing or planned IT infrastructure with specific hardware components, networks and application systems. ARIS support: An IT infrastructure can be portrayed using a network diagram as a concrete implementation of a network topology. Task: Access privileges The task is to demonstrate which applications and users have access to which data and in which way. ARIS support: The access diagram can be used to describe which applications or application modules have what kind of access (write/read/modify) to database stocks and information carriers, and if the data acts as input or output. Moreover, it can map which user privileges and views specific users or user groups have for the applications or application modules.
ARIS Methods
8-9
8.5
Activity-Based Cost Calculation
By recording and allocating the costs arising from the commercial provision of products and services, cost accounting provides a scheduling basis and a control instrument. Due to changes in the cost structures, in particular to the increase in overhead costs, traditional cost accounting methods are being replaced by activitybased cost calculation. Activity-Based Cost calculation determines the costs of processes across cost centers. Budgeting, cost transparency in the indirect performance areas, pricing and support in make-or-buy decisions are the main advantages of the Activity-Based Cost calculation. Parts of the ARIS support described in the following are only possible with the ARIS ABC system add-on. Task: Description of process and organizational structures Determine the processes to which the Activity-Cased Cost calculation is to be applied, as well as the description of the cost centers. ARIS support: Processes are mapped with standard model types, e.g. eEPC and PCD. For activity-based cost calculation, the maintenance of time attributes as well as the assignment of organizational units are important. The company organization is described in an organizational chart, in which the organizational units correspond to cost centers (with the cost rate and performance attributes). Task: Cost center analysis ARIS support: For cost center utilization, cost drivers which are defined in a CD diagram can be used. The calculation can be performed for any number of cost categories. The cost category structure will be depicted in a cost category diagram. In addition, it is necessary to create a cost category table and a functions table, in which the objects to be analyzed are described. Task: Process calculation ARIS support: A complete cost center analysis with a determination of the process cost rates is a prerequisite. No additional models have to be maintained in order to perform a process calculation. The results will be shown in a calculation table.
ARIS Methods
8-10
8.6
Quality Management
The term "Quality Management" (QM) applies to all activities that define a company's quality policy, objectives and responsibilities. The means for putting these activities into effect include quality planning, quality control (process management), quality assurance and quality improvement (quality enhancement). Task: Development of QM documentation In order to ensure the quality of products and processes within a company, appropriate documentation must be prepared that enables the company to evaluate, compare and thus improve products and processes. ARIS support: Product trees are well-suited to providing product documentation that allows efficient classification of products. This type of representation is used increasingly in the service industry and in particular in public administration. Furthermore, the product selection matrix allows a company to represent which of its functions are required for the creation of which products and which organizational units are responsible for the production. Another main objective of QM documentation is to document processes that can be recorded by means of eEPCs, PCDs or office and industrial processes, evaluated in reports, and refer to documents and applications within the company. Task: Certification procedures The use of procedure models in support of project management in the certification process according to nationally and internationally recognized standards such as ISO or VDA. ARIS support: A procedure model for certification (for example the ARIS procedure model) can be represented using a value-added chain diagram. The individual steps can be described in more detail by assigning additional process models. Task: Certification documents Creation of the quality documents required for certification. ARIS support: The structuring model subdivides individual certification standards into their components. The individual items of a structuring model can be assigned to company models for quality control. These models can be, for example, process models in the form of eEPCs, Office or Industrial processes, organizational charts or
ARIS Methods
8-11
even value-added chain diagrams. Using ARIS Toolset, reports can be generated that are recognized as a QM manual for certification purposes.
8.7
Reorganization Measures
Reorganization measures for the reduction of cost or time, improvement of the quality of the results or improvement of the quality of work involve the modification of company processes (process redesign) or their complete redevelopment (process re-engineering). Task: Project documentation Documentation of the planning, procedure and results of the reorganization measures. ARIS support: The main project phases of the reorganization process can be described as a procedure model through a value-added chain diagram. The individual project activities of the reorganization project can be documented in their processes by means of eEPCs. The organization of the people and units involved in the project can be displayed in organizational charts. Task: Carrying out the reorganization A reorganization project involves the preparation of the project and strategic planning, which are followed by an analysis of the actual situation, the development of the target concept and finally the implementation of the solutions. ARIS support: Product and performance models as well as objective diagrams are used to document strategic framework conditions, so that the company's essential business segments can be recorded along with their products, services and customer groups, and the critical success factors and the target hierarchy can be mapped. During the analysis of the actual situation, a framework containing the main business processes is developed first using value-added chain diagrams. Based on interviews with employees, these business processes are then recorded in detail in the form of an eEPC or a process chain diagram (PCD). The PCD is particularly suitable for identifying weak points caused by media breaks and changing process responsibilities.
ARIS Methods
8-12
Following a weak point analysis that takes into account throughput times, process costs, organizational breaks , systems and media breaks, data redundancies etc., alternative target processes are then defined. These processes are modeled using eEPCs in the same way actuals were recorded initially. In support of the implementation, system, organizational and data components are described more specifically at the end of target plan. For example, the term "word processing" as an application system construct can now be specified as MS Word. Note: The weak point analysis phase can be supported by evaluations using the ARIS Simulation and ARIS ABC components.
8.8
SAP R/3 Introduction
The support capabilities of ARIS in the introduction of standard R/3 software by SAP AG are geared to the lifecycle of the ASAP implementation approach. In addition to ASAP, however, other approaches geared more towards business process optimization (in the broadest sense) are also supported. Parts of the ARIS support described below are only possible with the ARIS for R/3 system add-on . Task: Analysis phase, specification phase (project preparation) The task is the identification of the degree of coverage of the company-specific processes by the SAP R/3 system as well as the timely identification of possible weak points. ARIS support: If the analysis is not done directly through the SAP R/3 reference model, the "optimum business processes" to be supported can be modeled with ARIS (see general company documentation). Then, an initial estimate of the degree of coverage can be obtained through reports, by mapping the company model with the SAP R/3 reference model. Task: Phase design (business blueprint) Process and/or function deficits were identified in the SAP R/3 reference model. ARIS support: Based on the existing components from the R/3 reference model, new process and scenario variants can be developed in ARIS. In addition, new functions, events and rules (i.e. through the development of new SAP-ABAP functions, if applicable) can be added to the process and scenario components.
ARIS Methods
8-13
Task: Phase design (business blueprint) Design of interfaces between SAP R/3 and non-SAP applications. ARIS support: The documentation of the attributes to be exchanged can be described in detail in process models in the ARIS repository by assigning data or objects to functions and data or object models. This information can also be output as a report and forms the basis for the development of interfaces. Task: Phase design (business blueprint) The development of the organizational design of business processes and the SAP system. ARIS support: The company's social structure and the SAP organizational structure can be described and juxtaposed using organizational charts.
8.9
Software Development and Introduction
Task: Project documentation Documentation of the planning, procedure and results of software development and implementation. ARIS support: The main project phases of the project can be described as a procedure model through a value-added chain diagram. The individual project activities during the development and introduction can be documented by means of eEPCs. The organization of the people and units involved in the project can be displayed in organizational charts. Task: Determination of application systems and modules The task is to show the structural organization of an information system based on the system requirements. ARIS support: The use-case diagram can be used to identify the application examples of the software system to be developed. Furthermore, it allows the definition of system users and their assignment to individual application examples. The use-case diagram often forms the starting point for detailed process modeling. Process models can be assigned to individual use cases. The application system type diagram can be used to describe the hierarchical structure of application systems using module types and IT function types.
ARIS Methods
8-14
The application system diagram can be used for specifically describing the individual types using specific occurrences. Task: Description of the IT processes The task is to describe the chronological-logical process within modules or across modules. ARIS support: The program structure chart, which corresponds to a program flowchart, can be used to model IT processes. Task: Development of the system interface The task is to develop and document a user interface. ARIS support: The geographical and functional organization of a screen (window) can be described with a screen diagram. Just as in the transition from ERM to a relations model, the program code can be derived from the screen diagram.
8.10 Knowledge Management

The starting point for designing comprehensive knowledge management is the idea that de facto knowledge has become or is becoming the dominant production factor in companies. This results in the need to understand knowledge as a controllable element just like the classic operational production factors. In consequence, the focus of knowledge management is the acquisition,
representation and distribution of knowledge. Knowledge management is the sum of all methods, measures and systems used by an organization in order to develop knowledge and to make it transparent and available independent of time, people and location. The objective of knowledge management is to increase knowledge and to apply the knowledge base in the company in an optimal way. Task: Knowledge map or yellow page The objective is to map what knowledge is available in the company and where.
ARIS Methods
8-15
ARIS support: The Knowledge map model type can be used to display the organizational distribution of different knowledge categories. It can show which organizational unit, position or employee possesses expertise in certain knowledge categories, and what their level of competence is. Task: Categorization of knowledge The task is to classify the intellectual capital of an organization analytically, i.e. to describe the different types and groups of knowledge in order to design a knowledge storage structure for example. ARIS support: The knowledge structure diagram can be used to show how the knowledge base of an organization is divided into different knowledge categories and how these are further subdivided into knowledge categories and documented knowledge. For documented knowledge it is also possible to depict the information carriers where this knowledge is stored. Task: Processing knowledge in business processes The task is to show where in the business processes knowledge is generated, modified and required in order to ensure the most efficient use of the knowledge resource. ARIS support: Within the eEPC, Process chain diagram, Office Process, Industrial Process and Function allocation diagram model types, the Knowledge category and Documented knowledge objects can be used. The structure and organizational distribution of the knowledge can be described separately using the knowledge structure diagram and the knowledge map.
8.11 Workflow Management

A workflow can be interpreted as a business process in the broadest sense. The term workflow means processes based on the division of labor that are initiated in order to carry out business transactions. This can include very simple business processes as well as complex, cross-organizational processes. The focus of the analysis is the dynamic flow of the processes from start to finish. Workflow management is the sum of methods, measures and systems used in order to develop, control and optimize workflows.
ARIS Methods
8-16
A workflow management system is an actively functioning, flexible software that works under an organizational framework of rules, and controls a process that spans several workstations and integrates existing basic technical components. With process control systems it is possible to support complex groups of tasks involving a large number of employees and positions. Task: Process customizing of workflow management systems ARIS supports in particular the transfer of general business process models to workflow models, with which various workflow management systems can be (semi-) automatically configured. ARIS support: The privileges diagram is used to describe which workflows (processes) exist and which people or people groups may initiate them. As with process modeling, the eEPC is used to depict the activity flow. Strict adherence to the methods is very important here! A function allocation diagram has to be created for each function, where a user as well as the input and output data are allocated to the function - if this has not already been shown in the eEPC. In order for the applications belonging to the data to run automatically during runtime, an allocation of files to applications has to be modeled in an application system diagram or an application system type diagram.
ARIS Methods
Balanced Scorecard Method
9-1
9 Balanced Scorecard Method

9.1 Introduction
If companies want to survive in the turbulent business environment and global competition of today's markets, they need the best possible operating procedures. But it is equally important to be able to react to new developments in the business environment, quickly and in line with the company's strategic goals. This requires efficient management processes which enable the realization of company strategies and strategic objectives and the implementation thereof in day-to-day business by means of operational initiatives. Many traditional management methods do not connect the formulation of business strategies with the strategy-oriented steps which have to be taken to implement them, nor do they make the link to the need for feed-back on achieving strategic objectives. In addition, many companies are still run purely on the basis of financial key performance indicators which are of limited use since they relate mainly to past performance and cannot therefore provide much information relevant to future management. It is only when we look at the reasons for financial success (customers, processes, innovations, etc.) that we can identify at an early stage anything that will prevent us from reaching strategic goals. The Balanced Scorecard approach offers a methodology with a structure which is easy to understand and implement, and helps to avoid these weaknesses.
9.2
9.2.1
The Balanced Scorecard Concept

Key Elements of the BSC Approach
The Balanced Scorecard approach is a strategic management system first proposed by Robert Kaplan and David Norton in 1992 ("The Balanced Scorecard Measures that drive Performance", Harvard Business Review, January/February 1992). It was developed from the results of research on the subject of "Approaches to Performance Measurement". This research found that Performance Measurement Systems geared exclusively to financial key performance indicators are likely to
ARIS Methods
9-2
hinder value-producing activities in many companies. Building on this finding, Kaplan and Norton set out to collaborate with innovative businesses to create a system of key performance indicators that would make it possible to measure the best way in which the aspirations and strategies of the companies could be realized. With the Balanced Scorecard method, key performance indicators taken from different points of view are allocated to the company (so-called perspectives). These include internal (e.g. learning and development perspective, process perspective) and external performance perspectives (e.g. customer perspective, financial and economic perspective). This arrangement of the key performance indicators achieves a certain balance between short-term and long-term goals, financial and non-financial key performance indicators, leading and lagging indicators, and internal and external points of view. The introduction of specific key performance indicators for different sectors adds a further benchmarking component to the concept. The purely Performance Measurement approach has evolved into a comprehensive management system for goal-oriented company management, starting from the company vision and going through individual competitive strategies right down to the formulation and control of initiatives using balanced key performance indicators. The Balanced Scorecard approach is thus more than just a system of performance measurement key performance indicators. It helps businesses in communicating and implementing company strategy, and in the strategic learning process resulting therefrom (double loop learning).
ARIS Methods
9-3
9.2.2
Strategic Management Process and Balanced Scorecard
Figure 9.2.2-1: The BSC as a Structure for Strategic Management
The strategic management process in the context of the Balanced Scorecard approach comprises two stages: 1. In the first stage the company's strategy must be established through a strategic analysis. The strategic analysis records all data relating to competition. The aim of this analysis is to identify and assess trends, opportunities and risks in the developing business environment, and to pin-point basic strengths within the company. At the end of this stage the company's individual business strategy is determined. 2. The implementation of the business strategy takes place in the second stage. The BSC method can help in this stage. The business strategy may be refined with partial strategies (e.g. specific business segment strategies). This then
ARIS Methods
9-4
leads to further strategic goals. These are then concretized on the basis of targets for particular amounts. A program of action in the form of instructions on how to proceed determines how these targets are to be achieved. In the business planning phase the program of action is "broken down" into the separate areas or departments of the business. Budgeting can be used to put actions into more concrete terms. Using individual strategy related scorecards the achievement of objectives can be measured by the key performance indicators generated. A review process takes place on the basis of the defined scorecards, in which further initiatives are defined or the strategy is re-worked in the light of possible deviations.
9.2.2.1
Formulation and Translation of Vision and Strategy
The strategy of a business derives from its vision. The vision represents a superior motif for the business concerned; as a comprehensive but very bold statement it is vague, yet serves as the prime principle of action and as such expresses a kind of short version of the company philosophy. Individual strategies are determined for separate strategic business units. These strategies must be geared to the goals of the company. It is therefore very important that before introducing a BSC, senior management of a business hold a workshop to establish the vision and the strategies that flow from it for the strategic business units. In most cases this will involve setting a financial target (financial perspective). The focus may vary: Possible goals are particular values for return on capital, ROI, shareholder value, sales revenue or cash flow. The financial objectives have to be achieved through a specific approach to the market concerned (client perspective). Therefore, after defining the objectives, the appropriate market and client segments are selected. This client perspective also involves the definition of strategic objectives and the identification of relevant key performance indicators. They may, for example, relate to market share or growth rates in particular client segments. Appropriate company resources are required to implement specific market-oriented strategies. In establishing a Balanced Scorecard resources fall into two categories:
ARIS Methods
9-5
1. After establishing financial and client objectives, the important business processes (process perspectives) are looked at, objectives determined and initiatives and key performance indicators generated. Central to this are usually process times and costs. 2. As part of the learning and development perspective, strategic objectives for personnel development, information technology and innovations are derived from the strategic objectives of the financial, client and process perspectives. In this definition of a Balanced Scorecard all the defined strategic objectives are mutually interactive, which is described as the cause-and-effect chain. It is important for this first step that at management level there should be a general consensus on the vision and the strategies and strategic objectives deriving from it.
9.2.2.1.1
The Standard Perspectives of a Balanced Scorecard
Kaplan and Norton propose four standard perspectives for the composition of a Balanced Scorecard: 1. Financial perspective Shareholders' expectations: "What effect on finances does the strategy have?" 2. Customer perspective Customers' expectations: "How do we position ourselves in the target markets?" 3. Process perspective - Requirements on processes: "Which processes are strategically significant?" 4. Learning perspective - Requirements for organizational learning and innovations: "How can we develop into a learning organization?" "How can we promote growth?"
ARIS Methods
9-6
Figure 9.2.2-2: The Perspectives of BSC
The standard perspectives have an implicit logic which helps in implementing strategy and formulating specific cause-and-effect relationships. However, it is also possible in principle to define further perspectives applicable to a business (e.g. environment perspective) which are relevant to its strategy and have objectives and key performance indicators linking with its other perspectives.
9.2.2.1.2
The Cause-and-Effect Chain
The cause-and-effect chain defines the cause-and-effect relations between the different individual objectives of a strategy, namely via the defined perspectives of the key performance indicators. That is, it describes how the objectives of the perspectives can be achieved. In doing this the perspectives themselves form, as it were, the structural conditions for the cause-and-effect chain ("force field of the
ARIS Methods
9-7
business"). We assume that improvements in the environment of the learning and development perspective will have a direct and positive effect on the objectives and key performance indicators of the internal process perspectives. Furthermore, developments in the process perspective also have a positive effect on the objectives and key performance indicators of the client perspective, which in turn leads to an improvement in the financial objectives. In developing a Balanced Scorecard system across the company objectives and key performance indicators are defined for each strategy, and the relationships between them are represented within as well as across the perspectives. We start from the objectives and key performance indicators of the financial perspective and look for corresponding "positive agents" (performance drivers) in the client perspective. These are then broken down via the internal process perspective, down to the learning and development perspective. This procedure allows strategies of a business or a division to be split up into partial objectives and key performance indicators, and corresponding operational initiatives to be derived from them. By establishing a cause-and-effect chain and defining the key performance indicators a balance is implicitly created between leading and lagging indicators.
9.2.2.1.3
Defining Leading and Lagging Indicators
The establishment of cause-and-effect chains also produces a temporal connection between the individual objectives and key performance indicators. Thus, as a rule, performance drivers belong to the learning and development perspective and the process perspective, and are so-called leading indicators. These performance drivers come before the effects of the client perspective and the financial perspective. Most of the key performance indicators in the client and financial perspectives are results indicators which measure the success of the business; as so-called lagging indicators they look back to the past. Both leading and lagging indicators should be defined in every Balanced Scorecard perspective so that the link between the initiatives and the attainment of the objectives can be displayed. Using leading indicators divergences from the objectives can be detected at an early stage.
ARIS Methods
9-8
9.2.2.2
Communication and Derivation of Further Scorecards
The effectiveness of a business strategy and its application using the Balanced Scorecard concept is partially dependent on the company scorecard being familiar to and accepted by throughout the company. For this reason it is vital that the business strategies and the company Scorecard are promoted at all hierarchy levels of the business through a comprehensive publicity campaign. From the higher-level business strategy (Company Scorecard) target guidelines are distilled in a top-down approach for implementation at the subordinate hierarchical levels of the company, and higher-level strategic objectives are adapted to specific departmental goals. Key performance indicators measuring the degree of goal accomplishment are generated for these too. Various initiatives are required in the different areas of a business in order to reach the objectives, and these initiatives are recorded in the Scorecards of the underlying hierarchy levels. All target guidelines must be based on long-term strategic considerations, and not with a view to short-term results which are not consistent with the overall strategy. An example of a short-term result might be a reduction in costs based on a short-term increase in the level of production.
9.2.2.3
Planning and Guidelines
The BSC can be used to link the process of strategy implementation to the various hierarchy levels of the company using the budgeting process. The purpose of linking the two is to gear all resources to the business strategy. There are four steps in integrating the BSC into the long-term strategic planning and budgeting process. 1. Challenging targets are set, communicated to all employees, and accepted by them. The key performance indicators relevant to results in the client and financial perspectives are identified by the cause-and-effect relationships. 2. The strategic initiatives must be introduced for the specific key performance indicators with the greatest discrepancy between their current value and the target values. With this procedure capital investments and action programs are concentrated together in an ongoing and rigorous manner on strategically significant targets.
ARIS Methods
9-9
3. Critical initiatives across the business are identified, and resulting synergy effects can be achieved with the strategic objectives. 4. The planned values for the result indicators are linked to the business plan, being tied to budget projections of varying duration (5, 3 and 1 year plan).
9.2.2.4
Strategic Learning and Feedback
The Balanced Scorecard concept contributes to strategic learning that takes place in the business and facilitates feedback in the achievement of strategy. Strategic learning is aimed at every single employee and at the entire business as a learning organization. Employees must know the strategy and make sure individually that their actions are in line with it. By means of a defined feedback process performance data are gathered to assess whether the strategy has been achieved. In this way propositions are checked by testing hypotheses through previously established cause-and-effect relations of strategic objectives. The net effect of this is the phenomenon known as double loop learning, in which strategic targets are subjected to critical review in a bottom-up process, after which new cause-and-effect relations are generated. These then lead to a more efficient execution of strategy on a ever growing information base. Feedback is therefore extremely important as it represents the counterprocess to the top-down effect of BSCs. Feedback not only involves the reporting of key performance indicators in the form of planned progress figures but also suggestions for further initiatives and new interrelations. Thus it reveals possible inconsistencies in the execution of strategy.
9.2.3
Advantages and Uses of the Balanced Scorecard
The advantage of the Balanced Scorecard method lies in its logical, strategyoriented company management, which comprises the lowest levels of the business and also derives operational initiatives in line with strategy at these levels. All the resources and all the employees of the business are geared to the strategy of the business. The strategy of the business is rigorously communicated and checked through Balanced Scorecards. The Balanced Scorecard method overcomes the disadvantages of traditional key performance indicator systems in business management:
ARIS Methods
9-10
There is no limit on financial key performance indicators Not purely looking to the past Qualitative data also taken into account Reduction of complexity and seeking consensus Strategic objectives as starting point of the Balanced Scorecard approach Orientation to management bottlenecks, not to existing data Speeding up necessary changes The Balanced Scorecard method is eminently suited to strategy-oriented company management as it overcomes the following barriers: Concretizing barrier: In traditional management initiatives vision and strategy are theoretical formulations, and the distillation of specific (operational) modes of action is not consistently pursued. Vision barrier: The strategy is often not understood by those employees who have to implement it. Commitment barrier: Strategies are not linked to specific departmental or individual targets. Implementation barrier: Reporting is geared to operational monetary objectives, rather than strategic objectives. Operational barrier: The budgeting process planning process. is separate from the strategic
ARIS Methods
9-11
9.3
9.3.1
Development of a Balanced Scorecard with ARIS BSC

Terms and Abbreviations
Vision: A vision indicates the future strategic thrust and task of a business and is realized by various strategies. Strategy: Strategies are developed with the vision as their starting-point. The strategies can be split up into specific partial strategies. Strategic objective: Each strategy consists of a certain number of strategic objectives. The strategic objectives are generally established by the management responsible in workshops. The objectives are connected by a cause-and-effect relationship and a temporal logic. Critical factor: A critical factor is a factor influencing the business of the company and critical to its success, which may interact with other critical factors and move them in a specific direction with a particular degree of effectiveness. View/Perspective: A perspective is putting a certain view of the company in more concrete terms. In principle the selection of perspectives should include the following viewpoints of a business: person-oriented view, internal view, processoriented view and external view. Key performance indicator: Each strategic objective or critical factor is allocated key performance indicators to measure performance and the achievement of objectives. Actual value: The current value of a key performance indicator, a strategic objective or a critical factor. From the actual value we can, by comparing the planned and the actual value, derive the current degree of goal accomplishment. Plan value: The planned value of a key performance indicator, strategic objective or critical factor set as a target for a particular period. In the case of strategic objectives this is usually a percentage derived from the weighted achievement of objectives of individual key performance indicators. The plan value can be broken down into separate periods and can then take into account periodic fluctuations. The plan value represents a degree of goal accomplishment of 100 %.
ARIS Methods
9-12
Target value: The value planned as a target for a period in the future. As a rule, this becomes the planned value when the target period is reached. Minimal value: The smallest possible value that an objective, a crucial critical factor or a key performance indicator can achieve. In ARIS the minimal value is set at 0 by default. But it can be altered. Maximum value: The highest value (upper threshold) a strategic objective, a critical factor or a key performance indicator can reach. In ARIS it is generally used to standardize the representation of a number of key performance indicators so that they can be compared. Warning limit: The warning limit corresponds to the planned value, i.e., the planned value corresponds to the limit at which the value of a key performance indicator, strategic objective or critical factor falls short of an expected target. Tolerance range: The tolerance range is the negative divergence from the planned value for a strategic objective, key performance indicator or critical factor that can still be accepted. Alarm limit: The alarm limit denotes the planned value minus the tolerance range. All values of a strategic objective, key performance indicator or critical factor that fall below the alarm limit are no longer acceptable. Measure: A measure works on a objective or on a number of strategic objectives. As a rule measures have someone responsible for them, a starting and an end point, resources, etc. Indicator type: A key performance indicator may be of the leading indicator or lagging indicator type. A leading indicator measures a performance driver and is an indicator pointing to the future. A lagging indicator measures a result (result indicator) and is retrospective. Financial targets are generally lagging indicators, while the targets of process, learning and development perspectives are increasingly leading indicators. Late indicators should also be included within the perspectives in order to represent the cause-and-effect relationship between the key performance indicators. Data source: Each key performance indicator has a data source from which it can be extracted into the Balanced Scorecard system.
ARIS Methods
9-13
9.3.2 9.3.2.1
Construction of the Balanced Scorecards with ARIS BSC Establishing Perspectives
At the start of a Balanced Scorecard project the perspectives should be established within the strategic plan. These perspectives should be used for all the Scorecards of a business. The perspective object type is available to do this. Perspectives can be created either as objects in ARIS Explorer or modeled in the BSC Cause-and-effect diagram. Perspectives are connected together with the help of the is influenced by link. It is not necessary to establish a methodical sequence. However, if the perspectives structure (i.e. the sequence of individual perspectives) is logically established, the automatic generation of a model is considerably simplified and the logical structure of the cause-and-effect chain is made clear.
9.3.2.2
Establishing the Structure of the Balanced Scorecard System
The following models provide the framework for the establishment of the Balanced Scorecard system: Organizational chart A Balanced Scorecard system can be structured according to the organizational structure of a company. To do this any number of BSC Cause-and-effect diagrams can be assigned to the objects of the organizational chart (e.g. for forming variants, managing histories, etc.). This assignment allocates the objectives required for the implementation of strategy to the corresponding organizational units. By means of the organizational chart the Balanced Scorecard system of a business can thus be broken down from the highest level of the business to the level of single departments or employees. Structuring model Should a business wish to structure its Balanced Scorecard system based on, say, strategic business areas rather than the organizational chart, the structuring model is available as a starting model for the balanced scorecard structure. In
ARIS Methods
9-14
this case any number of BSC Cause-and-effect diagrams can be assigned to a structuring object. Value-added chain diagram or function tree As the Balanced Scorecard is understood as being an instrument for Performance Management and Performance Measurement of companies, the Balanced Scorecard system can also be constructed in ARIS with an eye to value-added criteria. The value-added chain diagram or the function tree can be used for this purpose.
9.3.2.3
Establishing Cause-and-Effect Relationships
The BSC Cause-and-effect diagrams are assigned to the organizational chart objects, the functions or structuring items in the structuring model which determine the company wide structure of the balanced scorecard. The BSC Cause-and-effect diagram defines the strategic objectives and critical factors that need to be established to implement the strategy and displays their mutual interaction using the various perspectives of the Balanced Scorecard. To do this, the individual perspectives used in all the cause-and-effect chains of the business are first of all created as objects in ARIS. The BSC Cause-and-effect diagram is a lane model which allows the perspective object types to be stored in the relevant perspectives column and the strategy object types in the strategy row. The objective, critical factor and key performance indicator object types can be modeled in the cause-and-effect columns. The strength of the effect of the strategic objectives and their critical factors are described in the cause-and-effect column. The greater the strength, the thicker the arrow that represents it. Further critical factors for a Balanced Scorecard can be defined in the BSC Causeand-effect diagram. By using the critical factors object type, other factors and their key performance indicators that the business cannot influence directly may be included in the Balanced Scorecard, e.g. market growth. The BSC Cause-and-effect diagram can be found on the requirements definition level of the control view.
ARIS Methods
9-15
Figure 9.3.2-1: BSC Cause-and-Effect Diagram
The objective and critical factor object types in the modeling column of the BSC Cause-and-effect diagram can only be assigned to a BSC Key performance indicator allocation diagram.
ARIS Methods
9-16
The following symbols are used in the BSC Cause-and-effect diagram: Symbol Symbol name Perspective Object type Perspective
Strategy
Strategy
Strategic Objective
Objective
Critical factor
Critical factor
Key performance Key performance indicator instance indicator instance
9.3.2.4
Establishing Initiatives and Key Performance Indicators to Monitor Objectives
In accordance with the definition of strategic objectives and critical factors in the BSC Cause-and-effect diagram a BSC Key performance indicator allocation diagram is assigned to each of the individual objects. Objectives and critical factors are allocated key performance indicators to serve them as standards for the relevant objective or critical factor. These key performance indicators are subsequently identified and channeled. Should an object be allocated several key performance indicators, the weighting of each key performance indicator can be determined by a
ARIS Methods
9-17
connection of the is measured by/measures type. This shows with what weighting the key performance indicator is entered in the degree goal accomplishment of the objective or critical factor. For the analysis script of ARIS BSC to be carried out successfully, the Weighting attribute must be maintained in all connections of the is measured by/measures type. Apart from key performance indicators, objectives and critical factors in the BSC Key performance indicator allocation diagram may also be allocated objects to define the data source, e.g. entity type, file, document, database, data carrier, etc. This establishes a connection with the ARIS Toolset data warehouse method. This allows an accurate definition of which data items in the data warehouse method each Balanced Scorecard key performance indicator is connected with. Because you are able to describe the interaction of key performance indicators with influences/is influenced by, connection type, the effects leading indicators have on lagging indicators can be described in the BSC Key performance indicator allocation diagram. For this we recommend that an additional BSC Key performance indicator allocation diagram be designed, in which the emphasis is not on the allocation of individual key performance indicators to objectives or critical factors, but on the collection and definition of the key performance indicators used in the other BSC Key performance indicator allocation diagrams and on the description of their effects.
ARIS Methods
9-18
Figure 9.3.2-2: BSC Key Performance Indicator Allocation Diagram
The BSC Key performance indicator allocation diagram can be found on the requirements definition level of the control view.
ARIS Methods
9-19
The following symbols are used in the BSC Key performance indicator allocation diagram: Symbol Symbol name Strategic Objective Object type Objective
Critical factor
Critical factor
Key
performance Key
performance
indicator instance
indicator instance
Measure
Function instance
Organizational unit
Organizational unit
Organizational type
unit Organizational unit type
Position
Position
ARIS Methods
9-20
Symbol
Symbol name Person (m) Person (f)
Object type Person
Person type
Person type
Group
Group
Computer
Technical term
Technical term
Entity type
Entity type
Relationship type
Relationship type
ARIS Methods
9-21
Symbol
Symbol name ERM attribute
Object type ERM attribute
Cluster
Cluster/Data model
Knowledge category
Knowledge category
Documented knowledge
Class
Class
ARIS Methods
9-22
Symbol
Symbol name File,
Object type
Document, Information carrier
Telephone, Internet, File folder, Book, EMail, CD-ROM, Card index, Letter, Hard disk, Diskette,
Magnetic tape
ARIS Methods
9-23
9.3.2.5
Describing Key Performance Indicators and Their relationships
Once the key performance indicators for measuring strategic objectives and critical success factors have been selected, these indicators and their relationships can be defined in more detail using the Key performance indicator tree model type. A Key performance indicator tree structures the various key performance indicators in a hierarchy by means of the influences connection type. The Weighting attribute can be maintained for these connections making it possible to calculate an overall key performance indicator within a key performance indicator tree from the weights. The Key performance indicator tree is assigned to the key performance indicator instance representing the overall key performance indicator . The assignment is applied by the BSC evaluations Create Management View and Perform Planned-Actual Comparison.
Figure 9.3.2-3: Key Performance Indicator Tree
ARIS Methods
9-24
The Key performance indicator tree uses only the Key performance indicator instance Object type. The Key performance indicator tree can be found at the requirements definition level of the Data view.
9.3.3
Relationship to Other Models
The objects of the Balanced Scorecard method can be related to the following ARIS models: eEPC Target diagram DW structure DW transformation
ARIS Methods
eBusiness Scenario Diagram
10-1
10 eBusiness Scenario Diagram

10.1 Introduction
The smooth sequence of inter-company business processes is becoming ever more important. On the one hand the sequence of specific procedures at the interfaces between the companies is in the center of interest, on the other hand there are the interfaces between the companies and their customers. The contacts need to take place in a clear, quick, consistent and direct manner. The expeditious location of suitable business partners - from a corporate perspective - and vendors - from a consumer point of view - is also of great relevance. An optimum arrangement of these processes means a competitive advantage. The ideal platform for supporting these multilateral relations is the Internet. Since the processes in the above-mentioned environment are very complex, it is necessary to define what is meant by e-business. Definition: E-business is a generic term for the use of information and communications technologies in support of a company's commercial activities. It includes supporting the relationships and processes between business associates, employees and customers through the use of electronic media (Herrmans, Sauter, 1999).
Thus e-business can mean the creation of a web page for a corporate presentation, the acquisition of an item through the Internet, a very complex project of two companies, or the multilayered relationships between any number of business partners meeting in a marketplace. It can be sub-divided into the following concepts: B2B (Business to Business) Business to Business describes the transactions taking place between companies. An example of how this can be done is through the linking of companies' supply chains.
ARIS Methods
10-2
B2C (Business to Consumer) Business to Consumer describes transactions taking place between companies and their customers. An example of this is the purchasing done by customers in online shops. B2A/C2A (Business/Consumer to Administration) Business/Consumer to Administration describes all transactions between companies or individuals and the public administration. It is especially in the area of contacts between companies and the administration that a great potential for reducing expenses has been perceived.
Figure 10.1-1: Transaction Possibilities in e-Business
In addition to differentiating between several partners, a distinction can also be made in the range of relationships between the various partners: one to one, one to many, many to many. The marketplace scenario in particular has gained great importance.
ARIS Methods
10-3
Marketplaces Electronic Marketplaces are virtual places, in which any number of people buy and sell products and services openly as well as exchange information. It was to support these conceivable scenarios that the E-business scenario diagram was developed. In conjunction with other methods and various components supplied by the ARIS Toolset, it is possible to support the implementation of ebusiness projects optimally. This chapter of the E-Business scenario diagrams first describes the method with all the objects and evaluation possibilities and then goes on to discuss the link to other methods. Finally, an example of an application is presented that will demonstrate all the intricate possibilities.
10.2 The Method of the E-Business Scenario Diagrams

10.2.1 The Idea
The aim is to develop optimization potential from the ability to view a value-added chain holistically, i.e. from end customer through all the companies involved in the procedure. The objective is, for example, the improvement of the supply chain, the lowering of procurement and distribution costs or the optimization of the architecture of the information system. The E-Business scenario diagram representation allows visualizing the contents that need to be examined to attain the designated objectives. By selecting the type of column representation, the interfaces between very different process partners are abstracted and mapped over the column borders. Several reports supplement the models and offer important analysis capabilities.
10.2.2
The Model and its Objects
The business subjects considered in the model are placed in the header and identified as business participants. They originate in the organizational view and can be assigned by means of organizational charts that can, for example, clarify the company structure or the relationship between the objects of the individual columns.
ARIS Methods
10-4
The central and structurally relevant objects of the model are the individual processes of the business subjects and their interfaces that are involved in the overall process. An individual process, which may be a Business process, is a company process playing an important role in multicompany cooperation. The assignment of a process model allows a more precise representation and analysis of such an individual process to take place. All of the company's procedures are modeled in the line under the business participant but in the same column. Intercompany reconciliation also requires the precise analysis of the application systems and hardware that is being used by the various business objects in support of their individual processes, e.g. the ERP systems. They are represented by Business components. To reconcile these very different components, the exact responsibilities for the systems must be specified. For this, Organizational unit type objects can be used. Even the roles of the employees involved in the process can be defined. They are shown in the model as an Employee role. The inclusion of interfaces constitutes a special requirement for e-Business modeling in general. This is where the column edges become very important since they symbolize the interfaces between the process participants. They can be viewed from several perspectives. One point of emphasis can be the transfer of process-specific information. That is the purpose of the Business documents, which may be in the form of XML or HTML documents. The business document can have an assigned data view model such as a document type definition. Alternatively, the flow of money or goods can be displayed using Money transaction or Goods shipment objects. A further important aspect: the security of data must be ensured, and especially that of electronic payments sent via the Internet. Several different encoding techniques can be used for this purpose, e.g. SET (Secure Electronic Transaction), or SSL (Secure Socket Layer). This security aspect is taken into account with the inclusion of the Security protocol object. An Organizational unit type is also used to represent the persons responsible for securing transactions. Here it is possible to specify the analysis of a more technical aspect, namely the display of the technical buildup of the data transfer to the interfaces. For this, the model uses various information carriers. The individual processes can be linked via an intranet, an extranet or the Internet. Data transfer can take place per e-mail. The mobile phone is also gaining ground as a transmission medium.
ARIS Methods
10-5
Figure 10.2-1: The Objects in the e-Business Scenario Diagram
ARIS Methods
10-6
10.2.3
Transmission Type Attribute Group
Modeled objects can be further specified by maintaining their attributes. An attribute is especially tailored to the requirements of the e-business. Attention should be given to the Transmission type attribute group of the Business document, Money transaction and Goods shipment objects. Maintaining transmission type attributes not only identifies the transmission path, but also expresses the need for securing the transaction. In the case of an online transmission, for example, it is important not to omit the above-mentioned securing of confidential information and data.
10.3 Evaluations Using Reports

Several possible evaluation options provide support for E-Business Scenarios modeling. These evaluations are made in the form of reports. ARIS offers several pre-defined evaluation reports, but user-specific ones are also conceivable. The following reports for E-Business Scenarios are provided.
10.3.1
Checking Data Security
The security of data transferred online is one of the most important points influencing e-business acceptance. Protecting personal information or payments from access by unauthorized persons, is an issue that must be resolved in order to avoid a loss of confidence by customers and associates. A report allows all the exchanged services (Money transaction and Goods shipment) to be checked as well as the data (Business documents) referring to the same. For this, the mentioned Transmission type attribute group is evaluated and, in the event that it is an online transmission, checked to determine if data encoding takes place. Thus possible security gaps as well as obsolete encoding methods may be identified and easily updated.
ARIS Methods
10-7
10.3.2
System Support
A second important aspect in e-business projects is reconciling the application systems. Here a company must consider many questions. Which processes must be supported by which systems? Who will be responsible for operating which systems? Where might training expenses be incurred? What customizations of existing systems are necessary? Here too, the answers can be found in a report. The individual processes are listed together with the corresponding systems and the persons responsible for them.
10.3.3
Information Flow
In contrast to other process models, E-Business Scenarios highlight transactions. Special attention is given the data and services being exchanged. Consequently evaluations are also offered for this purpose. The important question is, what data and services are generated at a specific location, and where they are used. For this, there is a report that gives the modeled data services as well as the processes in which they figure as input or output.
10.3.4
Collaborative Business Maps
The collaborative business maps used by SAP constitute a special type of model. They emphasize a view of certain partners. There are two views that are oriented towards different target groups. The "aggregated view", which is destined for senior management, only contains the business participants and the processes. The "detailed view" includes documents and the roles of the process managers responsible for operational departments. The reports allow the transfer of the information shown in E-Business scenario diagram to both views at any time.
ARIS Methods
10-8
10.4 Connecting to Other Methods and Components

The various modeling methods in the ARIS Toolset allow the information in different views to be displayed and made available to various target groups with a special perspective. The E-Business Scenario is the starting point for these views. Its objects allow specific target group details to be given. In this way, an e-business project can be represented in its entirety. In addition, the various components of ARIS allow evaluations to be made for the models generated so that there is an optimal support for projects in the e-business environment. Example: Introduction of an Online Shop The first step is defining the objectives that are to be realized through the introduction of e-business with the help of the Balanced Scorecard ARIS component (see the chapter Balanced Scorecard Method). This identifies the processes that have to be optimized to attain this objective. In the present example, the goal is identified as the development of a new distribution channel, namely the Internet. In order to pursue this new path optimally, precise documentation and planning are indispensable. Not only must the process course itself be taken into account, but also the organization of the responsible persons, the interfaces between various systems, and data security. The starting point for the views is the E-Business scenario diagram. The business participants in our example are the company that implements the shop system, and the customer who will use this offer. The entire process from "entering the shop" to "leaving" is broken down into its most important parts. The representation contains the view of the customer and that of the company. The E-Business scenario diagram serves as an entry point to the implementation project. Figure 3 shows how the entire process is divided up.
ARIS Methods
10-9
Figure 10.4-1: Detail of the E-Business Scenario "online shop"
The various steps in the process can then be refined through EPCs, e.g. checked with simulations components, displayed after optimization by means of pipeline diagrams, and converted into a finished shop system through Intershop Enfinity where it can be further improved.
ARIS Methods
10-10
Figure 10.4-2: Detail from the pipeline diagram
If a shop is to be connected to an external ERP system (Enterprise Resource Planning-System) then the data to be transferred must be in the correct formats. For this purpose there are various ways of standardizing documents and data. One such possibility for standardization is offered by the use of extensible markup language (XML). In creating the documents, DTDs can be assigned to help define the structure and required contents. Since XML is a language that is being developed along completely different paths, a consistent foundation is also necessary here. Different organizations, consisting of companies and scientific institutions, are involved in standardizing XML for various sectors. The use of standardized XML documents facilitates the integration of ERP systems..
ARIS Methods
10-11
Figure 10.4-3: Detail from DTD - Ordering
The problems involved with various components that must be reconciled with each other, have already been mentioned. The application system diagram allows the systems to be visualized, and application systems or even business components to be assigned as models to clarify the systems' interrelationships. The organization's structure will also be affected by the introduction of e-business. It may be necessary to define new responsibilities or make new allocations. The EBusiness scenario diagram can describe the roles and organizational units within the various steps of the process. What position they take in the company's organization or in the process can be analyzed further by means of organizational charts. Implementation begins with the conversion of modeled contents. When the Intershop method is used, the modeled contents are converted into a working system with Intershop Enfinity.
ARIS Methods
IT City Planning
11-1
11 IT City Planning
Over the past few years the Internet has been increasingly used for customercompany and also inter-company communications. This has led to an increase in the variety of software solutions deployed within companies. For example, an automobile manufacturer might use modules of an ERP system1 in production planning, materials management, finance, controlling and sales and also a CRM system2 in the sales department. SCM solutions3, standard office and departmental applications such as CAD software in the R&D department complete the system landscape. Besides this technological development, the growing number of corporate mergers and acquisitions further increases the complexity of the information systems in a company. These trends mean that companies have had to increase their spending on developing new corporate architectures. They should be aiming for flexible architectures that can be easily adapted to the company's constantly changing environment, and are thus future-proof. According to the Gartner Group, 80% of the money spent on projects of this kind is wasted because the architectures implemented fail to achieve this objective and have to be replaced with new projects (see Jeff Schulman, A New View of Architectures Needed for New Business Drivers, P. 2ff.).
ERP = Enterprise Resource Planning. Software solutions deployed for managing, controlling and evaluating business processes in production, sales, logistics, finance, human resources, administration etc. CRM = Customer Relationship Management is an integrated, company-wide management and organization concept encompassing all actions designed to improve customer orientation and satisfaction. SCM = Supply Chain Management involves the optimization of process planning and implementation along a product's entire value-added chain. The processes are optimized, as it were, from the supplier's supplier through to the customer's customer.
ARIS Methods
IT City Planning
11-2
The reasons for this failure are: Lack of strategy/vision in the draft architecture. Insufficient financial and human resources to enable an understanding of the complexity of interactions within a corporate information system. Tendency towards silo developments that favor redundant infrastructures and components instead of shared services and applications created for communities of interest. Use of classic architecture methods that strive to enforce a particular standard within the company. Inadequate or inappropriate organizational influence on the building of the corporate architecture and its use.
11.1
What Will New, Successful Corporate Architectures Have to Look Like?
New, efficient architectures have to take five levels into consideration: 1. The top level is the corporate network, i.e. the totality of the companies that communicate with each other. 2. The level below that deals with the company which executes the business processes to achieve its corporate goals. 3. The third level looks at Business Process Styles. These are derived from business processes that meet similar requirements. 4. Each of these Business Process Styles4 leads to an architecture style, also known as a Pattern, that ensures optimum support for the processes. Examples of a Pattern are 3-tier architectures, host-centric, service-oriented etc. 5. From a Pattern, the company can derive the required components that provide the fundamental, base technology functionalities, e.g. operating systems and databases.
Process templates with reference processes
ARIS Methods
IT City Planning
11-3
11.2
Organizational Requirements of IT Projects
Successful IT projects must satisfy the following organizational requirements : At the highest level, the CEOs of the companies involved must coordinate and clearly formulate the objectives in a steering committee. At the next level, a permanent steering committee should be formed comprising the CIOs and the managers of the divisions concerned and the IT department. At the third level the architects work out the required functional definitions. At the fourth level, Integration Competence Centers develop, administer and monitor the installation, integration and operation of the infrastructure.
11.3
Technological Requirements
From the technological view, installing a successful corporate architecture calls for completely new architectural methods. These methods differ from their predecessors in that they address the interactions within the system rather than the systems technological aspects. The OMG Model-Driven Architecture (MDA) is one example of this new generation of architecture methods (see www.omg.org/mda). Entry into designing new architectures is via Computation and Platform Independent Models (CIM and PIM). Model transformation turns a PIM into a Platform Specific Model (PSM). These models are described using UML5.
11.4
Enterprise Architecture and IT City Planning
IT City Planning is an architectural approach that was developed by the Frenchman Jacques Sassoon in the 1980s. The aim of IT City Planning is to bring harmony to a heterogeneous system landscape by thoroughly analyzing its interactions, i.e. the exchange of information among the applications in that system. Based on the approach used in town planning, the procedure for drawing up an IT city plan is informed by the idea of enabling long-term, strategic IT management
Unified Modeling Language Modeling/notation for object-oriented software development
ARIS Methods
IT City Planning
11-4
that considers not only the present but also aspects of the past (legacy systems) and those of the future. There is no need to redesign the entire system. Instead, a project-by-project, incremental approach is adopted. As with MDA, entry is via models that describe the information system without reference to technology-related information. However, IT City Planning dispenses with UML, which simplifies entry for those with a less technical background and increases its acceptance.
11.5
Which Companies Could Benefit from IT City Planning?
Companies with a large portfolio of applications that have a long history of using information technologies for which information technology is of strategic importance that are involved in a merger.
Goals of IT City Planning: Reusing software resources so as to avoid creating further redundancies. Reducing maintenance costs by "block" overhaul and definition of new software resources that can replace existing resources and cover their diverse use cases. Consolidating information systems. Preparing the deployment of EAI software6 at a higher level.
Creating an IT city plan is the responsibility of the Integration Competence Center. The plan itself must address both the design pattern and the information and technology architecture.
EAI = Enterprise Application Integration. Company-wide integration of applications. EAI provides the e-Business infrastructure. EAI software is the technical middleware and a prerequisite for implementing an e-Business strategy.
ARIS Methods
IT City Planning
11-5
11.6
IT City Planning with ARIS
IT City Planning considers four views: Process View Data View Function View Information System View (IS View )
7
The Process View, Data View and Function View have long been used in ARIS, but the IS View is new. It is positioned between the requirements definition level and the design specification level of the Function View. From the ARIS Function View, the application system and IT function types are combined to form the "IT View". Elements of the IS View structure information systems initially without reference to the classic IT elements Application system type, IT function type and Module type.
IS View = Information System View
ARIS Methods
IT City Planning
11-6
Figure 11-1: Process, IS, IT and Data Views
ARIS Methods
IT City Planning
11-7
11.7
The IS View
ARIS includes the following model types for describing the IS View: Enterprise architecture model Enterprise architecture model (column display) IS context model
The two Enterprise architecture models structure the information system in a hierarchy. An IS hierarchy can include the following levels: Zones Districts Building clusters Functional blocks IS functions IS services
Zone, District, Building cluster and Functional block are Functional cluster object types. Functional clusters are used to organize an information system in independent units/blocks by function. Each cluster is characterized in that it is the "owner" of the data it uses and of the associated processing methods. Other clusters can only access these data and processing methods if they call a service of the "owner cluster". Within a cluster, similar data are used and identical activities and business functions are carried out.
At the top level the information system is divided into zones. A zone can correspond to an operational and development area, for example.
ARIS Methods
IT City Planning
11-8
The following figure shows the zones into which a company's information system can be typically broken down.
Figure 11-2: Zones of a Company's Information System
Each zone in turn can contain one or more districts. Districts of a zone are characterized by similar processes and substantial similarity in terms of temporal features (e.g. similar life cycles and information processing cycles). Districts can be terms of payment or of price, personnel administration, travel guidelines etc. For example, the second level of the Resources zone can include the Human resources and Accounting districts:
Figure 11-3: Zones Divided into Districts
A district may contain one or more building clusters that serve a functional purpose, e.g. salary payments, invoicing etc.
ARIS Methods
IT City Planning
11-9
The Human Resources district includes the Division administration, Recruiting, Personnel development, and Personnel support building clusters.
Figure 11-4: District Divided into Building Clusters
Each building cluster can encompass one or more functional blocks. Functional blocks are characterized by substantial similarity regarding the business objects and events they manage.
A functional block is an independent, reusable functional component. IS functions and IS services are combined to form a functional block according to the following rules: They feature a close interrelationship between the objects they manage and the functions they support. There is only minimal exchange with other functional blocks.
ARIS Methods
IT City Planning
11-10
The Personnel support building cluster in our example includes the Master data maintenance, Staff evaluations, Controlling and Salaries functional blocks.
Figure 11-5: "Personnel Support" Building Cluster Divided into Functional Blocks
An IS function describes an elemental function within a system. It supports the realization of an activity within a process.
An IS service
describes an interface of a functional cluster or an IS function. IS
services allow other IS elements to have controlled access to data and processing methods of the IS element which provides the service. These interfaces can be used to exchange messages with other elements of the IT View.
ARIS Methods
IT City Planning
11-11
The following figure shows the IS functions and IS services of the Salaries building cluster.
Figure 11-6: IS Functions and IS Services of the "Salaries" Building Cluster
For describing the IS hierarchy it is not necessary to model all levels described here entirely. The IS function and IS service IS elements are not regarded as elements of the city plan for purposes of IT City Planning. The city planner's responsibilities end at the building block level. IS functions and IS services are the responsibility of the architect (see Longp, Christoph: Le projet d'urbanisation du systme d'information, P. 18).
ARIS Methods
IT City Planning
11-12
11.8
Functional Clusters and their Data
The eERM is used to describe which data is encapsulated in a functional cluster or an IS function. In the context of the City Planning approach, the eERM offers the IS View symbols. An is owner of connection type can be used to link these objects to relationship and entity types.
Figure 11-7: "is owner of" Connection between Symbols of the IS View and Relationship and Entity Types
ARIS Methods
IT City Planning
11-13
11.9
Detailed Description of Clusters
The functional clusters and IS functions of an information system are described in detail in the IS context model. This includes the interfaces of a block, the interactions between the blocks, the application systems supporting the block, and business management functions that are supported by the block.
Zones, Districts, Building clusters, Functional blocks and IT functions can be connected to an IS service using the provides connection. Input/output connections can be used between IS elements and data elements to describe the information flow between the clusters. The various application system and IT function type objects can be assigned to the objects of the IT View using a connection of the supports type. If the city plan is interpreted as a development plan of a city, this connection provides information about which information system areas are "populated" by which application systems. The supports connection is also available for use between IS elements and the function.
Figure 11-8: "supports" Connection between IS Elements and Function
ARIS Methods
IT City Planning
11-14
11.10
The IT View
Analogous to the IS View, the IT View contains the following model types: Application system type diagram Application system type diagram (column display) Access diagram (also called IT context model)
Application system hierarchy In the context of City Planning, the application system hierarchy currently in use in the company is mapped with the aid of the application system type diagram or the application system type (column display). The application system type (column display) is a swimlane diagram needed for city planning.
8
which provides precisely those object types,
symbols and relationship types from the application system type diagram that are
The following levels of an application system type hierarchy can be mapped: IT system Subsystem IT software IT block IT procedure Socket
IT system, Subsystem, IT software and IT block are symbols of the Application system type object type. The hierarchy is built using the encompasses relationship type.
Swimlane diagram/model: diagram in column and/or row display
ARIS Methods
IT City Planning
11-15
The IT systems are at the top level of the application system type hierarchy. An IT system describes a structured set of IT elements, usually subsystems. Administering and operating an IT system is the responsibility of a uniquely defined organizational unit. A subsystem describes a component of an IT system. The components of a subsystem are called IT software. IT software supports an homogeneous set of functions. It is user-oriented and supports one or more business processes. IT blocks are components of IT software. As a rule, an IT block groups together those IT procedures that access the same data (databases, tables, files etc.). IT procedures are objects of the IT function type type. Each IT procedure supports a specific function. A socket corresponds to the IS service, i.e. it describes an interface that an IT element provides for other IT elements so that they can access its data and processing methods.
The following figure shows one example of the subsystem structure of the DATEV system:
Figure 11-9: Subsystem Structure of the DATEV System
ARIS Methods
IT City Planning
11-16
11.11
IT Elements and their Data
As with IS elements, the eERM includes the the is owner of connection between Application system type, IT function type or Socket and Entity or Relationship type to describe the data that are encapsulated in an IT element.
11.12
Detailed Description of IT Elements
IT elements in the IT city plan are described in detail in the Access diagram. This corresponds to the IS context model in the IS View. The following can be described: Input and output relationships of the IT element in question Supported business functions Supported IS elements Calling of other IT elements by the considered element Platform on which the IT element runs Users of the IT element
Figure 11-10: Detailed Description of IT Elements in the Access Diagram
ARIS Methods
IT City Planning
11-17
11.13
Organizational Aspects
The detailed description of an IT element also incorporates information from the Organization View. This includes information about which organizational elements can be users of an IT element, and more. A network diagram can be used to show the influences and effects of the IT infrastructure.
Figure 11-11: Influences and Effects of the IT Infrastructure
ARIS Methods
IT City Planning
11-18
11.14
Chronological Procedures within the Architecture
The appropriate objects for integrating IS and IT elements in a chronological flow are all available in the various process models (all variations of the eEPC) and the Program structure chart.
Figure 11-12: Integration of IS and IT Elements in a Chronological Procedure
ARIS Methods
IT City Planning
11-19
11.15
Possible Evaluations
Based on the modeling options described in the sections above, various evaluations can be run to answer the following questions and to help set up the future information system: What data is being managed by a given IS element? Which application systems support an IS element? Which functions are supported by a given IS element? What data are used by the IT elements of a given IS element? What data are generated by the IT elements of a given IS element? Which IS services are provided by an IS element and in which processes are they used? On which hardware components are the application systems of a particular IS element running?
ARIS Methods
11.1 Model Types - Specific Object Types
11-1
11 Appendix
11.1.1
Model Type Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Access diagram
Object Types Application system class Application system type Attribute Attribute type group Class Cluster/Data model DBMS type Entity type ERM attribute Field Function Graphical user interface type Group Hardware component Hardware component type Information carrier Information flow IT function class IT function type List
ARIS Methods
11-2
Model Type Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Object Types Location Module class Module type Operating system type Organizational unit Organizational unit type Person Person type Position Programming language Relation Relationship type Screen Table Technical term View View (physical)
11.1.2
Model Type
Access diagram (physical)

Object Types Application system Application system class Application system type Attribute
Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical)
ARIS Methods
11-3
Model Type Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical)
Object Types Attribute type group Class Cluster/Data model DBMS Entity type ERM attribute Field Field (specimen) Function Group Hardware component Information carrier Information flow IT function IT function class IT function type List Location Module Module class Module type Organizational unit Organizational unit type Person Person type
ARIS Methods
11-4
Model Type Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical)
Object Types Position Program module Program module type Relation Relationship type Screen Table Tables (specimen) Technical term View View (physical)
11.1.3
Model Type
Application system diagram

Object Types Application system Application system type DBMS DBMS type Function Graphical user interface type IT function IT function type List Module
Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram
ARIS Methods
11-5
Model Type Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram
Object Types Module type Operating system type Program library Program module Program module type Programming language Screen
11.1.4
Model Type
Application system type diagram

Object Types Application system class Application system type DBMS type Draft list Function Graphical user interface type IT function class IT function type List Module class Module type Objective Operating system type Program module type
Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram
ARIS Methods
11-6
Model Type Application system type diagram Application system type diagram Application system type diagram
Object Types Programming language Screen Screen design
11.1.5
Model Type
Attribute allocation diagram

Object Types Attribute Domain ERM attribute Relation Relationship type
Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram
11.1.6
Model Type
Authorization hierarchy
Object Types Authorization condition
Authorization hierarchy
11.1.7
Model Type
Authorization map
Object Types Authorization condition Group Location Organizational unit Organizational unit type
Authorization map Authorization map Authorization map Authorization map Authorization map
ARIS Methods
11-7
Model Type Authorization map Authorization map Authorization map
Object Types Person Person type Position
11.1.8
Model Type
BSC Cause-and-effect diagram

Object Types Critical factor Key performance indicator instance Objective Perspective Strategy
BSC Cause-and-effect diagram BSC Cause-and-effect diagram BSC Cause-and-effect diagram BSC Cause-and-effect diagram BSC Cause-and-effect diagram
11.1.9
Model Type
Business controls diagram

Object Types Control Information carrier Organizational unit Risk Solution
Business controls diagram Business controls diagram Business controls diagram Business controls diagram Business controls diagram
ARIS Methods
11-8
11.1.10
Model Type c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method c3 method
c3 method
Object Types Entity type Function Group Improvement potential Knowledge category Location Objective Organizational unit Organizational unit type Person Person type Position Structural element Tool
11.1.11
Model Type CD Diagram
CD Diagram
Object Types Cost driver
11.1.12
Model Type
Class diagram
Object Types Attribute type group
Class diagram
ARIS Methods
11-9
Model Type Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram
Object Types Cluster/Data model Entity type ERM attribute ERM domain Event Function Generalization type Relationship type Rule Technical term
11.1.13
Model Type
Classification diagram
Object Types Classification criterion Function Object type class
Classification diagram Classification diagram Classification diagram
11.1.14
Model Type
Communications diagram
Object Types Communication Organizational unit Organizational unit type
Communications diagram Communications diagram Communications diagram
ARIS Methods
11-10
11.1.15
Model Type
Competition model
Object Types Organizational unit Product/Service
Competition model Competition model
11.1.16
Model Type
Cost category diagram

Object Types Cost category
Cost category diagram
11.1.17
Model Type DTD DTD DTD DTD DTD DTD DTD DTD
DTD
Object Types Attribute type Conditional section Contents Element type Enumeration Enumeration attribute type Sequence XOR
ARIS Methods
11-11
11.1.18
Model Type
DW - structure
Object Types Cluster/Data model Entity type ERM attribute
DW - structure DW - structure DW - structure
11.1.19
Model Type
DW - transformation
Object Types Cluster/Data model Entity type ERM attribute Function
DW - transformation DW - transformation DW - transformation DW - transformation
11.1.20
Model Type
E-Business scenario diagram

Object Types Application system Application system type Cluster/Data model Function Information carrier Organizational unit type Person type Product/Service Security protocol
E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram
ARIS Methods
11-12
11.1.21
Model Type eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
eEPC
Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type Employee variable Entity type ERM attribute Event Function General resource Group
ARIS Methods
11-13
Model Type eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Object Types Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Module Module type Objective Operating resource Organizational unit Organizational unit type Package Person Person type Position Product/Service Relationship type Rule Screen Screen design System organizational unit System organizational unit type
ARIS Methods
11-14
Model Type eEPC
Object Types Technical term
11.1.22
Model Type
eEPC (column display)

Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type Employee variable Entity type ERM attribute Event
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
ARIS Methods
11-15
Model Type eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Object Types Function General resource Group Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Module Module type Objective Operating resource Organizational unit Organizational unit type Package Person Person type Position Product/Service Relationship type Rule Screen
ARIS Methods
11-16
Model Type eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Object Types Screen design System organizational unit System organizational unit type Technical term
11.1.23
Model Type
eEPC (instance)
Object Types Application system Application system class Application system type Cluster instance Complex object COT attribute (instance) Draft list Employee variable Entity ERM attribute instance Event instance Function instance General resource Group Hardware component type Information carrier IT function
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
ARIS Methods
11-17
Model Type eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Object Types IT function type List Location Module Module type Operating resource Organizational unit Organizational unit type Person Person type Position Relationship Rule instance Screen Screen design System organizational unit System organizational unit type Technical terms instance Transaction folder
11.1.24
Model Type

Object Types Application system Application system class
eEPC (material flow) eEPC (material flow)
ARIS Methods
11-18
Model Type eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Object Types Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type Employee variable Entity type ERM attribute Event Function General resource Group Hardware component type Information carrier IT function IT function type
ARIS Methods
11-19
Model Type eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Object Types Key performance indicator instance Knowledge category List Location Material type Module Module type Objective Operating resource Operating resource type Organizational unit Organizational unit type Package Packaging material type Person Person type Position Product/Service Relationship type Rule Screen Screen design System organizational unit System organizational unit type Technical operating supply
ARIS Methods
11-20
Model Type eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Object Types Technical operating supply type Technical term Transport system Transport system type Warehouse equipment Warehouse equipment type
11.1.25
Model Type
eEPC (row display)

Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type
eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display)
ARIS Methods
11-21
Model Type eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display)
Object Types Employee variable Entity type ERM attribute Event Function General resource Group Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Module Module type Objective Operating resource Organizational unit Organizational unit type Package Person Person type Position
ARIS Methods
11-22
Model Type eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display)
Object Types Product/Service Relationship type Rule Screen Screen design System organizational unit System organizational unit type Technical term
11.1.26
Model Type
eEPC (table display)

Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
ARIS Methods
11-23
Model Type eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Object Types Documented knowledge Draft list Element type Employee variable Entity type ERM attribute Event Function General resource Group Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Module Module type Objective Operating resource Organizational unit Organizational unit type Package
ARIS Methods
11-24
Model Type eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Object Types Person Person type Position Product/Service Relationship type Rule Screen Screen design System organizational unit System organizational unit type Technical term
11.1.27
Model Type eERM eERM eERM eERM eERM eERM eERM eERM eERM eERM
eERM
Object Types Attribute type group Cluster/Data model COT attribute Entity type Enumeration Enumeration list occurrence ERM attribute ERM domain Generalization type Measurement unit
ARIS Methods
11-25
Model Type eERM eERM
Object Types Measurement unit number Relationship type
11.1.28
Model Type
eERM attribute allocation diagram

Object Types Attribute type group COT attribute Entity type Enumeration Enumeration list occurrence ERM attribute ERM domain Generalization type Measurement unit Measurement unit number Relationship type
eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram
11.1.29
Model Type
Event diagram
Object Types Application system type Class Cluster/Data model Complex object type COT attribute
Event diagram Event diagram Event diagram Event diagram Event diagram
ARIS Methods
11-26
Model Type Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Object Types Documented knowledge Element type Entity type ERM attribute Event General resource Group Information carrier IT function type Key performance indicator instance Knowledge category Module type Organizational unit Organizational unit type Person Person type Position Product/Service Relationship type Rule Screen Technical term
ARIS Methods
11-27
11.1.30
Model Type
Function allocation diagram

Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type Employee variable Entity type ERM attribute Event Function General resource Group
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
ARIS Methods
11-28
Model Type Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Object Types Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Material type Module Module type Objective Operating resource Operating resource type Organizational unit Organizational unit type Package Packaging material type Person Person type Position Product/Service Relationship type Screen Screen design
ARIS Methods
11-29
Model Type Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Object Types System organizational unit System organizational unit type Technical operating supply Technical operating supply type Technical term Transport system Transport system type Warehouse equipment Warehouse equipment type
11.1.31
Model Type
Function allocation diagram (instance)

Object Types Application system Application system class Application system type Cluster instance Complex object COT attribute (instance) Draft list Employee variable Entity ERM attribute instance Event instance Function instance
Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
ARIS Methods
11-30
Model Type Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
Object Types General resource Group Hardware component type Information carrier IT function IT function type List Location Module Module type Operating resource Organizational unit Organizational unit type Person Person type Position Relationship Screen Screen design System organizational unit System organizational unit type Technical terms instance
ARIS Methods
11-31
11.1.32
Model Type
Function tree
Object Types Function
Function tree
11.1.33
Model Type
Function/organizational level diagram

Object Types Cluster/Data model Function Organizational level
Function/organizational level diagram Function/organizational level diagram Function/organizational level diagram
11.1.34
Model Type
IE Data model
Object Types Cluster/Data model Entity type ERM attribute Generalization type
IE Data model IE Data model IE Data model IE Data model
11.1.35
Model Type
Industrial process
Object Types Application system type Class Cluster/Data model Documented knowledge
Industrial process Industrial process Industrial process Industrial process
ARIS Methods
11-32
Model Type Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Object Types Entity type ERM attribute Event Function General resource Group Information carrier Key performance indicator instance Knowledge category Location Material type Objective Operating resource type Organizational unit Package Packaging material type Person Person type Position Product/Service Relationship type Rule Screen Technical operating supply type Technical term
ARIS Methods
11-33
Model Type Industrial process Industrial process
Object Types Transport system type Warehouse equipment type
11.1.36
Model Type
Information carrier diagram

Object Types Information carrier
Information carrier diagram
11.1.37
Model Type
Information flow diagram

Object Types Function Information flow Organizational unit Organizational unit type System organizational unit System organizational unit type
Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow diagram
11.1.38
Model Type
Input/Output diagram
Object Types Cluster/Data model Entity type ERM attribute Function Information carrier
Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram
ARIS Methods
11-34
Model Type Input/Output diagram
Object Types Relationship type
11.1.39
Model Type
Input/Output diagram (inverse)

Object Types Cluster/Data model Entity type ERM attribute Function Information carrier Relationship type
Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse)
11.1.40
Model Type
Key performance indicator allocation diagram

Object Types Application system Application system type Class
Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram
Cluster/Data model Critical factor Documented knowledge
ARIS Methods
11-35
Model Type Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram
Object Types Entity type
ERM attribute Function Function instance
Group Information carrier Key performance indicator instance Knowledge category
Objective Organizational unit Organizational unit type
Person Person type Position
ARIS Methods
11-36
Model Type Key performance indicator allocation diagram Key performance indicator allocation diagram
Object Types Relationship type
Technical term
11.1.41
Model Type
Key performance indicator tree

Object Types Key performance indicator instance
Key performance indicator tree
11.1.42
Model Type
Knowledge map
Object Types Group Knowledge category Location Organizational unit Organizational unit type Person Person type Position
Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map
ARIS Methods
11-37
11.1.43
Model Type
Knowledge structure diagram

Object Types Application system class Application system type Class Cluster/Data model Documented knowledge Entity type Information carrier Knowledge category Object instance Package Relationship type Technical term
Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram
11.1.44
Model Type
Material diagram
Object Types Material class Material type Packaging material class Packaging material type
Material diagram Material diagram Material diagram Material diagram
ARIS Methods
11-38
11.1.45
Model Type
Material flow diagram

Object Types Function Material flow Organizational unit Organizational unit type
Material flow diagram Material flow diagram Material flow diagram Material flow diagram
11.1.46
Model Type
Network diagram
Object Types DBMS Hardware component Hardware component type Location Network Network class Network connection Network connection type Network node Network node type Network type Operating system Organizational unit Person Person type Position
Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram
ARIS Methods
11-39
11.1.47
Model Type
Network topology
Object Types DBMS type Hardware component class Hardware component type Location Network class Network connection type Network node type Network protocol Network type Operating system type Organizational unit Person Person type Position
Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology
11.1.48
Model Type
Objective diagram
Object Types Critical factor Function Objective Product/Service
Objective diagram Objective diagram Objective diagram Objective diagram
ARIS Methods
11-40
11.1.49
Model Type
Office process
Object Types Application system type Class Cluster/Data model Documented knowledge Entity type ERM attribute Event Function General resource Group Information carrier Key performance indicator instance Knowledge category Location Objective Organizational unit Package Person Person type Position Product/Service Relationship type Rule
Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process
ARIS Methods
11-41
Model Type Office process Office process
Object Types Screen Technical term
11.1.50
Model Type
OMT Class description model

Object Types Class ERM attribute Operation
OMT Class description model OMT Class description model OMT Class description model
11.1.51
Model Type
OMT Data value decomposition

Object Types Data value
OMT Data value decomposition
11.1.52
Model Type
OMT Dynamic model

Object Types Class State
OMT Dynamic model OMT Dynamic model
11.1.53
Model Type
OMT Functional model

Object Types Actor Connector
OMT Functional model OMT Functional model
ARIS Methods
11-42
Model Type OMT Functional model OMT Functional model OMT Functional model
Object Types Data store Data value Process
11.1.54
Model Type
OMT Object model

Object Types Association Association instance Class Constraint ERM attribute Object instance Operation Sp./gen. operator
OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model
11.1.55
Model Type
Organizational chart
Object Types Group Location Organizational chart Organizational unit Organizational unit type Person Person type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
ARIS Methods
11-43
Model Type Organizational chart Organizational chart Organizational chart
Object Types Position System organizational unit System organizational unit type
11.1.56
Model Type PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
PCD
Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list Element type Employee variable Entity type
ARIS Methods
11-44
Model Type PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Object Types ERM attribute Event Function General resource Group Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Module Module type Objective Operating resource Organizational unit Organizational unit type Package Person Person type Position Product/Service Relationship type
ARIS Methods
11-45
Model Type PCD PCD PCD PCD PCD PCD
Object Types Rule Screen Screen design System organizational unit System organizational unit type Technical term
11.1.57
Model Type
PCD (material flow)

Object Types Application system Application system class Application system type Attribute type group Authorization condition Business object Class Cluster/Data model Complex object type Component Cost category Cost driver COT attribute Documented knowledge Draft list
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
ARIS Methods
11-46
Model Type PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
Object Types Element type Employee variable Entity type ERM attribute Event Function General resource Group Hardware component type Information carrier IT function IT function type Key performance indicator instance Knowledge category List Location Material type Module Module type Objective Operating resource Operating resource type Organizational unit Organizational unit type Package
ARIS Methods
11-47
Model Type PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
Object Types Packaging material type Person Person type Position Product/Service Relationship type Rule Screen Screen design System organizational unit System organizational unit type Technical operating supply Technical operating supply type Technical term Transport system Transport system type Warehouse equipment Warehouse equipment type
11.1.58
Model Type PPC PPC PPC
PPC
Object Types Cluster instance Event instance Function instance
ARIS Methods
11-48
Model Type PPC PPC PPC PPC PPC
Object Types General resource Operating resource Person Person type Rule
11.1.59
Model Type
Privileges diagram
Object Types Application system type Cluster/Data model Complex object type COT attribute Entity type ERM attribute Function Group IT function type Location Module type Organizational unit Person Person type Position Relationship type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
ARIS Methods
11-49
Model Type Privileges diagram
Object Types Technical term
11.1.60
Model Type
Process instantiation model

Object Types Instantiation cycle Instantiation interval Instantiation plan
Process instantiation model Process instantiation model Process instantiation model
11.1.61
Model Type
Process selection diagram

Object Types Function Main process Organizational unit
Process selection diagram Process selection diagram Process selection diagram
11.1.62
Model Type
Process selection matrix

Object Types Function Main process Organizational unit
Process selection matrix Process selection matrix Process selection matrix
ARIS Methods
11-50
11.1.63
Model Type
Product allocation diagram

Object Types Class Cluster/Data model Distribution channel Documented knowledge Entity type Function Group Information carrier Knowledge category Marketing instrument Need Objective Organizational unit Organizational unit type Performance characteristic Person Person type Position Product/Service Relationship type Technical term
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
ARIS Methods
11-51
11.1.64
Model Type
Product selection matrix

Object Types Function Organizational unit Product/Service
Product selection matrix Product selection matrix Product selection matrix
11.1.65
Model Type Product tree
Product tree
Object Types Product/Service
11.1.66
Model Type
Product/Service exchange diagram

Object Types Application system type Event Function Group Location Material type Operating resource type Organizational unit Organizational unit type Packaging material type Person Person type
Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram
ARIS Methods
11-52
Model Type Product/Service exchange diagram Product/Service exchange diagram
Object Types Product/Service Technical operating supply type
11.1.67
Model Type
Product/Service exchange diagram (graphic)

Object Types Application system type Event
Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic)
Function Group Location
Material type Operating resource type Organizational unit Organizational unit type
Packaging material type Person
ARIS Methods
11-53
Model Type Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic)
Object Types Person type
Product/Service Technical operating supply type
11.1.68
Model Type
Product/Service tree
Object Types Function Objective Product/Service
Product/Service tree Product/Service tree Product/Service tree
11.1.69
Model Type
Product/Service tree (graphic)

Object Types Function Objective Product/Service
Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic)
11.1.70
Model Type
Program flow-chart (PF)

Object Types Event Function Loop start
Program flow-chart (PF) Program flow-chart (PF) Program flow-chart (PF)
ARIS Methods
11-54
Model Type Program flow-chart (PF)
Object Types Rule
11.1.71
Model Type
Program structure chart

Object Types Application system class Application system type Attribute Attribute type group Class Cluster/Data model DBMS type Entity type ERM attribute Event Field Function Graphical user interface type Group Hardware component Hardware component type Information carrier Information flow IT function class IT function type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
ARIS Methods
11-55
Model Type Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Object Types List Location Module class Module type Operating system Operating system type Organizational unit Organizational unit type Person Person type Position Programming language Relation Relationship type Rule Screen Table Technical term View View (physical)
ARIS Methods
11-56
11.1.72
Model Type Quick model
Quick model
Object Types Quick object
11.1.73
Model Type RAD RAD
RAD
Object Types Person type Screen
11.1.74
Model Type RAMS RAMS RAMS RAMS
RAMS
Object Types Entity type Function Main process Organizational unit
11.1.75
Model Type
Relations diagram
Object Types Attribute Cluster/Data model Domain Entity type ERM attribute
Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram
ARIS Methods
11-57
Model Type Relations diagram Relations diagram Relations diagram Relations diagram
Object Types ERM domain Relation Relationship type View
11.1.76
Model Type
Role diagram
Object Types Authorization condition Function Group Knowledge category Location Organizational unit Organizational unit type Person Person type Position Technical term
Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram Role diagram
11.1.77
Model Type
Rule diagram
Object Types Event Function Rule
Rule diagram Rule diagram Rule diagram
ARIS Methods
11-58
11.1.78
Model Type
SAP ALE filter model

Object Types Filter object type Function
SAP ALE filter model SAP ALE filter model
11.1.79
Model Type
SAP ALE function model

SAP ALE function model
11.1.80
Model Type
SAP ALE message flow model

Object Types Function Message flow
SAP ALE message flow model SAP ALE message flow model
11.1.81
Model Type
SAP ALE message type model

Object Types Message type
SAP ALE message type model
11.1.82
Model Type
SAP applications diagram

SAP applications diagram
ARIS Methods
11-59
11.1.83
Model Type SAP SERM SAP SERM SAP SERM SAP SERM SAP SERM
SAP SERM
Object Types Business object Cluster/Data model Entity type ERM attribute Generalization type
11.1.84
Model Type
Screen design
Object Types Attribute type group Bitmap Business object Button Class Cluster/Data model Combo box COT attribute Element type Entity type ERM attribute Function IT function type List control Package
Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design
ARIS Methods
11-60
Model Type Screen design Screen design Screen design Screen design Screen design Screen design Screen design Screen design
Object Types Parameter Radio button/Check box Relationship type Spin box Technical term Text Text box Tree control
11.1.85
Model Type
Screen diagram
Object Types Bitmap Column Complex object type COT attribute Entity type ERM attribute IT function type Layout Page Parameter Screen Screen table Section
Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram
ARIS Methods
11-61
Model Type Screen diagram Screen diagram
Object Types Separator Text
11.1.86
Model Type
Screen navigation
Object Types Bitmap Button Combo box Event List control Radio button/Check box Rule Screen Spin box Text Text box Tree control
Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation
11.1.87
Model Type
SeDaM model
Object Types Attribute type group Cluster/Data model Entity type ERM attribute
SeDaM model SeDaM model SeDaM model SeDaM model
ARIS Methods
11-62
Model Type SeDaM model
Object Types Generalization type
11.1.88
Model Type
Shift calendar
Object Types Break Shift Shift cycle Shift plan
Shift calendar Shift calendar Shift calendar Shift calendar
11.1.89
Model Type
Structuring model
Object Types Structural element
Structuring model
11.1.90
Model Type
System attribute domain

Object Types System attribute domain
System attribute domain
11.1.91
Model Type
System attributes
Object Types System attribute
System attributes
ARIS Methods
11-63
11.1.92
Model Type
Table diagram
Object Types Attribute Domain Domain (physical) Entity type ERM attribute Field Field (specimen) Index Memory location Relation Relationship type Table Tables (specimen) View View (physical)
Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram
11.1.93
Model Type
Technical resources
Object Types Group Location Operating resource Operating resource class Operating resource type
Technical resources Technical resources Technical resources Technical resources Technical resources
ARIS Methods
11-64
Model Type Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources
Object Types Organizational unit Person Position System organizational unit System organizational unit type Tech. operating supply class Technical operating supply Technical operating supply type Transport system Transport system class Transport system type Warehouse equipment Warehouse equipment class Warehouse equipment type
11.1.94
Model Type
Technical terms model

Object Types Class Cluster/Data model Entity type ERM attribute Package Relationship type Technical term
Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model
ARIS Methods
11-65
11.1.95
Model Type

Object Types Action Activity graph Application system type Argument Association Association class Class Classifier-in-state Constraint ERM attribute Event Exception Function Group Key performance indicator instance Note Object instance Organizational unit Package Parameter Partition Person Person type
UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram
ARIS Methods
11-66
Model Type UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram
Object Types Position Product/Service Rule Signal UML Model
11.1.96
Model Type
UML Class description diagram

Object Types Association class Class Constraint ERM attribute Function Note Object instance Parameter
UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram
11.1.97
Model Type
UML Class diagram

Object Types Action Activity graph Argument Association Association class
UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram
ARIS Methods
11-67
Model Type UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram
Object Types Association instance Association role Attribute link Class Classifier role Collaboration Collaboration instance set Constraint Data value Enumeration literal ERM attribute Exception Function Link object Note Object instance Package Parameter Reception Signal State machine Subsystem Subsystem instance UML Model Use case instance
ARIS Methods
11-68
11.1.98
Model Type
UML Collaboration diagram

Object Types Association class Association instance Association role Attribute link Class Classifier role Collaboration instance set Constraint ERM attribute Interaction instance set Link object Note Object instance
UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram
11.1.99
Model Type
UML Component diagram

Object Types Artifact Association Association class Class Component Constraint Data value
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
ARIS Methods
11-69
Model Type UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
Object Types Enumeration literal Exception Function Link object Note Object instance Package Reception Signal UML Model
11.1.100 UML Deployment diagram

Model Type UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram Object Types Association Association class Association instance Class Collaboration instance set Component Component instance Constraint ERM attribute Function Hardware component
ARIS Methods
11-70
Model Type UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Object Types Hardware component type Note Object instance Package Reception UML Model
11.1.101 UML Sequence diagram

Model Type UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram Object Types Action Association instance Association role Classifier role Collaboration instance set Constraint Data value Hardware component Interaction instance set Link object Note Object instance Subsystem instance Use case instance
ARIS Methods
11-71
11.1.102 UML Statechart diagram

Model Type UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram Object Types Action Argument Class Classifier-in-state Constraint ERM attribute Event Function Note Package Parameter Product/Service Rule Signal State machine UML Model
11.1.103 UML Use case diagram

Model Type UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram Object Types Activity graph Application system type Association Attribute link
ARIS Methods
11-72
Model Type UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
Object Types Class Constraint Data value ERM attribute Extension point Function Group Link object Note Object instance Organizational unit Package Parameter Person Person type Position Reception State machine Subsystem UML Model Use case instance
11.1.104 Value-added chain diagram

Model Type Object Types
ARIS Methods
11-73
Model Type Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram
Object Types Application system type Cluster/Data model Function Group Key performance indicator instance Objective Organizational unit Organizational unit type Package Product/Service Technical term
11.1.105 Y diagram
Model Type Y diagram Object Types Function
ARIS Methods
11.2 Model Types - Specific Connection Types
11-74

11.2.1
Model Type
Access diagram
Source Object Type Relationship Type (active) has output of has output of Relationship Type (passive) is output of is output of Target Object Type Attribute Class
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system type
has output of has output of has output of
is output of is output of is output of
Cluster/Data model Entity type ERM attribute
can be located at has output of has output of has output of
can be location of is output of is output of is output of
Location Relation Relationship type Technical term
has output of has output of
is output of is output of
View Attribute
ARIS Methods
11-75
Model Type
Source Object Type
Relationship Type (active)
Relationship Type (passive)
Target Object Type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type
uses has output of realizes
is used by is output of is realized by
Attribute type group Class Class
transmits data to uses has output of uses
receives data from is used by is output of is used by
Class Class Cluster/Data model Cluster/Data model
has output of uses has output of
is output of is used by is output of
Entity type Entity type ERM attribute
uses has output of supports
is used by is output of is supported by
ERM attribute Field Function
ARIS Methods
11-76
Model Type
Source Object Type
Target Object Type
Access diagram
can run on
can be platform for
Hardware component type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type
creates output to sends creates can be located at has output of has output of uses
is output medium for is sent from is created by can be location of is output of is output of is used by
Information carrier Information flow List Location
Relation Relationship type Relationship type
encompasses has output of has output of
belongs to is output of is output of
Screen Table Technical term
uses has output of
is used by is output of
Technical term View
ARIS Methods
11-77
Model Type
Source Object Type
Target Object Type
Application system type Attribute Attribute
has output of is input for is input for
is output of has input of has input of
View (physical) Application system class Application system type
Attribute Attribute Attribute Attribute
is input for is input for is input for is input for
has input of has input of has input of has input of
IT function class IT function type Module class Module type
Attribute Attribute Attribute
is under responsibility of is under responsibility of is under responsibility of
is responsible for is responsible for is responsible for has information about has input of has input of
Organizational unit Person Position
lies on is input for is input for
Information carrier Application system class Application system type
ARIS Methods
11-78
Model Type
Source Object Type
Target Object Type
Class Class Class
transmits data to uses lies on
receives data from is used has information about
Application system type Application system type Information carrier IT function class IT function type IT function type Module class
Class Class Class Class
is input for is input for uses is input for
has input of has input of is used has input of
Class Class Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
is input for uses is input for
has input of is used has input of
Module type Module type Application system class
is input for lies on is input for
has input of has information about has input of
Application system type Information carrier IT function class
ARIS Methods
11-79
Model Type
Source Object Type
Target Object Type
Cluster/Data model Cluster/Data model Cluster/Data model DBMS type DBMS type DBMS type
is input for is input for is input for
has input of has input of has input of
IT function type Module class Module type
can be platform of uses can run on
can run under is used by can be platform for
Application system type Cluster/Data model Hardware component type IT function type Module type
DBMS type DBMS type
can be platform of can be platform of
can run under can run under
Employee variable Employee variable Employee variable Employee variable
can be user is responsible for development of is technically responsible for may carry out
can be used by development is under responsibility of is under technical responsibility of may be carried out by
Class Class
Class
Class
ARIS Methods
11-80
Model Type
Source Object Type
Target Object Type
Employee variable Entity type Entity type
may not carry out is input for is input for
may not be carried out by has input of has input of
Class Application system class Application system type
Entity type Entity type Entity type Entity type
lies on is input for is input for is input for
has information about has input of has input of has input of
Information carrier IT function class IT function type Module class
Entity type ERM attribute ERM attribute
Module type Application system class Application system type
ERM attribute ERM attribute ERM attribute
has information about has input of has input of
Information carrier IT function class IT function type
ARIS Methods
11-81
Model Type
Source Object Type
Target Object Type
ERM attribute ERM attribute Field
Module class Module type Application system type
Field Field Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type Group Group
is input for is input for can be platform of can run on
has input of has input of can run under can be platform for
IT function type Module type Application system type Hardware component type IT function type
can be platform of can be platform of can be user is responsible for development of
can run under
can run under can be used by development is under responsibility of is under technical responsibility of
Module type Application system class Application system class Application system class
Group
is technically responsible for
ARIS Methods
11-82
Model Type
Source Object Type
Target Object Type
Group Group
can be user is responsible for development of
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner is accessed by
Application system type Application system type Application system type Attribute type group Attribute type group Class
Group
Group Group Group
accesses is owner of accesses
Group Group Group
can be user is owner of is responsible for development of
can be used by has owner development is under responsibility of is under technical responsibility of may be carried out by
Class Class Class
Group
Class
Group
may carry out
Class
ARIS Methods
11-83
Model Type
Source Object Type
Target Object Type
Group Group Group
may not carry out accesses is owner of
may not be carried out by is accessed by has owner
Class Cluster/Data model Cluster/Data model
Group Group Group Group
accesses is owner of accesses is responsible for development of
is accessed by has owner is accessed by development is under responsibility of is under technical responsibility of is used by
Entity type Entity type ERM attribute IT function type IT function type IT function type
Group
Group
is user
Group Group
can be used by development is under responsibility of
Module type Module type
ARIS Methods
11-84
Model Type
Source Object Type
Target Object Type
Access diagram
Group
is under technical responsibility of
Module type
Group Group Group Hardware component Hardware component Hardware component Information carrier Information carrier Information carrier Information flow Information flow Information flow
accesses is owner of accesses can be platform of can be platform of can be platform of provides input for provides input for provides input for is received from is received from is received from
is accessed by has owner is accessed by can run under
Relationship type Relationship type Technical term Application system type
can run under can run under gets input from gets input from gets input from receives
IT function type Module type Application system type IT function type Module type Application system type
receives receives
IT function type Module type
ARIS Methods
11-85
Model Type
Source Object Type
Target Object Type
IT function IT function IT function
uses uses uses
is used by is used by is used by
IT function IT function IT function class IT function class IT function class IT function class IT function class IT function class IT function class IT function class
uses uses has output of has output of
is used by is used by is output of is output of
Relationship type Technical term Attribute Class
can be located at has output of has output of
can be location of is output of is output of
Location Relation Relationship type
ARIS Methods
11-86
Model Type
Source Object Type
Target Object Type
IT function class IT function class IT function type
Technical term View Attribute
IT function type IT function type IT function type IT function type
uses has output of realizes uses
is used by is output of is realized by is used by
Attribute type group Class Class Class
IT function type IT function type IT function type
Cluster/Data model Cluster/Data model Entity type
uses has output of uses
is used by is output of is used by
ARIS Methods
11-87
Model Type
Source Object Type
Target Object Type
has output of supports can run on
is output of is supported by can be platform for
Field Function Hardware component type Information carrier Information flow
IT function type IT function type
creates output to sends
is output medium for is sent from
creates can be located at has output of
is created by can be location of is output of
List Location Relation
has output of uses encompasses
is output of is used by belongs to
Relationship type Relationship type Screen
has output of has output of
is output of is output of
Table Technical term
ARIS Methods
11-88
Model Type
Source Object Type
Target Object Type
uses has output of has output of
is used by is output of is output of
Technical term View View (physical)
Location Location Location Location
accesses is owner of accesses can be user
is accessed by has owner is accessed by can be used by
Attribute type group Attribute type group Class Class
Location Location
is owner of is responsible for development of
has owner development is under responsibility of is under technical responsibility of may be carried out by may not be carried out by
Class Class
Location
Class
Location Location
may carry out may not carry out
Class Class
ARIS Methods
11-89
Model Type
Source Object Type
Target Object Type
Location Location Location
is accessed by has owner is accessed by
is owner of accesses accesses is owner of
has owner is accessed by is accessed by has owner
Entity type ERM attribute Relationship type Relationship type
Location Module class Module class
accesses has output of has output of
is accessed by is output of is output of
Technical term Attribute Class
Module class Module class Module class
ARIS Methods
11-90
Model Type
Source Object Type
Target Object Type
can be located at has output of has output of
can be location of is output of is output of
Location Relation Relationship type
Module class Module class Module type Module type
has output of has output of has output of uses
is output of is output of is output of is used by
Technical term View Attribute Attribute type group
Module type Module type Module type
has output of realizes uses
is output of is realized by is used by
Class Class Class
ARIS Methods
11-91
Model Type
Source Object Type
Target Object Type
creates can be located at has output of
is created by can be location of is output of
List Location Relation
has output of uses
is output of is used by
Relationship type Relationship type
ARIS Methods
11-92
Model Type
Source Object Type
Target Object Type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Module type Module type Module type Operating system type Operating system type
uses has output of has output of can be platform of can run on
is used by is output of is output of can run under
Technical term View View (physical) Application system type
can be platform for
Access diagram Access diagram Access diagram Access diagram
Operating system type Operating system type Organizational unit Organizational unit
can be platform of can be platform of can be user
can run under can run under can be used by
IT function type Module type Application system class
is responsible for development of
development is under responsibility of
Application system class
ARIS Methods
11-93
Model Type
Source Object Type
Target Object Type
Access diagram
Organizational unit
Access diagram Access diagram Access diagram
Organizational unit Organizational unit Organizational unit
can be user is responsible for development of is technically responsible for
can be used by development is under responsibility of is under technical responsibility of
Application system type Application system type Application system type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
accesses accesses is owner of
is accessed by is accessed by has owner
Attribute Attribute type group Attribute type group
accesses can be user is owner of
is accessed by can be used by has owner
Class Class Class
Class
ARIS Methods
11-94
Model Type
Source Object Type
Target Object Type
Access diagram
Organizational unit
Class
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
may carry out may not carry out accesses is owner of
may be carried out by may not be carried out by is accessed by has owner
can be user is responsible for development of is technically responsible for accesses is owner of
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner
DBMS type DBMS type
DBMS type
Entity type Entity type
accesses can be user
is accessed by can be used by
ERM attribute IT function class
ARIS Methods
11-95
Model Type
Source Object Type
Target Object Type
Access diagram
Organizational unit
development is under responsibility of is under technical responsibility of
IT function class
Access diagram
Organizational unit
IT function class
Access diagram Access diagram
Organizational unit Organizational unit
Access diagram
Organizational unit
IT function type
Access diagram Access diagram Access diagram Access diagram Access diagram
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
can be user is responsible for development of is technically responsible for can be user is responsible for development of
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of
Module class Module class
Module class
ARIS Methods
11-96
Model Type
Source Object Type
Target Object Type
Access diagram
Organizational unit
Module type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type
uses accesses accesses is owner of
is used by is accessed by is accessed by has owner
Programming language Relation Relationship type Relationship type
accesses accesses can be user
is accessed by is accessed by can be used by
Technical term View Application system type
Access diagram
Organizational unit type
Access diagram
accesses
is accessed by
Attribute
ARIS Methods
11-97
Model Type
Source Object Type
Target Object Type
Access diagram
can be responsible for
can be under responsibility of
Attribute
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
is owner of is responsible for development of is technically responsible for may carry out may not carry out accesses is owner of
has owner development is under responsibility of is under technical responsibility of may be carried out by may not be carried out by is accessed by has owner
Class Class
Class
Class Class
Cluster/Data model Cluster/Data model
ARIS Methods
11-98
Model Type
Source Object Type
Target Object Type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
accesses is owner of can be user
is accessed by has owner can be used by
Entity type Entity type IT function type
is responsible for development of is technically responsible for can be user
development is under responsibility of is under technical responsibility of can be used by
IT function type IT function type Module type
Module type
Access diagram
Module type
Organizational unit type Organizational unit type Organizational unit type
accesses can be responsible for accesses
is accessed by can be under responsibility of is accessed by
Relation Relation
Relationship type
ARIS Methods
11-99
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Person Person
is owner of accesses can be responsible for can be user is responsible for development of
has owner is accessed by can be under responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
Relationship type View View
Application system class Application system class Application system class Application system type
Person
Person
can be user
Person
Access diagram
Person
Person Person
accesses accesses
is accessed by is accessed by
Attribute Attribute type group
ARIS Methods
11-100
Model Type
Source Object Type
Target Object Type
Person Person Person
is owner of accesses can be user
has owner is accessed by can be used by
Person Person
has owner development is under responsibility of is under technical responsibility of
Class Class
Access diagram
Person
Class
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
may carry out may not carry out accesses
may be carried out by may not be carried out by is accessed by
Class Class Cluster/Data model
is owner of can be user is responsible for development of
has owner can be used by development is under responsibility of
Cluster/Data model DBMS type DBMS type
ARIS Methods
11-101
Model Type
Source Object Type
Target Object Type
Access diagram
Person
DBMS type
Person Person Person Person
Entity type Entity type ERM attribute IT function class
Person
IT function class
Access diagram
Person
IT function class
Person Person
can be used by development is under responsibility of is under technical responsibility of can be used by
IT function type IT function type IT function type Module class
Person
Person
can be user
ARIS Methods
11-102
Model Type
Source Object Type
Target Object Type
Access diagram
Person
Module class
Access diagram
Person
Module class
Person Person
Access diagram
Person
Module type
uses accesses accesses
is used by is accessed by is accessed by
Programming language Relation Relationship type
is owner of accesses accesses
has owner is accessed by is accessed by
Relationship type Technical term View
ARIS Methods
11-103
Model Type
Source Object Type
Target Object Type
Person type Person type
can be used by development is under responsibility of is under technical responsibility of is accessed by can be under responsibility of is accessed by has owner
Application system type Application system type Application system type Attribute Attribute
Person type
accesses can be responsible for
accesses is owner of
Attribute type group Attribute type group
Person type Person type Person type
Class Class Class
Person type
Class
ARIS Methods
11-104
Model Type
Source Object Type
Target Object Type
Access diagram
Person type
Class
Person type Person type Person type Person type
Person type
IT function type
Access diagram
Person type
IT function type
Access diagram
Person type
can be user
can be used by
Module type
ARIS Methods
11-105
Model Type
Source Object Type
Target Object Type
Access diagram
Person type
Module type
Access diagram
Person type
Module type
accesses can be responsible for
is accessed by can be under responsibility of
Relation Relation
Relationship type Relationship type View
Person type
View
Position Position
Application system class Application system class Application system class
Position
ARIS Methods
11-106
Model Type
Source Object Type
Target Object Type
Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram Access diagram
Position Position
can be used by development is under responsibility of is under technical responsibility of is accessed by is accessed by has owner
Application system type Application system type Application system type Attribute Attribute type group Attribute type group
Position
Position Position Position
Class Class Class
Position
Class
Access diagram
Position
Class
ARIS Methods
11-107
Model Type
Source Object Type
Target Object Type
has owner can be used by development is under responsibility of is under technical responsibility of is accessed by has owner
Position
DBMS type
Position Position
accesses can be user is responsible for development of
is accessed by can be used by development is under responsibility of
ERM attribute IT function class IT function class
ARIS Methods
11-108
Model Type
Source Object Type
Target Object Type
Access diagram
Position
IT function class
Position Position
Position
Position Position
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of
Position
Module class
Position Position
Position
Module type
ARIS Methods
11-109
Model Type
Source Object Type
Target Object Type
Relation Relationship type Relationship type
Position Position Programming language Programming language Programming language Relation Relation
accesses accesses is programming language of is programming language of is programming language of is input for is input for
is accessed by is accessed by is developed with is developed with is developed with has input of has input of
Technical term View Application system type IT function type Module type
Application system class Application system type
Relation Relation
is input for is input for
has input of has input of
IT function class IT function type
ARIS Methods
11-110
Model Type
Source Object Type
Target Object Type
Relation Relation Relation
is input for is input for is under responsibility of
has input of has input of is responsible for is responsible for is responsible for has input of has input of
Module class Module type Organizational unit Person Position Application system class Application system type
Relation Relation Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Table
is under responsibility of is under responsibility of is input for is input for
Module class Module type Application system type
ARIS Methods
11-111
Model Type
Source Object Type
Target Object Type
Table Table Technical term
Technical term Technical term Technical term Technical term
is input for lies on is input for is input for
has input of has information about has input of has input of
Application system type Information carrier IT function class IT function type
Technical term Technical term View
Module class Module type Application system class
View View View
Application system type IT function class IT function type
ARIS Methods
11-112
Model Type
Source Object Type
Target Object Type
View View View
has input of has input of is responsible for is responsible for is responsible for has input of has input of
Module class Module type Organizational unit Person Position Application system type IT function type
View View View (physical) View (physical)
is under responsibility of is under responsibility of is input for is input for
View (physical)
is input for
has input of
Program module type
ARIS Methods
11.2.2 Access diagram (physical)
11-113

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Application system uses is used by Cluster/Data model Application system has output of is output of Cluster/Data model Application system uses is used by Class Application system transmits data to receives data from Class Application system realizes is realized by Class Application system has output of is output of Class Application system uses is used by Attribute type group Application system has output of is output of Attribute Target Object Type
ARIS Methods
11-114
Model Type
Source Object Type
Target Object Type
Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical) Access diagram (physical)
Application system
has output of
is output of
Entity type
Application system
uses
is used by
Entity type
Application system Application system Application system Application system Application system Application system Application system
has output of
is output of
ERM attribute
uses
is used by
ERM attribute
has output of
is output of
Field
has output of
is output of
Field (specimen)
supports
is supported by
Function
Information carrier Information flow
ARIS Methods
11-115
Model Type
Source Object Type
Target Object Type
Application system
creates
is created by
List
Application system
is located at
is location of
Location
Application system Application system Application system Application system Application system Application system Application system
has output of
is output of
Relation
has output of
is output of
Relationship type
uses
is used by
Relationship type
encompasses
belongs to
Screen
has output of
is output of
Table
has output of
is output of
Tables (specimen)
has output of
is output of
Technical term
ARIS Methods
11-116
Model Type
Source Object Type
Target Object Type
Application system
uses
is used by
Technical term
Application system
has output of
is output of
View
Application system Application system class Application system class Application system class Application system type Application system type Application system type
has output of
is output of
View (physical)
has output of
is output of
Field
has output of
is output of
Table
has output of
is output of
View (physical)
uses
is used by
Attribute type group
transmits data to uses
receives data from is used by
Class
Class
ARIS Methods
11-117
Model Type
Source Object Type
Target Object Type
uses
is used by
Cluster/Data model
uses
is used by
Entity type
Application system type Application system type Application system type Application system type Application system type Application system type Application system type
uses
is used by
ERM attribute
has output of
is output of
Field
creates output to uses
is output medium for is used by
Information carrier Relationship type
has output of
is output of
Table
uses
is used by
Technical term
has output of
is output of
View (physical)
ARIS Methods
11-118
Model Type
Source Object Type
Target Object Type
Attribute
is input for
has input of
Application system
Attribute
is stored on
stores
Hardware component
Attribute
is input for
has input of
IT function
Attribute
is input for
has input of
Module
Attribute
is input for
has input of
Program module type
Attribute type group Class
lies on
has information about
Information carrier Application system
is input for
has input of
Class
transmits data to
receives data from is used
Application system Application system
Class
uses
ARIS Methods
11-119
Model Type
Source Object Type
Target Object Type
Class
transmits data to
receives data from
Class
is stored on
stores
Hardware component
Class
lies on
Information carrier IT function
Class
is input for
has input of
Class
uses
is used
IT function
Class
is input for
has input of
Module
Class
uses
is used
Module
Class
is input for
has input of
Program module type
Cluster/Data model
is input for
has input of
Application system
ARIS Methods
11-120
Model Type
Source Object Type
Target Object Type
Cluster/Data model
is stored on
stores
Hardware component
Cluster/Data model
lies on
Information carrier
Cluster/Data model Cluster/Data model Cluster/Data model DBMS
is input for
has input of
IT function
is input for
has input of
Module
is input for
has input of
Program module type
is platform of
runs under
Application system
DBMS
uses
is used by
Cluster/Data model
DBMS
runs with
is platform for
Hardware component
Entity type
is input for
has input of
Application system
ARIS Methods
11-121
Model Type
Source Object Type
Target Object Type
Entity type
is stored on
stores
Hardware component
Entity type
lies on
Information carrier
Entity type
is input for
has input of
IT function
Entity type
is input for
has input of
Module
Entity type
is input for
has input of
Program module type
ERM attribute
is input for
has input of
Application system
ERM attribute
is stored on
stores
Hardware component
ERM attribute
lies on
ERM attribute
is input for
has input of
ARIS Methods
11-122
Model Type
Source Object Type
Target Object Type
ERM attribute
is input for
has input of
Module
ERM attribute
is input for
has input of
Program module type
Field
is input for
has input of
Application system
Field
is input for
has input of
Field
is input for
has input of
Field
is stored on
stores
Hardware component
Field
is input for
has input of
IT function
Field
is input for
has input of
IT function class
Field
is input for
has input of
IT function type
ARIS Methods
11-123
Model Type
Source Object Type
Target Object Type
Field
is input for
has input of
Module
Field
is input for
has input of
Module class
Field
is input for
has input of
Module type
Field
is input for
has input of
Program module type
Field (specimen) Field (specimen) Field (specimen) Field (specimen) Field (specimen)
is input for
has input of
Application system
is stored on
stores
Hardware component
is input for
has input of
IT function
is input for
has input of
Module
is input for
has input of
Program module
ARIS Methods
11-124
Model Type
Source Object Type
Target Object Type
Group
accesses
is accessed by
Group
is owner of
has owner
Group
accesses
is accessed by
Class
Group
is owner of
has owner
Class
Group
accesses
is accessed by
Cluster/Data model
Group
is owner of
has owner
Cluster/Data model
Group
accesses
is accessed by
Entity type
Group
is owner of
has owner
Entity type
Group
accesses
is accessed by
ERM attribute
ARIS Methods
11-125
Model Type
Source Object Type
Target Object Type
Group
IT function
Group
IT function
Group
development is under responsibility of is under technical responsibility of is accessed by
Module
Group
Module
Group
accesses
Relationship type
Group
is owner of
has owner
Relationship type
Group
accesses
is accessed by
Technical term
Hardware component Hardware component
is platform of
runs under
Application system
can be platform of
can run under
ARIS Methods
11-126
Model Type
Source Object Type
Target Object Type
Hardware component
is platform of
runs under
IT function
Hardware component
can be platform of
can run under
IT function type
Hardware component Hardware component Hardware component Information carrier Information carrier Information carrier Information carrier
is platform of
runs under
Module
can be platform of is platform of
can run under
Module type
runs under
Program module
provides input for provides input for provides input for provides input for
gets input from gets input from gets input from gets input from
Application system Application system type IT function
IT function type
ARIS Methods
11-127
Model Type
Source Object Type
Target Object Type
Information carrier
provides input for
gets input from
Module
Information carrier
provides input for
gets input from
Module type
Information flow Information flow Information flow Information flow IT function
is received from is received from is received from is received from has output of
receives
Application system
receives
IT function
receives
Module
receives
Program module type
is output of
Attribute
IT function
uses
is used by
IT function
has output of
is output of
Class
ARIS Methods
11-128
Model Type
Source Object Type
Target Object Type
IT function
realizes
is realized by
Class
IT function
uses
is used by
Class
IT function
has output of
is output of
Cluster/Data model
IT function
uses
is used by
Cluster/Data model
IT function
has output of
is output of
Entity type
IT function
uses
is used by
Entity type
IT function
has output of
is output of
ERM attribute
IT function
uses
is used by
ERM attribute
IT function
has output of
is output of
Field
ARIS Methods
11-129
Model Type
Source Object Type
Target Object Type
IT function
has output of
is output of
Field (specimen)
IT function
supports
is supported by
Function
IT function
creates output to
IT function
sends
IT function
creates
is created by
List
IT function
is located at
is location of
Location
IT function
has output of
is output of
Relation
IT function
has output of
is output of
Relationship type
IT function
uses
is used by
Relationship type
ARIS Methods
11-130
Model Type
Source Object Type
Target Object Type
IT function
encompasses
belongs to
Screen
IT function
has output of
is output of
Table
IT function
has output of
is output of
Tables (specimen)
IT function
has output of
is output of
Technical term
IT function
uses
is used by
Technical term
IT function
has output of
is output of
View
IT function
has output of
is output of
View (physical)
IT function class IT function class
has output of
is output of
Field
has output of
is output of
Table
ARIS Methods
11-131
Model Type
Source Object Type
Target Object Type
IT function class
has output of
is output of
View (physical)
IT function type
uses
is used by
IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses
is used by
Class
uses
is used by
Cluster/Data model
uses
is used by
Entity type
uses
is used by
ERM attribute
has output of
is output of
Field
creates output to is located at
is output medium for is location of
Information carrier Location
ARIS Methods
11-132
Model Type
Source Object Type
Target Object Type
IT function type
uses
is used by
Relationship type
IT function type
has output of
is output of
Table
IT function type IT function type Location
uses
is used by
Technical term
has output of
is output of
View (physical)
accesses
is accessed by
Location
is owner of
has owner
Location
accesses
is accessed by
Class
Location
is owner of
has owner
Class
Location
accesses
is accessed by
Cluster/Data model
ARIS Methods
11-133
Model Type
Source Object Type
Target Object Type
Location
is owner of
has owner
Cluster/Data model
Location
accesses
is accessed by
Entity type
Location
is owner of
has owner
Entity type
Location
accesses
is accessed by
ERM attribute
Location
accesses
is accessed by
Relationship type
Location
is owner of
has owner
Relationship type
Location
accesses
is accessed by
Technical term
Module
has output of
is output of
Attribute
Module
uses
is used by
ARIS Methods
11-134
Model Type
Source Object Type
Target Object Type
Module
has output of
is output of
Class
Module
realizes
is realized by
Class
Module
uses
is used by
Class
Module
has output of
is output of
Cluster/Data model
Module
uses
is used by
Cluster/Data model
Module
has output of
is output of
Entity type
Module
uses
is used by
Entity type
Module
has output of
is output of
ERM attribute
Module
uses
is used by
ERM attribute
ARIS Methods
11-135
Model Type
Source Object Type
Target Object Type
Module
has output of
is output of
Field
Module
has output of
is output of
Field (specimen)
Module
supports
is supported by
Function
Module
creates output to
Module
sends
Module
creates
is created by
List
Module
is located at
is location of
Location
Module
has output of
is output of
Relation
Module
has output of
is output of
Relationship type
ARIS Methods
11-136
Model Type
Source Object Type
Target Object Type
Module
uses
is used by
Relationship type
Module
encompasses
belongs to
Screen
Module
has output of
is output of
Table
Module
has output of
is output of
Tables (specimen)
Module
has output of
is output of
Technical term
Module
uses
is used by
Technical term
Module
has output of
is output of
View
Module
has output of
is output of
View (physical)
Module class
has output of
is output of
Field
ARIS Methods
11-137
Model Type
Source Object Type
Target Object Type
Module class
has output of
is output of
Table
Module class
has output of
is output of
View (physical)
Module type
uses
is used by
Module type
uses
is used by
Class
Module type
uses
is used by
Cluster/Data model
Module type
uses
is used by
Entity type
Module type
uses
is used by
ERM attribute
Module type
has output of
is output of
Field
Module type
creates output to
is output medium for
Information carrier
ARIS Methods
11-138
Model Type
Source Object Type
Target Object Type
Module type
uses
is used by
Relationship type
Module type
has output of
is output of
Table
Module type
uses
is used by
Technical term
Module type
has output of
is output of
View (physical)
is responsible for development of is technically responsible for is user
development is under responsibility of is under technical responsibility of has user
Application system Application system Application system
accesses
is accessed by
is owner of
has owner
ARIS Methods
11-139
Model Type
Source Object Type
Target Object Type
Organizational unit
accesses
is accessed by
Class
Organizational unit
is owner of
has owner
Class
accesses
is accessed by
Cluster/Data model
is owner of
has owner
Cluster/Data model
is IT responsible for accesses
is under IT responsibility of is accessed by
DBMS
Entity type
is owner of
has owner
Entity type
accesses
is accessed by
ERM attribute
accesses
is accessed by
Field
ARIS Methods
11-140
Model Type
Source Object Type
Target Object Type
Organizational unit
is responsible for
is under responsibility of
Field
Organizational unit
accesses
is accessed by
Field (specimen)
is responsible for is user
is under responsibility of has user
Field (specimen) IT function
is user
has user
Module
accesses
is accessed by
Relationship type
is owner of
has owner
Relationship type
accesses
is accessed by
Table
is responsible for
Table
ARIS Methods
11-141
Model Type
Source Object Type
Target Object Type
Organizational unit
accesses
is accessed by
Tables (specimen)
Organizational unit
is responsible for
Tables (specimen)
Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type
accesses
is accessed by
Technical term
accesses
is accessed by
View (physical)
is responsible for can be user
is under responsibility of can be used by
View (physical)
Application system
is responsible for development of is technically responsible for accesses
Application system Application system Attribute type group
ARIS Methods
11-142
Model Type
Source Object Type
Target Object Type
is owner of
has owner
accesses
is accessed by
Class
is owner of
has owner
Class
accesses
is accessed by
Cluster/Data model
is owner of
has owner
Cluster/Data model
accesses
is accessed by
Entity type
is owner of
has owner
Entity type
accesses
is accessed by
Field
Field
ARIS Methods
11-143
Model Type
Source Object Type
Target Object Type
accesses
is accessed by
Relationship type
is owner of
has owner
Relationship type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Person
accesses
is accessed by
Table
can be responsible for accesses
can be under responsibility of is accessed by
Table
View (physical)
can be responsible for is responsible for development of
can be under responsibility of development is under responsibility of is under technical responsibility of has user
View (physical)
Person
Person
is user
ARIS Methods
11-144
Model Type
Source Object Type
Target Object Type
Person
accesses
is accessed by
Person
is owner of
has owner
Person
accesses
is accessed by
Class
Person
is owner of
has owner
Class
Person
accesses
is accessed by
Cluster/Data model
Person
is owner of
has owner
Cluster/Data model
Person
is IT responsible for
is under IT responsibility of is accessed by
DBMS
Person
accesses
Entity type
Person
is owner of
has owner
Entity type
ARIS Methods
11-145
Model Type
Source Object Type
Target Object Type
Person
accesses
is accessed by
ERM attribute
Person
accesses
is accessed by
Field
Person
is responsible for
is under responsibility of is accessed by
Field
Person
accesses
Field (specimen)
Person
is responsible for
Person
is user
Person
is user
has user
Module
Person
accesses
is accessed by
Relationship type
Person
is owner of
has owner
Relationship type
ARIS Methods
11-146
Model Type
Source Object Type
Target Object Type
Person
accesses
is accessed by
Table
Person
is responsible for
Table
Person
accesses
is accessed by
Tables (specimen)
Person
is responsible for
Tables (specimen) Technical term
Person
accesses
Person
accesses
is accessed by
View (physical)
Person
is responsible for
is under responsibility of can be used by
View (physical)
Person type
can be user
Application system
Person type
Application system
ARIS Methods
11-147
Model Type
Source Object Type
Target Object Type
Person type
Application system
Person type
accesses
is accessed by
Person type
is owner of
has owner
Person type
accesses
is accessed by
Class
Person type
is owner of
has owner
Class
Person type
accesses
is accessed by
Cluster/Data model
Person type
is owner of
has owner
Cluster/Data model
Person type
accesses
is accessed by
Entity type
Person type
is owner of
has owner
Entity type
ARIS Methods
11-148
Model Type
Source Object Type
Target Object Type
Person type
accesses
is accessed by
Field
Person type
Field
Person type
accesses
is accessed by
Relationship type
Person type
is owner of
has owner
Relationship type
Person type
accesses
is accessed by
Table
Person type
Table
Person type
accesses
View (physical)
Person type
can be under responsibility of development is under responsibility of
View (physical)
Position
Application system
ARIS Methods
11-149
Model Type
Source Object Type
Target Object Type
Position
Application system
Position
is user
has user
Application system
Position
accesses
is accessed by
Position
is owner of
has owner
Position
accesses
is accessed by
Class
Position
is owner of
has owner
Class
Position
accesses
is accessed by
Cluster/Data model
Position
is owner of
has owner
Cluster/Data model
Position
is under IT responsibility of
DBMS
ARIS Methods
11-150
Model Type
Source Object Type
Target Object Type
Position
accesses
is accessed by
Entity type
Position
is owner of
has owner
Entity type
Position
accesses
is accessed by
ERM attribute
Position
accesses
is accessed by
Field
Position
is responsible for
Field
Position
accesses
Field (specimen)
Position
is responsible for
Position
is user
Position
is user
has user
Module
ARIS Methods
11-151
Model Type
Source Object Type
Target Object Type
Position
accesses
is accessed by
Relationship type
Position
is owner of
has owner
Relationship type
Position
accesses
is accessed by
Table
Position
is responsible for
Table
Position
accesses
Tables (specimen)
Position
is responsible for
Tables (specimen) Technical term
Position
accesses
Position
accesses
is accessed by
View (physical)
Position
is responsible for
View (physical)
ARIS Methods
11-152
Model Type
Source Object Type
Target Object Type
Program module
has output of
is output of
Field (specimen)
Program module
has output of
is output of
Tables (specimen)
Program module type Program module type Program module type Program module type Program module type Program module type Program module type
has output of
is output of
Attribute
has output of
is output of
Class
has output of
is output of
Cluster/Data model
has output of
is output of
Entity type
has output of
is output of
ERM attribute
has output of
is output of
Field
sends
is sent from
Information flow
ARIS Methods
11-153
Model Type
Source Object Type
Target Object Type
Program module type
has output of
is output of
Relation
Program module type
has output of
is output of
Relationship type
Program module type Program module type Program module type Program module type Relation
has output of
is output of
Table
has output of
is output of
Technical term
has output of
is output of
View
has output of
is output of
View (physical)
is input for
has input of
Application system
Relation
is stored on
stores
Hardware component
Relation
is input for
has input of
IT function
ARIS Methods
11-154
Model Type
Source Object Type
Target Object Type
Relation
is input for
has input of
Module
Relation
is input for
has input of
Program module type
Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Table
is input for
has input of
Application system
is stored on
stores
Hardware component
lies on
is input for
has input of
is input for
has input of
Module
is input for
has input of
Program module type
is input for
has input of
Application system
ARIS Methods
11-155
Model Type
Source Object Type
Target Object Type
Table
is input for
has input of
Table
is input for
has input of
Table
is stored on
stores
Hardware component
Table
is input for
has input of
IT function
Table
is input for
has input of
IT function class
Table
is input for
has input of
IT function type
Table
is input for
has input of
Module
Table
is input for
has input of
Module class
Table
is input for
has input of
Module type
ARIS Methods
11-156
Model Type
Source Object Type
Target Object Type
Table
is input for
has input of
Program module type
Tables (specimen)
is input for
has input of
Application system
Tables (specimen) Tables (specimen) Tables (specimen) Tables (specimen) Technical term
is stored on
stores
Hardware component
is input for
has input of
IT function
is input for
has input of
Module
is input for
has input of
Program module
is input for
has input of
Application system
Technical term
is stored on
stores
Hardware component
Technical term
lies on
Information carrier
ARIS Methods
11-157
Model Type
Source Object Type
Target Object Type
Technical term
is input for
has input of
IT function
Technical term
is input for
has input of
Module
Technical term
is input for
has input of
Program module type
View
is input for
has input of
Application system
View
is stored on
stores
Hardware component
View
is input for
has input of
IT function
View
is input for
has input of
Module
View
is input for
has input of
Program module type
View
relates to
has
Table
ARIS Methods
11-158
Model Type
Source Object Type
Target Object Type
View (physical)
is input for
has input of
Application system
View (physical)
is input for
has input of
View (physical)
is input for
has input of
View (physical)
is stored on
stores
Hardware component
View (physical)
is input for
has input of
IT function
View (physical)
is input for
has input of
IT function class
View (physical)
is input for
has input of
IT function type
View (physical)
is input for
has input of
Module
View (physical)
is input for
has input of
Module class
ARIS Methods
11-159
Model Type
Source Object Type
Target Object Type
Access diagram (physical)
View (physical)
is input for
has input of
Program module type
ARIS Methods
11.2.3 Application system diagram
11-160

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system encompasses belongs to Screen Application system encompasses belongs to Module Application system creates is created by List Application system encompasses belongs to IT function Application system supports is supported by Function Application system is of type determines type of Application system type Application system is predecessor of is successor of Application system Application system encompasses belongs to Application system Target Object Type
ARIS Methods
11-161
Model Type
Source Object Type
Target Object Type
Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram Application system diagram
Application system
uses
is used by
Screen
DBMS
is of type
determines type of
DBMS type
DBMS type
is platform of
runs under
Application system
DBMS type
is platform of
runs under
IT function
DBMS type
is platform of
runs under
Module
DBMS type
is platform of
runs under
Program module
Graphical user interface type Graphical user interface type Graphical user interface type
is user interface is user interface is user interface
runs under
Application system
runs under
IT function
runs under
Module
ARIS Methods
11-162
Model Type
Source Object Type
Target Object Type
Graphical user interface type
is user interface
runs under
Program module
IT function
supports
is supported by
Function
IT function
encompasses
belongs to
IT function
IT function
is predecessor of
is successor of
IT function
IT function
is of type
determines type of
IT function type List
IT function
creates
is created by
IT function
encompasses
belongs to
Screen
IT function
uses
is used by
Screen
Module
supports
is supported by
Function
ARIS Methods
11-163
Model Type
Source Object Type
Target Object Type
Module
encompasses
belongs to
IT function
Module
creates
is created by
List
Module
encompasses
belongs to
Module
Module
is predecessor of
is successor of
Module
Module
is of type
determines type of
Module type
Module
encompasses
belongs to
Screen
Module
uses
is used by
Screen
Operating system type Operating system type
is platform of
runs under
Application system
is platform of
runs under
IT function
ARIS Methods
11-164
Model Type
Source Object Type
Target Object Type
Operating system type
is platform of
runs under
Module
is platform of
runs under
Program module
Program library Program module Program module Program module type Program module type Program module type Program module type
encompasses
belongs to
Program library
encompasses
belongs to
Program module
is of type
determines type of
Program module type Application system type IT function type Module type
implements
is implemented by
implements
is implemented by
implements
is implemented by
accesses
has access by
Program library
ARIS Methods
11.2.4 Application system type diagram
11-165
Model Type
Source Object Type
Target Object Type
Application system diagram Application system diagram Application system diagram Application system diagram
Program module type
can encompass
can belong to
Program module type
Programming language
is programming language of
is developed with
Application system
Programming language Programming language
is programming language of is programming language of
is developed with is developed with
IT function
Module

Model Type Source Object Type Application system type diagram Application system type diagram Application system type diagram Application system class can encompass can belong to IT function class Application system class can support can be supported by Function Application system class Relationship Type (active) encompasses Relationship Type (passive) belongs to Application system class Target Object Type
ARIS Methods
11-166
Model Type
Source Object Type
Target Object Type
Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram Application system type diagram
encompasses
belongs to
Module class
supports
is supported by using
Objective
belongs to class encompasses
encompasses
belongs to
is predecessor of supports
is successor of
is supported by
Function
encompasses
belongs to
IT function type
creates
is created by
List
encompasses
belongs to
Module type
ARIS Methods
11-167
Model Type
Source Object Type
Target Object Type
supports
Objective
encompasses
belongs to
Screen
Application system type DBMS type
uses
is used by
Screen
can be platform of
can run under
DBMS type
is predecessor of
is successor of
DBMS type
DBMS type
can be platform of
can run under
IT function type
DBMS type
can be platform of
can run under
Module type
DBMS type
can run under
can be platform of
Operating system type Draft list
Function
can create
can be created by
ARIS Methods
11-168
Model Type
Source Object Type
Target Object Type
Function
can use
can be used by
Draft list
Function
creates
is created by
List
Function
uses
is used by
List
Function
is represented by
represents
Screen
Function
can use
can be used by
Screen design
Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type
can be platform of is predecessor of can be platform of can be platform of
can run under
is successor of
Graphical user interface type
can run under
IT function type
can run under
Module type
ARIS Methods
11-169
Model Type
Source Object Type
Target Object Type
IT function class
supports
is supported by
Function
IT function class
encompasses
belongs to
IT function class
IT function class IT function type IT function type IT function type IT function type IT function type IT function type
supports
Objective
supports
is supported by
Function
belongs to class encompasses
encompasses
IT function class
belongs to
IT function type
is predecessor of creates
is successor of
IT function type
is created by
List
supports
Objective
ARIS Methods
11-170
Model Type
Source Object Type
Target Object Type
IT function type
encompasses
belongs to
Screen
IT function type
uses
is used by
Screen
List
implements
is implemented by
Draft list
Module class
supports
is supported by
Function
Module class
encompasses
belongs to
IT function class
Module class
encompasses
belongs to
Module class
Module class
supports
Objective
Module type
supports
is supported by
Function
Module type
encompasses
belongs to
IT function type
ARIS Methods
11-171
Model Type
Source Object Type
Target Object Type
Module type
creates
is created by
List
Module type
belongs to class
encompasses
Module class
Module type
encompasses
belongs to
Module type
Module type
is predecessor of
is successor of
Module type
Module type
supports
Objective
Module type
encompasses
belongs to
Screen
Module type
uses
is used by
Screen
Operating system type Operating system type
can be platform of can be platform of
can run under
can run under
IT function type
ARIS Methods
11-172
Model Type
Source Object Type
Target Object Type
can be platform of
can run under
Module type
is predecessor of
is successor of
Package
designs
is designed by
Package
designs
is designed by
IT function type
Package
designs
is designed by
Module type
Program module type Program module type Program module type Programming language
implements
is implemented by
Application system type IT function type Module type
implements
is implemented by
implements
is implemented by
is developed with
ARIS Methods
11.2.5 Attribute allocation diagram
11-173
Model Type
Source Object Type
Target Object Type
Application system type diagram Application system type diagram Application system type diagram Application system type diagram
is developed with
IT function type
is developed with
Module type
Programming language Screen
is predecessor of implements
is successor of
is implemented by
Screen design
11.2.5 Attribute allocation diagram

Model Type Source Object Type Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram Attribute Attribute Attribute is describing for is foreign key for is primary key for has foreign key has primary key Relation Relation is described by Relation Attribute depicts is depicted by ERM attribute Attribute Relationship Type (active) has Relationship Type (passive) is assigned to Domain Target Object Type
ARIS Methods
11.2.6 Authorization hierarchy
11-174
Model Type
Source Object Type
Target Object Type
Attribute allocation diagram
Attribute
depicts
is depicted by
Relationship type
Assignment Relationship
Source Object Type
Target Object Type
Attribute allocation diagram Attribute allocation diagram Attribute allocation diagram
is describing for is foreign key for is primary key for
is described by has foreign key has primary key
11.2.6 Authorization hierarchy

Model Type Source Object Type Authorization hierarchy Authorization hierarchy Authorization condition Authorization condition is generalization of is specialization of Relationship Type (active) encompasses Relationship Type (passive) belongs to Authorization condition Authorization condition Target Object Type
ARIS Methods
11.2.7 Authorization map
11-175
11.2.7 Authorization map

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Authorization map Person type Person type has knowledge of requires is required by is available at Person Organizational unit Organizational unit Organizational unit type Organizational unit type Person has knowledge of requires is required by is available at has knowledge of requires is required by is available at has knowledge of requires is required by is available at Location Location has knowledge of requires is required by is available at Group Group has knowledge of requires is required by is available at Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Authorization condition Target Object Type
ARIS Methods
11.2.8 BSC Cause-and-effect diagram
11-176
Model Type
Source Object Type
Target Object Type
Authorization map Authorization map
Position Position
has knowledge of requires
is available at is required by
Authorization condition Authorization condition

Model Type Source Object Type BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram Critical factor is measured by measures Key performance indicator instance Critical factor has weak influence on is weakly influenced by Critical factor Critical factor Critical factor has very strong influence on has very weak influence on is very strongly influenced by is very weakly influenced by Critical factor Critical factor Critical factor has strong influence on is strongly influenced by Critical factor Critical factor Relationship Type (active) has normal influence on Relationship Type (passive) is normally influenced by Critical factor Target Object Type
ARIS Methods
11-177
Model Type
Source Object Type
Target Object Type
BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram
Critical factor
has normal influence on
is normally influenced by
Objective
Critical factor
has strong influence on
is strongly influenced by
Objective
Critical factor
has very strong influence on
is very strongly influenced by is very weakly influenced by is weakly influenced by is supported by
Objective
Critical factor
has very weak influence on
Objective
Critical factor
has weak influence on
Objective
Critical factor
supports
Strategy
Objective
is normally influenced by is strongly influenced by is very strongly influenced by
Critical factor
Objective
Critical factor
Objective
Critical factor
ARIS Methods
11-178
Model Type
Source Object Type
Target Object Type
BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram
Objective
is very weakly influenced by
Critical factor
Objective
is weakly influenced by
Critical factor
Objective
is measured by
measures
Key performance indicator instance
Objective
is normally influenced by is strongly influenced by is very strongly influenced by is very weakly influenced by is weakly influenced by is supported by
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
Objective
supports
Strategy
ARIS Methods
11.2.9 Business controls diagram
11-179
Model Type
Source Object Type
Target Object Type
BSC Causeand-effect diagram BSC Causeand-effect diagram BSC Causeand-effect diagram
Perspective
contains
is contained in
Critical factor
Perspective
contains
is contained in
Objective
Perspective
is influenced by
has influence on
Perspective
11.2.9 Business controls diagram

Model Type Source Object Type Business controls diagram Business controls diagram Business controls diagram Business controls diagram Business controls diagram Business controls diagram Risk is prevented by prevents Risk is reported by is reported by Information carrier Organizational unit Risk Control Control Control Relationship Type (active) is implemented by is implemented by is implemented by is reduced by mitigates Control implements implements Relationship Type (passive) implements Information carrier Organizational unit Solution Target Object Type
ARIS Methods
11.2.10 c3 method
11-180
Model Type
Source Object Type
Target Object Type
Business controls diagram
Risk
is prevented by
prevents
Solution
Source Object Type
Target Object Type
Business controls diagram Business controls diagram Business controls diagram Business controls diagram Business controls diagram
Function Function Function Function
requires uses uses is exposed to
is required by is used by is used by is associated with
Control Information carrier Organizational unit Risk
Function
uses
is used by
Solution
11.2.10 c3 method
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) c3 method c3 method c3 method Entity type Function Function belongs to belongs to belongs to encompasses has assigned encompasses Structural element Function Structural element Target Object Type
ARIS Methods
11.2.10 c3 method
11-181
Model Type
Source Object Type
Target Object Type
c3 method
Group
is deputy process manager
is as process under representative responsibility of is under process responsibility of is substituted by is substituted by
Function
c3 method
Group
is process manager for
Function
c3 method c3 method
Group Group
substitutes for substitutes for
Group Location
c3 method c3 method c3 method
Group Group Group
substitutes for substitutes for substitutes for
is substituted by is substituted by is substituted by
Organizational unit Organizational unit type Person
Group Group Group
substitutes for substitutes for belongs to
is substituted by is substituted by encompasses
Person type Position Structural element
c3 method c3 method
Improvement potential Knowledge category
belongs to belongs to
encompasses encompasses
Structural element Structural element
ARIS Methods
11.2.10 c3 method
11-182
Model Type
Source Object Type
Target Object Type
c3 method
Location
Function
c3 method
Location
Function
c3 method c3 method
Location Location
Group Location
c3 method
Objective
belongs to
encompasses
Structural element
ARIS Methods
11.2.10 c3 method
11-183
Model Type
Source Object Type
Target Object Type
c3 method
Organizational unit
Function
c3 method
Organizational unit
is process manager for substitutes for substitutes for
Function
c3 method c3 method
Group Location
c3 method
is as process under representative responsibility of
Function
ARIS Methods
11.2.10 c3 method
11-184
Model Type
Source Object Type
Target Object Type
c3 method
is under process responsibility of
Function
c3 method c3 method c3 method c3 method
Organizational unit type Organizational unit type Organizational unit type Organizational unit type
substitutes for substitutes for substitutes for substitutes for
is substituted by is substituted by is substituted by is substituted by
Group Location Organizational unit Organizational unit type Person Person type Position
c3 method c3 method
Organizational unit type Person
belongs to is deputy process manager
encompasses is as process under representative responsibility of
Structural element Function
c3 method
Person
Function
ARIS Methods
11.2.10 c3 method
11-185
Model Type
Source Object Type
Target Object Type
Group Location Organizational unit Organizational unit type Person Person type Position
substitutes for substitutes for substitutes for substitutes for
is substituted by is substituted by is substituted by is substituted by
c3 method c3 method
Person Person type
belongs to is deputy process manager
encompasses is as process under representative responsibility of
Structural element Function
c3 method
Person type
Function
c3 method c3 method
is substituted by is substituted by
Group Location
ARIS Methods
11.2.10 c3 method
11-186
Model Type
Source Object Type
Target Object Type
Person type Person type Person type Position
substitutes for substitutes for belongs to is deputy process manager
is substituted by is substituted by encompasses is as process under representative responsibility of is under process responsibility of is substituted by is substituted by
Person type Position Structural element Function
c3 method
Position
Function
c3 method c3 method
Position Position
Group Location
c3 method c3 method
Position Position
is substituted by is substituted by
Organizational unit Organizational unit type
ARIS Methods
11.2.11 CD Diagram
11-187
Model Type
Source Object Type
Target Object Type
c3 method c3 method
Position Tool
encompasses encompasses
11.2.11 CD Diagram
Model Type Source Object Type CD Diagram Cost driver Relationship Type (active) determines volume of Relationship Type (passive) volume is dependent on Cost driver Target Object Type
ARIS Methods
11.2.12 Class diagram
11-188

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Class diagram Class diagram Class diagram Attribute type group Attribute type group Cluster/Data model Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Cluster/Data model Cluster/Data model Entity type Entity type Entity type Entity type Entity type ERM attribute has state has method is subtype of is supertype of defines belongs to is state of is method for has as subtype has as supertype is defined by encompasses Event Function Generalization type Generalization type Relationship type Attribute type group Class diagram Class diagram ERM attribute ERM attribute is assigned to is describing for has assigned is described by Cluster/Data model Entity type has method is method for Function has state is state of is attribute type group is attribute type group has link to has attribute type group has attribute type group has link to Relationship type Cluster/Data model Event Entity type Target Object Type
ARIS Methods
11-189
Model Type
Source Object Type
Target Object Type
Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram
ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event Event Function Function Generalization type
is foreign key for is primary key for has has state is describing for is foreign key for is primary key for activates is evaluated by creates leads to differentiates according to value of has state has method
has foreign key has primary key is assigned to is state of is described by has foreign key has primary key is activated by evaluates is created by is assigned to is characteristic for is state of is method for
Entity type Entity type ERM domain Event Relationship type Relationship type Relationship type Function Rule Event Rule ERM attribute
Class diagram Class diagram
Event Function
Class diagram
Relationship type
is subtype of
has as subtype
Generalization type
ARIS Methods
11-190
Model Type
Source Object Type
Target Object Type
Class diagram Class diagram Class diagram
Relationship type Relationship type Rule
is supertype of defines leads to
has as supertype is defined by is dependent on
Generalization type Relationship type Event
Class diagram Class diagram Class diagram Class diagram
Rule Rule Technical term Technical term
activates links has state has method
is activated by is linked by is state of is method for
Function Rule Event Function
Source Object Type
Target Object Type
Class diagram Class diagram Class diagram
Cluster/Data model Cluster/Data model Cluster/Data model
consists of consists of consists of
is part of is part of is part of
Class diagram Class diagram
consists of consists of
is part of is part of
Generalization type Relationship type
ARIS Methods
11.2.13 Classification diagram
11-191
Source Object Type
Target Object Type
Class diagram
Generalization type
differentiates according to value of
is characteristic for
ERM attribute
11.2.13 Classification diagram

Model Type Source Object Type Classification diagram Classification diagram Object type class classified by is criterion of Function Relationship Type (active) belongs to Relationship Type (passive) groups Object type class Classification criterion Target Object Type
11.2.14 Communications diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Communications diagram Communications diagram Communications diagram Communications diagram Communication Communication Organizational unit Organizational unit type sends is sent from is received from is received from sends is sent from receives receives Organizational unit Organizational unit type Communication Communication Target Object Type
ARIS Methods
11.2.15 Competition model
11-192
11.2.15 Competition model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Competition model Competition model Organizational unit Product/Service is used by uses provides is provided by Product/Service Organizational unit Target Object Type
11.2.16 Cost category diagram

Model Type Source Object Type Cost category diagram Cost category Relationship Type (active) is superior Relationship Type (passive) is subordinate Cost category Target Object Type
11.2.17 DTD
Model Type Source Object Type DTD DTD Conditional section Conditional section DTD Conditional section Relationship Type (active) has any number of times has at least once has at most once must occur at least once may occur at most once Element type Element type Relationship Type (passive) may occur Element type Target Object Type
ARIS Methods
11.2.17 DTD
11-193
Model Type
Source Object Type
Target Object Type
DTD DTD DTD DTD DTD DTD DTD DTD
Conditional section Contents Element type Element type Element type Element type Element type Element type
has exactly once contains is described by contains contains has any number of times has at least once has at most once
must occur exactly once is contents of is describing for is contents of is contents of may occur must occur at least once may occur at most once must occur exactly once is describing for may occur
Element type Element type Attribute type Conditional section Contents Element type Element type Element type
DTD DTD DTD
Element type Element type Element type
has exactly once is described by has any number of times
Element type Enumeration attribute type Sequence
DTD DTD DTD
has at least once has at most once has exactly once
must occur at least once may occur at most once must occur exactly once
Sequence Sequence Sequence
ARIS Methods
11.2.17 DTD
11-194
Model Type
Source Object Type
Target Object Type
DTD DTD DTD
has any number of times has at least once has at most once
may occur must occur at least once may occur at most once must occur exactly once is assigned to is contents of may occur must occur at least once may occur at most once must occur exactly once may occur must occur at least once may occur at most once must occur exactly once
XOR XOR XOR
DTD DTD DTD DTD DTD DTD
Element type Enumeration attribute type Sequence Sequence Sequence Sequence
has exactly once has contains has any number of times has at least once has at most once
XOR Enumeration Contents Element type Element type Element type
DTD DTD DTD
has exactly once has any number of times has at least once
Element type Sequence Sequence
DTD DTD
Sequence Sequence
has at most once has exactly once
Sequence Sequence
ARIS Methods
11.2.17 DTD
11-195
Model Type
Source Object Type
Target Object Type
DTD DTD DTD
may occur must occur at least once may occur at most once must occur exactly once is contents of may occur
XOR XOR XOR
DTD DTD DTD
Sequence XOR XOR
has exactly once contains has any number of times
XOR Contents Element type
DTD DTD DTD
XOR XOR XOR
must occur at least once may occur at most once must occur exactly once may occur must occur at least once may occur at most once must occur exactly once may occur
DTD DTD DTD
XOR XOR XOR
DTD DTD
XOR XOR
has exactly once has any number of times
Sequence XOR
ARIS Methods
11.2.18 DW - structure
11-196
Model Type
Source Object Type
Target Object Type
DTD DTD DTD
XOR XOR XOR
must occur at least once may occur at most once must occur exactly once
XOR XOR XOR
11.2.18 DW - structure
Model Type Source Object Type DW - structure Cluster/Data model DW - structure DW - structure DW - structure DW - structure Cluster/Data model Cluster/Data model Entity type ERM attribute has relationship to is describing for DW - structure DW - structure ERM attribute ERM attribute is foreign key for is primary key for has foreign key has primary key Entity type Entity type has relationship to is described by Entity type Entity type consists of is part of ERM attribute consists of is part of Relationship Type (active) consists of Relationship Type (passive) is part of Cluster/Data model Entity type Target Object Type
ARIS Methods
11.2.19 DW - transformation
11-197
11.2.19 DW - transformation
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) DW - transformation DW - transformation DW - transformation DW - transformation DW - transformation DW - transformation Function has output of is output of ERM attribute Function has output of is output of Function has output of is output of Cluster/Data model Entity type ERM attribute is input for has input of Function Cluster/Data model Entity type is input for has input of Function is input for has input of Function Target Object Type
11.2.20 E-Business scenario diagram

Model Type Source Object Type E-Business scenario diagram E-Business scenario diagram Application system type supports is supported by Function Application system Relationship Type (active) supports Relationship Type (passive) is supported by Function Target Object Type
ARIS Methods
11.2.20 E-Business scenario diagram
11-198
Model Type
Source Object Type
Target Object Type
E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram
Cluster/Data model
is input for
has input of
Function
Function
has output of
is output of
Cluster/Data model
Function
creates output to
is output medium for is output of
Information carrier Product/Service
Function
has output of
Information carrier Organizational unit type Organizational unit type Organizational unit type Organizational unit type
provides input for can be user
gets input from can be used by
Function
Application system
carries out
is carried out by
is IT responsible for is technically responsible for
is under IT responsibility of is under technical responsibility of
ARIS Methods
11.2.21 eEPC
11-199
Model Type
Source Object Type
Target Object Type
E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram E-Business scenario diagram
carries out
is carried out by
Function
Security protocol
Person type
carries out
is carried out by
Function
Product/Service Security protocol Security protocol
is input for
has input of
Function
secures
is secured by
Cluster/Data model
secures
is secured by
Product/Service
11.2.21 eEPC
Model Type Source Object Type eEPC eEPC Application system Application system uses is used by Relationship Type (active) uses Relationship Type (passive) is used by Attribute type group Class Target Object Type
ARIS Methods
11.2.21 eEPC
11-200
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
uses uses uses
Cluster/Data model Complex object type COT attribute
eEPC eEPC eEPC eEPC
Application system Application system Application system Application system
uses uses supports uses
is used by is used by is supported by is used by
Entity type ERM attribute Function Relationship type
eEPC eEPC eEPC
Application system Application system class Application system type
uses supports uses
is used by is supported by is used by
Technical term Function Attribute type group
eEPC eEPC eEPC
can use uses can use
can be used by is used by can be used by
ARIS Methods
11.2.21 eEPC
11-201
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
can use can use can use
can be used by can be used by can be used by
Complex object type COT attribute Entity type
eEPC eEPC eEPC eEPC
Application system type Application system type Application system type Application system type
can use creates supports can use
can be used by is created by is supported by can be used by
ERM attribute Event Function Relationship type
eEPC eEPC eEPC
Application system type Attribute type group Attribute type group
can use is approved by is checked by
can be used by approves checks
Technical term Function Function
eEPC eEPC eEPC
Attribute type group Attribute type group Authorization condition
is input for lies on is required for
has input of has information about requires
Function Information carrier Function
ARIS Methods
11.2.21 eEPC
11-202
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Authorization condition Business object Class Class Class Class Class Cluster/Data model
relates to is input for has state is approved by is checked by is input for lies on has state
has has input of is state of approves checks has input of has information about is state of
Technical term Function Event Function Function Function Information carrier Event
eEPC eEPC eEPC
is approved by is checked by is input for
approves checks has input of
Function Function Function
eEPC eEPC eEPC
is used by lies on is used by
uses has information about uses
Group Information carrier Organizational unit
eEPC
Cluster/Data model
is used by
uses
Person type
ARIS Methods
11.2.21 eEPC
11-203
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Cluster/Data model Complex object type Complex object type
is used by is managed by is managed by
uses manages manages
Position Application system type Component
eEPC eEPC eEPC eEPC
Complex object type Complex object type Complex object type Complex object type
has state is approved by is checked by is input for
is state of approves checks has input of
Event Function Function Function
eEPC eEPC eEPC
Complex object type Component Component
lies on can use can use
has information about can be used by can be used by
Information carrier Attribute type group Cluster/Data model
eEPC eEPC eEPC eEPC
Component Component Component Component
can use can use can use can use
can be used by can be used by can be used by can be used by
Complex object type COT attribute Entity type ERM attribute
ARIS Methods
11.2.21 eEPC
11-204
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Component Component Component Cost driver COT attribute COT attribute COT attribute
supports can use can use influences has state is compared to provides value for
is supported by can be used by can be used by is influenced by is state of is compared to uses value of
Function Relationship type Technical term Function Event Event Event
eEPC eEPC eEPC eEPC eEPC eEPC
COT attribute COT attribute COT attribute COT attribute Documented knowledge Documented knowledge
is approved by is checked by is input for lies on relates to is required for
approves checks has input of has information about relates to (passive) requires
Function Function Function Information carrier Event Function
eEPC eEPC eEPC eEPC
Element type Element type Element type Element type
has state is compared to provides value for is approved by
is state of is compared to uses value of approves
Event Event Event Function
ARIS Methods
11.2.21 eEPC
11-205
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC
Element type Element type Employee variable Employee variable
is checked by is input for is different from is disciplinary superior to is technical superior to substitutes for
checks has input of is different from has the disciplinary superior has the technical superior is substituted by
Function Function Employee variable Employee variable Employee variable Employee variable Function Function Function
eEPC eEPC
Employee variable Employee variable
eEPC eEPC eEPC
Employee variable Employee variable Employee variable
accepts carries out contributes to
is accepted by is carried out by is worked on by collaboration of
eEPC
Employee variable
decides on
is decided by
Function
eEPC
Employee variable
has consulting role in
is supported by consulting role of
Function
eEPC
Employee variable
Function
ARIS Methods
11.2.21 eEPC
11-206
Model Type
Source Object Type
Target Object Type
eEPC
Employee variable
Function
eEPC eEPC
must be informed about must be informed on cancellation must inform about result of is employee variable is employee variable is employee variable is employee variable is employee variable is employee variable is managed by is managed by has state is approved by
result is forwarded to sends information on cancellation to result is forwarded by has employee variable has employee variable has employee variable has employee variable has employee variable has employee variable manages manages is state of approves
Function Function
eEPC eEPC eEPC
Function Group Location
eEPC eEPC eEPC
Organizational unit Person Person type
eEPC eEPC eEPC eEPC eEPC
Employee variable Entity type Entity type Entity type Entity type
Position Application system type Component Event Function
ARIS Methods
11.2.21 eEPC
11-207
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Entity type Entity type Entity type ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event
is checked by is input for lies on has state is compared to provides value for is approved by is checked by is input for lies on defines screen field activates
checks has input of has information about is state of is compared to uses value of approves checks has input of has information about has screen field is activated by
Function Function Information carrier Event Event Event Function Function Function Information carrier Screen Application system type
Event Event Event Event Event
activates is used by activates activates is used by
is activated by uses is activated by is activated by uses
Function Group IT function type Module type Organizational unit
ARIS Methods
11.2.21 eEPC
11-208
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Event Event Event Event Event Event Event Function
is used by is used by is used by is used by corresponds to is evaluated by activates archives
uses uses uses uses corresponds to evaluates is activated by is archived by
Organizational unit type Person Person type Position Product/Service Rule Screen Attribute type group
eEPC eEPC eEPC
changes creates deletes
is changed by is created by is deleted by
Attribute type group Attribute type group Attribute type group
eEPC eEPC eEPC
distributes has output of reads
is distributed by is output of is read by
eEPC
Function
has knowledge of
is available at
Authorization condition
ARIS Methods
11.2.21 eEPC
11-209
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Function Function Function Function Function Function Function Function Function Function
has output of reads archives changes creates deletes distributes has output of reads archives
is output of is read by is archived by is changed by is created by is deleted by is distributed by is output of is read by is archived by
Business object Business object Class Class Class Class Class Class Class Cluster/Data model
eEPC eEPC eEPC
eEPC eEPC eEPC
ARIS Methods
11.2.21 eEPC
11-210
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
archives changes creates
is archived by is changed by is created by
Complex object type Complex object type Complex object type
eEPC eEPC eEPC eEPC
deletes distributes has output of reads
is deleted by is distributed by is output of is read by
Function Function Function Function Function Function Function
can support belongs to archives changes creates deletes distributes
can be supported by is assigned to is archived by is changed by is created by is deleted by is distributed by
Component Cost category COT attribute COT attribute COT attribute COT attribute COT attribute
eEPC eEPC
Function Function
has output of reads
is output of is read by
COT attribute COT attribute
ARIS Methods
11.2.21 eEPC
11-211
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
creates reads can create
is created by is read by can be created by
Documented knowledge Documented knowledge Draft list
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
can use archives changes creates deletes distributes has output of reads archives changes creates deletes distributes has output of reads archives changes
can be used by is archived by is changed by is created by is deleted by is distributed by is output of is read by is archived by is changed by is created by is deleted by is distributed by is output of is read by is archived by is changed by
Draft list Element type Element type Element type Element type Element type Element type Element type Entity type Entity type Entity type Entity type Entity type Entity type Entity type ERM attribute ERM attribute
ARIS Methods
11.2.21 eEPC
11-212
Model Type
Source Object Type
Target Object Type
creates deletes distributes has output of reads creates calls is predecessor of produces reads
is created by is deleted by is distributed by is output of is read by is created by is called by follows is produced by is read by
ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event Function Function General resource General resource
eEPC eEPC eEPC
creates output to reads is measured by
is output medium for is read by measures
Information carrier Information carrier Key performance indicator instance
eEPC
Function
creates
is created by
Knowledge category
eEPC
Function
has knowledge of
is available at
Knowledge category
ARIS Methods
11.2.21 eEPC
11-213
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC
reads creates uses is carried out at
is read by is created by is used by is performed in
Knowledge category List List Location
Function Function Function Function Function
supports has output of reads has output of produces
is supported by is output of is read by is output of is produced by
Objective Package Package Product/Service Product/Service
eEPC eEPC eEPC
Relationship type Relationship type Relationship type
eEPC eEPC eEPC
deletes distributes has output of
is deleted by is distributed by is output of
ARIS Methods
11.2.21 eEPC
11-214
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Function Function Function Function Function Function Function Function Function Function Function General resource General resource General resource
reads leads to is represented by can use archives changes creates deletes distributes has output of reads is compared to is consumed by is defined
is read by is assigned to represents can be used by is archived by is changed by is created by is deleted by is distributed by is output of is read by is compared to consumes can be processed by/with
Relationship type Rule Screen Screen design Technical term Technical term Technical term Technical term Technical term Technical term Technical term Event Function Function
eEPC eEPC
General resource Group
is used by is responsible for development of
uses development is under responsibility of
Function Application system
ARIS Methods
11.2.21 eEPC
11-215
Model Type
Source Object Type
Target Object Type
eEPC
Group
Application system
eEPC eEPC eEPC
Group Group Group
is user can be user is responsible for development of
is used by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by
Application system Application system class Application system class Application system class Application system type Application system type Application system type Attribute type group
eEPC
Group
eEPC eEPC
Group Group
eEPC
Group
eEPC
Group
accesses
eEPC eEPC
Group Group
is owner of has knowledge of
has owner is available at
Attribute type group Authorization condition
ARIS Methods
11.2.21 eEPC
11-216
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC
requires accesses is owner of accesses
is required by is accessed by has owner is accessed by
Authorization condition Class Class Cluster/Data model
eEPC eEPC eEPC eEPC
is owner of provides accesses is owner of
has owner is provided by is accessed by has owner
Cluster/Data model Cluster/Data model Complex object type Complex object type
eEPC eEPC eEPC
Group Group Group
is specimen owner of can be user is responsible for development of
has specimen owner can be used by development is under responsibility of is under technical responsibility of
eEPC
Group
Component
eEPC eEPC
Group Group
is accessed by has owner
ARIS Methods
11.2.21 eEPC
11-217
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Group Group Group Group Group Group Group Group Group Group Group
is specimen owner of accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out contributes to
has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by is worked on by collaboration of
COT attribute Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function Function
eEPC eEPC
Group Group
decides on has consulting role in
is decided by is supported by consulting role of
Function Function
eEPC eEPC
Group Group
is under IT responsibility of is under technical responsibility of
Function Function
ARIS Methods
11.2.21 eEPC
11-218
Model Type
Source Object Type
Target Object Type
eEPC eEPC
Group Group
must be informed about must be informed on cancellation
result is forwarded to sends information on cancellation to result is forwarded by is used by
Function Function
eEPC eEPC
Group Group
must inform about result of uses
Function Hardware component type
eEPC eEPC
Group Group
provides is responsible for development of
is provided by development is under responsibility of is under technical responsibility of is used by development is under responsibility of is under technical responsibility of is used by
eEPC
Group
IT function
eEPC eEPC
Group Group
is user is responsible for development of
IT function IT function type IT function type IT function type
eEPC
Group
eEPC
Group
is user
ARIS Methods
11.2.21 eEPC
11-219
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Group Group Group
has knowledge of requires is responsible for development of
is available at is required by development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of is accessed by
Knowledge category Knowledge category Module
eEPC
Group
Module
eEPC eEPC eEPC
Group Group Group
Module Module type Module type
eEPC
Group
Module type
eEPC
Group
accesses
Relationship type
eEPC eEPC eEPC eEPC
Group Group Group Hardware component type
is owner of accesses is owner of stores
has owner is accessed by has owner is stored on
Relationship type Technical term Technical term Attribute type group
ARIS Methods
11.2.21 eEPC
11-220
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Hardware component type Hardware component type Hardware component type
stores stores stores
is stored on is stored on is stored on
Class Cluster/Data model Complex object type
eEPC eEPC eEPC eEPC
Hardware component type Hardware component type Hardware component type Hardware component type
stores stores stores stores
is stored on is stored on is stored on is stored on
COT attribute Entity type ERM attribute Relationship type
eEPC eEPC eEPC
Hardware component type Information carrier Information carrier
stores has state provides input for is used by is used by is used by
is stored on is state of gets input from uses uses uses
Technical term Event Function
eEPC eEPC eEPC
Information carrier Information carrier Information carrier
Group Organizational unit Person type
ARIS Methods
11.2.21 eEPC
11-221
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Information carrier IT function IT function IT function IT function IT function IT function IT function IT function
is used by uses uses uses uses uses uses uses supports
uses is used by is used by is used by is used by is used by is used by is used by is supported by
Position Attribute type group Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute Function
IT function IT function IT function type IT function type IT function type IT function type
uses uses uses can use uses can use
is used by is used by is used by can be used by is used by can be used by
Relationship type Technical term Attribute type group Class Class Cluster/Data model
eEPC
IT function type
uses
is used by
Cluster/Data model
ARIS Methods
11.2.21 eEPC
11-222
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
can use uses can use uses can use uses can use uses creates relates to supports supports when time limit is exceeded
can be used by is used by can be used by is used by can be used by is used by can be used by is used by is created by relates to (passive) is supported by supports when time limit is exceeded (passive) is supported by supports when time limit is exceeded (passive)
Complex object type Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Event Event Event Event
eEPC eEPC
supports supports when time limit is exceeded
Function Function
ARIS Methods
11.2.21 eEPC
11-223
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type Key performance indicator instance
can use uses can use uses is measured upon occurrence relates to
can be used by is used by can be used by is used by triggers measuring relates to (passive)
Relationship type Relationship type Technical term Technical term Event
eEPC
Knowledge category
Event
eEPC eEPC eEPC
Knowledge category List Location
is required for provides input for accesses
requires gets input from is accessed by
Function Function Attribute type group
eEPC eEPC eEPC
is owner of has knowledge of requires
has owner is available at is required by
Attribute type group Authorization condition Authorization condition
eEPC eEPC
Location Location
Class Class
ARIS Methods
11.2.21 eEPC
11-224
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Cluster/Data model Cluster/Data model Complex object type
Location Location Location Location Location Location Location Location Location Location
is owner of accesses is owner of accesses is owner of accesses is owner of has knowledge of requires accesses
has owner is accessed by has owner is accessed by has owner is accessed by has owner is available at is required by is accessed by
Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Knowledge category Knowledge category Relationship type
eEPC eEPC eEPC eEPC
Location Location Location Module
is owner of accesses is owner of uses
has owner is accessed by has owner is used by
ARIS Methods
11.2.21 eEPC
11-225
Model Type
Source Object Type
Target Object Type
eEPC eEPC
Module Module
uses uses
is used by is used by
Class Cluster/Data model
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Module Module Module Module Module Module Module Module type Module type Module type Module type Module type Module type Module type Module type Module type
uses uses uses uses supports uses uses uses can use uses can use can use can use can use can use creates
is used by is used by is used by is used by is supported by is used by is used by is used by can be used by is used by can be used by can be used by can be used by can be used by can be used by is created by
Complex object type COT attribute Entity type ERM attribute Function Relationship type Technical term Attribute type group Class Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute Event
ARIS Methods
11.2.21 eEPC
11-226
Model Type
Source Object Type
Target Object Type
Module type Module type Module type Operating resource Operating resource
supports can use can use encompasses is alternative operating resource of is operating resource of encompasses
is supported by can be used by can be used by belongs to has alternative operating resource has operating resource belongs to
Function Relationship type Technical term Application system Function
eEPC eEPC
Operating resource Operating resource
Function IT function
eEPC eEPC
Operating resource Organizational unit
encompasses is responsible for development of is technically responsible for is user can be user
belongs to development is under responsibility of is under technical responsibility of is used by can be used by
Module Application system Application system Application system Application system class
eEPC
Organizational unit
eEPC eEPC
ARIS Methods
11.2.21 eEPC
11-227
Model Type
Source Object Type
Target Object Type
eEPC
Organizational unit
eEPC
Organizational unit
eEPC eEPC
Application system type Application system type
eEPC
Organizational unit
eEPC eEPC eEPC
accesses is owner of has knowledge of requires accesses is owner of
is accessed by has owner is available at
eEPC eEPC eEPC
is required by is accessed by has owner
Authorization condition Class Class
ARIS Methods
11.2.21 eEPC
11-228
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
accesses is owner of is specimen owner of provides accesses is owner of can be user
is accessed by has owner has specimen owner is provided by is accessed by has owner can be used by
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type Component
eEPC eEPC eEPC eEPC
Organizational unit Organizational unit Organizational unit Organizational unit
eEPC
Organizational unit
Component
eEPC
Organizational unit
Component
eEPC eEPC eEPC
accesses is owner of is specimen owner of
is accessed by has owner has specimen owner
COT attribute COT attribute COT attribute
ARIS Methods
11.2.21 eEPC
11-229
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
eEPC eEPC eEPC eEPC
is owner of is specimen owner of is owner of provides
has owner has specimen owner has owner is provided by
ERM attribute ERM attribute Event Event
eEPC eEPC eEPC
eEPC
Organizational unit
decides on
is decided by
Function
eEPC
Organizational unit
Function
ARIS Methods
11.2.21 eEPC
11-230
Model Type
Source Object Type
Target Object Type
eEPC eEPC
is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of uses
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is used by
Function Function
eEPC eEPC
Function Function
eEPC eEPC
eEPC
Organizational unit
provides
is provided by
Information carrier
eEPC
Organizational unit
IT function
eEPC
Organizational unit
IT function
eEPC eEPC
is used by development is under responsibility of
IT function IT function type
ARIS Methods
11.2.21 eEPC
11-231
Model Type
Source Object Type
Target Object Type
eEPC
Organizational unit
IT function type
eEPC eEPC eEPC eEPC
is user has knowledge of requires is responsible for development of is technically responsible for is user
is used by is available at is required by development is under responsibility of is under technical responsibility of is used by
IT function type Knowledge category Knowledge category Module
eEPC
Organizational unit
Module
eEPC
Organizational unit
Module
eEPC eEPC
can be user is responsible for development of is technically responsible for accesses
can be used by development is under responsibility of is under technical responsibility of is accessed by
eEPC
Organizational unit
Module type
eEPC
Organizational unit
Relationship type
ARIS Methods
11.2.21 eEPC
11-232
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
is owner of accesses is owner of
has owner is accessed by has owner
Relationship type Technical term Technical term
eEPC eEPC
Organizational unit type Organizational unit type
eEPC
Application system
eEPC eEPC
Application system class Application system class Application system class Application system type Application system type
eEPC
eEPC eEPC
ARIS Methods
11.2.21 eEPC
11-233
Model Type
Source Object Type
Target Object Type
eEPC
eEPC eEPC eEPC eEPC
accesses is owner of has knowledge of requires
is accessed by has owner is available at is required by
Attribute type group Attribute type group Authorization condition Authorization condition
eEPC eEPC eEPC
eEPC eEPC eEPC
eEPC
can be user
can be used by
Component
ARIS Methods
11.2.21 eEPC
11-234
Model Type
Source Object Type
Target Object Type
eEPC
Component
eEPC
Component
eEPC eEPC eEPC eEPC
accesses is owner of accesses is owner of
is accessed by has owner is accessed by has owner
COT attribute COT attribute Entity type Entity type
eEPC eEPC eEPC
accesses is owner of is owner of
is accessed by has owner has owner
ERM attribute ERM attribute Event
eEPC eEPC eEPC
provides accepts carries out
is provided by is accepted by is carried out by
Event Function Function
ARIS Methods
11.2.21 eEPC
11-235
Model Type
Source Object Type
Target Object Type
eEPC
contributes to
is worked on by collaboration of
Function
eEPC eEPC
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of can be user is responsible for development of is technically responsible for
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of
Function Function
eEPC eEPC
Function Function
eEPC eEPC
Function Function
eEPC
Function
eEPC eEPC
IT function IT function
eEPC
IT function
ARIS Methods
11.2.21 eEPC
11-236
Model Type
Source Object Type
Target Object Type
eEPC eEPC
can be user is responsible for development of is technically responsible for has knowledge of requires can be user
can be used by development is under responsibility of is under technical responsibility of is available at is required by can be used by
IT function type IT function type IT function type Knowledge category Knowledge category Module
eEPC
eEPC eEPC eEPC
eEPC
Module
eEPC
Module
eEPC eEPC
eEPC
Module type
ARIS Methods
11.2.21 eEPC
11-237
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Relationship type Relationship type Technical term
eEPC eEPC eEPC eEPC
Organizational unit type Package Package Person
is owner of contains is input for is responsible for development of
has owner is contained by has input of development is under responsibility of is under technical responsibility of is used by can be used by
Technical term Function Function Application system Application system Application system Application system class
eEPC
Person
eEPC eEPC
Person Person
is user can be user
eEPC
Person
eEPC
Person
ARIS Methods
11.2.21 eEPC
11-238
Model Type
Source Object Type
Target Object Type
eEPC eEPC
Person Person
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner is available at
Application system type Application system type Application system type Attribute type group Attribute type group Authorization condition
eEPC
Person
eEPC eEPC eEPC
accesses is owner of has knowledge of
eEPC eEPC eEPC eEPC
eEPC eEPC eEPC
eEPC
Person
can be user
can be used by
Component
ARIS Methods
11.2.21 eEPC
11-239
Model Type
Source Object Type
Target Object Type
eEPC
Person
Component
eEPC
Person
Component
eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC eEPC
Person Person Person Person Person Person Person Person Person Person Person Person Person
accesses is owner of is specimen owner of accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out contributes to
is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by is worked on by collaboration of
COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function Function
eEPC
Person
decides on
is decided by
Function
ARIS Methods
11.2.21 eEPC
11-240
Model Type
Source Object Type
Target Object Type
eEPC
Person
Function
eEPC eEPC
Person Person
Function Function
eEPC eEPC
Person Person
Function Function
eEPC eEPC
Person Person
eEPC
Person
development is under responsibility of is under technical responsibility of is used by development is under responsibility of
IT function
eEPC
Person
IT function
eEPC eEPC
Person Person
ARIS Methods
11.2.21 eEPC
11-241
Model Type
Source Object Type
Target Object Type
eEPC
Person
IT function type
eEPC eEPC eEPC eEPC
is user has knowledge of requires is responsible for development of
is used by is available at is required by development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of
eEPC
Person
Module
eEPC eEPC eEPC
eEPC
Person
Module type
eEPC eEPC
Person Person
ARIS Methods
11.2.21 eEPC
11-242
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC eEPC
Person Person Person type Person type
accesses is owner of can be user is responsible for development of
is accessed by has owner can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
Technical term Technical term Application system Application system Application system Application system class Application system class Application system class Application system type
eEPC
Person type
eEPC eEPC
eEPC
Person type
eEPC
Person type
can be user
eEPC
Person type
eEPC
Person type
ARIS Methods
11.2.21 eEPC
11-243
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
Person type Person type Person type Person type Person type
requires accesses is owner of accesses is owner of
is required by is accessed by has owner is accessed by has owner
Authorization condition Class Class Cluster/Data model Cluster/Data model
eEPC eEPC eEPC
provides accesses is owner of
is provided by is accessed by has owner
eEPC eEPC
Component Component
eEPC
Person type
Component
ARIS Methods
11.2.21 eEPC
11-244
Model Type
Source Object Type
Target Object Type
Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type
accesses is owner of accesses is owner of accesses is owner of is owner of provides accepts carries out
is accessed by has owner is accessed by has owner is accessed by has owner has owner is provided by is accepted by is carried out by
COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Event Event Function Function
eEPC
Person type
contributes to
Function
eEPC eEPC
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of
Function Function
eEPC
Person type
Function
eEPC
Person type
Function
eEPC
Person type
must be informed about
result is forwarded to
Function
ARIS Methods
11.2.21 eEPC
11-245
Model Type
Source Object Type
Target Object Type
eEPC
Person type
must be informed on cancellation
sends information on cancellation to result is forwarded by is provided by can be used by development is under responsibility of is under technical responsibility of
Function
eEPC eEPC eEPC eEPC
must inform about result of provides can be user is responsible for development of
Function Information carrier IT function IT function
eEPC
Person type
IT function
eEPC eEPC
can be used by development is under responsibility of is under technical responsibility of is available at is required by
IT function type IT function type IT function type Knowledge category Knowledge category
eEPC
Person type
eEPC eEPC
eEPC
Person type
can be user
can be used by
Module
ARIS Methods
11.2.21 eEPC
11-246
Model Type
Source Object Type
Target Object Type
eEPC
Person type
Module
eEPC
Person type
Module
eEPC eEPC
can be used by development is under responsibility of is under technical responsibility of is in conflict with is accessed by
eEPC
Person type
Module type
eEPC eEPC
is in conflict with accesses
Person type Relationship type
eEPC eEPC eEPC eEPC
is owner of accesses is owner of is responsible for development of
has owner is accessed by has owner development is under responsibility of is under technical responsibility of
Relationship type Technical term Technical term Application system Application system
eEPC
Position
ARIS Methods
11.2.21 eEPC
11-247
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
eEPC
Position
eEPC eEPC
Position Position
eEPC
Position
eEPC
Position
accesses
eEPC eEPC eEPC
eEPC
Position
accesses
is accessed by
Class
ARIS Methods
11.2.21 eEPC
11-248
Model Type
Source Object Type
Target Object Type
eEPC eEPC
Position Position
is owner of accesses
has owner is accessed by
eEPC eEPC eEPC eEPC
Position Position Position Position
eEPC eEPC
Position Position
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner
Component Component
eEPC
Position
Component
Position Position Position Position Position Position Position
accesses is owner of is specimen owner of accesses is owner of accesses is owner of
COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute
ARIS Methods
11.2.21 eEPC
11-249
Model Type
Source Object Type
Target Object Type
Position Position Position Position Position Position
is specimen owner of is owner of provides accepts carries out contributes to
has specimen owner has owner is provided by is accepted by is carried out by is worked on by collaboration of
ERM attribute Event Event Function Function Function
eEPC eEPC
Position Position
Function Function
eEPC eEPC
Position Position
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by
Function Function
eEPC eEPC
Position Position
Function Function
eEPC
Position
must inform about result of
Function
ARIS Methods
11.2.21 eEPC
11-250
Model Type
Source Object Type
Target Object Type
eEPC
Position
uses
is used by
eEPC eEPC
Position Position
is provided by development is under responsibility of is under technical responsibility of
eEPC
Position
IT function
eEPC eEPC
Position Position
is used by development is under responsibility of is under technical responsibility of is used by
eEPC
Position
eEPC
Position
is user
eEPC eEPC eEPC
is available at is required by development is under responsibility of
ARIS Methods
11.2.21 eEPC
11-251
Model Type
Source Object Type
Target Object Type
eEPC
Position
Module
eEPC eEPC eEPC
is used by can be used by development is under responsibility of is under technical responsibility of
eEPC
Position
Module type
Position Position Position Position Product/Service Product/Service
accesses is owner of accesses is owner of is compared to is consumed by
is accessed by has owner is accessed by has owner is compared to consumes
Relationship type Relationship type Technical term Technical term Event Function
eEPC eEPC eEPC eEPC
Product/Service Product/Service Relationship type Relationship type
is input for is used by is managed by is managed by
has input of uses manages manages
Function Function Application system type Component
ARIS Methods
11.2.21 eEPC
11-252
Model Type
Source Object Type
Target Object Type
eEPC eEPC eEPC
has state is approved by is checked by
is state of approves checks
Relationship type Relationship type Rule Rule Rule Screen Screen
is input for lies on leads to activates links can use can use
has input of has information about is dependent on is activated by is linked by can be used by can be used by
Function Information carrier Event Function Rule Class Cluster/Data model
Screen Screen Screen Screen Screen Screen Screen
can use can use can use can use creates can use can use
can be used by can be used by can be used by can be used by is created by can be used by can be used by
Complex object type COT attribute Entity type ERM attribute Event Relationship type Technical term
ARIS Methods
11.2.21 eEPC
11-253
Model Type
Source Object Type
Target Object Type
eEPC eEPC
System organizational unit System organizational unit type
is assigned to can be assigned to has state is approved by is checked by is input for lies on
is assigned to can be assigned to is state of approves checks has input of has information about
Function Function
Technical term Technical term Technical term Technical term Technical term
Event Function Function Function Information carrier
Assignment Relationship eEPC
Source Object Type Function
Relationship Type (active) is processoriented superior
Relationship Type (passive) is processoriented subordinate
Target Object Type Function
ARIS Methods
11.2.22 eEPC (column display)
11-254

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type Application system type uses is used by Class can use supports is supported by can be used by Class Function uses is used by uses supports is supported by is used by Relationship type Technical term Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by Cluster/Data model Complex object type COT attribute uses is used by Class Target Object Type
ARIS Methods
11-255
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Attribute type group Attribute type group Attribute type group Attribute type group
can use can use creates supports
can be used by can be used by is created by is supported by
Entity type ERM attribute Event Function
can use can use is approved by
can be used by can be used by approves
Relationship type Technical term Function
is checked by is input for lies on
checks has input of has information about
Function Function Information carrier
ARIS Methods
11-256
Model Type
Source Object Type
Target Object Type
Authorization condition Authorization condition Business object Class Class Class Class
is required for relates to is input for
requires has has input of
Function Technical term Function
has state is approved by is checked by is input for
is state of approves checks has input of
Class Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
lies on has state is approved by
has information about is state of approves
Information carrier Event Function
is checked by is input for is used by
checks has input of uses
Function Function Group
ARIS Methods
11-257
Model Type
Source Object Type
Target Object Type
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Component Component
lies on is used by is used by
has information about uses uses
Information carrier Organizational unit Person type
is used by is managed by is managed by has state
uses manages manages is state of
Position Application system type Component Event
Information carrier Cluster/Data model Complex object type
ARIS Methods
11-258
Model Type
Source Object Type
Target Object Type
Component Component Component
COT attribute Entity type ERM attribute
Component Component Component Cost driver
supports can use can use influences
is supported by can be used by can be used by is influenced by
Function Relationship type Technical term Function
has state is compared to provides value for
is state of is compared to uses value of
Event Event Event
ARIS Methods
11-259
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
COT attribute Documented knowledge Documented knowledge Element type Element type Element type Element type
lies on relates to is required for
has information about relates to (passive) requires
Element type Element type Employee variable Employee variable
is checked by is input for is different from is disciplinary superior to
checks has input of is different from has the disciplinary superior
Function Function Employee variable Employee variable
eEPC (column display) eEPC (column display)
is technical superior to substitutes for
has the technical superior is substituted by
ARIS Methods
11-260
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable
decides on has consulting role in is IT responsible for is technically responsible for
Function Function
Function
Function
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
must be informed about must be informed on cancellation must inform about result of is employee variable
result is forwarded to sends information on cancellation to result is forwarded by has employee variable
Function Function
Function Group
ARIS Methods
11-261
Model Type
Source Object Type
Target Object Type
Employee variable Employee variable Employee variable Employee variable Employee variable Entity type Entity type
is employee variable is employee variable is employee variable is employee variable is employee variable is managed by is managed by
has employee variable has employee variable has employee variable has employee variable has employee variable manages manages
Location Organizational unit Person
Person type Position Application system type Component
Entity type Entity type Entity type
is input for lies on has state
has input of has information about is state of
Function Information carrier Event
ARIS Methods
11-262
Model Type
Source Object Type
Target Object Type
is compared to provides value for is approved by
is compared to uses value of approves
Event Event Function
ERM attribute ERM attribute ERM attribute ERM attribute
is checked by is input for lies on defines screen field
checks has input of has information about has screen field is activated by is activated by uses
Function Function Information carrier Screen
Event Event Event
activates activates is used by
Application system type Function Group
Event Event Event
is activated by is activated by uses
IT function type Module type Organizational unit
ARIS Methods
11-263
Model Type
Source Object Type
Target Object Type
Event Event Event
uses uses uses
Organizational unit type Person Person type
Event Event Event Event
is used by corresponds to is evaluated by activates
uses corresponds to evaluates is activated by
Position Product/Service Rule Screen
ARIS Methods
11-264
Model Type
Source Object Type
Target Object Type
reads has knowledge of has output of
is read by is available at is output of
Attribute type group Authorization condition Business object
reads archives changes creates
is read by is archived by is changed by is created by
Business object Class Class Class
Class Class Class
reads archives changes
is read by is archived by is changed by
ARIS Methods
11-265
Model Type
Source Object Type
Target Object Type
creates deletes distributes
is created by is deleted by is distributed by
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type
has output of reads archives changes
is output of is read by is archived by is changed by
Complex object type Complex object type Complex object type Complex object type Complex object type Component
has output of reads can support
is output of is read by can be supported by
ARIS Methods
11-266
Model Type
Source Object Type
Target Object Type
belongs to archives changes
is assigned to is archived by is changed by
Cost category COT attribute COT attribute
creates deletes distributes has output of
is created by is deleted by is distributed by is output of
COT attribute COT attribute COT attribute COT attribute
reads creates reads
is read by is created by is read by
COT attribute Documented knowledge Documented knowledge
can create can use archives
can be created by can be used by is archived by
Draft list Draft list Element type
ARIS Methods
11-267
Model Type
Source Object Type
Target Object Type
distributes has output of reads archives
is distributed by is output of is read by is archived by
Element type Element type Element type Entity type
ARIS Methods
11-268
Model Type
Source Object Type
Target Object Type
creates calls is predecessor of
is created by is called by follows
produces reads creates output to
is produced by is read by is output medium for
General resource General resource Information carrier
ARIS Methods
11-269
Model Type
Source Object Type
Target Object Type
Function Function
reads is measured by
is read by measures
Information carrier Key performance indicator instance
creates has knowledge of reads
is created by is available at is read by
Knowledge category Knowledge category Knowledge category
creates uses is carried out at
is created by is used by is performed in
List List Location
supports has output of reads
is supported by is output of is read by
Objective Package Package
Function Function
has output of produces
is output of is produced by
Product/Service Product/Service
ARIS Methods
11-270
Model Type
Source Object Type
Target Object Type
Relationship type Relationship type Relationship type Relationship type
leads to is represented by can use
is assigned to represents can be used by
Rule Screen Screen design
Technical term Technical term Technical term
ARIS Methods
11-271
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Function General resource General resource General resource General resource Group
reads is compared to is consumed by is defined
is read by is compared to consumes can be processed by/with
Technical term Event Function Function
uses development is under responsibility of is under technical responsibility of is used by can be used by
Function Application system Application system Application system Application system class
Group
Group Group
is user can be user
ARIS Methods
11-272
Model Type
Source Object Type
Target Object Type
Group
Group
Group Group
Group
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Group Group Group
Group Group Group
requires accesses is owner of
ARIS Methods
11-273
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Group Group Group
accesses is owner of provides
is accessed by has owner is provided by
accesses is owner of is specimen owner of can be user
is accessed by has owner has specimen owner can be used by
Complex object type Complex object type Complex object type Component
Group
Component
Group
Component
eEPC (column display) eEPC (column display) eEPC (column display)
Group Group Group
ARIS Methods
11-274
Model Type
Source Object Type
Target Object Type
Group Group Group
Group Group Group
Group
decides on
is decided by
Function
Group
Function
ARIS Methods
11-275
Model Type
Source Object Type
Target Object Type
Group Group
Function Function
Group Group
Function Function
Group Group
Group
provides
is provided by
Information carrier
Group
IT function
Group
IT function
Group Group
ARIS Methods
11-276
Model Type
Source Object Type
Target Object Type
Group
IT function type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Group
Module
Group
is user
Module
Group Group
Group
Module type
Group
accesses
Relationship type
ARIS Methods
11-277
Model Type
Source Object Type
Target Object Type
Group Group Group
Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type
stores
is stored on
stores
is stored on
Class
stores
is stored on
Cluster/Data model
stores
is stored on
Complex object type
stores
is stored on
COT attribute
stores
is stored on
Entity type
stores
is stored on
ERM attribute
ARIS Methods
11-278
Model Type
Source Object Type
Target Object Type
stores
is stored on
Relationship type
stores
is stored on
Technical term
Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier IT function
has state provides input for is used by is used by
is state of gets input from uses uses
Event Function Group Organizational unit
is used by is used by uses
uses uses is used by
Person type Position Class
uses uses uses
ARIS Methods
11-279
Model Type
Source Object Type
Target Object Type
uses uses supports
is used by is used by is supported by
Entity type ERM attribute Function
IT function IT function IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses uses can use uses
is used by is used by can be used by is used by
Relationship type Technical term Class Class
uses can use uses
is used by can be used by is used by
Complex object type COT attribute COT attribute
ARIS Methods
11-280
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses creates relates to supports
is used by is created by relates to (passive) is supported by
ERM attribute Event Event Event
supports when time limit is exceeded
supports when time limit is exceeded (passive) is supported by
Event
supports
Function
supports when time limit is exceeded (passive) can be used by
Function
IT function type
can use
Relationship type
ARIS Methods
11-281
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type Key performance indicator instance Knowledge category Knowledge category List Location
uses can use uses
is measured upon occurrence relates to
triggers measuring relates to (passive)
Event
Event
Location Location
Class Class
ARIS Methods
11-282
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of accesses
has owner is accessed by has owner is accessed by
Complex object type COT attribute COT attribute Entity type
has knowledge of requires accesses
is available at is required by is accessed by
Knowledge category Knowledge category Relationship type
ARIS Methods
11-283
Model Type
Source Object Type
Target Object Type
Module Module Module Module
uses uses uses uses
is used by is used by is used by is used by
Class Cluster/Data model Complex object type COT attribute
Module Module Module
uses uses supports
Module Module Module type
uses uses can use
is used by is used by can be used by
Relationship type Technical term Class
ARIS Methods
11-284
Model Type
Source Object Type
Target Object Type
uses can use can use
is used by can be used by can be used by
Module type Module type Module type Module type
can use can use can use creates
can be used by can be used by can be used by is created by
COT attribute Entity type ERM attribute Event
supports can use can use
is supported by can be used by can be used by
Function Relationship type Technical term
Operating resource Operating resource Operating resource
encompasses is alternative operating resource of is operating resource of
belongs to has alternative operating resource has operating resource
Application system Function
Function
ARIS Methods
11-285
Model Type
Source Object Type
Target Object Type
Operating resource Operating resource Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
encompasses encompasses is responsible for development of is technically responsible for is user can be user
belongs to belongs to development is under responsibility of is under technical responsibility of is used by can be used by
IT function Module Application system Application system Application system Application system class
Organizational unit
ARIS Methods
11-286
Model Type
Source Object Type
Target Object Type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
accesses is owner of has knowledge of requires accesses is owner of accesses
is owner of is specimen owner of provides
has owner has specimen owner is provided by
Complex object type Complex object type Component
ARIS Methods
11-287
Model Type
Source Object Type
Target Object Type
Organizational unit
Component
Organizational unit
Component
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
accesses is owner of is specimen owner of accesses
is accessed by has owner has specimen owner is accessed by
COT attribute COT attribute COT attribute Entity type
is specimen owner of is owner of provides
has specimen owner has owner is provided by
ERM attribute Event Event
ARIS Methods
11-288
Model Type
Source Object Type
Target Object Type
Function Function
Function
Function
must be informed about must be informed on cancellation must inform about result of uses
Function Function
ARIS Methods
11-289
Model Type
Source Object Type
Target Object Type
provides is responsible for development of is technically responsible for is user is responsible for development of is technically responsible for is user has knowledge of requires is responsible for development of is technically responsible for
is provided by development is under responsibility of is under technical responsibility of is used by development is under responsibility of is under technical responsibility of is used by is available at
IT function
IT function IT function type IT function type IT function type Knowledge category
is required by development is under responsibility of is under technical responsibility of
Knowledge category Module
Module
ARIS Methods
11-290
Model Type
Source Object Type
Target Object Type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type
is user can be user is responsible for development of is technically responsible for accesses is owner of
is used by can be used by development is under responsibility of is under technical responsibility of is accessed by has owner
Module type
Technical term Technical term Application system
Application system
Application system
ARIS Methods
11-291
Model Type
Source Object Type
Target Object Type
can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for accesses is owner of
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by has owner
Application system class Application system class Application system class Application system type Application system type Application system type Attribute type group Attribute type group
Authorization condition Authorization condition Class
ARIS Methods
11-292
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
accesses is owner of can be user is responsible for development of is technically responsible for accesses
is accessed by has owner can be used by development is under responsibility of is under technical responsibility of is accessed by
Complex object type Complex object type Component Component
Component
COT attribute
COT attribute Entity type Entity type
ARIS Methods
11-293
Model Type
Source Object Type
Target Object Type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
provides accepts carries out contributes to
is provided by is accepted by is carried out by is worked on by collaboration of
decides on
is decided by
Function
Function
is IT responsible for is technically responsible for must be informed about
is under IT responsibility of is under technical responsibility of result is forwarded to
Function Function
Function
ARIS Methods
11-294
Model Type
Source Object Type
Target Object Type
sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is available at
Function
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
must inform about result of can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for has knowledge of requires can be user
Function IT function IT function
IT function
IT function type IT function type IT function type Knowledge category
is required by can be used by
ARIS Methods
11-295
Model Type
Source Object Type
Target Object Type
Module
Module
Module type
eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display) eEPC (column display)
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Package Package
is owner of contains is input for
has owner is contained by has input of
ARIS Methods
11-296
Model Type
Source Object Type
Target Object Type
Person
Application system
Person
Application system
Person
Person Person
Person
Person
accesses
Person
is owner of
has owner
ARIS Methods
11-297
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of accesses
has owner is accessed by has owner is accessed by
Class Cluster/Data model Cluster/Data model Complex object type
has owner can be used by development is under responsibility of is under technical responsibility of is accessed by
Person
Component
Person
accesses
COT attribute
ARIS Methods
11-298
Model Type
Source Object Type
Target Object Type
is owner of is specimen owner of accesses
has owner has specimen owner is accessed by
COT attribute COT attribute Entity type
is owner of accesses is owner of is specimen owner of
has owner is accessed by has owner has specimen owner has owner is provided by is accepted by
Entity type ERM attribute ERM attribute ERM attribute
is owner of provides accepts
Person Person
carries out contributes to
is carried out by is worked on by collaboration of
Function Function
Person
decides on
is decided by
Function
ARIS Methods
11-299
Model Type
Source Object Type
Target Object Type
Person
Function
Person Person
Function Function
Person Person
Function Function
Person Person
Person
development is under responsibility of is under technical responsibility of is used by
IT function
Person
IT function
Person
is user
IT function
ARIS Methods
11-300
Model Type
Source Object Type
Target Object Type
Person
IT function type
Person
IT function type
Person
Module
Person
is user
Module
Person Person
Person
Module type
ARIS Methods
11-301
Model Type
Source Object Type
Target Object Type
Person Person type Person type
has owner can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
Technical term Application system Application system Application system Application system class Application system class Application system class Application system type
Person type
Person type
Person type
can be user
ARIS Methods
11-302
Model Type
Source Object Type
Target Object Type
Person type
Person type
is owner of provides accesses
has owner is provided by is accessed by
ARIS Methods
11-303
Model Type
Source Object Type
Target Object Type
Person type
Component
is owner of is owner of provides
has owner has owner is provided by
ARIS Methods
11-304
Model Type
Source Object Type
Target Object Type
Function Function
Person type
Function
Person type
Function
result is forwarded to sends information on cancellation to result is forwarded by is provided by
Function Function
must inform about result of provides
Function Information carrier
ARIS Methods
11-305
Model Type
Source Object Type
Target Object Type
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is available at is required by
Person type
IT function
Person type
Module Module
Person type
Module
ARIS Methods
11-306
Model Type
Source Object Type
Target Object Type
can be used by development is under responsibility of is under technical responsibility of is in conflict with is accessed by has owner
Person type
Module type
is in conflict with accesses is owner of
Person type Relationship type Relationship type
Person type Person type Position
accesses is owner of is responsible for development of
is accessed by has owner development is under responsibility of is under technical responsibility of is used by
Technical term Technical term Application system Application system Application system
Position
Position
is user
ARIS Methods
11-307
Model Type
Source Object Type
Target Object Type
Position Position
Position
Position Position
Position
Position Position
ARIS Methods
11-308
Model Type
Source Object Type
Target Object Type
provides accesses is owner of can be user
is provided by is accessed by has owner can be used by
Cluster/Data model Complex object type Complex object type Component
Position
Component
Position
Component
ARIS Methods
11-309
Model Type
Source Object Type
Target Object Type
Position
decides on
is decided by
Function
Position
Function
ARIS Methods
11-310
Model Type
Source Object Type
Target Object Type
Position Position
Function Function
Position Position
Function Function
Position Position
Position
provides
is provided by
Information carrier
Position
IT function
Position
IT function
Position Position
ARIS Methods
11-311
Model Type
Source Object Type
Target Object Type
Position
IT function type
Position
Module
Position
is user
Module
Position Position
Position
Module type
Position
accesses
Relationship type
ARIS Methods
11-312
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Product/Service Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type
is compared to is consumed by is input for is used by
is compared to consumes has input of uses
is managed by is managed by has state
manages manages is state of
Application system type Component Event
ARIS Methods
11-313
Model Type
Source Object Type
Target Object Type
Relationship type Rule Rule
lies on leads to activates
has information about is dependent on is activated by
Rule Screen Screen Screen
links can use can use can use
is linked by can be used by can be used by can be used by
Rule Class Cluster/Data model Complex object type
Screen Screen Screen
creates can use can use
is created by can be used by can be used by
Event Relationship type Technical term
ARIS Methods
11-314
Model Type
Source Object Type
Target Object Type
System organizational unit System organizational unit type Technical term Technical term Technical term
is assigned to can be assigned to has state is approved by is checked by
is assigned to can be assigned to is state of approves checks
Function Function
Technical term Technical term
is input for lies on
has input of has information about
Assignment Relationship eEPC (column display)
ARIS Methods
11.2.23 eEPC (instance)
11-315

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type Application system type Application system type can use can be used by can use can be used by can use supports is supported by can be used by uses is used by Technical terms instance Function instance Cluster instance Complex object COT attribute (instance) uses supports is supported by is used by uses is used by ERM attribute instance Function instance Relationship uses is used by uses is used by uses is used by uses is used by Cluster instance Complex object COT attribute (instance) Entity Target Object Type
ARIS Methods
11-316
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Application system type Application system type Application system type Application system type Application system type Cluster instance Cluster instance Cluster instance Cluster instance Cluster instance Complex object Complex object Complex object
can use can use supports
can be used by can be used by is supported by
Entity ERM attribute instance Function instance Relationship Technical terms instance Event instance Function instance
can use can use has state is approved by
can be used by can be used by is state of approves
is checked by is input for has current location is managed by has state is approved by
checks has input of is current location of manages is state of approves
Function instance Function instance Information carrier Application system type Event instance Function instance
ARIS Methods
11-317
Model Type
Source Object Type
Target Object Type
Complex object Complex object Complex object COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) Employee variable Employee variable Employee variable
is checked by is input for has current location has state is compared to provides value for is approved by
checks has input of is current location of is state of is compared to uses value of approves
Function instance Function instance Information carrier Event instance Event instance Event instance Function instance
Function instance Function instance Information carrier Employee variable Employee variable Employee variable
is different from is disciplinary superior to is technical superior to
is different from has the disciplinary superior has the technical superior
ARIS Methods
11-318
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
substitutes for carries out contributes to
is substituted by is carried out by is worked on by collaboration of
Employee variable Function instance Function instance Function instance Function instance Function instance Function instance
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Employee variable Employee variable Employee variable Employee variable Employee variable
must be informed about must inform about result of is employee variable is employee variable is employee variable
result is forwarded to result is forwarded by has employee variable has employee variable has employee variable
Function instance Function instance Group
Location Organizational unit
ARIS Methods
11-319
Model Type
Source Object Type
Target Object Type
Employee variable Employee variable Employee variable Entity Entity Entity Entity
is employee variable is employee variable is employee variable is managed by has state is approved by is checked by
has employee variable has employee variable has employee variable manages is state of approves checks
Application system type Event instance Function instance Function instance
Entity Entity ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance
is input for has current location has state
has input of is current location of is state of
Function instance Information carrier Event instance
Event instance Event instance Function instance
ARIS Methods
11-320
Model Type
Source Object Type
Target Object Type
ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance Event instance Event instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance
is checked by is input for has current location defines screen field activates is evaluated by archives
checks has input of is current location of has screen field is activated by evaluates is archived by
Function instance Function instance Information carrier Screen Function instance Rule instance Cluster instance
Cluster instance Cluster instance Cluster instance
distributes has output of archives
is distributed by is output of is archived by
Cluster instance Cluster instance Complex object
ARIS Methods
11-321
Model Type
Source Object Type
Target Object Type
Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance
Complex object Complex object Complex object
distributes has output of archives changes
is distributed by is output of is archived by is changed by
Complex object Complex object COT attribute (instance) COT attribute (instance)
COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) Draft list Draft list
has output of can create can use
is output of can be created by can be used by
ARIS Methods
11-322
Model Type
Source Object Type
Target Object Type
Entity Entity Entity
deletes distributes has output of archives
is deleted by is distributed by is output of is archived by
Entity Entity Entity ERM attribute instance
ERM attribute instance ERM attribute instance ERM attribute instance
distributes has output of creates
is distributed by is output of is created by
ERM attribute instance ERM attribute instance Event instance
ARIS Methods
11-323
Model Type
Source Object Type
Target Object Type
creates output to creates uses
is output medium for is created by is used by
Information carrier List List
is carried out at archives changes creates
is performed in is archived by is changed by is created by
Location Relationship Relationship Relationship
Relationship Relationship Relationship
Rule instance Screen Screen design
ARIS Methods
11-324
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Function instance Function instance Function instance Function instance Function instance Function instance General resource Group
Technical terms instance Technical terms instance Technical terms instance
deletes distributes has output of is defined
is deleted by is distributed by is output of can be processed by/with
Technical terms instance Technical terms instance Technical terms instance Function instance Application system
eEPC (instance)
Group
Application system
eEPC (instance) eEPC (instance) eEPC (instance)
Group Group Group
is used by can be used by development is under responsibility of
Application system Application system class Application system class
ARIS Methods
11-325
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Group
Group Group
Group
Group Group Group
Group Group Group
Complex object COT attribute (instance) COT attribute (instance)
Group Group
is specimen owner of accesses
has specimen owner is accessed by
COT attribute (instance) Entity
ARIS Methods
11-326
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Group Group Group
Entity ERM attribute instance ERM attribute instance
Group Group Group
is specimen owner of carries out contributes to
has specimen owner is carried out by is worked on by collaboration of
ERM attribute instance Function instance Function instance Function instance Function instance Function instance Function instance
Group Group
Group
Group
eEPC (instance)
Group
Function instance
ARIS Methods
11-327
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Group
sends information on cancellation to result is forwarded by is used by
Function instance
Group Group
Function instance Hardware component type
Group
IT function
eEPC (instance)
Group
IT function
Group Group
is used by development is under responsibility of is under technical responsibility of is used by development is under responsibility of
IT function IT function type IT function type IT function type Module
Group
Group Group
ARIS Methods
11-328
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Group
Module
Group Group Group
Group
Module type
Group Group
Relationship Relationship
Group Group Hardware component type Hardware component type
accesses is owner of stores
is accessed by has owner is stored on
Technical terms instance Technical terms instance Cluster instance
stores
is stored on
Complex object
ARIS Methods
11-329
Model Type
Source Object Type
Target Object Type
eEPC (instance)
stores
is stored on
COT attribute (instance)
eEPC (instance)
stores
is stored on
Entity
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Hardware component type Hardware component type Hardware component type Information carrier Information carrier IT function IT function
stores
is stored on
ERM attribute instance
stores
is stored on
Relationship
stores
is stored on
Technical terms instance
has state
is state of
Event instance
provides input for uses uses
gets input from is used by is used by
Function instance Cluster instance Complex object
uses uses
ARIS Methods
11-330
Model Type
Source Object Type
Target Object Type
uses supports uses
ERM attribute instance Function instance Relationship
IT function IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses uses uses uses
Technical terms instance Cluster instance Complex object COT attribute (instance)
uses uses supports
Entity ERM attribute instance Event instance
supports uses uses
is supported by is used by is used by
Function instance Relationship Technical terms instance
ARIS Methods
11-331
Model Type
Source Object Type
Target Object Type
List Module Module
provides input for uses uses
gets input from is used by is used by
Function instance Cluster instance Complex object
uses uses uses supports
is used by is used by is used by is supported by
COT attribute (instance) Entity ERM attribute instance Function instance Relationship Technical terms instance Cluster instance
uses uses can use
Complex object COT attribute (instance) Entity
ARIS Methods
11-332
Model Type
Source Object Type
Target Object Type
can use supports can use
can be used by is supported by can be used by
ERM attribute instance Function instance Relationship
Module type Operating resource Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
can use is defined is responsible for development of is technically responsible for is user can be user
can be used by can be processed by/with development is under responsibility of is under technical responsibility of is used by can be used by
Technical terms instance Function instance Application system Application system Application system Application system class
eEPC (instance)
Organizational unit
ARIS Methods
11-333
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
can be user is responsible for development of is technically responsible for accesses is owner of is specimen owner of accesses is owner of accesses
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner has specimen owner is accessed by has owner is accessed by
Application system type Application system type Application system type Cluster instance Cluster instance Cluster instance Complex object Complex object COT attribute (instance)
COT attribute (instance) COT attribute (instance) Entity
ARIS Methods
11-334
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Organizational unit
Function instance
ARIS Methods
11-335
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Organizational unit
Function instance
IT function
eEPC (instance)
Organizational unit
IT function
is user is responsible for development of is technically responsible for is user is responsible for development of
ARIS Methods
11-336
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Organizational unit
Module
Module type
Technical terms instance Technical terms instance Application system
Application system
ARIS Methods
11-337
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Application system
can be user is responsible for development of is technically responsible for accesses accesses
can be used by development is under responsibility of is under technical responsibility of is accessed by is accessed by
Application system type Application system type Application system type Cluster instance Complex object
accesses accesses
ARIS Methods
11-338
Model Type
Source Object Type
Target Object Type
accesses carries out has consulting role in is IT responsible for is technically responsible for can be user
is accessed by is carried out by is supported by consulting role of is under IT responsibility of is under technical responsibility of can be used by
ERM attribute instance Function instance Function instance Function instance Function instance IT function
IT function
eEPC (instance)
IT function
ARIS Methods
11-339
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Person
can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for accesses accesses
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by is accessed by
Module Module
Module
Module type
Relationship Technical terms instance
Application system
eEPC (instance)
Person
Application system
eEPC (instance)
Person
is user
is used by
Application system
ARIS Methods
11-340
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Person Person
Application system class Application system class Application system class Application system type Application system type Application system type Cluster instance Cluster instance
Person
Person Person
Person
Person Person
Complex object Complex object COT attribute (instance)
ARIS Methods
11-341
Model Type
Source Object Type
Target Object Type
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
COT attribute (instance) COT attribute (instance) Entity
has owner is accessed by has owner has specimen owner is carried out by is worked on by collaboration of
Entity ERM attribute instance ERM attribute instance ERM attribute instance Function instance Function instance Function instance Function instance Function instance
Person Person
Person Person
decides on has carried out
is decided by was carried out by
Person
ARIS Methods
11-342
Model Type
Source Object Type
Target Object Type
Person Person
Function instance Function instance Function instance Function instance Function instance Hardware component type
Person Person
Person Person
Person
IT function
Person
IT function
Person
is user
IT function
Person
IT function type
ARIS Methods
11-343
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Person
IT function type
Person Person
is used by development is under responsibility of is under technical responsibility of
IT function type Module
Person
Module
is used by can be used by development is under responsibility of is under technical responsibility of is accessed by
Person
Module type
Person
accesses
Relationship
Person Person
Relationship Technical terms instance
ARIS Methods
11-344
Model Type
Source Object Type
Target Object Type
Technical terms instance Application system Application system Application system Application system class Application system class Application system class Application system type
Person type
Person type
Person type
can be user
Person type
eEPC (instance)
Person type
eEPC (instance)
Person type
accesses
is accessed by
Cluster instance
ARIS Methods
11-345
Model Type
Source Object Type
Target Object Type
accesses accesses accesses
is accessed by is accessed by is accessed by
Complex object COT attribute (instance) Entity
accesses carries out contributes to
is accessed by is carried out by is worked on by collaboration of
Person type
Person type
eEPC (instance)
Person type
Function instance
ARIS Methods
11-346
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Person type
sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
Function instance
must inform about result of can be user is responsible for development of
Function instance IT function IT function
Person type
IT function
IT function type IT function type IT function type Module
Person type
Person type
can be user
Person type
Module
ARIS Methods
11-347
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Person type
Module
Person type
Module type
accesses accesses is responsible for development of
is accessed by is accessed by development is under responsibility of is under technical responsibility of is used by
Relationship Technical terms instance Application system Application system Application system
Position
Position
is user
Position Position
Application system class Application system class
ARIS Methods
11-348
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Position
Position Position
Position
Complex object COT attribute (instance) COT attribute (instance)
Position Position
ARIS Methods
11-349
Model Type
Source Object Type
Target Object Type
Position Position
Position
Position
eEPC (instance)
Position
Function instance
ARIS Methods
11-350
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Position
Function instance
Position Position
Position
IT function
eEPC (instance)
Position
IT function
Position Position
Position
Position Position
ARIS Methods
11-351
Model Type
Source Object Type
Target Object Type
eEPC (instance)
Position
Module
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Position
Module type
Position Position
Position Position Relationship
accesses is owner of is managed by
is accessed by has owner manages
Technical terms instance Technical terms instance Application system type
has state is approved by
is state of approves
Event instance Function instance
ARIS Methods
11-352
Model Type
Source Object Type
Target Object Type
Relationship Relationship Relationship
is checked by is input for has current location
checks has input of is current location of is dependent on is activated by is linked by is assigned to
Function instance Function instance Information carrier Event instance Function instance Rule instance Function instance
Rule instance Rule instance Rule instance System organizational unit System organizational unit type
leads to activates links is assigned to
can be assigned to
can be assigned to
Function instance
Technical terms instance Technical terms instance Technical terms instance Technical terms instance Technical terms instance
Event instance Function instance Function instance
is input for has current location
has input of is current location of
Function instance Information carrier
ARIS Methods
11-353
Assignment Relationship eEPC (instance)
Source Object Type Function instance
Target Object Type Function instance
ARIS Methods
11.2.24 eEPC (material flow)
11-354

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type uses supports is supported by is used by Attribute type group Function uses is used by uses supports is supported by is used by Relationship type Technical term Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by Cluster/Data model Complex object type COT attribute uses is used by uses is used by Attribute type group Class Target Object Type
ARIS Methods
11-355
Model Type
Source Object Type
Target Object Type
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Attribute type group Attribute type group
creates supports can use
is created by is supported by can be used by
Event Function Relationship type
ARIS Methods
11-356
Model Type
Source Object Type
Target Object Type
Attribute type group Attribute type group Authorization condition Authorization condition Business object Class Class
relates to is input for has state is approved by
has has input of is state of approves
Technical term Function Event Function
Class Class Class
Function Function Information carrier Event Function Function
ARIS Methods
11-357
Model Type
Source Object Type
Target Object Type
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type
is input for is used by lies on
has input of uses has information about
Function Group Information carrier Organizational unit Person type Position Application system type
is used by is used by is used by is managed by
uses uses uses manages
is managed by has state is approved by
manages is state of approves
Component Event Function
ARIS Methods
11-358
Model Type
Source Object Type
Target Object Type
Attribute type group Cluster/Data model Complex object type
can use can use can use supports
can be used by can be used by can be used by is supported by
COT attribute Entity type ERM attribute Function
Component Component Cost driver
can use can use influences
can be used by can be used by is influenced by
Event Event Event
ARIS Methods
11-359
Model Type
Source Object Type
Target Object Type
COT attribute Documented knowledge Documented knowledge Element type
lies on relates to is required for has state
has information about relates to (passive) requires is state of
Information carrier Event Function Event
Element type Element type Employee variable
is checked by is input for is different from
checks has input of is different from
Function Function Employee variable
ARIS Methods
11-360
Model Type
Source Object Type
Target Object Type
Employee variable
is disciplinary superior to
has the disciplinary superior
Employee variable
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
is technical superior to substitutes for accepts carries out
has the technical superior is substituted by is accepted by is carried out by
Employee variable Employee variable Function Function
contributes to
Function
decides on has consulting role in is IT responsible for is technically responsible for must be informed about
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to
Function Function
Function Function
Function
ARIS Methods
11-361
Model Type
Source Object Type
Target Object Type
Employee variable
sends information on cancellation to result is forwarded by has employee variable has employee variable has employee variable has employee variable has employee variable has employee variable manages manages is state of
Function
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Entity type Entity type Entity type
must inform about result of is employee variable is employee variable is employee variable is employee variable is employee variable is employee variable is managed by is managed by has state
Function Group Location Organizational unit Person Person type Position
is approved by is checked by
approves checks
Function Function
ARIS Methods
11-362
Model Type
Source Object Type
Target Object Type
is input for lies on belongs to
has input of has information about encompasses
Function Information carrier Attribute type group
Function Function Information carrier Screen Application system type Function
defines screen field activates activates
has screen field is activated by is activated by
ARIS Methods
11-363
Model Type
Source Object Type
Target Object Type
Event Event Event
is used by activates defines status
uses is activated by is defined
Group IT function type Material type
activates is used by is used by is used by
is activated by uses uses uses
Module type Organizational unit Organizational unit type Person
Event Event Event
is used by is used by corresponds to
uses uses corresponds to
Person type Position Product/Service
is evaluated by activates archives
evaluates is activated by is archived by
Rule Screen Attribute type group
ARIS Methods
11-364
Model Type
Source Object Type
Target Object Type
distributes has output of reads has knowledge of
is distributed by is output of is read by is available at
Attribute type group Attribute type group Attribute type group Authorization condition
has output of reads archives
is output of is read by is archived by
Business object Business object Class
Class Class Class
ARIS Methods
11-365
Model Type
Source Object Type
Target Object Type
Class Class Class
archives changes creates deletes
is archived by is changed by is created by is deleted by
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
ARIS Methods
11-366
Model Type
Source Object Type
Target Object Type
reads can support belongs to archives
is read by can be supported by is assigned to is archived by
Complex object type Component Cost category COT attribute
ARIS Methods
11-367
Model Type
Source Object Type
Target Object Type
creates reads can create
is created by is read by can be created by
Documented knowledge Documented knowledge Draft list
can use archives changes creates
can be used by is archived by is changed by is created by
Draft list Element type Element type Element type
Element type Entity type Entity type
ARIS Methods
11-368
Model Type
Source Object Type
Target Object Type
Entity type Entity type ERM attribute ERM attribute
has output of reads creates
is output of is read by is created by
ARIS Methods
11-369
Model Type
Source Object Type
Target Object Type
calls is predecessor of produces
is called by follows is produced by
Function Function General resource
reads creates output to reads is measured by
is read by is output medium for is read by measures
General resource Information carrier Information carrier Key performance indicator instance
Function
creates
is created by
Knowledge category
has knowledge of reads creates
is available at is read by is created by
Knowledge category Knowledge category List
Function Function
uses is carried out at
is used by is performed in
List Location
ARIS Methods
11-370
Model Type
Source Object Type
Target Object Type
creates supports has output of
is created by is supported by is output of
Material type Objective Package
reads requires has output of produces
is read by is required by is output of is produced by
Package Packaging material type Product/Service Product/Service
ARIS Methods
11-371
Model Type
Source Object Type
Target Object Type
reads leads to is represented by
is read by is assigned to represents
Relationship type Rule Screen
Function Function
can use requires
can be used by is required by
Screen design Technical operating supply
Function
requires alternatively
is required alternatively
Technical operating supply
Function
requires
is required by
Technical operating supply type
Function
eEPC (material flow) eEPC (material flow) eEPC (material flow)
ARIS Methods
11-372
Model Type
Source Object Type
Target Object Type
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
reads accesses accesses alternatively
is read by is accessed by is accessed alternatively by is accessed by is accessed alternatively by is required by
Technical term Transport system Transport system Transport system type Transport system type Warehouse equipment
Function Function
accesses accesses alternatively
Function
requires
Function Function
requires alternatively requires
is required alternatively is required by
Warehouse equipment Warehouse equipment type
ARIS Methods
11-373
Model Type
Source Object Type
Target Object Type
Function
Warehouse equipment type
General resource General resource General resource General resource Group
is compared to is consumed by is defined is used by
is compared to consumes can be processed by/with uses
Application system
Group
Application system
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Group Group Group
Application system Application system class Application system class Application system class
Group
ARIS Methods
11-374
Model Type
Source Object Type
Target Object Type
Group Group
Group
Group Group Group
Group Group Group
Group Group Group
ARIS Methods
11-375
Model Type
Source Object Type
Target Object Type
Group Group Group
is accessed by has owner has specimen owner can be used by development is under responsibility of is under technical responsibility of
Complex object type Complex object type Complex object type Component Component
Group Group
Group
Component
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Group Group Group
is accessed by has owner has specimen owner is accessed by has owner is accessed by
Group Group Group
ARIS Methods
11-376
Model Type
Source Object Type
Target Object Type
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Group Group Group
is owner of is specimen owner of is owner of
has owner has specimen owner has owner
Group
decides on
is decided by
Function
Group
Function
Group Group
Function Function
Group
Function
ARIS Methods
11-377
Model Type
Source Object Type
Target Object Type
Group
Function
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Group Group
Group Group
Group
IT function
Group Group
Group
Group
is user
Group
has knowledge of
is available at
Knowledge category
ARIS Methods
11-378
Model Type
Source Object Type
Target Object Type
Group Group
requires is responsible for development of
is required by development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of is accessed by
Group
Module
Group Group Group
Group
Module type
Group
accesses
Relationship type
Group Group Group
ARIS Methods
11-379
Model Type
Source Object Type
Target Object Type
stores
is stored on
stores
is stored on
Class
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
stores
is stored on
Cluster/Data model
stores
is stored on
Complex object type
stores
is stored on
COT attribute
stores
is stored on
Entity type
stores
is stored on
ERM attribute
stores
is stored on
Relationship type
stores
is stored on
Technical term
ARIS Methods
11-380
Model Type
Source Object Type
Target Object Type
Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier IT function
has state provides input for is used by
is state of gets input from uses
Event Function Group
is used by is used by is used by uses
uses uses uses is used by
Organizational unit Person type Position Attribute type group
uses uses uses
uses uses uses
ARIS Methods
11-381
Model Type
Source Object Type
Target Object Type
supports uses uses
is supported by is used by is used by
Function Relationship type Technical term
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses can use uses can use
is used by can be used by is used by can be used by
Attribute type group Class Class Cluster/Data model
uses can use uses
ARIS Methods
11-382
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses can use uses
creates relates to supports supports when time limit is exceeded
is created by relates to (passive) is supported by supports when time limit is exceeded (passive) is supported by supports when time limit is exceeded (passive) can be used by is used by
Function Function
can use uses
ARIS Methods
11-383
Model Type
Source Object Type
Target Object Type
IT function type IT function type Key performance indicator instance Knowledge category Knowledge category List Location Location
can use uses is measured upon occurrence relates to is required for
can be used by is used by triggers measuring relates to (passive) requires
Technical term Technical term Event
Event Function
provides input for accesses is owner of
gets input from is accessed by has owner
Function Attribute type group Attribute type group
Location Location
ARIS Methods
11-384
Model Type
Source Object Type
Target Object Type
ERM attribute ERM attribute Knowledge category
Knowledge category Relationship type Relationship type
ARIS Methods
11-385
Model Type
Source Object Type
Target Object Type
Location Location Material type
accesses is owner of is consumed
is accessed by has owner consumes
Technical term Technical term Function
Material type Material type Module Module
is not consumed is partly consumed uses uses
does not consume partly consumes is used by is used by
Function Function Attribute type group Class
uses uses uses
uses uses supports
ARIS Methods
11-386
Model Type
Source Object Type
Target Object Type
uses uses uses
Relationship type Technical term Attribute type group
can use uses can use can use
can be used by is used by can be used by can be used by
Class Class Cluster/Data model Complex object type
ARIS Methods
11-387
Model Type
Source Object Type
Target Object Type
Module type Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Organizational unit
can use encompasses is alternative operating resource of is operating resource of encompasses
can be used by belongs to has alternative operating resource has operating resource belongs to
Technical term Application system Function
encompasses can encompass is alternative operating resource of is operating resource of can encompass can encompass is responsible for development of
belongs to can belong to has alternative operating resource has operating resource can belong to can belong to development is under responsibility of
Module Application system type Function
Function
IT function type Module type Application system
ARIS Methods
11-388
Model Type
Source Object Type
Target Object Type
Organizational unit
Application system
is user can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for accesses
ARIS Methods
11-389
Model Type
Source Object Type
Target Object Type
accesses is owner of is specimen owner of provides
is accessed by has owner has specimen owner is provided by
Component
Organizational unit
Component
ARIS Methods
11-390
Model Type
Source Object Type
Target Object Type
is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner
ARIS Methods
11-391
Model Type
Source Object Type
Target Object Type
eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow) eEPC (material flow)
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of uses
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is used by
Function Function
Function Function
Function Function
Function
provides is responsible for development of is technically responsible for
IT function
ARIS Methods
11-392
Model Type
Source Object Type
Target Object Type
is user is responsible for development of is technically responsible for is user has knowledge of requires
is used by development is under responsibility of is under technical responsibility of is used by is available at is required by
IT function IT function type IT function type IT function type Knowledge category Knowledge category
Module
Organizational unit
Module
ARIS Methods
11-393
Model Type
Source Object Type
Target Object Type
Organizational unit
Module type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
Relationship type Relationship type Technical term Technical term
can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for
Application system Application system Application system Application system class Application system class Application system class
ARIS Methods
11-394
Model Type
Source Object Type
Target Object Type
can be user is responsible for development of is technically responsible for accesses is owner of has knowledge of requires accesses is owner of
ARIS Methods
11-395
Model Type
Source Object Type
Target Object Type
is owner of can be user is responsible for development of is technically responsible for accesses is owner of
Component
ARIS Methods
11-396
Model Type
Source Object Type
Target Object Type
Function Function
Function
Function
must be informed about must be informed on cancellation must inform about result of can be user
result is forwarded to sends information on cancellation to result is forwarded by can be used by
Function Function
ARIS Methods
11-397
Model Type
Source Object Type
Target Object Type
IT function
IT function
IT function type
has knowledge of requires can be user
is available at is required by can be used by
Module
Module
can be user
can be used by
Module type
ARIS Methods
11-398
Model Type
Source Object Type
Target Object Type
Module type
Module type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Package Package Person
contains is input for is responsible for development of
is contained by has input of development is under responsibility of is under technical responsibility of is used by
Function Function Application system Application system Application system
Person
Person
is user
ARIS Methods
11-399
Model Type
Source Object Type
Target Object Type
Person Person
Person
Person Person
Person
Person Person
ARIS Methods
11-400
Model Type
Source Object Type
Target Object Type
is accessed by has owner can be used by development is under responsibility of is under technical responsibility of is accessed by
Person
Component
Person
accesses
COT attribute
ARIS Methods
11-401
Model Type
Source Object Type
Target Object Type
is specimen owner of is owner of provides accepts
has specimen owner has owner is provided by is accepted by
ERM attribute Event Event Function
Person Person
Function Function
Person Person
is decided by is supported by consulting role of is under IT responsibility of
Function Function
Person
Function
ARIS Methods
11-402
Model Type
Source Object Type
Target Object Type
Person
Function
Person Person
Function Function
Person Person
Person
development is under responsibility of is under technical responsibility of is used by development is under responsibility of is under technical responsibility of
IT function
Person
IT function
Person Person
IT function IT function type IT function type
Person
ARIS Methods
11-403
Model Type
Source Object Type
Target Object Type
is user has knowledge of requires
is used by is available at is required by
IT function type Knowledge category Knowledge category
Person
Module
Person
Module
Person
is user
Module
Person Person
Person
Module type
Person Person
ARIS Methods
11-404
Model Type
Source Object Type
Target Object Type
Person Person Person type
Person type
Application system Application system Application system class
Person type
Person type
can be user
Person type
Person type
Person type
ARIS Methods
11-405
Model Type
Source Object Type
Target Object Type
has owner can be used by development is under responsibility of
ARIS Methods
11-406
Model Type
Source Object Type
Target Object Type
Person type
Component
Person type
contributes to
Function
ARIS Methods
11-407
Model Type
Source Object Type
Target Object Type
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is provided by can be used by development is under responsibility of is under technical responsibility of
Function Function
Function Function
Function Function
Person type
Function
provides can be user is responsible for development of
Information carrier IT function IT function
Person type
IT function
ARIS Methods
11-408
Model Type
Source Object Type
Target Object Type
Person type
Person type
Module
Person type
Module
Person type
Module type
ARIS Methods
11-409
Model Type
Source Object Type
Target Object Type
is in conflict with is accessed by has owner
is accessed by has owner development is under responsibility of is under technical responsibility of is used by can be used by
Technical term Technical term Application system Application system Application system Application system class
Position
Position Position
is user can be user
Position
Position
ARIS Methods
11-410
Model Type
Source Object Type
Target Object Type
Position Position
Position
ARIS Methods
11-411
Model Type
Source Object Type
Target Object Type
Position
Component
Position
Component
Position
accesses
COT attribute
ARIS Methods
11-412
Model Type
Source Object Type
Target Object Type
Position Position
Function Function
Position
Function
Position
Function
Position
Function
ARIS Methods
11-413
Model Type
Source Object Type
Target Object Type
Position
Function
Position Position
Position Position
Position
IT function
Position Position
Position
Position
is user
Position
has knowledge of
is available at
Knowledge category
ARIS Methods
11-414
Model Type
Source Object Type
Target Object Type
Position Position
Position
Module
Position
Module type
Position
accesses
Relationship type
ARIS Methods
11-415
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Product/Service Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Rule Rule
is compared to is consumed by is input for
is compared to consumes has input of
is used by is managed by is managed by has state
uses manages manages is state of
Function Application system type Component Event
ARIS Methods
11-416
Model Type
Source Object Type
Target Object Type
Rule Screen Screen
links can use can use
is linked by can be used by can be used by
Rule Class Cluster/Data model
Screen Screen Screen Screen
is assigned to can be assigned to
Function Function
ARIS Methods
11-417
Model Type
Source Object Type
Target Object Type
encompasses
belongs to
Application system
encompasses
belongs to
IT function
Technical operating supply Technical operating supply type Technical operating supply type Technical operating supply type Technical term
encompasses
belongs to
Module
can encompass
can belong to
can encompass
can belong to
IT function type
can encompass
can belong to
Module type
has state
is state of
Event
Technical term
lies on
Information carrier
ARIS Methods
11-418
Model Type
Source Object Type
Target Object Type
Transport system Transport system Transport system Transport system type Transport system type Transport system type Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment type Warehouse equipment type Warehouse equipment type
encompasses encompasses encompasses
belongs to belongs to belongs to
Application system IT function Module
can encompass can encompass can encompass encompasses
can belong to can belong to can belong to belongs to
Application system type IT function type Module type Application system
encompasses encompasses can encompass
belongs to belongs to can belong to
IT function Module Application system type
can encompass
can belong to
IT function type
can encompass
can belong to
Module type
ARIS Methods
11-419
Source Object Type
Target Object Type
Function
is processoriented superior
is processoriented subordinate
Function
ARIS Methods
11.2.26 eEPC (table display)
11-482

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type uses supports is supported by is used by Attribute type group Function uses is used by uses supports is supported by is used by Relationship type Technical term Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by Cluster/Data model Complex object type COT attribute uses is used by uses is used by Attribute type group Class Target Object Type
ARIS Methods
11-483
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-484
Model Type
Source Object Type
Target Object Type
Class Class Class
ARIS Methods
11-485
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-486
Model Type
Source Object Type
Target Object Type
Event Event Event
ARIS Methods
11-487
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-488
Model Type
Source Object Type
Target Object Type
Employee variable
Employee variable
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
contributes to
Function
Function Function
Function Function
Function
ARIS Methods
11-489
Model Type
Source Object Type
Target Object Type
Employee variable
Function
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
approves checks
Function Function
ARIS Methods
11-490
Model Type
Source Object Type
Target Object Type
is compared to provides value for is approved by is checked by
is compared to uses value of approves checks
Event Event Function Function
is input for lies on defines screen field
has input of has information about has screen field is activated by is activated by uses
Function Information carrier Screen
Event Event Event
ARIS Methods
11-491
Model Type
Source Object Type
Target Object Type
Event Event Event
uses uses uses uses
Organizational unit type Person Person type Position
Event Event Event
corresponds to is evaluated by activates
corresponds to evaluates is activated by
Product/Service Rule Screen
ARIS Methods
11-492
Model Type
Source Object Type
Target Object Type
reads has knowledge of has output of reads
is read by is available at is output of is read by
Attribute type group Authorization condition Business object Business object
Class Class Class
Class Class Class
ARIS Methods
11-493
Model Type
Source Object Type
Target Object Type
creates deletes distributes has output of
is created by is deleted by is distributed by is output of
ARIS Methods
11-494
Model Type
Source Object Type
Target Object Type
belongs to archives changes creates
is assigned to is archived by is changed by is created by
Cost category COT attribute COT attribute COT attribute
reads creates reads
is read by is created by is read by
ARIS Methods
11-495
Model Type
Source Object Type
Target Object Type
can create can use archives
can be created by can be used by is archived by
Draft list Draft list Element type
changes creates deletes distributes
is changed by is created by is deleted by is distributed by
Element type Element type Entity type
ARIS Methods
11-496
Model Type
Source Object Type
Target Object Type
creates calls is predecessor of
is created by is called by follows
ARIS Methods
11-497
Model Type
Source Object Type
Target Object Type
produces reads creates output to
is produced by is read by is output medium for is read by measures
General resource General resource Information carrier Information carrier Key performance indicator instance
Function Function
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
List List Location
Function Function
supports has output of
is supported by is output of
Objective Package
ARIS Methods
11-498
Model Type
Source Object Type
Target Object Type
reads has output of produces
is read by is output of is produced by
Package Product/Service Product/Service
Relationship type Relationship type Relationship type Relationship type
Rule Screen Screen design
ARIS Methods
11-499
Model Type
Source Object Type
Target Object Type
is compared to is consumed by is defined
is compared to consumes can be processed by/with
uses development is under responsibility of
ARIS Methods
11-500
Model Type
Source Object Type
Target Object Type
Group
Application system
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Group Group Group
Group
Group Group
Group
Group
accesses
Group Group
ARIS Methods
11-501
Model Type
Source Object Type
Target Object Type
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Group Group Group
accesses is owner of provides accesses
is accessed by has owner is provided by is accessed by
Cluster/Data model Cluster/Data model Cluster/Data model Complex object type
Group Group Group
is owner of is specimen owner of can be user
has owner has specimen owner can be used by
Group
Component
Group
Component
ARIS Methods
11-502
Model Type
Source Object Type
Target Object Type
Group Group Group
Group Group Group
Group Group Group
ARIS Methods
11-503
Model Type
Source Object Type
Target Object Type
Group Group
Function Function
Group Group
Function Function
Group Group
Function Function
Group
Function
Group
uses
eEPC (table display) eEPC (table display) eEPC (table display)
Group Group
Group
IT function
ARIS Methods
11-504
Model Type
Source Object Type
Target Object Type
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Group Group
is used by development is under responsibility of is under technical responsibility of is used by is available at is required by
IT function IT function type IT function type IT function type Knowledge category Knowledge category
Group
Group Group Group
Group
Module
Group
Module
Group Group Group
ARIS Methods
11-505
Model Type
Source Object Type
Target Object Type
Group
Module type
stores
is stored on
stores
is stored on
Class
stores
is stored on
Cluster/Data model
stores
is stored on
Complex object type
stores
is stored on
COT attribute
ARIS Methods
11-506
Model Type
Source Object Type
Target Object Type
stores
is stored on
Entity type
stores
is stored on
ERM attribute
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Hardware component type Hardware component type Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier IT function
stores
is stored on
Relationship type
stores
is stored on
Technical term
has state
is state of
Event
provides input for is used by is used by
gets input from uses uses
Function Group Organizational unit
Person type Position Attribute type group
ARIS Methods
11-507
Model Type
Source Object Type
Target Object Type
uses uses uses
IT function IT function IT function IT function
uses uses uses
ARIS Methods
11-508
Model Type
Source Object Type
Target Object Type
uses can use uses
can use uses can use uses
can be used by is used by can be used by is used by
can use uses creates
can be used by is used by is created by
relates to supports
relates to (passive) is supported by
Event Event
ARIS Methods
11-509
Model Type
Source Object Type
Target Object Type
IT function type
Event
eEPC (table display) eEPC (table display)
supports
Function
supports when time limit is exceeded (passive) can be used by is used by
Function
IT function type IT function type IT function type IT function type Key performance indicator instance Knowledge category Knowledge category List
can use uses
can use uses is measured upon occurrence relates to
can be used by is used by triggers measuring relates to (passive)
Event
is required for provides input for
requires gets input from
Function Function
ARIS Methods
11-510
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-511
Model Type
Source Object Type
Target Object Type
has knowledge of requires accesses is owner of
is available at is required by is accessed by has owner
Knowledge category Knowledge category Relationship type Relationship type
Location Location Module
accesses is owner of uses
is accessed by has owner is used by
Technical term Technical term Attribute type group
uses uses uses
ARIS Methods
11-512
Model Type
Source Object Type
Target Object Type
uses uses uses
Module Module Module Module type
supports uses uses uses
is supported by is used by is used by is used by
Function Relationship type Technical term Attribute type group
ARIS Methods
11-513
Model Type
Source Object Type
Target Object Type
can use creates supports
can be used by is created by is supported by
ERM attribute Event Function
Module type Module type Operating resource Operating resource Operating resource Operating resource Operating resource Organizational unit Organizational unit
can use can use encompasses is alternative operating resource of is operating resource of encompasses encompasses is responsible for development of is technically responsible for
can be used by can be used by belongs to has alternative operating resource has operating resource belongs to belongs to development is under responsibility of is under technical responsibility of
Relationship type Technical term Application system Function
Function
IT function Module Application system Application system
ARIS Methods
11-514
Model Type
Source Object Type
Target Object Type
is user can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for accesses
ARIS Methods
11-515
Model Type
Source Object Type
Target Object Type
is owner of is specimen owner of provides accesses
has owner has specimen owner is provided by is accessed by
is owner of can be user is responsible for development of is technically responsible for accesses
has owner can be used by development is under responsibility of is under technical responsibility of is accessed by
Component
COT attribute
ARIS Methods
11-516
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of is specimen owner of is owner of provides accepts
has owner is accessed by has owner has specimen owner has owner is provided by is accepted by
Function Function
decides on
is decided by
Function
ARIS Methods
11-517
Model Type
Source Object Type
Target Object Type
Organizational unit
Function
Function Function
Function Function
provides
is provided by
Information carrier
IT function
Organizational unit
IT function
Organizational unit
is user
is used by
IT function
ARIS Methods
11-518
Model Type
Source Object Type
Target Object Type
Organizational unit
IT function type
Organizational unit
IT function type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
Module
Module
Module type
ARIS Methods
11-519
Model Type
Source Object Type
Target Object Type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
is owner of can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for can be user
ARIS Methods
11-520
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-521
Model Type
Source Object Type
Target Object Type
can be user is responsible for development of is technically responsible for accesses is owner of accesses
Component Component
Component
has owner is provided by is accepted by
ARIS Methods
11-522
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
Function Function
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by can be used by development is under responsibility of
Function Function
Function Function
Function
Function
must inform about result of can be user is responsible for development of
ARIS Methods
11-523
Model Type
Source Object Type
Target Object Type
IT function
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
is available at is required by can be used by
Module
Module
ARIS Methods
11-524
Model Type
Source Object Type
Target Object Type
Module type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Package Package Person
is contained by has input of development is under responsibility of is under technical responsibility of is used by
Function Function Application system Application system Application system
Person
Person
is user
Person
can be user
can be used by
ARIS Methods
11-525
Model Type
Source Object Type
Target Object Type
Person
Person
Person Person
Person
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
ARIS Methods
11-526
Model Type
Source Object Type
Target Object Type
Person
Component
Person Person
is specimen owner of accesses is owner of
has specimen owner is accessed by has owner
ARIS Methods
11-527
Model Type
Source Object Type
Target Object Type
is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by
is owner of provides accepts carries out
Person
contributes to
Function
Person Person
Function Function
Person Person
Function Function
ARIS Methods
11-528
Model Type
Source Object Type
Target Object Type
Person Person
Function Function
Person Person
Person
development is under responsibility of is under technical responsibility of is used by development is under responsibility of is under technical responsibility of is used by
IT function
Person
IT function
Person Person
Person
Person
is user
Person
has knowledge of
is available at
Knowledge category
ARIS Methods
11-529
Model Type
Source Object Type
Target Object Type
Person Person
Person
Module
Person
Module type
Person
accesses
Relationship type
ARIS Methods
11-530
Model Type
Source Object Type
Target Object Type
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by
Application system Application system Application system Application system class Application system class Application system class Application system type Application system type Application system type Attribute type group
Person type
Person type
Person type
Person type
accesses
Person type
is owner of
has owner
ARIS Methods
11-531
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of provides
has owner is accessed by has owner is provided by
Class Cluster/Data model Cluster/Data model Cluster/Data model
Person type
Component
Person type
Component
ARIS Methods
11-532
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of is owner of
has owner is accessed by has owner has owner
Entity type ERM attribute ERM attribute Event
Person type
contributes to
Function
Person type
decides on
is decided by
Function
ARIS Methods
11-533
Model Type
Source Object Type
Target Object Type
Person type
Function
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is provided by
Function Function
Function Function
Person type
IT function
Person type
can be user
IT function type
ARIS Methods
11-534
Model Type
Source Object Type
Target Object Type
Person type
IT function type
Person type
IT function type
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
has knowledge of requires can be user is responsible for development of
is available at is required by can be used by development is under responsibility of is under technical responsibility of can be used by
Knowledge category Knowledge category Module Module
Person type
Module
Person type
can be user
Module type
Person type
Module type
Person type
Module type
Person type
is in conflict with
is in conflict with
Person type
ARIS Methods
11-535
Model Type
Source Object Type
Target Object Type
Person type Position
has owner development is under responsibility of is under technical responsibility of
Technical term Application system
Position
Application system
is used by can be used by development is under responsibility of is under technical responsibility of can be used by
Application system Application system class Application system class Application system class Application system type
Position
Position
can be user
ARIS Methods
11-536
Model Type
Source Object Type
Target Object Type
Position
Position
ARIS Methods
11-537
Model Type
Source Object Type
Target Object Type
Position
Component
Position Position
ARIS Methods
11-538
Model Type
Source Object Type
Target Object Type
Position Position
Function Function
eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display) eEPC (table display)
Position Position
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to
Function Function
Position Position
Function Function
Position
Function
Position
Function
ARIS Methods
11-539
Model Type
Source Object Type
Target Object Type
Position Position
result is forwarded by is used by
Position Position
Position
IT function
Position Position
Position
Position
is user
Position Position
Knowledge category Knowledge category
ARIS Methods
11-540
Model Type
Source Object Type
Target Object Type
Position
Module
Position
Module
Position
Module type
Position Position
Position Position Product/Service
accesses is owner of is compared to
is accessed by has owner is compared to
ARIS Methods
11-541
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Rule Rule Rule
is consumed by is input for is used by
consumes has input of uses
is managed by is managed by has state is approved by
manages manages is state of approves
Application system type Component Event Function
Function Function Information carrier Event Function Rule
leads to activates links
is dependent on is activated by is linked by
ARIS Methods
11-542
Model Type
Source Object Type
Target Object Type
can use can use can use creates
can be used by can be used by can be used by is created by
COT attribute Entity type ERM attribute Event
Screen Screen System organizational unit System organizational unit type
can use can use is assigned to
can be used by can be used by is assigned to
can be assigned to
can be assigned to
Function
has state is approved by
is state of approves
Event Function
ARIS Methods
11-543
Model Type
Source Object Type
Target Object Type
Assignment Relationship eEPC (table display)
ARIS Methods
11.2.27 eERM
11-544
11.2.27 eERM
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) eERM eERM eERM Attribute type group Attribute type group Cluster/Data model eERM eERM COT attribute Entity type corresponds to is subtype of corresponds to has as subtype is attribute type group is attribute type group has link to has attribute type group has attribute type group has link to Relationship type Cluster/Data model ERM attribute Generalization type eERM eERM eERM eERM Entity type Entity type Enumeration ERM attribute is supertype of defines has value belongs to has as supertype is defined by is value of encompasses Generalization type Relationship type Enumeration list occurrence Attribute type group eERM eERM eERM ERM attribute ERM attribute ERM attribute is describing for is foreign key for is primary key for eERM eERM ERM attribute ERM attribute has has has foreign key has primary key is assigned to is assigned to Enumeration ERM domain Entity type Entity type is described by Entity type Entity type Target Object Type
ARIS Methods
11.2.27 eERM
11-545
Model Type
Source Object Type
Target Object Type
eERM eERM eERM
has has is describing for
is assigned to is assigned to is described by
Measurement unit Measurement unit number Relationship type
eERM eERM eERM eERM
ERM attribute ERM attribute Function Generalization type
is foreign key for is primary key for no (out) differentiates according to value of
has foreign key has primary key no (in) is characteristic for
Relationship type Relationship type Class ERM attribute
eERM eERM eERM
Measurement unit number Measurement unit number Relationship type
has has is subtype of
is assigned to is assigned to has as subtype
ERM domain Measurement unit Generalization type
eERM eERM
is supertype of defines
has as supertype is defined by
Generalization type Relationship type
ARIS Methods
11.2.27 eERM
11-546
Source Object Type
Target Object Type
eERM eERM eERM
eERM eERM eERM eERM
Cluster/Data model Cluster/Data model Enumeration Information carrier
consists of consists of has value lies on
is part of is part of is value of has information about
Generalization type Relationship type Enumeration list occurrence Cluster/Data model Entity type ERM attribute Relationship type Cluster/Data model Entity type ERM attribute
eERM eERM eERM
lies on lies on lies on
has information about has information about has information about
eERM eERM eERM
defines screen field defines screen field defines screen field
has screen field has screen field has screen field
ARIS Methods
11.2.28 eERM attribute allocation diagram
11-547
Source Object Type
Target Object Type
eERM eERM eERM
Screen Screen design Screen design
has screen field has screen field has screen field has screen field has screen field
Relationship type Cluster/Data model Entity type
eERM eERM
Screen design Screen design
defines screen field defines screen field
ERM attribute Relationship type

Model Type Source Object Type eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram Enumeration has value is value of Enumeration list occurrence COT attribute corresponds to corresponds to ERM attribute Attribute type group is attribute type group has attribute type group Relationship type Attribute type group Relationship Type (active) is attribute type group Relationship Type (passive) has attribute type group Entity type Target Object Type
ARIS Methods
11-548
Model Type
Source Object Type
Target Object Type
eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram
ERM attribute
belongs to
encompasses
ERM attribute
is describing for
is described by
Entity type
ERM attribute
is foreign key for
has foreign key has primary key is assigned to
Entity type
ERM attribute
is primary key for
Entity type
ERM attribute
has
Enumeration
ERM attribute
has
is assigned to
ERM domain
ERM attribute
has
is assigned to
Measurement unit
ERM attribute
has
is assigned to
Measurement unit number
ERM attribute
is describing for
is described by
Relationship type
ARIS Methods
11-549
Model Type
Source Object Type
Target Object Type
eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram
ERM attribute
is foreign key for
has foreign key
Relationship type
ERM attribute
is primary key for
has primary key
Relationship type
Function
no (out)
no (in)
Class
Generalization type Measurement unit number Measurement unit number
differentiates according to value of has
is characteristic for is assigned to
ERM attribute
ERM domain
has
is assigned to
Measurement unit
Assignment Relationship eERM attribute allocation diagram eERM attribute allocation diagram
Source Object Type Entity type
Relationship Type (active) is describing for
Relationship Type (passive) is described by
Target Object Type ERM attribute
Entity type
is foreign key for
has foreign key
ERM attribute
ARIS Methods
11.2.29 Event diagram
11-550
Source Object Type
Target Object Type
eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram
Entity type
is primary key for
has primary key
ERM attribute
Enumeration
has value
is value of
Enumeration list occurrence
Generalization type Relationship type Relationship type Relationship type
differentiates according to value of is describing for is foreign key for is primary key for
is characteristic for is described by
ERM attribute
ERM attribute
has foreign key has primary key
ERM attribute
ERM attribute

Model Type Source Object Type Event diagram Event diagram Application system type Application system type can use can be used by Cluster/Data model Relationship Type (active) can use Relationship Type (passive) can be used by Class Target Object Type
ARIS Methods
11-551
Model Type
Source Object Type
Target Object Type
Event diagram Event diagram Event diagram
Event diagram Event diagram Event diagram Event diagram
can use creates can use can use
can be used by is created by can be used by can be used by
ERM attribute Event Information carrier Relationship type
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Application system type Class Cluster/Data model Complex object type COT attribute COT attribute COT attribute
can use has state has state has state has state is compared to provides value for
can be used by is state of is state of is state of is state of is compared to uses value of
Technical term Event Event Event Event Event Event
ARIS Methods
11-552
Model Type
Source Object Type
Target Object Type
Documented knowledge Element type Element type Element type
relates to has state is compared to provides value for
relates to (passive) is state of is compared to uses value of
has state has state is compared to provides value for
is state of is state of is compared to uses value of
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Event Event Event Event Event Event Event Event Event
activates has subordinate event links is used by activates activates is used by is used by is used by
is activated by is subordinate event of is linked to uses is activated by is activated by uses uses uses
Application system type Event Event Group IT function type Module type Organizational unit Organizational unit type Person
ARIS Methods
11-553
Model Type
Source Object Type
Target Object Type
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Event Event Event Event Event General resource Group Group Information carrier IT function type
is used by is used by corresponds to is evaluated by activates is compared to is owner of provides has state can use
uses uses corresponds to evaluates is activated by is compared to has owner is provided by is state of can be used by
Person type Position Product/Service Rule Screen Event Event Event Event Class
can use can use creates
can be used by can be used by is created by
Entity type ERM attribute Event
ARIS Methods
11-554
Model Type
Source Object Type
Target Object Type
relates to supports supports when time limit is exceeded
relates to (passive) is supported by supports when time limit is exceeded (passive) can be used by can be used by can be used by
Event Event Event
Information carrier Relationship type Technical term
Event diagram
is measured upon occurrence relates to can use can use can use can use can use can use
triggers measuring
Event
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Knowledge category Module type Module type Module type Module type Module type Module type
relates to (passive) can be used by can be used by can be used by can be used by can be used by can be used by
Event Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute
ARIS Methods
11-555
Model Type
Source Object Type
Target Object Type
Event diagram Event diagram
creates can use
is created by can be used by
Event Information carrier
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Module type Module type Organizational unit Organizational unit Organizational unit type Organizational unit type
can use can use is owner of provides is owner of provides
can be used by can be used by has owner is provided by has owner is provided by
Relationship type Technical term Event Event Event Event
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Person Person Person type Person type Position Position Product/Service Relationship type Rule
is owner of provides is owner of provides is owner of provides is compared to has state leads to
has owner is provided by has owner is provided by has owner is provided by is compared to is state of is dependent on
Event Event Event Event Event Event Event Event Event
ARIS Methods
11-556
Model Type
Source Object Type
Target Object Type
Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram Event diagram
Rule Screen Screen Screen Screen Screen Screen Screen Screen Screen Screen Technical term
has subordinate rule can use can use can use can use can use can use creates can use can use can use has state
is subordinate rule of can be used by can be used by can be used by can be used by can be used by can be used by is created by can be used by can be used by can be used by is state of
Rule Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute Event Information carrier Relationship type Technical term Event
Assignment Relationship Event diagram
Source Object Type Event
Relationship Type (active) has subordinate event
Relationship Type (passive) is subordinate event of
Target Object Type Event
ARIS Methods
11.2.30 Function allocation diagram
11-557

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type Application system type can use can be used by uses supports is supported by is used by Attribute type group Cluster/Data model Function uses is used by uses supports is supported by is used by Relationship type Technical term Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by uses is used by Attribute type group Cluster/Data model Complex object type COT attribute Target Object Type
ARIS Methods
11-558
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Attribute type group Attribute type group Attribute type group Attribute type group Authorization condition Authorization condition
can use supports can use can use
can be used by is supported by can be used by can be used by
ERM attribute Function Relationship type Technical term
lies on is required for relates to
has information about requires has
Information carrier Function Technical term
ARIS Methods
11-559
Model Type
Source Object Type
Target Object Type
Business object Class Class
is input for has state is approved by
has input of is state of approves
Function Event Function
Class Class Class Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
is checked by is input for lies on has state
checks has input of has information about is state of
Function Function Information carrier Event
is used by lies on is used by
uses has information about uses
Group Information carrier Organizational unit
ARIS Methods
11-560
Model Type
Source Object Type
Target Object Type
Cluster/Data model Cluster/Data model Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Component
is used by is used by is managed by
uses uses manages
Person type Position Application system type
is managed by has state is approved by is checked by
manages is state of approves checks
Component Event Function Function
is input for lies on can use
has input of has information about can be used by
Function Information carrier Attribute type group
ARIS Methods
11-561
Model Type
Source Object Type
Target Object Type
Component Component Cost driver COT attribute
can use can use influences has state
can be used by can be used by is influenced by is state of
Relationship type Technical term Function Event
ARIS Methods
11-562
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Documented knowledge Element type Element type
is required for is approved by is checked by
requires approves checks
Element type Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable
is input for is different from is disciplinary superior to is technical superior to substitutes for
has input of is different from has the disciplinary superior has the technical superior is substituted by
Function Employee variable Employee variable Employee variable Employee variable Function Function Function
decides on
is decided by
Function
ARIS Methods
11-563
Model Type
Source Object Type
Target Object Type
Employee variable
Function
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable Employee variable
is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of is employee variable is employee variable is employee variable is employee variable is employee variable is employee variable
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by has employee variable has employee variable has employee variable has employee variable has employee variable has employee variable
Function Function
Function Function
Function Group
Location Organizational unit Person
ARIS Methods
11-564
Model Type
Source Object Type
Target Object Type
Entity type Entity type Entity type Entity type
is approved by is checked by is input for lies on
approves checks has input of has information about
Function Function Function Information carrier Attribute type group Event Event
belongs to has state is compared to
encompasses is state of is compared to
provides value for is approved by is checked by
uses value of approves checks
ARIS Methods
11-565
Model Type
Source Object Type
Target Object Type
has input of has information about has screen field is defined corresponds to is archived by is changed by
defines status corresponds to archives changes
Material type Product/Service Attribute type group Attribute type group
Attribute type group Attribute type group Attribute type group Attribute type group Attribute type group Authorization condition
has output of reads has knowledge of
is output of is read by is available at
ARIS Methods
11-566
Model Type
Source Object Type
Target Object Type
Business object Business object Class
ARIS Methods
11-567
Model Type
Source Object Type
Target Object Type
can support belongs to archives
can be supported by is assigned to is archived by
Component Cost category COT attribute
ARIS Methods
11-568
Model Type
Source Object Type
Target Object Type
distributes has output of reads creates
is distributed by is output of is read by is created by
COT attribute COT attribute COT attribute Documented knowledge
reads can create can use
is read by can be created by can be used by
Documented knowledge Draft list Draft list
ARIS Methods
11-569
Model Type
Source Object Type
Target Object Type
Element type Entity type Entity type Entity type
ARIS Methods
11-570
Model Type
Source Object Type
Target Object Type
has output of reads calls produces
is output of is read by is called by is produced by
ERM attribute ERM attribute Function General resource
reads creates output to reads
is read by is output medium for is read by
General resource Information carrier Information carrier
Function
is measured by
measures
Function allocation diagram Function allocation diagram
Function Function
creates has knowledge of
is created by is available at
ARIS Methods
11-571
Model Type
Source Object Type
Target Object Type
reads creates uses
is read by is created by is used by
Knowledge category List List
is carried out at creates supports has output of
is performed in is created by is supported by is output of
Location Material type Objective Package
reads requires has output of
is read by is required by is output of
Package Packaging material type Product/Service
produces archives changes
is produced by is archived by is changed by
Product/Service Relationship type Relationship type
ARIS Methods
11-572
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Relationship type Relationship type Relationship type Relationship type Relationship type Screen Screen design
has output of reads is represented by can use
is output of is read by represents can be used by
Function
requires
is required by
Function
Function
requires
is required by
Function
ARIS Methods
11-573
Model Type
Source Object Type
Target Object Type
Function Function
is accessed by is accessed alternatively by is accessed by is accessed alternatively by is required by
Transport system Transport system Transport system type Transport system type Warehouse equipment
Function Function
Function
requires
ARIS Methods
11-574
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Function Function
requires alternatively requires
Warehouse equipment Warehouse equipment type
Function
is required alternatively consumes can be processed by/with uses
Warehouse equipment type Function Function Function
General resource General resource General resource Group
is consumed by is defined is used by
Application system
Group
Application system
Function allocation diagram Function allocation diagram Function allocation diagram
Group Group Group
ARIS Methods
11-575
Model Type
Source Object Type
Target Object Type
Group
Group Group
Group
Group Group Group
Group Group Group
Group Group
provides accesses
is provided by is accessed by
Cluster/Data model Complex object type
ARIS Methods
11-576
Model Type
Source Object Type
Target Object Type
Group Group Group
is owner of is specimen owner of can be user
has owner has specimen owner can be used by
Group
Component
Group
Component
Group
accesses
COT attribute
Group Group Group
Group Group Group
ARIS Methods
11-577
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Group Group Group
is specimen owner of accepts carries out
has specimen owner is accepted by is carried out by
ERM attribute Function Function
Group
contributes to
Function
Group
decides on
is decided by
Function
Group
Function
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Group Group
Function Function
Group Group
Function Function
Group
Function
ARIS Methods
11-578
Model Type
Source Object Type
Target Object Type
Group
uses
is used by
Group Group
Group
IT function
Group Group
is used by development is under responsibility of is under technical responsibility of is used by is available at
Group
Group Group
is user has knowledge of
Group Group
is required by development is under responsibility of
ARIS Methods
11-579
Model Type
Source Object Type
Target Object Type
Group
Module
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Group Group Group
Group
Module type
Group Group
Group Group Hardware component type Hardware component type
accesses is owner of stores
is accessed by has owner is stored on
Technical term Technical term Attribute type group
stores
is stored on
Class
ARIS Methods
11-580
Model Type
Source Object Type
Target Object Type
stores
is stored on
Cluster/Data model
stores
is stored on
Complex object type
Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Information carrier Information carrier Information carrier
stores
is stored on
COT attribute
stores
is stored on
Entity type
stores
is stored on
ERM attribute
stores
is stored on
Relationship type
stores
is stored on
Technical term
has state
is state of
Event
provides input for is used by
gets input from uses
Function Group
ARIS Methods
11-581
Model Type
Source Object Type
Target Object Type
Information carrier Information carrier Information carrier IT function IT function IT function IT function
uses uses uses
Organizational unit Person type Position
uses uses uses uses
Attribute type group Cluster/Data model Complex object type COT attribute
uses uses supports
IT function IT function IT function type
uses uses uses
ARIS Methods
11-582
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
uses uses uses
uses uses relates to supports
is used by is used by relates to (passive) is supported by
Entity type ERM attribute Event Event
Event
supports
Function
supports when time limit is exceeded (passive) is used by
Function
IT function type
uses
Relationship type
ARIS Methods
11-583
Model Type
Source Object Type
Target Object Type
IT function type Knowledge category List
uses is required for provides input for
is used by requires gets input from is available at is required by is accessed by has owner
Authorization condition Authorization condition Class Class
ARIS Methods
11-584
Model Type
Source Object Type
Target Object Type
is owner of has knowledge of requires accesses
has owner is available at is required by is accessed by
ERM attribute Knowledge category Knowledge category Relationship type
Material type Material type Material type
is consumed is not consumed is partly consumed
consumes does not consume partly consumes
ARIS Methods
11-585
Model Type
Source Object Type
Target Object Type
uses uses uses
uses uses uses
ARIS Methods
11-586
Model Type
Source Object Type
Target Object Type
Module type Module type Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource type Operating resource type
can use can use encompasses is alternative operating resource of is operating resource of encompasses encompasses can encompass
can be used by can be used by belongs to has alternative operating resource has operating resource belongs to belongs to can belong to
Function
is alternative operating resource of
has alternative operating resource
Function
ARIS Methods
11-587
Model Type
Source Object Type
Target Object Type
Operating resource type Operating resource type Operating resource type Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
is operating resource of can encompass can encompass
has operating resource can belong to can belong to
Function IT function type Module type
ARIS Methods
11-588
Model Type
Source Object Type
Target Object Type
Organizational unit
is available at is required by is accessed by has owner
Authorization condition Authorization condition Class Class
accesses is owner of is specimen owner of provides accesses is owner of
is accessed by has owner has specimen owner is provided by is accessed by has owner
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type
can be user
can be used by
Component
ARIS Methods
11-589
Model Type
Source Object Type
Target Object Type
Organizational unit
Component
Organizational unit
Component
is specimen owner of accepts carries out
has specimen owner is accepted by is carried out by
ERM attribute Function Function
ARIS Methods
11-590
Model Type
Source Object Type
Target Object Type
Organizational unit
contributes to
Function
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of uses
Function Function
Function Function
Function Function
Function
is provided by development is under responsibility of
ARIS Methods
11-591
Model Type
Source Object Type
Target Object Type
Organizational unit
IT function
is user is responsible for development of is technically responsible for
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Module
Organizational unit
Module
is user can be user
is used by can be used by
Module Module type
ARIS Methods
11-592
Model Type
Source Object Type
Target Object Type
Organizational unit
Module type
Organizational unit
Module type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type
Application system Application system Application system Application system class Application system class
ARIS Methods
11-593
Model Type
Source Object Type
Target Object Type
Complex object type Complex object type
ARIS Methods
11-594
Model Type
Source Object Type
Target Object Type
Component Component
Component
ARIS Methods
11-595
Model Type
Source Object Type
Target Object Type
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of can be user is responsible for development of is technically responsible for can be user
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of can be used by
Function Function
Function Function
Function Function
Function
IT function
IT function type
ARIS Methods
11-596
Model Type
Source Object Type
Target Object Type
IT function type
IT function type
has knowledge of requires can be user is responsible for development of is technically responsible for can be user
is available at is required by can be used by development is under responsibility of is under technical responsibility of can be used by
Knowledge category Knowledge category Module Module
Module
Module type
Module type
Module type
accesses
is accessed by
Relationship type
ARIS Methods
11-597
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Package Package Person
is contained by has input of development is under responsibility of is under technical responsibility of is used by can be used by
Function Function Application system Application system Application system Application system class
Person
Person Person
is user can be user
Person
Person
ARIS Methods
11-598
Model Type
Source Object Type
Target Object Type
Person Person
Person
ARIS Methods
11-599
Model Type
Source Object Type
Target Object Type
Person
Component
Person Person
ARIS Methods
11-600
Model Type
Source Object Type
Target Object Type
Person Person
Function Function
Person
Function
Person
Function
Person Person
Function Function
Person Person
ARIS Methods
11-601
Model Type
Source Object Type
Target Object Type
Person
IT function
Person
IT function
Person Person
Person
IT function type
Person
Module
Person
Module
Person
is user
is used by
Module
ARIS Methods
11-602
Model Type
Source Object Type
Target Object Type
Person Person
Person
Module type
has owner can be used by development is under responsibility of is under technical responsibility of can be used by
Technical term Application system Application system Application system Application system class
Person type
Person type
can be user
ARIS Methods
11-603
Model Type
Source Object Type
Target Object Type
Person type
Person type
Person type
ARIS Methods
11-604
Model Type
Source Object Type
Target Object Type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Component Component
Person type
Component
ARIS Methods
11-605
Model Type
Source Object Type
Target Object Type
Function Function
Person type
Function
Person type
Function
Function Function
ARIS Methods
11-606
Model Type
Source Object Type
Target Object Type
Person type
IT function
Person type
Module Module
Person type
Module
ARIS Methods
11-607
Model Type
Source Object Type
Target Object Type
Person type
Module type
Position
Position
is user
ARIS Methods
11-608
Model Type
Source Object Type
Target Object Type
Position Position
Application system class Application system class Application system class Application system type Application system type Application system type Authorization condition Authorization condition
Position
Position Position
Position
Position Position
ARIS Methods
11-609
Model Type
Source Object Type
Target Object Type
Position
Component
Position Position
ARIS Methods
11-610
Model Type
Source Object Type
Target Object Type
is accessed by has owner has specimen owner is accepted by is carried out by is worked on by collaboration of
Position Position
Function Function
Position
Function
Position
Function
Position
Function
ARIS Methods
11-611
Model Type
Source Object Type
Target Object Type
Position
Function
Position Position
Position Position
Position
IT function
Position Position
Position
Position
is user
Position
has knowledge of
is available at
Knowledge category
ARIS Methods
11-612
Model Type
Source Object Type
Target Object Type
Position Position
Position
Module
Position
Module type
Position
accesses
Relationship type
ARIS Methods
11-613
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type System organizational unit System organizational unit type
is consumed by is input for is used by
consumes has input of uses
is managed by is managed by has state is approved by
manages manages is state of approves
Application system type Component Event Function
Function Function Information carrier Function Function
ARIS Methods
11-614
Model Type
Source Object Type
Target Object Type
encompasses
belongs to
Application system
encompasses
belongs to
IT function
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
Technical operating supply Technical operating supply type Technical operating supply type Technical operating supply type Technical term
encompasses
belongs to
Module
can encompass
can belong to
can encompass
can belong to
IT function type
can encompass
can belong to
Module type
has state
is state of
Event
Technical term
lies on
Information carrier
ARIS Methods
11-615
Model Type
Source Object Type
Target Object Type
Transport system Transport system Transport system Transport system type Transport system type Transport system type Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment type Warehouse equipment type Warehouse equipment type
encompasses encompasses encompasses
can encompass can encompass can encompass encompasses
can belong to can belong to can belong to belongs to
Application system type IT function type Module type Application system
encompasses encompasses can encompass
belongs to belongs to can belong to
can encompass
can belong to
IT function type
can encompass
can belong to
Module type
ARIS Methods
11.2.31 Function allocation diagram (instance)
11-616

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Application system uses is used by Technical terms instance Application system uses is used by Relationship Application system supports is supported by Function instance Application system uses is used by ERM attribute instance Application system uses is used by Entity Application system uses is used by COT attribute (instance) Application system uses is used by Complex object Application system uses is used by Cluster instance Target Object Type
ARIS Methods
11-617
Model Type
Source Object Type
Target Object Type
Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
supports
is supported by
Function instance
can use
can be used by
Cluster instance
can use
can be used by
Complex object
can use
can be used by
can use
can be used by
Entity
can use
can be used by
supports
is supported by
Function instance Relationship
can use
can be used by
can use
can be used by
ARIS Methods
11-618
Model Type
Source Object Type
Target Object Type
Cluster instance
has state
is state of
Event instance
Cluster instance
is approved by
approves
Function instance
Cluster instance Cluster instance Cluster instance Complex object Complex object Complex object Complex object
is checked by
checks
Function instance
is input for
has input of
Function instance
has current location is managed by
is current location of manages
Information carrier Application system type
has state
is state of
Event instance
is approved by
approves
Function instance
is checked by
checks
Function instance
ARIS Methods
11-619
Model Type
Source Object Type
Target Object Type
Complex object
is input for
has input of
Function instance
Complex object
has current location
is current location of
Information carrier
COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance)
has state
is state of
Event instance
is compared to
is compared to
Event instance
provides value for is approved by
uses value of
Event instance
approves
Function instance
is checked by
checks
Function instance
is input for
has input of
Function instance
lies on
Information carrier
ARIS Methods
11-620
Model Type
Source Object Type
Target Object Type
Employee variable
is different from
is different from
Employee variable
Employee variable
Employee variable
has the technical superior is substituted by
Employee variable Employee variable Function instance Function instance Function instance
carries out
is carried out by
contributes to
decides on
is decided by
has consulting role in is IT responsible for
is supported by consulting role of is under IT responsibility of
Function instance Function instance
ARIS Methods
11-621
Model Type
Source Object Type
Target Object Type
Employee variable
Function instance
Employee variable
Function instance
must inform about result of is employee variable is employee variable is employee variable is employee variable is employee variable is employee variable
result is forwarded by has employee variable has employee variable has employee variable has employee variable has employee variable has employee variable
Function instance Group
Location
Organizational unit Person
Person type
Position
ARIS Methods
11-622
Model Type
Source Object Type
Target Object Type
Entity
is managed by
manages
Entity
has state
is state of
Event instance
Entity
is approved by
approves
Function instance
Entity
is checked by
checks
Function instance
Entity
is input for
has input of
Function instance
Entity
is current location of is state of
Information carrier Event instance
ERM attribute instance ERM attribute instance ERM attribute instance
has state
is compared to
is compared to
Event instance
provides value for
uses value of
Event instance
ARIS Methods
11-623
Model Type
Source Object Type
Target Object Type
is approved by
approves
Function instance
is checked by
checks
Function instance
ERM attribute instance ERM attribute instance ERM attribute instance Function instance Function instance Function instance Function instance
is input for
has input of
Function instance
has current location defines screen field archives
is current location of has screen field is archived by
Information carrier Screen
Cluster instance
changes
is changed by
Cluster instance
creates
is created by
Cluster instance
deletes
is deleted by
Cluster instance
ARIS Methods
11-624
Model Type
Source Object Type
Target Object Type
Function instance
distributes
is distributed by
Cluster instance
Function instance
has output of
is output of
Cluster instance
Function instance Function instance Function instance Function instance Function instance Function instance Function instance
archives
is archived by
Complex object
changes
is changed by
Complex object
creates
is created by
Complex object
deletes
is deleted by
Complex object
distributes
is distributed by
Complex object Complex object
has output of
is output of
archives
is archived by
ARIS Methods
11-625
Model Type
Source Object Type
Target Object Type
Function instance
changes
is changed by
Function instance
creates
is created by
deletes
is deleted by
distributes
is distributed by
COT attribute (instance) COT attribute (instance)
has output of
is output of
can create
can be created by
Draft list
can use
can be used by
Draft list
archives
is archived by
Entity
changes
is changed by
Entity
ARIS Methods
11-626
Model Type
Source Object Type
Target Object Type
Function instance
creates
is created by
Entity
Function instance
deletes
is deleted by
Entity
distributes
is distributed by
Entity
has output of
is output of
Entity
archives
is archived by
changes
is changed by
creates
is created by
deletes
is deleted by
distributes
is distributed by
ARIS Methods
11-627
Model Type
Source Object Type
Target Object Type
Function instance
has output of
is output of
Function instance
creates output to
is output medium for
Information carrier
creates
is created by
List
uses
is used by
List
is carried out at archives
is performed in
Location
is archived by
Relationship
changes
is changed by
Relationship
creates
is created by
Relationship
deletes
is deleted by
Relationship
ARIS Methods
11-628
Model Type
Source Object Type
Target Object Type
Function instance
distributes
is distributed by
Relationship
Function instance
has output of
is output of
Relationship
is represented by can use
represents
Screen
can be used by
Screen design
archives
is archived by
changes
is changed by
creates
is created by
deletes
is deleted by
distributes
is distributed by
ARIS Methods
11-629
Model Type
Source Object Type
Target Object Type
Function instance
has output of
is output of
General resource
is defined
can be processed by/with
Function instance
Group
Group
Group
is user
Group
can be user
can be used by
Group
Application system class Application system class Application system type
Group
Group
can be user
ARIS Methods
11-630
Model Type
Source Object Type
Target Object Type
Group
Group
Group
accesses
is accessed by
Cluster instance
Group
is owner of
has owner
Cluster instance
Group
accesses
is accessed by
Complex object
Group
is owner of
has owner
Complex object
Group
accesses
is accessed by
Group
is owner of
has owner
Group
is specimen owner of
has specimen owner
ARIS Methods
11-631
Model Type
Source Object Type
Target Object Type
Group
accesses
is accessed by
Entity
Group
is owner of
has owner
Entity
Group
accesses
is accessed by
Group
is owner of
has owner
Group
has specimen owner is carried out by
ERM attribute instance Function instance Function instance Function instance
Group
carries out
Group
contributes to
Group
decides on
is decided by
Group
Function instance
ARIS Methods
11-632
Model Type
Source Object Type
Target Object Type
Group
Function instance
Group
Function instance
Group
Function instance Function instance Function instance Hardware component type
Group
Group
Group
uses
Group
IT function
Group
IT function
Group
is user
IT function
ARIS Methods
11-633
Model Type
Source Object Type
Target Object Type
Group
IT function type
Group
IT function type
Group
is user
is used by
IT function type
Group
Module
Group
Module
Group
is user
Module
Group
can be user
can be used by
Module type
Group
Module type
Group
Module type
ARIS Methods
11-634
Model Type
Source Object Type
Target Object Type
Group
accesses
is accessed by
Relationship
Group
is owner of
has owner
Relationship
Group
accesses
is accessed by
Group
is owner of
has owner
Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type
stores
is stored on
Cluster instance
stores
is stored on
Complex object
stores
is stored on
stores
is stored on
Entity
stores
is stored on
ARIS Methods
11-635
Model Type
Source Object Type
Target Object Type
Hardware component type Hardware component type Information carrier Information carrier IT function
stores
is stored on
Relationship
stores
is stored on
has state
is state of
Event instance
provides input for uses
gets input from is used by
Function instance Cluster instance
IT function
uses
is used by
Complex object
IT function
uses
is used by
IT function
uses
is used by
Entity
IT function
uses
is used by
ARIS Methods
11-636
Model Type
Source Object Type
Target Object Type
IT function
supports
is supported by
Function instance
IT function
uses
is used by
Relationship
IT function
uses
is used by
IT function type IT function type IT function type IT function type IT function type IT function type
uses
is used by
Cluster instance
uses
is used by
Complex object
uses
is used by
uses
is used by
Entity
uses
is used by
supports
is supported by
Event instance
ARIS Methods
11-637
Model Type
Source Object Type
Target Object Type
IT function type
supports
is supported by
Function instance
IT function type
uses
is used by
Relationship
IT function type List
uses
is used by
provides input for
gets input from is used by
Function instance Cluster instance
Module
uses
Module
uses
is used by
Complex object
Module
uses
is used by
Module
uses
is used by
Entity
Module
uses
is used by
ARIS Methods
11-638
Model Type
Source Object Type
Target Object Type
Module
supports
is supported by
Function instance
Module
uses
is used by
Relationship
Module
uses
is used by
Module type
can use
can be used by
Cluster instance
Module type
can use
can be used by
Complex object
Module type
can use
can be used by
Module type
can use
can be used by
Entity
Module type
can use
can be used by
Module type
supports
is supported by
Function instance
ARIS Methods
11-639
Model Type
Source Object Type
Target Object Type
Module type
can use
can be used by
Relationship
Module type
can use
can be used by
Operating resource Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
is defined
can be processed by/with
Function instance Application system Application system Application system
can be user
can be used by
is responsible for development of is technically responsible for
ARIS Methods
11-640
Model Type
Source Object Type
Target Object Type
Organizational unit
can be user
can be used by
Organizational unit
is technically responsible for accesses
Application system type Cluster instance
is owner of
has owner
Cluster instance
Cluster instance Complex object
is owner of
has owner
Complex object
accesses
is accessed by
ARIS Methods
11-641
Model Type
Source Object Type
Target Object Type
Organizational unit
is owner of
has owner
Organizational unit
has specimen owner
accesses
is accessed by
Entity
is owner of
has owner
Entity
accesses
is accessed by
is owner of
has owner
is specimen owner of carries out
ERM attribute instance Function instance Function instance
contributes to
ARIS Methods
11-642
Model Type
Source Object Type
Target Object Type
Organizational unit
decides on
is decided by
Function instance
Organizational unit
Function instance
Function instance Function instance Function instance Function instance Function instance Hardware component type
IT function
ARIS Methods
11-643
Model Type
Source Object Type
Target Object Type
Organizational unit
IT function
Organizational unit
is user
is used by
IT function
Module
Module
Module
can be user
can be used by
Module type
ARIS Methods
11-644
Model Type
Source Object Type
Target Object Type
Organizational unit
Module type
Organizational unit
Module type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type
accesses
is accessed by
Relationship
is owner of
has owner
Relationship
accesses
is accessed by
is owner of
has owner
can be user
can be used by
Application system
ARIS Methods
11-645
Model Type
Source Object Type
Target Object Type
can be user
can be used by
is technically responsible for can be user
is responsible for development of is technically responsible for accesses
Application system type Application system type Cluster instance
accesses
is accessed by
Complex object
accesses
is accessed by
ARIS Methods
11-646
Model Type
Source Object Type
Target Object Type
accesses
is accessed by
Entity
accesses
is accessed by
carries out
is carried out by
Function instance Function instance Function instance Function instance IT function
has consulting role in is IT responsible for is technically responsible for can be user
is supported by consulting role of is under IT responsibility of is under technical responsibility of can be used by
IT function
IT function
ARIS Methods
11-647
Model Type
Source Object Type
Target Object Type
can be user
can be used by
IT function type
IT function type
is responsible for development of is technically responsible for can be user
Module
Module
Module type
Module type
Module type
ARIS Methods
11-648
Model Type
Source Object Type
Target Object Type
accesses
is accessed by
Relationship
accesses
is accessed by
Person
Person
Person
is user
Person
can be user
can be used by
Person
Person
Person
can be user
ARIS Methods
11-649
Model Type
Source Object Type
Target Object Type
Person
Person
Person
accesses
is accessed by
Cluster instance
Person
is owner of
has owner
Cluster instance
Person
accesses
is accessed by
Complex object
Person
is owner of
has owner
Complex object
Person
accesses
is accessed by
Person
is owner of
has owner
Person
has specimen owner
ARIS Methods
11-650
Model Type
Source Object Type
Target Object Type
Person
accesses
is accessed by
Entity
Person
is owner of
has owner
Entity
Person
accesses
is accessed by
Person
is owner of
has owner
Person
ERM attribute instance Function instance Function instance Function instance
Person
carries out
Person
contributes to
Person
decides on
is decided by
Person
has carried out
was carried out by
Function instance
ARIS Methods
11-651
Model Type
Source Object Type
Target Object Type
Person
Function instance
Person
Function instance
Person
is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is used by
Function instance Function instance Function instance Function instance Hardware component type
Person
Person
Person
Person
uses
Person
IT function
Person
IT function
ARIS Methods
11-652
Model Type
Source Object Type
Target Object Type
Person
is user
is used by
IT function
Person
IT function type
Person
Person
is user
Person
Module
Person
Module
Person
is user
Module
Person
can be user
can be used by
Module type
Person
Module type
ARIS Methods
11-653
Model Type
Source Object Type
Target Object Type
Person
Module type
Person
accesses
is accessed by
Relationship
Person
is owner of
has owner
Relationship
Person
accesses
is accessed by
Person
is owner of
has owner
Person type
can be user
can be used by
Application system
Person type
Application system Application system Application system class
Person type
Person type
can be user
ARIS Methods
11-654
Model Type
Source Object Type
Target Object Type
Person type
Person type
Person type
can be user
can be used by
Person type
Person type
Person type
accesses
Person type
accesses
is accessed by
Complex object
Person type
accesses
is accessed by
Person type
accesses
is accessed by
Entity
ARIS Methods
11-655
Model Type
Source Object Type
Target Object Type
Person type
accesses
is accessed by
Person type
carries out
is carried out by
Function instance
Person type
contributes to
Function instance Function instance
Person type
decides on
is decided by
Person type
is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to
Function instance Function instance Function instance Function instance Function instance
Person type
Person type
Person type
Person type
ARIS Methods
11-656
Model Type
Source Object Type
Target Object Type
Person type
result is forwarded by
Function instance
Person type
can be user
can be used by
IT function
Person type
IT function
Person type
IT function
Person type
can be user
IT function type
Person type
IT function type IT function type Module
Person type
Person type
can be user
Person type
Module
ARIS Methods
11-657
Model Type
Source Object Type
Target Object Type
Person type
Module
Person type
can be user
can be used by
Module type
Person type
Module type
Person type
Module type
Person type
accesses
Relationship
Person type
accesses
is accessed by
Position
Position
Position
is user
ARIS Methods
11-658
Model Type
Source Object Type
Target Object Type
Position
can be user
can be used by
Position
Position
Position
can be user
Position
Position
Position
accesses
Position
is owner of
has owner
Cluster instance
Position
accesses
is accessed by
Complex object
ARIS Methods
11-659
Model Type
Source Object Type
Target Object Type
Position
is owner of
has owner
Complex object
Position
accesses
is accessed by
Position
is owner of
has owner
Position
Position
accesses
Position
is owner of
has owner
Entity
Position
accesses
is accessed by
Position
is owner of
has owner
Position
has specimen owner
ARIS Methods
11-660
Model Type
Source Object Type
Target Object Type
Position
carries out
is carried out by
Function instance
Position
contributes to
Function instance
Position
decides on
is decided by
Function instance
Position
is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by
Function instance Function instance Function instance Function instance Function instance Function instance
Position
Position
Position
Position
Position
ARIS Methods
11-661
Model Type
Source Object Type
Target Object Type
Position
uses
is used by
Position
IT function
Position
IT function
Position
is user
IT function
Position
Position
Position
is user
Position
Module
Position
Module
ARIS Methods
11-662
Model Type
Source Object Type
Target Object Type
Position
is user
is used by
Module
Position
can be user
can be used by
Module type
Position
Module type
Position
Module type
Position
accesses
Relationship
Position
is owner of
has owner
Relationship
Position
accesses
is accessed by
Position
is owner of
has owner
Relationship
is managed by
manages
ARIS Methods
11-663
Model Type
Source Object Type
Target Object Type
Relationship
has state
is state of
Event instance
Relationship
is approved by
approves
Function instance
Relationship
is checked by
checks
Function instance
Relationship
is input for
has input of
Function instance
Relationship
is current location of is assigned to
Information carrier Function instance
System organizational unit System organizational unit type Technical terms instance Technical terms instance
is assigned to
can be assigned to has state
can be assigned to is state of
Function instance Event instance
is approved by
approves
Function instance
ARIS Methods
11-664
Model Type
Source Object Type
Target Object Type
Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
is checked by
checks
Function instance
is input for
has input of
Function instance
is current location of
Information carrier
ARIS Methods
11.2.32 Function tree
11-665
11.2.32 Function tree

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Function tree Function is executionoriented superior Function tree Function is objectoriented superior Function tree Function is processoriented superior is executionoriented subordinate is objectoriented subordinate is processoriented subordinate Function Function Function Target Object Type
11.2.33 Function/organizational level diagram

Model Type Source Object Type Function/organizatio nal level diagram Function/organizatio nal level diagram Function belongs to is assigned to Organizational level Cluster/Data model Relationship Type (active) belongs to Relationship Type (passive) is assigned to Organizational level Target Object Type
ARIS Methods
11.2.34 IE Data model
11-666

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) IE Data model IE Data model IE Data model Cluster/Data model Cluster/Data model Cluster/Data model IE Data model IE Data model IE Data model Cluster/Data model Entity type Entity type has relationship to is subtype of has relationship to has as subtype Generalization type IE Data model IE Data model IE Data model IE Data model Entity type ERM attribute ERM attribute ERM attribute is supertype of is describing for is foreign key for is primary key for IE Data model Generalization type differentiates according to value of has foreign key has primary key is characteristic for ERM attribute Entity type Entity type has as supertype is described by Generalization type Entity type consists of is part of Generalization type Entity type consists of is part of ERM attribute consists of is part of consists of is part of Cluster/Data model Entity type Target Object Type
ARIS Methods
11-667
Source Object Type
Target Object Type
IE Data model IE Data model IE Data model
IE Data model IE Data model IE Data model IE Data model
Cluster/Data model Screen Screen Screen
consists of defines screen field defines screen field defines screen field
is part of has screen field has screen field has screen field has screen field has screen field has screen field
Generalization type Cluster/Data model Entity type ERM attribute
IE Data model IE Data model IE Data model
Screen design Screen design Screen design
ARIS Methods
11.2.35 Industrial process
11-668

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Application system Application system Application system Application system Application system Application system type Application system type Application system type Application system type Application system type Application system type Application system type supports is supported by Function creates is created by Event can use can be used by ERM attribute can use can be used by can use can be used by Cluster/Data model Entity type uses is used by Class can use can be used by Class uses is used by uses is used by Relationship type Technical term uses is used by ERM attribute uses is used by uses is used by Cluster/Data model Entity type Target Object Type
ARIS Methods
11-669
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Application system type Application system type Class
can use can use has state
can be used by can be used by is state of
Relationship type Technical term Event
is approved by is checked by is input for lies on
approves checks has input of has information about
Function Function Function Information carrier Event Function Function
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
Function Group Information carrier
ARIS Methods
11-670
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Cluster/Data model Cluster/Data model Cluster/Data model Documented knowledge Documented knowledge Employee variable Employee variable Employee variable
uses uses uses
relates to is required for accepts carries out
relates to (passive) requires is accepted by is carried out by
contributes to
Function
Function Function
Function Function
ARIS Methods
11-671
Model Type
Source Object Type
Target Object Type
Employee variable Employee variable Employee variable Entity type Entity type
must be informed about must be informed on cancellation must inform about result of is managed by has state
result is forwarded to sends information on cancellation to result is forwarded by manages is state of
Function Function
Function Application system type Event
lies on has state is compared to
has information about is state of is compared to
Information carrier Event Event
ERM attribute ERM attribute
provides value for is approved by
uses value of approves
Event Function
ARIS Methods
11-672
Model Type
Source Object Type
Target Object Type
Function Function Information carrier Screen Application system type Function Group
ERM attribute Event Event Event
defines screen field activates activates is used by
has screen field is activated by is activated by uses
Event Event Event
Event Event Event
uses uses uses
ARIS Methods
11-673
Model Type
Source Object Type
Target Object Type
Event Event Event
is used by corresponds to is evaluated by
uses corresponds to evaluates
Position Product/Service Rule
activates reads reads archives
is activated by is read by is read by is archived by
Screen Attribute type group Business object Class
Class Class Class
Class Class Class
ARIS Methods
11-674
Model Type
Source Object Type
Target Object Type
reads reads creates
is read by is read by is created by
Complex object type COT attribute Documented knowledge
Documented knowledge Entity type Entity type
ARIS Methods
11-675
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-676
Model Type
Source Object Type
Target Object Type
is predecessor of produces reads
follows is produced by is read by
Function General resource General resource
creates output to reads is measured by
is output medium for is read by measures
Information carrier Information carrier Key performance indicator instance
Function Function
creates reads
is created by is read by
is carried out at supports has output of
is performed in is supported by is output of
Location Objective Package
Function Function
reads requires
is read by is required by
Package Packaging material type
ARIS Methods
11-677
Model Type
Source Object Type
Target Object Type
has output of produces archives
is output of is produced by is archived by
Product/Service Product/Service Relationship type
Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Rule
has output of reads leads to
is output of is read by is assigned to
Function Function
is represented by requires
represents is required by
Screen Technical operating supply type
Function
archives
is archived by
Technical term
ARIS Methods
11-678
Model Type
Source Object Type
Target Object Type
distributes has output of reads accesses
is distributed by is output of is read by is accessed by
Technical term Technical term Technical term Transport system type
Function
requires
is required by
Industrial process Industrial process Industrial process Industrial process Industrial process
is compared to is consumed by is defined
is compared to consumes can be processed by/with
is used by is user
uses is used by
ARIS Methods
11-679
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Group Group
Application system class Application system class Application system class Application system type Application system type Application system type Class Class
Group
Group Group
Group
Group Group
Group Group Group
ARIS Methods
11-680
Model Type
Source Object Type
Target Object Type
Group Group Group
is accessed by has owner has specimen owner is accessed by has owner has specimen owner is accessed by
Complex object type Complex object type Complex object type COT attribute COT attribute COT attribute Entity type
Group Group Group
Group Group Group
ARIS Methods
11-681
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Group Group Group
Group Group
Function Function
Group
Function
Group
Function
Group Group
Function Function
Group Group
ARIS Methods
11-682
Model Type
Source Object Type
Target Object Type
Group Group
is used by development is under responsibility of is under technical responsibility of is used by is used by can be used by
IT function IT function type IT function type IT function type Module Module type
Group
Group Group Group
is user is user can be user
Group
Module type
Industrial process
Group
Module type
Industrial process Industrial process Industrial process
Group Group Group
ARIS Methods
11-683
Model Type
Source Object Type
Target Object Type
Group Hardware component type Hardware component type Hardware component type
is owner of stores
has owner is stored on
Technical term Attribute type group
stores
is stored on
Class
stores
is stored on
Cluster/Data model
Industrial process
stores
is stored on
Entity type
Industrial process
stores
is stored on
ERM attribute
Industrial process
stores
is stored on
Relationship type
Industrial process
stores
is stored on
Technical term
Industrial process Industrial process
Information carrier Information carrier
provides input for is used by
gets input from uses
Function Group
ARIS Methods
11-684
Model Type
Source Object Type
Target Object Type
Information carrier Information carrier Information carrier IT function IT function IT function IT function
uses uses uses
uses uses uses uses
Cluster/Data model Entity type ERM attribute Relationship type
IT function IT function type IT function type IT function type IT function type IT function type
Technical term Class Cluster/Data model
ARIS Methods
11-685
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type Key performance indicator instance Knowledge category Knowledge category Location
uses creates can use uses
is used by is created by can be used by is used by
ERM attribute Event Relationship type Relationship type
can use uses is measured upon occurrence relates to
can be used by is used by triggers measuring relates to (passive)
Event
is required for accesses
requires is accessed by
Function Class
ARIS Methods
11-686
Model Type
Source Object Type
Target Object Type
Complex object type Complex object type COT attribute COT attribute
ERM attribute Relationship type Relationship type
ARIS Methods
11-687
Model Type
Source Object Type
Target Object Type
Location Location Material type
accesses is owner of is partly consumed
is accessed by has owner partly consumes is used by is used by is used by is used by
uses uses uses uses
Cluster/Data model Entity type ERM attribute Relationship type
Technical term Class Cluster/Data model
can use can use creates
can be used by can be used by is created by
Entity type ERM attribute Event
ARIS Methods
11-688
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Module type Module type Operating resource type Operating resource type Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
can use can use can encompass
can be used by can be used by can belong to
Relationship type Technical term Application system type
is operating resource of is user can be user is responsible for development of is technically responsible for can be user
has operating resource is used by can be used by development is under responsibility of is under technical responsibility of can be used by
Function Application system Application system class Application system class Application system class Application system type
Industrial process
Organizational unit
ARIS Methods
11-689
Model Type
Source Object Type
Target Object Type
is owner of is specimen owner of provides accesses
has owner has specimen owner is provided by is accessed by
ARIS Methods
11-690
Model Type
Source Object Type
Target Object Type
accesses is owner of is specimen owner of is owner of provides accepts carries out
is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by
contributes to
Function
Function Function
Function Function
ARIS Methods
11-691
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
must be informed about must be informed on cancellation must inform about result of provides is user
result is forwarded to sends information on cancellation to result is forwarded by is provided by is used by
Function Function
Function Information carrier IT function
IT function type
Industrial process
Organizational unit
IT function type
is user is user can be user
IT function type Module Module type
Module type
ARIS Methods
11-692
Model Type
Source Object Type
Target Object Type
Industrial process
Organizational unit
Module type
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type
Application system
Industrial process
Application system
can be user is responsible for development of is technically responsible for can be user
Application system class Application system class Application system class Application system type
ARIS Methods
11-693
Model Type
Source Object Type
Target Object Type
Industrial process
Industrial process
Complex object type Complex object type COT attribute
ARIS Methods
11-694
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
decides on
is decided by
Function
Function
is IT responsible for is technically responsible for must be informed about
Function Function
Function
ARIS Methods
11-695
Model Type
Source Object Type
Target Object Type
Industrial process
sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of development is under responsibility of is under technical responsibility of
Function
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
must inform about result of can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for is responsible for development of is technically responsible for
IT function
IT function type IT function type IT function type Module
Module
ARIS Methods
11-696
Model Type
Source Object Type
Target Object Type
Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process Industrial process
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Package Package
Module type
ARIS Methods
11-697
Model Type
Source Object Type
Target Object Type
Industrial process
Person
Person Person
Person
Person Person
ARIS Methods
11-698
Model Type
Source Object Type
Target Object Type
accesses is owner of is specimen owner of is owner of
is accessed by has owner has specimen owner has owner
ERM attribute ERM attribute ERM attribute Event
Person
contributes to
Function
Industrial process
Person
decides on
is decided by
Function
ARIS Methods
11-699
Model Type
Source Object Type
Target Object Type
Industrial process
Person
Function
Person Person
Function Function
Person Person
Function Function
Person Person
must inform about result of is user
Person
IT function type
Industrial process
Person
IT function type
Person Person
is user is user
ARIS Methods
11-700
Model Type
Source Object Type
Target Object Type
Person Person
Person
Module type
has owner can be used by development is under responsibility of is under technical responsibility of can be used by
Technical term Application system Application system Application system Application system class
Person type
Person type
can be user
ARIS Methods
11-701
Model Type
Source Object Type
Target Object Type
Industrial process
Person type
Industrial process
Person type
Industrial process
Person type
ARIS Methods
11-702
Model Type
Source Object Type
Target Object Type
Function Function
Person type
decides on
is decided by
Function
ARIS Methods
11-703
Model Type
Source Object Type
Target Object Type
Industrial process
Person type
Function
Function Function
Function Function
Person type
IT function
Person type
can be user
IT function type
ARIS Methods
11-704
Model Type
Source Object Type
Target Object Type
Industrial process
Person type
IT function type
Industrial process
Person type
IT function type
Module Module
Industrial process
Person type
Module
Person type
Module type
Person type
accesses
is accessed by
Technical term
ARIS Methods
11-705
Model Type
Source Object Type
Target Object Type
Person type Position Position
is owner of is user can be user
has owner is used by can be used by
Technical term Application system Application system class
Position
Position
Position
can be user
Position
Industrial process
Position
ARIS Methods
11-706
Model Type
Source Object Type
Target Object Type
has owner is accessed by has owner has specimen owner is accessed by has owner is accessed by
Complex object type COT attribute COT attribute COT attribute
ARIS Methods
11-707
Model Type
Source Object Type
Target Object Type
Position
contributes to
Function
Position
decides on
is decided by
Function
Position
Function
Position Position
Function Function
Position Position
Function Function
Position
Function
ARIS Methods
11-708
Model Type
Source Object Type
Target Object Type
provides is user is responsible for development of
is provided by is used by development is under responsibility of is under technical responsibility of is used by is used by
Information carrier IT function IT function type IT function type IT function type Module
Position
Position Position
is user is user
Position Position
Position
Module type
Position Position
ARIS Methods
11-709
Model Type
Source Object Type
Target Object Type
Position Position Product/Service Product/Service Product/Service Product/Service Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Rule
accesses is owner of is compared to
is accessed by has owner is compared to
is consumed by is input for is used by is managed by
consumes has input of uses manages
Function Function Function Application system type
is input for lies on leads to
has input of has information about is dependent on
ARIS Methods
11-710
Model Type
Source Object Type
Target Object Type
Rule Rule Screen
activates links can use
is activated by is linked by can be used by
Function Rule Class
Cluster/Data model Complex object type COT attribute Entity type
can use creates can use
can be used by is created by can be used by
ERM attribute Event Relationship type
Screen Technical operating supply type Technical term
can use can encompass
can be used by can belong to
Technical term Application system type
has state
is state of
Event
ARIS Methods
11-711
Model Type
Source Object Type
Target Object Type
Technical term Transport system type Warehouse equipment type
lies on can encompass can encompass
has information about can belong to can belong to
Information carrier Application system type Application system type
Source Object Type
Target Object Type
Industrial process
Function
Function
ARIS Methods
11.2.36 Information carrier diagram
11-712
11.2.36 Information carrier diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Information carrier diagram Information carrier encompasses belongs to Information carrier Target Object Type
11.2.37 Information flow diagram

Model Type Source Object Type Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow diagram Information flow Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type is IT responsible for is IT responsible for is technically responsible for carries out is received from carries out is carried out by is under IT responsibility of is under technical responsibility of is carried out by is under IT responsibility of Function Function Function Function Function receives Function Relationship Type (active) sends Relationship Type (passive) is sent from Information flow Function Target Object Type
ARIS Methods
11.2.38 Input/Output diagram
11-713
Model Type
Source Object Type
Target Object Type
Information flow diagram
Function
Information flow diagram Information flow diagram
Function Function
11.2.38 Input/Output diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram Function has output of is output of ERM attribute Function has output of is output of Function has output of is output of Cluster/Data model Entity type ERM attribute is input for has input of Function Cluster/Data model Entity type is input for has input of Function is input for has input of Function Target Object Type
ARIS Methods
11.2.39 Input/Output diagram (inverse)
11-714
Model Type
Source Object Type
Target Object Type
Input/Output diagram Input/Output diagram Input/Output diagram Input/Output diagram
Function Function Information carrier Relationship type
creates output to has output of provides input for is input for
is output medium for is output of gets input from has input of
Information carrier Relationship type Function
Function

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Function has output of is output of Cluster/Data model ERM attribute is input for has input of Function Entity type is input for has input of Function Cluster/Data model is input for has input of Function Target Object Type
ARIS Methods
11-715
Model Type
Source Object Type
Target Object Type
Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse) Input/Output diagram (inverse)
Function
has output of
is output of
Entity type
Function
has output of
is output of
ERM attribute
Function
creates output to
is output medium for is output of
Function
has output of
provides input for is input for
gets input from has input of
Function
Function
ARIS Methods
11.2.40 Key performance indicator allocation diagram
11-716

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Critical factor is measured by measures Key performance indicator instance Critical factor is under responsibility of is responsible for Group Cluster/Data model is input for has input of Key performance indicator instance Class is input for has input of Key performance indicator instance Application system type has output of is output of Key performance indicator instance Application system has output of is output of Key performance indicator instance Target Object Type
ARIS Methods
11-717
Model Type
Source Object Type
Target Object Type
Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram
Critical factor
is responsible for
Organizational unit
Critical factor
is responsible for
Critical factor
is responsible for
Person
Critical factor
is responsible for
Person type
Critical factor
is responsible for
Position
is required for
requires
Entity type
is input for
has input of
ARIS Methods
11-718
Model Type
Source Object Type
Target Object Type
ERM attribute
is input for
has input of
Function
supports
is supported by
Critical factor
Function
supports
is supported by
Objective
Function instance
supports
is supported by
Critical factor
Function instance
supports
is supported by
Objective
Group
influences
is influenced by
Critical factor
Group
carries out
is carried out by
Function
ARIS Methods
11-719
Model Type
Source Object Type
Target Object Type
Group
contributes to
Function
Group
decides on
is decided by
Function
Group
Function
Group
Function
Group
carries out
is carried out by
Function instance
Group
contributes to
Function instance
Group
decides on
is decided by
Function instance
ARIS Methods
11-720
Model Type
Source Object Type
Target Object Type
Group
Function instance
Group
Function instance
Group
influences
is influenced by
Objective
Information carrier
provides input for
gets input from
is of type
determines type of
Entity type
Key performance indicator instance Key performance indicator instance
is of type
determines type of
ERM attribute
is measured by
measures
Group
ARIS Methods
11-721
Model Type
Source Object Type
Target Object Type
Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance
is responsible for
Group
influences
is influenced by
is measured by
measures
Organizational unit
is responsible for
Organizational unit
is measured by
measures
Key performance indicator instance Key performance indicator instance
is responsible for
is measured by
measures
Person
ARIS Methods
11-722
Model Type
Source Object Type
Target Object Type
Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance
is responsible for
Person
is measured by
measures
Person type
is responsible for
Person type
is measured by
measures
Position
is responsible for
Position
Knowledge category
is required for
requires
Objective
is responsible for
Group
ARIS Methods
11-723
Model Type
Source Object Type
Target Object Type
Objective
is measured by
measures
Objective
is responsible for
Organizational unit
Objective
is responsible for
Objective
is responsible for
Person
Objective
is responsible for
Person type
Objective
is responsible for
Position
Organizational unit
influences
is influenced by
Critical factor
ARIS Methods
11-724
Model Type
Source Object Type
Target Object Type
Organizational unit
carries out
is carried out by
Function
Organizational unit
contributes to
Function
Organizational unit
decides on
is decided by
Function
Organizational unit
Function
Organizational unit
Function
Organizational unit
carries out
is carried out by
Function instance
Organizational unit
contributes to
Function instance
ARIS Methods
11-725
Model Type
Source Object Type
Target Object Type
Organizational unit
decides on
is decided by
Function instance
Organizational unit
Function instance
Organizational unit
Function instance
Organizational unit
influences
is influenced by
Objective
influences
is influenced by
Critical factor
carries out
is carried out by
Function
Function
ARIS Methods
11-726
Model Type
Source Object Type
Target Object Type
Function
carries out
is carried out by
Function instance
Function instance
Function instance
influences
is influenced by
Objective
Person
influences
is influenced by
Critical factor
Person
carries out
is carried out by
Function
ARIS Methods
11-727
Model Type
Source Object Type
Target Object Type
Person
contributes to
Function
Person
decides on
is decided by
Function
Person
Function
Person
Function
Person
carries out
is carried out by
Function instance
Person
contributes to
Function instance
Person
decides on
is decided by
Function instance
ARIS Methods
11-728
Model Type
Source Object Type
Target Object Type
Person
Function instance
Person
Function instance
Person
influences
is influenced by
Objective
Person type
influences
is influenced by
Critical factor
Person type
carries out
is carried out by
Function
Person type
contributes to
Function
Person type
decides on
is decided by
Function
ARIS Methods
11-729
Model Type
Source Object Type
Target Object Type
Person type
Function
Person type
carries out
is carried out by
Function instance
Person type
contributes to
Function instance
Person type
decides on
is decided by
Function instance
Person type
Function instance
Person type
influences
is influenced by
Objective
Position
influences
is influenced by
Critical factor
ARIS Methods
11-730
Model Type
Source Object Type
Target Object Type
Position
carries out
is carried out by
Function
Position
contributes to
Function
Position
decides on
is decided by
Function
Position
Function
Position
Function
Position
carries out
is carried out by
Function instance
Position
contributes to
Function instance
ARIS Methods
11-731
Model Type
Source Object Type
Target Object Type
Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram Key performance indicator allocation diagram
Position
decides on
is decided by
Function instance
Position
Function instance
Position
Function instance
Position
influences
is influenced by
Objective
Relationship type
is input for
has input of
Technical term
is input for
has input of
ARIS Methods
11.2.41 Key performance indicator tree
11-732
11.2.41 Key performance indicator tree

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Key performance indicator tree Key performance indicator instance is influenced by has influence on Key performance indicator instance Target Object Type
11.2.42 Knowledge map

Model Type Source Object Type Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map Organizational unit Organizational unit Organizational unit type Organizational unit type Person has knowledge of is available at has knowledge of requires is required by is available at Location has knowledge of has knowledge of requires is required by is available at is available at Group Group Relationship Type (active) has knowledge of requires is required by Relationship Type (passive) is available at Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Target Object Type
ARIS Methods
11.2.43 Knowledge structure diagram
11-733
Model Type
Source Object Type
Target Object Type
Knowledge map Knowledge map Knowledge map Knowledge map Knowledge map
requires has knowledge of requires
is required by is available at is required by
Position Position

Model Type Source Object Type Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Documented knowledge is documented in documents Cluster/Data model Documented knowledge is documented in documents Class Documented knowledge is managed with manages Application system type Documented knowledge Relationship Type (active) is managed with Relationship Type (passive) manages Application system class Target Object Type
ARIS Methods
11-734
Model Type
Source Object Type
Target Object Type
Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram Knowledge structure diagram
encompasses
belongs to
is documented in
documents
Entity type
Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Knowledge category Knowledge category
is documented in is documented in is documented in is documented in is documented in encompasses
documents
Information carrier
documents
Object instance
documents
Package
documents
Relationship type
documents
Technical term
belongs to
encompasses
belongs to
Knowledge category
ARIS Methods
11.2.44 Material diagram
11-735
Model Type
Source Object Type
Target Object Type
Knowledge category
is generalization of
is specialization of
Knowledge category
11.2.44 Material diagram

Model Type Source Object Type Material diagram Material diagram Material diagram Material diagram Material diagram Material diagram Material diagram Material diagram Packaging material class Packaging material class Packaging material type can encompass can belong to belongs to has assigned can encompass can belong to Material type is assigned to is assigned to Packaging material type Packaging material class Packaging material type Packaging material type Material type Material class can be assigned to can encompass can be assigned to can belong to Packaging material class Material type Material class belongs to has assigned Material type Material class Relationship Type (active) can encompass Relationship Type (passive) can belong to Material class Target Object Type
ARIS Methods
11.2.45 Material flow diagram
11-736
11.2.45 Material flow diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Material flow diagram Material flow diagram Material flow diagram Material flow diagram Material flow diagram Material flow diagram Material flow diagram Material flow diagram Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type is IT responsible for is technically responsible for is IT responsible for is technically responsible for carries out Material flow is received from carries out is carried out by is under IT responsibility of is under technical responsibility of is carried out by is under IT responsibility of is under technical responsibility of Function Function Function Function Function Function receives Function Function sends is sent from Material flow Target Object Type
ARIS Methods
11.2.46 Network diagram
11-737

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Network diagram Network diagram Network diagram Network diagram Hardware component Hardware component Hardware component is of type determines type of is connected to is connected to encompasses belongs to DBMS runs with is platform for Hardware component Hardware component Hardware component Hardware component type Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network connection Network connection is implemented by is located at is location of Network Network belongs to class is of type determines type of implements Hardware component Location Network type encompasses Network class Network is connected to is connected to Network Network encompasses belongs to Network Hardware component Network is located at is location of Location is located at is location of Location Target Object Type
ARIS Methods
11-738
Model Type
Source Object Type
Target Object Type
Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram
Network connection Network connection Network connection Network connection Network connection Network connection Network connection Network node
belongs to consists (hor.) of part of connection consists (vert.) of section encompasses is implemented by is of type ends in is implemented by
has assigned encompasses part of connection encompasses section belongs to implements
Network Network connection Network connection Network connection Network connection
determines type of is end of implements
Network connection type Network node Hardware component
Network node Network node Network node
is located at belongs to encompasses
is location of has assigned belongs to
Location Network Network connection
Network node Network node
encompasses is of type
belongs to determines type of
Network node Network node type
ARIS Methods
11-739
Model Type
Source Object Type
Target Object Type
Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram Network diagram
Operating system Organizational unit Organizational unit Person Person Person type Person type
runs with is responsible for is responsible for is responsible for is responsible for is responsible for is responsible for
is platform for is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of
Hardware component Hardware component Network
Hardware component Network Hardware component Network
Position Position
is responsible for is responsible for
Hardware component Network
ARIS Methods
11.2.47 Network topology
11-740

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Network topology DBMS type can run on can be platform for Hardware component type Network topology Hardware component class Network topology Hardware component class Network topology Hardware component type Network topology Network topology Network topology Network topology Network topology Location can realize Location can realize Hardware component type Hardware component type Location can realize can be realized at can be realized at can be realized at can encompass can belong to can be connected to can be connected to belongs to class encompasses can encompass can belong to can be connected to can be connected to Hardware component class Hardware component class Hardware component class Hardware component type Hardware component type Hardware component class Hardware component type Network class Target Object Type
ARIS Methods
11-741
Model Type
Source Object Type
Target Object Type
Network topology Network topology Network topology Network topology Network topology Network topology
can realize can realize can realize
can be realized at can be realized at can be realized at
Network connection type Network node type Network type
Network connection type Network connection type Network connection type
can be realized by can be realized by can consist (hor.) of part of connection
can realize
can realize
Network connection type
can encompass Network conpart of connection can encompass Network consection nection type nection type
Network topology
Network connection type
can consist (vert.) of section
Network topology Network topology Network topology Network topology
Network connection type Network connection type Network node type Network node type
can end in can occur can be connected to can be realized by
can be end point of can encompass can be connected to can realize
Network node type Network type Hardware component type Hardware component type
ARIS Methods
11-742
Model Type
Source Object Type
Target Object Type
Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology Network topology
Network node type Network node type Network node type Network node type Network protocol Network type Network type
can occur can be connected to can encompass
can encompass can be connected to can belong to
Network class Network node type Network node type
is used in is used in belongs to class can be connected to
uses uses encompasses can be connected to belongs to is successor of can be platform for
Network type Network type Network class Network type
Network type Network type Operating system type Organizational unit Person
encompasses is predecessor of can run on
Network type Network type Hardware component type Hardware component type Hardware component type
can be responsible for can be responsible for
can be under responsibility of can be under responsibility of
ARIS Methods
11-743
Model Type
Source Object Type
Target Object Type
Network topology
Person type
Hardware component type Hardware component type
Network topology
Position
ARIS Methods
11.2.48 Objective diagram
11-744
11.2.48 Objective diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Objective diagram Product/Service Product/Service Product/Service Product/Service Product/Service supports is supported by Objective is used by uses Function has transition to is consumed by is input for has input of Function has transition from consumes Function Function Objective belongs to encompasses Function Function has transition to produces has transition from is produced by Function has output of Function Critical factor is critical factor for supports has critical factor is supported by is output of Product/Service Product/Service Product/Service Objective Objective Objective Critical factor is superior is subordinate Critical factor Target Object Type
ARIS Methods
11.2.49 Office process
11-745

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Office process Office process Office process Application system Application system Application system Office process Office process Office process Application system Application system Application system type Office process Office process Office process Office process Application system type Application system type Application system type Application system type Office process Office process Application system type Application system type supports is supported by Function creates is created by Event can use can be used by ERM attribute can use can be used by can use can be used by Cluster/Data model Entity type uses is used by Class can use can be used by Class uses is used by uses is used by Relationship type Technical term uses is used by ERM attribute uses is used by uses is used by Cluster/Data model Entity type Target Object Type
ARIS Methods
11-746
Model Type
Source Object Type
Target Object Type
Office process Office process Office process Office process Office process Office process Office process Office process Office process
Application system type Application system type Class Class Class Class Class Cluster/Data model Cluster/Data model
can use can use has state is approved by is checked by is input for lies on has state is approved by
can be used by can be used by is state of approves checks has input of has information about is state of approves
Relationship type Technical term Event Function Function Function Information carrier Event Function
Office process Office process Office process
lies on is used by is used by
has information about uses uses
Information carrier Organizational unit Person type
ARIS Methods
11-747
Model Type
Source Object Type
Target Object Type
Cluster/Data model Documented knowledge Documented knowledge
is used by relates to is required for
uses relates to (passive) requires
Position Event Function
Office process Office process
Function Function
Office process
Employee variable
Function
Office process
Employee variable
Function
Office process
Employee variable
Function
ARIS Methods
11-748
Model Type
Source Object Type
Target Object Type
Office process
Employee variable
sends information on cancellation to result is forwarded by manages is state of approves checks has input of has information about is state of is compared to uses value of
Function
Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process
Employee variable Entity type Entity type Entity type Entity type Entity type Entity type ERM attribute ERM attribute ERM attribute
must inform about result of is managed by has state is approved by is checked by is input for lies on has state is compared to provides value for
Function Application system type Event Function Function Function Information carrier Event Event Event
Office process Office process Office process Office process Office process Office process
ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event
is approved by is checked by is input for lies on defines screen field activates
approves checks has input of has information about has screen field is activated by
Function Function Function Information carrier Screen Application system type
ARIS Methods
11-749
Model Type
Source Object Type
Target Object Type
Event Event Event Event Event Event Event Event Event Event
activates is used by activates activates is used by is used by is used by is used by is used by corresponds to
is activated by uses is activated by is activated by uses uses uses uses uses corresponds to
Function Group IT function type Module type Organizational unit Organizational unit type Person Person type Position Product/Service
Office process Office process Office process Office process
is evaluated by activates reads reads
evaluates is activated by is read by is read by
Rule Screen Attribute type group Business object
ARIS Methods
11-750
Model Type
Source Object Type
Target Object Type
distributes has output of reads archives
is distributed by is output of is read by is archived by
Class Class Class Cluster/Data model
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type
has output of reads reads
is output of is read by is read by
Function Function
reads creates
is read by is created by
COT attribute Documented knowledge
Function Function
reads archives
is read by is archived by
Documented knowledge Entity type
ARIS Methods
11-751
Model Type
Source Object Type
Target Object Type
Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process
Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
changes creates deletes distributes has output of reads archives changes creates deletes distributes has output of reads creates is predecessor of produces
is changed by is created by is deleted by is distributed by is output of is read by is archived by is changed by is created by is deleted by is distributed by is output of is read by is created by follows is produced by
Entity type Entity type Entity type Entity type Entity type Entity type ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event Function General resource
Function Function
reads creates output to
is read by is output medium for
General resource Information carrier
ARIS Methods
11-752
Model Type
Source Object Type
Target Object Type
Function Function
is read by measures
Information carrier Key performance indicator instance
creates reads is carried out at
is created by is read by is performed in
Knowledge category Knowledge category Location
supports has output of reads requires
is supported by is output of is read by is required by
Objective Package Package Packaging material type
has output of produces archives
is output of is produced by is archived by
Product/Service Product/Service Relationship type
Function Function
changes creates
is changed by is created by
ARIS Methods
11-753
Model Type
Source Object Type
Target Object Type
reads leads to is represented by
is read by is assigned to represents
Relationship type Rule Screen
Office process
Function
requires
is required by
Office process Office process Office process Office process Office process
archives changes creates deletes distributes
is archived by is changed by is created by is deleted by is distributed by
has output of reads accesses
is output of is read by is accessed by
Technical term Technical term Transport system type
ARIS Methods
11-754
Model Type
Source Object Type
Target Object Type
Office process
Function
requires
is required by
General resource General resource General resource General resource
is compared to is consumed by is defined is used by
is compared to consumes can be processed by/with uses
Group Group Group
is used by can be used by development is under responsibility of is under technical responsibility of can be used by
Application system Application system class Application system class Application system class Application system type
Office process
Group
Office process
Group
can be user
Office process
Group
ARIS Methods
11-755
Model Type
Source Object Type
Target Object Type
Office process
Group
Group Group Group Group Group
accesses is owner of accesses is owner of provides
is accessed by has owner is accessed by has owner is provided by
Class Class Cluster/Data model Cluster/Data model Cluster/Data model
Group Group Group
is accessed by has owner has specimen owner is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner
Complex object type Complex object type Complex object type COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute
Office process Office process Office process Office process Office process Office process Office process
Group Group Group Group Group Group Group
ARIS Methods
11-756
Model Type
Source Object Type
Target Object Type
Group Group Group Group Group Group
Group Group
Function Function
Group Group
Function Function
Group Group
Function Function
Office process
Group
Function
ARIS Methods
11-757
Model Type
Source Object Type
Target Object Type
Group Group Group
provides is user is responsible for development of
is provided by is used by development is under responsibility of is under technical responsibility of is used by
Information carrier IT function IT function type
Office process
Group
Office process
Group
is user
Group Group Group
Office process
Group
Module type
Group Group
Group Group
ARIS Methods
11-758
Model Type
Source Object Type
Target Object Type
Office process
stores
is stored on
Office process
stores
is stored on
Class
Office process
stores
is stored on
Cluster/Data model
Office process
stores
is stored on
Entity type
Office process
stores
is stored on
ERM attribute
Office process
stores
is stored on
Relationship type
Office process
stores
is stored on
Technical term
Office process
Information carrier
provides input for is used by is used by
gets input from uses uses
Function
Group Organizational unit
ARIS Methods
11-759
Model Type
Source Object Type
Target Object Type
Information carrier Information carrier IT function
Person type Position Cluster/Data model
IT function IT function IT function IT function IT function type IT function type IT function type
uses uses uses uses can use can use uses
is used by is used by is used by is used by can be used by can be used by is used by
Entity type ERM attribute Relationship type Technical term Class Cluster/Data model Cluster/Data model
Office process
IT function type
uses
is used by
Entity type
ARIS Methods
11-760
Model Type
Source Object Type
Target Object Type
can use uses creates
can be used by is used by is created by
can use uses can use uses
can be used by is used by can be used by is used by
Office process
is measured upon occurrence relates to is required for accesses is owner of accesses is owner of
triggers measuring
Event
Knowledge category Knowledge category Location Location Location Location
relates to (passive) requires is accessed by has owner is accessed by has owner
Event Function Class Class Cluster/Data model Cluster/Data model
ARIS Methods
11-761
Model Type
Source Object Type
Target Object Type
accesses is owner of accesses is owner of accesses is owner of accesses is owner of accesses is owner of
is accessed by has owner is accessed by has owner is accessed by has owner is accessed by has owner is accessed by has owner
Complex object type Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Relationship type Relationship type
Location Location Material type Module
accesses is owner of is partly consumed uses
is accessed by has owner partly consumes is used by
Technical term Technical term Function Cluster/Data model
uses uses uses uses
Entity type ERM attribute Relationship type Technical term
ARIS Methods
11-762
Model Type
Source Object Type
Target Object Type
can use can use
can be used by can be used by
Module type Module type Module type Module type Module type Operating resource type
can use can use creates can use can use can encompass
can be used by can be used by is created by can be used by can be used by can belong to
Entity type ERM attribute Event Relationship type Technical term Application system type
Operating resource type Organizational unit Organizational unit
is operating resource of is user can be user
has operating resource is used by can be used by
Function Application system Application system class
Office process
Organizational unit
Office process
Organizational unit
Office process
Organizational unit
can be user
can be used by
ARIS Methods
11-763
Model Type
Source Object Type
Target Object Type
Office process
Organizational unit
Office process
Organizational unit
is specimen owner of provides accesses
has specimen owner is provided by is accessed by
ARIS Methods
11-764
Model Type
Source Object Type
Target Object Type
accesses is owner of is specimen owner of is owner of
is accessed by has owner has specimen owner has owner
ERM attribute ERM attribute ERM attribute Event
Office process
Organizational unit
contributes to
Function
Office process
Organizational unit
decides on
is decided by
Function
ARIS Methods
11-765
Model Type
Source Object Type
Target Object Type
Office process
Organizational unit
Function
is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of provides
Function Function
Function Function
is user is responsible for development of is technically responsible for is user
Office process
Organizational unit
Office process
Organizational unit
ARIS Methods
11-766
Model Type
Source Object Type
Target Object Type
Office process
Organizational unit
Module type
Organizational unit Organizational unit Organizational unit type
accesses is owner of is responsible for development of is technically responsible for can be user
is accessed by has owner development is under responsibility of is under technical responsibility of can be used by
Technical term Technical term Application system Application system Application system class
Office process
Office process
ARIS Methods
11-767
Model Type
Source Object Type
Target Object Type
Office process
Office process
Office process
ARIS Methods
11-768
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of is owner of
has owner is accessed by has owner has owner
Office process
contributes to
Function
Office process
decides on
is decided by
Function
ARIS Methods
11-769
Model Type
Source Object Type
Target Object Type
Office process
Function
is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of can be user
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by can be used by
Function Function
Function Function
Office process
IT function
Office process
IT function
ARIS Methods
11-770
Model Type
Source Object Type
Target Object Type
Office process
IT function type
Office process
Module
Office process
Module
Office process
Module type
Office process
Module type
Office process
Module type
Organizational unit type Package Package
ARIS Methods
11-771
Model Type
Source Object Type
Target Object Type
is used by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by has owner is accessed by has owner is accessed by
Application system Application system class Application system class Application system class Application system type Application system type Application system type Class Class Cluster/Data model Cluster/Data model Complex object type
Office process
Person
Person Person
Office process
Person
Person Person Person Person Person
accesses is owner of accesses is owner of accesses
ARIS Methods
11-772
Model Type
Source Object Type
Target Object Type
has owner is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by
Complex object type COT attribute COT attribute COT attribute
Office process Office process Office process Office process Office process Office process Office process Office process Office process
Person Person Person Person Person Person Person Person Person
accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out
Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function
Office process
Person
contributes to
Function
Person Person
Function Function
Office process
Person
Function
ARIS Methods
11-773
Model Type
Source Object Type
Target Object Type
Office process
Person
Function
Person Person
result is forwarded to sends information on cancellation to result is forwarded by is used by development is under responsibility of is under technical responsibility of
Function Function
must inform about result of is user is responsible for development of
Function IT function IT function type
Office process
Person
IT function type
is user is user can be user is responsible for development of
is used by is used by can be used by development is under responsibility of is under technical responsibility of
IT function type Module Module type Module type
Office process
Person
Module type
ARIS Methods
11-774
Model Type
Source Object Type
Target Object Type
Person Person Person Person Person type Person type
accesses is owner of accesses is owner of can be user is responsible for development of
is accessed by has owner is accessed by has owner can be used by development is under responsibility of is under technical responsibility of
Relationship type Relationship type Technical term Technical term Application system Application system
Office process
Person type
Application system
Office process
Person type
ARIS Methods
11-775
Model Type
Source Object Type
Target Object Type
Office process
Person type
accesses is owner of accesses is owner of provides
is accessed by has owner is accessed by has owner is provided by
Class Class Cluster/Data model Cluster/Data model Cluster/Data model
Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process
Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type
accesses is owner of accesses is owner of accesses is owner of accesses is owner of is owner of provides accepts
is accessed by has owner is accessed by has owner is accessed by has owner is accessed by has owner has owner is provided by is accepted by
Complex object type Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Event Event Function
ARIS Methods
11-776
Model Type
Source Object Type
Target Object Type
Function Function
Function Function
Office process
Person type
Function
Office process
Person type
Function
Function Function
ARIS Methods
11-777
Model Type
Source Object Type
Target Object Type
Office process
Person type
IT function
Office process
Person type
can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of is accessed by
Module Module
Office process
Person type
Module
Office process
Person type
Module type
Office process
Person type
accesses
Relationship type
ARIS Methods
11-778
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of is user
Relationship type Technical term Technical term Application system
Position Position
Office process
Position
Position Position
Application system type Application system type Application system type Class Class Cluster/Data model
Office process
Position
ARIS Methods
11-779
Model Type
Source Object Type
Target Object Type
Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process Office process
Position Position Position Position Position Position Position Position Position Position Position Position Position
is owner of accesses is owner of is specimen owner of accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out
has owner is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by
Complex object type COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function
Office process
Position
contributes to
Function
ARIS Methods
11-780
Model Type
Source Object Type
Target Object Type
Position Position
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is provided by is used by development is under responsibility of is under technical responsibility of is used by
Function Function
Office process
Position
Function
Office process
Position
Function
Office process
Position
Function
Office process
Position
Function
must inform about result of provides is user is responsible for development of
Function Information carrier IT function IT function type IT function type IT function type
Office process
Position
Office process
Position
is user
ARIS Methods
11-781
Model Type
Source Object Type
Target Object Type
is used by can be used by development is under responsibility of is under technical responsibility of is accessed by has owner is accessed by has owner is compared to consumes has input of
Office process
Position
Module type
Position Position Position Position Product/Service Product/Service Product/Service
accesses is owner of accesses is owner of is compared to is consumed by is input for
Relationship type Relationship type Technical term Technical term Event Function Function
Product/Service Relationship type Relationship type
is used by is managed by has state
uses manages is state of
Function Application system type Event
ARIS Methods
11-782
Model Type
Source Object Type
Target Object Type
Relationship type Rule Rule Rule Screen Screen Screen
lies on leads to activates links can use can use can use
has information about is dependent on is activated by is linked by can be used by can be used by can be used by
Information carrier Event Function Rule Class Cluster/Data model Complex object type
Screen Screen Screen Screen Screen
can use can use can use creates can use
can be used by can be used by can be used by is created by can be used by
COT attribute Entity type ERM attribute Event Relationship type
Office process
Screen
can use
can be used by
Technical term
ARIS Methods
11-783
Model Type
Source Object Type
Target Object Type
Office process
can encompass
can belong to
Technical term Technical term Technical term Technical term Technical term Transport system type
has state is approved by is checked by is input for lies on can encompass
is state of approves checks has input of has information about can belong to
Event Function Function Function Information carrier Application system type
Office process
can encompass
can belong to
Assignment Relationship Office process
ARIS Methods
11.2.50 OMT Class description model
11-784
11.2.50 OMT Class description model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) OMT Class description model OMT Class description model Class has operation is operation of Operation Class has attribute is attribute of ERM attribute Target Object Type
11.2.51 OMT Data value decomposition

Model Type Source Object Type OMT Data value decomposition Data value Relationship Type (active) is composed of Relationship Type (passive) is part of Data value Target Object Type
11.2.52 OMT Dynamic model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) OMT Dynamic model OMT Dynamic model OMT Dynamic model State State has transition to has associated has transition from is associated Event/action pair Class State has associated is associated Activity Target Object Type
ARIS Methods
11.2.53 OMT Functional model
11-785
Model Type
Source Object Type
Target Object Type
OMT Dynamic model
State
has transition to
has transition from
State
Source Object Type
Target Object Type
OMT Dynamic model
State
is substate
has substate
State
11.2.53 OMT Functional model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) OMT Functional model OMT Functional model OMT Functional model OMT Functional model OMT Functional model OMT Functional model Data value is received from receives Actor Data store sends is sent from Data value Data store sends receives Actor Connector splits to is splitted by Data value Actor sends is sent from Data value Actor sends receives Data store Target Object Type
ARIS Methods
11.2.54 OMT Object model
11-786
Model Type
Source Object Type
Target Object Type
OMT Functional model OMT Functional model OMT Functional model OMT Functional model
Data value Data value Data value
is composed by is received from is received from
composes receives receives
Connector Data store Process
Process
sends
is sent from
Data value
Assignment Relationship OMT Functional model
Source Object Type Process
Relationship Type (active) has subprocess
Relationship Type (passive) is subprocess of
Target Object Type Process

Model Type Source Object Type OMT Object model OMT Object model OMT Object model Association has attribute is attribute of ERM attribute Association is defined by defines Class Association Relationship Type (active) constrains Relationship Type (passive) is constrained Association Target Object Type
ARIS Methods
11-787
Model Type
Source Object Type
Target Object Type
OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model
Association Association instance Association instance Class Class Class Class
has operation constrains is defined by
is operation of is constrained defines
Operation Association instance Object instance
defines an association aggregates propagates has attribute
is defined by is aggregated is propagated is attribute of
Association Class Class ERM attribute
Class Class Class
has operation is subtype of is supertype of
is operation of has subtype has supertype
Operation Sp./gen. operator Sp./gen. operator
Constraint Constraint Constraint
concerns concerns concerns
is concerned by is concerned by is concerned by
Association Class ERM attribute
ARIS Methods
11-788
Model Type
Source Object Type
Target Object Type
OMT Object model OMT Object model OMT Object model OMT Object model OMT Object model
Constraint ERM attribute Object instance Object instance Sp./gen. operator
concerns propagates is instance of
is concerned by is propagated by has instance
Object instance ERM attribute Class
is linked to is discriminator of
is linked to is discriminated by
Object instance ERM attribute
ARIS Methods
11.2.55 Organizational chart
11-789

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational unit is located at Location performs is performed by is location of Location Person type Location encompasses Group is composed of Group performs Group belongs to has as employee is performed by is a component of is located at Location Position Person type Person type Group is managed by manages Person Group has member is member of Group is assigned to is assigned to Organizational unit Person Group is located at is location of Location Group Group cooperates with is superior cooperates with is subordinate Group Group Target Object Type
ARIS Methods
11-790
Model Type
Source Object Type
Target Object Type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
is composed of is disciplinary superior to is responsible for is superior is technical superior to is of type belongs to belongs to
is a component of has the disciplinary superior is assigned to is subordinate has the technical superior determines type of has as employee has as employee
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Person Person type
performs is composed of is disciplinary superior to is technical superior to
is performed by is a component of has the disciplinary superior has the technical superior
Position
ARIS Methods
11-791
Model Type
Source Object Type
Target Object Type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Person
can be constituent can be disciplinary superior can be technical superior performs is organization manager for
can have as constituent can have disciplinary superior can have technical superior is performed by is under organizational responsibility of is location of
Organizational unit type Organizational unit type Organizational unit type Person type Group
Person
is located at
Location
Person
is organization manager for
is under organizational responsibility of
Location
Organizational chart Organizational chart Organizational chart Organizational chart
Person Person
belongs to is organization manager for
has as employee is under organizational responsibility of is under organizational responsibility of is under organizational responsibility of
Organizational unit Organizational unit Organizational unit type Person
Person
Person
ARIS Methods
11-792
Model Type
Source Object Type
Target Object Type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
substitutes for is of type is organization manager for
is substituted by determines type of is under organizational responsibility of is performed by is under organizational responsibility of is occupied by
Person Person
performs is organization manager for
Person
occupies
Position
substitutes for belongs to can belong to
is substituted by has as employee can have as employee
Position Organizational unit Organizational unit type Person type Person type Person type
is composed of is generalization of is in conflict with
is a component of is specialization of is in conflict with
ARIS Methods
11-793
Model Type
Source Object Type
Target Object Type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
occupies is organization manager for
is occupied by is under organizational responsibility of has position is location of is under organizational responsibility of has the disciplinary superior is under organizational responsibility of has the technical superior determines type of is under organizational responsibility of is under organizational responsibility of
Position Group
is position of is located at is organization manager for
Group Location Location
Position
Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Person
Position
Position
is technical superior to
Position Position
is of type is organization manager for
Position
ARIS Methods
11-794
Model Type
Source Object Type
Target Object Type
Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart
Position Position
substitutes for is organization manager for
is substituted by is under organizational responsibility of is performed by has the disciplinary superior is under organizational responsibility of has the technical superior is substituted by
Person Person type
Position Position
performs is disciplinary superior to
Position
Position
Position Position
Position Position
System organizational unit System organizational unit System organizational unit System organizational unit
depicts depicts has assigned
is depicted by is depicted by is assigned to
Organizational unit Position System organizational unit
is of type
determines type of
System organizational unit type
ARIS Methods
11-795
Model Type
Source Object Type
Target Object Type
depicts
is depicted by
Organizational unit
depicts
is depicted by
Organizational chart Organizational chart Organizational chart
System organizational unit type System organizational unit type System organizational unit type
is assigned 1:1
is assigned 1:1
is assigned 1:n
is assigned n:1
is assigned n:m
is assigned m:n
Assignment Relationship Organizational chart Organizational chart Organizational chart Organizational chart
Source Object Type Location Location
Relationship Type (active) is located at encompasses
Relationship Type (passive) is location of is located at
Target Object Type Group Location
Location Location
is located at is located at
is location of is location of
Organizational unit Person type
ARIS Methods
11.2.56 PCD
11-796
Source Object Type
Target Object Type
Location
is located at
is location of
Position
11.2.56 PCD
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) PCD PCD PCD Application system Application system Application system PCD PCD PCD PCD Application system Application system Application system Application system PCD PCD Application system Application system uses supports is supported by is used by Relationship type Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by Cluster/Data model Complex object type COT attribute uses is used by uses is used by Attribute type group Class Target Object Type
ARIS Methods
11.2.56 PCD
11-797
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
uses supports uses
Technical term Function Attribute type group
PCD PCD PCD PCD
can use uses can use can use
can be used by is used by can be used by can be used by
Class Class Cluster/Data model Complex object type
PCD PCD PCD
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-798
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Application system type Attribute type group Attribute type group
PCD PCD PCD PCD
is input for lies on is required for relates to
has input of has information about requires has
Function Information carrier Function Technical term
PCD PCD PCD PCD PCD PCD PCD
Business object Class Class Class Class Class Cluster/Data model
is input for has state is approved by is checked by is input for lies on has state
has input of is state of approves checks has input of has information about is state of
Function Event Function Function Function Information carrier Event
PCD
Cluster/Data model
is approved by
approves
Function
ARIS Methods
11.2.56 PCD
11-799
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD PCD PCD
lies on is used by is used by is used by
has information about uses uses uses
Information carrier Organizational unit Person type Position
PCD PCD PCD
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-800
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Information carrier Attribute type group Cluster/Data model
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Component Component Component Component Component Component Component Cost driver COT attribute COT attribute COT attribute COT attribute COT attribute COT attribute
can use can use can use can use supports can use can use influences has state is compared to provides value for is approved by is checked by is input for
can be used by can be used by can be used by can be used by is supported by can be used by can be used by is influenced by is state of is compared to uses value of approves checks has input of
Complex object type COT attribute Entity type ERM attribute Function Relationship type Technical term Function Event Event Event Function Function Function
ARIS Methods
11.2.56 PCD
11-801
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
lies on relates to is required for
has information about relates to (passive) requires
PCD PCD PCD PCD PCD PCD PCD PCD
Element type Element type Element type Element type Element type Element type Employee variable Employee variable
has state is compared to provides value for is approved by is checked by is input for is different from is disciplinary superior to is technical superior to substitutes for accepts carries out
is state of is compared to uses value of approves checks has input of is different from has the disciplinary superior has the technical superior is substituted by is accepted by is carried out by
Event Event Event Function Function Function Employee variable Employee variable Employee variable Employee variable Function Function
PCD
Employee variable
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-802
Model Type
Source Object Type
Target Object Type
PCD
Employee variable
contributes to
Function
PCD PCD
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of is employee variable is employee variable is employee variable
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by has employee variable has employee variable has employee variable
Function Function
PCD PCD
Function Function
PCD PCD
Function Function
PCD
Employee variable
Function
PCD PCD PCD
Group Location Organizational unit
ARIS Methods
11.2.56 PCD
11-803
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
is employee variable is employee variable is employee variable is managed by is managed by has state is approved by is checked by is input for lies on has state is compared to provides value for is approved by is checked by is input for lies on
has employee variable has employee variable has employee variable manages manages is state of approves checks has input of has information about is state of is compared to uses value of approves checks has input of has information about
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Entity type Entity type Entity type Entity type Entity type Entity type Entity type ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute
Application system type Component Event Function Function Function Information carrier Event Event Event Function Function Function Information carrier
ARIS Methods
11.2.56 PCD
11-804
Model Type
Source Object Type
Target Object Type
ERM attribute Event Event Event Event Event Event
defines screen field activates activates is used by activates activates is used by
has screen field is activated by is activated by uses is activated by is activated by uses
Screen Application system type Function Group IT function type Module type Organizational unit
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Event Event Event Event Event Event Event Function Function Function
is used by is used by is used by is used by corresponds to is evaluated by activates archives changes creates
uses uses uses uses corresponds to evaluates is activated by is archived by is changed by is created by
Organizational unit type Person Person type Position Product/Service Rule Screen Attribute type group Attribute type group Attribute type group
ARIS Methods
11.2.56 PCD
11-805
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD PCD PCD
reads has knowledge of has output of reads
is read by is available at is output of is read by
Attribute type group Authorization condition Business object Business object
PCD PCD PCD PCD PCD
Class Class Class Class Class
PCD PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-806
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type
PCD PCD PCD PCD
PCD PCD PCD
Complex object type Complex object type Complex object type Complex object type Complex object type Component
PCD PCD PCD
PCD
Function
belongs to
is assigned to
Cost category
ARIS Methods
11.2.56 PCD
11-807
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD
COT attribute COT attribute COT attribute COT attribute COT attribute
PCD PCD PCD PCD PCD
has output of reads creates reads can create
is output of is read by is created by is read by can be created by
COT attribute COT attribute Documented knowledge Documented knowledge Draft list
can use archives changes creates deletes distributes has output of reads archives changes
can be used by is archived by is changed by is created by is deleted by is distributed by is output of is read by is archived by is changed by
Draft list Element type Element type Element type Element type Element type Element type Element type Entity type Entity type
ARIS Methods
11.2.56 PCD
11-808
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
creates deletes distributes has output of reads archives changes creates deletes distributes has output of reads creates calls is predecessor of reads
is created by is deleted by is distributed by is output of is read by is archived by is changed by is created by is deleted by is distributed by is output of is read by is created by is called by follows is read by
Entity type Entity type Entity type Entity type Entity type ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Event Function Function General resource
PCD PCD
Function Function
creates output to reads
is output medium for is read by
ARIS Methods
11.2.56 PCD
11-809
Model Type
Source Object Type
Target Object Type
PCD
Function
is measured by
measures
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Function Function Function Function Function Function Function Function Function Function Function Function
creates has knowledge of reads creates uses is carried out at supports has output of reads has output of produces archives
is created by is available at is read by is created by is used by is performed in is supported by is output of is read by is output of is produced by is archived by
Knowledge category Knowledge category Knowledge category List List Location Objective Package Package Product/Service Product/Service Relationship type
PCD
Function
changes
is changed by
Relationship type
ARIS Methods
11.2.56 PCD
11-810
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Relationship type Relationship type Relationship type Relationship type Relationship type Rule Screen Screen design Technical term Technical term Technical term Technical term Technical term
has output of reads leads to is represented by can use archives changes creates deletes distributes
is output of is read by is assigned to represents can be used by is archived by is changed by is created by is deleted by is distributed by
PCD PCD PCD PCD
Function Function General resource General resource
has output of reads is compared to is defined
is output of is read by is compared to can be processed by/with
Technical term Technical term Event Function
ARIS Methods
11.2.56 PCD
11-811
Model Type
Source Object Type
Target Object Type
PCD
Group
Application system
PCD
Group
Application system
PCD PCD PCD
Group Group Group
PCD
Group
PCD PCD
Group Group
PCD
Group
PCD
Group
accesses
PCD
Group
is owner of
has owner
ARIS Methods
11.2.56 PCD
11-812
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD PCD PCD PCD
Group Group Group Group Group Group Group Group
has knowledge of requires accesses is owner of accesses is owner of provides accesses
is available at is required by is accessed by has owner is accessed by has owner is provided by is accessed by
Authorization condition Authorization condition Class Class Cluster/Data model Cluster/Data model Cluster/Data model Complex object type
PCD PCD PCD PCD
is owner of is specimen owner of can be user is responsible for development of
has owner has specimen owner can be used by development is under responsibility of is under technical responsibility of is accessed by
PCD
Group
Component
PCD
Group
accesses
COT attribute
ARIS Methods
11.2.56 PCD
11-813
Model Type
Source Object Type
Target Object Type
PCD PCD
Group Group
is owner of is specimen owner of
has owner has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by
PCD PCD PCD PCD PCD PCD PCD PCD PCD
Group Group Group Group Group Group Group Group Group
accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out
Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function
PCD
Group
contributes to
Function
PCD PCD
Group Group
Function Function
PCD
Group
Function
PCD
Group
Function
ARIS Methods
11.2.56 PCD
11-814
Model Type
Source Object Type
Target Object Type
PCD PCD
Group Group
Function Function
PCD PCD
Group Group
PCD PCD
Group Group
PCD
Group
IT function
PCD PCD
Group Group
PCD
Group
PCD
Group
is user
ARIS Methods
11.2.56 PCD
11-815
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Group Group Group
is available at is required by development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of is accessed by
PCD
Group
Module
PCD PCD PCD
Group Group Group
PCD
Group
Module type
PCD
Group
accesses
Relationship type
PCD PCD PCD PCD
Group Group Group Hardware component type
is owner of accesses is owner of stores
has owner is accessed by has owner is stored on
ARIS Methods
11.2.56 PCD
11-816
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Hardware component type Hardware component type Hardware component type
PCD PCD PCD PCD
stores stores stores stores
is stored on is stored on is stored on is stored on
COT attribute Entity type ERM attribute Relationship type
PCD PCD PCD
Hardware component type Information carrier Information carrier
stores has state provides input for is used by is used by is used by
is stored on is state of gets input from uses uses uses
Technical term Event Function
PCD PCD PCD
Group Organizational unit Person type
ARIS Methods
11.2.56 PCD
11-817
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD PCD PCD PCD PCD
Information carrier IT function IT function IT function IT function IT function IT function IT function IT function
is used by uses uses uses uses uses uses uses supports
uses is used by is used by is used by is used by is used by is used by is used by is supported by
Position Attribute type group Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute Function
PCD PCD PCD PCD PCD PCD
uses uses uses can use uses can use
is used by is used by is used by can be used by is used by can be used by
Relationship type Technical term Attribute type group Class Class Cluster/Data model
PCD
IT function type
uses
is used by
Cluster/Data model
ARIS Methods
11.2.56 PCD
11-818
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
can use uses can use uses can use uses can use uses creates relates to supports supports when time limit is exceeded
can be used by is used by can be used by is used by can be used by is used by can be used by is used by is created by relates to (passive) is supported by supports when time limit is exceeded (passive) is supported by supports when time limit is exceeded (passive)
Complex object type Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Event Event Event Event
PCD PCD
Function Function
ARIS Methods
11.2.56 PCD
11-819
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD
IT function type IT function type IT function type IT function type Key performance indicator instance
can use uses can use uses is measured upon occurrence relates to
can be used by is used by can be used by is used by triggers measuring relates to (passive)
Relationship type Relationship type Technical term Technical term Event
PCD
Knowledge category
Event
PCD PCD PCD
Knowledge category List Location
PCD PCD PCD
PCD PCD
Location Location
Class Class
ARIS Methods
11.2.56 PCD
11-820
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
is owner of accesses is owner of accesses is owner of accesses is owner of has knowledge of requires accesses
has owner is accessed by has owner is accessed by has owner is accessed by has owner is available at is required by is accessed by
Complex object type COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Knowledge category Knowledge category Relationship type
PCD PCD PCD PCD
Location Location Location Module
is owner of accesses is owner of uses
ARIS Methods
11.2.56 PCD
11-821
Model Type
Source Object Type
Target Object Type
PCD PCD
Module Module
uses uses
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Module Module Module Module Module Module Module Module type Module type Module type Module type Module type Module type Module type Module type Module type
uses uses uses uses supports uses uses uses can use uses can use can use can use can use can use creates
is used by is used by is used by is used by is supported by is used by is used by is used by can be used by is used by can be used by can be used by can be used by can be used by can be used by is created by
Complex object type COT attribute Entity type ERM attribute Function Relationship type Technical term Attribute type group Class Class Cluster/Data model Complex object type COT attribute Entity type ERM attribute Event
ARIS Methods
11.2.56 PCD
11-822
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD PCD
Module type Module type Module type Operating resource Operating resource
supports can use can use encompasses is alternative operating resource of is operating resource of encompasses
is supported by can be used by can be used by belongs to has alternative operating resource has operating resource belongs to
Function Relationship type Technical term Application system Function
PCD PCD
Operating resource Operating resource
PCD PCD
Operating resource Organizational unit
encompasses is responsible for development of is technically responsible for is user can be user
belongs to development is under responsibility of is under technical responsibility of is used by can be used by
Module Application system Application system Application system Application system class
PCD
Organizational unit
PCD PCD
ARIS Methods
11.2.56 PCD
11-823
Model Type
Source Object Type
Target Object Type
PCD
Organizational unit
PCD
Organizational unit
PCD PCD
PCD
Organizational unit
PCD PCD PCD
accesses is owner of has knowledge of requires accesses is owner of
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-824
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
accesses is owner of is specimen owner of provides accesses is owner of can be user
is accessed by has owner has specimen owner is provided by is accessed by has owner can be used by
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type Complex object type Component
PCD PCD PCD PCD
PCD
Organizational unit
Component
PCD
Organizational unit
Component
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-825
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD PCD PCD
PCD PCD PCD
PCD
Organizational unit
decides on
is decided by
Function
PCD
Organizational unit
Function
ARIS Methods
11.2.56 PCD
11-826
Model Type
Source Object Type
Target Object Type
PCD PCD
Function Function
PCD PCD
Function Function
PCD PCD
PCD
Organizational unit
provides
is provided by
Information carrier
PCD
Organizational unit
IT function
PCD
Organizational unit
IT function
PCD PCD
ARIS Methods
11.2.56 PCD
11-827
Model Type
Source Object Type
Target Object Type
PCD
Organizational unit
IT function type
PCD PCD PCD PCD
PCD
Organizational unit
Module
PCD
Organizational unit
Module
PCD PCD
can be user is responsible for development of is technically responsible for accesses
PCD
Organizational unit
Module type
PCD
Organizational unit
Relationship type
ARIS Methods
11.2.56 PCD
11-828
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD
PCD
Application system
PCD PCD
PCD
PCD PCD
ARIS Methods
11.2.56 PCD
11-829
Model Type
Source Object Type
Target Object Type
PCD
PCD PCD PCD PCD
PCD PCD PCD
PCD PCD PCD
PCD
can be user
can be used by
Component
ARIS Methods
11.2.56 PCD
11-830
Model Type
Source Object Type
Target Object Type
PCD
Component
PCD
Component
PCD PCD PCD PCD
PCD PCD PCD
PCD PCD PCD
ARIS Methods
11.2.56 PCD
11-831
Model Type
Source Object Type
Target Object Type
PCD
contributes to
Function
PCD PCD
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of can be user is responsible for development of is technically responsible for
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of
Function Function
PCD PCD
Function Function
PCD PCD
Function Function
PCD
Function
PCD PCD
PCD
IT function
ARIS Methods
11.2.56 PCD
11-832
Model Type
Source Object Type
Target Object Type
PCD PCD
can be user is responsible for development of is technically responsible for has knowledge of requires can be user
PCD
PCD PCD PCD
PCD
Module
PCD
Module
PCD PCD
PCD
Module type
ARIS Methods
11.2.56 PCD
11-833
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD PCD PCD
Organizational unit type Package Package Person
is owner of contains is input for is responsible for development of
has owner is contained by has input of development is under responsibility of is under technical responsibility of is used by can be used by
Technical term Function Function Application system Application system Application system Application system class
PCD
Person
PCD PCD
Person Person
is user can be user
PCD
Person
PCD
Person
ARIS Methods
11.2.56 PCD
11-834
Model Type
Source Object Type
Target Object Type
PCD PCD
Person Person
PCD
Person
PCD PCD PCD
PCD PCD PCD PCD
PCD PCD PCD
PCD
Person
can be user
can be used by
Component
ARIS Methods
11.2.56 PCD
11-835
Model Type
Source Object Type
Target Object Type
PCD
Person
Component
PCD
Person
Component
PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD PCD
Person Person Person Person Person Person Person Person Person Person Person Person Person
accesses is owner of is specimen owner of accesses is owner of accesses is owner of is specimen owner of is owner of provides accepts carries out contributes to
is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner has specimen owner has owner is provided by is accepted by is carried out by is worked on by collaboration of
COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute ERM attribute Event Event Function Function Function
PCD
Person
decides on
is decided by
Function
ARIS Methods
11.2.56 PCD
11-836
Model Type
Source Object Type
Target Object Type
PCD
Person
Function
PCD PCD
Person Person
Function Function
PCD PCD
Person Person
Function Function
PCD PCD
Person Person
PCD
Person
development is under responsibility of is under technical responsibility of is used by development is under responsibility of
IT function
PCD
Person
IT function
PCD PCD
Person Person
ARIS Methods
11.2.56 PCD
11-837
Model Type
Source Object Type
Target Object Type
PCD
Person
IT function type
PCD PCD PCD PCD
is used by is available at is required by development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of
PCD
Person
Module
PCD PCD PCD
PCD
Person
Module type
PCD PCD
Person Person
ARIS Methods
11.2.56 PCD
11-838
Model Type
Source Object Type
Target Object Type
PCD PCD PCD PCD
Person Person Person type Person type
is accessed by has owner can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
Technical term Technical term Application system Application system Application system Application system class Application system class Application system class Application system type
PCD
Person type
PCD PCD
PCD
Person type
PCD
Person type
can be user
PCD
Person type
PCD
Person type
ARIS Methods
11.2.56 PCD
11-839
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD PCD PCD PCD PCD
requires accesses is owner of accesses is owner of
is required by is accessed by has owner is accessed by has owner
Authorization condition Class Class Cluster/Data model Cluster/Data model
PCD PCD PCD
PCD PCD
Component Component
PCD
Person type
Component
ARIS Methods
11.2.56 PCD
11-840
Model Type
Source Object Type
Target Object Type
Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type
accesses is owner of accesses is owner of accesses is owner of is owner of provides accepts carries out
is accessed by has owner is accessed by has owner is accessed by has owner has owner is provided by is accepted by is carried out by
COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute Event Event Function Function
PCD
Person type
contributes to
Function
PCD PCD
Function Function
PCD
Person type
Function
PCD
Person type
Function
PCD
Person type
Function
ARIS Methods
11.2.56 PCD
11-841
Model Type
Source Object Type
Target Object Type
PCD
Person type
sends information on cancellation to result is forwarded by is provided by can be used by development is under responsibility of is under technical responsibility of
Function
PCD PCD PCD PCD
must inform about result of provides can be user is responsible for development of
Function Information carrier IT function IT function
PCD
Person type
IT function
PCD PCD
can be used by development is under responsibility of is under technical responsibility of is available at is required by
PCD
Person type
PCD PCD
PCD
Person type
can be user
can be used by
Module
ARIS Methods
11.2.56 PCD
11-842
Model Type
Source Object Type
Target Object Type
PCD
Person type
Module
PCD
Person type
Module
PCD PCD
can be used by development is under responsibility of is under technical responsibility of is in conflict with is accessed by
PCD
Person type
Module type
PCD PCD
is in conflict with accesses
Person type Relationship type
PCD PCD PCD PCD
is owner of accesses is owner of is responsible for development of
has owner is accessed by has owner development is under responsibility of is under technical responsibility of
Relationship type Technical term Technical term Application system Application system
PCD
Position
ARIS Methods
11.2.56 PCD
11-843
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
PCD
Position
PCD PCD
Position Position
PCD
Position
PCD
Position
accesses
PCD PCD PCD
PCD
Position
accesses
is accessed by
Class
ARIS Methods
11.2.56 PCD
11-844
Model Type
Source Object Type
Target Object Type
PCD PCD
Position Position
PCD PCD PCD PCD
PCD PCD
Position Position
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner has specimen owner is accessed by has owner is accessed by has owner
Component Component
PCD
Position
Component
Position Position Position Position Position Position Position
COT attribute COT attribute COT attribute Entity type Entity type ERM attribute ERM attribute
ARIS Methods
11.2.56 PCD
11-845
Model Type
Source Object Type
Target Object Type
Position Position Position Position Position Position
PCD PCD
Position Position
Function Function
PCD PCD
Position Position
Function Function
PCD PCD
Position Position
Function Function
PCD
Position
Function
ARIS Methods
11.2.56 PCD
11-846
Model Type
Source Object Type
Target Object Type
PCD
Position
uses
is used by
PCD PCD
Position Position
PCD
Position
IT function
PCD PCD
Position Position
PCD
Position
PCD
Position
is user
PCD PCD PCD
is available at is required by development is under responsibility of
ARIS Methods
11.2.56 PCD
11-847
Model Type
Source Object Type
Target Object Type
PCD
Position
Module
PCD PCD PCD
PCD
Position
Module type
Position Position Position Position Product/Service Product/Service
accesses is owner of accesses is owner of is compared to is consumed by
is accessed by has owner is accessed by has owner is compared to consumes
Relationship type Relationship type Technical term Technical term Event Function
PCD PCD PCD PCD
is input for is used by is managed by is managed by
has input of uses manages manages
Function Function Application system type Component
ARIS Methods
11.2.56 PCD
11-848
Model Type
Source Object Type
Target Object Type
PCD PCD PCD
Relationship type Relationship type Rule Rule Rule Screen Screen
is input for lies on leads to activates links can use can use
has input of has information about is dependent on is activated by is linked by can be used by can be used by
Function Information carrier Event Function Rule Class Cluster/Data model
Screen Screen Screen Screen Screen Screen Screen
can use can use can use can use creates can use can use
can be used by can be used by can be used by can be used by is created by can be used by can be used by
Complex object type COT attribute Entity type ERM attribute Event Relationship type Technical term
ARIS Methods
11.2.56 PCD
11-849
Model Type
Source Object Type
Target Object Type
PCD PCD
is assigned to can be assigned to has state is approved by is checked by is input for lies on
is assigned to can be assigned to is state of approves checks has input of has information about
Function Function
PCD PCD PCD PCD PCD
Event Function Function Function Information carrier
Assignment Relationship PCD
ARIS Methods
11.2.57 PCD (material flow)
11-850

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system Application system class Application system type uses supports is supported by is used by Attribute type group Function uses is used by uses supports is supported by is used by Relationship type Technical term Function uses is used by ERM attribute uses is used by Entity type uses is used by uses is used by uses is used by Cluster/Data model Complex object type COT attribute uses is used by uses is used by Attribute type group Class Target Object Type
ARIS Methods
11-851
Model Type
Source Object Type
Target Object Type
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
ARIS Methods
11-852
Model Type
Source Object Type
Target Object Type
Class Class Class
ARIS Methods
11-853
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-854
Model Type
Source Object Type
Target Object Type
Event Event Event
ARIS Methods
11-855
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-856
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Employee variable
Employee variable
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
contributes to
Function
Function Function
Function Function
Function
ARIS Methods
11-857
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Employee variable
Function
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
approves checks
Function Function
ARIS Methods
11-858
Model Type
Source Object Type
Target Object Type
is compared to provides value for is approved by is checked by
is compared to uses value of approves checks
has input of has information about has screen field is activated by is activated by uses
Event Event Event
ARIS Methods
11-859
Model Type
Source Object Type
Target Object Type
Event Event Event
activates defines status activates
is activated by is defined is activated by
IT function type Material type Module type
uses uses uses uses
Organizational unit Organizational unit type Person Person type
Event Event Event
is used by corresponds to is evaluated by
uses corresponds to evaluates
Position Product/Service Rule
activates archives changes
is activated by is archived by is changed by
Screen Attribute type group Attribute type group
ARIS Methods
11-860
Model Type
Source Object Type
Target Object Type
Attribute type group Attribute type group Attribute type group Attribute type group Attribute type group Authorization condition Business object
has output of reads has knowledge of has output of
is output of is read by is available at is output of
Business object Class Class
Class Class Class
ARIS Methods
11-861
Model Type
Source Object Type
Target Object Type
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Complex object type
ARIS Methods
11-862
Model Type
Source Object Type
Target Object Type
can support belongs to archives changes
can be supported by is assigned to is archived by is changed by
Component Cost category COT attribute COT attribute
COT attribute COT attribute Documented knowledge
ARIS Methods
11-863
Model Type
Source Object Type
Target Object Type
reads can create can use
is read by can be created by can be used by
Documented knowledge Draft list Draft list
ARIS Methods
11-864
Model Type
Source Object Type
Target Object Type
reads creates calls
is read by is created by is called by
ARIS Methods
11-865
Model Type
Source Object Type
Target Object Type
is predecessor of reads creates output to
follows is read by is output medium for is read by measures
Function General resource Information carrier Information carrier Key performance indicator instance
Function Function
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
List List Location
Function Function
creates supports
is created by is supported by
Material type Objective
ARIS Methods
11-866
Model Type
Source Object Type
Target Object Type
has output of reads requires
is output of is read by is required by
Package Package Packaging material type
has output of produces archives changes
is output of is produced by is archived by is changed by
Relationship type Relationship type Relationship type Relationship type Relationship type Rule
has output of reads leads to
is output of is read by is assigned to
ARIS Methods
11-867
Model Type
Source Object Type
Target Object Type
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
is represented by can use requires
represents can be used by is required by
Screen Screen design Technical operating supply
Function
Technical operating supply Technical operating supply type
Function
requires
Function
is required alternatively is archived by is changed by
Technical operating supply type Technical term Technical term
Function Function
archives changes
ARIS Methods
11-868
Model Type
Source Object Type
Target Object Type
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
has output of reads accesses
is output of is read by is accessed by
Technical term Technical term Transport system
Function
accesses alternatively
is accessed alternatively by is accessed by
Transport system Transport system type
Function
accesses
Function
accesses alternatively
is accessed alternatively by
requires requires alternatively requires
is required by is required alternatively is required by
Warehouse equipment Warehouse equipment Warehouse equipment type
Function
is required alternatively is compared to
Warehouse equipment type Event
General resource
is compared to
ARIS Methods
11-869
Model Type
Source Object Type
Target Object Type
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
General resource Group
is defined is responsible for development of
can be processed by/with development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of can be used by
Function Application system Application system Application system Application system class Application system class Application system class Application system type
Group
Group Group Group
Group
Group
can be user
Group
PCD (material flow)
Group
PCD (material flow)
Group
accesses
is accessed by
ARIS Methods
11-870
Model Type
Source Object Type
Target Object Type
Group Group Group
Group Group Group
Group Group Group
is specimen owner of can be user is responsible for development of
has specimen owner can be used by development is under responsibility of
ARIS Methods
11-871
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Group
Component
Group Group Group
Group Group Group
Group Group
accepts carries out
is accepted by is carried out by
Function Function
ARIS Methods
11-872
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Group
contributes to
Function
Group Group
Function Function
Group Group
Function Function
Group Group
Function Function
Group
Function
Group
uses
PCD (material flow) PCD (material flow)
Group Group
is provided by development is under responsibility of
ARIS Methods
11-873
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Group
IT function
PCD (material flow) PCD (material flow) PCD (material flow)
Group Group
Group
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
Group Group Group
Group
Module
PCD (material flow)
Group
Module
Group Group
is user can be user
is used by can be used by
Module Module type
ARIS Methods
11-874
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Group
Module type
PCD (material flow)
Group
Module type
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type
Attribute type group Class Cluster/Data model
ARIS Methods
11-875
Model Type
Source Object Type
Target Object Type
Hardware component type Hardware component type Hardware component type Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier IT function
ERM attribute Relationship type Technical term
has state provides input for is used by is used by
is state of gets input from uses uses
Event Function Group Organizational unit
Person type Position Attribute type group
uses uses uses
ARIS Methods
11-876
Model Type
Source Object Type
Target Object Type
uses uses uses
IT function IT function IT function IT function type
uses can use uses
ARIS Methods
11-877
Model Type
Source Object Type
Target Object Type
uses can use uses creates
is used by can be used by is used by is created by
relates to supports supports when time limit is exceeded
relates to (passive) is supported by supports when time limit is exceeded (passive) is supported by
Event Event Event
PCD (material flow)
IT function type
supports
Function
ARIS Methods
11-878
Model Type
Source Object Type
Target Object Type
PCD (material flow)
IT function type
supports when time limit is exceeded (passive) can be used by
Function
IT function type
can use
Relationship type
IT function type IT function type IT function type Key performance indicator instance Knowledge category Knowledge category List Location
uses can use uses is measured upon occurrence relates to
is used by can be used by is used by triggers measuring relates to (passive)
Relationship type Technical term Technical term Event
Event
Location Location
ARIS Methods
11-879
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-880
Model Type
Source Object Type
Target Object Type
Knowledge category Knowledge category Relationship type
Location Location Location Material type
is owner of accesses is owner of is consumed
has owner is accessed by has owner consumes
Relationship type Technical term Technical term Function
Material type Material type Module
is not consumed is partly consumed uses
does not consume partly consumes is used by
uses uses uses
ARIS Methods
11-881
Model Type
Source Object Type
Target Object Type
uses uses uses
Module Module Module Module type
ARIS Methods
11-882
Model Type
Source Object Type
Target Object Type
can use creates supports
can be used by is created by is supported by
Module type Module type Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource type Operating resource type
can use can use encompasses is alternative operating resource of is operating resource of encompasses encompasses can encompass
can be used by can be used by belongs to has alternative operating resource has operating resource belongs to belongs to can belong to
Function
is alternative operating resource of
has alternative operating resource
Function
ARIS Methods
11-883
Model Type
Source Object Type
Target Object Type
Operating resource type Operating resource type Operating resource type Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
is operating resource of can encompass can encompass
has operating resource can belong to can belong to
Function IT function type Module type
ARIS Methods
11-884
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Organizational unit
is owner of is specimen owner of provides
has owner has specimen owner is provided by
Complex object type Complex object type
ARIS Methods
11-885
Model Type
Source Object Type
Target Object Type
can be user is responsible for development of is technically responsible for accesses is owner of is specimen owner of accesses is owner of accesses
can be used by development is under responsibility of is under technical responsibility of is accessed by has owner has specimen owner is accessed by has owner is accessed by
Component Component
Component
ARIS Methods
11-886
Model Type
Source Object Type
Target Object Type
contributes to
Function
decides on
is decided by
Function
Function
is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of
Function Function
Function Function
Function
ARIS Methods
11-887
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Organizational unit
uses
is used by
provides is responsible for development of is technically responsible for
IT function
PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow) PCD (material flow)
is user is responsible for development of is technically responsible for is user has knowledge of requires is responsible for development of
is used by development is under responsibility of is under technical responsibility of is used by is available at
is required by development is under responsibility of
ARIS Methods
11-888
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Organizational unit
Module
Module type
Application system
ARIS Methods
11-889
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Application system
Application system type Application system type Application system type Attribute type group Attribute type group
Authorization condition Authorization condition
ARIS Methods
11-890
Model Type
Source Object Type
Target Object Type
is owner of accesses is owner of can be user
has owner is accessed by has owner can be used by
Component
PCD (material flow)
Component
ARIS Methods
11-891
Model Type
Source Object Type
Target Object Type
is owner of provides accepts carries out
has owner is provided by is accepted by is carried out by
contributes to
Function
Function Function
Function Function
ARIS Methods
11-892
Model Type
Source Object Type
Target Object Type
must be informed about must be informed on cancellation must inform about result of can be user is responsible for development of is technically responsible for can be user
result is forwarded to sends information on cancellation to result is forwarded by can be used by development is under responsibility of is under technical responsibility of can be used by
Function Function
IT function
IT function type
IT function type
PCD (material flow)
IT function type
ARIS Methods
11-893
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Package
can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for accesses is owner of
Module Module
Module
Module type
accesses is owner of contains
is accessed by has owner is contained by
ARIS Methods
11-894
Model Type
Source Object Type
Target Object Type
Package Person
is input for is responsible for development of
has input of development is under responsibility of is under technical responsibility of is used by can be used by development is under responsibility of is under technical responsibility of can be used by
Function Application system Application system Application system Application system class Application system class Application system class Application system type
Person
Person
Person
can be user
Person
PCD (material flow)
Person
PCD (material flow)
Person
accesses
is accessed by
ARIS Methods
11-895
Model Type
Source Object Type
Target Object Type
Person
Component
PCD (material flow)
Person
Component
ARIS Methods
11-896
Model Type
Source Object Type
Target Object Type
ARIS Methods
11-897
Model Type
Source Object Type
Target Object Type
Person Person
Function Function
Person Person
Function Function
Person Person
Function Function
Person
Function
Person
uses
PCD (material flow)
Person
IT function
PCD (material flow)
Person
IT function
PCD (material flow)
Person
is user
is used by
IT function
ARIS Methods
11-898
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Person
IT function type
PCD (material flow)
Person
IT function type
Person
Module
Person
is user
Module
Person Person
Person
Module type
ARIS Methods
11-899
Model Type
Source Object Type
Target Object Type
Person type
Person type
Person type
can be user
ARIS Methods
11-900
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Person type
PCD (material flow)
Person type
ARIS Methods
11-901
Model Type
Source Object Type
Target Object Type
Person type
Component
ARIS Methods
11-902
Model Type
Source Object Type
Target Object Type
Function Function
Person type
Function
Person type
Function
Function Function
ARIS Methods
11-903
Model Type
Source Object Type
Target Object Type
Person type
IT function
Person type
Module Module
Person type
Module
ARIS Methods
11-904
Model Type
Source Object Type
Target Object Type
Person type
Module type
Position
Position
is user
ARIS Methods
11-905
Model Type
Source Object Type
Target Object Type
Position Position
Position
Position Position
Position
Position Position
ARIS Methods
11-906
Model Type
Source Object Type
Target Object Type
provides accesses is owner of can be user
is provided by is accessed by has owner can be used by
Position
Component
PCD (material flow)
Position
Component
ARIS Methods
11-907
Model Type
Source Object Type
Target Object Type
Position
decides on
is decided by
Function
Position
Function
ARIS Methods
11-908
Model Type
Source Object Type
Target Object Type
Position Position
Function Function
Position Position
Function Function
Position Position
Position
provides
is provided by
Information carrier
Position
IT function
PCD (material flow)
Position
IT function
Position Position
ARIS Methods
11-909
Model Type
Source Object Type
Target Object Type
PCD (material flow)
Position
IT function type
Position
Module
Position
is user
Module
Position Position
Position
Module type
Position
accesses
Relationship type
ARIS Methods
11-910
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Product/Service
is compared to is consumed by is input for is used by
is compared to consumes has input of uses
Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type
ARIS Methods
11-911
Model Type
Source Object Type
Target Object Type
Relationship type Rule Rule
Rule Screen Screen Screen
links can use can use can use
is linked by can be used by can be used by can be used by
Rule Class Cluster/Data model Complex object type
ARIS Methods
11-912
Model Type
Source Object Type
Target Object Type
System organizational unit System organizational unit type Technical operating supply Technical operating supply Technical operating supply Technical operating supply type
is assigned to can be assigned to encompasses encompasses encompasses
is assigned to can be assigned to belongs to belongs to belongs to
Function Function
can encompass
can belong to
PCD (material flow)
can encompass
can belong to
IT function type
PCD (material flow)
can encompass
can belong to
Module type
ARIS Methods
11-913
Model Type
Source Object Type
Target Object Type
Technical term Technical term Transport system Transport system Transport system Transport system type Transport system type Transport system type Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment type Warehouse equipment type
is input for lies on encompasses
has input of has information about belongs to
Function Information carrier Application system
encompasses encompasses can encompass can encompass
belongs to belongs to can belong to can belong to
IT function Module Application system type IT function type
can encompass encompasses encompasses
can belong to belongs to belongs to
Module type Application system IT function
encompasses can encompass can encompass
belongs to can belong to can belong to
Module Application system type IT function type
ARIS Methods
11-914
Model Type
Source Object Type
Target Object Type
PCD (material flow)
can encompass
can belong to
Module type
Source Object Type
Target Object Type
PCD (material flow)
Function
Function
ARIS Methods
11.2.58 PPC
11-915
11.2.58 PPC
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) PPC PPC PPC Cluster instance Cluster instance Cluster instance PPC PPC PPC Event instance Event instance Function instance PPC PPC PPC PPC Function instance Function instance Function instance Function instance PPC PPC Function instance Function instance is predecessor of is successor of has output of distributes is distributed by is output of deletes is deleted by creates is created by changes is changed by is predecessor of is predecessor of archives is archived by Cluster instance Cluster instance Cluster instance Cluster instance Cluster instance Cluster instance Event instance is successor of is successor of is input for has input of is checked by checks is approved by approves Function instance Function instance Function instance Function instance Rule Target Object Type
ARIS Methods
11.2.59 Privileges diagram
11-916
Model Type
Source Object Type
Target Object Type
PPC PPC PPC
Function instance Function instance General resource
is predecessor of is predecessor of is defined
is successor of is successor of can be processed by/with
Function instance Rule Function instance Function instance Function instance Function instance Event instance Function instance Rule
PPC PPC PPC PPC PPC PPC
Operating resource Person Person type Rule Rule Rule
is defined is defined is defined activates activates links
can be processed by/with can be processed by/with can be processed by/with is activated by is activated by is linked by

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Privileges diagram Function is workflow class of is workflow class of (passive) Privileges diagram Group can be user can be used by Application system type Function Target Object Type
ARIS Methods
11-917
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Group Group Group
may carry out may not carry out may access
may be carried out by may not be carried out by can be accessed by
Application system type Application system type Cluster/Data model Complex object type COT attribute Entity type ERM attribute
may access may access may access may access
can be accessed by can be accessed by can be accessed by can be accessed by
Group
may change privileges
may change privileges (passive)
Function
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Group Group Group
may instantiate may search may carry out
can be instantiated by may search (passive) may be carried out by
Function Function IT function type IT function type Module type
Group Group
may not carry out may carry out
may not be carried out by may be carried out by
ARIS Methods
11-918
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Group Group Group
may not carry out may access may access
may not be carried out by can be accessed by can be accessed by
Module type Relationship type Technical term
IT function type Location Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
supports may instantiate can be user may carry out
is supported by can be instantiated by can be used by may be carried out by
Function Function Application system type Application system type Application system type Cluster/Data model Complex object type COT attribute Entity type ERM attribute
may not carry out may access may access
may not be carried out by can be accessed by can be accessed by
may access may access may access
can be accessed by can be accessed by can be accessed by
ARIS Methods
11-919
Model Type
Source Object Type
Target Object Type
Privileges diagram
Organizational unit
Function
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Person Person
may instantiate may search may carry out may not carry out may carry out may not carry out may access
can be instantiated by may search (passive) may be carried out by may not be carried out by may be carried out by may not be carried out by can be accessed by
Function Function IT function type IT function type Module type Module type Relationship type Technical term Application system type Application system type Application system type Cluster/Data model
may access can be user may carry out
can be accessed by can be used by may be carried out by
Person Person
may not carry out may access
may not be carried out by can be accessed by
ARIS Methods
11-920
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Person Person
may access is process manager for
can be accessed by is under process responsibility of
ERM attribute Function
Privileges diagram
Person
Function
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
may instantiate may search may carry out
can be instantiated by may search (passive) may be carried out by
Function Function IT function type IT function type Module type Module type
may not carry out may carry out may not carry out
may not be carried out by may be carried out by may not be carried out by
ARIS Methods
11-921
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Person Person Person type
may access may access can be user
can be accessed by can be accessed by can be used by
Relationship type Technical term Application system type
may carry out may not carry out may access may access
may be carried out by may not be carried out by can be accessed by can be accessed by
Application system type Application system type Cluster/Data model Complex object type COT attribute Entity type ERM attribute
Person type
Function
Privileges diagram Privileges diagram
may instantiate may search
can be instantiated by may search (passive)
Function Function
ARIS Methods
11-922
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
may carry out may not carry out may carry out
may be carried out by may not be carried out by may be carried out by
may not carry out may access may access can be user
may not be carried out by can be accessed by can be accessed by can be used by
Module type Relationship type Technical term Application system type
may be carried out by may not be carried out by can be accessed by
Application system type Application system type Cluster/Data model Complex object type COT attribute Entity type
ARIS Methods
11-923
Model Type
Source Object Type
Target Object Type
Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram Privileges diagram
Position Position
may access is process manager for
can be accessed by is under process responsibility of can be instantiated by may be carried out by may not be carried out by may be carried out by may not be carried out by can be accessed by
may instantiate may carry out may not carry out
Function IT function type IT function type Module type Module type Relationship type Technical term
Position
may access
can be accessed by
ARIS Methods
11.2.60 Process instantiation model
11-924
11.2.60 Process instantiation model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Process instantiation model Process instantiation model Process instantiation model Instantiation plan contains is contained in Instantiation cycle Instantiation cycle repeats is repeated by Instantiation interval Instantiation cycle is superior is subordinate Instantiation cycle Target Object Type
11.2.61 Process selection diagram

Model Type Source Object Type Process selection diagram Process selection diagram Process selection diagram Process selection diagram Process selection diagram Organizational unit is assigned to has assigned Function Main process is superior is subordinate Main process Function belongs to belongs to Main process Function is superior Function Relationship Type (active) consists of Relationship Type (passive) is component of is subordinate Function Function Target Object Type
ARIS Methods
11.2.62 Process selection matrix
11-925
11.2.62 Process selection matrix

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Process selection matrix Process selection matrix Organizational unit is assigned to Function consists of is component of has assigned Function Function Target Object Type
11.2.63 Product allocation diagram

Model Type Source Object Type Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Entity type is input for has input of Cluster/Data model Cluster/Data model Documented knowledge Entity type is basis for has basis is required for requires is input for has input of is basis for has basis Class is input for has input of Class Relationship Type (active) is basis for Relationship Type (passive) has basis Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Target Object Type
ARIS Methods
11-926
Model Type
Source Object Type
Target Object Type
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
Function Function Information carrier Information carrier Knowledge category Marketing instrument Person
has output of has output of is input for
is output of is output of has input of
Information carrier Product/Service Function
is input for is required for is used for provides
has input of requires uses is provided by
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
has output of has output of is offered via
is output of is output of offers
Class Cluster/Data model Distribution channel
has output of is input for is created with help from
is output of has input of helps with the creation of
Entity type Function Group
ARIS Methods
11-927
Model Type
Source Object Type
Target Object Type
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
is demanded by is received from is under financial responsibility of is under technical responsibility of is used by has output of
demands is a receiver of is financially responsible for is technically responsible for uses is output of
Group Group Group
Group
Group Information carrier
satisfies supports is created with help from is demanded by is received from is under financial responsibility of
is satisfied by is supported by helps with the creation of demands is a receiver of is financially responsible for
Need Objective Organizational unit Organizational unit Organizational unit Organizational unit
ARIS Methods
11-928
Model Type
Source Object Type
Target Object Type
Product/Service
Organizational unit
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
Product/Service Product/Service Product/Service Product/Service Product/Service
is used by is created with help from is demanded by is received from is under financial responsibility of
uses helps with the creation of demands is a receiver of
Organizational unit Organizational unit type Organizational unit type Organizational unit type
is financially responsible for
Product/Service
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
is used by has performance characteristic is created with help from is demanded by
uses is performance characteristic of helps with the creation of demands
Organizational unit type Performance characteristic Person Person
ARIS Methods
11-929
Model Type
Source Object Type
Target Object Type
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
is received from is under financial responsibility of is under technical responsibility of is used by is created with help from is demanded by is received from is under financial responsibility of is under technical responsibility of is used by is created with help from
is a receiver of is financially responsible for is technically responsible for uses helps with the creation of demands
Person Person
Person
is a receiver of is financially responsible for is technically responsible for uses helps with the creation of
Person type
ARIS Methods
11-930
Model Type
Source Object Type
Target Object Type
Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram Product allocation diagram
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Relationship type Relationship type Technical term Technical term Technical term
is demanded by is received from is under financial responsibility of is under technical responsibility of is used by has output of
demands is a receiver of is financially responsible for is technically responsible for uses is output of
Position
Position Relationship type
has output of is basis for is input for
is output of has basis has input of
Technical term Product/Service Product/Service
is basis for is input for is order basis for
has basis has input of has order basis
Product/Service Product/Service Product/Service
ARIS Methods
11.2.64 Product selection matrix
11-931
11.2.64 Product selection matrix

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Product selection matrix Product selection matrix Organizational unit is responsible for is under responsibility of Function has output of is output of Product/Service Product/Service Target Object Type
11.2.65 Product tree

Model Type Source Object Type Product tree Product tree Product/Service Product/Service Product tree Product/Service has relation with has relation with encompasses Relationship Type (active) consists of Relationship Type (passive) is component of belongs to Product/Service Product/Service Product/Service Target Object Type
11.2.66 Product/Service exchange diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Product/Service exchange diagram Application system type is is Product/Service Target Object Type
ARIS Methods
11-932
Model Type
Source Object Type
Target Object Type
Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram
Event
corresponds to
corresponds to
Product/Service
Function
has output of
is output of
Product/Service
Group
has output of
is output of
Product/Service
Group
provides
is provided by
Product/Service
Location
has output of
is output of
Product/Service
Location
provides
is provided by
Product/Service
Material type
is
is
Product/Service
ARIS Methods
11-933
Model Type
Source Object Type
Target Object Type
Operating resource type
is
is
Product/Service
Organizational unit
has output of
is output of
Product/Service
Organizational unit
provides
is provided by
Product/Service
has output of
is output of
Product/Service
provides
is provided by
Product/Service
Packaging material type
is
is
Product/Service
Person
has output of
is output of
Product/Service
ARIS Methods
11-934
Model Type
Source Object Type
Target Object Type
Person
provides
is provided by
Product/Service
Person type
has output of
is output of
Product/Service
Person type
provides
is provided by
Product/Service
Position
provides
is provided by
Product/Service
Product/Service
is input for
has input of
Function
Product/Service
is used by
uses
Function
Product/Service
is created with help from
helps with the creation of
Group
ARIS Methods
11-935
Model Type
Source Object Type
Target Object Type
Product/Service
is received from
is a receiver of
Group
Product/Service
is under financial responsibility of
Group
Product/Service
Group
Product/Service
is used by
uses
Group
Product/Service
provides input for
gets input from
Group
Product/Service
Location
Product/Service
is received from
is a receiver of
Location
ARIS Methods
11-936
Model Type
Source Object Type
Target Object Type
Product/Service
Location
Product/Service
Location
Product/Service
is used by
uses
Location
Product/Service
provides input for
gets input from
Location
Product/Service
Organizational unit
Product/Service
is received from
is a receiver of
Organizational unit
Product/Service
Organizational unit
ARIS Methods
11-937
Model Type
Source Object Type
Target Object Type
Product/Service
Organizational unit
Product/Service
is used by
uses
Organizational unit
Product/Service
provides input for
gets input from
Organizational unit
Product/Service
Product/Service
is received from
is a receiver of
Product/Service
Product/Service
ARIS Methods
11-938
Model Type
Source Object Type
Target Object Type
Product/Service
is used by
uses
Product/Service
provides input for
gets input from
Product/Service
Person
Product/Service
is received from
is a receiver of
Person
Product/Service
Person
Product/Service
Person
Product/Service
is used by
uses
Person
ARIS Methods
11-939
Model Type
Source Object Type
Target Object Type
Product/Service
provides input for
gets input from
Person
Product/Service
Person type
Product/Service
is received from
is a receiver of
Person type
Product/Service
Person type
Product/Service
Person type
Product/Service
is used by
uses
Person type
Product/Service
provides input for
gets input from
Person type
ARIS Methods
11-940
Model Type
Source Object Type
Target Object Type
Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram Product/Service exchange diagram
Product/Service
Position
Product/Service
is received from
is a receiver of
Position
Product/Service
Position
Product/Service
Position
Product/Service
is used by
uses
Position
is
is
Product/Service
ARIS Methods
11.2.67 Product/Service exchange diagram (graphic)
11-941
Source Object Type
Target Object Type
Product/Service exchange diagram
Product/Service
encompasses
belongs to
Product/Service

Model Type Source Object Type Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Group has output of is output of Product/Service Function has output of is output of Product/Service Event corresponds to corresponds to Product/Service Application system type Relationship Type (active) is Relationship Type (passive) is Product/Service Target Object Type
ARIS Methods
11-942
Model Type
Source Object Type
Target Object Type
Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic)
Group
provides
is provided by
Product/Service
Location
has output of
is output of
Product/Service
Location
provides
is provided by
Product/Service
Material type
is
is
Product/Service
is
is
Product/Service
Organizational unit
has output of
is output of
Product/Service
Organizational unit
provides
is provided by
Product/Service
ARIS Methods
11-943
Model Type
Source Object Type
Target Object Type
has output of
is output of
Product/Service
provides
is provided by
Product/Service
Packaging material type
is
is
Product/Service
Person
has output of
is output of
Product/Service
Person
provides
is provided by
Product/Service
Person type
has output of
is output of
Product/Service
Person type
provides
is provided by
Product/Service
ARIS Methods
11-944
Model Type
Source Object Type
Target Object Type
Position
provides
is provided by
Product/Service
Product/Service
is input for
has input of
Function
Product/Service
is used by
uses
Function
Product/Service
Group
Product/Service
is received from
is a receiver of
Group
Product/Service
Group
Product/Service
Group
ARIS Methods
11-945
Model Type
Source Object Type
Target Object Type
Product/Service
is used by
uses
Group
Product/Service
provides input for
gets input from
Group
Product/Service
Location
Product/Service
is received from
is a receiver of
Location
Product/Service
Location
Product/Service
Location
Product/Service
is used by
uses
Location
ARIS Methods
11-946
Model Type
Source Object Type
Target Object Type
Product/Service
provides input for
gets input from
Location
Product/Service
Organizational unit
Product/Service
is received from
is a receiver of
Organizational unit
Product/Service
Organizational unit
Product/Service
Organizational unit
Product/Service
is used by
uses
Organizational unit
Product/Service
provides input for
gets input from
Organizational unit
ARIS Methods
11-947
Model Type
Source Object Type
Target Object Type
Product/Service
Product/Service
is received from
is a receiver of
Product/Service
Product/Service
Product/Service
is used by
uses
Product/Service
provides input for
gets input from
Product/Service
Person
ARIS Methods
11-948
Model Type
Source Object Type
Target Object Type
Product/Service
is received from
is a receiver of
Person
Product/Service
Person
Product/Service
Person
Product/Service
is used by
uses
Person
Product/Service
provides input for
gets input from
Person
Product/Service
Person type
Product/Service
is received from
is a receiver of
Person type
ARIS Methods
11-949
Model Type
Source Object Type
Target Object Type
Product/Service
Person type
Product/Service
Person type
Product/Service
is used by
uses
Person type
Product/Service
provides input for
gets input from
Person type
Product/Service
Position
Product/Service
is received from
is a receiver of
Position
Product/Service
Position
ARIS Methods
11-950
Model Type
Source Object Type
Target Object Type
Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic) Product/Service exchange diagram (graphic)
Product/Service
Position
Product/Service
is used by
uses
Position
is
is
Product/Service
Assignment Relationship Product/Service exchange diagram (graphic)
Source Object Type Product/Service
Relationship Type (active) encompasses
Relationship Type (passive) belongs to
Target Object Type Product/Service
ARIS Methods
11.2.68 Product/Service tree
11-951
11.2.68 Product/Service tree

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Product/Service tree Product/Service tree Product/Service tree Product/Service tree Product/Service tree Product/Service tree Product/Service tree Product/Service has relation with has relation with Product/Service Product/Service encompasses belongs to Product/Service Product/Service consists of is component of Product/Service Product/Service can replace can be replaced by Product/Service Product/Service supports is supported by Objective Product/Service is input for has input of Function Function has output of is output of Product/Service Target Object Type
ARIS Methods
11.2.69 Product/Service tree (graphic)
11-952
11.2.69 Product/Service tree (graphic)

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service tree (graphic) Product/Service has relation with has relation with Product/Service Product/Service encompasses belongs to Product/Service Product/Service consists of is component of Product/Service Product/Service can replace can be replaced by Product/Service Product/Service supports is supported by Objective Product/Service is input for has input of Function Function has output of is output of Product/Service Target Object Type
ARIS Methods
11.2.70 Program flow-chart (PF)
11-953
11.2.70 Program flow-chart (PF)

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Program flowchart (PF) Rule occurs before occurs after Loop start Rule occurs before occurs after Function Rule occurs before occurs after Event Loop start occurs before occurs after Rule Loop start occurs before occurs after Function Function occurs before occurs after Rule Function occurs before occurs after Loop start Function occurs before occurs after Function Function occurs before occurs after Event Event occurs before occurs after Rule Event occurs before occurs after Loop start Event occurs before occurs after Function Target Object Type
ARIS Methods
11.2.71 Program structure chart
11-954
Model Type
Source Object Type
Target Object Type
Program flowchart (PF)
Rule
occurs before
occurs after
Rule

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system class Application system class has output of is output of has output of is output of Relationship type Technical term can be located at has output of can be location of is output of Relation Location has output of is output of ERM attribute has output of is output of has output of is output of Cluster/Data model Entity type has output of is output of Class has output of is output of Attribute Target Object Type
ARIS Methods
11-955
Model Type
Source Object Type
Target Object Type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Application system class Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type
has output of is predecessor of has output of
is output of follows is output of
View Application system type Attribute
uses has output of realizes uses
is used by is output of is realized by is used by
Attribute type group Class Class Class
ARIS Methods
11-956
Model Type
Source Object Type
Target Object Type
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type
creates has output of supports
is created by is output of is supported by
Event Field Function
can run on
can be platform for
Hardware component type Information carrier Information flow IT function type List
creates output to sends is predecessor of creates
is output medium for is sent from follows is created by
can be located at is predecessor of has output of
can be location of follows is output of
Location Module type Relation
has output of uses
is output of is used by
ARIS Methods
11-957
Model Type
Source Object Type
Target Object Type
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Attribute Attribute Attribute
leads to encompasses has output of
is assigned to belongs to is output of
Rule Screen Table
has output of uses has output of has output of
is output of is used by is output of is output of
Technical term Technical term View View (physical)
is input for is input for has state
has input of has input of is state of
Application system class Application system type Event
IT function class IT function type Module class
ARIS Methods
11-958
Model Type
Source Object Type
Target Object Type
is input for is under responsibility of is under responsibility of
has input of is responsible for is responsible for is responsible for has information about has input of has input of
Module type Organizational unit Person
Attribute Attribute type group Class Class
is under responsibility of lies on is input for is input for
Position Information carrier Application system class Application system type
Class Class Class
uses has output of has output of
is used is output of is output of
Application system type Cluster/Data model Entity type
Class Class Class
has output of has state creates output to
is output of is state of is output medium for
ERM attribute Event Information carrier
ARIS Methods
11-959
Model Type
Source Object Type
Target Object Type
Class Class Class
uses is input for is input for uses
is used has input of has input of is used
IT function type Module class Module type Module type
Class Class Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
has output of has output of is input for
is output of is output of has input of
Relationship type Technical term Application system class
Application system type Class Event
ARIS Methods
11-960
Model Type
Source Object Type
Target Object Type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model DBMS type DBMS type
is input for is input for can be platform of uses
has input of has input of can run under is used by
Module class Module type Application system type Cluster/Data model
DBMS type
can run on
can be platform for
Program structure chart Program structure chart Program structure chart Program structure chart
DBMS type DBMS type Employee variable Employee variable
can run under can run under can be used by
IT function type Module type Class
Class
ARIS Methods
11-961
Model Type
Source Object Type
Target Object Type
Employee variable
Class
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Employee variable Employee variable Entity type Entity type
may carry out may not carry out is input for is input for
may be carried out by may not be carried out by has input of has input of
Class Class Application system class Application system type
is input for has state lies on
has input of is state of has information about
Class Event Information carrier IT function class IT function type Module class
Entity type ERM attribute
Module type Application system class
ARIS Methods
11-962
Model Type
Source Object Type
Target Object Type
lies on is input for is input for is input for
has information about has input of has input of has input of
Information carrier IT function class IT function type Module class
is input for activates activates
has input of is activated by is activated by
Module type Application system type IT function type
Event Event Event
activates is evaluated by must not occur for
is activated by evaluates has condition (false)
Module type Rule Rule
ARIS Methods
11-963
Model Type
Source Object Type
Target Object Type
Event Field Field
must occur for is input for has state
has condition (true) has input of is state of
Rule Application system type Event
Field Field Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type Group Group
is input for is input for can be platform of can run on
has input of has input of can run under can be platform for
IT function type Module type Application system type Hardware component type IT function type
can be platform of can be platform of accesses is owner of
can run under
can run under is accessed by has owner
Module type Attribute type group Attribute type group
Group Group
accesses can be user
is accessed by can be used by
Class Class
ARIS Methods
11-964
Model Type
Source Object Type
Target Object Type
Group Group
has owner development is under responsibility of is under technical responsibility of may be carried out by may not be carried out by is accessed by
Class Class
Group
Class
Group Group Group
Group Group Group
Cluster/Data model Entity type Entity type
Group Group Group
ERM attribute Relationship type Relationship type
ARIS Methods
11-965
Model Type
Source Object Type
Target Object Type
Group Hardware component Hardware component Hardware component Hardware component Hardware component type Information carrier Information carrier Information carrier Information carrier Information carrier Information flow Information flow
accesses can be platform of is platform of
is accessed by can run under runs under
Technical term Application system type Class
can be platform of can be platform of is platform of
can run under can run under runs under
IT function type Module type Class
provides input for provides input for has state provides input for provides input for is received from is received from
gets input from gets input from is state of gets input from gets input from receives receives
Application system type Class
Event IT function type Module type
Application system type IT function type
ARIS Methods
11-966
Model Type
Source Object Type
Target Object Type
Information flow IT function IT function
is received from uses uses
receives is used by is used by
Module type Cluster/Data model Entity type
IT function IT function IT function IT function class IT function class IT function class IT function class IT function class IT function class IT function class
uses uses uses has output of
is used by is used by is used by is output of
ERM attribute Relationship type Technical term Attribute
Class Cluster/Data model Entity type
has output of can be located at has output of
is output of can be location of is output of
ERM attribute Location Relation
ARIS Methods
11-967
Model Type
Source Object Type
Target Object Type
IT function class IT function class IT function class IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
is predecessor of has output of uses has output of
follows is output of is used by is output of
Application system type Attribute Attribute type group Class
realizes uses has output of
is realized by is used by is output of
ARIS Methods
11-968
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
has output of uses creates
is output of is used by is created by
is predecessor of creates can be located at is predecessor of has output of
follows is created by can be location of follows is output of
IT function type List Location
Module type Relation
ARIS Methods
11-969
Model Type
Source Object Type
Target Object Type
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type Location
has output of uses leads to
is output of is used by is assigned to
Relationship type Relationship type Rule
encompasses has output of has output of uses
belongs to is output of is output of is used by
Screen Table Technical term Technical term
has output of has output of accesses
is output of is output of is accessed by
View View (physical) Attribute type group
is owner of accesses can be user
has owner is accessed by can be used by
ARIS Methods
11-970
Model Type
Source Object Type
Target Object Type
Location Location
has owner development is under responsibility of is under technical responsibility of may be carried out by may not be carried out by is accessed by
Class Class
Location
Class
accesses is user can be user
is accessed by has user can be used by
ERM attribute Operating system Operating system type
ARIS Methods
11-971
Model Type
Source Object Type
Target Object Type
Module class Module class Module class Module class
has output of has output of has output of has output of
is output of is output of is output of is output of
Attribute Class Cluster/Data model Entity type
has output of can be located at has output of
is output of can be location of is output of
ERM attribute Location Relation
ARIS Methods
11-972
Model Type
Source Object Type
Target Object Type
is predecessor of has output of uses
follows is output of is used by
Application system type Attribute Attribute type group
has output of realizes uses has output of
is output of is realized by is used by is output of
Class Class Class Cluster/Data model
has output of uses creates
is output of is used by is created by
ARIS Methods
11-973
Model Type
Source Object Type
Target Object Type
is predecessor of creates can be located at
follows is created by can be location of follows is output of is output of
IT function type List Location
is predecessor of has output of has output of
Module type Relation Relationship type
uses leads to
is used by is assigned to
Relationship type Rule
ARIS Methods
11-974
Model Type
Source Object Type
Target Object Type
Module type Module type Module type Operating system Operating system type Operating system type Operating system type Operating system type Organizational unit
uses has output of has output of runs with
is used by is output of is output of is platform for
Technical term View View (physical) Hardware component
can be platform of can run on
can run under can be platform for
Application system type Hardware component type IT function type Module type
can run under can run under
can be used by
ARIS Methods
11-975
Model Type
Source Object Type
Target Object Type
Organizational unit
Organizational unit
Program structure chart Program structure chart
Organizational unit
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Class Class Class
ARIS Methods
11-976
Model Type
Source Object Type
Target Object Type
Organizational unit
Class
Organizational unit
Class
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
DBMS type DBMS type
DBMS type
ARIS Methods
11-977
Model Type
Source Object Type
Target Object Type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
accesses can be user is responsible for development of is technically responsible for can be user is responsible for development of is technically responsible for can be user
is accessed by can be used by development is under responsibility of is under technical responsibility of can be used by development is under responsibility of is under technical responsibility of can be used by
ERM attribute IT function class IT function class IT function class IT function type IT function type IT function type Module class
Module class
Organizational unit
Module class
Organizational unit
can be user
can be used by
Module type
ARIS Methods
11-978
Model Type
Source Object Type
Target Object Type
Organizational unit
Module type
Organizational unit
Module type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
is user can be user uses accesses
has user can be used by is used by is accessed by
Operating system Operating system type Programming language Relation
View Application system type Application system type
ARIS Methods
11-979
Model Type
Source Object Type
Target Object Type
accesses can be responsible for accesses is owner of accesses
is accessed by can be under responsibility of is accessed by has owner is accessed by
Attribute Attribute
Attribute type group Attribute type group Class
can be user is owner of is responsible for development of is technically responsible for may carry out
can be used by has owner development is under responsibility of is under technical responsibility of may be carried out by
Class Class Class
Class
Class
ARIS Methods
11-980
Model Type
Source Object Type
Target Object Type
accesses is owner of can be user is responsible for development of is technically responsible for can be user
is accessed by has owner can be used by development is under responsibility of is under technical responsibility of can be used by
Entity type Entity type IT function type IT function type IT function type Module type
Module type
Module type
ARIS Methods
11-981
Model Type
Source Object Type
Target Object Type
Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Person
is user can be user accesses
has user can be used by is accessed by
Operating system Operating system type Relation
can be responsible for accesses
Relation
Relationship type
is owner of accesses can be responsible for can be user
has owner is accessed by can be under responsibility of can be used by
Relationship type View View
Person
Person
ARIS Methods
11-982
Model Type
Source Object Type
Target Object Type
Person Person
can be used by development is under responsibility of is under technical responsibility of is accessed by is accessed by has owner
Application system type Application system type Application system type Attribute Attribute type group Attribute type group
Person
Class Class Class
Person
Class
Person
Class
ARIS Methods
11-983
Model Type
Source Object Type
Target Object Type
Person
DBMS type
Person Person
ERM attribute IT function class IT function class
ARIS Methods
11-984
Model Type
Source Object Type
Target Object Type
Person
IT function class
Program structure chart Program structure chart Program structure chart
Person Person
Person
Person Person
Person
Module class
Person Person
Person
Module type
ARIS Methods
11-985
Model Type
Source Object Type
Target Object Type
is user can be user uses
has user can be used by is used by
Operating system Operating system type Programming language
accesses accesses is owner of accesses
is accessed by is accessed by has owner is accessed by
Relation Relationship type Relationship type Technical term
is accessed by can be used by development is under responsibility of is under technical responsibility of is accessed by
View Application system type Application system type Application system type Attribute
Person type
Person type
accesses
ARIS Methods
11-986
Model Type
Source Object Type
Target Object Type
Person type
Attribute
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
has owner development is under responsibility of is under technical responsibility of may be carried out by may not be carried out by is accessed by has owner
Class Class
Person type
Class
may carry out may not carry out
Class Class
ARIS Methods
11-987
Model Type
Source Object Type
Target Object Type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Person type
Person type
Person type
can be user
Person type
Module type
Person type
Module type
is user can be user accesses
has user can be used by is accessed by
Operating system Operating system type Relation
ARIS Methods
11-988
Model Type
Source Object Type
Target Object Type
Person type
Relation
accesses is owner of accesses can be responsible for
is accessed by has owner is accessed by can be under responsibility of can be used by
Relationship type Relationship type View View
Position
can be user
Position
Position
Position Position
Position
ARIS Methods
11-989
Model Type
Source Object Type
Target Object Type
accesses can be user is owner of is responsible for development of
is accessed by can be used by has owner development is under responsibility of is under technical responsibility of may be carried out by
Position
Class
Position
may carry out
Class
ARIS Methods
11-990
Model Type
Source Object Type
Target Object Type
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Position Position
DBMS type DBMS type
Position
DBMS type
Position Position
IT function class IT function class IT function class IT function type IT function type
Position
Position Position
ARIS Methods
11-991
Model Type
Source Object Type
Target Object Type
Position
IT function type
Position Position
Position
Module class
Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart Program structure chart
Position Position
can be used by development is under responsibility of is under technical responsibility of has user can be used by
Position
Module type
Position Position
is user can be user
Operating system Operating system type
Position Position
accesses accesses
Relation Relationship type
ARIS Methods
11-992
Model Type
Source Object Type
Target Object Type
is owner of accesses accesses
has owner is accessed by is accessed by
Programming language Programming language Programming language Relation
is programming language of is programming language of is programming language of is input for
is developed with is developed with is developed with has input of
Application system type IT function type Module type
is input for has state is input for
has input of is state of has input of
Application system type Event IT function class
Relation Relation
IT function type Module class
ARIS Methods
11-993
Model Type
Source Object Type
Target Object Type
is input for is under responsibility of is under responsibility of
has input of is responsible for is responsible for is responsible for has input of has input of has input of
Module type Organizational unit Person
Relation Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type
is under responsibility of is input for is input for is input for
Position Application system class Application system type Class
has state lies on is input for
is state of has information about has input of
Event Information carrier IT function class
IT function type Module class Module type
ARIS Methods
11-994
Model Type
Source Object Type
Target Object Type
Rule Rule Rule
activates leads to activates
is activated by is dependent on is activated by
Application system type Event IT function type
Rule Rule Table Table
activates links is input for has state
is activated by is linked by has input of is state of
Module type Rule Application system type Event
Table Table Technical term
ARIS Methods
11-995
Model Type
Source Object Type
Target Object Type
Technical term Technical term View View
is input for is input for is input for is input for
has input of has input of has input of has input of
Module class Module type Application system class Application system type
View View View
has state is input for is input for
is state of has input of has input of
Event IT function class IT function type
View View View
has input of has input of is responsible for
Module class Module type Organizational unit
ARIS Methods
11.2.72 Quick model
11-996
Model Type
Source Object Type
Target Object Type
View View View (physical)
is under responsibility of is under responsibility of is input for
is responsible for is responsible for has input of
Person Position Application system type
View (physical) View (physical) View (physical)
has state is input for is input for
is state of has input of has input of
Event IT function type Module type
11.2.72 Quick model

Model Type Source Object Type Quick model Quick object Relationship Type (active) has relation with Relationship Type (passive) has relation with Quick object Target Object Type
ARIS Methods
11.2.73 RAD
11-997
11.2.73 RAD
Model Type Source Object Type Relationship Type (active) Relationship Type (passive) RAD Person type can be user can be used by Screen Target Object Type
11.2.74 RAMS
Model Type Source Object Type RAMS RAMS RAMS RAMS RAMS RAMS RAMS Entity type Entity type Function Function Main process Organizational unit Organizational unit is assigned to has assigned Function Relationship Type (active) is input for is input for has output of consists of has output of accesses Relationship Type (passive) has input of has input of is output of is component of is output of is accessed by Entity type Entity type Function Main process Entity type Function Target Object Type
ARIS Methods
11.2.75 Relations diagram
11-998
11.2.75 Relations diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relations diagram Relation Relation Relation Relation is describing for is foreign key for is primary key for depicts has foreign key has primary key is depicted by Relationship type Relation Relation is described by Relation Relation depicts is depicted by Entity type Domain depicts is depicted by Attribute Attribute Attribute Attribute is describing for is foreign key for is primary key for depicts has foreign key has primary key is depicted by Relationship type ERM domain Relation Relation is described by Relation Attribute depicts is depicted by ERM attribute Attribute has is assigned to Domain Target Object Type
ARIS Methods
11.2.76 Role diagram
11-999
Model Type
Source Object Type
Target Object Type
Relations diagram Relations diagram Relations diagram
View View View
depicts belongs to belongs to
is depicted by has encompasses
Cluster/Data model Relation View

Model Type Source Object Type Role diagram Authorization condition Role diagram Role diagram Role diagram Role diagram Authorization condition Function Function Function has knowledge of has knowledge of is carried out at Role diagram Role diagram Group Group has knowledge of requires is required by is available at Authorization condition Authorization condition is performed in is available at is available at Authorization condition Knowledge category Location relates to has Technical term Relationship Type (active) is required for Relationship Type (passive) requires Function Target Object Type
ARIS Methods
11-1000
Model Type
Source Object Type
Target Object Type
Role diagram Role diagram
Group Group
Function Function
Group Group
Function Function
Role diagram
Group
Function
Role diagram
Group
Function
Group Group
result is forwarded to sends information on cancellation to result is forwarded by is available at
Function Function
Group Group
must inform about result of has knowledge of
Function Knowledge category
Group Knowledge category
requires is required for
is required by requires
Knowledge category Function
ARIS Methods
11-1001
Model Type
Source Object Type
Target Object Type
Role diagram Role diagram Role diagram
has knowledge of requires has knowledge of
is available at is required by is available at
Authorization condition Authorization condition Knowledge category
Role diagram Role diagram Role diagram Role diagram
Location Organizational unit Organizational unit Organizational unit
requires has knowledge of requires accepts
is required by is available at is required by is accepted by
Knowledge category Authorization condition Authorization condition Function
Function Function
decides on has consulting role in is IT responsible for
Function Function
Role diagram
Organizational unit
Function
ARIS Methods
11-1002
Model Type
Source Object Type
Target Object Type
Role diagram
Organizational unit
Function
must be informed about must be informed on cancellation must inform about result of has knowledge of requires
result is forwarded to sends information on cancellation to result is forwarded by is available at is required by
Function Function
Function Knowledge category Knowledge category
has knowledge of requires carries out
is available at is required by is carried out by
Authorization condition Authorization condition Function
Role diagram
Function
Role diagram
Function
ARIS Methods
11-1003
Model Type
Source Object Type
Target Object Type
Role diagram
Function
Organizational unit type Organizational unit type Person Person
has knowledge of requires has knowledge of requires
is available at is required by is available at is required by
Knowledge category Knowledge category Authorization condition Authorization condition
Person Person
Function Function
Person Person
Function Function
Person Person
Function Function
Role diagram
Person
Function
ARIS Methods
11-1004
Model Type
Source Object Type
Target Object Type
Role diagram
Person
sends information on cancellation to result is forwarded by is available at is required by is available at
Function
Person Person Person Person type
must inform about result of has knowledge of requires has knowledge of
Function Knowledge category Knowledge category Authorization condition
requires carries out contributes to
is required by is carried out by is worked on by collaboration of
Authorization condition Function Function
Function Function
Function Function
ARIS Methods
11-1005
Model Type
Source Object Type
Target Object Type
result is forwarded to sends information on cancellation to result is forwarded by is available at is required by
Function Function
must inform about result of has knowledge of requires
Function Knowledge category Knowledge category
is in conflict with has knowledge of requires
is in conflict with is available at is required by
Person type Authorization condition Authorization condition
Position Position
Function Function
Position Position
Function Function
ARIS Methods
11.2.77 Rule diagram
11-1006
Model Type
Source Object Type
Target Object Type
Position Position
is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is available at
Function Function
Position Position
Function Function
Position Position
must inform about result of has knowledge of
Function Knowledge category
Role diagram
Position
requires
is required by
Knowledge category
11.2.77 Rule diagram

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Rule diagram Rule diagram Rule diagram Event Event Event activates is evaluated by must not occur for is activated by evaluates has condition (false) Function Rule Rule Target Object Type
ARIS Methods
11.2.78 SAP ALE filter model
11-1007
Model Type
Source Object Type
Target Object Type
Rule diagram Rule diagram Rule diagram Rule diagram
Event Function Function Rule
must occur for creates leads to leads to
has condition (true) is created by is assigned to is dependent on
Rule Event Rule Event
Rule diagram Rule diagram Rule diagram
Rule Rule Rule
activates has subordinate rule links
is activated by is subordinate rule of is linked by
Function Rule Rule
11.2.78 SAP ALE filter model

Model Type Source Object Type SAP ALE filter model Filter object type Relationship Type (active) is filter of Relationship Type (passive) is filtered by Function Target Object Type
11.2.79 SAP ALE function model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) SAP ALE function model Function is processoriented superior is processoriented subordinate Function Target Object Type
ARIS Methods
11.2.80 SAP ALE message flow model
11-1008
11.2.80 SAP ALE message flow model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) SAP ALE message flow model SAP ALE message flow model Message flow is received from receives Function Function sends is sent from Message flow Target Object Type
11.2.81 SAP SERM

Model Type Source Object Type SAP SERM Business object SAP SERM SAP SERM SAP SERM Entity type Entity type Entity type Relationship Type (active) has relation with defines (aggregating) defines (hierarchical) forms an incoming reference with SAP SERM SAP SERM Entity type Entity type has mandatory field is subtype of is mandatory field has as subtype Generalization type ERM attribute is depending hierarchically has reference to Entity type Entity type Relationship Type (passive) has relation with is aggregating Business object Entity type Target Object Type
ARIS Methods
11.2.81 SAP SERM
11-1009
Model Type
Source Object Type
Target Object Type
SAP SERM
Entity type
is supertype of
has as supertype
Generalization type
Source Object Type
Target Object Type
SAP SERM SAP SERM SAP SERM SAP SERM
consists of consists of consists of consists of
is part of is part of is part of is part of
Cluster/Data model Entity type ERM attribute Generalization type
SAP SERM SAP SERM SAP SERM
lies on lies on lies on
has information about has information about has information about
ARIS Methods
11.2.82 Screen design
11-1010
Source Object Type
Target Object Type

Model Type Source Object Type Screen design Bitmap Relationship Type (active) represents Relationship Type (passive) is represented in Screen design Screen design Screen design Screen design Bitmap Bitmap Button Button represents represents represents represents is represented in is represented in is represented in is represented in Screen design Screen design Button Combo box represents represents is represented in is represented in Attribute type group IT function type Parameter Function IT function type Parameter Function Target Object Type
ARIS Methods
11-1011
Model Type
Source Object Type
Target Object Type
Combo box Combo box Combo box
represents represents represents
is represented in is represented in is represented in
Business object Class Cluster/Data model COT attribute Element type Entity type ERM attribute
Screen design Screen design Screen design Screen design
Combo box Combo box Combo box Combo box
represents represents represents represents
is represented in is represented in is represented in is represented in
Function IT function type Package
Parameter Relationship type Technical term
ARIS Methods
11-1012
Model Type
Source Object Type
Target Object Type
List control List control List control
Attribute type group Business object Class
List control List control List control List control
Cluster/Data model COT attribute Element type Entity type
ERM attribute Function IT function type Package Parameter Relationship type
ARIS Methods
11-1013
Model Type
Source Object Type
Target Object Type
List control Radio button/Check box Radio button/Check box
Technical term Attribute type group Business object Class Cluster/Data model COT attribute Element type
Radio button/Check box Radio button/Check box Radio button/Check box Radio button/Check box
Radio button/Check box Radio button/Check box Radio button/Check box
Radio button/Check box Radio button/Check box Radio button/Check box
IT function type Package Parameter
ARIS Methods
11-1014
Model Type
Source Object Type
Target Object Type
Radio button/Check box Radio button/Check box Spin box
Relationship type Technical term Attribute type group Business object Class Cluster/Data model COT attribute
Spin box Spin box Spin box Spin box
Spin box Spin box Spin box
Element type Entity type ERM attribute
Function IT function type Package
ARIS Methods
11-1015
Model Type
Source Object Type
Target Object Type
Parameter Relationship type Technical term
Text box Text box Text box Text box
Attribute type group Business object Class Cluster/Data model COT attribute Element type Entity type
Text box Text box Text box
ERM attribute Function IT function type
ARIS Methods
11-1016
Model Type
Source Object Type
Target Object Type
Package Parameter Relationship type Technical term Attribute type group Business object Class
Text box Tree control Tree control Tree control
Tree control Tree control Tree control
Cluster/Data model COT attribute Element type
ARIS Methods
11.2.83 Screen diagram
11-1017
Model Type
Source Object Type
Target Object Type
IT function type Package Parameter
Screen design Screen design
Tree control Tree control
represents represents
is represented in is represented in
Relationship type Technical term

Model Type Source Object Type Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Column represents Column represents Column represents is represented in is represented in is represented in Parameter ERM attribute COT attribute Column is oriented at Column Relationship Type (active) represents Relationship Type (passive) is represented in is oriented at Column Bitmap Target Object Type
ARIS Methods
11-1018
Model Type
Source Object Type
Target Object Type
Column Column Column
is divided into is divided into represents
divides divides is represented in
Screen table Section Separator
Column Complex object type Entity type IT function type Layout Layout Layout
represents is represented in is represented in is represented in designs designs designs
is represented in represents represents represents
Text Screen Screen Screen
is designed by is designed by is designed by
Bitmap Column COT attribute
Layout Layout Layout
designs designs designs
ERM attribute Page Parameter
ARIS Methods
11-1019
Model Type
Source Object Type
Target Object Type
Layout Layout Layout
designs designs designs
Screen Screen table Section
Layout Page Page Page
designs represents is divided into represents
is designed by is represented in divides is represented in
Text Bitmap Column COT attribute
Page Page Page
represents represents is divided into
is represented in is represented in divides
ERM attribute Parameter Screen table
Page Page Page
is divided into represents represents
divides is represented in is represented in
Section Separator Text
ARIS Methods
11-1020
Model Type
Source Object Type
Target Object Type
represents is divided into represents
is represented in divides is represented in
Bitmap Column COT attribute
represents is divided into represents is divided into
is represented in divides is represented in divides
ERM attribute Page Parameter Screen table
is divided into represents represents
divides is represented in is represented in
Section Separator Text
Screen table Screen table Screen table
is divided into represents is divided into
divides is represented in divides
Column COT attribute Page
ARIS Methods
11-1021
Model Type
Source Object Type
Target Object Type
Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram Screen diagram
Screen table Screen table Section
represents is divided into represents
is represented in divides is represented in
Parameter Section Bitmap
Section Section Section Section
is divided into represents represents represents
divides is represented in is represented in is represented in
Column COT attribute ERM attribute Parameter
Section Section Section
is divided into is oriented at represents
divides is oriented at is represented in
Screen table Section Separator
Section
represents
is represented in
Text
ARIS Methods
11.2.84 Screen navigation
11-1022
Source Object Type
Target Object Type
Screen diagram
Entity type
is represented in
represents
Screen

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation List control leads to is assigned to Rule Event activates is activated by Screen Event leads to is assigned to Rule Combo box calls is called by Screen Combo box leads to is assigned to Rule Button calls is called by Screen Button leads to is assigned to Rule Bitmap calls is called by Screen Bitmap leads to is assigned to Rule Target Object Type
ARIS Methods
11-1023
Model Type
Source Object Type
Target Object Type
Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation
List control Radio button/Check box Radio button/Check box Rule Rule Screen Screen
calls leads to calls
is called by is assigned to is called by
Screen Rule Screen
leads to activates contains contains
is assigned to is activated by is contents of is contents of
Event Screen Bitmap Button
contains contains contains
is contents of is contents of is contents of
Combo box List control Radio button/Check box
leads to consists of is predecessor of
is assigned to is component of is successor of
Rule Screen Screen
ARIS Methods
11-1024
Model Type
Source Object Type
Target Object Type
Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation Screen navigation
is contents of is contents of is contents of
Spin box Text Text box
Screen Spin box Spin box Text
contains leads to calls leads to
is contents of is assigned to is called by is assigned to
Tree control Rule Screen Rule
Text Text box Text box
calls leads to calls
is called by is assigned to is called by
Screen Rule Screen
leads to calls
is assigned to is called by
Rule Screen
ARIS Methods
11.2.85 SeDaM model
11-1025
11.2.85 SeDaM model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) SeDaM model SeDaM model SeDaM model Attribute type group Entity type Entity type is attribute type group defines (aggregating) defines (hierarchical) SeDaM model Entity type forms an incoming reference with SeDaM model SeDaM model SeDaM model SeDaM model Entity type Entity type Entity type ERM attribute has mandatory field is subtype of is supertype of belongs to is mandatory field has as subtype has as supertype encompasses Generalization type Generalization type Attribute type group ERM attribute is depending hierarchically has reference to Entity type Entity type has attribute type group is aggregating Entity type Entity type Target Object Type
Assignment Relationship SeDaM model
Source Object Type Cluster/Data model
Relationship Type (active) consists of
Relationship Type (passive) is part of
Target Object Type Cluster/Data model
SeDaM model
Cluster/Data model
consists of
is part of
Entity type
ARIS Methods
11.2.86 Shift calendar
11-1026
Source Object Type
Target Object Type
SeDaM model SeDaM model
consists of consists of
is part of is part of
ERM attribute Generalization type
11.2.86 Shift calendar

Model Type Source Object Type Shift calendar Shift calendar Shift calendar Shift Shift cycle Shift plan Relationship Type (active) is interrupted by repeats is superior is repeated by is subordinate Shift Shift cycle Relationship Type (passive) interrupts Break Target Object Type
11.2.87 Structuring model

Model Type Source Object Type Structuring model Structural element Relationship Type (active) contains Relationship Type (passive) is contents of Structural element Target Object Type
ARIS Methods
11.2.88 System attribute domain
11-1027
11.2.88 System attribute domain

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) System attribute domain System attribute has domain is domain for System attribute domain Target Object Type
11.2.89 System attributes

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes Event Event Event Event Entity type Entity type Entity type Entity type is describing for is foreign key for is mandatory field for is primary key for is describing for is foreign key for is mandatory field for is primary key for has foreign key has mandatory field has primary key has foreign key has mandatory field has primary key has describing has describing System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute Target Object Type
ARIS Methods
11.2.89 System attributes
11-1028
Model Type
Source Object Type
Target Object Type
System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes System attributes
is describing for is foreign key for is mandatory field for
has describing has foreign key has mandatory field has primary key has describing has foreign key has mandatory field has primary key has describing has foreign key has mandatory field has primary key has describing
System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute System attribute
Function Information carrier Information carrier Information carrier Information carrier Organizational unit Organizational unit Organizational unit Organizational unit Person
is primary key for is describing for is foreign key for is mandatory field for is primary key for is describing for is foreign key for is mandatory field for is primary key for is describing for
ARIS Methods
11.2.90 Table diagram
11-1029
Model Type
Source Object Type
Target Object Type
System attributes System attributes System attributes System attributes System attributes System attributes System attributes
is foreign key for is mandatory field for is primary key for
has foreign key has mandatory field has primary key has describing has foreign key has mandatory field has primary key
System attribute System attribute System attribute System attribute System attribute System attribute System attribute
is describing for is foreign key for is mandatory field for is primary key for

Model Type Source Object Type Table diagram Domain (physical) Table diagram Table diagram Field Field depicts has is depicted by belongs to Attribute Domain (physical) Table diagram Field depicts is depicted by ERM attribute Relationship Type (active) depicts Relationship Type (passive) is depicted by Domain Target Object Type
ARIS Methods
11-1030
Model Type
Source Object Type
Target Object Type
Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram
Field Field (specimen) Index Memory location Memory location Table Table Table Table
depicts is of type is defined by is assigned to is assigned to depicts owns depicts depicts
is depicted by determines type of defines is assigned to is assigned to is depicted by is part of is depicted by is depicted by
Relationship type Field Field Field Table Entity type Field Relation Relationship type
Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram Table diagram
Table Table Tables (specimen) View (physical) View (physical) View (physical) View (physical)
has reference to depicts is of type reads reads depicts reads
has reference to is depicted by determines type of is read by is read by is depicted by reads
Table View Table Field Table View View (physical)
ARIS Methods
11.2.91 Technical resources
11-1031

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Operating resource Operating resource Operating resource Operating resource class Operating resource type Operating resource type Organizational unit is responsible for is under responsibility of can encompass can belong to belongs to has assigned can encompass can belong to belongs to has assigned encompasses belongs to Operating resource Operating resource type Operating resource class Operating resource class Operating resource type Operating resource Group Group Group Group is responsible for is responsible for is responsible for is responsible for is located at is under responsibility of is under responsibility of is under responsibility of is under responsibility of is location of Operating resource Technical operating supply Transport system Warehouse equipment Location Target Object Type
ARIS Methods
11-1032
Model Type
Source Object Type
Target Object Type
Technical resources
Organizational unit
is responsible for
Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources
Organizational unit Organizational unit Person Person
is responsible for is responsible for is responsible for is responsible for
is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is under responsibility of is depicted by
Transport system Warehouse equipment Operating resource Technical operating supply Transport system Warehouse equipment Operating resource Technical operating supply Transport system Warehouse equipment Warehouse equipment
Person
is responsible for
Person Position Position
is responsible for is responsible for is responsible for
Position
is responsible for
Position System organizational unit
is responsible for depicts
ARIS Methods
11-1033
Model Type
Source Object Type
Target Object Type
Technical resources
depicts
is depicted by
Technical resources
Tech. operating supply class
can encompass
can belong to
Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources
Technical operating supply Technical operating supply Technical operating supply Technical operating supply type Technical operating supply type Transport system Transport system Transport system
is located at
is location of
Location
encompasses
belongs to
belongs to
has assigned
belongs to
has assigned
can encompass
can belong to
is located at
is location of
Location
encompasses belongs to
belongs to has assigned
Transport system Transport system type
ARIS Methods
11-1034
Model Type
Source Object Type
Target Object Type
Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources Technical resources
Transport system class Transport system type Transport system type Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment class Warehouse equipment type Warehouse equipment type
can encompass belongs to can encompass
can belong to has assigned can belong to
Transport system class Transport system class Transport system type
is located at encompasses belongs to
is location of belongs to has assigned
Location Warehouse equipment Warehouse equipment type
can encompass
can belong to
Warehouse equipment class
belongs to
has assigned
Warehouse equipment class
can encompass
can belong to
ARIS Methods
11.2.92 Technical terms model
11-1035
11.2.92 Technical terms model

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model Technical term Technical term has relation with is a has relation with is a Technical term Technical term Technical term has belongs to Technical term Technical term encompasses is part of Technical term Technical term classifies is classified Technical term Technical term can be can be Technical term depicts is depicted by Relationship type Technical term Technical term depicts is depicted by Package Technical term depicts is depicted by ERM attribute Technical term depicts is depicted by Technical term depicts is depicted by Cluster/Data model Entity type Technical term depicts is depicted by Class Target Object Type
ARIS Methods
11.2.93 UML Activity diagram
11-1036
Model Type
Source Object Type
Target Object Type
Technical terms model
Technical term
is a functional generic term of
is a functional subterm of
Technical term
Technical terms model Technical terms model Technical terms model Technical terms model Technical terms model
is feature of is generic term of is part of is specimen of
has feature is subterm of has part has specimen
Technical term
synonym (preferred term of)
synonym (not a preferred term of)
Technical term

Model Type Source Object Type UML Activity diagram UML Activity diagram UML Activity diagram Action sends signal has been sent Signal Action sends signal has been sent Exception Action Relationship Type (active) contains Relationship Type (passive) is contained by Action Target Object Type
ARIS Methods
11-1037
Model Type
Source Object Type
Target Object Type
UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram
Activity graph Activity graph Application system type Class Class Class Classifier-instate Classifier-instate Classifier-instate Classifier-instate Classifier-instate Classifier-instate Classifier-instate
has partition has top state carries out
is partition of is top state of is carried out by
Partition Product/Service Function
has member has member has member associates (multiple) has type has type generalizes
is member of is member of is member of is associated by (multiple) is type of is type of specializes
ERM attribute Function Reception Association
Association class Class Classifier-instate
has member is triggered by has member
is member of triggers is member of
ARIS Methods
11-1038
Model Type
Source Object Type
Target Object Type
Classifier-instate Classifier-instate Classifier-instate Classifier-instate Classifier-instate Constraint Constraint
is in state is nested is in state
has been put in state nests has been put in state
Function Package Product/Service Reception UML Model Action Activity graph
has member is nested concerns concerns
is member of nests is concerned by is concerned by
Application system type Argument Association class Class Classifier-instate Event
ARIS Methods
11-1039
Model Type
Source Object Type
Target Object Type
Function Group Object instance Operating resource type Organizational unit Parameter Partition
Constraint Constraint Constraint Constraint
concerns concerns concerns concerns
is concerned by is concerned by is concerned by is concerned by
Product/Service Programming language type Rule
ARIS Methods
11-1040
Model Type
Source Object Type
Target Object Type
Constraint Constraint Event
concerns concerns has effect
is concerned by is concerned by is effect of
Signal Transport system type Action
Event Event Event Exception
receives signal calls receives signal has member
sends signal is called by sends signal is member of
Exception Function Signal ERM attribute
Exception Exception Function
has member has member performs on entry
is member of is member of is performed on entry is raised by is internal transition of follows
Function Reception Action
raises has internal transition to is predecessor of
Exception Function Function
ARIS Methods
11-1041
Model Type
Source Object Type
Target Object Type
Function
is measured by
measures
UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram
has internal transition to has internal transition to has output of has transition to
is internal transition of is internal transition of is output of has transition from is internal transition of is internal transition of is assigned to
Operating resource type Organizational unit Product/Service Product/Service Programming language type Rule Rule
has internal transition to has internal transition to leads to
raises has internal transition to carries out
is raised by is internal transition of is carried out by
Signal Transport system type Function
Link object Link object
has guard depends
is guard of is depending
Constraint Link object
ARIS Methods
11-1042
Model Type
Source Object Type
Target Object Type
Link object Link object Link object
depends depends depends
is depending is depending is depending
Operating resource type Organizational unit Programming language type
Link object Link object Note Note
depends depends belongs to belongs to
is depending is depending belongs to belongs to
Rule Transport system type Action Activity graph
Note Note Note
Application system type Argument Association class
Note Note Note
Class Classifier-instate Constraint
ARIS Methods
11-1043
Model Type
Source Object Type
Target Object Type
Note Note Note
Event Function Group
Note Note Note Note
belongs to belongs to belongs to belongs to
Note Object instance Operating resource type Organizational unit
Note Note Note
Parameter Partition Person
Note Note Note
Person type Position Product/Service
ARIS Methods
11-1044
Model Type
Source Object Type
Target Object Type
Note Note Note
Programming language type Rule Signal
Note Object instance Object instance Object instance Object instance Object instance Object instance Object instance Operating resource type Operating resource type
belongs to depends depends depends
belongs to is depending is depending is depending
Transport system type Link object Object instance Operating resource type
depends depends depends
is depending is depending is depending
Organizational unit Programming language type Rule
depends has effect has guard
is depending is effect of is guard of
Transport system type Action Constraint
ARIS Methods
11-1045
Model Type
Source Object Type
Target Object Type
Operating resource type Operating resource type Operating resource type Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Partition
is triggered by depends depends
triggers is depending is depending
Event Link object Object instance
has effect has guard is triggered by carries out
is effect of is guard of triggers is carried out by
Action Constraint Event Function
depends depends contains
is depending is depending is contained by
Link object Object instance Function
Partition Partition Partition
is contained by is contained by is contained by
Object instance Product/Service Rule
ARIS Methods
11-1046
Model Type
Source Object Type
Target Object Type
carries out carries out carries out
is carried out by is carried out by is carried out by
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
has type has type has type has transition to is input for has internal transition to has internal transition to has parameter has internal transition to has transition to
is type of is type of is type of has transition from has input of is internal transition of is internal transition of is parameter of is internal transition of has transition from
Association class Class Classifier-instate Function
Function Operating resource type Organizational unit Parameter Product/Service Product/Service
ARIS Methods
11-1047
Model Type
Source Object Type
Target Object Type
Product/Service Product/Service Product/Service Product/Service Programming language type Programming language type Programming language type Programming language type Programming language type Reception
has internal transition to has internal transition to has transition to has internal transition to has effect has guard is triggered by
is internal transition of is internal transition of has transition from is internal transition of is effect of is guard of triggers
Programming language type Rule Rule
Transport system type Action Constraint Event
depends depends raises
is depending is depending is raised by
Link object Object instance Exception
Reception Reception Reception
receives signal raises receives signal
sends signal is raised by sends signal
Exception Signal Signal
ARIS Methods
11-1048
Model Type
Source Object Type
Target Object Type
Rule Rule Rule
has effect has guard is triggered by
is effect of is guard of triggers
Action Constraint Event
Rule Rule Rule Rule
activates depends depends has transition to
is activated by is depending is depending has transition from has transition from is linked by is member of
Function Link object Object instance Product/Service Rule Rule ERM attribute
Rule Rule Signal
has transition to links has member
Signal Signal Transport system type
has member has member has effect
is member of is member of is effect of
Function Reception Action
ARIS Methods
11.2.94 UML Class description diagram
11-1049
Model Type
Source Object Type
Target Object Type
UML Activity diagram UML Activity diagram UML Activity diagram UML Activity diagram
Transport system type Transport system type Transport system type Transport system type
has guard is triggered by depends
is guard of triggers is depending
Constraint Event Link object
depends
is depending
Object instance

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram Class has member is member of ERM attribute Class has enumeration literal is enumeration literal of Enumeration literal Class supports is supported Class Association class has member is member of ERM attribute Target Object Type
ARIS Methods
11-1050
Model Type
Source Object Type
Target Object Type
UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram
Class
has member
is member of
Function
Class
has instance
is instance
Object instance
Constraint
concerns
is concerned by
Association class Class
Constraint
concerns
is concerned by
Constraint
concerns
is concerned by
Constraint
Constraint
concerns
is concerned by
Enumeration literal ERM attribute
Constraint
concerns
is concerned by
Constraint
concerns
is concerned by
Function
Constraint
concerns
is concerned by
Object instance
ARIS Methods
11-1051
Model Type
Source Object Type
Target Object Type
UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram
Constraint
concerns
is concerned by
Parameter
ERM attribute
has type
is type of
Association class
ERM attribute
has type
is type of
Class
Function
has parameter
is parameter of
Parameter
Note
belongs to
belongs to
Association class
Note
belongs to
belongs to
Class
Note
belongs to
belongs to
Constraint
Note
belongs to
belongs to
Enumeration literal
Note
belongs to
belongs to
ERM attribute
ARIS Methods
11-1052
Model Type
Source Object Type
Target Object Type
UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram UML Class description diagram
Note
belongs to
belongs to
Function
Note
belongs to
belongs to
Note
Note
belongs to
belongs to
Parameter
Note
belongs to
belongs to
Role
Parameter
has type
is type of
Association class
Parameter
has type
is type of
Class
Assignment Relationship UML Class description diagram UML Class description diagram
Source Object Type Class
Relationship Type (active) has member
Relationship Type (passive) is member of
Target Object Type ERM attribute
Class
has member
is member of
Function
ARIS Methods
11.2.95 UML Class diagram
11-1053

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram Association permits access access is permitted by Association Association has member is member of Association Association generalizes specializes Association Association depends is depending Association Activity graph is nested nests UML Model Activity graph is nested nests Package Action sends signal has been sent Signal Action calls is called by Function Action sends signal has been sent Exception Action is nested Action instantiate is instantiated by nests Collaboration Class Action has argument is argument of Argument Target Object Type
ARIS Methods
11-1054
Model Type
Source Object Type
Target Object Type
UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram
Association Association Association
realizes refines uses
is realized by is refined by is used by
Association Association Association Association
depends is nested permits access realizes
is depending nests access is permitted by is realized by
Association class Association class Association class Association class
refines uses has instance
is refined by is used by is instance
Association class Association class Association instance
depends has argument is nested
is depending is argument of nests
Class Class Class
ARIS Methods
11-1055
Model Type
Source Object Type
Target Object Type
permits access realizes refines
access is permitted by is realized by is refined by
Class Class Class
uses depends permits access realizes
is used by is depending access is permitted by is realized by
Class Exception Exception Exception
refines uses depends
is refined by is used by is depending
Exception Exception Package
is nested permits access realizes
nests access is permitted by is realized by
Package Package Package
ARIS Methods
11-1056
Model Type
Source Object Type
Target Object Type
Package Package Signal
permits access realizes refines uses
access is permitted by is realized by is refined by is used by
Signal Signal Signal Signal
depends is nested permits access
is depending nests access is permitted by
Subsystem Subsystem Subsystem
ARIS Methods
11-1057
Model Type
Source Object Type
Target Object Type
UML Model UML Model UML Model
Association Association Association Association class Association class Association class Association class Association class Association class Association class
realizes refines uses associates (multiple) depends permits access realizes
is realized by is refined by is used by is associated by (multiple) is depending access is permitted by is realized by
UML Model UML Model UML Model Association
refines uses associates (multiple)
is refined by is used by is associated by (multiple)
Association Association Association class
ARIS Methods
11-1058
Model Type
Source Object Type
Target Object Type
Association class Association class Association class Association class Association class Association class Association class Association class Association class Association class Association class Association class Association class
depends generalizes has member
is depending specializes is member of
Association class Association class Association class
is nested permits access realizes refines
nests access is permitted by is realized by is refined by
uses has slot depends
is used by is slot of is depending
Association class Attribute link Class
has default element is nested permits access
is default element of nests access is permitted by
Class Class Class
ARIS Methods
11-1059
Model Type
Source Object Type
Target Object Type
Class Class Class
has member depends permits access realizes
is member of is depending access is permitted by is realized by
ERM attribute Exception Exception Exception
refines uses has member
is refined by is used by is member of
has instance depends is nested
is instance is depending nests
Link object Package Package
ARIS Methods
11-1060
Model Type
Source Object Type
Target Object Type
uses has member depends has specification permits access realizes refines
is used by is member of is depending is specification of access is permitted by is realized by is refined by
Package Reception Signal Signal
Signal Signal Signal
uses depends is nested
is used by is depending nests
Signal Subsystem Subsystem
ARIS Methods
11-1061
Model Type
Source Object Type
Target Object Type
Association class Association class Association class Association class Association class Association class Association class Association class Association class Association class Association instance Association instance Association instance
uses depends is nested permits access
is used by is depending nests access is permitted by
Subsystem UML Model UML Model UML Model
depends has flow to permits access
is depending receives flow from access is permitted by
Association instance Association instance Association instance
ARIS Methods
11-1062
Model Type
Source Object Type
Target Object Type
Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance Association instance
depends is linked with permits access realizes
is depending is linked with access is permitted by is realized by
Data value Data value Data value Data value
Data value Data value Link object
is linked with permits access realizes
is linked with access is permitted by is realized by
ARIS Methods
11-1063
Model Type
Source Object Type
Target Object Type
Link object Link object Object instance
is linked with is owned by permits access realizes
is linked with owns access is permitted by is realized by
Object instance Object instance Object instance Object instance
Object instance Object instance Subsystem instance
is linked with is owned by permits access
is linked with owns access is permitted by
Subsystem instance Subsystem instance Subsystem instance
ARIS Methods
11-1064
Model Type
Source Object Type
Target Object Type
Association instance Association instance Association instance Association instance Association instance Association role Association role Association role Association role Association role Association role Association role Attribute link
is linked to is linked with has base is nested
is linked to is linked with is base of nests
Use case instance Use case instance Association Association class
generalizes is nested is nested
specializes nests nests
Association role Class Collaboration
is nested is nested has value
nests nests is value of
Package UML Model Data value
ARIS Methods
11-1065
Model Type
Source Object Type
Target Object Type
Attribute link Attribute link Attribute link
originates from has value has value
is origin of is value of is value of
ERM attribute Link object Object instance
has behavior associates (multiple) depends permits access
is behavior of is associated by (multiple) is depending access is permitted by
Activity graph Association Association Association
Class Class Class
realizes refines supplies properties for
is realized by is refined by has properties supplied by is used by is associated by (multiple) is depending
Class Class Class
uses associates (multiple) depends
Association Association class Association class
ARIS Methods
11-1066
Model Type
Source Object Type
Target Object Type
Class Class Class
refines uses associates binds
is refined by is used by is associated is bound by
Association class Association class Class Class
Class Class Class
calls depends generalizes
is called by is depending specializes
Class Class Class
Class Class Class
has template parameter is nested permits access
is template parameter of nests access is permitted by
Class Class Class
ARIS Methods
11-1067
Model Type
Source Object Type
Target Object Type
Class Class Class
realizes refines supports
is realized by is refined by is supported
Class Class Class
uses has default element has instance has enumeration literal
is used by is default element of is instance is enumeration literal of is member of is depending access is permitted by
Class Data value Data value Enumeration literal ERM attribute Exception Exception
Class Class Class
has member depends permits access
Class Class Class
Exception Exception Exception
ARIS Methods
11-1068
Model Type
Source Object Type
Target Object Type
Class Class Class
has member has instance depends
is member of is instance is depending
Function Object instance Package
Package Package Package Package
Class Class Class
uses has member depends
is used by is member of is depending
Package Reception Signal
Class Class Class
ARIS Methods
11-1069
Model Type
Source Object Type
Target Object Type
Class Class Class
uses has behavior depends
is used by is behavior of is depending
Signal State machine Subsystem
Subsystem Subsystem Subsystem Subsystem
Class Class Class
uses depends is nested
is used by is depending nests
Subsystem UML Model UML Model
Class Class Class
ARIS Methods
11-1070
Model Type
Source Object Type
Target Object Type
Class Classifier role Classifier role
uses has base has base
is used by is base of is base of
UML Model Association class Class
Classifier role Classifier role Classifier role Classifier role
generalizes is nested has member has member
specializes nests is member of is member of
Classifier role Collaboration ERM attribute Function
Classifier role Classifier role Classifier role
is nested has member is nested
nests is member of nests
Package Reception UML Model
Collaboration Collaboration Collaboration
is nested is nested is nested
nests nests nests
Association class Class Package
ARIS Methods
11-1071
Model Type
Source Object Type
Target Object Type
Collaboration Collaboration Collaboration instance set Collaboration instance set Collaboration instance set Collaboration instance set Collaboration instance set Constraint Constraint Constraint
is nested is nested has participating instance has participating instance has participating instance has participating instance has participating instance concerns concerns is nested
nests nests participates
Subsystem UML Model Association instance
participates participates participates participates
Link object Object instance Subsystem instance Use case instance
is concerned by is concerned by nests
concerns concerns has powertype
is concerned by is concerned by is powertype of
Association instance Class Class
ARIS Methods
11-1072
Model Type
Source Object Type
Target Object Type
is nested concerns is nested
nests is concerned by nests
Class Collaboration Collaboration
concerns concerns concerns concerns
is concerned by is concerned by is concerned by is concerned by
Constraint Data value Enumeration literal ERM attribute
Exception Function Link object
concerns concerns is nested
is concerned by is concerned by nests
Object instance Package Package
ARIS Methods
11-1073
Model Type
Source Object Type
Target Object Type
Parameter Reception Signal
concerns is nested concerns concerns
is concerned by nests is concerned by is concerned by
Subsystem Subsystem Subsystem instance UML Model
Constraint Data value Data value
is nested depends permits access
nests is depending access is permitted by
UML Model Association instance Association instance Association instance Association instance Association instance
ARIS Methods
11-1074
Model Type
Source Object Type
Target Object Type
depends has flow to permits access
is depending receives flow from access is permitted by
realizes refines uses depends
is realized by is refined by is used by is depending
Data value Data value Data value Link object
uses depends is owned by
is used by is depending owns
Link object Object instance Object instance
ARIS Methods
11-1075
Model Type
Source Object Type
Target Object Type
Object instance Object instance Object instance
uses depends is owned by permits access
is used by is depending owns access is permitted by
Object instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance
has type has specification has type
is type of is specification of is type of
Association class Class Class
ARIS Methods
11-1076
Model Type
Source Object Type
Target Object Type
Event Event Exception
has qualifier receives signal associates (multiple)
is qualifier of sends signal is associated by (multiple) is depending access is permitted by is realized by is refined by
ERM attribute Signal Association
Exception Exception Exception Exception
depends permits access realizes refines
uses associates (multiple) depends
is used by is associated by (multiple) is depending
ARIS Methods
11-1077
Model Type
Source Object Type
Target Object Type
uses depends permits access
is used by is depending access is permitted by
realizes refines uses has member
is realized by is refined by is used by is member of
Class Class Class ERM attribute
depends generalizes permits access
is depending specializes access is permitted by
ARIS Methods
11-1078
Model Type
Source Object Type
Target Object Type
has member depends is nested
is member of is depending nests
Function Package Package
is member of is depending access is permitted by
Reception Signal Signal
ARIS Methods
11-1079
Model Type
Source Object Type
Target Object Type
Subsystem Subsystem Subsystem UML Model
refines uses has behavior
is refined by is used by is behavior of
UML Model UML Model Activity graph
ARIS Methods
11-1080
Model Type
Source Object Type
Target Object Type
has template parameter raises binds
is template parameter of is raised by is bound by
Class Exception Function
Function Function Function Link object
has parameter raises has behavior depends
is parameter of is raised by is behavior of is depending
Parameter Signal State machine Association instance
uses has slot depends
is used by is slot of is depending
Association instance Attribute link Data value
ARIS Methods
11-1081
Model Type
Source Object Type
Target Object Type
Link object Link object Link object Link object
refines uses depends has flow to
is refined by is used by is depending receives flow from
Data value Data value Link object Link object
Link object Link object Object instance
ARIS Methods
11-1082
Model Type
Source Object Type
Target Object Type
is linked with is owned by permits access
is linked with owns access is permitted by
Object instance Object instance Object instance Object instance Object instance Object instance Subsystem
Link object Link object Link object Link object
realizes refines uses has specification
is realized by is refined by is used by is specification of is depending is linked with owns
depends is linked with is owned by
ARIS Methods
11-1083
Model Type
Source Object Type
Target Object Type
Link object Link object Note
uses is linked with belongs to
is used by is linked with belongs to
Subsystem instance Use case instance Association
Note Note Note Note
Association class Association instance Class Collaboration
Note Note Note
Collaboration instance set Constraint Data value
Note Note Note
Enumeration literal ERM attribute Exception
ARIS Methods
11-1084
Model Type
Source Object Type
Target Object Type
Note Note Note
Function Link object Note
Note Note Note Note
Object instance Package Parameter Role
Note Note Note
Signal Subsystem Subsystem instance
Note Object instance Object instance
belongs to has specification depends
belongs to is specification of is depending
UML Model Association class Association instance
ARIS Methods
11-1085
Model Type
Source Object Type
Target Object Type
Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance
uses has slot depends permits access
is used by is slot of is depending access is permitted by
Association instance Attribute link Data value Data value
has specification depends permits access
is specification of is depending access is permitted by
Exception Link object Link object
ARIS Methods
11-1086
Model Type
Source Object Type
Target Object Type
depends has argument has flow to is linked with
is depending is argument of receives flow from is linked with
Object instance Object instance Object instance Object instance
is owned by permits access realizes
owns access is permitted by is realized by
Object instance Object instance Subsystem instance
ARIS Methods
11-1087
Model Type
Source Object Type
Target Object Type
Object instance Object instance Object instance Object instance Object instance Operating resource type Package
refines uses has guard has behavior
is refined by is used by is guard of is behavior of
Subsystem instance Subsystem instance Constraint Activity graph
contains depends imports
is contained by is depending is imported
ARIS Methods
11-1088
Model Type
Source Object Type
Target Object Type
uses depends imports
is used by is depending is imported
contains depends imports
is contained by is depending is imported
Class Class Class
permits access realizes references
access is permitted by is realized by is referenced by
Class Class Class
ARIS Methods
11-1089
Model Type
Source Object Type
Target Object Type
refines uses imports
is refined by is used by is imported
Class Class Classifier role
imports imports contains references
is imported is imported is contained by is referenced by
Collaboration Constraint ERM attribute ERM attribute
depends imports permits access
is depending is imported access is permitted by
ARIS Methods
11-1090
Model Type
Source Object Type
Target Object Type
contains references contains
is contained by is referenced by is contained by
Function Function Note
references contains references accesses
is referenced by is contained by is referenced by is accessed
Note Object instance Object instance Package
contains depends generalizes
is contained by is depending specializes
imports is nested permits access
is imported nests access is permitted by
ARIS Methods
11-1091
Model Type
Source Object Type
Target Object Type
realizes references refines
is realized by is referenced by is refined by
uses depends imports permits access
is used by is depending is imported access is permitted by
Package Signal Signal Signal
depends imports is nested
is depending is imported nests
ARIS Methods
11-1092
Model Type
Source Object Type
Target Object Type
uses depends imports is nested
is used by is depending is imported nests
Subsystem UML Model UML Model UML Model
Package Parameter Parameter
uses has type has type
is used by is type of is type of
UML Model Association class Class
ARIS Methods
11-1093
Model Type
Source Object Type
Target Object Type
Reception Reception Reception
has behavior raises has parameter
is behavior of is raised by is parameter of
Activity graph Exception Parameter
Reception Reception Reception Signal
raises receives signal has behavior associates (multiple)
is raised by sends signal is behavior of is associated by (multiple) is depending access is permitted by is realized by
Signal Signal State machine Association
depends permits access realizes
is refined by is used by is associated by (multiple)
Association Association Association class
ARIS Methods
11-1094
Model Type
Source Object Type
Target Object Type
is depending access is permitted by is realized by
refines uses depends permits access
is refined by is used by is depending access is permitted by
Association class Association class Class Class
Class Class Class
is member of is depending access is permitted by
ERM attribute Exception Exception
ARIS Methods
11-1095
Model Type
Source Object Type
Target Object Type
has member depends is nested permits access
is member of is depending nests access is permitted by
Function Package Package Package
has member depends generalizes
is member of is depending specializes
Reception Signal Signal
ARIS Methods
11-1096
Model Type
Source Object Type
Target Object Type
uses depends is nested permits access
is used by is depending nests access is permitted by
Signal Subsystem Subsystem Subsystem
ARIS Methods
11-1097
Model Type
Source Object Type
Target Object Type
State machine State machine State machine State machine
has guard is nested is nested is nested
is guard of nests nests nests
Constraint Package Subsystem UML Model
has behavior associates (multiple) depends
is behavior of is associated by (multiple) is depending
Activity graph Association Association
imports permits access realizes
is imported access is permitted by is realized by
ARIS Methods
11-1098
Model Type
Source Object Type
Target Object Type
is refined by is used by is associated by (multiple) is depending is imported access is permitted by is realized by
Association Association Association class Association class Association class Association class Association class
depends imports permits access realizes
Association class Association class Class
imports permits access realizes
is imported access is permitted by is realized by
Class Class Class
ARIS Methods
11-1099
Model Type
Source Object Type
Target Object Type
refines uses imports
is refined by is used by is imported
Class Class Collaboration
imports has argument depends imports
is imported is argument of is depending is imported
Constraint Data value Exception Exception
uses has member depends
is used by is member of is depending
Exception Function Package
ARIS Methods
11-1100
Model Type
Source Object Type
Target Object Type
realizes refines uses has member
is realized by is refined by is used by is member of
Package Package Package Reception
ARIS Methods
11-1101
Model Type
Source Object Type
Target Object Type
depends generalizes imports
is depending specializes is imported
uses has instance depends
is used by is instance is depending
Subsystem Subsystem instance UML Model
ARIS Methods
11-1102
Model Type
Source Object Type
Target Object Type
Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance
is depending access is permitted by is realized by is refined by
Association instance Association instance Association instance Association instance
Association instance Data value Data value
ARIS Methods
11-1103
Model Type
Source Object Type
Target Object Type
Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance Subsystem instance
Link object Link object Object instance Object instance Object instance Object instance Object instance
depends has flow to is owned by
is depending receives flow from owns
ARIS Methods
11-1104
Model Type
Source Object Type
Target Object Type
Subsystem instance Subsystem instance Subsystem instance Subsystem instance UML Model UML Model UML Model
uses has behavior depends imports
is used by is behavior of is depending is imported
Subsystem instance Activity graph Association Association
uses depends imports
is used by is depending is imported
ARIS Methods
11-1105
Model Type
Source Object Type
Target Object Type
UML Model UML Model UML Model UML Model
uses depends imports permits access
is used by is depending is imported access is permitted by
Association class Class Class Class
Class Class Class
imports imports imports
is imported is imported is imported
Classifier role Collaboration Constraint
ARIS Methods
11-1106
Model Type
Source Object Type
Target Object Type
Exception Exception Exception Package
ARIS Methods
11-1107
Model Type
Source Object Type
Target Object Type
Signal Signal Signal Subsystem
ARIS Methods
11-1108
Model Type
Source Object Type
Target Object Type
UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram
depends imports is nested
is depending is imported nests
Use case instance Use case instance Use case instance
has type is owned by is owned by
is type of owns owns
Class Object instance Subsystem instance
ARIS Methods
11-1109
Source Object Type
Target Object Type
UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram UML Class diagram
Class Component ERM attribute
contains contains contains contains
is contained by is contained by is contained by is contained by
Function Note Object instance Organizational unit
Package Person type Rule
ARIS Methods
11.2.96 UML Collaboration diagram
11-1110

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram Constraint concerns Constraint concerns Constraint concerns Constraint concerns Constraint concerns Constraint concerns Constraint concerns Class interacts with Class interacts with Association instance Association role Class associates classifier role interacts with is associated to has interaction from has interaction from has interaction from is concerned by is concerned by is concerned by is concerned by is concerned by is concerned by is concerned by Constraint Classifier role Class Association class Association instance Association role Attribute link Object instance Person type Class is linked with is linked with Object instance Classifier role Target Object Type
ARIS Methods
11-1111
Model Type
Source Object Type
Target Object Type
UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram
ERM attribute Link object Object instance Link object Association class Interaction instance set Link object
Data value ERM attribute Interaction instance set Link object
realizes has type has participating stimulus is linked with
is realized by is type of participates is linked with
Link object Note Note
is linked with belongs to belongs to
is linked with belongs to belongs to
Object instance Association instance Association role
Note Note Note
Attribute link Class Classifier role
ARIS Methods
11-1112
Model Type
Source Object Type
Target Object Type
UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram UML Collaboration diagram
Note Note Note
Collaboration instance set Constraint ERM attribute
Note Note Note Note
Interaction instance set Link object Note Object instance
Object instance Object instance Object instance Person type Person type
interacts with interacts with interacts with
has interaction from has interaction from has interaction from
Class Object instance Person type
interacts with interacts with
has interaction from has interaction from
Class Object instance
ARIS Methods
11.2.97 UML Component diagram
11-1113

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram Association permits access access is permitted by Signal Association uses is used by Component Association resides in contains Component Association refines is refined by Component Association realizes Association permits access access is permitted by is realized by Component Component Association depends is depending Component Artifact is nested nests UML Model Artifact Artifact Artifact associates (multiple) associates (multiple) is nested is associated by (multiple) is associated by (multiple) nests Association class Package Association Artifact generalizes specializes Artifact Target Object Type
ARIS Methods
11-1114
Model Type
Source Object Type
Target Object Type
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
Association Association class Association class Class Class Class Class
uses has member resides in
is used by is member of contains
Signal Association class Component
depends refines depends is nested
is depending is refined by is depending nests
Association Association Class Class
Class Class Class
Class Class Class
Class Class Class
Class Component Component
ARIS Methods
11-1115
Model Type
Source Object Type
Target Object Type
Class Class Class
realizes refines resides in
is realized by is refined by contains
uses has enumeration literal has member has member
is used by is enumeration literal of is member of is member of
Component Enumeration literal ERM attribute Function
Class Class Class
Class Class Class
refines uses has member
is refined by is used by is member of
Package Package Reception
ARIS Methods
11-1116
Model Type
Source Object Type
Target Object Type
permits access is implemented by associates (multiple)
access is permitted by implements is associated by (multiple) is depending access is permitted by is realized by is refined by
Signal Artifact Association
uses associates (multiple) calls
is used by is associated by (multiple) is called by
Association Association class Class
Class Class Class
ARIS Methods
11-1117
Model Type
Source Object Type
Target Object Type
refines supports uses
is refined by is supported is used by
Class Class Class
contains depends is nested permits access
is contained by is depending nests access is permitted by
refines refines refines
is refined by is refined by is refined by
Exception Package Signal
ARIS Methods
11-1118
Model Type
Source Object Type
Target Object Type
Component Constraint Constraint
refines concerns concerns
is refined by is concerned by is concerned by
UML Model Artifact Association
concerns is nested concerns resides in
is concerned by nests is concerned by contains
Class Class Component Component
Constraint Enumeration literal Object instance Package Component Association class
Constraint Data value Exception
concerns resides in realizes
is concerned by contains is realized by
ARIS Methods
11-1119
Model Type
Source Object Type
Target Object Type
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
refines refines resides in
is refined by is refined by contains
Association class Component Component
raises deploys
is raised by is deployed
Exception Component
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
Link object Note Note
resides in belongs to belongs to
contains belongs to belongs to
Component Artifact Class
Note Note Note
Component Constraint Enumeration literal
Note Note
Function Note
ARIS Methods
11-1120
Model Type
Source Object Type
Target Object Type
Note Note Note
Object instance Package Reception
Object instance Object instance Object instance Object instance Object instance Object instance Package
resides in depends permits access realizes
contains is depending access is permitted by is realized by
Component Object instance Object instance Object instance
refines uses contains
is refined by is used by is contained by
Object instance Object instance Class
Class Class Class
ARIS Methods
11-1121
Model Type
Source Object Type
Target Object Type
refines uses contains
is refined by is used by is contained by
Class Class Component
refines contains depends permits access
is refined by is contained by is depending access is permitted by
Component Package Package Package
Package Reception Reception
permits access raises receives signal
access is permitted by is raised by sends signal
Signal Exception Exception
ARIS Methods
11-1122
Model Type
Source Object Type
Target Object Type
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
realizes refines refines
is realized by is refined by is refined by
Association class Association class Component
Signal UML Model
resides in refines
contains is refined by
Component Component
Source Object Type
Target Object Type
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
Component Package Package
Component Association Class
Component ERM attribute Function
ARIS Methods
11-1123
Source Object Type
Target Object Type
UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram UML Component diagram
Note Object instance Organizational unit
Package Person type Rule

Model Type Source Object Type UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram Association refines is refined by Association Association realizes Association permits access access is permitted by is realized by Association Association Association Relationship Type (active) depends Relationship Type (passive) is depending Association Target Object Type
ARIS Methods
11-1124
Model Type
Source Object Type
Target Object Type
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Association Association class Association class Association class Association class Association class Association instance
realizes refines uses has instance
is realized by is refined by is used by is instance
Class Class Class
Class Class Class
ARIS Methods
11-1125
Model Type
Source Object Type
Target Object Type
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Association Association
refines depends
is refined by is depending
Component Hardware component type
UML Deployment diagram
Association
permits access
access is permitted by
Association
realizes
is realized by
Association
refines
is refined by
Association
uses
is used by
UML Deployment diagram UML Deployment diagram
Association class Association class
depends permits access
is depending access is permitted by
ARIS Methods
11-1126
Model Type
Source Object Type
Target Object Type
is depending access is permitted by is realized by is refined by
Class Class Class
ARIS Methods
11-1127
Model Type
Source Object Type
Target Object Type
Association class
depends
is depending
Association class
permits access
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Association class Association class Association class Association instance Association instance Association instance Association instance Association instance Association instance
realizes
is realized by
refines
is refined by
uses
is used by
depends
is depending
Association instance
uses depends
is used by is depending
Association instance Component instance
ARIS Methods
11-1128
Model Type
Source Object Type
Target Object Type
Component instance Component instance Component instance
refines uses depends is linked with
is refined by is used by is depending is linked with
Component instance Component instance Hardware component Hardware component
Hardware component Hardware component Hardware component
uses is linked with is owned by
is used by is linked with owns
Hardware component Object instance Object instance
ARIS Methods
11-1129
Model Type
Source Object Type
Target Object Type
Association instance Association instance Association instance Association instance Class Class Class
uses associates (multiple) depends permits access
is used by is associated by (multiple) is depending access is permitted by
Object instance Association Association Association
Class Class Class
Class Class Class
ARIS Methods
11-1130
Model Type
Source Object Type
Target Object Type
Class Class Class
Association class Association class Class
Class Class Class
Class Class Class
ARIS Methods
11-1131
Model Type
Source Object Type
Target Object Type
Class
depends
is depending
Class
permits access
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Class
realizes
is realized by
Class
refines
is refined by
Class
uses
is used by
Class
has instance
is instance
Object instance
Collaboration instance set Collaboration instance set Component
has participating instance has participating instance associates (multiple)
participates participates is associated by (multiple) is depending access is permitted by
Component instance Hardware component Association
Component Component
depends permits access
ARIS Methods
11-1132
Model Type
Source Object Type
Target Object Type
associates (multiple) depends permits access realizes
is associated by (multiple) is depending access is permitted by is realized by
Association class Class Class Class
Class Class Component
generalizes is nested permits access
specializes nests access is permitted by
ARIS Methods
11-1133
Model Type
Source Object Type
Target Object Type
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Component Component
has instance depends
is instance is depending
Component instance Hardware component type
Component
permits access
Component
realizes
is realized by
Component
refines
is refined by
Component
uses
is used by
UML Deployment diagram UML Deployment diagram
Component Component
is nested refines
nests is refined by
Package Package
ARIS Methods
11-1134
Model Type
Source Object Type
Target Object Type
Component Component Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance
is nested refines depends
nests is refined by is depending
UML Model UML Model Association instance
Association instance Association instance Association instance Association instance
depends is owned by permits access
is depending owns access is permitted by
Component instance Component instance Component instance Component instance Component instance Component instance
ARIS Methods
11-1135
Model Type
Source Object Type
Target Object Type
Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Component instance Constraint Constraint Constraint
Hardware component Hardware component Object instance Object instance Object instance Object instance Object instance
Association Association instance Class
ARIS Methods
11-1136
Model Type
Source Object Type
Target Object Type
is nested concerns concerns
nests is concerned by is concerned by
Class Component Component instance Constraint Hardware component Hardware component type Object instance Association instance
Constraint Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component
concerns depends
is concerned by is depending
uses contains
is used by is contained by
Association instance Component instance
ARIS Methods
11-1137
Model Type
Source Object Type
Target Object Type
Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component
Component instance Component instance Hardware component Hardware component Hardware component Hardware component Hardware component
ARIS Methods
11-1138
Model Type
Source Object Type
Target Object Type
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Hardware component Hardware component Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type
refines uses associates (multiple) depends
is refined by is used by is associated by (multiple) is depending
Object instance Object instance Association
Association
permits access
Association
realizes
is realized by
Association
refines
is refined by
Association
uses
is used by
Association
associates (multiple) depends
is associated by (multiple) is depending
Association class Association class
ARIS Methods
11-1139
Model Type
Source Object Type
Target Object Type
permits access
Association class
realizes
is realized by
Association class
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
refines
is refined by
Association class
uses
is used by
Association class
depends
is depending
Class
permits access
Class
realizes
is realized by
Class
refines
is refined by
Class
uses
is used by
Class
ARIS Methods
11-1140
Model Type
Source Object Type
Target Object Type
depends
is depending
Component
deploys
is deployed
Component
permits access
Component
realizes
is realized by
Component
refines
is refined by
Component
uses
is used by
Component
has member
is member of
ERM attribute
has member
is member of
Function
has instance
is instance
Hardware component
ARIS Methods
11-1141
Model Type
Source Object Type
Target Object Type
depends
is depending
generalizes
specializes
permits access
Hardware component type Hardware component type
realizes
is realized by
refines
is refined by
uses
is used by
depends
is depending
Package
is nested
nests
Package
permits access
Package
ARIS Methods
11-1142
Model Type
Source Object Type
Target Object Type
realizes
is realized by
Package
refines
is refined by
Package
uses
is used by
Package
has member
is member of
Reception
depends
is depending
UML Model
is nested
nests
UML Model
permits access
UML Model
realizes
is realized by
UML Model
refines
is refined by
UML Model
ARIS Methods
11-1143
Model Type
Source Object Type
Target Object Type
uses
is used by
UML Model
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Note Note Note Note
Association Association instance Class Collaboration instance set
Note Note Note
Component Component instance Constraint
Note Note
Hardware component Hardware component type
Note Object instance
belongs to depends
belongs to is depending
Note Association
ARIS Methods
11-1144
Model Type
Source Object Type
Target Object Type
permits access depends permits access
access is permitted by is depending access is permitted by
Association Association instance Association instance Association instance Association instance Association instance Component instance
Component instance Hardware component Hardware component
ARIS Methods
11-1145
Model Type
Source Object Type
Target Object Type
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Object instance Package
has specification depends
is specification of is depending
Hardware component type Object instance
refines uses refines
is refined by is used by is refined by
Object instance Object instance Component
Package
depends
is depending
ARIS Methods
11-1146
Model Type
Source Object Type
Target Object Type
Package
permits access
Package
realizes
is realized by
UML Deployment diagram UML Deployment diagram UML Deployment diagram UML Deployment diagram
Package
refines
is refined by
Package
uses
is used by
UML Model
refines
is refined by
Component
UML Model
depends
is depending
UML Model
permits access
UML Model
realizes
is realized by
UML Model
refines
is refined by
ARIS Methods
11-1147
Model Type
Source Object Type
Target Object Type
UML Model
uses
is used by

Model Type Source Object Type UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram Constraint concerns is concerned by Link object Constraint has argument Constraint concerns Constraint concerns Association instance Association role Classifier role sends message receives message is concerned by is concerned by is argument of Data value Constraint Classifier role Classifier role has argument is argument of Link object has link is link of Action is connected to is connected to Action Relationship Type (active) has link Relationship Type (passive) is link of Association instance Association role Link object Target Object Type
ARIS Methods
11-1148
Model Type
Source Object Type
Target Object Type
UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram
Constraint Constraint Data value
concerns concerns realizes
is concerned by is concerned by is realized by
Object instance Subsystem instance Link object
Hardware component Interaction instance set Link object Link object
has activation bar has participating stimulus is linked with has activation bar
is activation bar of participates is linked with is activation bar of has interaction from is argument of has interaction from
Hardware component Interaction instance set Hardware component Link object
interacts with has argument interacts with
Link object Object instance Object instance Subsystem instance Subsystem instance Classifier role
Link object Link object Note
interacts with is linked with belongs to
has interaction from is linked with belongs to
ARIS Methods
11-1149
Model Type
Source Object Type
Target Object Type
UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram
Note Note Note
Collaboration instance set Constraint Interaction instance set
Note Note Note Note
Link object Note Object instance Subsystem instance
Object instance Object instance Object instance Object instance Object instance Subsystem instance
is dispatched by interacts with has activation bar interacts with interacts with has action
dispatchs has interaction from is activation bar of has interaction from has interaction from is action of
Action Link object Object instance Object instance Subsystem instance Action
ARIS Methods
11-1150
Model Type
Source Object Type
Target Object Type
UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram UML Sequence diagram
Subsystem instance Subsystem instance Subsystem instance Subsystem instance Use case instance
interacts with interacts with has activation bar interacts with has activation bar
has interaction from has interaction from is activation bar of has interaction from is activation bar of
Link object Object instance Subsystem instance Subsystem instance Use case instance

Model Type Source Object Type UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram Action sends signal has been sent Exception Action instantiate is instantiated by Class Action has argument is argument of Argument Action Relationship Type (active) contains Relationship Type (passive) is contained by Action Target Object Type
ARIS Methods
11-1151
Model Type
Source Object Type
Target Object Type
UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram
Action
calls
is called by
Function
Action
sends signal
has been sent
Signal
Class
has member
is member of
ERM attribute
Class
has member
is member of
Function
Class
has member
is member of
Reception
Classifier-instate Classifier-instate Classifier-instate Classifier-instate
generalizes
specializes
Classifier-instate
has member
is member of
ERM attribute
has member
is member of
Function
is in state
has been put in state
Function
ARIS Methods
11-1152
Model Type
Source Object Type
Target Object Type
Classifier-instate
is nested
nests
Package
Classifier-instate
is in state
has been put in state
Product/Service
Classifier-instate Classifier-instate Constraint
has member
is member of
Reception
is nested
nests
UML Model
concerns
is concerned by
Action
Constraint
concerns
is concerned by
Argument
Constraint
concerns
is concerned by
Class
Constraint
concerns
is concerned by
Classifier-instate Constraint
Constraint
concerns
is concerned by
ARIS Methods
11-1153
Model Type
Source Object Type
Target Object Type
Constraint
concerns
is concerned by
Event
Constraint
concerns
is concerned by
Function
Constraint
concerns
is concerned by
Parameter
Constraint
concerns
is concerned by
Product/Service Rule
Constraint
concerns
is concerned by
Constraint
concerns
is concerned by
Signal
Constraint
concerns
is concerned by
State machine
Event
has effect
is effect of
Action
Event
receives signal
sends signal
Exception
ARIS Methods
11-1154
Model Type
Source Object Type
Target Object Type
Event
calls
is called by
Function
Event
has parameter
is parameter of
Parameter
Event
receives signal
sends signal
Signal
Function
has submachine
is submachine of is guard of
Activity graph
Function
has guard
Constraint
Function
defers
is deferred
Event
Function
has internal transition to
is internal transition of has substate
Function
Function
is substate
Function
Function
is internal transition of
ARIS Methods
11-1155
Model Type
Source Object Type
Target Object Type
Function
Organizational unit
Function
is substate
has substate
Product/Service
Function
is internal transition of is internal transition of is submachine of is internal transition of belongs to
Programming language type Rule
Function
Function
has submachine
State machine
Function
Transport system type Action
Note
belongs to
Note
belongs to
belongs to
Argument
Note
belongs to
belongs to
Class
ARIS Methods
11-1156
Model Type
Source Object Type
Target Object Type
Note
belongs to
belongs to
Classifier-instate
Note
belongs to
belongs to
Constraint
Note
belongs to
belongs to
Event
Note
belongs to
belongs to
Function
Note
belongs to
belongs to
Note
Note
belongs to
belongs to
Parameter
Note
belongs to
belongs to
Product/Service
Note
belongs to
belongs to
Rule
Note
belongs to
belongs to
Signal
ARIS Methods
11-1157
Model Type
Source Object Type
Target Object Type
Note
belongs to
belongs to
State machine
Organizational unit
is triggered by
triggers
Event
Parameter
has type
is type of
Class
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
performs on entry performs on exit performs while in state has submachine defers
is performed on entry is performed on exit is performed while in state is submachine of is deferred
Action
Action
Action
Activity graph
Event
is substate
has substate
Function
ARIS Methods
11-1158
Model Type
Source Object Type
Target Object Type
Product/Service
Product/Service
Organizational unit
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
has internal transition to has transition to is substate
is internal transition of has transition from has substate
has internal transition to has internal transition to has transition to has submachine
is internal transition of is internal transition of has transition from is submachine of
Programming language type Rule
Rule
State machine
ARIS Methods
11-1159
Model Type
Source Object Type
Target Object Type
UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram UML Statechart diagram
Product/Service
Reception
receives signal
sends signal
Exception
Rule
is substate
has substate
Function
Rule
has transition to
has transition from has substate
Product/Service Product/Service
Rule
is substate
Rule
has transition to
has transition from is top state of
Rule
State machine
has top state
Product/Service
Assignment Relationship UML Statechart diagram
Source Object Type Product/Service
Relationship Type (active) is substate
Relationship Type (passive) has substate
Target Object Type Product/Service
ARIS Methods
11-1160

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type is nested nests UML Model is nested nests Subsystem has member is member of Reception has specification is nested supports is supported by is specification of nests Organizational unit Package Function communicates with has member communicates with is member of Function Function associates (multiple) has member is associated by (multiple) is member of ERM attribute refines is refined by generalizes specializes Application system type Application system type Association Target Object Type
ARIS Methods
11-1161
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
generalizes is nested is nested
specializes nests nests
Association Class Package
Association Association Attribute link Attribute link
is nested is nested has value originates from
nests nests is value of is origin of
Subsystem UML Model Data value ERM attribute
Attribute link Attribute link Class
has value has value associates (multiple)
is value of is value of is associated by (multiple) is associated specializes nests
Link object Object instance Association
Class Class Class
associates generalizes is nested
Class Class Class
ARIS Methods
11-1162
Model Type
Source Object Type
Target Object Type
Class Class Class
has qualifier is nested is nested
is qualifier of nests nests
ERM attribute Subsystem UML Model
concerns concerns concerns is nested
is concerned by is concerned by is concerned by nests
Application system type Association Class Class
Constraint Extension point Function
Group Organizational unit Package
ARIS Methods
11-1163
Model Type
Source Object Type
Target Object Type
concerns is nested concerns is nested
is concerned by nests is concerned by nests
Subsystem Subsystem UML Model UML Model
Constraint ERM attribute ERM attribute
concerns has specification has type
is concerned by is specification of is type of
Use case instance Class Class
ERM attribute Extension point Function
has specification refers to has behavior
is specification of is referred by is behavior of
Subsystem Extension point Activity graph
ARIS Methods
11-1164
Model Type
Source Object Type
Target Object Type
associates (multiple) is nested is nested
is associated by (multiple) nests nests
Association Association class Class
has member has extension point extend generalizes
is member of is extension point of is extended specializes
ERM attribute Extension point Function Function
has member include refines
is member of is included is refined by
is nested has parameter has specification
nests is parameter of is specification of
Package Parameter Person type
ARIS Methods
11-1165
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
has member has behavior is nested
is member of is behavior of nests
Reception State machine Subsystem
Function Function Group Group
is nested has instance associates (multiple) has member
nests is instance is associated by (multiple) is member of
UML Model Use case instance Association ERM attribute
Group Group Group
accepts carries out communicates with
is accepted by is carried out by communicates with is worked on by collaboration of
Group
contributes to
Function
UML Use case diagram
Group
decides on
is decided by
Function
ARIS Methods
11-1166
Model Type
Source Object Type
Target Object Type
Group
Function
Group Group Group
has member is IT responsible for is technically responsible for
is member of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by specializes is refined by nests
Group Group
Function Function
Group
Function
Group Group Group
generalizes refines is nested
Group Group Package
Group Group
has specification has member
is specification of is member of
Position Reception
ARIS Methods
11-1167
Model Type
Source Object Type
Target Object Type
Group Group Link object
is nested is nested has slot
nests nests is slot of
Subsystem UML Model Attribute link
Note Note Note Note
Application system type Association Class Constraint
Note Note Note
Extension point Function Group
Note Note Note
Object instance Organizational unit Package
ARIS Methods
11-1168
Model Type
Source Object Type
Target Object Type
Note Note Note
Note Note Note Object instance Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
belongs to belongs to belongs to has slot
belongs to belongs to belongs to is slot of
Subsystem UML Model Use case instance Attribute link
associates (multiple) has member accepts
is associated by (multiple) is member of is accepted by
Association ERM attribute Function
carries out communicates with contributes to
is carried out by communicates with is worked on by collaboration of
ARIS Methods
11-1169
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
decides on has consulting role in has member is IT responsible for is technically responsible for must be informed about must be informed on cancellation
is decided by is supported by consulting role of is member of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is specification of specializes
Function Function
Function
Function
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
must inform about result of has specification generalizes
Function Group Organizational unit
refines is nested
is refined by nests
Organizational unit Package
ARIS Methods
11-1170
Model Type
Source Object Type
Target Object Type
Organizational unit Organizational unit Organizational unit Organizational unit type Package
has member is nested is nested
is member of nests nests
Reception Subsystem UML Model
has consulting role in has behavior
is supported by consulting role of is behavior of
Function
Activity graph
Class Function Package
Package Parameter Person
contains has type associates (multiple)
is contained by is type of is associated by (multiple) is member of is accepted by
Person type Class Association
Person Person
has member accepts
ARIS Methods
11-1171
Model Type
Source Object Type
Target Object Type
Person Person
is decided by is supported by consulting role of is member of
Function Function
Person
has member
Function
has specification is IT responsible for is technically responsible for
is specification of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to
Person
Function
Person
Function
ARIS Methods
11-1172
Model Type
Source Object Type
Target Object Type
must inform about result of is nested generalizes
result is forwarded by nests specializes
Function Package Person
refines has member is nested is nested
is refined by is member of nests nests
Person Reception Subsystem UML Model
has specification associates (multiple) has member
is specification of is associated by (multiple) is member of
Application system type Association ERM attribute
accepts carries out communicates with
is accepted by is carried out by communicates with
ARIS Methods
11-1173
Model Type
Source Object Type
Target Object Type
Person type
contributes to
Function
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
is decided by is supported by consulting role of is member of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by nests specializes
Function Function
Person type
Function
Person type
Function
UML Use case diagram UML Use case diagram UML Use case diagram
must inform about result of is nested generalizes
Function Package Person type
ARIS Methods
11-1174
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
refines has member is nested
is refined by is member of nests
Person type Reception Subsystem
Person type Position Position Position
is nested associates (multiple) has member accepts
nests is associated by (multiple) is member of is accepted by
UML Model Association ERM attribute Function
Position
decides on
is decided by
Function
Position
Function
ARIS Methods
11-1175
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
is member of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by nests is specification of specializes
Position Position
Function Function
Position
Function
is nested has specification generalizes
Package Person Position
refines has member is nested
is refined by is member of nests
Position Reception Subsystem
ARIS Methods
11-1176
Model Type
Source Object Type
Target Object Type
UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram UML Use case diagram
Position Subsystem Subsystem
is nested associates (multiple) has powertype
nests is associated by (multiple) is powertype of
UML Model Association Class
Subsystem Subsystem Subsystem UML Model
generalizes is nested is nested is nested
specializes nests nests nests
Subsystem Subsystem UML Model Subsystem
UML Model Use case instance Use case instance
is nested has slot has flow to
nests is slot of receives flow from
UML Model Attribute link Use case instance
ARIS Methods
11-1177
Source Object Type
Target Object Type
Association Class Component
contains contains contains contains
is contained by is contained by is contained by is contained by
ERM attribute Function Note Object instance
Organizational unit Package Person type
Package
contains
is contained by
Rule
ARIS Methods
11-1178

Model Type Source Object Type Relationship Type (active) Relationship Type (passive) Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Group accepts is accepted by Function Function has output of is output of Function produces is produced by Function has output of is output of Product/Service Product/Service Technical term Function has output of Function supports is supported by is output of Package Function Function Function is predecessor of is processoriented superior is measured by is processoriented subordinate measures Key performance indicator instance Objective Function follows Application system type Cluster/Data model Function has output of is output of Cluster/Data model Function is input for supports is supported by has input of Function Function Target Object Type
ARIS Methods
11-1179
Model Type
Source Object Type
Target Object Type
Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram
Group Group
Function Function
Group Group
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is accepted by is carried out by
Function Function
Group Group
Function Function
Group
Function
Group
Function
Value-added chain diagram Value-added chain diagram Value-added chain diagram
Group Organizational unit Organizational unit
must inform about result of accepts carries out
ARIS Methods
11-1180
Model Type
Source Object Type
Target Object Type
Value-added chain diagram
Organizational unit
contributes to
Function
Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type
decides on has consulting role in is IT responsible for is technically responsible for must be informed about must be informed on cancellation must inform about result of carries out is IT responsible for is technically responsible for
is decided by is supported by consulting role of is under IT responsibility of is under technical responsibility of result is forwarded to sends information on cancellation to result is forwarded by is carried out by is under IT responsibility of is under technical responsibility of
Function Function
Function Function
Function Function
Function
ARIS Methods
11-1181
Model Type
Source Object Type
Target Object Type
Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram Value-added chain diagram
Package Package Product/Service Product/Service Product/Service Technical term
contains is input for is consumed by is input for is used by is input for
is contained by has input of consumes
has input of uses has input of
ARIS Methods
11.3 ARIS Object Types
11-1182

11.3.1
Action Definition Specifies an executable expression which leads to a change in the model state. Actions can be realized by sending a message to an object, changing an attribute value of an object or changing a relationship between instances. Symbol(s)
Object Types
Activity graph Definition Represents a specialization of the state machine serving to visualize control and object flows in the form of an activity diagram. Symbol(s)
Actor Definition An actor is an object which activates the data flowchart by creating or consuming data values. It thus represents the source or sink of the data flow and is bound to its input and output.
ARIS Methods
11-1183
Symbol(s)
Application system Definition An application system is one specimen of an application system type. A single application system can be identified by its license number, for example. A company may have several application systems (several licenses) of one application system type. Symbol(s)
Application system class Definition Similar application system types can be combined to form one application system class. The similarity can be defined regarding different classification criteria. In other words, one application system type can also be assigned to several application system classes. Symbol(s)
ARIS Methods
11-1184
Application system type Definition An application system type represents the typification of individual application systems which have exactly the same technological properties. Symbol(s)
Argument Definition Describes how a parameter value for a call of the action can be determined. Symbol(s)
Artifact Definition An artifact represents a physical unit which is required or created during the software development process. Examples for artifacts are source texts, programs and libraries. Symbol(s)
ARIS Methods
11-1185
Association Definition An association is a group of links that are equal according to their structure and semantics. Symbol(s)
Association class Definition Represents an Association that has the properties of a Class. Symbol(s)
Association instance Definition An association instance is an instance of an association. It represents links between object instances. Symbol(s)
ARIS Methods
11-1186
Association role Definition An association role is a role a participant assumes in a collaboration. It is a restricted view on the underlying association which only contains those characteristics of this association that are required within the scope of the collaboration. The association to the collaboration is realized via the ElementOwnership relationship. Symbol(s)
Attribute Definition In the relations diagram, relations and attributes are used to describe logical database schemas. An attribute describes here a property of a relation. The relation is a subset of the Cartesian product of the attribute value range. Symbol(s)
ARIS Methods
11-1187
Attribute link Definition Placeholder in an instance for the entry of an attribute value. Symbol(s)
Attribute type Definition Describes a characteristic of the item described and specifies the data type and the default value of the attribute value. Symbol(s)
Attribute type group Definition An attribute type group represents a group of ERM attributes of one entity type which are closely related in terms of semantics. This allows, for example, to group the ERM attributes of an entity type which form a secondary key to an attribute type group. Symbol(s)
ARIS Methods
11-1188
Authorization condition Definition The authorization condition object type can, for example, be found in the eEPC or PCD. It defines prerequisites that restrict the organizational units' ability to act. This means that the abilities of a person in accessing a function are specified by various conditions. Symbol(s)
Bitmap Definition The Bitmap object type points to graphics that are integrated into the current screen. The name of the object should be chosen to provide some idea of the nature of the bitmap. The path to the desired bitmap is specified in the Bitmap path attribute. Symbol(s)
Break Definition Breaks are shift calendar object types that define the time within a shift when work is not being performed. The beginning and end times of the breaks must lie within the defined shift.
ARIS Methods
11-1189
Symbol(s)
Business object Definition A business object is a complex object which can be parameterized in order to support different business processes. Symbol(s)
Button Definition A button is a screen item that can be used to execute a command. Symbol(s)
Class Definition A group of objects with similar characteristics and common relationships forms a class. Classes represent the basic structures of the field of application which is supposed to be modeled. Symbol(s)
ARIS Methods
11-1190
Classification criterion Definition The classification criterion specifies the criteria according to which the objects to be examined are to be combined. Symbol(s)
Classifier role Definition A classifier role is a role a participant assumes in a collaboration. It is a restricted view on the underlying classifier which only contains those characteristics of this classifier that are required within the scope of the collaboration. The association to the collaboration is realized via the ElementOwnership relationship. Symbol(s)
Classifier-in-state Definition Designates a classifier instance which is in a certain state. Symbol(s)
ARIS Methods
11-1191
Cluster instance Definition A cluster instance represents the creation of instances for the cluster/data model object. It represents a logical view on a collection of data objects or structures. Symbol(s)
Cluster/Data model Definition A cluster represents the logical view on a collection of entity types and relationship types of a data model that is required for the description of a complex object. Symbol(s)
ARIS Methods
11-1192
Collaboration Definition A collaboration describes how an operation or a classifier (such as a use case for example) can be realized in a specific manner via the use of classifiers and associations. Symbol(s)
Collaboration instance set Definition Designates a quantity of instances which cooperate to perform a certain task that is determined via the collaboration of this item. Symbol(s)
Column Definition In the screen diagram a geographical division of the surface into areas can be made. The resulting vertical divisions are referred to as columns. Symbol(s)
ARIS Methods
11-1193
Combo box Definition The Combo box screen item enables the user to select entries from a list and to enter text directly. Using the Field type attribute you can choose from the Standard combo box, the Drop-list combo box and the Drop-down combo box representation forms. Symbol(s)
Communication Definition The communication object type is a substantial component of the communications diagram. The type of information exchange between two organizational units is determined here. Thus, it is also automatically determined, who in a relationship exchanges information with whom. Symbol(s)
ARIS Methods
11-1194
Complex object Definition No help text is available for this object type. Symbol(s)
Complex object type Definition A complex object type represents a view of several information objects (entity and relationship types). Usually a complex object type includes at least 3 information objects. Each complex object type should be assigned with a model of the eERM type in which its data structure is described. Symbol(s)
Component Definition The component object type belongs to the UML models. It represents components that form units at the time they are compiled or linked, or during system operation, e.g., executables. Components can be contained in other components, or call other components up.
ARIS Methods
11-1195
Symbol(s)
Component instance Definition Represents the instance of a Component. Component instances exist within Node instances. Symbol(s)
Conditional section Definition Item types that are assigned to a conditional section can be integrated into the DTD if desired. To integrate the item types, the Ignore attribute of the conditional section has to be deactivated. Symbol(s)
Connector Definition A connector represents the splitting of one data flow into multiple data flows. Symbol(s)
ARIS Methods
11-1196
Constraint Definition A constraint allows constraining the value range for instance attributes. Symbol(s)
Contents Definition Symbolizes any text that is entered as content of an item. Symbol(s)
Control Definition Risk control defines the general way to eliminate or reduce risks. Symbol(s)
Cost category Definition Cost category represent a group of original vouchers of the same kind. A cost category represents allocated costs which have occurred for purposes of the same kind.
ARIS Methods
11-1197
Symbol(s)
Cost driver Definition The cost driver is the unit of measurement for the result (output) of a function, e.g., pieces, hours, etc. Symbol(s)
COT attribute Definition The COT attribute object type describes the attributes of a Complex object type. It does not represent any new information but always refers to exactly one ERM attribute of an entity type or a relationship type belonging to the complex object type. The relationship between COT attribute and ERM attribute can be created in the ERM attribute allocation diagram. Symbol(s)
ARIS Methods
11-1198
COT attribute (instance) Definition The COT attribute (Instance) object type describes a COT attribute on the instance level. In other words, situations that are described at a higher level in general are now described in greater detail here (Example: Customer -> Peter Miller). Symbol(s)
Critical factor Definition Critical factors specify the aspects which need to be considered in order to reach a particular company objective. They are allocated to the company objectives in the objective diagram. Symbol(s)
Data store Definition A data store is an object which stores data for future access. Symbol(s)
ARIS Methods
11-1199
Data value Definition Data flows link the input of one process or object with the input of another. They are modeled as objects of the Data value type between objects and in general labeled with the description of the data. The connection types in the OMT (Object Modeling Technique) functional model are more precisely described by data values, in order to better describe the details of a data flow. Symbol(s)
DBMS Definition A DBMS represents a database management system. Symbol(s)
DBMS type Definition A DBMS type represents the typification of individual database management systems (DBMS) which have exactly the same technological properties. DBMS types are usually identified by their name and the corresponding version number.
ARIS Methods
11-1200
Symbol(s)
Distribution channel Definition Describes the path by which the product reaches the customer. Symbol(s)
Documented knowledge Definition The documented knowledge object type allows you to classify knowledge contained in documents, drawings or files by topic. Symbol(s)
Domain Definition The value ranges of attributes in the relations diagram are designated as domain. A domain represents the set of all values that an attribute can have. Symbol(s)
ARIS Methods
11-1201
Domain (physical) Definition The value ranges of field contents in tables of the table diagram are called 'domain (physical)'. A domain (physical) represents the set of all values a field can have. Symbol(s)
Draft list Definition A list design represents the typification of individual lists which have similar characteristics. Similarities can be defined according to the layout structure or the structure of the list contents, for example. Symbol(s)
Element type Definition Describes the structure of a component that may occur in an XML document. Symbol(s)
ARIS Methods
11-1202
Employee variable Definition An employee variable is a placeholder for a person to be specified later which is involved in a process. Symbol(s)
Entity Definition Entities are real or abstract things that are of interest within the currently observed tasks of a company. Symbol(s)
Entity type Definition Combining similar entities in sets results in the creation of entity types. The corresponding instances are the actual entities. Entities are of the same type if they can be described by the same attributes.
ARIS Methods
11-1203
Symbol(s)
Enumeration Definition The enumeration object type is used for more detailed specification of the relation of an entity type by listing its attributes. Symbol(s)
Enumeration attribute type Definition Describes a characteristic of the described item type with the possible attribute values specified. Symbol(s)
ARIS Methods
11-1204
Enumeration list occurrence Definition Enumeration list occurrence represents a more specific description level of the enumeration. In the enumeration object type, the attributes of a relation are generally described, while the content of these attributes are described in the enumeration list occurrence. Symbol(s)
Enumeration literal Definition Defines the possible values for the current enumeration data type. Symbol(s)
ERM attribute Definition ERM attributes are characteristics which described entity types. Symbol(s)
ARIS Methods
11-1205
ERM attribute instance Definition ERM attribute instances describe an entity or a relationship. Symbol(s)
ERM domain Definition The set of values which an ERM attribute may have is called ERM domain. Symbol(s)
Event Definition An event represents a state that is relevant in terms of business management and which influences or controls the further flow of one or more business processes. Changes in state are reflected in the changes of status of the relevant environment data (information objects). Events trigger functions and are results of functions. As opposed to a function which represents a timeconsuming process, an event occurs at one point in time. Symbol(s)
ARIS Methods
11-1206
Event instance Definition A event instance is an event which occurs in a specific process instance. An event instance can be evaluated, i.e. it can be true or false. Symbol(s)
Exception Definition A signal that is triggered by a behavioral feature (Operation and Reception) as a result of an error is an exception. Symbol(s)
Extension point Definition Refers to one or more locations where the current use case may be extended. Symbol(s)
ARIS Methods
11-1207
Field Definition The logical structure of database systems can be described by tables and the corresponding fields of a table. Fields define the logical contents of a table. The possible values of a field can be defined by assigning a domain (physical). Symbol(s)
Field (specimen) Definition A field (specimen) is one specimen of a field. Tables and fields define the logical structure of a database management system. Several specimens of the logically defined tables and fields with exactly the same structure can exist in one company. Symbol(s)
ARIS Methods
11-1208
Filter object type Definition A filter object type is a division criterion in the distribution model which sets the criteria for a function type on how often it can be repeatedly used in the system. Symbol(s)
ARIS Methods
11-1209
Function Definition A function is the technical task or activity performed on an object in order to support one or several business objectives. Symbol(s)
ARIS Methods
11-1210
Function instance Definition A function instance is a function which occurs in a specific process instance. This function instance can be assigned unique start and end times as well as other necessary attributes. Symbol(s)
General resource Definition A general resource is a resource that does not need to be a person or an operating resource and is not explicitly defined. The general resource allows performing processes. Symbol(s)
Generalization type Definition During the generalization process, the similarity between objects (entities) is recognized. These objects are then combined to form a superior object type. Symbol(s)
ARIS Methods
11-1211
Graphical user interface type Definition A graphical user interface type represents the typification of individual graphical user interfaces which have exactly the same properties. Application system types are realized on the basis of specific user interface types. Graphical user interface types are usually identified by their name and the version number. Symbol(s)
Group Definition A group may represent a group of employees (persons) which are working together for a specific period of time (project group), for example. Symbol(s)
ARIS Methods
11-1212
Hardware component Definition Hardware components are specimen of different hardware component types that are available in a company in order to operate properly on the IT level. Hardware components are often identified by assigned inventory numbers (e.g. inventory number of a data processing equipment). Symbol(s)
Hardware component class Definition Similar hardware component types can be combined to form a hardware component class. The similarity can be defined according to different classification criteria. In other words, one hardware component type can also be assigned to several hardware component classes. Symbol(s)
Hardware component type Definition A hardware component type represents the typification of individual hardware components which have exactly the same technological properties.
ARIS Methods
11-1213
Symbol(s)
Improvement potential Definition Describes weak points in the processes or areas that are to be examined in greater detail during Change Management to identify measures for process optimization. Symbol(s)
Index Definition An index allows sorting field contents of a table according to different criteria in order to access the field contents expediently and efficiently. In the table diagram, indices can be assigned to the fields of a table. Symbol(s)
Information carrier Definition An information carrier represents a means to store information. This may be accomplished in the form of card files, forms or files on a computer.
ARIS Methods
11-1214
Symbol(s)
ARIS Methods
11-1215
nformation flow Definition The information flow is an object containing the information that, for example, is forwarded between the function and und application system type object types or between the module and IT function type object types. It is used for more precise specification of the connections between these objects, thus it represents the data that are exchanged. Symbol(s) 385
Instantiation cycle Definition The object type instantiation cycle belongs to the model type process instantiation model and defines the medium object level for the description of repeating instantiation interval sequences. Example of the contents of an instantiation cycle: 'For a defined process, which in the instance specifies the events on a workday, the cycle is Mo - Fr.' Symbol(s)
ARIS Methods
11-1216
Instantiation interval Definition The object type instantiation interval belongs to the model type process instantiation model and defines the lowest object level for the description of small time periods during the process cycle. Elements are the relative interval start, the interval duration, the number of process instances, the distribution of the processes to be performed, the cyclical repetition and the periods. Example of the contents of an instantiation interval: 'For a defined process, at the beginning of a workday at 8:00 50 processes are started with equal distribution.' Symbol(s)
Instantiation plan Definition The object type instantiation plan belongs to the model type process instantiation model and represents the upper object level for the description of several instantiation cylces. Example of the contents of an instantiation plan: 'For a defined process, which in the cycle specifies the events of a week, the instantiation plan is the yearly work schedule.' Symbol(s)
ARIS Methods
11-1217
Interaction instance set Definition Designates a group of stimuli which participate in a Collaboration instance set to perform a specific task there. Symbol(s)
IT function Definition An IT function is one specimen of an IT function type. In a company, several specimen (IT functions) of one IT function type may be implemented. Usually, they are not identified by themselves, but rather by the license number of the modules that are in operation and to which they are assigned. Symbol(s)
IT function class Definition Similar IT function types can be combined to form a IT function class. The similarity can be defined regarding different classification criteria. Hence, one IT function type can be assigned to several IT function classes. Symbol(s)
ARIS Methods
11-1218
IT function type Definition In terms of a transaction, IT function types are the smallest units of a module type. They are realized as individual program modules and need to be executed as a whole in order to accomplish one processing step. A IT function type represents the typification of individual IT functions which have exactly the same technological properties. Symbol(s)
Key performance indicator instance Definition A key performance indicator instance is an indicator or a key indicator for measuring a degree of goal accomplishment. It can contain a plan value, an actual value and a target value. Symbol(s)
Knowledge category Definition A knowledge category is used to classify knowledge by topic. Symbol(s)
ARIS Methods
11-1219
Layout Definition The layout object type assigns representation properties to the objects screen, page, section, column, screen table, COT attribute and text. Symbol(s)
Link object Definition Represents the instance of an association class. Symbol(s)
List Definition Lists and screens represent the interfaces between users and application systems. A list visualizes the procedure of data input or data output as used by an application system. As opposed to a list design which defines a common structure for several similar lists in the sense of a list type, a list is the concrete instance of the list design. Symbol(s)
ARIS Methods
11-1220
List control Definition A list control displays a set of items. An icon precedes the name of each item so that items of the same type can be recognized. The items can either be displayed as large icons, small icons, in a list or in a detail view. Symbol(s)
Location Definition Locations specify the physical positions of organizational units, positions or specimen of hardware components and technical resources of a company. They may refer to - a region - a city - a plant - a building - a room - or an individual workstation. Symbol(s)
Loop start Definition The loop start object type belongs to the program flow chart (PF) model. It defines the beginning of a sequence of several processing steps. This sequence is completed by a loop end. It is characteristic that this flow scheme is repeated several times.
ARIS Methods
11-1221
Symbol(s)
Main process Definition The main process represents the main functions in the function trees to which the processes (functions from the scenario processes) are allocated. Symbol(s)
Marketing instrument Definition Describes activities/instruments that are used for market organization. Symbol(s)
Material class Definition Similar material types can be combined to form an operating resource class. The similarity can be defined according to different classification criteria. In other words, one material type can also be assigned to several material classes. Symbol(s)
ARIS Methods
11-1222
Material flow Definition Material flow is an object which contains information about materials that are transferred between two functions in a material flow diagram. It is used for more precise specification of the connections between the materials being transferred. Symbol(s)
Material type Definition A material type represents the typification of individual materials which have exactly the same material characteristics. Symbol(s)
Measurement unit Definition No help text is available for this object type. Symbol(s)
ARIS Methods
11-1223
Measurement unit number Definition No help text is available for this object type. Symbol(s)
Memory location Definition In a memory location, data are stored as tables or fields. Symbol(s)
Message flow Definition Message flow is an object containing the precise kind of messages that are forwarded between the object types. It is used for more precise specification of the connections in order to describe the messages transferred by the connections in detail. Symbol(s)
ARIS Methods
11-1224
Message type Definition A message type classifies the messages which flow between distributed systems according to the data and processes involved. Symbol(s)
Module Definition A module is one specimen of a module type. A single module can be identified by its license number, for example. A company may have several modules (several licenses) of one module type. Symbol(s)
Module class Definition Similar module types can be combined to form a module class. The similarity can be defined according to different classification criteria. In other words, one module type can also be assigned to several module classes. Symbol(s)
ARIS Methods
11-1225
Module type Definition A module type represents a part of an application system type which can be executed on its own. A module type represents the typification of individual modules which have exactly the same technological properties. Symbol(s)
Need Definition Describes a person's feeling of deficiency, which is to be dispelled. A need stands at the beginning of a purchasing decision process. If the person is faced with a product that is likely to satisfy his need, a demand arises. Symbol(s)
Network Definition Networks are specimen of different network types that are available in a company in order to operate properly on the IT level. Networks are often identified by assigning unique location identifiers or inventory numbers.
ARIS Methods
11-1226
Symbol(s)
Network class Definition Similar network types can be combined to form a network class. The similarity can be defined according to different classification criteria. In other words, one network type can also be assigned to several network classes. Symbol(s)
Network connection Definition Network connections are specimen of different network connection types that are available in a company in order to operate properly on the IT level. Network connections link network nodes to one another. Symbol(s)
ARIS Methods
11-1227
Network connection type Definition A network connection type represents the typification of network connections which have exactly the same technological properties. Symbol(s)
Network node Definition Network nodes are specimen of different network node types that are available in a company in order to operate properly on the IT level In this case, one network node represents one access point to a network to which hardware components can be connected. Symbol(s)
Network node type Definition A network node type represents the typification of individual network nodes which have exactly the same technological properties. Symbol(s)
ARIS Methods
11-1228
Network protocol Definition A network protocol represents a standardized communication and information exchange method of application systems in networks. The network protocols used in a network can be specified for each network type. Symbol(s)
Network type Definition A network type represents the typification of individual networks (information system networks) which have exactly the same technological properties. Symbol(s)
Note Definition The object type note belongs to the UML models. It offers the option of attaching notes to objects. Symbol(s)
ARIS Methods
11-1229
Object instance Definition An object instance is a concrete instance of an object, i.e. a specimen of an object with specified values. Symbol(s)
Object type class Definition An object type class classifies functions. The functions which are to be examined according to a specified classification criterion are allocated to an object type class. Symbol(s)
Objective Definition An objective is the definition of future company goals which are supposed to be reached by supporting the critical factors and realizing new business processes. Symbol(s)
ARIS Methods
11-1230
Operating resource Definition Operating resources are specimens of different operating resource types that are available in a company in order to operate properly. Operating resources are often identified by assigned inventory numbers (e.g. inventory number of a machine). Symbol(s)
Operating resource class Definition Similar operating resource types can be combined to form an operating resource class. The similarity can be defined regarding different classification criteria. Hence, one operating resource type can also be assigned to several operating resource classes. Symbol(s)
Operating resource type Definition An operating resource type represents the typification of operating resources which have exactly the same technological properties.
ARIS Methods
11-1231
Symbol(s)
Operating system Definition The operating system object type supports the determination of the technological base for application system types and module types. Several object types of this category can be connected to one application system type. For example, an application system can be operative with the operating system Windows 3.1 and Windows NT. Symbol(s)
Operating system type Definition An operating system type represents the typification of individual operating systems which have exactly the same technological properties. Operating system types are usually identified by their name and the corresponding version number. Symbol(s)
ARIS Methods
11-1232
Operation Definition Operations (operational methods) represent functionalities or transformations which are assigned to a class. Symbol(s)
Organizational chart Definition An organizational chart represents a cluster of organizational relationships at a high level of abstraction. Symbol(s)
Organizational level Definition Organizational structures are usually represented in organizational charts. The structural criterion is the operation principle, in other words, areas in a company that perform the same operations are combined to form an organizational unit. Additionally, large companies are structured in different (organizational) levels which, among other things, serve the purpose of assigning responsibilities and authorizations. Examples for organizational levels: - 'Product area' 'Operation' - 'Operation area' - etc.
ARIS Methods
11-1233
Symbol(s)
Organizational unit Definition Organizational units are the performers of the tasks required to attain the business objectives. Symbol(s)
Organizational unit type Definition An organizational unit type represents the typification of individual organizational units which have exactly the same characteristics. These characteristics may refer to similar authorizations and responsibilities, for example. All departments and sub-departments of a company, for example, have to follow rules and relationships which - in case a corresponding type exists - need to be defined only once.
ARIS Methods
11-1234
Symbol(s)
Package Definition A package is an object type that derives from the UML models. It is used to divide model elements by arranging components into groups and assigning them to specific packages. In the EPC a package displays input and output relationships of functions at a rough or fine level of detail, i.e. it only represents the generation or use of information. A package does not have a write or read function. Symbol(s)
Packaging material class Definition Similar packaging material types can be combined to form a packaging materials class. The similarity can be defined according to different classification criteria. In other words, one packaging material type can also be assigned to several packaging material classes.
ARIS Methods
11-1235
Symbol(s)
Packaging material type Definition A packaging material type represents the typification of individual packaging materials which have exactly the same characteristics (e.g. material characteristics). Symbol(s)
Page Definition The pageobject type belongs to the screen diagram model type. A screen can feature several tabs. These are referred to as pages. Symbol(s)
Parameter Definition No help text is available for this object type. Symbol(s)
ARIS Methods
11-1236
Partition Definition Utility serving to divide the individual states of an activity graph into groups. Symbol(s)
Performance characteristic Definition No help text is available for this object type. Symbol(s)
Person Definition Persons are employees of a company and can be identified by their individual personnel number. Persons can be assigned to the organizational units to which they belong and to the functions they perform or for which they are responsible. Symbol(s)
ARIS Methods
11-1237
Person type Definition A person type (employee type) represents the typification of individual persons which have the same characteristics. These characteristics may refer to similar authorizations and responsibilities, for example. Department heads or foremen, for example, have to follow rules and fulfill responsibilities which - in case a corresponding type exists - need to be defined only once. Symbol(s)
Perspective Definition Perspectives are the views by which a company can be looked at during strategic business planning. Symbol(s)
ARIS Methods
11-1238
Position Definition The smallest organizational unit in a company is a position. It is assigned to employees (persons). In general, the authorizations and responsibilities of a position are defined in position description. Symbol(s)
Process Definition A process represents a function which transforms data values. The result of a process depends on the behavior of the whole system. Symbol(s)
ARIS Methods
11-1239
Product/Service Definition A product/service is performed in the course of a value-added process. It is the result of a human act or a technical process. A product/service can represent either a service or a product. Products can be a material type, operating resource type, technical operating supply type or a packaging material type. The trigger for the creation of a product/service is always the requirements of an organizational unit or of a customer. Symbol(s)
ARIS Methods
11-1240
Program library Definition A program library contains programs and/or program modules which are necessary for creating or performing a task. Symbol(s)
Program module Definition A program module is a program file on a storage medium (e.g. EXE file or COM file) which has been acquired by purchasing a license. In general, it can be identified by means of a license number. Symbol(s)
Program module type Definition A program module type represents the typification of individual program modules which have exactly the same technological properties. Symbol(s)
ARIS Methods
11-1241
Programming language Definition A programming language provides a set of commands as well as a syntax and allows creating programs. In general, it can be identified by a license number. Symbol(s)
Quick object Definition Supports modeling without any method restriction in Quick model model types.
ARIS Methods
11-1242
Symbol(s)
ARIS Methods
11-1243
Radio button/Check box Definition Depending on the value set in the Field type attribute, this screen item can be used either as an option box or as a check box. If you wish to offer the user a given set of options, from which he is to select exactly one option, each option is represented as an option button on the screen. If you wish to offer the user a given set of options, from which he is to select several options, each of these options is shown as a check box. Symbol(s)
Reception Definition Describes the ability of a classifier to receive and process a certain signal. Receptions are modeled and represented like operations, having the signal prefix in addition. Symbol(s)
Relation Definition A relation describes an entity type by its attributes. It is a subset of all possible combinations of the attribute value ranges.
ARIS Methods
11-1244
Symbol(s)
Relationship Definition A relationship is a logical link between entities. Similar relationships can be combined to form a relationship type. Symbol(s)
Relationship type Definition A relationship is a logical link between entities. Combining similar relationships to sets results in the creation of relationship types. Relationships are of the same type if they can be described by the same attributes. Symbol(s)
Risk Definition A risk represents the possible danger that a set process objective will not be achieved. Symbol(s)
ARIS Methods
11-1245
Rule Definition Rules represent logic operators which allow specifying the logical links that exist between events and functions in process chains, for example. Symbol(s)
Rule instance Definition Rule instances represent the operators at instance level. They can specify the logic link between function and event instances.
ARIS Methods
11-1246
Symbol(s)
Screen Definition Lists and screens represent the interfaces between users and application systems. A screen visualizes the procedure of data input or data output as used by an application system. As opposed to a screen design which defines a common structure for several similar screens in the sense of a screen type, a screen is the concrete instance of the screen design. Symbol(s)
ARIS Methods
11-1247
Screen design Definition A screen design represents the typification of individual screens which have similar characteristics. Similarities can be defined according to the layout structure or the contents of screens, for example. Symbol(s)
ARIS Methods
11-1248
Screen table Definition Using a screen table, you can represent polyvalent functionally dependent attributes of a Complex object type in one screen. The screen table can be used, for example, if your customer base contains customers for whom several addresses (e.g. for several locations) are managed. This means that the Country, Zip code, City, Street and Street no. attributes functionally depend on the Customer no. key attribute in a polyvalent way. Since a table can itself extend over several pages (cf. for example Excel) the is divided into connection type between screen table and Page@ is available in the Screen diagram. A page in a screen table may not be subdivided using the Section and Column object types. Only COT attributes may be assigned to a page in a screen table; these are converted into columns on the table page. Symbol(s)
Section Definition In the screen diagram a geographical division of the surface into areas can be made. The resulting rows are referred to as sections.
ARIS Methods
11-1249
Symbol(s)
Security protocol Definition No help text is available for this object type. Symbol(s)
Separator Definition No help text is available for this object type. Symbol(s)
Sequence Definition Item types that are assigned to the item type described via a sequence connector have to be entered in a specific order into the item. The order is maintained in the Sequence attribute of the connections that lead from the item types to the connector. Symbol(s)
ARIS Methods
11-1250
Shift Definition Shifts are shift calendar object types. A shift is a defined interval of time during which a personnel resource works each day or during which a material resource is available to perform functions. This object type can depict early and late shifts, day and night shifts, etc. If a shift within a shift calendar is not assigned to any shift cycle, the shift will automatically restart every 24 hours during a simulation run. Interruptions of work during a shift are depicted using breaks. Symbol(s)
Shift cycle Definition Shift cycles are shift calendar object types that define the validity of shifts. This is where you specify the days a particular shift will run. It is possible to create one-week or two-week shift cycles. Symbol(s)
ARIS Methods
11-1251
Shift plan Definition Shift plans are shift calendar object types. A shift plan summarizes various shift cycles. For example, the shift plan describes which shift cycles repeat and when they repeat. You can use this feature to specify the sequence of early, late, and special shifts. Symbol(s)
Signal Definition Signals are classifiers that are exchanged between instances in the form of asynchronous messages. The signal recipient processes the signals using a state machine. Symbol(s)
Solution Definition A solution represents the implementation of risk control concerning a risk. Symbol(s)
ARIS Methods
11-1252
Sp./gen. operator Definition The Sp./Gen. operator (specialization/generalization operator) divides/combines similar classes. Symbol(s)
Spin box Definition A spinbox is a screen item that is used in combination with a Text box, in which a value can be entered from a list of discrete, sorted values. The association of text and spin box is controlled by the Tabindex attribute. The user can enter the required value either directly into the text box or he can use arrow keys on the spin box to increase a displayed numerical value by a fixed increment, or he can 'scroll cyclically through' a list of preset values. If you scroll through the list and come to the last value, another click on the up arrow will display the first value on the list again. In the same way, when scrolling with the down arrow, after the first value on the list you go back to the last. Symbol(s)
ARIS Methods
11-1253
State Definition A state is a group of sets of values. The state describes the reaction of an object to an arriving event. Symbol(s)
State machine Definition Represents a state machine. It always describes all possible behaviors of a model item. A Statechart diagram always visualizes exactly one state machine. Symbol(s)
Strategy Definition No help text is available for this object type. Symbol(s)
Structural element Definition Structural elements are used to structure models according to different viewpoints, e.g., ISO 900x.
ARIS Methods
11-1254
Symbol(s)
Subsystem Definition Represents a grouping of model items that form a behavioral unit in a physical system. Symbol(s)
Subsystem instance Definition Symbol(s) Represents the instance of a Subsystem.
System attribute Definition System attributes describe objects for tasks which are related to the export of data. They illustrate and manage interface-oriented data. The representation of primary keys, foreign keys, mandatory fields and descriptive fields is possible. Symbol(s)
ARIS Methods
11-1255
System attribute domain Definition A system attribute domain describes the allowed value range for system attributes. Symbol(s)
System organizational unit Definition Integrated Application systems contain organizational structures which must be taken into account when introducing such a system into a company. These organizational structures can be modeled using the System organizational unit object type. Symbol(s)
System organizational unit type Definition A system organizational unit type represents the typification of individual system organizational units which have the same characteristics. These characteristics may pertain to similar authorizations in an application system, for example. Symbol(s)
ARIS Methods
11-1256
Table Definition The logical structure of database systems can be described by tables and the corresponding fields of a table. A table represents the typification of individual tables (specimen) which have exactly the same logical structure. Symbol(s)
Tables (specimen) Definition A table (specimen) is one specimen of a table. Tables and fields define the logical structure of a database management system. Several specimen of the logically defined tables and fields with exactly the same structure can exist in one company. Symbol(s)
Tech. operating supply class Definition Similar tech. operating supply types can be combined to form a tech. operating supply class. The similarity can be defined according to different classification criteria. Hence, one technical operating supply type can also be assigned to several technical operating supply classes.
ARIS Methods
11-1257
Symbol(s)
Technical operating supply Definition A technical operating supply is a specimen of a technical operating supply type. In general, it can be identified by means of an inventory number. Symbol(s)
Technical operating supply type Definition A tech. operating supply type represents the typification of techn. operating supplies which have exactly the same technological properties. Symbol(s)
Technical term Definition Technical terms represent the concepts that exist in a company and have the task of describing the observed information objects. Symbol(s)
ARIS Methods
11-1258
Technical terms instance Definition Technical term instances represent the instance level of a technical term. Symbol(s)
Text Definition Text object types contain explanations that are displayed as static text in the current screen. The name of the object should be chosen to provide some idea of the content of the text. The text to be displayed is maintained in the Full name attribute. Symbol(s)
Text box Definition A text box is a screen item in which the user can enter text or in which he can edit displayed text. You can specify the text box more precisely using the Field type attribute type. If the text box is used as a standard or rich text box, you can use the Encoded attribute to specify whether asterisks are displayed instead of the entered text, as is usual for example when entering passwords.
ARIS Methods
11-1259
Symbol(s)
Tool Definition Describes software, methods or continual training that are being used within the current process or that are to be used to improve the processes and the integration into the entire systematics. Symbol(s)
Transaction folder Definition Symbol(s) No help text available.
ARIS Methods
11-1260
Transport system Definition A transport system is one specimen of a transport system type. In general, it can be identified by means of an inventory number or a plant number. Symbol(s)
Transport system class Definition Similar transport system types can be combined to form a transport system class. The similarity can be defined according to different classification criteria. Hence, one transport system type can also be assigned to several transport system classes. Symbol(s)
Transport system type Definition A transport system type represents the typification of transport systems which have exactly the same technological properties. Symbol(s)
ARIS Methods
11-1261
Tree control Definition A tree control displays a set of items in their hierarchical structure (in the form of a tree). You can put buttons on items within the control. The buttons can be used to open views of the subordinate items. You can also show lines in order to emphasize the hierarchical structures, and have check boxes precede the individual items. Symbol(s)
UML Model Definition Represents an abstracted view on a physical system. Symbol(s)
Use case instance Definition Specifies the instance of a use case which can also be called scenario. Symbol(s)
ARIS Methods
11-1262
View Definition A view represents a logical view on a collection of relations and attributes. Symbol(s)
View (physical) Definition A view (physical) represents a logical view on a collection of tables and fields. Symbol(s)
Warehouse equipment Definition Warehouse equipment items are specimen of different warehouse equipment types that are available in a company in order to operate properly. Warehouse equipment items are often identified by assigned warehouse numbers. Symbol(s)
ARIS Methods
11-1263
Warehouse equipment class Definition Similar warehouse equipment types can be combined to form a warehouse equipment class. The similarity can be defined according to different classification criteria. Hence, one warehouse equipment type can also be assigned to several warehouse equipment classes. Symbol(s)
Warehouse equipment type Definition A warehouse equipment type represents the typification of individual warehouse equipments which have exactly the same technological properties. Symbol(s)
XOR Definition Only one of the item types that are assigned to the item type described via an XOR connector may occur within an item. Symbol(s)
ARIS Methods
11.3.2 Object Type Specific Attribute Types
11-1264
11.3.2 Object Type Specific Attribute Types 11.3.2.1 Action

Action Action Action Action Action Action Action Action Name Recurrence Recurrence language Script Script language Target Target language Stereotype
11.3.2.2 Activity graph

Activity graph Activity graph Name Stereotype
11.3.2.3 Actor
Actor Name
11.3.2.4 Application system

Application system Application system Application system Application system Name External Internal Data management system
ARIS Methods
11-1265
Operating system License number
11.3.2.5 Application system class

Application system class Name
11.3.2.6 Application system type

Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Name Manufacturer Release External Internal Installation status Scheduled from Scheduled until Realized from Realized until In use since Development effort Development effort (estimated) Development costs Development costs (estimated) Current cost for computer center Computer center (CC) costs Acquisition costs
ARIS Methods
11-1266
Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system type
Costs per unit Frequency of execution No. of occurrences - avg. Quality of specialist support Workflow Parameter list WPDL-external attribute list ARIS Applications Internal name Doc requirements definition Doc development Shortcut In the toolbar Icon path Status bar Quick help Caption Transaction code SAP Server IsRoot IsLeaf IsAbstract Stereotype IsPersistent UML Actor Customizing view
ARIS Methods
11-1267
Customizing transaction
11.3.2.7 Argument
Argument Argument Argument Argument Name Value Value language Stereotype
11.3.2.8 Artifact
Artifact Artifact Artifact Artifact Artifact Artifact Name IsRoot IsLeaf IsAbstract IsPersistent Stereotype
11.3.2.9 Association
Association Association Association Association Association Association Association Name Derived Stereotype Constraint IsRoot IsLeaf IsAbstract
ARIS Methods
11-1268
Association
IsPersistent
11.3.2.10 Association class

Association class Association class Association class Association class Association class Association class Association class Association class Name IsRoot IsLeaf IsAbstract Stereotype IsPersistent Derived IsActive
11.3.2.11 Association instance

Association instance Association instance Association instance Association instance Association instance Name Default (import) Derived IsPersistent Stereotype
11.3.2.12 Association role

Association role Association role Association role Association role Name Derived Stereotype IsRoot
ARIS Methods
11-1269
Association role Association role Association role
IsLeaf IsAbstract IsPersistent
11.3.2.13 Attribute
Attribute Attribute Attribute Attribute Attribute Name Quantity structure Throughput/avg. access Quality of specialist support Relevance to data protection act
11.3.2.14 Attribute link

Attribute link Attribute link Name Stereotype
11.3.2.15 Attribute type

Attribute type Attribute type Attribute type Attribute type Name Data type Default value Attribute default
11.3.2.16 Attribute type group

Attribute type group Name
ARIS Methods
11-1270
Attribute type group Attribute type group Attribute type group Attribute type group
Secondary key Default (import) ARIS Applications Internal name
11.3.2.17 Authorization condition

Authorization condition Authorization condition Authorization condition Name Condition Type
11.3.2.18 Bitmap
Bitmap Bitmap Bitmap Name Bitmap path Hyperlink
11.3.2.19 Break
Break Break Break Break Name Simulation Break start Break duration
11.3.2.20 Business object

Business object Name
ARIS Methods
11-1271
Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object Business object
Synonyms Transmission type Transmission type, manually Transmission type, batch Transmission type, online Storage type Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend SQL name Release Attributes of external system External ID SAP development class Text Default (import) Workflow Data type Object access ID Template Default name ARIS Applications
ARIS Methods
11-1272
Business object Business object Business object Business object
Internal name Doc requirements definition Doc development SAP Attributes
11.3.2.21 Button
Button Button Name Tabindex
11.3.2.22 Class
Class Class Class Class Class Class Class Class Class Class Class Class Class Class Class Name Derived Constraint IsRoot IsLeaf IsAbstract Stereotype Visibility Type Complexity Space Session mode Concurrency Disabled IsStatic
ARIS Methods
11-1273
Class Class
IsPersistent IsActive
11.3.2.23 Classification criterion

Classification criterion Name
11.3.2.24 Classifier role

Classifier role Classifier role Classifier role Classifier role Classifier role Classifier role Name IsRoot IsLeaf IsAbstract IsPersistent Stereotype
11.3.2.25 Classifier-in-state
Classifier-in-state Classifier-in-state Classifier-in-state Classifier-in-state Classifier-in-state Classifier-in-state Name IsRoot IsLeaf IsAbstract IsPersistent Stereotype
11.3.2.26 Cluster instance

Cluster instance Name
ARIS Methods
11-1274
Cluster instance
Default (import)
11.3.2.27 Cluster/Data model

Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Name Synonyms Transmission type Transmission type, manually Transmission type, batch Transmission type, online Storage type Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend SQL name Release Text Default (import) ARIS Applications Internal name Doc requirements definition Doc development
ARIS Methods
11-1275
11.3.2.28 Collaboration
Collaboration Collaboration Name Stereotype
11.3.2.29 Collaboration instance set

Collaboration instance set Collaboration instance set Name Stereotype
11.3.2.30 Column
Column Name
11.3.2.31 Combo box

Combo box Combo box Combo box Name Field type Tabindex
11.3.2.32 Communication
Communication Communication Communication Communication Communication Communication Name Default (import) Attributes of external system External ID SAP development class SAP Attributes
ARIS Methods
11-1276
11.3.2.33 Complex object

Complex object Name
11.3.2.34 Complex object type

Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Complex object type Name ARIS Applications Internal name Doc requirements definition Doc development Hidden Standard COT
11.3.2.35 Component
Component Component Component Component Component Component Name Stereotype IsRoot IsLeaf IsAbstract IsPersistent
11.3.2.36 Component instance

Component instance Component instance Name IsPersistent
ARIS Methods
11-1277
Component instance
Stereotype
11.3.2.37 Conditional section

Conditional section Conditional section Name Ignore
11.3.2.38 Connector
Connector Connector Name Default (import)
11.3.2.39 Constraint
Constraint Constraint Constraint Constraint Name Language Body Stereotype
11.3.2.40 Contents
Contents Name
ARIS Methods
11-1278
11.3.2.41 Control
Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Name Synonyms Origin System-internal System-external Company-internal Company-external Event classification Trigger Condition Type of origin Frequency Frequency, daily Frequency, weekly Frequency, monthly Frequency, annually Release Workflow Communication channel Parameter list Keyword Milestone ID Probability Business control
ARIS Methods
11-1279
Control Control
Central control code Local control code
11.3.2.42 Cost category

Cost category Cost category Cost category Cost category Cost category Name Default (import) Cost category No. Cost category type Performance scale
11.3.2.43 Cost driver

Cost driver Cost driver Name CD Number
11.3.2.44 COT attribute

COT attribute COT attribute COT attribute COT attribute COT attribute COT attribute COT attribute COT attribute COT attribute Name Workflow Data type Instance value ARIS Applications Internal name Doc requirements definition Doc development Search attribute
ARIS Methods
11-1280
11.3.2.45 COT attribute (instance)

COT attribute (instance) COT attribute (instance) COT attribute (instance) COT attribute (instance) Name Workflow Data type Instance value
11.3.2.46 Critical factor

Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Critical factor Name SQL name Default (import) Balanced Scorecard Actual time period Minimum value Maximum value Plan value Tolerance range Actual value Achievement of objectives Target time period Target value Unit BSC - Remark/Example End date
ARIS Methods
11-1281
11.3.2.47 Data store

Data store Name
11.3.2.48 Data value

Data value Data value Data value Name IsPersistent Stereotype
11.3.2.49 DBMS
DBMS DBMS Name License number
11.3.2.50 DBMS type

DBMS type DBMS type DBMS type DBMS type DBMS type Name Manufacturer Release Acquisition costs Costs per unit
11.3.2.51 Distribution channel

Distribution channel Name
ARIS Methods
11-1282
11.3.2.52 Documented knowledge

Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Documented knowledge Name Updating frequency Significance Degree of coverage Knowledge advantage Knowledge usage Desired degree of coverage Future significance Structural change speed
11.3.2.53 Domain
Domain Domain Domain Name Domain type Length
11.3.2.54 Domain (physical)

Domain (physical) Domain (physical) Domain (physical) Name Domain type Length
11.3.2.55 Draft list

Draft list Name
ARIS Methods
11-1283
11.3.2.56 Element type

Element type Name
11.3.2.57 Employee variable

Employee variable Employee variable Employee variable Name Default (import) Role
11.3.2.58 Entity
Entity Entity Entity Entity Entity Entity Entity Entity Entity Name Default (import) Workflow Data type Last modification date Creation date Object access ID Template Default name
11.3.2.59 Entity type

Entity type Entity type Entity type Name Synonyms Application
ARIS Methods
11-1284
Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type
Integrity conditions Transmission type Transmission type, online Transmission type, batch Transmission type, manually Storage type Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend Release SQL name Attributes of external system External ID SAP development class Text Default (import) Workflow Data type Object access ID Template Default name WPDL-external attribute list
ARIS Methods
11-1285
Entity type Entity type Entity type Entity type Entity type Entity type Entity type
ARIS Applications Internal name Doc requirements definition Doc development Hidden Transient SAP Attributes
11.3.2.60 Enumeration
Enumeration Enumeration Enumeration Enumeration Enumeration Enumeration Name Length ARIS Applications Internal name Doc requirements definition Doc development
11.3.2.61 Enumeration attribute type

Enumeration attribute type Enumeration attribute type Enumeration attribute type Enumeration attribute type Name Notation Default value Attribute default
ARIS Methods
11-1286
11.3.2.62 Enumeration list occurrence

Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Enumeration list occurrence Name Ordinal Short text Descriptive text ARIS Applications Internal name Doc requirements definition Doc development
11.3.2.63 Enumeration literal

Enumeration literal Enumeration literal Name Stereotype
11.3.2.64 ERM attribute

ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute Name Synonyms Length Secondary key Integrity conditions Decimal places Transmission type Transmission type, online Transmission type, batch
ARIS Methods
11-1287
ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute
Transmission type, manually Storage type Multiple value tag Derived attribute type Derived attribute Description of attribute derivation Safety class of specimens Optional attribute Data type operations Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend SQL name Text Default (import) Workflow Data type Instance value WPDL-external attribute list ARIS Applications Internal name Doc requirements definition
ARIS Methods
11-1288
ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute ERM attribute
Doc development Search attribute Default value Evaluation Value Value (numeric) Value (logical) IsRoot Class attribute IsLeaf IsAbstract IsPersistent Derived Stereotype Type Initial value Initial value language Simulation Upper limit Lower limit Visibility Containment Static Default value IsVolatile Changeability
ARIS Methods
11-1289
ERM attribute ERM attribute
IsOrdered (Src) UML Attribute
11.3.2.65 ERM attribute instance

ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance ERM attribute instance Name Default (import) Workflow Data type Instance value Last modification date Creation date
11.3.2.66 ERM domain

ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain ERM domain Name Domain type Data type operations Specification Length Decimal places SQL name ARIS Applications Internal name Doc requirements definition Doc development Upper limit
ARIS Methods
11-1290
ERM domain ERM domain ERM domain
Lower limit Data type Default value
11.3.2.67 Event
Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Name Synonyms Origin System-internal System-external Company-internal Company-external Event classification Trigger Condition Type of origin Frequency Simulation Probability Priority Comparison operator Comparison value Comparison value (numeric) Comparison value (logical) Frequency, daily
ARIS Methods
11-1291
Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event Event
Frequency, weekly Frequency, monthly Frequency, annually Evaluation Release Workflow Communication channel Parameter list Keyword Milestone ID Attributes of external system External ID SAP development class Text Default (import) Workflow Error message on non-compliance WPDL-external attribute list SAP Attributes Automatic event Original language (SAP) Commit resource Call mode Parameter key Change expression Change expression language
ARIS Methods
11-1292
Time expression Time expression language UML Event Stereotype
11.3.2.68 Event instance

Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Event instance Name Default (import) Project management attributes Target data Fixed date Planning constraint Priority Workflow Comparison operator Comparison value Status Error message on non-compliance PIP Distribution according to cost driver Absolute change in EMC Change in percent Bank code
ARIS Methods
11-1293
11.3.2.69 Exception
Exception Exception Exception Exception Exception Exception Name IsRoot IsLeaf IsAbstract Stereotype IsPersistent
11.3.2.70 Extension point

Extension point Extension point Extension point Name Stereotype Location
11.3.2.71 Field
Field Field Field Field Field Field Field Name NOT NULL Quantity structure Throughput/avg. access Quality of specialist support Relevance to data protection act SQL name
ARIS Methods
11-1294
11.3.2.72 Field (specimen)

Field (specimen) Field (specimen) Field (specimen) Name NOT NULL SQL name
11.3.2.73 Filter object type

Filter object type Filter object type Filter object type Filter object type Name Default (import) ALE Filter object type key
11.3.2.74 Function
Function Function Function Function Function Function Function Function Function Function Function Function Name Synonyms Sources used Source Application Book title Chapter name Heading 1 Heading 2 Processing type Online central Online decentralized
ARIS Methods
11-1295
Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
Batch central Batch decentralized Auto central Auto decentralized Manually Function use Company affiliation Optional function Classification ISO 9000 relevance Times Wait time Avg. wait time Min. wait time Max. wait time Orientation time Avg. orientation time Min. orientation time Max. orientation time Processing time Avg. processing time Min. processing time Max. processing time Frequency Frequency, daily Frequency, weekly
ARIS Methods
11-1296
Frequency, monthly Frequency, annually Volume Frequency per time period Period of time Expense Costs Total costs Avg. total costs Min. total costs Max. total costs Material costs Avg. material costs Min. material costs Max. material costs Personnel costs Avg. personnel costs Min. personnel costs Max. personnel costs Operating supplies costs Avg. operating supplies costs Min. operating supplies costs Max. operating supplies costs Energy costs Avg. energy costs Min. energy costs
ARIS Methods
11-1297
Function Function Function Function Function Function Function
Max. energy costs Various overhead costs Avg. various overhead costs Min. various overhead costs Max. various overhead costs Costs for depreciation/repair/maintenance Avg. costs for depreciation/repair/maintenance
Min. costs for depreciation/repair/maintenance Max. costs for depreciation/repair/maintenance Imputed interest Avg. imputed interest Min. imputed interest Max. imputed interest Other costs Avg. other costs Min. other costs Max. other costs Workflow Process successor immediately WPDL-external attribute list External applications Delayed forwarding possible Exit possible
ARIS Methods
11-1298
Cancel possible Can be reset Can be delegated Start step End step Only direct data visible Release Transaction code User exit Desktop integration Parameter list Keyword Degree of requirement satisfaction Attributes of external system External ID SAP function type SAP development class Text Default (import) ALE ALE Attribute Simulation Static wait time Orientation time Processing time Orientation (always)
ARIS Methods
11-1299
Evaluation Time limits Relative time limits Earliest start after instance creation Desired start after instance creation Latest start after instance creation Earliest end after instance creation Desired end after instance creation Latest end after instance creation Minimum total time Desired total time Maximum total time Maximum wait time after start Minimum processing time Desired processing time Maximum processing time Promet(r)BPR Cost driver Cost driver quantity units Measurement unit (CDU) Value (CDU) Costs per cost driver quantity unit Measurement unit of costs (CD) Costs (CD) Function type Type 1
ARIS Methods
11-1300
Type 2 Type 3 Type 4 Type 5 Type 6 Type 7 Deactivated Time keys UML Operation UML Use case UML Action state IsRoot IsLeaf IsAbstract IsStatic Visibility IsQuery IsPersistent Concurrency Derived IsPolymorphic Constraint Parameter Class operation Body SAP Attributes
ARIS Methods
11-1301
Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
Online Automatically controlled Batch-controlled Requirement SAP Degree of coverage Original language (SAP) Milestone Priority change allowed Skipping allowed Forwarding allowed Automatic Assignment type Time limit calculation Trigger function Workflow class Multiple procedures Privileges Free search access Search privilege for OU of the current user
Search privilege for Pos1 of the OU of the current user Search privilege for Pos1 of all superior OU's of the current user Search privilege for creators Search privilege for OU of the creator
ARIS Methods
11-1302
Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
Search privilege for all previous WF users Privileges can be changed by current user Privileges can be changed by creator Priority Benchmarking Index unit 1 Index 1 Description 1 Index unit 2 Index 2 Description 2 Index unit 3 Index 3 Description 3 Index unit 4 Index 4 Description 4 Interruptible Processes to be processed Resource allocation Usage factor Activity-based cost calculation SAP Dominant SAP-ARIS Online Guide
ARIS Methods
11-1303
Min. throughput time Avg. throughput time Max. throughput time Throughput time Return type Protocol Qualification Size Time SAP Server Trigger Result Invariances Non-functional requirements Process description Exceptions Variations Rules Services Miscellaneous requirements Contact person Change history Annotations Diagrams Redocumentation Scout Stereotype
ARIS Methods
11-1304
Dynamic arguments Dynamic arguments language IsDynamic Customizing view Customizing transaction
11.3.2.75 Function instance

Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Name Current status Times Processing time Min. processing time Max. processing time Mean processing time Wait time Orientation time Avg. total time Estimated duration Start date End date To be completed by Type of aggregation Default (import) Project management attributes Target data
ARIS Methods
11-1305
Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance
Actual data Earliest start date Latest start date Earliest end date Latest end date Fixed date Planning constraint Fixed plan operation costs Priority Task duration Operation work Number 1 Number 2 Number 3 Text 1 Text 2 Text 3 Workflow Compression type Process successor immediately Status Dunning period Restrictive period Only direct data visible Time limits Relative time limits
ARIS Methods
11-1306
Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance Function instance
Earliest start after instance creation Desired start after instance creation Latest start after instance creation Earliest end after instance creation Desired end after instance creation Latest end after instance creation Minimum total time Desired total time Maximum total time Maximum wait time after start Minimum processing time Desired processing time Maximum processing time Absolute time limits Earliest start time Desired start time Latest start time Earliest end time Desired end time Latest end time Avg. total costs Balanced Scorecard
ARIS Methods
11-1307
11.3.2.76 General resource

General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource General resource Name Default (import) Telephone number Fax number Address Project management attributes Target data Actual data Due date of fixed costs Fixed costs per operation ResCode Available capacity Cost rate Overtime cost rate Text 1 Text 2 Text 3 Simulation Minimum capacity Maximum capacity Startup capacity Evaluation
ARIS Methods
11-1308
11.3.2.77 Generalization type

Generalization type Generalization type Generalization type Generalization type Generalization type Generalization type Generalization type Generalization type Name Degree of division Attributes of external system External ID SAP development class Text Default (import) SAP Attributes
11.3.2.78 Graphical user interface type

Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type Graphical user interface type Name License number Manufacturer Release Acquisition costs Costs per unit
11.3.2.79 Group
Group Group Group Group Group Name Short description Default (import) Simulation Number of employees
ARIS Methods
11-1309
Group Group Group Group Group Group Group Group Group Group Group
Evaluation ARIS Applications Internal name Priority IsRoot IsLeaf IsAbstract Stereotype IsPersistent UML Actor Company affiliation
11.3.2.80 Hardware component

Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Hardware component Name Model Manufacturer Percentage utilization Acquisition costs Costs per unit Inventory number UML Node instance IsPersistent Stereotype
ARIS Methods
11-1310
11.3.2.81 Hardware component class

Hardware component class Hardware component class Name Category
11.3.2.82 Hardware component type

Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Name Model Manufacturer Percentage utilization Acquisition costs Costs per unit Text Default (import) UML Node IsRoot IsLeaf IsAbstract Stereotype IsPersistent
11.3.2.83 Improvement potential

Improvement potential Name
ARIS Methods
11-1311
11.3.2.84 Index
Index Index Index Index Name Category Default (import) SQL name
11.3.2.85 Information carrier

Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Name Subject Text SAP-ARIS Online Guide Book title Heading 2
11.3.2.86 Information flow

Information flow Information flow Information flow Information flow Information flow Information flow Information flow Information flow Information flow Name Transmission time Avg. transmission time Min. transmission time Max. transmission time Attributes of external system External ID SAP development class SAP Attributes
ARIS Methods
11-1312
11.3.2.87 Instantiation cycle

Instantiation cycle Instantiation cycle Instantiation cycle Instantiation cycle Instantiation cycle Instantiation cycle Name Simulation Relative cycle start Cycle duration Cyclical repeat Period
11.3.2.88 Instantiation interval

Instantiation interval Instantiation interval Instantiation interval Instantiation interval Instantiation interval Instantiation interval Instantiation interval Instantiation interval Name Simulation Relative interval start Interval duration Number of process instances Distribution Cyclical repeat Period
11.3.2.89 Instantiation plan

Instantiation plan Instantiation plan Instantiation plan Instantiation plan Instantiation plan Name Simulation Plan start Plan duration Cyclical repeat
ARIS Methods
11-1313
Instantiation plan
Period
11.3.2.90 Interaction instance set

Interaction instance set Interaction instance set Name Stereotype
11.3.2.91 IT function
IT function IT function Name Default (import)
11.3.2.92 IT function class

IT function class IT function class Name Default (import)
11.3.2.93 IT function type

IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type Name Manufacturer Release External Internal Installation status Scheduled from Scheduled until
ARIS Methods
11-1314
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
Realized from Realized until In use since Development effort Development effort (estimated) Development costs Development costs (estimated) Current cost for computer center Computer center (CC) costs Acquisition costs Costs per unit Frequency of execution Quality of specialist support ARIS Applications Internal name Doc requirements definition Doc development Shortcut In the toolbar Icon path Status bar Quick help Caption Function category Object type selection Object instance selection
ARIS Methods
11-1315
IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type IT function type
Screen required? As button? Access type Read Create Modify Delete Trigger to be released Time limit with fixed date calc. Unit for date calculation Calculation type for fixed date calculation Regulation for variable date calculation Process type Workflow Transaction code SAP Server Customizing view Customizing transaction
11.3.2.94 Key performance indicator instance

Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Name Actual time period Minimum value Maximum value
ARIS Methods
11-1316
Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance Key performance indicator instance
Plan value Tolerance range Actual value Achievement of objectives Target time period Target value Unit BSC - Remark/Example Key performance indicator evaluation Indicator type Degree of goal accomplishment End date Balanced Scorecard
11.3.2.95 Knowledge category

Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Knowledge category Name Updating frequency Significance Degree of coverage Knowledge advantage Knowledge usage Desired degree of coverage Future significance Structural change speed
ARIS Methods
11-1317
11.3.2.96 Layout
Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Layout Name Frame Left margin Right margin Top margin Bottom margin Frame width Bitmap Scaling in % Height Attributes Attribute flag Combo flag Length of entry field Status bar Title/Name Font format Font size Font Font color Background color Number of lines ARIS Applications Default value
ARIS Methods
11-1318
Layout Layout Layout Layout Layout
Access type Read Create Modify Delete
11.3.2.97 Link object

Link object Link object Link object Name IsPersistent Stereotype
11.3.2.98 List
List Name
11.3.2.99 List control

List control List control List control Name View Tabindex
11.3.2.100 Location
Location Location Name Location type
ARIS Methods
11-1319
11.3.2.101 Loop start

Loop start Name
11.3.2.102 Main process

Main process Main process Main process Main process Main process Main process Name Release Attributes of external system External ID SAP development class SAP Attributes
11.3.2.103 Marketing instrument

Marketing instrument Name
11.3.2.104 Material class

Material class Material class Material class Material class Material class Material class Material class Material class Name Default (import) Material number Hazard class Dangerous goods number Dangerous goods note Subject to management in batches Material type
ARIS Methods
11-1320
11.3.2.105 Material flow

Material flow Material flow Name Default (import)
11.3.2.106 Material type

Material type Material type Material type Material type Material type Material type Material type Material type Name Default (import) Material number Hazard class Dangerous goods number Dangerous goods note Subject to management in batches Material type
11.3.2.107 Measurement unit

Measurement unit Measurement unit Measurement unit Measurement unit Measurement unit Measurement unit Name Length ARIS Applications Internal name Doc requirements definition Doc development
ARIS Methods
11-1321
11.3.2.108 Measurement unit number

Measurement unit number Measurement unit number Measurement unit number Measurement unit number Measurement unit number Name ARIS Applications Internal name Doc requirements definition Doc development
11.3.2.109 Memory location

Memory location Memory location Memory location Memory location Memory location Memory location Memory location Name Size in KBytes Database Storage group Primary quantity Secondary quantity Category
11.3.2.110 Message flow

Message flow Message flow Name Default (import)
ARIS Methods
11-1322
11.3.2.111 Message type

Message type Message type Message type Message type Name Default (import) ALE Message type key
11.3.2.112 Module
Module Module Name License number
11.3.2.113 Module class

Module class Name
11.3.2.114 Module type

Module type Module type Module type Module type Module type Module type Module type Module type Module type Name Manufacturer Release External Internal Installation status Scheduled from Scheduled until Realized from
ARIS Methods
11-1323
Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type Module type
Realized until In use since Development effort Development effort (estimated) Development costs Development costs (estimated) Current cost for computer center Computer center (CC) costs Acquisition costs Costs per unit Frequency of execution Quality of specialist support Workflow Service name Parameter list ARIS Applications Internal name Doc requirements definition Doc development Shortcut In the toolbar Icon path Status bar Quick help Caption Function category
ARIS Methods
11-1324
Module type Module type Module type Module type Module type Module type Module type Module type
Object type selection Object instance selection Screen required? As button? Transaction code SAP Server Customizing view Customizing transaction
11.3.2.115 Need
Need Name
11.3.2.116 Network
Network Network Network Network Name License number Network topology Avg. utilization
11.3.2.117 Network class

Network class Network class Network class Network class Network class Name Network extension Network typification Network topology Network access procedure
ARIS Methods
11-1325
11.3.2.118 Network connection

Network connection Network connection Network connection Network connection Name Transmission speed Number of channels Transmission medium
11.3.2.119 Network connection type

Network connection type Network connection type Network connection type Name Transmission speed Number of channels
11.3.2.120 Network node

Network node Name
11.3.2.121 Network node type

Network node type Name
11.3.2.122 Network protocol

Network protocol Network protocol Network protocol Name Protocol layer Default (import)
ARIS Methods
11-1326
11.3.2.123 Network type

Network type Network type Network type Network type Network type Network type Network type Network type Network type Name Manufacturer Release Transmission speed Network typification Network topology Network access procedure Acquisition costs Costs per unit
11.3.2.124 Note
Note Note Note Note Name Stereotype Interface implementation Body
11.3.2.125 Object instance

Object instance Object instance Object instance Name Stereotype IsPersistent
ARIS Methods
11-1327
11.3.2.126 Object type class

Object type class Name
11.3.2.127 Objective
Objective Objective Objective Objective Objective Objective Objective Objective Objective Objective Objective Objective Objective Objective Name Balanced Scorecard Actual time period Minimum value Maximum value Plan value Tolerance range Actual value Achievement of objectives Target time period Target value Unit BSC - Remark/Example End date
11.3.2.128 Operating resource

Operating resource Operating resource Operating resource Operating resource Name Default (import) Operating resource number Acquisition costs
ARIS Methods
11-1328
Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource Operating resource
Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer Inventory number Simulation Evaluation Project management attributes Target data Actual data Due date of fixed costs Fixed costs per operation ResCode Available capacity Cost rate Overtime cost rate
ARIS Methods
11-1329
Operating resource Operating resource Operating resource Operating resource Operating resource
Text 1 Text 2 Text 3 Capacity Priority
11.3.2.129 Operating resource class

Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Operating resource class Name Default (import) Operating resource number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time
ARIS Methods
11-1330
11.3.2.130 Operating resource type

Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Operating resource type Name Default (import) Operating resource number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer
11.3.2.131 Operating system

Operating system Operating system Name License number
ARIS Methods
11-1331
11.3.2.132 Operating system type

Operating system type Operating system type Operating system type Operating system type Operating system type Name Manufacturer Release Acquisition costs Costs per unit
11.3.2.133 Operation
Operation Operation Operation Operation Operation Operation Operation Operation Operation Operation Name Derived Class operation Parameter Constraint IsAbstract Stereotype IsPolymorphic IsQuery Body
11.3.2.134 Organizational chart

Organizational chart Name
ARIS Methods
11-1332
11.3.2.135 Organizational level

Organizational level Name
11.3.2.136 Organizational unit

Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Name Application Type of organizational unit Line position Staff position Company affiliation Address Telephone number Attributes of external system External ID SAP development class Text Default (import) Workflow WPDL-external attribute list Simulation Number of employees Evaluation ARIS Applications Internal name Activity-based cost calculation
ARIS Methods
11-1333
Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit
Client Company code Head of cost center PIP O category number O category name O competitive situation number O competitive situation name O location number O location name O equipment number O equipment name O size Employee council number Employee council name Cost center ID SAP Attributes Privileges Individual access privileges Bank code Cost rate Cost center number Priority IsRoot IsLeaf IsAbstract
ARIS Methods
11-1334
Stereotype IsPersistent UML Actor
11.3.2.137 Organizational unit type

Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Name Type of organizational unit Line position Staff position Attributes of external system External ID SAP development class Tolerance Tolerance executive management Tolerance control Tolerance administration Tolerance decision Tolerance default processing Tolerance sales Tolerance individual processing Function type number SAP Attributes Company affiliation
ARIS Methods
11-1335
11.3.2.138 Package
Package Package Package Package Package Name IsRoot IsLeaf IsAbstract Stereotype
11.3.2.139 Packaging material class

Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Packaging material class Name Default (import) Packaging material number Packaging instruction/rule Transport instruction/rule Packaging type Capacity Value Unit of capacity Costs Measurement unit of costs Costs
ARIS Methods
11-1336
11.3.2.140 Packaging material type

Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Packaging material type Name Default (import) Packaging material number Packaging instruction/rule Transport instruction/rule Packaging type Capacity Value Unit of capacity Costs Measurement unit of costs Costs
11.3.2.141 Page
Page Name
11.3.2.142 Parameter
Parameter Parameter Parameter Parameter Parameter Parameter Name ARIS Applications Internal name Doc requirements definition Doc development Direction
ARIS Methods
11-1337
Parameter Parameter Parameter Parameter
Default value Stereotype Default value language IsOrdered (Src)
11.3.2.143 Partition
Partition Partition Name Stereotype
11.3.2.144 Performance characteristic

Performance characteristic Name
11.3.2.145 Person
Person Person Person Person Person Person Person Person Person Person Person Name Telephone number Fax number E-mail address Address Text Default (import) Project management attributes Target data Actual data Due date of fixed costs
ARIS Methods
11-1338
Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person Person
Fixed costs per operation ResCode Available capacity Cost rate Overtime cost rate Text 1 Text 2 Text 3 Person status Simulation Evaluation Workflow Home directory WPDL-external attribute list ARIS Applications Internal name Individual access privileges Language First name Title Role binding Workflow domain Privileges Priority IsRoot IsLeaf
ARIS Methods
11-1339
IsAbstract Stereotype IsPersistent UML Actor
11.3.2.146 Person type

Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Person type Name Cost rate Amount Amount per time unit Text Default (import) Workflow WPDL-external attribute list ARIS Applications Internal name Simulation Number of employees Evaluation Position Priority Activity group IsRoot IsLeaf IsAbstract
ARIS Methods
11-1340
Stereotype IsPersistent UML Actor Company affiliation
11.3.2.147 Perspective
Perspective Name
11.3.2.148 Position
Position Position Position Position Position Position Position Position Position Position Position Position Position Position Position Position Name Employee Simulation Number of employees Evaluation ARIS Applications Internal name Tolerance Tolerance executive management Tolerance control Tolerance administration Tolerance decision Tolerance default processing Tolerance sales Tolerance individual processing Position
ARIS Methods
11-1341
Position Position Position Position Position Position Position Position
Workflow Priority IsRoot IsLeaf IsAbstract Stereotype IsPersistent UML Actor
11.3.2.149 Process
Process Name
11.3.2.150 Product/Service
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Name Default (import) Frequency Frequency, daily Frequency, weekly Frequency, monthly Frequency, annually Volume Frequency per time period Period of time Expense Costs
ARIS Methods
11-1342
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
Total costs Avg. total costs Min. total costs Max. total costs Material costs Avg. material costs Min. material costs Max. material costs Personnel costs Avg. personnel costs Min. personnel costs Max. personnel costs Operating supplies costs Avg. operating supplies costs Min. operating supplies costs Max. operating supplies costs Energy costs Avg. energy costs Min. energy costs Max. energy costs Various overhead costs Avg. various overhead costs Min. various overhead costs Max. various overhead costs Costs for depreciation/repair/maintenance
ARIS Methods
11-1343
Avg. costs for depreciation/repair/maintenance Min. costs for depreciation/repair/maintenance Max. costs for depreciation/repair/maintenance
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
Imputed interest Avg. imputed interest Min. imputed interest Max. imputed interest Other costs Avg. other costs Min. other costs Max. other costs Significance Occurrence Internal process (actual) Internal process (target) Most important competitor Digit Budgetary relation Revenues Federal government Federal land Citizen Free market Other
ARIS Methods
11-1344
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
Order processing Price Product quantity Simulation Minimum capacity Maximum capacity Startup capacity Evaluation UML State Do Exit Stereotype Entry System attributes Transmission type Transmission type, online Transmission type, batch Transmission type, manually Sales product
11.3.2.151 Program library

Program library Program library Program library Program library Name Manufacturer Release Size in KBytes
ARIS Methods
11-1345
11.3.2.152 Program module

Program module Name
11.3.2.153 Program module type

Program module type Program module type Program module type Program module type Name Size in KBytes Archiving Format
11.3.2.154 Programming language

Programming language Name
11.3.2.155 Quick object

Quick object Name
11.3.2.156 Radio button/Check box

Radio button/Check box Radio button/Check box Radio button/Check box Name Field type Tabindex
ARIS Methods
11-1346
11.3.2.157 Reception
Reception Reception Reception Reception Reception Reception Reception Reception Reception Name IsRoot IsLeaf IsAbstract IsStatic Visibility IsQuery Specification Stereotype
11.3.2.158 Relation
Relation Relation Relation Relation Relation Relation Relation Name Archiving Quantity structure Throughput/avg. access Relevance to data protection act Quality of specialist support SQL name
11.3.2.159 Relationship
Relationship Relationship Relationship Name Default (import) Workflow
ARIS Methods
11-1347
Relationship Relationship Relationship Relationship Relationship Relationship
Data type Last modification date Creation date Object access ID Template Default name
11.3.2.160 Relationship type

Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Name Synonyms Integrity conditions Storage type Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend SQL name Aggregation Text Default (import) Workflow Data type
ARIS Methods
11-1348
Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type Relationship type
Object access ID Template Default name WPDL-external attribute list ARIS Applications Internal name Doc requirements definition Doc development Hidden Transient
11.3.2.161 Risk
Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Name Synonyms Origin System-internal System-external Company-internal Company-external Event classification Trigger Condition Type of origin Frequency Frequency, daily
ARIS Methods
11-1349
Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk Risk
Frequency, weekly Frequency, monthly Frequency, annually Release Workflow Communication channel Parameter list Keyword Milestone ID Probability Business control Central control code Local control code
11.3.2.162 Rule
Rule Rule Rule Rule Rule Rule Rule Rule Rule Rule Name Operator type Attributes of external system External ID SAP development class Text Default (import) Simulation Synchronization time Evaluation
ARIS Methods
11-1350
Rule Rule Rule Rule Rule Rule Rule Rule Rule
Workflow Error message on non-compliance WPDL-external attribute list Condition SAP Attributes Usage type Stereotype Synchronization type Number of synchronizations
11.3.2.163 Rule instance

Rule instance Rule instance Rule instance Rule instance Rule instance Name Default (import) Workflow Error message on non-compliance Status
11.3.2.164 Screen
Screen Screen Screen Screen Screen Screen Screen Name ARIS Applications Internal name Default screen Doc requirements definition Doc development Transaction code
ARIS Methods
11-1351
Screen Screen Screen Screen Screen
SAP Server SAP-ARIS Online Guide Redocumentation Scout Customizing view Customizing transaction
11.3.2.165 Screen design

Screen design Name
11.3.2.166 Screen table

Screen table Name
11.3.2.167 Section
Section Section Section Section Name Column Column width Alignment
11.3.2.168 Security protocol

Security protocol Name
ARIS Methods
11-1352
11.3.2.169 Separator
Separator Separator Name Factor
11.3.2.170 Sequence
Sequence Name
11.3.2.171 Shift
Shift Shift Shift Shift Name Simulation Relative shift start Shift duration
11.3.2.172 Shift cycle

Shift cycle Shift cycle Shift cycle Shift cycle Shift cycle Shift cycle Name Simulation Relative cycle start Cycle duration Cyclical repeat Period
ARIS Methods
11-1353
11.3.2.173 Shift plan

Shift plan Shift plan Shift plan Shift plan Shift plan Shift plan Name Simulation Plan start Plan duration Cyclical repeat Period
11.3.2.174 Signal
Signal Signal Signal Signal Signal Signal Name IsRoot IsLeaf IsAbstract Stereotype IsPersistent
11.3.2.175 Solution
Solution Solution Solution Solution Solution Solution Solution Name Synonyms Origin System-internal System-external Company-internal Company-external
ARIS Methods
11-1354
Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution Solution
Event classification Trigger Condition Type of origin Frequency Frequency, daily Frequency, weekly Frequency, monthly Frequency, annually Release Workflow Communication channel Parameter list Keyword Milestone ID Probability Business control Central control code Local control code
11.3.2.176 Sp./gen. operator

Sp./gen. operator Sp./gen. operator Sp./gen. operator Name Disjoint Aspect
ARIS Methods
11-1355
11.3.2.177 Spin box

Spin box Spin box Name Tabindex
11.3.2.178 State
State State State State State Name Do/activity Entry/action Exit/action Event/action
11.3.2.179 State machine

State machine State machine Name Stereotype
11.3.2.180 Strategy
Strategy Name
11.3.2.181 Structural element

Structural element Name
ARIS Methods
11-1356
11.3.2.182 Subsystem
Subsystem Subsystem Subsystem Subsystem Subsystem Subsystem Subsystem Name IsInstantiable IsRoot IsLeaf IsAbstract IsPersistent Stereotype
11.3.2.183 Subsystem instance

Subsystem instance Subsystem instance Subsystem instance Name IsPersistent Stereotype
11.3.2.184 System attribute

System attribute System attribute System attribute System attribute System attribute Name Value 1 Value 2 Default (import) SQL name
ARIS Methods
11-1357
11.3.2.185 System attribute domain

System attribute domain System attribute domain System attribute domain System attribute domain System attribute domain System attribute domain Name Domain type Length Category Default (import) SQL name
11.3.2.186 System organizational unit

System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit Name Release Attributes of external system External ID SAP development class Text Default (import) SAP Attributes Redocumentation Scout
11.3.2.187 System organizational unit type

System organizational unit type System organizational unit type System organizational unit type System organizational unit type Name Application Release Text
ARIS Methods
11-1358
System organizational unit type System organizational unit type System organizational unit type System organizational unit type System organizational unit type
Default (import) Attributes of external system External ID SAP development class SAP Attributes
11.3.2.188 Table
Table Table Table Table Table Table Table Name Archiving Quantity structure Throughput/avg. access Quality of specialist support Relevance to data protection act SQL name
11.3.2.189 Tables (specimen)

Tables (specimen) Tables (specimen) Name SQL name
11.3.2.190 Tech. operating supply class

Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Name Default (import) Technical operating supply number Acquisition costs
ARIS Methods
11-1359
Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class Tech. operating supply class
Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Serviceable life
11.3.2.191 Technical operating supply

Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Name Default (import) Technical operating supply number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity
ARIS Methods
11-1360
Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply Technical operating supply
Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Serviceable life Model Manufacturer Inventory number Simulation Evaluation Capacity Priority
11.3.2.192 Technical operating supply type

Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Name Default (import) Technical operating supply number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time
ARIS Methods
11-1361
Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type Technical operating supply type
Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer Serviceable life
11.3.2.193 Technical term

Technical term Technical term Technical term Technical term Technical term Technical term Technical term Technical term Technical term Technical term Technical term Name Synonyms Quantity structure Throughput/avg. access No. of occurrences No. of occurrences - max. No. of occurrences - min. No. of occurrences - avg. No. of occurrences - trend Text Default (import)
ARIS Methods
11-1362
11.3.2.194 Technical terms instance

Technical terms instance Technical terms instance Name Default (import)
11.3.2.195 Text
Text Text Name Hyperlink
11.3.2.196 Text box

Text box Text box Text box Text box Name Field type Encoded Tabindex
11.3.2.197 Tool
Tool Name
11.3.2.198 Transaction folder

Transaction folder Transaction folder Transaction folder Transaction folder Transaction folder Name Default (import) Workflow Status Priority
ARIS Methods
11-1363
Transaction folder Transaction folder Transaction folder Transaction folder Transaction folder
Resubmission date Resubmission reason Times Time limits Relative time limits
11.3.2.199 Transport system

Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Transport system Name Default (import) Transport system number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer
ARIS Methods
11-1364
Transport system Transport system Transport system Transport system Transport system
Inventory number Simulation Evaluation Capacity Priority
11.3.2.200 Transport system class

Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Transport system class Name Default (import) Transport system number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time
ARIS Methods
11-1365
11.3.2.201 Transport system type

Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Transport system type Name Default (import) Transport system number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer
11.3.2.202 Tree control

Tree control Tree control Tree control Tree control Name Buttons Lines Lines at roots
ARIS Methods
11-1366
Check box Tabindex
11.3.2.203 UML Model

UML Model UML Model Name Stereotype
11.3.2.204 Use case instance

Use case instance Use case instance Use case instance Name IsPersistent Stereotype
11.3.2.205 View
View View Name SQL name
11.3.2.206 View (physical)

View (physical) View (physical) Name SQL name
ARIS Methods
11-1367
11.3.2.207 Warehouse equipment

Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Warehouse equipment Name Default (import) Warehouse equip. number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer Inventory number Simulation Evaluation Capacity Priority
ARIS Methods
11-1368
11.3.2.208 Warehouse equipment class

Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Warehouse equipment class Name Default (import) Warehouse equip. number Acquisition costs Value Measurement unit Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time
11.3.2.209 Warehouse equipment type

Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Name Default (import) Warehouse equip. number Acquisition costs Value Measurement unit
ARIS Methods
11-1369
Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type Warehouse equipment type
Maintenance cycle Frequency per time unit Period of time Production capacity Production quantity Measurement unit of production quantity Period of time Cleaning cycle Frequency per time period Period of time Model Manufacturer
11.3.2.210 XOR
XOR Name
ARIS Methods
11.4 ARIS Attribute Types
11-1370

11.4.1 Possible Attribute Values
Basic Type Floating point number Value Integer N-liner One-liner Floating point number Boolean N-liner Boolean Boolean Value Integer Integer N-liner N-liner Boolean Boolean N-liner Value Value Value Maximum Length 7 20 5 50 20 20 2 512 2 2 256 30 20 10000000 512 2 2 512 25 50 512
Attribute Type Name Absolute change in EMC Achievement of objectives Activations Activity group Actual time period Actual value Added from RBE database Address Aggregation ALE Attribute Alignment Amount Amount per time unit Annotations Application Archiving As button? Aspect Assignment type Association kind Attribute default
ARIS Methods
11-1371
Attribute Type Name Attribute flag Author Author Auto central Auto decentralized Automatic Automatic event Automatically controlled Available capacity Average capacity Average initial wait time Average transaction frequency Average wait time Avg. costs for depreciation/repair/maintenance Avg. energy costs Avg. imputed interest Avg. material costs Avg. operating supplies costs Avg. orientation time Avg. other costs Avg. personnel costs Avg. processing time Avg. throughput time
Basic Type Value N-liner One-liner Boolean Boolean Boolean Boolean Boolean Floating point number Floating point number Combined Integer
Maximum Length 10 50 10000 2 2 2 2 2 20 10 20 20
Combined Combined
20 20
Combined Combined Combined Combined Combined Combined Combined Combined Combined
20 20 20 20 20 20 20 20 20
ARIS Methods
11-1372
Attribute Type Name Avg. total costs Avg. total time Avg. transmission time Avg. utilization Avg. various overhead costs Avg. wait time Background color Bank code Batch central Batch decentralized Batch-controlled Bitmap path Body Book title Bottom margin Bound Break duration Break start BSC - Remark/Example Budgetary relation Buttons Calculated end date Calculated operation costs Calculated start date
Basic Type Combined Combined Combined Floating point number Combined Combined One-liner Integer Boolean Boolean Boolean One-liner N-liner N-liner Boolean Integer Duration Duration N-liner N-liner Boolean Date Floating point number Date
Maximum Length 20 20 20 10 20 20 50 9 2 2 2 256 10000000 100 2 256 30 30 10000000 256 2 20 20 20
ARIS Methods
11-1373
Attribute Type Name Calculation type for fixed date calculation Call mode Can be delegated Can be reset Cancel possible Capacity Caption Category Category Category Cause of complaint CD Number Central control code Change expression Change expression language Change history Change in percent Changeability Changed by Changed on Chapter name Check box Checked by
Basic Type Value
Maximum Length 30
Value Boolean Boolean Boolean Integer domain One-liner N-liner One-liner Value N-liner Integer N-liner N-liner One-liner N-liner Floating point number Value N-liner Date One-liner Boolean N-liner
30 2 2 2 8 1 100 10 512 10000000 100 300 10000000 500 10000000 6 50 100 20 100 2 100
ARIS Methods
11-1374
Attribute Type Name Checked on Citizen Class attribute Class operation Classification Client Column width Combo flag Commit resource Communication channel Company affiliation Company code Company-external Company-internal Comparison attribute Comparison operator Comparison value Comparison value (logical) Comparison value (numeric) Complaint duration Complaint pending Complexity Compression type
Basic Type Date Combined Boolean Boolean Value One-liner Value Value Boolean One-liner Value One-liner Boolean Boolean Integer Value N-liner Boolean Floating point number Duration Boolean One-liner N-liner
Maximum Length 20 20 2 2 512 4 256 20 2 2 512 4 2 2 4 20 80 2 10 20 2 10 80
ARIS Methods
11-1375
Attribute Type Name Computer center (CC) costs Concurrency Concurrency Condition Condition Condition Constraint Contact person Containment Conversion to table Copy Cost category No. Cost category type Cost center ID Cost center number Cost driver Cost rate Cost rate Costs Costs (CD) Costs per unit Create Created by Created in R/3 release
Basic Type Combined
Maximum Length 20
Value Value Boolean N-liner N-liner N-liner N-liner Value Boolean Boolean One-liner One-liner Boolean One-liner One-liner Combined Floating point number One-liner Floating point number Combined Boolean N-liner N-liner
15 20 2 100 10000000 256 250 20 2 2 10 2 2 20 20 20 20 100 20 40 2 100 4
ARIS Methods
11-1376
Attribute Type Name Created on Creation date Creator Creator (SAP) Current capacity Current costs Current duration Current end date Current object Current operation work Current provision time Current resource costs Current resource work Current start date Current start time Current status Current user Customizing transaction Customizing view Cycle duration Cyclical repeat Dangerous goods note Dangerous goods number Data management system Data type
Basic Type Date Point in time N-liner N-liner Integer Floating point number Combined Date Integer Floating point number Point in time Floating point number Floating point number Date Point in time One-liner Integer One-liner One-liner Duration Boolean One-liner One-liner One-liner Value
Maximum Length 20 20 81 10000000 10 20 20 20 8 20 20 20 20 20 20 50 8 20 30 30 2 100 100 30 10
ARIS Methods
11-1377
Attribute Type Name Data type Data type Data type operations Database Deactivated Decimal places Default (import) Default name Default screen Default value Default value Default value Default value language Degree of activation Degree of coverage Degree of division Degree of fulfillment Degree of goal accomplishment Degree of requirement satisfaction Delayed forwarding possible Delete Derived Derived attribute
Basic Type Value Value N-liner N-liner Boolean Integer N-liner N-liner Boolean N-liner One-liner One-liner One-liner Floating point number Integer domain Value Floating point number Floating point number
Maximum Length 20 512 512 100 2 3 512 20 2 150 100 1000 500 10 3 512 10 20
Value Boolean Boolean Boolean Boolean
512 2 2 2 2
ARIS Methods
11-1378
Attribute Type Name Description 1 Description 2 Description 3 Description 4 Description of attribute derivation Description of eEPC (build time) Description of eEPC (run time) Description/Definition Descriptive text Desired degree of coverage Desired end after instance creation Desired end time Desired processing time Desired start after instance creation Desired start time Desired total time Desktop integration Development costs Development costs (estimated) Development effort
Basic Type N-liner N-liner N-liner N-liner One-liner Integer
Maximum Length 512 512 512 512 400 20
Integer N-liner N-liner Integer domain Duration
20 10000000 80 3 20
Point in time Duration Duration Point in time Duration One-liner Combined Combined Combined
20 20 20 20 20 2 20 20 10
ARIS Methods
11-1379
Attribute Type Name Development effort (estimated) Diagrams Digit Direction Disabled Disjoint Distribution Distribution according to cost driver Distribution list Do Do/activity Doc development Doc requirements definition Domain type Due date of fixed costs Dunning period Duration Duration of interruption Dynamic arguments Dynamic arguments language Dynamic wait time sum E-mail address
Basic Type Combined
Maximum Length 10
N-liner N-liner Value Boolean Boolean Longtext Boolean N-liner N-liner N-liner N-liner N-liner
10000000 30 50 2 2 80 2 10000000 100 300 512 512
Value Value N-liner Integer domain Duration N-liner One-liner Duration One-liner
512 20 40 20 20 10000000 500 30 512
ARIS Methods
11-1380
Attribute Type Name Earliest end after instance creation Earliest end date Earliest end time Earliest start after instance creation Earliest start date Earliest start time eEPC (build time) eEPC (run time) Employee Employee council name Employee council number Encoded End after instance creation End date End of complaint End of interruption End step End time End time after instance creation English descriptive text Entry Entry/action
Basic Type Duration
Maximum Length 20
Date Point in time Duration Date Point in time Integer Integer One-liner One-liner Integer Boolean N-liner
20 20 20 20 20 8 8 100 512 2 2 20
Date Point in time Point in time Boolean Point in time Duration N-liner N-liner N-liner
20 20 20 2 20 20 10000000 100 300
ARIS Methods
11-1381
Attribute Type Name Error message on noncompliance Estimated duration Evaluation time Event/action Exceptions Existence Exit Exit possible Exit/action Expense External External documents External ID Factor Fax number Federal government Federal land Field type Filter object type key First name Fixed costs per operation Fixed date Fixed plan operation costs Folder rule test
Basic Type Boolean
Maximum Length 2
Combined Point in time N-liner N-liner Boolean N-liner Boolean N-liner Combined Boolean N-liner External identifier Integer N-liner Combined Combined Value One-liner N-liner Floating point number Date Floating point number N-liner
20 20 300 32000 2 100 2 300 20 2 10000000 20 4 512 20 20 100 20 64 20 20 20 2024
ARIS Methods
11-1382
Attribute Type Name Font Font color Font size Format Forwarding allowed Frame width Free market Free search access Frequency of execution Frequency per time period Frequency per time period Frequency per time unit Frequency, annually Frequency, daily Frequency, monthly Frequency, weekly Full name Function type number Future significance Hazard class Head of cost center Heading 1 Heading 2 Height Help file
Basic Type One-liner One-liner Integer Integer Boolean Integer Combined Boolean Integer Integer Integer Integer Integer Integer Integer Integer N-liner Integer Value One-liner N-liner N-liner N-liner Floating point number N-liner
Maximum Length 50 50 2 40 2 4 20 2 12 100 20 100 12 12 12 12 255 1 20 100 22 200 200 4 512
ARIS Methods
11-1383
Attribute Type Name Hidden Hierarchy number History Home directory Hyperlink Icon path Identifier Ignore Improvement potential In the toolbar In use since Incoming process folders Index 1 Index 2 Index 3 Index 4 Index unit 1 Index unit 2 Index unit 3 Index unit 4 Indicator type Individual access privileges Initial value Initial value language
Basic Type Boolean N-liner N-liner N-liner One-liner One-liner One-liner Boolean N-liner Boolean Date Integer Floating point number Floating point number Floating point number Floating point number One-liner One-liner One-liner One-liner Value Boolean N-liner One-liner
Maximum Length 2 10 10000000 128 512 256 32 2 10000000 2 12 5 12 12 12 12 50 50 50 50 20 2 256 500
ARIS Methods
11-1384
Attribute Type Name Initial wait time Instance creation time Instance value Integrity conditions Interface implementation Internal Internal name Internal process (actual) Internal process (target) Interruptible Interruption time sum Interval duration Invariances Inventory number IsAbstract IsActive IsAsynchronous IsBinary IsConcurrent IsDynamic IsInstantiable IsLeaf ISO 9000 relevance IsOrdered (Src) IsPersistent
Basic Type Combined Point in time N-liner N-liner N-liner Boolean N-liner Floating point number Floating point number Boolean Duration Duration N-liner One-liner Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean
Maximum Length 20 20 80 100 10000000 2 40 20 20 2 20 30 10000000 100 2 2 2 20 2 2 2 2 2 2 2
ARIS Methods
11-1385
Attribute Type Name IsPolymorphic IsQuery IsRoot IsStatic IsSynch IsVolatile Key performance indicator evaluation Keyword Knowledge advantage Knowledge usage Language Language Last change Last change (SAP) Last change (Workflow) Last change in R/3 release Last modification date Last status (CMA) Last user Last user (SAP) Latest end after instance creation Latest end date Latest end time
Basic Type Boolean Boolean Boolean Boolean Boolean Boolean Value
Maximum Length 2 2 2 2 2 2 512
N-liner Integer domain Integer domain N-liner One-liner Point in time Point in time Point in time N-liner Point in time Value N-liner N-liner Duration Date Point in time
80 3 3 3 500 20 20 32 4 20 20 100 10000000 20 20 20
ARIS Methods
11-1386
Attribute Type Name Latest release Latest start after instance creation Latest start date Latest start time Left margin Length Length Length of entry field License number Line position Lines Lines at roots Link 1 Link 2 Link 3 Link 4 LNC Link1 LNC Title1 Local control code Local descriptive text Location Location type Lower limit Manually
Basic Type N-liner Duration Date Point in time Boolean Integer Integer Integer One-liner Boolean Boolean Boolean Link/File Link/File Link/File Link/File N-liner N-liner N-liner N-liner N-liner Value Floating point number Boolean
Maximum Length 10000 20 20 20 2 10 100 3 100 2 2 2 512 512 512 512 1000 100 300 10000000 10000000 512 20 2
ARIS Methods
11-1387
Attribute Type Name Manufacturer Manufacturer Material number Material type Max. costs for depreciation/repair/maintenance Max. energy costs Max. imputed interest Max. material costs Max. operating supplies costs Max. orientation time Max. other costs Max. personnel costs Max. processing time Max. throughput time Max. total costs Max. total time Max. transmission time Max. various overhead costs Max. wait time Maximum capacity Maximum initial wait time Maximum processing time Maximum total time
Basic Type One-liner One-liner One-liner Value Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Integer Combined Duration Duration
Maximum Length 100 50 100 512 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 10 20 20 20
ARIS Methods
11-1388
Attribute Type Name Maximum value Maximum wait time after start Mean orientation time Mean processing time Measure Measurement unit Measurement unit (CDU) Measurement unit of costs Measurement unit of costs (CD) Measurement unit of production quantity Message on error Message type key Milestone Milestone ID Min. costs for depreciation/repair/maintenance Min. energy costs Min. imputed interest Min. material costs Min. operating supplies costs Min. orientation time Min. other costs
Basic Type Floating point number Duration Combined Combined N-liner Value One-liner Value One-liner One-liner
Maximum Length 20 20 20 20 10000000 512 20 512 20 100
Boolean One-liner Boolean Boolean Combined
2 20 2 2 20
Combined Combined Combined Combined Combined Combined
20 20 20 20 20 20
ARIS Methods
11-1389
Attribute Type Name Min. personnel costs Min. processing time Min. throughput time Min. total costs Min. total time Min. transmission time Min. various overhead costs Min. wait time Minimum capacity Minimum initial wait time Minimum processing time Minimum total time Minimum value Miscellaneous requirements Model Model Modify Module code Most important competitor Multiple procedures Multiple value tag Multiplicity Name
Basic Type Combined Combined Combined Combined Combined Combined Combined
Maximum Length 20 20 20 20 20 20 20
Combined Integer Combined Duration Duration Floating point number N-liner
20 10 20 20 20 20 10000000
One-liner One-liner Boolean Value Floating point number Value Value One-liner N-liner
10 100 2 20 20 30 100 500 81
ARIS Methods
11-1390
Attribute Type Name Name ext. system (alias) Network access procedure Network extension Network topology Network typification No. of occurrences - avg. No. of occurrences - max. No. of occurrences - min. No. of occurrences - trend Non-functional requirements NOT NULL Notation Number 1 Number 2 Number 3 Number being processed Number carried out Number dynamic waiting Number in orientation Number of channels Number of compressed object definitions Number of employees Number of events not yet evaluated
Basic Type One-liner Value Value Value Value Integer Integer Integer One-liner N-liner Boolean Boolean Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer domain Integer
Maximum Length 33 512 512 512 512 12 12 12 60 10000000 2 2 20 20 20 4 5 4 4 10 10 10 10
ARIS Methods
11-1391
Attribute Type Name Number of false events Number of function executions Number of interruptions during orientation Number of interruptions during processing Number of lines Number of process instances Number of synchronizations Number of true events Number static waiting O category name O category number O competitive situation name O competitive situation number O equipment name O equipment number O location name O location number O size Object access ID Object ID
Basic Type Integer Integer Integer
Maximum Length 10 5 8
Integer Integer Integer Integer Integer Integer One-liner Integer One-liner Integer One-liner Integer One-liner Integer Integer N-liner One-liner
8 2 10 20 10 4 512 2 512 2 512 2 512 2 2 1024 10000
ARIS Methods
11-1392
Attribute Type Name Object instance selection Object type selection OID Oldest release Online Online central Online decentralized Only direct data visible Operating resource number Operating system Operation work Operator type Optional attribute Optional function Order processing Ordinal Organization Orientation (always) Orientation time Orientation time Orientation time sum Original language (SAP) Other
Basic Type Boolean Boolean One-liner N-liner Boolean Boolean Boolean Boolean One-liner One-liner Floating point number Value Boolean Boolean Value Integer N-liner Boolean Combined Longtext Duration N-liner Combined
Maximum Length 2 2 200 10000 2 2 2 2 100 30 20 512 2 2 20 4 500 2 20 50 30 2 20
ARIS Methods
11-1393
Attribute Type Name Other applicable documents Overtime cost rate Packaging instruction/rule Packaging material number Packaging type Parameter Parameter 1 Parameter 2 Parameter 3 Parameter 4 Parameter key Parameter list Parameter list Percentage utilization Performance scale Period Period of time Period of time Person responsible Person status Plan duration Plan start Plan value
Basic Type N-liner
Maximum Length 10000000
Floating point number One-liner One-liner Value N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner Floating point number One-liner Duration Combined Combined One-liner Value Duration Point in time Floating point number
20 100 100 512 10000000 260 260 260 260 10000000 128 2048 10 20 30 100 60 250 20 30 30 20
ARIS Methods
11-1394
Attribute Type Name Planning constraint Position Previous object Previous user Price Primary quantity Priority Priority Priority Priority Priority change allowed Privileges can be changed by creator Privileges can be changed by current user Probability Process description Process instantiations Process manager Process priority Process successor immediately Process type Processes to be processed Processing code
Basic Type Value Value Integer Integer Combined N-liner Integer Integer Integer domain Value Boolean Boolean
Maximum Length 512 15 8 8 20 100 2 8 2 512 2 2
Boolean Floating point number domain N-liner Integer N-liner Integer Boolean Value Integer domain One-liner
2 20 10000000 5 80 8 2 10 8 30
ARIS Methods
11-1395
Attribute Type Name Processing time Processing time Processing time Processing time sum Product quantity Production quantity Protocol Protocol layer Provision time Pseudostate kind Purpose Qualification Quality of specialist support Quick help RBE usage factor Read Realized from Realized until Recurrence Recurrence language Reference state Regulation for variable date calculation Relative cycle start
Basic Type Combined Longtext N-liner Duration Integer One-liner One-liner Value Point in time Value N-liner One-liner Value One-liner Floating point number Boolean Date Date N-liner One-liner One-liner N-liner Duration
Maximum Length 20 50 20 30 10 100 32000 512 20 50 10000000 32000 512 50 30 2 12 12 10000000 500 1000 1024 30
ARIS Methods
11-1396
Attribute Type Name Relative interval start Relative shift start Release Released by Released on Relevance to data protection act Remark Remark/Example Replaces version Reported on Requirement ResCode Resource allocation Responsibility Responsible Restrictive period Resubmission date Resubmission reason Result Return type Right margin Role Role binding Rule attribute
Basic Type Duration Duration One-liner N-liner Date Boolean N-liner N-liner One-liner Date One-liner N-liner Value N-liner One-liner N-liner Point in time N-liner N-liner N-liner Boolean Value Boolean Value
Maximum Length 30 30 16 100 20 2 10000000 10000000 20 20 20 255 20 200 20 40 22 2024 10000000 60 2 20 2 512
ARIS Methods
11-1397
Attribute Type Name Rules Safety class of specimens Sales product SAP Degree of coverage
Basic Type N-liner One-liner Boolean Floating point number domain
Maximum Length 10000000 100 2 5
SAP development class SAP Dominant SAP function type SAP ID SAP Server SAP-ARIS Online Guide Scaling in % Scheduled from Scheduled until Screen required? Script Script language Search attribute Search privilege for all previous WF users Search privilege for creators Search privilege for OU of the creator Search privilege for OU of the current user
N-liner N-liner Value One-liner One-liner Boolean Integer Date Date Boolean N-liner One-liner Boolean Boolean Boolean
5 40 20 40 80 2 4 12 12 2 10000000 500 2 2 2
Boolean Boolean
2 2
ARIS Methods
11-1398
Attribute Type Name Search privilege for Pos1 of all superior OU's of the current user Search privilege for Pos1 of the OU of the current user Secondary key Secondary quantity Semantics Service name Serviceable life Services Session mode Shift duration Short description Short text Shortcut Significance Significance Since/on Size Size in KBytes Skipping allowed Source Space Specification
Basic Type Boolean
Maximum Length 2
Boolean
Boolean N-liner N-liner N-liner Combined N-liner Value Duration N-liner N-liner One-liner Integer domain Value Date One-liner Integer Boolean N-liner One-liner N-liner
2 100 10000000 20 100 10000000 30 30 80 20 20 3 20 20 32000 40 2 100 600 200
ARIS Methods
11-1399
Attribute Type Name Specification SQL name Staff position Standard COT Start Start after instance creation Start date Start of complaint Start of interruption Start step Start time Start time after instance creation Startup capacity Static Static wait time Static wait time sum Status Status Status (CMA) Status bar Stereotype Storage group Storage mode
Basic Type One-liner One-liner Boolean Boolean Date N-liner Date Point in time Point in time Boolean Point in time Duration Integer Boolean Longtext Duration Value Value Value One-liner N-liner N-liner Value
Maximum Length 1000 32 2 2 20 20 20 20 20 2 20 20 10 2 50 30 20 512 20 100 256 100 512
ARIS Methods
11-1400
Attribute Type Name Storage type Structural change speed Subject Subject to management in batches Sum of interruption time while orienting Sum of interruption time while processing Synchronization time Synchronization type Synonyms System-external System-internal Tabindex Target Target language Target time period Target value Task duration Technical operating supply number Telephone number Template Terms/Abbreviations Text
Basic Type Value Integer domain N-liner Boolean
Maximum Length 512 3 80 2
Duration Duration Longtext Value N-liner Boolean Boolean Integer N-liner One-liner One-liner Floating point number Combined One-liner
8 8 30 20 512 2 2 10 10000000 500 20 20 20 100
N-liner Link/File N-liner N-liner
512 512 500 10000000
ARIS Methods
11-1401
Attribute Type Name Text 1 Text 2 Text 3 Throughput/avg. access Time Time expression Time expression language Time keys Time last used Time limit calculation Time limit with fixed date calc. Time of folder event Time of generation Time of generation (SAP) Title Title Title 1 Title 2 Title 3 Title 4 Title/Name To be completed by Tolerance administration Tolerance control
Basic Type N-liner N-liner N-liner Integer One-liner N-liner One-liner Boolean Point in time N-liner Integer Point in time Point in time Point in time N-liner N-liner N-liner N-liner N-liner N-liner One-liner Date Integer Integer
Maximum Length 255 255 255 12 32 10000000 500 2 20 256 4 20 20 20 200 64 100 100 100 100 50 20 3 3
ARIS Methods
11-1402
Attribute Type Name Tolerance decision Tolerance default processing Tolerance executive management Tolerance individual processing Tolerance range Tolerance sales Top margin Total time Total time Transaction code Transient Transmission medium Transmission speed Transmission type, batch Transmission type, manually Transmission type, online Transport instruction/rule Transport system number Trigger Trigger Trigger function Trigger to be released
Basic Type Integer Integer Integer
Maximum Length 3 3 3
Integer Floating point number Integer Boolean Combined N-liner N-liner Boolean One-liner One-liner Boolean Boolean
3 20 3 2 20 20 10000000 2 100 50 2 2
Boolean One-liner One-liner Boolean N-liner Boolean N-liner
2 100 100 2 10000000 2 1024
ARIS Methods
11-1403
Attribute Type Name Type Type Type Type Type 1 Type 2 Type 3 Type 4 Type 5 Type 6 Type 7 Type of aggregation Type of origin UML Action type UML Class type UML Event type UML Function type UML Service type Unit Unit for date calculation Unit of capacity Updating frequency Upper limit Usage factor Usage time sum
Basic Type Item type N-liner Value Value One-liner One-liner One-liner One-liner One-liner One-liner One-liner One-liner Value Value Value Value Value Value One-liner Value One-liner Value Floating point number Floating point number Duration
Maximum Length 50 256 10 512 2 2 2 2 2 2 2 50 512 50 50 50 50 50 15 20 100 15 20 30 20
ARIS Methods
11-1404
Attribute Type Name Usage type User attribute Boolean 1 User attribute Boolean 10 User attribute Boolean 11 User attribute Boolean 12 User attribute Boolean 13 User attribute Boolean 14 User attribute Boolean 15 User attribute Boolean 16 User attribute Boolean 17 User attribute Boolean 18 User attribute Boolean 19 User attribute Boolean 2 User attribute Boolean 20 User attribute Boolean 21 User attribute Boolean 22 User attribute Boolean 23 User attribute Boolean 24 User attribute Boolean 25 User attribute Boolean 26 User attribute Boolean 27 User attribute Boolean 28 User attribute Boolean 29 User attribute Boolean 3 User attribute Boolean 30
Basic Type Value Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean
Maximum Length 10 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
ARIS Methods
11-1405
Attribute Type Name User attribute Boolean 31 User attribute Boolean 32 User attribute Boolean 33 User attribute Boolean 34 User attribute Boolean 35 User attribute Boolean 36 User attribute Boolean 37 User attribute Boolean 38 User attribute Boolean 39 User attribute Boolean 4 User attribute Boolean 40 User attribute Boolean 41 User attribute Boolean 42 User attribute Boolean 43 User attribute Boolean 44 User attribute Boolean 45 User attribute Boolean 46 User attribute Boolean 47 User attribute Boolean 48 User attribute Boolean 49 User attribute Boolean 5 User attribute Boolean 50 User attribute Boolean 6 User attribute Boolean 7 User attribute Boolean 8
Basic Type Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean
Maximum Length 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
ARIS Methods
11-1406
Attribute Type Name User attribute Boolean 9 User attribute Date 1 User attribute Date 10 User attribute Date 2 User attribute Date 3 User attribute Date 4 User attribute Date 5 User attribute Date 6 User attribute Date 7 User attribute Date 8 User attribute Date 9 User attribute Duration 1 User attribute Duration 10 User attribute Duration 2 User attribute Duration 3 User attribute Duration 4 User attribute Duration 5 User attribute Duration 6 User attribute Duration 7 User attribute Duration 8 User attribute Duration 9 User attribute Float 1 User attribute Float 10 User attribute Float 11 User attribute Float 12
Basic Type Boolean Date Date Date Date Date Date Date Date Date Date Duration Duration Duration Duration Duration Duration Duration Duration Duration Duration Floating point number Floating point number Floating point number Floating point number
Maximum Length 2 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 5 5 5 5
ARIS Methods
11-1407
Attribute Type Name User attribute Float 13 User attribute Float 14 User attribute Float 15 User attribute Float 16 User attribute Float 17 User attribute Float 18 User attribute Float 19 User attribute Float 2 User attribute Float 20 User attribute Float 21 User attribute Float 22 User attribute Float 23 User attribute Float 24 User attribute Float 25 User attribute Float 26 User attribute Float 27 User attribute Float 28 User attribute Float 29 User attribute Float 3 User attribute Float 30 User attribute Float 31 User attribute Float 32 User attribute Float 33 User attribute Float 34 User attribute Float 35
Basic Type Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number
Maximum Length 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
ARIS Methods
11-1408
Attribute Type Name User attribute Float 36 User attribute Float 37 User attribute Float 38 User attribute Float 39 User attribute Float 4 User attribute Float 40 User attribute Float 41 User attribute Float 42 User attribute Float 43 User attribute Float 44 User attribute Float 45 User attribute Float 46 User attribute Float 47 User attribute Float 48 User attribute Float 49 User attribute Float 5 User attribute Float 50 User attribute Float 6 User attribute Float 7 User attribute Float 8 User attribute Float 9 User attribute Functional cluster User attribute Int 1 User attribute Int 10
Basic Type Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number N-liner Integer Integer
Maximum Length 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 10000000 5 5
ARIS Methods
11-1409
Attribute Type Name User attribute Int 11 User attribute Int 12 User attribute Int 13 User attribute Int 14 User attribute Int 15 User attribute Int 16 User attribute Int 17 User attribute Int 18 User attribute Int 19 User attribute Int 2 User attribute Int 20 User attribute Int 21 User attribute Int 22 User attribute Int 23 User attribute Int 24 User attribute Int 25 User attribute Int 26 User attribute Int 27 User attribute Int 28 User attribute Int 29 User attribute Int 3 User attribute Int 30 User attribute Int 31 User attribute Int 32 User attribute Int 33
Basic Type Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer
Maximum Length 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
ARIS Methods
11-1410
Attribute Type Name User attribute Int 34 User attribute Int 35 User attribute Int 36 User attribute Int 37 User attribute Int 38 User attribute Int 39 User attribute Int 4 User attribute Int 40 User attribute Int 41 User attribute Int 42 User attribute Int 43 User attribute Int 44 User attribute Int 45 User attribute Int 46 User attribute Int 47 User attribute Int 48 User attribute Int 49 User attribute Int 5 User attribute Int 50 User attribute Int 6 User attribute Int 7 User attribute Int 8 User attribute Int 9 User attribute Link
Basic Type Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Link/File
Maximum Length 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 256
ARIS Methods
11-1411
Attribute Type Name User attribute Point in time 1 User attribute Point in time 10 User attribute Point in time 2 User attribute Point in time 3 User attribute Point in time 4 User attribute Point in time 5 User attribute Point in time 6 User attribute Point in time 7 User attribute Point in time 8 User attribute Point in time 9 User attribute Text 1 User attribute Text 10 User attribute Text 100 User attribute Text 101 User attribute Text 102 User attribute Text 103 User attribute Text 104
Basic Type Point in time
Maximum Length 256
Point in time Point in time Point in time
256 256 256
Point in time Point in time Point in time Point in time
256 256 256 256
Point in time Point in time N-liner N-liner N-liner N-liner N-liner N-liner N-liner
256 256 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1412
Attribute Type Name User attribute Text 105 User attribute Text 106 User attribute Text 107 User attribute Text 108 User attribute Text 109 User attribute Text 11 User attribute Text 110 User attribute Text 111 User attribute Text 112 User attribute Text 113 User attribute Text 114 User attribute Text 115 User attribute Text 116 User attribute Text 117 User attribute Text 118 User attribute Text 119 User attribute Text 12 User attribute Text 120 User attribute Text 121 User attribute Text 122 User attribute Text 123 User attribute Text 124 User attribute Text 125 User attribute Text 126 User attribute Text 127
Basic Type N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1413
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1414
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1415
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1416
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1417
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1418
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000
ARIS Methods
11-1419
Attribute Type Name User attribute Text 82 User attribute Text 83 User attribute Text 84 User attribute Text 85 User attribute Text 86 User attribute Text 87 User attribute Text 88 User attribute Text 89 User attribute Text 9 User attribute Text 90 User attribute Text 91 User attribute Text 92 User attribute Text 93 User attribute Text 94 User attribute Text 95 User attribute Text 96 User attribute Text 97 User attribute Text 98 User attribute Text 99 User attribute Time 1 User attribute Time 10 User attribute Time 2 User attribute Time 3 User attribute Time 4 User attribute Time 5
Basic Type N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner Time Time Time Time Time Time
Maximum Length 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 10000000 256 256 256 256 256 256
ARIS Methods
11-1420
Attribute Type Name User attribute Time 6 User attribute Time 7 User attribute Time 8 User attribute Time 9 User attribute Values 1 User attribute Values 10 User attribute Values 11 User attribute Values 12 User attribute Values 13 User attribute Values 14 User attribute Values 15 User attribute Values 16 User attribute Values 17 User attribute Values 18 User attribute Values 19 User attribute Values 2 User attribute Values 20 User attribute Values 21 User attribute Values 22 User attribute Values 23 User attribute Values 24 User attribute Values 25 User attribute Values 26 User attribute Values 27 User attribute Values 28
Basic Type Time Time Time Time Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value
Maximum Length 256 256 256 256 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
ARIS Methods
11-1421
Attribute Type Name User attribute Values 29 User attribute Values 3 User attribute Values 30 User attribute Values 31 User attribute Values 32 User attribute Values 33 User attribute Values 34 User attribute Values 35 User attribute Values 36 User attribute Values 37 User attribute Values 38 User attribute Values 39 User attribute Values 4 User attribute Values 40 User attribute Values 41 User attribute Values 42 User attribute Values 43 User attribute Values 44 User attribute Values 45 User attribute Values 46 User attribute Values 47 User attribute Values 48 User attribute Values 49 User attribute Values 5 User attribute Values 50
Basic Type Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value Value
Maximum Length 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
ARIS Methods
11-1422
Attribute Type Name User attribute Values 51 User attribute Values 52 User attribute Values 53 User attribute Values 54 User attribute Values 55 User attribute Values 56 User attribute Values 57 User attribute Values 58 User attribute Values 59 User attribute Values 6 User attribute Values 60 User attribute Values 7 User attribute Values 8 User attribute Values 9 User exit Valid from Valid until Validity Value Value Value Value (CDU) Value (logical) Value (numeric) Value 1
Basic Type Value Value Value Value Value Value Value Value Value Value Value Value Value Value One-liner Date Date N-liner N-liner N-liner One-liner Floating point number Boolean Floating point number N-liner
Maximum Length 20 20 20 20 20 20 20 20 20 20 20 20 20 20 2 20 20 1000 10000000 80 100 20 2 10 2000
ARIS Methods
11-1423
Attribute Type Name Value 2 Value language Variations View Visibility Wait time Wait time sum Warehouse equip. number With complaint Workflow Workflow class Workflow domain WPDL-external attribute list
Basic Type N-liner One-liner N-liner Value Value Combined Combined One-liner Boolean One-liner Boolean N-liner N-liner
Maximum Length 2000 500 10000000 50 20 20 10 100 2 2 2 256 512
11.4.2
Domain: Integer and Floating Point Numbers

Lower Limit 0 0 0 0 0 Upper limit 10000000 100 100 2147483647 100 Default 10000000 100 100 2147483647 100
Attribute Type Name Capacity Degree of coverage Desired degree of coverage Duration Knowledge advantage
ARIS Methods
11-1424
Attribute Type Name Knowledge usage Number of employees Priority Probability Processes to be processed SAP Degree of coverage Significance Structural change speed
Lower Limit 0 1 0 0 1
Upper limit 100 10000000 9 1 10000000
Default 100 10000000 9 1 10000000
0 0 0
100 100 100
100 100 100
11.4.3
Attribute Type Groups
Attribute Type Name Absolute time limits Access type Acquisition costs Activity-based cost calculation Actual data ALE Analysis attributes ARIS Applications Attributes
ARIS Methods
11-1425
Attributes of external system Balanced Scorecard Benchmarking Bitmap Business control Capacity Certification Change management Cleaning cycle Column Cost driver quantity units Costs Costs for depreciation/repair/maintenance Costs per cost driver quantity unit Current cost for computer center Derived attribute type Development costs Development effort Energy costs Evaluation Event classification Expense External applications Font format Frame Free attribute type group 1
ARIS Methods
11-1426
Free attribute type group 2 Free attribute type group 3 Free attribute type group 4 Free attribute type group 5 Free attributes Frequency Function category Function type Function use Imputed interest Initial wait time Installation status Maintenance cycle Material costs No. of occurrences Occurrence Operating supplies costs Orientation time Origin Other costs Period of validity Personnel costs PIP Privileges Processing time Processing type
ARIS Methods
11-1427
Production capacity Project management attributes Promet(r)BPR Quantity structure Redocumentation Scout Relative time limits Revenues SAP Attributes Simulation Sources used System attributes Target data Throughput time Time limits Times Tolerance Total costs Total time Transmission time Transmission type Type of organizational unit UML Action state UML Actor UML Attribute UML Event UML Node
ARIS Methods
11-1428
UML Node instance UML Operation UML State UML Use case Validity Various overhead costs Volume Wait time Workflow
ARIS Methods
11.5 Hidable/Displayable Model Types
11-1429

Source Model Type Name Access diagram BSC Cause-and-effect diagram BSC Cause-and-effect diagram CD Diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Class diagram Cost driver Cluster/Data model Cluster/Data model Entity type Entity type ERM attribute ERM attribute Event Event Function Function Generalization type Generalization type Objective Hardware component type Critical factor Program structure chart Key performance indicator allocation diagram Key performance indicator allocation diagram CD Diagram Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Object Type Assigned Model Type
ARIS Methods
11-1430
Source Model Type Name Class diagram Class diagram Class diagram Class diagram Cost category diagram DTD DTD DTD DTD eEPC eEPC eEPC
Object Type Relationship type Relationship type Technical term Technical term Cost category Element type Enumeration attribute type Sequence XOR Application system Application system class Application system type
Assigned Model Type Class diagram eERM attribute allocation diagram Class diagram eERM attribute allocation diagram Cost category diagram DTD DTD DTD DTD Function allocation diagram Function allocation diagram Function allocation diagram
Authorization condition Entity type Event Event Function
Function allocation diagram Function allocation diagram Event diagram Function allocation diagram Function allocation diagram
ARIS Methods
11-1431
Source Model Type Name eEPC eEPC
Object Type Group Hardware component type
Assigned Model Type Function allocation diagram Function allocation diagram
eEPC eEPC eEPC eEPC
Information carrier IT function IT function type Location
eEPC eEPC eEPC
Module Module type Organizational unit
eEPC eEPC eEPC
eEPC eEPC
Position Rule
ARIS Methods
11-1432
Source Model Type Name eEPC eEPC (column display)
Object Type Screen Application system
Application system class Application system type Authorization condition Entity type
Event Event
Event diagram Function allocation diagram
Function Group Hardware component type
ARIS Methods
11-1433
Source Model Type Name eEPC (column display) eEPC (column display)
Object Type Location Module
Module type Organizational unit Organizational unit type Person
Person type Position Rule
eEPC (column display) eEPC (instance) eEPC (instance)
Screen Application system Application system type
Function allocation diagram Function allocation diagram (instance) Function allocation diagram (instance)
eEPC (instance) eEPC (instance)
Cluster instance Complex object
Function allocation diagram (instance) Function allocation diagram (instance)
ARIS Methods
11-1434
Source Model Type Name eEPC (instance) eEPC (instance)
Object Type COT attribute (instance) Employee variable
Assigned Model Type Function allocation diagram (instance) Function allocation diagram (instance)
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Entity ERM attribute instance Event instance Function instance
Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
Group Information carrier IT function
IT function type Module Module type
eEPC (instance) eEPC (instance)
Organizational unit Organizational unit type
Function allocation diagram (instance) Function allocation diagram (instance)
ARIS Methods
11-1435
Source Model Type Name eEPC (instance) eEPC (instance)
Object Type Person Person type
Assigned Model Type Function allocation diagram (instance) Function allocation diagram (instance)
eEPC (instance) eEPC (instance) eEPC (instance) eEPC (instance)
Position Relationship Rule instance Technical terms instance
Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance) Function allocation diagram (instance)
Application system Application system type Authorization condition
Entity type Event Event Function Group
Function allocation diagram Event diagram Function allocation diagram Function allocation diagram Function allocation diagram
ARIS Methods
11-1436
Source Model Type Name eEPC (material flow) eEPC (material flow)
Object Type Hardware component type Information carrier
IT function IT function type Location Material type
Module Module type Operating resource
Operating resource type Organizational unit Organizational unit type
Person Person type
ARIS Methods
11-1437
Source Model Type Name eEPC (material flow) eEPC (material flow)
Object Type Position Rule
Screen Technical operating supply Technical operating supply type Transport system
Transport system type Warehouse equipment Warehouse equipment type
Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Event diagram Function allocation diagram Function allocation diagram Function allocation diagram
eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display)
Authorization condition Event Function Group Hardware component type
ARIS Methods
11-1438
Source Model Type Name eEPC (row display) eEPC (row display)
Object Type Location Organizational unit
eEPC (row display) eEPC (row display) eEPC (row display) eEPC (row display)
Organizational unit type Person Person type Position
ARIS Methods
11-1439
Source Model Type Name eEPC (table display) eEPC (table display)
Module Module type Organizational unit
Position Rule
ARIS Methods
11-1440
Source Model Type Name eEPC (table display) eERM eERM eERM
Object Type Screen Cluster/Data model Cluster/Data model Entity type
Assigned Model Type Function allocation diagram eERM eERM attribute allocation diagram eERM attribute allocation diagram
eERM eERM eERM eERM eERM eERM eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram Event diagram
ERM attribute ERM attribute Generalization type Generalization type Relationship type Relationship type Attribute type group
eERM eERM attribute allocation diagram eERM eERM attribute allocation diagram eERM eERM attribute allocation diagram eERM attribute allocation diagram
Enumeration ERM attribute Generalization type
eERM attribute allocation diagram eERM attribute allocation diagram eERM attribute allocation diagram
Measurement unit number Event
eERM attribute allocation diagram Event diagram
ARIS Methods
11-1441
Source Model Type Name Event diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram Function tree Function tree IE Data model
Object Type Rule Function Hardware component type Hardware component type
Assigned Model Type Event diagram Value-added chain diagram eEPC eEPC (column display)
eEPC (material flow) eEPC (row display) eEPC (table display) PCD
Hardware component type Function Function Cluster/Data model
PCD (material flow) Function tree SAP ALE function model eERM attribute allocation diagram
IE Data model IE Data model Industrial process
Entity type Generalization type Application system type
eERM attribute allocation diagram eERM attribute allocation diagram Function allocation diagram
ARIS Methods
11-1442
Source Model Type Name Industrial process Industrial process
Object Type Entity type Event
Function Group Information carrier Organizational unit
Rule Screen Technical term
Key performance indicator tree Objective diagram
Key performance indicator instance Critical factor
Key performance indicator tree Objective diagram
ARIS Methods
11-1443
Source Model Type Name Objective diagram Office process Office process Office process
Object Type Objective Application system type Entity type Event
Assigned Model Type Objective diagram Function allocation diagram Function allocation diagram Function allocation diagram
Function Group Information carrier Organizational unit
Rule Screen Technical term
ARIS Methods
11-1444
Source Model Type Name OMT Class description model OMT Dynamic model OMT Object model OMT Object model
Object Type Class State Association Class
Assigned Model Type OMT Class description model OMT Dynamic model OMT Class description model OMT Class description model
OMT Object model OMT Object model OMT Object model Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart PCD
Constraint Object instance Sp./gen. operator Group Location Organizational unit Organizational unit type Person Position System organizational unit System organizational unit type Application system
OMT Class description model OMT Class description model OMT Class description model Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Organizational chart Function allocation diagram
PCD
ARIS Methods
11-1445
Source Model Type Name PCD PCD
Object Type Application system type Authorization condition
Entity type Event Event Function Group Hardware component type
Function allocation diagram Event diagram Function allocation diagram Function allocation diagram Function allocation diagram Function allocation diagram
PCD PCD PCD
PCD PCD PCD
Location Module Module type
ARIS Methods
11-1446
Source Model Type Name PCD PCD
Object Type Organizational unit Organizational unit type
PCD PCD PCD PCD
Person Person type Position Rule
PCD PCD (material flow) PCD (material flow)
Screen Application system Application system type
ARIS Methods
11-1447
Source Model Type Name PCD (material flow) PCD (material flow)
Material type Module Module type
Operating resource Operating resource type Organizational unit
Organizational unit type Person
ARIS Methods
11-1448
Source Model Type Name PCD (material flow) PCD (material flow)
Object Type Person type Position
Rule Screen Technical operating supply Technical operating supply type
Transport system Transport system type Warehouse equipment
PCD (material flow) Product tree Program structure chart Quick model SAP ALE filter model SAP ALE function model SAP ALE message flow model
Warehouse equipment type Product/Service Hardware component type Quick object Function Function Function
Function allocation diagram Product tree Access diagram Quick model SAP ALE filter model SAP ALE function model SAP ALE message flow model
ARIS Methods
11-1449
Source Model Type Name Structuring model Technical terms model UML Class diagram
Object Type Structural element Technical term Class
Assigned Model Type Structuring model Technical terms model UML Class description diagram
Value-added chain diagram
Function
ARIS Methods
11.6 Number of Possible Assignments
11-1450

Object Type Name Application system type Application system type Assignable Model Type Access diagram Application system type diagram Application system type Application system type Application system type Application system type Application system type Application system type Application system type Application system class Application system class Application system class Attribute Graphical user interface type Operating system type Relationship type Relationship type Relationship type Relationship type Quick model eERM attribute allocation diagram Class diagram Quick model DTD Unique Multiple Unique Multiple Unique Application system diagram Program structure chart UML Class diagram UML Component diagram Program flow-chart (PF) Quick model Screen navigation Application system type diagram Program flow-chart (PF) Quick model Quick model Quick model Unique Multiple Multiple Multiple Multiple Unique Unique Unique Multiple Unique Multiple Multiple Number Assignments Multiple Multiple
ARIS Methods
11-1451
Object Type Name Relationship type System organizational unit System organizational unit System organizational unit System organizational unit System organizational unit type System organizational unit type System organizational unit type System organizational unit type Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model Cluster/Data model
Assignable Model Type Screen design Organizational chart Knowledge map Authorization map Quick model Organizational chart Knowledge map Authorization map Quick model
Number Assignments Unique Unique Unique Unique Multiple Unique Unique Unique Multiple
eERM SAP SERM Attribute allocation diagram OMT Object model IE Data model Class diagram SeDaM model UML Class diagram DW - structure Quick model DTD Screen design
Unique Unique Unique Unique Multiple Unique Unique Unique Unique Multiple Unique Unique
ARIS Methods
11-1452
Object Type Name DBMS type Domain Entity type Entity type Entity type Entity type Entity type Entity type Entity type Entity type Event Event Event
Assignable Model Type Quick model Quick model eERM attribute allocation diagram Attribute allocation diagram Class diagram System attributes DW - structure Quick model DTD Screen design Event diagram System attributes Process instantiation model
Number Assignments Multiple Multiple Unique Unique Unique Unique Unique Multiple Unique Unique Unique Unique Multiple
Event ERM attribute ERM domain Field Field Function Function Function
Quick model Quick model Quick model Table diagram Quick model Screen diagram Value-added chain diagram eEPC
Multiple Multiple Multiple Unique Multiple Multiple Unique Multiple
ARIS Methods
11-1453
Object Type Name Function
Assignable Model Type Function allocation diagram
Number Assignments Unique
Function Function Function Function Function Function Function Function Function Function Function Function Function
Information flow diagram PCD Function tree Process selection matrix SAP applications diagram Objective diagram System attributes eEPC (material flow) PCD (material flow) Program structure chart SAP ALE function model SAP ALE filter model SAP ALE message flow model
Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique
Function Function Function Function Function Function Function Function Function
Material flow diagram Business controls diagram Office process Industrial process UML Use case diagram UML Activity diagram UML Collaboration diagram eEPC (column display) Program flow-chart (PF)
Unique Unique Unique Unique Unique Unique Multiple Multiple Unique
ARIS Methods
11-1454
Object Type Name Function Function Function Function
Assignable Model Type eEPC (row display) Process selection diagram Role diagram E-Business scenario diagram
Number Assignments Multiple Unique Unique Multiple
Function Function Function Function Function Function Function Generalization type Generalization type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component type Hardware component class Information flow Information flow
BSC Cause-and-effect diagram DW - transformation eEPC (table display) RAD Quick model Screen design UML Sequence diagram eERM attribute allocation diagram Quick model Function allocation diagram Access diagram Access diagram (physical) Program structure chart Quick model Quick model eERM SAP SERM
Multiple Unique Multiple Unique Multiple Unique Multiple Unique Multiple Unique Unique Unique Unique Multiple Multiple Unique Unique
ARIS Methods
11-1455
Object Type Name Information flow Information flow Information flow Information flow Information flow Information flow Information flow Information flow Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Information carrier Main process List Draft list Screen Screen
Assignable Model Type Relations diagram Table diagram Technical terms model IE Data model Class diagram SeDaM model UML Class diagram Quick model eERM SAP SERM Relations diagram Table diagram Technical terms model System attributes SeDaM model Information carrier diagram UML Class diagram Quick model Screen navigation Quick model Quick model Quick model Screen diagram eERM
Number Assignments Unique Unique Unique Unique Unique Unique Unique Multiple Unique Unique Unique Unique Unique Unique Unique Unique Unique Multiple Unique Multiple Multiple Multiple Unique Unique
ARIS Methods
11-1456
Object Type Name Screen Screen Screen Screen Screen Screen Screen Screen Screen design Screen design Screen design Screen design Screen design Classification criterion Object type class Module type Module type Module type Module type Module type Module type Module class Network type Network type
Assignable Model Type SAP SERM Technical terms model IE Data model SeDaM model UML Class diagram Quick model Screen design Screen navigation eERM SAP SERM IE Data model SeDaM model Quick model Quick model Quick model Access diagram Application system type diagram Program structure chart UML Class diagram Quick model Screen navigation Quick model Network topology Quick model
Number Assignments Unique Unique Unique Unique Unique Multiple Unique Unique Unique Unique Unique Unique Multiple Multiple Multiple Unique Unique Unique Unique Multiple Unique Multiple Unique Multiple
ARIS Methods
11-1457
Object Type Name Network node type Network class Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Position
Assignable Model Type Quick model Quick model Organizational chart Network topology Network diagram Process selection matrix System attributes Communications diagram Shift calendar Knowledge map Process selection diagram Authorization map BSC Cause-and-effect diagram Quick model Organizational chart Process selection matrix Communications diagram Knowledge map Process selection diagram Authorization map BSC Cause-and-effect diagram Quick model Organizational chart
Number Assignments Multiple Multiple Unique Unique Unique Unique Unique Unique Multiple Unique Unique Unique Multiple Multiple Unique Unique Unique Unique Unique Unique Multiple Multiple Unique
ARIS Methods
11-1458
Object Type Name Position Position Position Position
Assignable Model Type Shift calendar Knowledge map Authorization map BSC Cause-and-effect diagram
Number Assignments Multiple Unique Unique Multiple
Position Person Person Person Person Person Person Domain (physical) Rule Rule Relation Relation Memory location Location Location Location Location Location
Quick model System attributes Shift calendar Knowledge map Authorization map BSC Cause-and-effect diagram Quick model Quick model Rule diagram Quick model Attribute allocation diagram Quick model Quick model Organizational chart Network topology Network diagram Knowledge map Authorization map
Multiple Unique Multiple Unique Unique Multiple Multiple Multiple Unique Multiple Unique Multiple Multiple Unique Unique Unique Unique Unique
ARIS Methods
11-1459
Object Type Name Location
Assignable Model Type BSC Cause-and-effect diagram
Number Assignments Multiple
Location Table Table View View Technical term Technical term Technical term Technical term Technical term Technical term Technical term Organizational level Organizational chart Organizational chart Application system Application system Application system Application system Module Module
Quick model Table diagram Quick model Relations diagram Quick model Relations diagram Attribute allocation diagram Technical terms model Class diagram System attributes Quick model DTD Quick model Organizational chart Quick model Access diagram (physical) Application system diagram Program flow-chart (PF) Quick model Access diagram (physical) Application system diagram
Multiple Unique Multiple Unique Multiple Unique Unique Unique Unique Unique Multiple Unique Multiple Unique Multiple Unique Unique Unique Multiple Unique Unique
ARIS Methods
11-1460
Object Type Name Module Program module type Program module Program library DBMS Programming language Operating system Tables (specimen) Field (specimen) View (physical) Hardware component Person type Person type Person type Person type Person type Person type Person type Network node Network connection type Network connection Material flow Material flow Network
Assignable Model Type Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Organizational chart Shift calendar Knowledge map Authorization map Role diagram BSC Cause-and-effect diagram Quick model Quick model Quick model Quick model Material diagram Quick model Network diagram
Number Assignments Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique Multiple Unique Unique Unique Multiple Multiple Multiple Multiple Multiple Unique Multiple Unique
ARIS Methods
11-1461
Object Type Name Network Objective Objective Objective Objective Objective Association Association Constraint Sp./gen. operator Class Class Class Class Class Class Class Class Class Class Class Class Class
Assignable Model Type Quick model Objective diagram Product/Service tree (graphic) Product/Service tree Key performance indicator allocation diagram Quick model eERM Quick model Quick model Quick model Screen diagram eERM SAP SERM Relations diagram Attribute allocation diagram eEPC Access diagram Access diagram (physical) Technical terms model OMT Dynamic model IE Data model SeDaM model Program structure chart
Number Assignments Multiple Unique Unique Unique Unique Multiple Unique Multiple Multiple Multiple Multiple Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique
ARIS Methods
11-1462
Object Type Name Class
Assignable Model Type OMT Class description model
Class Class Class Class Class Class Class Class Class Operation Object instance Process Process Data store Data store Actor Data value Data value
UML Class diagram UML Activity diagram UML Class description diagram UML Statechart diagram eEPC (column display) eEPC (row display) eEPC (table display) Quick model Screen design Quick model Quick model OMT Functional model Quick model OMT Object model Quick model Quick model OMT Object model OMT Data value decomposition
Multiple Unique Unique Unique Unique Unique Unique Multiple Unique Multiple Multiple Unique Multiple Unique Multiple Multiple Unique Unique
Data value State State Connector
Quick model OMT Dynamic model Quick model Quick model
Multiple Unique Multiple Multiple
ARIS Methods
11-1463
Object Type Name Index Network protocol IT function type IT function type
Assignable Model Type Quick model Quick model Access diagram Application system type diagram
Number Assignments Multiple Multiple Multiple Multiple
IT function type IT function type IT function type IT function type IT function type IT function type IT function class IT function class IT function IT function
Program structure chart UML Class diagram Program flow-chart (PF) Quick model Screen design Screen navigation Program flow-chart (PF) Quick model Access diagram (physical) Application system diagram
Multiple Unique Unique Multiple Unique Unique Unique Multiple Unique Unique
IT function IT function Critical factor Critical factor System attribute System attribute System attribute domain Attribute type group
Program flow-chart (PF) Quick model Key performance indicator allocation diagram Quick model System attribute domain Quick model Quick model Relations diagram
Unique Multiple Unique Multiple Unique Multiple Multiple Unique
ARIS Methods
11-1464
Object Type Name Attribute type group
Assignable Model Type Attribute allocation diagram
Attribute type group Operating resource class Warehouse equipment class Transport system class Tech. operating supply class Operating resource type Operating resource type Warehouse equipment type Transport system type Technical operating supply type Operating resource Operating resource Warehouse equipment Warehouse equipment Transport system Transport system Technical operating supply Technical operating supply Material class Packaging material class
Quick model Quick model Quick model Quick model Quick model Technical resources Quick model Quick model
Multiple Multiple Multiple Multiple Multiple Unique Multiple Multiple
Quick model Quick model
Multiple Multiple
Shift calendar Quick model Shift calendar Quick model Shift calendar Quick model Shift calendar Quick model Quick model Quick model
Unique Multiple Unique Multiple Unique Multiple Unique Multiple Multiple Multiple
ARIS Methods
11-1465
Object Type Name Material type Packaging material type Group Group Group Group Group
Assignable Model Type Quick model Quick model Organizational chart Shift calendar Knowledge map Authorization map BSC Cause-and-effect diagram
Number Assignments Multiple Multiple Unique Multiple Unique Unique Multiple
Group Association instance Communication Communication Communication Communication Communication Communication Communication Communication Communication Communication Cost category Filter object type Message flow Message flow
Quick model Quick model SAP SERM Process selection matrix IE Data model Class diagram SeDaM model UML Class diagram Process selection diagram DW - structure Quick model DTD Quick model Quick model SAP ALE message type model Quick model
Multiple Multiple Multiple Unique Multiple Multiple Multiple Multiple Unique Multiple Multiple Multiple Multiple Multiple Unique Multiple
ARIS Methods
11-1466
Object Type Name Function instance Function instance Function instance Function instance Cluster instance Cluster instance Entity Relationship Technical terms instance ERM attribute instance Event instance Message type General resource Business object Business object Business object
Assignable Model Type eEPC (instance) PPC Function allocation diagram (instance) Quick model Information carrier diagram Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model SAP SERM Relations diagram Attribute allocation diagram
Number Assignments Unique Unique Unique Multiple Unique Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique Unique Unique
Business object Employee variable Employee variable Employee variable Rule instance Product/Service
Quick model Knowledge map Authorization map Quick model Quick model Value-added chain diagram
Multiple Unique Unique Multiple Multiple Unique
ARIS Methods
11-1467
Object Type Name Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service
Assignable Model Type eEPC Function tree Process selection matrix eEPC (material flow) Product/Service exchange diagram (graphic) Product/Service tree (graphic)
Number Assignments Unique Unique Unique Unique Unique Unique
Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Product/Service Performance characteristic Transaction folder Risk
Product tree Product selection matrix Office process Product allocation diagram Competition model Industrial process UML Statechart diagram Product/Service tree Product/Service exchange diagram eEPC (column display) eEPC (row display) Process selection diagram eEPC (table display) Quick model Quick model Quick model Quick model
Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Unique Multiple Multiple Multiple Multiple
ARIS Methods
11-1468
Object Type Name Solution Control Page Page Section Section Column Column Bitmap Text Separator Layout Enumeration list occurrence Enumeration Measurement unit COT attribute COT attribute (instance) Complex object Complex object type Complex object type Complex object type Complex object type Complex object type
Assignable Model Type Quick model Quick model Screen diagram Quick model Screen diagram Quick model Screen diagram Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model eERM Relations diagram Attribute allocation diagram Quick model DTD
Number Assignments Multiple Multiple Unique Multiple Unique Multiple Unique Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique Unique Unique Multiple Unique
ARIS Methods
11-1469
Object Type Name Complex object type Screen table Screen table Parameter Measurement unit number Note Package Package Package Package Package Package Package Package Package
Assignable Model Type Screen design Screen diagram Quick model Quick model Quick model Quick model Relations diagram Attribute allocation diagram Application system type diagram UML Class diagram UML Component diagram UML Use case diagram UML Activity diagram UML Collaboration diagram UML Class description diagram
Number Assignments Unique Unique Multiple Multiple Multiple Multiple Unique Unique Unique Multiple Unique Unique Unique Unique Unique
Package Package Package Component Component Component
UML Statechart diagram Quick model DTD Access diagram Access diagram (physical) Application system type diagram
Unique Multiple Unique Unique Unique Unique
ARIS Methods
11-1470
Object Type Name Component
Assignable Model Type Application system diagram
Component Component Component Component Instantiation interval Instantiation cycle Instantiation plan Shift plan Shift cycle Shift Break Cost driver Knowledge category
Program structure chart UML Component diagram Program flow-chart (PF) Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Knowledge structure diagram
Unique Unique Unique Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique
Knowledge category Knowledge category Documented knowledge Structural element Structural element Structural element Structural element Structural element Structural element
Knowledge map Quick model Quick model Organizational chart Screen diagram Network topology Network diagram eERM SAP SERM
Unique Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1471
Object Type Name Structural element
Assignable Model Type eERM attribute allocation diagram
Relations diagram Attribute allocation diagram
Multiple Multiple
Table diagram Value-added chain diagram
Multiple Multiple
Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element
eEPC Function allocation diagram Information flow diagram Access diagram Access diagram (physical) PCD Function tree Application system type diagram Technical terms model Event diagram Rule diagram Function/organizational level diagram Process selection matrix Y diagram SAP applications diagram
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1472
Object Type Name Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element
Assignable Model Type Classification diagram Objective diagram Application system diagram OMT Object model OMT Dynamic model OMT Functional model IE Data model OMT Data value decomposition Class diagram System attributes System attribute domain SeDaM model Technical resources Material diagram eEPC (material flow) PCD (material flow) Communications diagram Program structure chart Cost category diagram OMT Class description model RAMS SAP ALE function model SAP ALE filter model
Number Assignments Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1473
Assignable Model Type SAP ALE message flow model
Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element
SAP ALE message type model eEPC (instance) Material flow diagram PPC Information carrier diagram Function allocation diagram (instance) Privileges diagram Business controls diagram Product/Service exchange diagram (graphic) Product/Service tree (graphic) Product tree Product selection matrix Office process Product allocation diagram Competition model Industrial process UML Class diagram UML Component diagram UML Use case diagram
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1474
Assignable Model Type Process instantiation model
Structural element Structural element Structural element Structural element Structural element
Shift calendar CD Diagram UML Activity diagram Input/Output diagram Knowledge structure diagram
Multiple Multiple Multiple Multiple Multiple
Structural element Structural element Structural element
Knowledge map UML Collaboration diagram UML Class description diagram
Multiple Multiple Multiple
Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element Structural element
UML Statechart diagram Product/Service tree Product/Service exchange diagram Structuring model eEPC (column display) Program flow-chart (PF) eEPC (row display) Process selection diagram E-Business scenario diagram BSC Cause-and-effect diagram eEPC (table display)
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1475
Object Type Name Structural element Structural element Structural element Structural element Structural element Structural element Strategy Loop start Authorization condition Authorization condition Perspective Key performance indicator instance Key performance indicator instance Security protocol Quick object Quick object Quick object Quick object Quick object Quick object Quick object
Assignable Model Type RAD Quick model DTD Screen design Screen navigation Key performance indicator tree Quick model Quick model Authorization hierarchy Quick model Quick model Quick model Key performance indicator tree Quick model Organizational chart Screen diagram Network topology Network diagram eERM SAP SERM eERM attribute allocation diagram
Number Assignments Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique Multiple Multiple Multiple Unique
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
Quick object
Relations diagram
Multiple
ARIS Methods
11-1476
Object Type Name Quick object
Assignable Model Type Attribute allocation diagram
Quick object Quick object
Table diagram Value-added chain diagram
Multiple Multiple
Quick object Quick object
eEPC Function allocation diagram
Multiple Multiple
Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object
Information flow diagram Access diagram Access diagram (physical) PCD Function tree Application system type diagram Technical terms model Event diagram Rule diagram Function/organizational level diagram Process selection matrix Y diagram SAP applications diagram Classification diagram Objective diagram
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1477
Assignable Model Type Application system diagram
Quick object Quick object Quick object Quick object Quick object
OMT Object model OMT Dynamic model OMT Functional model IE Data model OMT Data value decomposition
Multiple Multiple Multiple Multiple Multiple
Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object
Class diagram System attributes System attribute domain SeDaM model Technical resources Material diagram eEPC (material flow) PCD (material flow) Communications diagram Program structure chart Cost category diagram OMT Class description model RAMS SAP ALE function model SAP ALE filter model SAP ALE message flow model
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1478
Assignable Model Type SAP ALE message type model
Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object
eEPC (instance) Material flow diagram PPC Information carrier diagram Function allocation diagram (instance) Privileges diagram Business controls diagram Product/Service exchange diagram (graphic)
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object
Product/Service tree (graphic) Product tree Product selection matrix Office process Product allocation diagram Competition model Industrial process UML Class diagram UML Component diagram UML Use case diagram CD Diagram UML Activity diagram
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1479
Object Type Name Quick object Quick object Quick object Quick object Quick object
Assignable Model Type Input/Output diagram Knowledge structure diagram Knowledge map UML Collaboration diagram UML Class description diagram
Number Assignments Multiple Multiple Multiple Multiple Multiple
Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object
UML Statechart diagram Product/Service tree Product/Service exchange diagram Structuring model eEPC (column display) Program flow-chart (PF) eEPC (row display) Process selection diagram Authorization map Authorization hierarchy Role diagram E-Business scenario diagram
Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
Quick object Quick object Quick object
BSC Cause-and-effect diagram Key performance indicator allocation diagram DW - structure
Multiple Multiple Multiple
ARIS Methods
11-1480
Object Type Name Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Quick object Element type Element type Conditional section Contents Sequence XOR Enumeration attribute type Improvement potential Tool Text box Radio button/Check box Combo box Spin box
Assignable Model Type DW - transformation eEPC (table display) Input/Output diagram (inverse) RAD Quick model DTD c3 method Screen design Screen navigation Key performance indicator tree Quick model DTD Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model
Number Assignments Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Unique Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11-1481
Object Type Name Tree control List control Button Association class Extension point Enumeration literal Need Marketing instrument Distribution channel Subsystem UML Model
Assignable Model Type Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model Quick model UML Class diagram UML Class diagram
Number Assignments Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple Multiple
ARIS Methods
11.7 Classification of Models
11-1482

The layout of models is determined on the basis of symbol positions and the significance of relationships. Which symbols and relationships take on the central role depends on the model type. The allocations are listed in the following tables.
11.7.1
Class
Layout Classes
Description
Pure hierarchies consist of only one object type. The hierarchy relationship can be reflected by different connection types.
Pure Hierarchy (PH)
Pure Hierarchy with Allocation (HA)
Hierarchies with allocations represent trees that are made up of only one object type. The hierarchy relationship can be reflected by different connection types. Besides the hierarchy relationships, other object types can be assigned to the objects that make up the hierarchy.
Hierarchies with Crosslinks (HC) Hierarchies with crosslinks represent hierarchies that are made up of various object types. The hierarchy relationship can be reflected by different connection types. Besides the hierarchy relationships, the objects that make up the hierarchy can have relationships with each other, either directly or via other object types. Central Object Type (CO) Models with a central object type are used to represent relationships between this object type and other object types. Central Object Type with Priority (CP) Models with a central object type with priority are used to represent relationships between the central object type and other object types. Here the object type that has the highest priority in the current model occupies the central role. Directed Graph with Allocations (DG) Directed graphs with allocations are used to represent models in which specific object types make up a directional structure. These object types can have relationships with other object types. SAP SERM Layout A directed graph with assignments, where the direction in which the relationships are created does not match the direction of the model flow. This means that is supertype of relationships between entity type and generalization type, and is subtype of relationships between generalization type and entity type are both
ARIS Methods
11-1483
Class
Description
drawn from the entity type to the generalization, but the layout represents the relationship from entity type to generalization, and from generalization type to entity type.
11.7.2
Model
Assignment of Models to Layout Classes

Class Structurally Relevant / Central Objects (Priority)
Application system diagram
Hierarchies with Crosslinks
Application system (1), IT function (1), Program module type (3), Type program module (2), Module (1)
Application system type diagram Hierarchies with Crosslinks
Type IT function (2), Class IT function (1), Class application system (1), Class module (1), Type application system (2), Type module (2),
Attribute allocation diagram CD Diagram eEPC
Central Object Type with Priority Attribute (2), Relation (1) Pure Hierarchy Directed Graph with Allocations Cost Driver Process interface, Function target, All links, Function, Operation, System function target, Shift, System function actual, Event, Function actual
eEPC (instance)
Directed Graph with Allocations
All links (inst.), Event instance, Project guideline, Function instance
All links, Event, Process interface, Function target, Operation, System function actual, System function target, Function actual, Function
eERM
Non-directed Graph (ERM)
Generalization, Cluster, Reint. relationship type, Entity type
ARIS Methods
11-1484
Model
Class
Structurally Relevant / Central Objects (Priority)
eERM Attribute allocation diagram
Central Object Type with Priority Attribute type group (5), Generalization (3), FK attribute (ERM) (4), K attribute (ERM) (4), D attribute (ERM) (4), Reint. relationship type, Relationship type (2), Entity type (1)
Event diagram Technical terms model Function/Organizational level diagram Function tree Function allocation diagram Function allocation diagram (instance) Structuring model Graphical description
Hierarchy with Allocations Hierarchy with Allocations Central Object Type
Event, All links Technical term Organizational level
Pure Hierarchy Central Object Type Central Object Type
Function Object state, Function Function instance
Pure Hierarchy Directed Graph with Allocations
Structural element Line of work, Impulse, Abort icon, All links, Reflector
IEF data model
SAP SERM
Cluster, Generalization, Generalization, Generalization, Entity type, Generalization
Industrial process
Event, Function (manufacturing), Rule, Function (office), Object state
Class diagram
SAP SERM
Entity type, Relationship type, Reint. relationship type, Cluster, Technical term
Classification diagram Cost category diagram Material diagram
Central Object Type Pure Hierarchy Hierarchies with Crosslinks
Object type class Cost category Material type (1), Packaging materials class (4), Materials class (3), Packaging material type (2)
ARIS Methods
11-1485
Model
Class
Network diagram
HW component (1), Network (4), Network connection (3), Network node (2)
Network topology
Network connection type (5), Network node type (4), HW component type (2), HW component class(1), Network type (3)
Office process
Function (office), Event, Function (manufacturing), Rule
OMT Class description model OMT Dynamic model OMT Object model Organizational chart
Central Object Type Directed Graph with Alocations Hierarchy with Allocations Hierarchies with Crosslinks
Class State, Initial state, Final state Class System organizational unit type, System organizational unit, Location (5), Organizational unit type (1), Position (1), Organizational unit (1), System organizational unit type (7), System organizational unit (6), Position type, Cost center, Group (4)
PPC
All links, Event instance, Function instance, Project guideline
Product tree Process instantiation model
Pure Hierarchy Directed Graph with Allocations
Product Instantiation plan, Instantiation interval, Instantiation cycle
Privileges diagram
Central Object Type
Group, Person type, Organizational unit, Position, External person, Location, Organizational unit, Internal person,
Relations diagram
Non-directed Graph (ERM)
eERM domain, Relation, View
ARIS Methods
11-1486
Model
Class
SAP ALE filter model SAP ALE function model SAP SERM
Central Object Type Pure Hierarchy SAP SERM
Function Function Entity type, Cluster, Generalization, Business object, SAP SERM gen.
Shift calendar
Shift plan, Shift cycle, Shift, Break, Operation
SeDaM model
SAP SERM
Generalization, Entity type, Cluster
Table diagram Technical resources
Non-directed Graph (ERM) Hierarchy with Crosslinks
View (physical), Field, Table Operating resource (9), Technical operating supply class (4), Transport systems class (3), Warehouse equipment class (2), Operating resource class (1), Technical operating supplies (12), Warehouse equipment (10), Operating resource type (5), Transport systems type (7), Technical operating supplies type (8), Warehouse equipment type (6), Transport system (11)
Pure Hierarchy
Documented knowledge, Knowledge category
Objective diagram
Hierarchy with Crosslinks
Critical factor (2), Objective (1)
ARIS Methods
11.8 Implicit Relationships in Swimlane Models
11-1487

In the following swimlane models (models as column/row display) implicit
relationships are generated automatically. eEPC (column/row display) see page 11-1488 Input/Output diagram see page 11-1492 UML Activity diagram see page 11-1492 PCD see page 11-1493 PCD (material flow) see page 11-1493
ARIS Methods
11-1488
11.8.1
Implicit Relationships - eEPC as Column/Row Display
The following objects can have the listed implicit relationships within this model:
Source Object Type
Organizational unit Position Person Group Employee variable Organizational unit Position Person Group Organizational unit Position Person Group Employee variable Application system Organizational unit Position Person Group Employee variable Organizational unit type Person type Organizational unit type Person type
Implicit Relationship
is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for carries out carries out carries out carries out carries out supports is IT responsible for is IT responsible for is IT responsible for is IT responsible for is IT responsible for carries out carries out is IT responsible for is IT responsible for
Target Object Type

Function Function Function Function Function IT function type IT function type IT function type IT function type Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
ARIS Methods
11-1489
Source Object Type

Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Organizational unit type Position Position Position Person Person Person Person type Person type Person type Person type Person type Person type Person type Person type Group Group
is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for is technically responsible for
Target Object Type

Application system type Application system class Module type Application system type Application system class Function Module type Application system Module IT function type IT function Application system type Application system class Module type Application system type Application system class Module type Application system type Application system class Function Module type Application system Module IT function type IT function Application system type Application system class
ARIS Methods
11-1490
Source Object Type

Group Application system type Application system class Organizational unit Position Person Group Employee variable Organizational unit Position Person Group Employee variable Organizational unit Position Person Group Employee variable Organizational unit Position Person Group Employee variable Organizational unit Position Person Group
is technically responsible for can support can support decides on decides on decides on decides on decides on contributes to contributes to contributes to contributes to contributes to must inform about result of must inform about result of must inform about result of must inform about result of must inform about result of must be informed about must be informed about must be informed about must be informed about must be informed about
Target Object Type

Module type Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function Function
must be informed on cancellation Function must be informed on cancellation Function must be informed on cancellation Function must be informed on cancellation Function
ARIS Methods
11-1491
Source Object Type

Person type Person type Person type Person type Organizational unit type Person type Organizational unit Position Person Employee variable Organizational unit type Person type Group Organizational unit
decides on contributes to must inform about result of must be informed about carries out
Target Object Type

must be informed on cancellation Function has consulting role in has consulting role in has consulting role in has consulting role in has consulting role in has consulting role in has consulting role in accepts Function Function Function Function Function Function Function Function
ARIS Methods
11-1492
11.8.2
Implicit Relationships of the Input/Output Diagram
Source Object Type Implicit Relationship Target Object Type
Function Cluster/Data model Entity type ERM attribute Function Function Function Function Information carrier generates output to is input for is input for is input for has output of has output of has output of has output of provides input for Information carrier Function Function Function Relationship type Cluster/Data model Entity type ERM attribute Function
11.8.3
Implicit Relationships of the UML Activity Diagram
Organizational unit Position Person Group Person type carries out carries out carries out carries out carries out Function Function Function Function Function
ARIS Methods
11-1493
11.8.4
Implicit Relationships of the PCD
11.8.5
Implicit Relationships of the PCD (Material Flow)
ARIS Methods
11.9 Model Types (ModelTypeNum)
11-1494

Model Name Access diagram Access diagram (physical) Application system diagram Application system type diagram Attribute allocation diagram Authorization hierarchy Authorization map BSC Cause-and-effect diagram Business controls diagram Model Description Access diagram Access diagram (physical) Application system diagram Application system type diagram Attribute allocation diagram Authorization hierarchy Authorization map Balanced Scorecard - Cause-and-effect diagram Business controls diagram 145/MT_AUTH_HIER 144/MT_AUTH_MAP 149/MT_CAUSE_EFFECT_ DGM 79/MT_BUSY_CONTR_DG M c3 method CD Diagram Class diagram Classification diagram Communications diagram Competition model Cost category diagram DTD DW - structure c3 method Cost driver diagram Class diagram Classification diagram Communications diagram Competition model Cost category diagram Document type definition Data Warehouse structure diagram 161/MT_C3METHOD 118/MT_CD_DGM 44/MT_CLS_DGM 36/MT_CLSFC_DGM 54/MT_COMM_DGM 102/MT_COMP_FORCES 57/MT_COST_TYPE_DGM 160/MT_DTD 152/MT_DW_STRUC 21/MT_APPL_SYS_TYPE_D GM 10/MT_ATTR_ALLOC_DGM Type No. 16/MT_ACS_DGM 17/MT_ACS_DGM_PHYS 38/MT_APPL_SYS_DGM
ARIS Methods
11-1495
Model Name DW - transformation
Model Description Data Warehouse data transformation diagram
Type No. 153/MT_DW_TRANS
E-Business scenario diagram eEPC eEPC (column display)
E-Business scenario diagram Extended event-driven process chain Extended event-driven process chain as column display
147/MT_SCEN_DGM 13/MT_EEPC 134/MT_EEPC_COLUMN
eEPC (instance) eEPC (material flow)
Extended event-driven process chain (instance) Extended event-driven process chain with material flow
65/MT_EEPC_INST 50/MT_EEPC_MAT
eEPC (row display)
Extended event-driven process chain as row display
140/MT_EEPC_ROW
Extended event-driven process chain as table display
154/MT_EEPC_TAB
eERM
Extended entity relationship model
6/MT_EERM
eERM attribute allocation diagram Event diagram Function allocation diagram Function allocation diagram (instance)
eERM attribute allocation diagram Event diagram Function allocation diagram Function allocation diagram (instance)
8/MT_EERM_ATTR_ALLOC _DGM 23/MT_EV_DGM 14/MT_FUNC_ALLOC_DGM 72/MT_FUNC_ALLOC_DGM _INST
ARIS Methods
11-1496
Model Name Function tree Function/organizational level diagram IE Data model
Model Description Function tree Function/organizational level diagram Information engineering facility data model
Type No. 19/MT_FUNC_TREE 25/MT_FUNC_ORG_LVL_D GM 42/MT_IEF_DATA_MDL
Industrial process Information carrier diagram Information flow diagram Input/Output diagram Input/Output diagram (inverse) Key performance indicator allocation diagram Key performance indicator tree Knowledge map Knowledge structure diagram Material diagram Material flow diagram Network diagram Network topology Objective diagram Office process OMT Class description model
Industrial process Information carrier diagram Information flow diagram Input/Output diagram Input/Output diagram Key performance indicator allocation diagram Key performance indicator tree Knowledge map Knowledge structure diagram Material diagram Material flow diagram Network diagram Network topology Objective diagram Office process Class description model
103/MT_IND_PROC 70/MT_INFO_CARR_DGM
15/MT_INFO_FLW_DGM 125/MT_IN_OUT_DGM 155/MT_IN_OUT_DGM_2 150/MT_KPI_ALLOC_DGM 165/MT_KPI_TREE
127/MT_KNWLDG_MAP 126/MT_KNWLDG_STRCT _DGM 49/MT_MAT_DGM 66/MT_MAT_FLW_DGM 5/MT_NW_DGM 3/MT_NW_TOPLG 37/MT_OBJ_DGM 100/MT_OFFICE_PROC 59/MT_CLS_DESC_MDL
ARIS Methods
11-1497
Model Name OMT Data value decomposition OMT Dynamic model OMT Functional model OMT Object model Organizational chart PCD PCD (material flow) PPC Privileges diagram Process instantiation model Process selection diagram Process selection matrix Product allocation diagram Product selection matrix Product tree Product/Service exchange diagram Product/Service exchange diagram (graphic) Product/Service tree Product/Service tree (graphic)
Model Description Data value decomposition
Type No. 43/MT_DATA_VAL_DCMP
Dynamic model Functional model Object model Organizational chart Process chain diagram Process chain diagram with material flow Project process chain Privileges diagram Process instantiation model Process selection diagram Process selection matrix Product allocation diagram Product selection matrix Product tree Product/Service exchange diagram Product/Service exchange diagram (graphic) Product/Service tree Product/Service tree (graphic)
40/MT_DYN_MDL 41/MT_FUNC_MDL 39/MT_OBJ_MDL 1/MT_ORG_CHRT 18/MT_PRCS_CHN_DGM 51/MT_PCD_MAT 67/MT_PPC 73/MT_WRKFLW_RGHT_M AN 112/MT_PRCS_INST 141/MT_PRCS_SLCT_DIA 28/MT_PRCS_SLCT_MTX 101/MT_PRDCT_ALLOC_D GM 99/MT_PRDCT_SLCT_MTX 98/MT_PRDCT_TREE 132/MT_PROD_SERV_EXC H_DGM 93/MT_PERF_MAP 131/MT_PERFORM_TREE 96/MT_PERF_TREE
ARIS Methods
11-1498
Model Name Program flow-chart (PF) Program structure chart Quick model RAD RAMS Relations diagram Role diagram Rule diagram SAP ALE filter model SAP ALE function model
Model Description Program flow-chart (PF) Program structure chart Quick model Role assignment diagram Requirements analysis for management systems Relations diagram Role diagram Rule diagram SAP ALE filter model SAP ALE function model
Type No. 139/MT_PF 55/MT_PRG_STRCT_CHRT 158/MT_CASUALMOD 156/MT_RAD 60/MT_REQU_ANALY_MAN _SYS 9/MT_REL_DGM 146/MT_ROLE_DGM 24/MT_RULE_DGM 62/MT_SAP_ALE_FLTR_M DL 61/MT_SAP_ALE_FUNC_M DL
SAP ALE message flow model SAP ALE message type model SAP applications diagram SAP SERM Screen design Screen diagram Screen navigation SeDaM model Shift calendar Structuring model
SAP ALE message flow model SAP ALE message type model SAP applications diagram SAP structured entity relationship model Screen design Screen diagram Screen navigation Semantic data model Shift calendar Structuring model
63/MT_SAP_ALE_MSG_FL W_MDL 64/MT_SAP_ALE_MSG_TY PE_MDL 31/MT_SAP_APPL_DGM 7/MT_SAP_SERM 163/MT_SCREEN_DES 2/MT_SCRN_DGM 164/MT_SCREEN_NAV 47/MT_SEM_DATA_MDL 113/MT_SHIFT_CAL 133/MT_STRCT_DGM
ARIS Methods
11-1499
Model Name System attribute domain System attributes Table diagram Technical resources Technical terms model UML Activity diagram UML Class description diagram UML Class diagram UML Collaboration diagram UML Component diagram UML Deployment diagram UML Sequence diagram UML Statechart diagram UML Use case diagram Value-added chain diagram Y diagram
Model Description System attribute domain System attributes Table diagram Technical resources Technical terms model Activity diagram (Unified Modeling Language) Class description diagram (Unified Modeling Language) Class diagram (Unified Modeling Language) Collaboration diagram (Unified Modeling Language) Component diagram (Unified Modeling Language) UML Deployment diagram UML Sequence diagram Statechart diagram (Unified Modeling Language) Use case diagram (Unified Modeling Language) Value-added chain diagram Y diagram
Type No. 46/MT_DOM_SYS_ATTR 45/MT_SYS_ATTR 11/MT_TBL_DGM 48/MT_TECH_RES 22/MT_TECH_TRM_MDL 124/MT_UML_ACTIVITY_D GM 129/MT_UML_CLS_DESC_ DGM 104/MT_CLS_DGM_UML 128/MT_UML_COLAB_DG M 105/MT_CMPNT_DGM_UM L 167/MT_DEPLOY_DIAGR 166/MT_SEQ_DIAGR 130/MT_UML_STATE_CHR T_DGM 106/MT_USE_CSE_DGM_ UML 12/MT_VAL_ADD_CHN_D GM 30/MT_Y_DGM
ARIS Methods
11.10 Object Definitions (ObjTypeNum)
11-1500

Object Name Action Activity graph Actor Application system Application system class Application system type Argument Artifact Association Association class Association instance Association role Attribute Attribute link Attribute type Attribute type group Authorization condition Bitmap Break Business object Button Class Classification criterion Type No. 284/OT_ACTION 287/OT_ACT_GRAPH 97/OT_ACTOR 64/OT_APPL_SYS 7/OT_APPL_SYS_CLS 6/OT_APPL_SYS_TYPE 285/OT_ARGUM 289/OT_ARTIFACT 87/OT_ASSOC 264/OT_ASSOC_CLS 129/OT_ASSOC_INST 275/OT_ASSOC_ROLE 8/OT_ATTR 277/OT_ATTR_LINK 252/OT_XML_ATTRTYPE 111/OT_ATTR_TYPE_GRP 242/OT_AUTH_CON 167/OT_BITM 218/OT_BREAK 150/OT_BUSY_OBJ 263/OT_BUTTON 90/OT_CLS 33/OT_CLASSFC_CRIT
ARIS Methods
11-1501
Object Name Classifier role Classifier-in-state Cluster instance Cluster/Data model Collaboration Collaboration instance set Column Combo box Communication Complex object Complex object type Component Component instance Conditional section Connector Constraint Contents Control Cost category Cost driver COT attribute COT attribute (instance) Critical factor Data store Data value
Type No. 276/OT_CLS_ROLE 283/OT_CLS_IN_STATE 138/OT_CLST_INST 14/OT_CLST 286/OT_COLLABORATION 291/OT_COLLAB_INST_SET 166/OT_COL 259/OT_COMBOBOX 130/OT_COMM 181/OT_CX_OBJ 182/OT_OBJ_CX 188/OT_CMP 290/OT_COMP_INST 248/OT_COND_SECT 102/OT_CONNECTOR 88/OT_CNSTR 249/OT_XML_CONTENTS 161/OT_CONTR 132/OT_COST_TYPE 226/OT_COST_DRIVER 179/OT_COT_ATTR 180/OT_COT_ATTR_INS 108/OT_CRIT_FACT 96/OT_DATA_STORE 98/OT_DATA_VAL
ARIS Methods
11-1502
Object Name DBMS DBMS type Distribution channel Documented knowledge Domain Domain (physical) Draft list Element type Employee variable Entity Entity type Enumeration Enumeration attribute type Enumeration list occurrence Enumeration literal ERM attribute ERM attribute instance ERM domain Event Event instance Exception Extension point Field Field (specimen) Filter object type
Type No. 69/OT_DBMS 15/OT_DBMS_TYPE 269/OT_SALES_CHAN 231/OT_DOC_KNWLDG 16/OT_DOM 47/OT_DOM_PHYS 30/OT_LST_DSGN 247/OT_ELEM_TYPE 151/OT_EMPL_INST 139/OT_ENT 17/OT_ENT_TYPE 175/OT_ENUM 253/OT_XML_ENUMTYPE 171/OT_COUNT_INST 266/OT_ENUM_LIT 19/OT_ERM_ATTR 142/OT_ERM_ATTR_INST 20/OT_ERM_DOM 18/OT_EVT 143/OT_EV_INST 281/OT_UML_EXCEPT 265/OT_EXT_PT 21/OT_FLD 74/OT_FLD_SPEC 135/OT_FLTR_OBJ_TYPE
ARIS Methods
11-1503
Object Name Function Function instance General resource Generalization type Graphical user interface type Group Hardware component Hardware component class Hardware component type Improvement potential Index Information carrier Information flow Instantiation cycle Instantiation interval Instantiation plan Interaction instance set IT function IT function class IT function type Key performance indicator instance Knowledge category Layout Link object List
Type No. 22/OT_FUNC 137/OT_FUNC_INST 145/OT_GNRL_RES 23/OT_GNRL_TYPE 9/OT_GRPH_UI_TYPE 128/OT_GRP 76/OT_HW_CMP 25/OT_HW_CMP_CLS 24/OT_HW_CMP_TYPE 254/OT_C3_IMPROVE 103/OT_IDX 27/OT_INFO_CARR 26/OT_INFO_FLW 213/OT_INST_CYC 212/OT_INSTAN_INTERVALL 214/OT_INST_PLAN 292/OT_INTERACT_INST_SET 107/OT_DP_FUNC 106/OT_DP_FUNC_CLS 105/OT_DP_FUNC_TYPE 244/OT_KPI 230/OT_KNWLDG_CAT 170/OT_PRES 274/OT_LINK_OBJ 29/OT_LST
ARIS Methods
11-1504
Object Name List control Location Loop start Main process Marketing instrument Material class Material flow Material type Measurement unit Measurement unit number Memory location Message flow Message type Module Module class Module type Need Network Network class Network connection Network connection type Network node Network node type Network protocol Network type
Type No. 262/OT_LISTCTRL 54/OT_LOC 241/OT_LOOP_START 28/OT_MAIN_PRCS 268/OT_MARKET_INST 124/OT_MAT_CLS 83/OT_MAT_FLW 126/OT_MAT_TYPE 176/OT_UNIT 185/OT_UNIT_NUM 53/OT_MEM_LOC 136/OT_MSG_FLW 144/OT_MSG_TYPE 65/OT_MOD 38/OT_MOD_CLS 37/OT_MOD_TYPE 267/OT_WANT 85/OT_NW 42/OT_NW_CLS 82/OT_NW_LINE 81/OT_NW_LINE_TYPE 79/OT_NW_NODE 40/OT_NW_NODE_TYPE 104/OT_NW_PROT 39/OT_NW_TYPE
ARIS Methods
11-1505
Object Name Note Object instance Object type class Objective Operating resource Operating resource class Operating resource type Operating system Operating system type Operation Organizational chart Organizational level Organizational unit Organizational unit type Package Packaging material class Packaging material type Page Parameter Partition Performance characteristic Person Person type Perspective Position
Type No. 186/OT_NOTE 94/OT_OBJ_INST 36/OT_OBJ_TYPE_CLS 86/OT_OBJECTIVE 120/OT_OP_RES 112/OT_OP_RES_CLS 116/OT_OP_RES_TYPE 72/OT_OS 10/OT_OS_TYPE 93/OT_OP 60/OT_ORG_CHRT 59/OT_ORG_LVL 43/OT_ORG_UNIT 44/OT_ORG_UNIT_TYPE 187/OT_PACK 125/OT_PACK_MAT_CLS 127/OT_PACK_MAT_TYPE 164/OT_PAGE 184/OT_PARA 288/OT_PARTITION 157/OT_PERF_CHARACT 46/OT_PERS 78/OT_PERS_TYPE 243/OT_PERSPECT 45/OT_POS
ARIS Methods
11-1506
Object Name Process Product/Service Program library Program module Program module type Programming language Quick object Radio button/Check box Reception Relation Relationship Relationship type Risk Rule Rule instance Screen Screen design Screen table Section Security protocol Separator Sequence Shift Shift cycle Shift plan
Type No. 95/OT_PRCS 153/OT_PERF 68/OT_PRG_LIB 67/OT_PRG_MOD 66/OT_PRG_MOD_TYPE 70/OT_PRG_LNG 246/OT_CASUALOBJ 258/OT_OPT_CTRL 282/OT_UML_RECEPT 51/OT_REL 140/OT_RELSHP 11/OT_RELSHP_TYPE 159/OT_RISK 50/OT_RULE 152/OT_RULE_INST 31/OT_SCRN 32/OT_SCRN_DSGN 183/OT_SCRN_TBL 165/OT_SECT 245/OT_SECUREPROT 169/OT_SEPRT 250/OT_XML_SEQUENCE 217/OT_SHIFT 216/OT_SHIFT_CYC 215/OT_SHIFT_PLAN
ARIS Methods
11-1507
Object Name Signal Solution Sp./gen. operator Spin box State State machine Strategy Structural element Subsystem Subsystem instance System attribute System attribute domain System organizational unit System organizational unit type Table Tables (specimen) Tech. operating supply class Technical operating supply Technical operating supply type Technical term Technical terms instance Text Text box Tool Transaction folder
Type No. 280/OT_UML_SIGNAL 160/OT_SOLU 89/OT_SP_GEN_OPR 260/OT_SPINBOX 99/OT_STATE 279/OT_STATE_MACH 239/OT_STAT 232/OT_STRCT_ELMT 270/OT_SUBSYS 271/OT_SUBSYS_INST 109/OT_SYS_ATTR 110/OT_DOM_SYS_ATTR 12/OT_SYS_ORG_UNIT 13/OT_SYS_ORG_UNIT_TYPE 55/OT_TBL 73/OT_TBL_SPEC 115/OT_TECH_OP_SUPPLY_CLS 123/OT_TECH_OP_SUPPLY 119/OT_TECH_OP_SUPPLY_TYPE 58/OT_TECH_TRM 141/OT_TECH_TERM_INST 168/OT_TXT 257/OT_TEXTBOX 255/OT_C3_TOOL 158/OT_TASK_FOLD
ARIS Methods
11.11 Connection Definitions (CxnTypeNum)
11-1508
Object Name Transport system Transport system class Transport system type Tree control UML Model Use case instance View View (physical) Warehouse equipment Warehouse equipment class Warehouse equipment type XOR
Type No. 122/OT_TRNSP_SYS 114/OT_TRNSP_SYS_CLS 118/OT_TRNSP_SYS_TYPE 261/OT_TREECTRL 272/OT_UML_MOD 273/OT_USECASE_INST 57/OT_VIEW 75/OT_VIEW_PHYS 121/OT_WH_EQUIP 113/OT_WH_EQUIP_CLS 117/OT_WH_EQUIP_TYPE 251/OT_XML_XOR

Active Name accepts accesses accesses accesses accesses accesses accesses accesses alternatively Passive Name is accepted by has access by is accessed is accessed by is accessed by is accessed by is accessed by is accessed alternatively by Type No. 435/CT_AGREES 138/CT_ACS_3 491/CT_ACCESS 102/CT_ACS_2 234/CT_CAN_ACS 281/CT_ACS_4 98/CT_ACS_1 282/CT_ACS_ALT
ARIS Methods
11-1509
Active Name activates activates activates activates activates (Baan) affects aggregates applies to archives assigned with assigns associates associates (multiple) associates classifier role belongs to belongs to belongs to belongs to belongs to belongs to belongs to belongs to belongs to belongs to
Passive Name is activated by is activated by is activated by is activated by is activated by (Baan) is affected by is aggregated is applied by is archived by assigned to is assigned by is associated is associated by (multiple) is associated to belongs to belongs to encompasses encompasses groups has has as employee has assigned is affected by is assigned to
Type No. 308/CT_ACTIV_2 329/CT_ACTIV_3 43/CT_ACTIV_1 516/CT_AVTIV_4 429/CT_ACTIVATES 383/CT_CONC_2 186/CT_AGGREG 466/CT_APPL 225/CT_ARCH 567/CT_BO_ASSIGN 444/CT_IS_ASSIGNED_TO 416/CT_ASSOCIA 456/CT_ASSOCIATES_MU LTI 535/CT_ASSOC_CLSFIER 369/CT_BELONGS_TO_8 423/CT_BELONGS 269/CT_BELONGS_TO_6 87/CT_BELONGS_TO_1 115/CT_BELONGS_TO_3 91/CT_BELONGS_TO_2 6/CT_WRK_IN 253/CT_BELONGS_TO_5 382/CT_BELONGS_TO_9 120/CT_BELONGS_TO_4
ARIS Methods
11-1510
Active Name belongs to belongs to class belongs to type
Passive Name is assigned to encompasses is assigned to type
Type No. 337/CT_BELONGS_TO_7 212/CT_BELONGS_TO_CL S 338/CT_BOLONGS_TO_TY PE
binds calls calls can be can be assigned to can be connected to can be connected to can be connected to
is bound by is called by is called by can be can be assigned to can be connected to can be connected to can be connected to
528/CT_BINDS 426/CT_CALLS 455/CT_CALLS_1 286/CT_CAN_BE 166/CT_CAN_BE_ASSIG 156/CT_CAN_BE_CNN_TO _2 160/CT_CAN_BE_CNN_TO _3 162/CT_CAN_BE_CNN_TO _4
can be connected to can be connected to
can be connected to can be connected to
163/CT_CAN_BE_LNK_TO 26/CT_CAN_BE_CNN_TO_ 1
can be constituent can be disciplinary superior can be located at can be platform of
can have as constituent can have disciplinary superior can be location of can run under
195/CT_CAN_BE_CONST 197/CT_CAN_BE_DISC_S UP 165/CT_CAN_BE_LOC_AT 241/CT_CAN_BE_PLTFRM _OF
can be realized by
can realize
159/CT_CAN_BE_REAL_B Y
ARIS Methods
11-1511
Active Name can be responsible for
Passive Name can be under responsibility of
Type No. 217/CT_CAN_BE_RESP_F OR 196/CT_CAN_BE_TECH_S UP 230/CT_CAN_BE_USER 209/CT_CAN_BELONG_TO 291/CT_CAN_CHNG_WRK FLW_TO
can be technical superior can be user can belong to can change workflow to
can have technical superior can be used by can have as employee can be reached by
can consist (hor.) of part of connection can consist (vert.) of section can create can encompass can encompass can encompass can end in can occur can occur can realize can replace can run on can run under can support can use can use
can encompass part of connection can encompass section can be created by can belong to can belong to can belong to can be end point of can encompass can encompass can be realized at can be replaced by can be platform for can be platform of can be supported by can be used by can be used by
213/CT_CAN_CONS_HOR_ OF 214/CT_CAN_CONS_VER_ OF 267/CT_CAN_CRT 161/CT_CAN_SUBS_3 249/CT_CAN_SUBS_4 25/CT_CAN_SUBS_1 157/CT_CAN_END_IN 215/CT_CAN_OCC_2 27/CT_CAN_OCC_1 135/CT_CAN_REAL 411/CT_CAN_REPLACE 158/CT_CAN_RUN_ON 242/CT_CAN_EXEC_ON 238/CT_CAN_SUPP_2 125/CT_CAN_USE_1 243/CT_CAN_USE_2
ARIS Methods
11-1512
Active Name cancels carries out carries out carries out carries out changes classified by classifies communicates with concerns consists (hor.) of part of connection consists (vert.) of section consists of consists of constrains consults contains contains contains contains contains contributes to
Passive Name cancels is carried out by is carried out by is carried out by is carried out by is changed by is criterion of is classified communicates with is concerned by encompasses part of connection encompasses section is component of is part of is constrained is consulted by belongs to is contained by is contained in is contained in is contents of is worked on by collaboration of
Type No. 573/CT_CANCELS 218/CT_EXEC_2 306/CT_EXEC_3 346/CT_EXEC_4 65/CT_EXEC_1 224/CT_CHNG 114/CT_CLSF_BY 284/CT_CLSF 427/CT_COMM_WITH 192/CT_CONC 171/CT_CONS_OF_PRT_S TR 172/CT_CONS_OF_PRT_S EC 30/CT_CONS_OF_1 85/CT_CONS_OF_2 204/CT_CNSTR 288/CT_CONS 431/CT_BELONG_CAT 421/CT_CONTAINS 439/CT_CONTAINS_1 566/CT_BO_CONTAINS 461/CT_CONTAINS_2 233/CT_CONTR_TO_1
ARIS Methods
11-1513
Active Name contributes to
Passive Name is worked on by collaboration of
Type No. 324/CT_CONTR_TO_2
cooperates with corresponds to Cost category allocation creates creates creates creates creates creates creates creates output to decides on decides on defers defines defines defines (aggregating) defines (hierarchical) defines an association defines screen field defines status deletes
cooperates with corresponds to allocation of cost centers is created by is created by is created by is created by is created by is created by is created by is output medium for is decided by is decided by is deferred is defined by is defined by is aggregating is depending hierarchically is defined by has screen field is defined is deleted by
296/CT_COLLAB_WITH 391/CT_CORRES 309/CT_ALLOC_OF_COST _CAT_1 226/CT_CRT_5 330/CT_CRT_6 44/CT_CRT_1 454/CT_CREATES 57/CT_CRT_2 66/CT_CRT_3 69/CT_CRT_4 28/CT_CRT_OUT_TO 232/CT_DECID_ON 323/CT_DECD_ON 550/CT_DEFERS 103/CT_DEF 447/CT_DEFINES 105/CT_DEF_AGGR 106/CT_DEF_HIER 189/CT_DEF_AN_ASSOC 295/CT_DEF_MASK_ENTR 273/CT_DEF_STATE 227/CT_DEL
ARIS Methods
11-1514
Active Name delivers to denotes maturity level of depends depicts depicts deploys designs determines volume of differentiates according to value of distributes do DUMMY encompasses encompasses encompasses encompasses encompasses encompasses encompasses ends in error (out) extend forms an incoming reference with
Passive Name receives has maturity level is depending is depicted by is depicted by is deployed is designed by volume is dependent on is characteristic for is distributed by is done DUMMY belongs to belongs to belongs to belongs to belongs to is located at is part of is end of error (in) is extended has reference to
Type No. 572/CT_DELIVERS 469/CT_DENOTE 425/CT_DEPENDS 113/CT_DEPICTS_2 84/CT_DEPICTS_1 555/CT_DEPLOY 372/CT_IS_REPR_BY_2 448/CT_DETERM_AMOUN 268/CT_DIFF 228/CT_DISTR 524/CT_DO 1/CT_DUMMY 155/CT_CAN_SUBS_2 174/CT_SUBS_4 239/CT_SUBS_5 449/CT_INCLUDES 67/CT_SUBS_1 150/CT_SUBS_3 112/CT_SUBS_2 170/CT_END_IN 493/CT_ERROR 489/CT_EXTEND 107/CT_HAS_REL_REF
ARIS Methods
11-1515
Active Name generalizes has has has has has action has activation bar
Passive Name specializes belongs to belongs to has is assigned to is action of is activation bar of
Type No. 415/CT_GENERAL 446/CT_HAS 96/CT_HAS_1 368/CT_HAS_3 121/CT_HAS_2 557/CT_HAS_ACTION 569/CT_HAS_ACTIVATION _BAR
has activator has any number of times has argument has assigned has assigned has assigned has assigned has associated has at least once has at most once has attribute has base has behavior has carried out has consulting role in has consulting role in
is activator of may occur is argument of is assigned to is assigned to is assigned to is assigned to is associated must occur at least once may occur at most once is attribute of is base of is behavior of was carried out by is supported by consulting role of is supported by consulting role of
558/CT_HAS_ACTIVATOR 497/CT_MAY_OCCUR 534/CT_HAS_ARGU 328/CT_HAS_ASSIG_1 343/CT_HAS_ASSIG_2 349/CT_HAS_ASSIG_3 354/CT_HAS_ASSIG_4 199/CT_HAS_ASSOC 498/CT_REQ_AT_LEAST_1 499/CT_OPT_MAX_1 187/CT_HAS_ATTR 529/CT_HAS_BASE 544/CT_HAS_BEHAV 384/CT_HAS_EXEC 355/CT_HAS_CONSLT_RO LE_IN_1 358/CT_HAS_CONSLT_RO LE_IN_2
ARIS Methods
11-1516
Active Name has context has current location has default element has domain has effect has enumeration literal has exactly once has extension point has feature has flow to has guard has input parameter has instance has instance has internal transition to
Passive Name is context of is current location of is default element of is domain for is effect of is enumeration literal of must occur exactly once is extension point of is feature of receives flow from is guard of is input parameter of is instance is instance of is internal transition of
Type No. 563/CT_HAS_CONTEXT 303/CT_HAS_CUR_LOC 553/CT_HAS_DEF_ELEM 263/CT_HAS_DOM 549/CT_HAS_EFFECT 513/CT_HAS_ENUM_LIT 500/CT_EXACTLY_1 512/CT_HAS_EXT_PT 412/CT_HAS_FEATURE 526/CT_HAS_FLOW_TO 539/CT_HAS_GUARD 392/CT_HAS_IN_PARA 419/CT_HAS_INSTANCE 321/CT_HAS_INST 551/CT_HAS_INTERN_TR ANS
has knowledge of has link has link to has mandatory field has member has member has method has normal influence on
is available at is link of has link to is mandatory field is member of is member of is method for is normally influenced by
452/CT_IS_AVAILABLE 562/CT_HAS_LINK 83/CT_HAS_LINK_TO 130/CT_HAS_MAND_FIEL D 293/CT_HAS_MEMB 420/CT_HAS_MEMBER 251/CT_HAS_METH 483/CT_HAS_NORMAL_IN FL
ARIS Methods
11-1517
Active Name has operation has output of has output parameter has parameter has participating instance has participating stimulus has partition has performance characteristic has performance component has possible detour to has powertype has predecessor
Passive Name is operation of is output of is output parameter of is parameter of participates participates is partition of is performance characteristic of is performance component of is detour of is powertype of is predecessor of
Type No. 188/CT_HAS_OPR 50/CT_HAS_OUT 393/CT_HAS_OUT_PARA 510/CT_HAS_PARA 564/CT_HAS_PART_INST 565/CT_HAS_PART_STIM U 552/CT_HAS_PARTITION 340/CT_HAS_PERF_CHAR AC 339/CT_HAS_PERF_COMP 290/CT_HAS_DETOUR 531/CT_HAS_PTYPE 559/CT_HAS_PREDECESS OR
has process manager has qualifier has quota of has recursion has reference to has relation with has relation with
is process manager is qualifier of indicates quota of has recursion has reference to has relation with has relation with
342/CT_HAS_PRCS_MAN 515/CT_IS_QUALI 377/CT_HAS_QUO 390/CT_HAS_RECURS 294/CT_HAS_REF_TO 111/CT_IS_IN_RELSHP_T O 504/CT_IS_IN_RELSHP_T O_1
has relationship to
has relationship to
194/CT_HAS_REL_WITH
ARIS Methods
11-1518
Active Name has return type
Passive Name is return type of
Type No. 509/CT_HAS_RETURN_TY PE
has root has session has sink has slot has specification has state has strong influence on has submachine has subordinate event has subordinate rule has subprocess has template parameter has top state has transition to has transition to has type has value has value has very strong influence on has very weak influence on has weak influence on
is root of belongs to utility is sink of is slot of is specification of is state of is strongly influenced by is submachine of is subordinate event of is subordinate rule of is subprocess of is template parameter of is top state of has transition from has transition from is type of is value of is value of is very strongly influenced by is very weakly influenced by is weakly influenced by
387/CT_HAS_ORGIN 437/CT_HAS_SESSION 336/CT_HAS_SINK 530/CT_HAS_SLOT 518/CT_HAS_SPEC 75/CT_HAS_STATE 484/CT_HAS_STRONG_IN FL 538/CT_HAS_SUBMACH 46/CT_HAS_SUBO_EV 45/CT_HAS_SUBO_RULE 208/CT_HAS_SUBPRCS 527/CT_HAS_TMPL_PARA 540/CT_HAS_TOPSTATE 198/CT_HAS_TRANS_TO 459/CT_HAS_TANSITION 508/CT_IS_TYPE_OF 373/CT_IS_VALUE 533/CT_HAS_VALUE 485/CT_HAS_FULL_INFL 505/CT_HAS_VERY_WEAK _INFL 482/CT_HAS_WEAK_INFL
ARIS Methods
11-1519
Active Name implements imports include influences influences information flow instantiate interacts with is is a is a functional generic term of is alternative operating resource of is approved by is assigned 1:1 is assigned 1:n is assigned n:m is assigned to is assigned to is assigned to is assigned to is assigned to is assigned to is assigned to
Passive Name is implemented by is imported is included is influenced by is influenced by information flow (passive) is instantiated by has interaction from is is a is a functional subterm of
Type No. 56/CT_REAL 490/CT_IMPORT 488/CT_INCLUDE 380/CT_HAS_RESULT 571/CT_INFLUENCES 470/CT_INFO_FLOW 445/CT_IS_INSTANCIATE 460/CT_INTERACTS_WIT H 414/CT_IS 283/CT_IS_A 406/CT_FUNC_HEADLINE
has alternative operating resource approves is assigned 1:1 is assigned n:1 is assigned m:n has assigned has assigned has assigned is assigned to is assigned to is assigned to is assigned to
278/CT_IS_ALT_PROD_FA C_OF 222/CT_IS_GRANT_BY 101/CT_IS_1_1_ASSIG 42/CT_IS_1_N_ASSIG 51/CT_IS_N_M_ASSIG 252/CT_IS_ASSIG_6 376/CT_IS_ASSIG_7 378/CT_IS_ASSIG_8 17/CT_IS_ASSIG_1 22/CT_IS_ASSIG_2 52/CT_IS_ASSIG_3 93/CT_IS_ASSIG_5
ARIS Methods
11-1520
Active Name is attribute type group
Passive Name has attribute type group
Type No. 270/CT_IS_ATTR_TYPE_G RP
is based on is basis for is by default processed by is carried out at is checked by is compared to is composed by is composed of is composed of is connected to is connected to is connected to is consumed is consumed by is contained in is created with help from is critical factor for
is a base for has basis processes by default is performed in checks is compared to composes is a component of is part of is connected to is connected to is connected to consumes consumes contains helps with the creation of has critical factor
398/CT_IS_BASED_ON 520/CT_BASIS_FOR 386/CT_IS_PROC_STAND 258/CT_IS_EXEC_AT 223/CT_IS_CHCKD_BY 322/CT_IS_CMP_TO 409/CT_IS_COMPOSED 7/CT_IS_CRT_BY 201/CT_IS_COMPOSED_O F 175/CT_IS_CNN_TO_2 18/CT_IS_CNN_TO_1 560/CT_IS_CONNECTED 274/CT_IS_CONS_BY 443/CT_IS_USED_BY_1 385/CT_LIES_IN 464/CT_HELPS_TO_SET_ WITH 256/CT_IS_CRIT_FACT_F OR
is critical factor for is defined is defined is defined by
has critical factor can be processed by/with can be processed by/with defines
468/CT_IS_CRITCAL 305/CT_IS_DEF_1 327/CT_IS_DEF_2 246/CT_IS_DEF_BY_1
ARIS Methods
11-1521
Active Name is defined by is demanded by is deputy process manager is described by is describing for is describing for is different from is disciplinary superior to is discriminator of is dispatched by is divided into is documented in is driver is employee variable is evaluated by is evaluated by is execution-oriented superior is exposed to is feature of is filter of is foreign key for
Passive Name defines demands is as process under representative responsibility of is describing for has describing is described by is different from has the disciplinary superior is discriminated by dispatchs divides documents has driver has employee variable evaluates evaluates is execution-oriented subordinate is associated with has feature is filtered by has foreign key
Type No. 265/CT_IS_DEF_BY_2 519/CT_DEMANDED_BY 506/CT_IS_SUBST_PRCS_ RSPN 396/CT_IS_DSCR 261/CT_IS_DESC_FOR_2 78/CT_IS_DESC_FOR_1 359/CT_IS_DIFF 9/CT_IS_DISC_SUPER 190/CT_IS_DISC_OF 561/CT_IS_DISPATCHED 370/CT_IS_STRCR_IN 450/CT_IS_DOCU_IN 375/CT_IS_DRV 320/CT_IS_EMPL_INST 331/CT_IS_EVAL_BY_2 48/CT_IS_EVAL_BY_1 40/CT_IS_EXEC_ORNT_S UPER 361/CT_IS_EXPOS_TO 285/CT_IS_FEAT_OF 300/CT_IS_FLTR_OF 260/CT_IS_FRGN_KEY_FO R_2
ARIS Methods
11-1522
Active Name is foreign key for
Passive Name has foreign key
Type No. 79/CT_IS_FRGN_KEY_FOR _1
is generalization of is generic term of
is specialization of is subterm of
479/CT_GENERAL_2 403/CT_IS_GENERIC_TER M
is implemented by is implemented by is in conflict with is in state is included is influenced by is input for is instance of is interrupted by is IT responsible for is IT responsible for
implements implements is in conflict with has been put in state will be included has influence on has input of has instance interrupts is under IT responsibility of is under IT responsibility of
244/CT_IS_REAL_BY 366/CT_IS_IMPL_BY 481/CT_CONFLICTS 543/CT_IS_IN_STATE 568/CT_BO_RELATION 487/CT_HAS_INFL 49/CT_IS_INP_FOR 193/CT_IS_INST_OF_1 440/CT_IS_INTERUPTED_ BY 148/CT_IS_DP_RESP_1 219/CT_IS_DP_RESP_2
is linked to is linked with is located at is located at is located at is managed by is managed by
is linked to is linked with is location of is location of is location of manages manages
313/CT_IS_LNK_TO 424/CT_IS_LINKED 12/CT_IS_LOC_AT_1 14/CT_IS_LOC_AT_2 167/CT_IS_LOC_AT_3 292/CT_MAN 317/CT_IS_MAN_BY
ARIS Methods
11-1523
Active Name is managed with is mandatory field for is measured by is measured by is measured upon occurrence is nested is not consumed is object-oriented superior is of type is of type is of type is of type is offered via is operating resource of is operationalized is order basis for is organization manager for is oriented at is owned by is owner of is parallel to
Passive Name manages has mandatory field measures measures triggers measuring nests does not consume is object-oriented subordinate determines type of determines type of determines type of determines type of offers has operating resource operationalizes has order basis is under organizational responsibility of is oriented at owns has owner is parallel to
Type No. 451/CT_IS_ADMIN_WITH 262/CT_IS_MANDAT_FIEL D_FOR 486/CT_MEASURED_BY 570/CT_MEASURED_BY_1 574/CT_IS_MEASURED_W HEN_OCCURRING 418/CT_IS_NESTED 276/CT_IS_NOT_CONS_B Y 41/CT_IS_OBJ_ORNT_SUP ER 169/CT_IS_OF_TYPE_3 344/CT_IS_OF_TYPE_4 4/CT_IS_OF_TYPE_1 61/CT_IS_OF_TYPE_2 523/CT_IS_OFFERED 277/CT_IS_PROD_FAC_OF 341/CT_IS_OPRLZD 413/CT_IS_ORDER 395/CT_IS_ORG_RSPN
374/CT_ORIENT 525/CT_IS_OWNED_BY 271/CT_IS_OWN 353/CT_IS_PARAL_TO
ARIS Methods
11-1524
Active Name is part of is partly consumed is platform of is position of is predecessor of is predecessor of is predecessor of is predecessor of is prevented by is primary key for is primary key for is process manager for
Passive Name has part partly consumes runs under has position follows is successor of is successor of is successor of prevents has primary key has primary key is under process responsibility of
Type No. 404/CT_IS_PART_OF 275/CT_IS_PARTLY_CONS _BY 70/CT_IS_PLTFRM_OF 178/CT_IS_JOB_OF 118/CT_IS_PREDEC_OF_1 152/CT_IS_PRED_OF 314/CT_IS_PREDEC_OF_2 345/CT_IS_PREDEC_OF_3 365/CT_IS_PREV_BY 259/CT_IS_PRIM_KEY_FO R_2 80/CT_IS_PRIM_KEY_FOR _1 394/CT_IS_PRCS_RSPN
is process-oriented superior is programming language of is reached via is received from is received from is reduced by is reported by is represented by
is process-oriented subordinate is developed with leads to is a receiver of receives mitigates is reported by represents
39/CT_IS_PRCS_ORNT_S UPER 240/CT_IS_PRG_LNG 388/CT_IS_REACH 465/CT_IS_RECEIVED_BY 408/CT_IS_RECEIVED 363/CT_IS_REDU_BY 364/CT_IS_REPO_BY 73/CT_IS_REPR_BY
ARIS Methods
11-1525
Active Name is represented in is required for is responsible for is responsible for is responsible for is responsible for is responsible for development of is responsible for development of is shifted to is source of is specimen of is specimen owner of is stored on is substate is subtype of is subtype of is subtype of is superior is superior is superior is superior (Baan) is supertype of is supertype of
Passive Name represents requires is assigned to is under responsibility of is under responsibility of is under responsibility of development is under responsibility of development is under responsibility of is affected by shift has source has specimen has specimen owner stores has substate has as subtype has as subtype has subtype is subordinate is subordinate is subordinate has superior (Baan) has as supertype has as supertype
Type No. 389/CT_IS_REPRESEN 453/CT_IS_NEEDED_BY 211/CT_IS_RESP_2 122/CT_IS_RESP_FOR_2 168/CT_IS_RESP_1 33/CT_IS_RESP_FOR_1 179/CT_IS_RESP_FOR_DE V_1 231/CT_IS_RESP_FOR_DE V_2 381/CT_REPLACED 335/CT_IS_SOURCE_OF 287/CT_IS_SPEC_OF 272/CT_IS_SPEC_OWN 173/CT_STOR_ON 200/CT_IS_SUBST 356/CT_IS_SUB_OF_3 76/CT_IS_SUB_OF_1 184/CT_IS_SUB_OF_2 257/CT_IS_SUPERIOR_2 3/CT_IS_SUPERIOR_1 347/CT_IS_SUPERORD 430/CT_IS_SUPERIOR 357/CT_IS_SUPER_OF_3 77/CT_IS_SUPER_OF_1
ARIS Methods
11-1526
Active Name is supertype of is taken at is technical superior to is technically responsible for is technically responsible for is technically responsible for is triggered by is under financial responsibility of is under responsibility of is under technical responsibility of is used by is used by is used for is used in is user is user is user interface is value of (Baan) is workflow class of leads to
Passive Name has supertype takes has the technical superior is under technical responsibility of is under technical responsibility of is under technical responsibility of triggers is financially responsible for is responsible for is technically responsible for uses uses uses uses has user is used by runs under has value is workflow class of (passive) is assigned to
Type No. 185/CT_IS_SUPER_OF_2 467/CT_IS_TAKEN 8/CT_IS_TECH_SUPER 10/CT_IS_TECH_RESP_1
11/CT_IS_TECH_RESP_2 220/CT_IS_TECH_RESP_3 537/CT_IS_TRIGG_BY 463/CT_IS_FINANC_RESP ON 100/CT_IS_UNDER_RESP_ OF 462/CT_IS_TECH_RESPO N 400/CT_IS_USED_OF 441/CT_IS_USED_BY 522/CT_IS_USED_FOR 216/CT_IS_USED_IN 149/CT_IS_USER_1 229/CT_IS_USER_2 254/CT_IS_UI 434/CT_IS_VALUE_BAAN 472/CT_IS_WFCLASS_OF 116/CT_LEADS_TO_1
ARIS Methods
11-1527
Active Name leads to leads to leads to leads to leads to (Baan) lies on links links links links material flow may access may carry out may change privileges may instantiate may not carry out may search must be informed about must be informed about must be informed on cancellation
Passive Name is assigned to is assigned to is dependent on is dependent on is reached by (Baan) has information about is linked by is linked by is linked by is linked to material flow (passive) can be accessed by may be carried out by may change privileges (passive) can be instantiated by may not be carried out by may search (passive) result is forwarded to result is forwarded to sends information on cancellation to
Type No. 333/CT_LEADS_TO_3 517/CT_LEADS_TO_5 117/CT_LEADS_TO_2 334/CT_LEADS_TO_4 428/CT_LEADS_TO 86/CT_LIES_ON 315/CT_LNK_3 332/CT_LNK_4 54/CT_LNK_2 47/CT_LNK_1 471/CT_MAT_FLOW 351/CT_MUST_NOT_ACS 401/CT_CAN_EXEC 474/CT_MAY_CHG_PRIVIL 350/CT_IS_ALLOW_TO_A SSIG_INST 402/CT_CANNOT_EXEC 473/CT_MAY_SEARCH 266/CT_MUST_BE_INFO_ ABT_1 326/CT_MUST_BE_INFO_ ABT_2 316/CT_MUST_BE_INFO_ ON_CNC_1
ARIS Methods
11-1528
Active Name must be informed on cancellation must inform about result of must inform about result of must not occur for
Passive Name sends information on cancellation to result is forwarded by result is forwarded by has condition (false)
Type No. 352/CT_MUST_BE_INFO_ ON_CNC_2 255/CT_MUST_INFO_ABT _RES 325/CT_MUST_INFO_ABT _RES_OF 128/CT_MUST_NOT_OCC_ WHN
must occur for next no (out) occupies occurs at occurs before Optimization path
has condition (true) previous no (in) is occupied by has occurs after Optimization path (passive)
127/CT_MUST_OCC_FOR 492/CT_NEXT 494/CT_NO 210/CT_OCCUPIES 507/CT_OCCUR 477/CT_SUCCEED 433/CT_OPT_PATH
originates from owns owns passes value passes value
is origin of is effect of is part of evaluates evaluates function attribute
532/CT_ORIG 379/CT_OWNS_2 95/CT_OWNS 136/CT_PSS_VAL_2 31/CT_PSS_VAL_1
performs performs on entry performs on exit performs while in state
is performed by is performed on entry is performed on exit is performed while in state
480/CT_EXEC_5 546/CT_PERF_ENTRY 547/CT_PERF_EXIT 548/CT_PERF_STATE
ARIS Methods
11-1529
Active Name permits access Phase assignment (Baan) produces propagates propagates provides provides provides input for provides value for queries raises reads reads realizes receives signal references refers to refines relates to relates to repeats represents requires requires
Passive Name access is permitted by phase assignment is produced by is propagated is propagated by is provided by is provided by gets input from uses value of is queried by is raised by is read by reads is realized by sends signal is referenced by is referred by is refined by has relates to (passive) is repeated by is represented in is required by is required by
Type No. 536/CT_PERM_ACCESS 436/CT_PHASE_ASSIGN_ BAAN 442/CT_PROCUCES 264/CT_PROPG_2 191/CT_PROPG_1 399/CT_PROVIDES 575/CT_DELIVERS_1 53/CT_PROV_INP_FOR 319/CT_PROV_VAL_FOR 289/CT_QUIR_WITH 542/CT_RAISES 247/CT_READ_1 248/CT_READ_2 458/CT_REALIZES 541/CT_RECEIVES 422/CT_REF 514/CT_REFS_TO 511/CT_REFINES 177/CT_REL_TO 476/CT_RELATES_TO 438/CT_REPEATS 371/CT_REPR 279/CT_REQU 362/CT_REQ
ARIS Methods
11-1530
Active Name requires alternatively resides in Role assignment runs with satisfies secures sees sends sends sends message sends signal sets value splits to stores substitutes for supplies properties for supports supports supports supports supports supports when time limit is exceeded synonym (preferred term of)
Passive Name is required alternatively contains Role assignment (passive) is platform for is satisfied by is secured by is seen is sent from receives receives message has been sent is set by is splitted by is stored on is substituted by has properties supplied by is supported is supported by is supported by is supported by using is supported by using supports when time limit is exceeded (passive) synonym (not a preferred term of)
Type No. 280/CT_REQU_ALT 554/CT_RESIDES 432/CT_ROLE_ASSIGN 503/CT_RUNS_ON 521/CT_SUPPLY 496/CT_SECURE 203/CT_SEE 407/CT_SENDS_2 205/CT_SENDS 556/CT_SENDS_MESSAGE 545/CT_SENDS_SIG 32/CT_SET_VAL 410/CT_SPLITS 126/CT_STOR 318/CT_SUBST 457/CT_SUPPL_PROP 417/CT_SUPPORTS 147/CT_SUPP_3 221/CT_CAN_SUPP_1 145/CT_SUPP_1 146/CT_SUPP_2 475/CT_SUPP_TIME_LIMI T_EXCEED 405/CT_SYNONYM
ARIS Methods
11.12 Object Symbols (SymbolNum)
11-1531
Active Name time assessment position transmits data to uses uses uses uses uses uses uses yes (out)
Passive Name time assessment position receives data from is used is used by is used by is used by is used by is used by is used by yes (in)
Type No. 367/CT_TIME_EST_POS 502/CT_SENDS_3 478/CT_USES_2 124/CT_USE_2 137/CT_USE_3 348/CT_USE_4 360/CT_USE_5 397/CT_USES 60/CT_USE_1 495/CT_YES

Symbol Name #PCDATA Action Activity Activity graph Actor Actor Actor (group) Actor (organizational unit) Actor (person) Actor (position) Actor (tech.) Symbol No. 672 801 456 803 172 399 684 685 682 683 681 Object Type No. 249/ST_XML_PCDATA 284/ST_ACTION 22/ST_ACTIVITY 287/ST_ACT_GRAPH 97/ST_ACTOR 78/ST_ACTOR2 128/ST_ACTOR6 43/ST_ACTOR7 46/ST_ACTOR4 45/ST_ACTOR5 6/ST_ACTOR3
ARIS Methods
11-1532
Symbol Name Airplane AND operator (inst.) AND rule AND rule AND/OR operator (inst.) AND/OR rule AND/XOR operator (inst.) AND/XOR rule ANY Application system Application system Application system Application system class Application system type Argument ARIS diagram Artifact Association Association class Association instance Association role Attribute Attribute link Attribute type Attribute type group
Symbol No. 364 253 42 526 259 133 261 136 674 107 629 669 14 33 802 248 797 146 761 210 786 21 788 677 206
Object Type No. 118/ST_PLANE_PIC 152/ST_OPR_AND_INST 50/ST_OPR_AND_1 50/ST_AND 152/ST_OPR_AND_OR_INST 50/ST_AND_OR 152/ST_OPR_AND_XOR_INST 50/ST_AND_XOR 249/ST_XML_ANY 64/ST_APPL_SYS 64/ST_APPL_SYS_1 64/ST_APPL_SYS_PIC 7/ST_APPL_SYS_CLS 6/ST_APPL_SYS_TYPE 285/ST_ARGUM 27/ST_ARIS_DGM 289/ST_ARTIFACT 87/ST_ASSOC 264/ST_ASSOC_CLS 129/ST_ASSOC_INST 275/ST_ASS_ROLE 8/ST_ATTR_1 277/ST_ATTR_LINK 252/ST_XML_ATTRTYPE 111/ST_ATTR_TYPE_GRP
ARIS Methods
11-1533
Symbol Name Attributes Authorization condition Bar code Bitmap Book Book Branch Break Business component Business document Business object Business participant Business process Button Card file CD-ROM CD-ROM Cell sp. Characteristic Characteristic Class Class Classification criterion Classifier role Classifier-in-state
Symbol No. 155 533 48 290 345 723 513 426 537 535 250 534 538 757 27 337 697 117 580 602 152 520 139 787 795
Object Type No. 19/ST_ATTR_3 242/ST_AUTH_COND 27/ST_BARCODE 167/ST_BITM 27/ST_BOOK_PIC 27/ST_INFO_CARR_BOOK 50/ST_BRANCH 218/ST_BREAK 6/ST_BUS_COM 14/ST_BUS_DOC 150/ST_BUSY_OBJ 44/ST_BUS_PART 22/ST_BUS_PROC 263/ST_BUTTON 27/ST_CRD_FILE 27/ST_CD_PIC 27/ST_INFO_CARR_CD 74/ST_FLD_EX 17/ST_KAT 19/ST_KAT_AT 90/ST_CLS 90/ST_CLASS 33/ST_CLSFC_CRIT 276/ST_CLS_ROLE 283/ST_CLS_IN_STATE
ARIS Methods
11-1534
Symbol Name Cluster Cluster Cluster instance Collaboration Collaboration instance set Column Combo box Communication Communication structure Company Competitor Complex object Complex object type Component Component instance Computer Conditional section Connection Connector Constraint Control Core competence Cost category Cost center Cost driver
Symbol No. 13 521 235 796 808 289 749 388 579 392 390 307 324 397 807 353 671 179 517 147 284 714 224 223 435
Object Type No. 14/ST_CLST 14/ST_CLUSTER_2 138/ST_CLST_INST 286/ST_COLLABORATION 291/ST_COLLAB_INST_SET 166/ST_COL 259/ST_COMBOBOX 130/ST_COMM 14/ST_COM_STRUC 43/ST_CPANY_PIC 43/ST_CTITOR_PIC 181/ST_CX_OBJ 182/ST_OBJ_CX 188/ST_CMP 290/ST_COMP_INST 6/ST_COMPUT_PIC 248/ST_COND_SECT 102/ST_CONNECTION 50/ST_CONNEC 88/ST_CNSTR 161/ST_CONTR 230/ST_CORE_COMPETENCE 132/ST_TYPE_OF_COST 43/ST_COST_CNT 226/ST_COST_DRIVER
ARIS Methods
11-1535
Symbol Name COT attribute COT attribute (instance) Critical factor Critical factor Customer D attribute (ERM) d attribute instance (ERM) Data store Data value Data value DBMS DBMS type Decision Descriptive field Dialog box Dimension Diskette Diskette Distribution channel Document Document Documented knowledge Documented knowledge Domain Draft list
Symbol No. 305 306 186 551 384 8 240 171 173 387 112 36 462 189 765 570 344 722 771 29 340 453 454 22 17
Object Type No. 179/ST_COT_ATTR 180/ST_COT_ATTR_INS 108/ST_CRIT_FACT 108/ST_CRIT_FACT_2 43/ST_CSTOMER_PIC 19/ST_DESC_ATTR 142/ST_DESC_ATTR_INST_ERM 96/ST_DATA_STORE 98/ST_DATA_VAL 98/ST_DVALUE 69/ST_DBMS 15/ST_DBMS_TYPE 50/ST_DECISION 109/ST_DESC_FIELD 31/ST_DLG 14/ST_DIM 27/ST_DISK_PIC 27/ST_INFO_CARR_FDD 269/ST_SALES_CHAN 27/ST_DOC 27/ST_DOCU_PIC 231/ST_DOC_KNWLDG_1 231/ST_DOC_KNWLDG_2 16/ST_DOM 30/ST_LIST_DSGN
ARIS Methods
11-1536
Symbol Name DVD E-mail E-mail E-mail EDI Electronic document Electronic folder Element type Employee role Employee variable EMPTY Entity Entity type Entity type Entity type Enumeration Enumeration Enumeration attribute type Enumeration list occurrence Enumeration literal ERM attribute ERM domain Event Event Event instance
Symbol No. 736 352 604 718 728 729 730 670 536 252 673 236 404 5 522 301 679 678 294 763 529 57 1 356 243
Object Type No. 27/ST_INFO_CARR_DVD 27/ST_EMAIL_PIC 27/ST_EMAIL_PIC2 27/ST_EMAIL_1 27/ST_INFO_CARR_EDI 27/ST_INFO_CARR_EDOC 27/ST_INFO_CARR_EFOLDER 247/ST_ELEM_TYPE 78/ST_EMPL_ROLE 151/ST_EMPL_INST 249/ST_XML_EMPTY 139/ST_ENT 17/ST_ENT_TYPE_1 17/ST_ENT_TYPE 17/ST_ET 175/ST_ENUM 175/ST_XML_ENUM 253/ST_XML_ENUMTYPE 171/ST_COUNT_INST 266/ST_ENUM_LIT 19/ST_ERM_ATTR 20/ST_EERM_DOM 18/ST_EV 18/ST_EVENT_PIC 143/ST_EV_INST
ARIS Methods
11-1537
Symbol Name Exception Expertise Expertise Extension point External person Extranet Extranet Fact table Fax Fax Field File File File File cabinet File cabinet Filing basket Filing basket Filter object type Final state Final state Fixed value Fixed value FK attribute (ERM)
Symbol No. 793 46 732 762 58 593 735 572 350 51 31 28 339 569 346 724 354 727 233 176 460 573 600 10
Object Type No. 281/ST_UML_EXCEP 27/ST_KNOWHOW 27/ST_INFO_CARR_EXPERT 265/ST_EXT_PT 46/ST_PERS_EXT 27/ST_EXTRANET 27/ST_INFO_CARR_EXTRA 14/ST_FACT_TAB 27/ST_FAX_PIC 27/ST_FAX 21/ST_FLD 27/ST_FILE 27/ST_FILE_PIC 27/ST_FILE_PIC_2 27/ST_FCABIN_PIC 27/ST_INFO_CARR_FCABIN 27/ST_FILE_BIN_PIC 27/ST_INFO_CARR_FILE_BIN 135/ST_FLTR_OBJ_TYPE 99/ST_FINAL_STATE 153/ST_STATE_FINAL 17/ST_FIX 19/ST_FIX_AT 19/ST_FRGN_KEY_ATTR
ARIS Methods
11-1538
Symbol Name FK attribute instance (ERM)
Symbol No. 242
Object Type No. 142/ST_FRGN_KEY_ATTR_INST_ ERM
Folder Foreign key Frame Function Function (actual) Function (manufacturing) Function (office) Function (target) Function instance General resource General resource Generalization Generalization Generalization Generalization Generalization Generalization Generalization Generalization Goods shipment Group Group GUI type
47 188 767 335 227 374 355 228 234 246 518 11 148 149 150 151 62 63 64 591 209 375 38
27/ST_FOLD 109/ST_FRGN_KEY 31/ST_FRAME 22/ST_FUNC 22/ST_FUNC_ACT 22/ST_FUNC_PIC_2 22/ST_FUNC_PIC 22/ST_FUNC_TRG 137/ST_FUNC_INST 145/ST_GNRL_RES 145/ST_GEN_RESRC 23/ST_GNRL_1 89/ST_GNRL_5 89/ST_GNRL_6 89/ST_GNRL_7 89/ST_GNRL_8 23/ST_GNRL_2 23/ST_GNRL_3 23/ST_GNRL_4 153/ST_GOODS 128/ST_GRP 128/ST_GRP_PIC 9/ST_GRPH_UI_TYPE
ARIS Methods
11-1539
Symbol Name Hard disk Hard disk Hardware component Hardware component class Hardware component type Heading Hierarchy table Improvement potential (quality) Improvement potential (quantity) Index InfoCube Information (actual) Information (target) Information carrier Information flow Information object Information service Information service Initial state Initial state Initiative Input parameter Input/Output Instance
Symbol No. 338 698 119 25 26 716 576 712 713 181 577 231 232 218 385 217 531 532 175 459 553 326 719 157
Object Type No. 27/ST_HDISK_PIC 27/ST_INFO_CARR_HD 76/ST_HW_CMP 25/ST_HW_CMP_CLS 24/ST_HW_CMP_TYPE 232/ST_HEAD 14/ST_HIERARC_TAB 254/ST_IMPROVE_QUAL 254/ST_IMPROVE_QUANT 103/ST_IDX 14/ST_INFO_CUBE 17/ST_INFO_ACT 17/ST_INFO_TRG 27/ST_INFO_CARR 26/ST_INFO_FLW 14/ST_INFO_OBJ 153/ST_INF_SERV 153/ST_INF_SERV_PIC 99/ST_INIT_STATE 153/ST_STATE_INITIAL 137/ST_INITIATIVE 184/ST_IN_PARA 22/ST_IN_OUTPUT 94/ST_INST
ARIS Methods
11-1540
Symbol Name Instantiation cycle Instantiation interval Instantiation plan Interaction instance set Interface Internal person Internet Internet Internet Intranet Intranet IT function IT function class IT function type K attribute (ERM) K attribute instance (ERM) Key figure Key figure Key performance indicator (estimated) Key performance indicator (exact) Key performance indicator instance Knowledge category Knowledge category
Symbol No. 421 420 422 809 401 2 349 605 726 592 734 185 184 183 9 241 578 601 709 708
Object Type No. 213/ST_INST_CYC 212/ST_INST_INTERV 214/ST_INST_PLAN 292/ST_INTERACT_INST_SET 90/ST_IF 46/ST_PERS_INT 27/ST_INTERNET_PIC 27/ST_INTERNET_PIC2 27/ST_INFO_CARR_INTERN 27/ST_INTRANET 27/ST_INFO_CARR_INTRANET 107/ST_DP_FUNC 106/ST_DP_FUNC_CLS 105/ST_DP_FUNC_TYPE 19/ST_KEY_ATTR 142/ST_KEY_ATTR_INST_ERM 17/ST_KPI_2 19/ST_KPI_2_AT 17/ST_KPI_ESTIMATED 17/ST_KPI_EXACT
552 451 452
244/ST_KPI 230/ST_KNWLDG_CAT_1 230/ST_KNWLDG_CAT_2
ARIS Methods
11-1541
Symbol Name LAN Layout Letter Letter Link object List List control Location Location Location Log Loop limit (end) Loop limit (start) Machine Magnetic tape Magnetic tape Main process Mandatory field Manual processing Marketing instrument Master data table Material class Material flow Material type Material type
Symbol No. 731 293 343 721 785 40 756 12 362 371 247 515 514 367 180 348 70 190 512 770 581 207 386 193 372
Object Type No. 27/ST_INFO_CARR_LAN 170/ST_PRES 27/ST_LETT_PIC 27/ST_INFO_CARR_LETTER 274/ST_LINK_OBJ 29/ST_LIST 262/ST_LISTCTRL 54/ST_LOC_1 54/ST_LOCA_PIC 54/ST_LOCA_PIC2 27/ST_LOG 18/ST_LLIMIT_END 241/ST_LLIMIT_START 116/ST_MACH_PIC 27/ST_MAGN_TAPE 27/ST_TAPE_PIC 28/ST_MAIN_PRCS 109/ST_MAND_FIELD 22/ST_PRC_MAN 268/ST_MARKET_INST 14/ST_XXX_TAB 124/ST_MAT_CLS 83/ST_MAT_FLW 126/ST_MAT_TYPE 126/ST_MAT_TYPE_PIC
ARIS Methods
11-1542
Symbol Name Material type Measurement unit Measurement unit number Memory location Message flow Message type Microfiche Mobile phone Mobile phone (WAP) Module Module class Module type Money transaction Need Network Network class Network connection Network connection type Network node Network node type Network protocol Network type Node Node instance Note
Symbol No. 373 302 328 32 389 244 49 733 589 108 15 41 590 769 128 23 125 124 122 121 182 24 805 806 395
Object Type No. 126/ST_MAT_TYPE_PIC2 176/ST_UNIT 185/ST_UNIT_NUM 53/ST_MEM_LOC 136/ST_MSG_FLW 144/ST_MSG_TYPE 27/ST_MICROFICHE 27/ST_INFO_CARR_HANDY 27/ST_HANDY 65/ST_MOD 38/ST_MOD_CLS 37/ST_MOD_TYPE 153/ST_MONEY 267/ST_WANT 85/ST_NW 42/ST_NW_CLS 82/ST_NW_LINE 81/ST_NW_LINE_TYPE 79/ST_NW_NODE_1 40/ST_NW_NODE_TYPE 104/ST_NW_PROT 39/ST_NW_TYPE 24/ST_UML_NODE 76/ST_UML_NODE_INST 186/ST_NOTE
ARIS Methods
11-1543
Symbol Name Notepad Notepad Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object
Symbol No. 347 725 402 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655
Object Type No. 27/ST_NOTE_PIC 27/ST_INFO_CARR_NOTE 94/ST_OBJ 246/ST_OBJECT_1 246/ST_OBJECT_2 246/ST_OBJECT_3 246/ST_OBJECT_4 246/ST_OBJECT_5 246/ST_OBJECT_6 246/ST_OBJECT_7 246/ST_OBJECT_8 246/ST_OBJECT_9 246/ST_OBJECT_10 246/ST_OBJECT_11 246/ST_OBJECT_12 246/ST_OBJECT_13 246/ST_OBJECT_14 246/ST_OBJECT_15 246/ST_OBJECT_16 246/ST_OBJECT_31 246/ST_OBJECT_17 246/ST_OBJECT_18 246/ST_OBJECT_19 246/ST_OBJECT_20 246/ST_OBJECT_21
ARIS Methods
11-1544
Symbol Name Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object Object state Object type Object type class Objective
Symbol No. 656 657 658 659 660 661 662 663 664 665 666 667 668 686 687 694 703 704 705 706 707 457 461 140 129
Object Type No. 246/ST_OBJECT_22 246/ST_OBJECT_23 246/ST_OBJECT_24 246/ST_OBJECT_25 246/ST_OBJECT_26 246/ST_OBJECT_27 246/ST_OBJECT_28 246/ST_OBJECT_29 246/ST_OBJECT_32 246/ST_OBJECT_33 246/ST_OBJECT_34 246/ST_OBJECT_35 246/ST_OBJECT_30 246/ST_OBJECT_36 246/ST_OBJECT_37 246/ST_OBJECT_44 246/ST_OBJECT_51 246/ST_OBJECT_52 246/ST_OBJECT_53 246/ST_OBJECT_54 246/ST_OBJECT_55 153/ST_OBJ_STATE 90/ST_OBJ_TYPE 36/ST_OBJ_TYPE_CLS 86/ST_OBJCTV
ARIS Methods
11-1545
Symbol Name Objective Operating resource Operating resource class Operating resource type Operating system Operating system type Operation Operation OR operator (inst.) OR rule OR rule OR/AND operator (inst.) OR/AND rule OR/XOR operator (inst.) OR/XOR rule Order Organizational chart Organizational level Organizational unit Organizational unit Organizational unit Organizational unit type Organizational unit type Organizational unit type Organizational unit type
Symbol No. 394 198 202 197 115 35 156 455 254 43 527 257 131 262 137 376 59 60 144 3 361 161 393 4 628
Object Type No. 86/ST_TARGET_PIC 120/ST_OP_RES 112/ST_OP_RES_CLS 116/ST_OP_RES_TYPE 72/ST_OS 10/ST_OS_TYPE 93/ST_OP 22/ST_OP_1 152/ST_OPR_OR_INST 50/ST_OPR_OR_1 50/ST_OR 152/ST_OPR_OR_AND_INST 50/ST_OR_AND 152/ST_OPR_OR_XOR_INST 50/ST_OR_XOR 58/ST_ORDER_PIC 60/ST_ORG_CHRT 59/ST_ORG_LVL 43/ST_ORG_UNIT_2 43/ST_ORG_UNIT_1 43/ST_ORG_PIC 44/ST_ORG_UNIT_TYPE_2 44/ST_ORG_TYPE_PIC 44/ST_ORG_UNIT_TYPE_1 44/ST_ORG_UNIT_TYPE_3
ARIS Methods
11-1546
Symbol Name Organizational unit type Output parameter Package Package Packaging material Packaging material class Packaging material type Page Parameter Partition PDA Performance characteristic Person (f) Person (m) Person type Person type Perspective Phys. domain Picture Position Position Position description Position type Position type Pot. competitor
Symbol No. 630 327 396 588 363 208 195 287 759 804 695 269 359 358 145 360 548 53 758 143 467 510 299 631 391
Object Type No. 44/ST_ORG_UNIT_TYPE_4 184/ST_OUT_PARA 187/ST_PACK 187/ST_PACK_PIC_2 127/ST_PACK_PIC 125/ST_PACK_MAT_CLS 127/ST_PACK_MAT_TYPE 164/ST_PAGE 184/ST_UML_PARA 288/ST_PARTITION 27/ST_INFO_CARR_PDA 157/ST_PERF_CHARAC 46/ST_PERS_F_PIC 46/ST_PERS_M_PIC 78/ST_EMPL_TYPE 78/ST_PERS_TYPE_PIC 243/ST_PERSPEC 47/ST_PHYS_DOM 167/ST_PICTURE 45/ST_POS 45/ST_POS_1 78/ST_JOB_DESC 44/ST_POS_TYPE 44/ST_POS_TYPE_1 43/ST_PCTITOR_PIC
ARIS Methods
11-1547
Symbol Name Primary key Printer Printer Process Process Process interface Process module Processing (Process) Product Product Product/Service Product/Service Program library Program modification Program module Program module type Programming language Project guideline Pseudostate (choice) Pseudostate (deep history) Pseudostate (initial) Pseudostate (shallow history) Radio button/Check box Reception Reint. relationship
Symbol No. 187 336 696 170 72 94 772 511 377 380 465 524 111 738 110 109 113 251 800 798 790 799 746 794 238
Object Type No. 109/ST_PRIM_KEY 27/ST_PRINT_PIC 27/ST_INFO_CARR_PRINT 95/ST_PRCS_2 22/ST_PRCS_1 22/ST_PRCS_IF 22/ST_PRCS_MOD 22/ST_PRC2 153/ST_PROD_PIC 153/ST_PROD_PIC2 153/ST_PERFORM 153/ST_PROD_SERV 68/ST_PRG_LIB 22/ST_PROGMOD 67/ST_PRG_MOD 66/ST_PRG_MOD_TYPE 70/ST_PRG_LNG 137/ST_PROJ_GUIDLINE 50/ST_PSTATE_CH 50/ST_PSTATE_DH 50/ST_PSTATE 50/ST_PSTATE_SH 258/ST_OPT_CTRL 282/ST_UML_RECEPT 140/ST_REINT_RELSHP
ARIS Methods
11-1548
Symbol Name Reint. relationship type Relation Relationship Relationship type Relationship type Risk Robot Rule Rule Rule operator (inst.) SAP function SAP function SAP function SAP function SAP SERM gen. Scenario Screen Screen Screen design Screen table Section Security protocol Separator Sequence Service
Symbol No. 7 20 237 519 6 282 368 357 45 256 73 76 77 78 275 71 39 525 16 325 288 619 292 675 378
Object Type No. 11/ST_REINT_RELSHP_TYPE 51/ST_REL 140/ST_RELSHP 11/ST_RELAT_TYPE 11/ST_RELSHP_TYPE 159/ST_RISK 116/ST_ROBO_PIC 50/ST_RULE_PIC 50/ST_OPR_RULE 152/ST_OPR_RULE_INST 22/ST_SAP_FUNC_1 22/ST_SAP_FUNC_2 22/ST_SAP_FUNC_3 22/ST_SAP_FUNC_4 23/ST_SAP_SERM_GEN 22/ST_SCENARIO 31/ST_SCRN 31/ST_SCRN_2 32/ST_SCRN_DSGN 183/ST_SCRN_TBL 165/ST_SECT 245/ST_SECURE 169/ST_SEPRT 250/ST_XML_SEQUENCE 153/ST_SERV_PIC
ARIS Methods
11-1549
Symbol Name Service Shift Shift cycle Shift plan Signal Solution Spin box Spin box Split/Synchro Split/Synchro State State State machine Strategic objective Strategy Structural element Subroutine Substitute product Substitute service Subsystem Subsystem instance Supplier System attribute domain System function (actual) System function (target)
Symbol No. 530 425 424 423 792 283 753 754 463 464 174 458 791 550 549 466 720 381 379 781 782 383 191 229 230
Object Type No. 153/ST_SERV 217/ST_SHIFT 216/ST_SHIFT_CYC 215/ST_SHIFT_PLAN 280/ST_UML_SIGNAL 160/ST_SOLU 260/ST_SPINBOX_VERT 260/ST_SPINBOX_HORIZ 50/ST_SPLIT_1 50/ST_SPLIT_2 99/ST_STATE 153/ST_STATE_1 279/ST_STATE_MACH 86/ST_STRAT_OBJCTV 239/ST_STRATEGY_2 232/ST_STRCT_ELEMENT 22/ST_SUBPROG 153/ST_SPROD_PIC 153/ST_SSERV_PIC 270/ST_SUBSYSY 271/ST_SUBSYSY_INST 43/ST_SUPPL_PIC 110/ST_DOM_SYS_ATTR 22/ST_SYS_FUNC_ACT 22/ST_SYS_FUNC_TRG
ARIS Methods
11-1550
Symbol Name System organizational unit System organizational unit System organizational unit type System organizational unit type Tab Table Table sp. Take over MTR Take over UR Task Tech. operating supply class Technical operating supply Technical operating supply type Technical term Technical term Technical terms instance Telephone Telephone Terminator Text Text Text box Text table
Symbol No. 168 95 169 97 764 30 116 585 575 715 205 201 194 523 54 239 351 50 516 291 745 744 582
Object Type No. 12/ST_SYS_ORG_UNIT_2 12/ST_SYS_ORG_UNIT_1 13/ST_SYS_ORG_UNIT_TYPE_2 13/ST_SYS_ORG_UNIT_TYPE_1 31/ST_TAB 55/ST_TBL 73/ST_TBL_EX 22/ST_TRANS_FUNC_NO_CHAN G 22/ST_APPND_FUNC_NO_CHAN G 22/ST_TASK 115/ST_TECH_OP_SUPPLY_CLS 123/ST_TECH_OP_SUPPLY 119/ST_TECH_OP_SUPPLY_TYPE 58/ST_TTERM 58/ST_TECH_TERM 141/ST_TECH_TERM_INST 27/ST_PHONE_PIC 27/ST_PHONE 18/ST_TERMINAT 168/ST_TXT 168/ST_TXT_1 257/ST_TEXTBOX 14/ST_TXT_TAB
ARIS Methods
11-1551
Symbol Name Tf being prc.cmpl.pnd.w.cmpl. Tf being processed compl.pend. Tf being processed with compl. Tf has error status Tf is waiting Tf ready with complaint Tf suspended Tf suspended with complaint Tf will ab.cmpl.pnd.w.cmpl. Tf will abort Tf will abort compl. pend. Tf will abort with complaint Tf will be ssp. compl.pend. Tf will be ssp. with compl. Tf will be ssp.cmpl.pnd.w.cmpl.
Symbol No. 321 313 317 312 311 316 310 320 322 308 315 319 314 318 323
Object Type No. 158/ST_CMPL_PRCS_CMPL 158/ST_CMPL_PRCS 158/ST_PRCS_CMPL 158/ST_ERROR 158/ST_WAIT 158/ST_IDLE_CMPL 158/ST_SUSPEN 158/ST_BE_ABORT_CMPL 158/ST_CMPL_BE_ABORT_CMPL 158/ST_ABORT 158/ST_CMPL_BE_ABORT 158/ST_CANCEL_CMPL 158/ST_CMPL_BE_SUSPEN 158/ST_BE_SUSPEN_CMPL 158/ST_CMPL_BE_SUSPEN_CMP L
Tf will be suspended Time characteristic Time characteristic Time planner Time planner Tool Tool (actual) Tool (target) Transaction folder
309 586 603 342 700 370 711 710 270
158/ST_BE_SUSPEN 17/ST_KAT_TIME 19/ST_KAT_TIME_AT 27/ST_TPLAN_PIC 27/ST_INFO_CARR_TPLAN 119/ST_TOOL_PIC 255/ST_TOOL_ACT 255/ST_TOOL_TRG 158/ST_TASK_FOLD
ARIS Methods
11-1552
Symbol Name Transaction folder OK Transaction folder open Transaction folder stopped Transfer rule Transfer structure Transport system Transport system class Transport system type Transport systems Tree control Truck UML Model Unit characteristic Unit characteristic Update rule Use case Use case instance Value-added chain Value-added chain View View (physical) Warehouse equipment Warehouse equipment Warehouse equipment class Warehouse equipment type
Symbol No. 272 271 273 584 583 366 204 196 200 755 365 783 571 599 574 398 784 105 141 19 118 199 369 203 192
Object Type No. 158/ST_TASK_FOLD_OK 158/ST_TASK_FOLD_OPEN 158/ST_TASK_FOLD_HALT 22/ST_TRANS_FUNC 14/ST_TRANS_STRUC 118/ST_TRANSP_PIC 114/ST_TRNSP_SYS_CLS 118/ST_TRNSP_SYS_TYPE 122/ST_TRNSP_SYS 261/ST_TREECTRL 118/ST_VAN_PIC 272/ST_UML_MOD 17/ST_KAT_DIM 19/ST_KAT_DIM_AT 22/ST_APPND_FUNC 22/ST_USECASE 273/ST_USECASE_INST 22/ST_VAL_ADD_CHN_SML_1 22/ST_VAL_ADD_CHN_SML_2 57/ST_VIEW 75/ST_VIEW_PHYS 121/ST_WH_EQUIP 117/ST_STOCK 113/ST_WH_EQUIP_CLS 117/ST_WH_EQUIP_TYPE
ARIS Methods
11.13 Attribute Number, Length and Data Type (AttrTypeNum)
11-1553
Symbol Name Wastepaper basket Wastepaper basket Website Window Workstation XOR XOR operator (inst.) XOR rule XOR rule XOR/AND operator (inst.) XOR/AND rule XOR/OR operator (inst.) XOR/OR rule Y function Y function (left) Y function (right)
Symbol No. 341 699 768 766 509 676 255 44 528 258 132 260 135 82 83 84
Object Type No. 27/ST_WASTE_PIC 27/ST_INFO_CARR_WASTE 31/ST_WEBSITE 31/ST_WINDOW 54/ST_WORK_PLACE 251/ST_XML_XOR 152/ST_OPR_XOR_INST 50/ST_OPR_XOR_1 50/ST_XOR 152/ST_OPR_XOR_AND_INST 50/ST_XOR_AND 152/ST_OPR_XOR_OR_INST 50/ST_XOR_OR 22/ST_Y_FUNC 22/ST_Y_FUNC_LEFT 22/ST_Y_FUNC_RIGHT

Attribute Type Name *Release Absolute change in EMC Absolute time limits Access type 722 907 0/ABT_TIMESPAN 0/ABT_BOOL Duration Boolean 119 830 Type No. Attribute Type Length 0/ABT_COMBINED 7/ABT_FLOAT Combined Floating point number Data Type
ARIS Methods
11-1554
Attribute Type Name Achievement of objectives Acquisition costs Acquisition costs Action Action (FALSE) Action (TRUE) Action when time limit exceeded Activations Activity category Activity group Activity type Activity-based cost calculation Actual data Actual date of occurrence Actual duration Actual end date Actual performance Actual start date Actual time period Actual value
Type No. 1378 218 297 1197 104 103 1276 1122 1082 1458 1049 469
Attribute Type Length 20/ABT_VALUE 0/ABT_SINGLELINE 0/ABT_SINGLELINE 100/ABT_MULTILINE 200/ABT_MULTILINE 200/ABT_MULTILINE 1024/ABT_MULTILINE 5/ABT_INTEGER 6/ABT_SINGLELINE 50/ABT_MULTILINE 20/ABT_VALUE 0/ABT_VALUE
Data Type Value One-liner One-liner N-liner N-liner N-liner N-liner Integer One-liner N-liner Value Value
402 403
0/ABT_FLOAT 20/ABT_DATE
Floating point number Date
407 405 476 404 1376 1377
20/ABT_INTEGER 20/ABT_DATE 20/ABT_FLOAT 20/ABT_DATE 20/ABT_SINGLELINE 20/ABT_FLOAT
Integer Date Floating point number Date One-liner Floating point number
ARIS Methods
11-1555
Attribute Type Name Added from RBE database Address Aggregated target duration Aggregation Aggregation kind ALE ALE Attribute Alias Alignment Alternative assignment Alternative status Amount Amount of damages Amount of damages Amount per time unit Analysis attributes Analysis name and ID
Type No. 1661 244 421 456 1219 360 361 999 947 592 490 269 1564 1625 247 115 1653
Attribute Type Length 2/ABT_BOOL 512/ABT_MULTILINE 20/ABT_INTEGER 2/ABT_BOOL 15/ABT_VALUE 0/ABT_FLOAT 2/ABT_BOOL 256/ABT_SINGLELINE 256/ABT_VALUE 2/ABT_BOOL 2/ABT_VALUE 30/ABT_INTEGER 0/ABT_TIMESTAMP 50/ABT_VALUE 20/ABT_INTEGER 0/ABT_COMBINED 10000/ABT_MULTILIN E
Data Type Boolean N-liner Integer Boolean Value Floating point number Boolean One-liner Value Boolean Value Integer Point in time Value Integer Combined N-liner
Annotations AO Document Application
1598 1052 226
10000000/ABT_MULT ILINE 6/ABT_SINGLELINE 512/ABT_MULTILINE
N-liner One-liner N-liner
ARIS Methods
11-1556
Attribute Type Name Archiving ARIS Applications As button? Aspect Assessment rate Assignment type Association kind Association role (Src) Association role (Trg) Attribute category Attribute default Attribute flag Attribute type number Attributes Attributes of external system Author
Type No. 136 856 905 146 357 1253 1648 1362 1363 518 1502 798 102 793 737 1660
Attribute Type Length 2/ABT_BOOL 0/ABT_MULTILINE 2/ABT_BOOL 512/ABT_MULTILINE 20/ABT_FLOAT 25/ABT_VALUE 50/ABT_VALUE 100/ABT_MULTILINE 100/ABT_MULTILINE 20/ABT_VALUE 512/ABT_VALUE 10/ABT_VALUE 10/ABT_INTEGER 0/ABT_SINGLELINE 0/ABT_MULTILINE 10000/ABT_SINGLELI NE
Data Type Boolean N-liner Boolean N-liner Floating point number Value Value N-liner N-liner Value Value Value Integer One-liner N-liner One-liner
Author Auto central Auto decentralized Automated Automatic Automatic event Automatic event
46 79 82 6 1252 1057 1232
50/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
N-liner Boolean Boolean Boolean Boolean Boolean Boolean
ARIS Methods
11-1557
Attribute Type Name Automatically controlled Available capacity Available in template Average amount of damages Average capacity Average initial wait time Average reduced relative probability Average relative probability Average transaction frequency Average wait time Avg. access Avg. costs for depreciation/repair/maintenanc e Avg. energy costs Avg. imputed interest Avg. material costs Avg. number
Type No. 1228 484 1468 1552
Attribute Type Length 2/ABT_BOOL 20/ABT_FLOAT 10000000/ABT_MULT ILINE 20/ABT_COMBINED
Data Type Boolean Floating point number N-liner Combined
1131 643 1637
10/ABT_FLOAT 20/ABT_COMBINED 20/ABT_RANGEFLOAT
Floating point number Combined Floating point number domain
1573 1657 531 45 62
20/ABT_RANGEFLOAT 20/ABT_INTEGER 20/ABT_COMBINED 12/ABT_INTEGER 20/ABT_COMBINED
Floating point number domain Integer Combined Integer Combined
61 63 58 33
20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 10/ABT_INTEGER
Combined Combined Combined Integer
ARIS Methods
11-1558
Attribute Type Name Avg. operating supplies costs Avg. orientation time Avg. other costs Avg. personnel costs Avg. processing time Avg. throughput time Avg. throughput time Avg. total costs Avg. total time Avg. transmission time Avg. utilization costs Avg. wait time Baan parameter Baan user Background color Background job processor Backoffice Balanced Scorecard Bank code Basic driver
Type No. 60 67 57 59 68 1462 69 65 647 74
Attribute Type Length 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Data Type Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined
232
10/ABT_FLOAT 20/ABT_COMBINED
Floating point number Combined
Avg. various overhead 64
66 1086 1103 797 1403
20/ABT_COMBINED 17/ABT_SINGLELINE 12/ABT_MULTILINE 50/ABT_SINGLELINE 2/ABT_BOOL
Combined One-liner N-liner One-liner Boolean
1402 1370 1292 754
2/ABT_BOOL 0/ABT_MULTILINE 9/ABT_INTEGER 2/ABT_BOOL
Boolean N-liner Integer Boolean
ARIS Methods
11-1559
Attribute Type Name Basis of valuation Batch central Batch decentralized Batch-controlled Benchmarking Benchmarks Bitmap Bitmap path Body Book title Bottom margin BottomCenter BottomLeft BottomMargin BottomRight Bound Break duration Break start BSC - Remark/Example Budgetary relation
Type No. 1642 78 81 1229 913 573 792 782 976 12 780 1438 1437 1443 1439 1676 1156 1155 1381
Attribute Type Length 50/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 0/ABT_BOOL 0/ABT_FLOAT 0/ABT_SINGLELINE 256/ABT_SINGLELINE 10000000/ABT_MULT ILINE 100/ABT_MULTILINE 2/ABT_BOOL 1000/ABT_SINGLELIN E 1000/ABT_SINGLELIN E 10/ABT_INTEGER 1000/ABT_SINGLELIN E 256/ABT_INTEGER 30/ABT_TIMESPAN 30/ABT_TIMESPAN 10000000/ABT_MULT ILINE
Data Type Value Boolean Boolean Boolean Boolean Floating point number One-liner One-liner N-liner N-liner Boolean One-liner One-liner Integer One-liner Integer Duration Duration N-liner
955
256/ABT_MULTILINE
N-liner
ARIS Methods
11-1560
Attribute Type Name Buffered Building cluster attributes Business control Business function category Business Model Key (Baan) Business process category Buttons Calculate cost center percentage utilization Calculate process performance Calculated end date Calculated operation costs Calculated planned project costs Calculated project duration Calculated project end date Calculated project start date
Type No. 1469 2087 751 1080 1090 1081 1592 1289 1288
Attribute Type Length 2/ABT_BOOL 0/ABT_BOOL 0/ABT_INTEGER 6/ABT_SINGLELINE 6/ABT_SINGLELINE 6/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
Data Type Boolean Boolean Integer One-liner One-liner One-liner Boolean Boolean Boolean
428 438
20/ABT_DATE 20/ABT_FLOAT
Date Floating point number
331 430 410
20/ABT_FLOAT 20/ABT_COMBINED 20/ABT_DATE
Floating point number Combined Date
408
20/ABT_DATE
Date
ARIS Methods
11-1561
Attribute Type Name Calculated project work Calculated resource costs Calculated resource work Calculated start date Calculation Calculation method Calculation type for fixed date calculation Calendar end Calendar start Call mode Call when time limit exceeded Can be delegated Can be reset Cancel possible Capacity Capacity Caption Cardinality (source)
Type No. 333 488
Attribute Type Length 20/ABT_FLOAT 20/ABT_FLOAT
Data Type Floating point number Floating point number
487 427 561 1168 1259 1151 1150 1407 1275
20/ABT_FLOAT 20/ABT_DATE 10000000/ABT_MULT ILINE 4/ABT_RANGEINTEGE R 30/ABT_VALUE 30/ABT_TIMESTAMP 30/ABT_TIMESTAMP 30/ABT_VALUE 2/ABT_BOOL
Floating point number Date N-liner Integer domain Value Point in time Point in time Value Boolean
692 691 690 1304 290 883 149
2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 8/ABT_RANGEINTEGE R 0/ABT_VALUE 1/ABT_SINGLELINE 512/ABT_VALUE
Boolean Boolean Boolean Integer domain Value One-liner Value
ARIS Methods
11-1562
Attribute Type Name Cardinality (source) Cardinality (target) Cardinality (target) Category Category Category Category Category Cause of complaint CD Number CD Relationship denominator CD Relationship numerator Central control code Certification Chain of tasks Change expression Change expression language Change history
Type No. 41 150 42 228 229 253 267 929 894 1164 1166 1165
Attribute Type Length 200/ABT_VALUE 512/ABT_VALUE 200/ABT_VALUE 512/ABT_VALUE 512/ABT_VALUE 100/ABT_MULTILINE 10/ABT_SINGLELINE 0/ABT_INTEGER 10000000/ABT_MULT ILINE 100/ABT_INTEGER 2/ABT_RANGEINTEGE R 1/ABT_INTEGER
Data Type Value Value Value Value Value N-liner One-liner Integer N-liner Integer Integer domain Integer
752 607 676 1697 1698 1599
300/ABT_MULTILINE 0/ABT_SINGLELINE 2/ABT_BOOL 10000000/ABT_MULT ILINE 500/ABT_SINGLELINE 10000000/ABT_MULT ILINE
N-liner One-liner Boolean N-liner One-liner N-liner
Change in percent Change management
831 1431
6/ABT_FLOAT 0/ABT_VALUE
Floating point number Value
ARIS Methods
11-1563
Attribute Type Name Change management Change privilege Changeability Changed by Changed on Chapter name Characteristics classifying as to contents CharSet Check box Checked by Checked on Checkin/Checkout order ID Checkin/Checkout order name Checkin/Checkout transfer status CICO mode Citizen Class Class attribute Class operation Classification
Type No. 1453 875 1613 615 614 14 933 1447 1595 613 612 741 739 738
Attribute Type Length 2/ABT_BOOL 2/ABT_BOOL 50/ABT_VALUE 100/ABT_MULTILINE 20/ABT_DATE 100/ABT_SINGLELINE 2/ABT_BOOL 10/ABT_INTEGER 2/ABT_BOOL 100/ABT_MULTILINE 20/ABT_DATE 21/ABT_MULTILINE 81/ABT_MULTILINE 2/ABT_BOOL
Data Type Boolean Boolean Value N-liner Date One-liner Boolean Integer Boolean N-liner Date N-liner N-liner Boolean
685 959 1392 147 148 87
2/ABT_MULTILINE 20/ABT_COMBINED 10000000/ABT_MULT ILINE 2/ABT_BOOL 2/ABT_BOOL 512/ABT_VALUE
N-liner Combined N-liner Boolean Boolean Value
ARIS Methods
11-1564
Attribute Type Name Cleaning cycle Client Client name Color (hexadecimal) Color (RGB) Column Column width Combo flag Commit resource Communication channel Company Company Company affiliation Company affiliation Company code Company key Company-external Company-internal Comparison attribute Comparison operator Comparison operator Comparison value Comparison value (logical)
Type No. 309 375 1220 1571 1099 948 946 790 1388 460 1582 678 243 84 327 1088 261 260 108 1470 497 498 1125
Attribute Type Length 0/ABT_VALUE 4/ABT_SINGLELINE 256/ABT_MULTILINE 6/ABT_SINGLELINE 9/ABT_INTEGER 0/ABT_VALUE 256/ABT_VALUE 20/ABT_VALUE 2/ABT_BOOL 2/ABT_SINGLELINE 250/ABT_SINGLELINE 2/ABT_BOOL 512/ABT_VALUE 512/ABT_VALUE 4/ABT_SINGLELINE 6/ABT_INTEGER 2/ABT_BOOL 2/ABT_BOOL 4/ABT_INTEGER 512/ABT_VALUE 20/ABT_VALUE 80/ABT_MULTILINE 2/ABT_BOOL
Data Type Value One-liner N-liner One-liner Integer Value Value Value Boolean One-liner One-liner Boolean Value Value One-liner Integer Boolean Boolean Integer Value Value N-liner Boolean
ARIS Methods
11-1565
Attribute Type Name Comparison value (numeric) Complaint duration Complaint pending Complete frame Completed Completeness Complexity Compressed period indicator Compression type Computer center (CC) costs Concurrency Concurrency Condition Condition
Type No. 1126 890 893 926 770 552 26 658 504 114 1457 977 1193 1365
Attribute Type Length 10/ABT_FLOAT 20/ABT_TIMESPAN 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 20/ABT_VALUE 10/ABT_SINGLELINE 0/ABT_MULTILINE 80/ABT_MULTILINE 20/ABT_COMBINED 15/ABT_VALUE 20/ABT_VALUE 100/ABT_MULTILINE 10000000/ABT_MULT ILINE
Data Type Floating point number Duration Boolean Boolean Boolean Value One-liner N-liner N-liner Combined Value Value N-liner N-liner
Condition Condition Condition (FALSE) Condition (TRUE) Condition is checked only once Condition language
263 700 121 120 698
2/ABT_BOOL 255/ABT_MULTILINE 200/ABT_MULTILINE 200/ABT_MULTILINE 2/ABT_BOOL
Boolean N-liner N-liner N-liner Boolean
1699
500/ABT_SINGLELINE
One-liner
ARIS Methods
11-1566
Attribute Type Name Condition type Conditions Config Config key Config value
Type No. 1050 207 1411 1393 1394
Attribute Type Length 20/ABT_VALUE 300/ABT_MULTILINE 0/ABT_MULTILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
Data Type Value N-liner N-liner N-liner N-liner
Conflict class Conflict type Connection role Connection role (passive) Connection shortcut Consider function allocation diagrams Constraint Constraint Constraint (Src) Constraint (Trg) Contact person Containment Containment (Src) Containment (Trg) Controllability
1368 1367 25 857
25/ABT_VALUE 25/ABT_VALUE 100/ABT_MULTILINE 100/ABT_MULTILINE
Value Value N-liner N-liner
1622 1286 156 967 1516 1517 1600 1522 1529 1530 554
10000000/ABT_MULT ILINE 2/ABT_BOOL 512/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 250/ABT_MULTILINE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE
N-liner Boolean N-liner N-liner N-liner N-liner N-liner Value Value Value Value
ARIS Methods
11-1567
Attribute Type Name Conversion factor Conversion to table Copied-from model Copied-from model version Copied-from type Copy Core competence Cost category ID Cost category No. Cost category type Cost center ID Cost center number Cost center performance Cost driver Cost driver quantity units Cost rate Cost rate Cost rate Cost volume Cost volume (total) Costs Costs
Type No. 801 863 1091 1092 1068 865 671 338 337 342 1167 1296 1171
Attribute Type Length 12/ABT_FLOAT 2/ABT_BOOL 6/ABT_SINGLELINE 10/ABT_SINGLELINE 512/ABT_VALUE 2/ABT_BOOL 20/ABT_VALUE 32/ABT_MULTILINE 10/ABT_SINGLELINE 2/ABT_SINGLELINE 2/ABT_BOOL 20/ABT_SINGLELINE 20/ABT_FLOAT
Data Type Floating point number Boolean One-liner One-liner Value Boolean Value N-liner One-liner One-liner Boolean One-liner Floating point number
564 565
20/ABT_SINGLELINE 0/ABT_SINGLELINE
One-liner One-liner
1295 140 485 1170 1471 293 295
20/ABT_COMBINED 20/ABT_FLOAT 20/ABT_FLOAT 20/ABT_FLOAT 20/ABT_FLOAT 0/ABT_SINGLELINE 100/ABT_SINGLELINE
Combined Floating point number Floating point number Floating point number Floating point number One-liner One-liner
ARIS Methods
11-1568
Attribute Type Name Costs Costs (CD) Costs for depreciation/repair/maintenanc e Costs per cost driver quantity unit Costs per unit Coverage quality Create Create privilege Created by Created in R/3 release Created on Creation date Creator Creator Creator (SAP) Critical code Critical date Currency Current capacity Current cost for computer center
Type No. 35 570 162
Attribute Type Length 0/ABT_INTEGER 20/ABT_FLOAT 0/ABT_MULTILINE
Data Type Integer Floating point number N-liner
568
0/ABT_FLOAT
Floating point number
219 1188 909 874 609 1238 608 584 1009 388 1233 397 767 334 1127 217
40/ABT_COMBINED 20/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL 100/ABT_MULTILINE 4/ABT_MULTILINE 20/ABT_DATE 20/ABT_TIMESTAMP 81/ABT_MULTILINE 50/ABT_MULTILINE 10000000/ABT_MULT ILINE 2/ABT_BOOL 10/ABT_DATE 7/ABT_SINGLELINE 10/ABT_INTEGER 0/ABT_SINGLELINE
Combined Value Boolean Boolean N-liner N-liner Date Point in time N-liner N-liner N-liner Boolean Date One-liner Integer One-liner
ARIS Methods
11-1569
Attribute Type Name Current costs Current duration Current end date Current object Current operation work Current planned project costs Current project duration Current project end date Current project start date Current project work
Type No. 417 416 434 632 415 332 431 411
Attribute Type Length 20/ABT_FLOAT 20/ABT_COMBINED 20/ABT_DATE 8/ABT_INTEGER 20/ABT_FLOAT 20/ABT_FLOAT 20/ABT_COMBINED 20/ABT_DATE
Data Type Floating point number Combined Date Integer Floating point number Floating point number Combined Date
409 423
20/ABT_DATE 20/ABT_FLOAT 20/ABT_TIMESTAMP 20/ABT_FLOAT
Date Floating point number Point in time Floating point number
Current provision time 884 Current resource costs Current resource work Current start date Current start time Current status Current user Customer Customer segment 400 432 885 362 633 462 762 401
20/ABT_FLOAT 20/ABT_DATE 20/ABT_TIMESTAMP 50/ABT_SINGLELINE 8/ABT_INTEGER 49/ABT_MULTILINE 512/ABT_VALUE
Floating point number Date Point in time One-liner Integer N-liner Value
ARIS Methods
11-1570
Attribute Type Name Customizing transaction Customizing view Cycle duration Cycle exit Cycle frequency Cyclical repeat Dangerous goods note Dangerous goods number Data management system Data source Data type Data type Data type Data type operations Database Database export Database management Date type Days/Year DBLogo
Type No. 1970 1969 1145 697 200 1143 283 282 11 1643 1501 494 501 277 249 1294 1003 1152 771 1452
Attribute Type Length 20/ABT_SINGLELINE 30/ABT_SINGLELINE 30/ABT_TIMESPAN 2/ABT_BOOL 20/ABT_INTEGER 2/ABT_BOOL 100/ABT_SINGLELINE 100/ABT_SINGLELINE 30/ABT_SINGLELINE 50/ABT_VALUE 512/ABT_VALUE 10/ABT_VALUE 20/ABT_VALUE 512/ABT_MULTILINE 100/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_VALUE 3/ABT_INTEGER 0/ABT_BITMAP
Data Type One-liner One-liner Duration Boolean Integer Boolean One-liner One-liner One-liner Value Value Value Value N-liner N-liner Boolean Boolean Value Integer Bitmap
ARIS Methods
11-1571
Attribute Type Name Deactivated Deadline date Deadline mode Deadline time Decimal places Decision key
Type No. 757 1071 1069 1070 34 1398
Attribute Type Length 2/ABT_BOOL 6/ABT_INTEGER 512/ABT_VALUE 4/ABT_INTEGER 3/ABT_INTEGER 10000000/ABT_MULT ILINE
Data Type Boolean Integer Value Integer Integer N-liner
Default Default (import) Default function Default name Default prefix Default screen Default value Default value Default value Default value language Degree of activation Degree of coverage Degree of division Degree of fulfillment
1036 56 950 734 1178 867 1507 1612 949 1705 1123 1182 52 1108
2/ABT_BOOL 512/ABT_MULTILINE 2/ABT_BOOL 20/ABT_MULTILINE 20/ABT_SINGLELINE 2/ABT_BOOL 100/ABT_SINGLELINE 1000/ABT_SINGLELIN E 150/ABT_MULTILINE 500/ABT_SINGLELINE 10/ABT_FLOAT 3/ABT_RANGEINTEGE R 512/ABT_VALUE 10/ABT_FLOAT
Boolean N-liner Boolean N-liner One-liner Boolean One-liner One-liner N-liner One-liner Floating point number Integer domain Value Floating point number
ARIS Methods
11-1572
Attribute Type Name Degree of goal accomplishment Degree of maturity Degree of requirement satisfaction Delayed forwarding possible Delete Delete privilege Deleting rule Dependencies Depth of version tree Derived Derived attribute Derived attribute type Derived from version Description
Type No. 1384 672 86 688
Attribute Type Length 20/ABT_FLOAT 4/ABT_INTEGER 512/ABT_VALUE 2/ABT_BOOL
Data Type Floating point number Integer Value Boolean
911 876 877 1628 1034 144 275 323 1031 1418
2/ABT_BOOL 2/ABT_BOOL 512/ABT_VALUE 0/ABT_COMBINED 3/ABT_INTEGER 2/ABT_BOOL 2/ABT_BOOL 0/ABT_SINGLELINE 10/ABT_SINGLELINE 10000000/ABT_MULT ILINE
Boolean Boolean Value Combined Integer Boolean Boolean One-liner One-liner N-liner
Description (dynamic condition) Description 1 Description 1 Description 10 Description 2 Description 2
1106 650 916 708 651 919
60/ABT_MULTILINE 256/ABT_MULTILINE 512/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 512/ABT_MULTILINE
N-liner N-liner N-liner N-liner N-liner N-liner
ARIS Methods
11-1573
Attribute Type Name Description 3 Description 3 Description 4 Description 4 Description 5 Description 6 Description 7 Description 8 Description 9 Description of attribute derivation Description of eEPC (build time) Description of eEPC (run time) Description of the calculation method Description on printout Description/Definition
Type No. 652 922 653 925 654 655 705 706 707 324 681 682
Attribute Type Length 256/ABT_MULTILINE 512/ABT_MULTILINE 256/ABT_MULTILINE 512/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 256/ABT_MULTILINE 400/ABT_SINGLELINE 20/ABT_INTEGER 20/ABT_INTEGER
Data Type N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner One-liner Integer Integer
1204 1035 9
3000/ABT_MULTILINE 10/ABT_MULTILINE 10000000/ABT_MULT ILINE
N-liner N-liner N-liner
Descriptive text Desired degree of coverage Desired end after instance creation
800 1185
80/ABT_MULTILINE 3/ABT_RANGEINTEGE R
N-liner Integer domain
714
20/ABT_TIMESPAN
Duration
ARIS Methods
11-1574
Attribute Type Name Desired end time Desired processing time Desired start after instance creation Desired start time Desired total time Desktop integration Development costs Development costs Development costs (estimated) Development effort Development effort Development effort (estimated) Diagrams
Type No. 729 723 711 726 717 458 116 117 118
Attribute Type Length 20/ABT_TIMESTAMP 20/ABT_TIMESPAN 20/ABT_TIMESPAN 20/ABT_TIMESTAMP 20/ABT_TIMESPAN 2/ABT_SINGLELINE 0/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Data Type Point in time Duration Duration Point in time Duration One-liner Combined Combined Combined
110 111 112 1610
0/ABT_INTEGER 10/ABT_COMBINED 10/ABT_COMBINED 10000000/ABT_MULT ILINE
Integer Combined Combined N-liner
Digit Direction
954 1414
30/ABT_MULTILINE 10000000/ABT_MULT ILINE
N-liner N-liner
Direction Direction Direction of planning Disabled
1611 983 466 1534
50/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 2/ABT_BOOL
Value Value Value Boolean
ARIS Methods
11-1575
Attribute Type Name Discriminator Disjoint Display tuple Distinguished name Distribution Distribution according to cost driver Distribution list District attributes Do Do/activity Doc development Doc requirements definition Document handling in loops Domain type Don't generate call DrawLines Driver category Driver value Due date of fixed costs Dunning period
Type No. 1673 145 879 1578 1141 829 745 2086 1190 209 861 860 703
Attribute Type Length 32000/ABT_SINGLELI NE 2/ABT_BOOL 2/ABT_INTEGER 550/ABT_SINGLELINE 80/ABT_LONGTEXT 2/ABT_BOOL 10000000/ABT_MULT ILINE 0/ABT_BOOL 100/ABT_MULTILINE 300/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 20/ABT_VALUE
Data Type One-liner Boolean Integer One-liner Longtext Boolean N-liner Boolean N-liner N-liner N-liner N-liner Value
123 912 1445 808 768 412 512
512/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL 50/ABT_VALUE 9/ABT_FLOAT 20/ABT_VALUE 40/ABT_MULTILINE
Value Boolean Boolean Value Floating point number Value N-liner
ARIS Methods
11-1576
Attribute Type Name Duration Duration of damage effect Duration of interruption Dynamic arguments Dynamic arguments language Dynamic condition Dynamic template Dynamic wait time Dynamic wait time sum E-mail address Earliest date of occurrence Earliest end after instance creation Earliest end date Earliest end time Earliest start after instance creation Earliest start date Earliest start time
Type No. 1542 1631
Attribute Type Length 20/ABT_RANGEINTEG ER 50/ABT_TIMESPAN
Data Type Integer domain Duration
891 1693 1694 1095 1396 576 1114
20/ABT_TIMESPAN 10000000/ABT_MULT ILINE 500/ABT_SINGLELINE 6/ABT_MULTILINE 2/ABT_BOOL 20/ABT_INTEGER 30/ABT_TIMESPAN
Duration N-liner One-liner N-liner Boolean Integer Duration
509 1630
512/ABT_SINGLELINE 50/ABT_DATE
One-liner Date
713 394 728 710
20/ABT_TIMESPAN 20/ABT_DATE 20/ABT_TIMESTAMP 20/ABT_TIMESPAN
Duration Date Point in time Duration
392 725
20/ABT_DATE 20/ABT_TIMESTAMP
Date Point in time
ARIS Methods
11-1577
Attribute Type Name Early warning indicators Editor
Type No. 1639 1672
Attribute Type Length 1000/ABT_MULTILINE 10000000/ABT_MULT ILINE
Data Type N-liner N-liner
eEPC (build time) eEPC (run time) Element key EMC target value EMC value Employee Employee council name Employee council number Employee key Encoded Encoding End after instance creation End date End date End date End date End of complaint End of compression
628 679 1671 766 763 254 842
8/ABT_INTEGER 8/ABT_INTEGER 255/ABT_SINGLELINE 13/ABT_FLOAT 13/ABT_FLOAT 100/ABT_SINGLELINE 512/ABT_SINGLELINE
Integer Integer One-liner Floating point number Floating point number One-liner One-liner
841 1102 1587 1474 844 1154 1424 1432 370 887 662
2/ABT_INTEGER 8/ABT_MULTILINE 2/ABT_BOOL 20/ABT_MULTILINE 20/ABT_MULTILINE 30/ABT_TIMESTAMP 20/ABT_DATE 20/ABT_DATE 20/ABT_DATE 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP
Integer N-liner Boolean N-liner N-liner Point in time Date Date Date Point in time Point in time
ARIS Methods
11-1578
Attribute Type Name End of interruption End step End time End time after instance creation Energy costs enfinity English descriptive text Entry Entry/action Error connector Error message on non-compliance Estimated duration Evaluate condition immediately Evaluation Evaluation time Event Event Event classification Event type Event/action
Type No. 889 694 364 896 161 1410 1666 1189 210 1419 634 368 699 1201 635 1196 206 224 16 212
Attribute Type Length 20/ABT_TIMESTAMP 2/ABT_BOOL 20/ABT_TIMESTAMP 20/ABT_TIMESPAN 0/ABT_MULTILINE 0/ABT_MULTILINE 10000000/ABT_MULT ILINE 100/ABT_MULTILINE 300/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 20/ABT_COMBINED 2/ABT_BOOL 0/ABT_BOOL 20/ABT_TIMESTAMP 100/ABT_MULTILINE 300/ABT_MULTILINE 0/ABT_VALUE 512/ABT_VALUE 300/ABT_MULTILINE
Data Type Point in time Boolean Point in time Duration N-liner N-liner N-liner N-liner N-liner Boolean Boolean Combined Boolean Boolean Point in time N-liner N-liner Value Value N-liner
ARIS Methods
11-1579
Attribute Type Name Exceptions Excluded Execution sequence Existence Exit Exit possible Exit/action Expand Expense Expense Expense Expense percentage (%) Expired Expiry date Exponential representation External External applications External documents External entities External entity 1 External entity 2
Type No. 1526 1059 1278 135 1191 689 211 952 53 571 72 572 1017 1048 807
Attribute Type Length 32000/ABT_MULTILIN E 2/ABT_BOOL 4/ABT_INTEGER 2/ABT_BOOL 100/ABT_MULTILINE 2/ABT_BOOL 300/ABT_MULTILINE 2/ABT_BOOL 0/ABT_VALUE 0/ABT_FLOAT 20/ABT_COMBINED 20/ABT_FLOAT 2/ABT_BOOL 256/ABT_DATE 2/ABT_BOOL
Data Type N-liner Boolean Integer Boolean N-liner Boolean N-liner Boolean Value Floating point number Combined Floating point number Boolean Date Boolean
17 704 619 1481 1482 1483
2/ABT_BOOL 0/ABT_VALUE 10000000/ABT_MULT ILINE 0/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE
Boolean Value N-liner N-liner N-liner N-liner
ARIS Methods
11-1580
Attribute Type Name External entity 3 External entity 4 External entity 5 External event External ID Extract creation date Extract name and ID Factor Fax number Feasibility Federal government Federal land Field type Field type Field type File name Filter object type key First name Fixed costs per operation Fixed date Fixed plan operation costs Folder rule test
Type No. 1484 1485 1486 1055 740 1655 1652 785 246 558 957 958 1586 1590 1591 585 373 1243 413
Attribute Type Length 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 2/ABT_BOOL 20/ABT_FOREIGN_ID 20/ABT_DATE 10000/ABT_MULTILIN E 4/ABT_INTEGER 512/ABT_MULTILINE 20/ABT_VALUE 20/ABT_COMBINED 20/ABT_COMBINED 100/ABT_VALUE 100/ABT_VALUE 100/ABT_VALUE 256/ABT_FILE 20/ABT_SINGLELINE 64/ABT_MULTILINE 20/ABT_FLOAT
Data Type N-liner N-liner N-liner Boolean External identifier Date N-liner Integer N-liner Value Combined Combined Value Value Value Link/File One-liner N-liner Floating point number
396 440
20/ABT_DATE 20/ABT_FLOAT
Date Floating point number
736
2024/ABT_MULTILINE
N-liner
ARIS Methods
11-1581
Attribute Type Name Font Font color Font format Font format management Font size FontName FontSize Footer 1 Footer 2 Footer 3 Footer 4 Footer 5 Footer 6 Foreign key relation Format Forwarding allowed Frame Frame width Free attribute type group 1 Free attribute type group 2 Free attribute type group 3
Type No. 795 796 880 1004 881 1448 1449 601 602 603 604 605 606 897 250 1251 776 781 2089
Attribute Type Length 50/ABT_SINGLELINE 50/ABT_SINGLELINE 0/ABT_INTEGER 2/ABT_BOOL 2/ABT_INTEGER 256/ABT_MULTILINE 5/ABT_MULTILINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 2/ABT_BOOL 40/ABT_INTEGER 2/ABT_BOOL 0/ABT_INTEGER 4/ABT_INTEGER 0/ABT_BOOL
Data Type One-liner One-liner Integer Boolean Integer N-liner N-liner One-liner One-liner One-liner One-liner One-liner One-liner Boolean Integer Boolean Integer Integer Boolean
2090 2091
0/ABT_BOOL 0/ABT_BOOL
Boolean Boolean
ARIS Methods
11-1582
Attribute Type Name Free attribute type group 4 Free attribute type group 5 Free attributes Free market Free search access Frequency Frequency of execution Frequency per time period Frequency per time period Frequency per time unit Frequency, annually Frequency, daily Frequency, monthly Frequency, weekly Friendship Friendship (Src) Friendship (Trg) Full name Full name Function category
Type No. 2092 2093
Attribute Type Length 0/ABT_BOOL 0/ABT_BOOL
Data Type Boolean Boolean
984 960 1266 27 106 202
0/ABT_VALUE 20/ABT_COMBINED 2/ABT_BOOL 0/ABT_SINGLELINE 12/ABT_INTEGER 20/ABT_INTEGER
Value Combined Boolean One-liner Integer Integer
310 301 21 20 19 22 1510 1520 1521 1007 28 133
100/ABT_INTEGER 100/ABT_INTEGER 12/ABT_INTEGER 12/ABT_INTEGER 12/ABT_INTEGER 12/ABT_INTEGER 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 100/ABT_MULTILINE 255/ABT_MULTILINE 512/ABT_VALUE
Integer Integer Integer Integer Integer Integer Boolean Boolean Boolean N-liner N-liner Value
ARIS Methods
11-1583
Attribute Type Name Function category Function key Function privileges Function type Function type Function type number Function use Functional block attributes Future significance General conditions
Type No. 901 1085 1001 18 818 756 109 2088 1186 560
Attribute Type Length 0/ABT_BOOL 6/ABT_SINGLELINE 0/ABT_MULTILINE 512/ABT_VALUE 0/ABT_INTEGER 1/ABT_INTEGER 0/ABT_INTEGER 0/ABT_BOOL 20/ABT_VALUE 10000000/ABT_MULT ILINE
Data Type Boolean One-liner N-liner Value Integer Integer Integer Boolean Value N-liner
Group Half years/Year Hazard class Head of cost center Header 1 Header 2 Header 3 Header 4 Header 5 Header 6 Heading 1 Heading 2
1466 775 281 330 595 596 597 598 599 600 15 13
10000000/ABT_MULT ILINE 1/ABT_INTEGER 100/ABT_SINGLELINE 22/ABT_MULTILINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 200/ABT_MULTILINE 200/ABT_MULTILINE
N-liner Integer One-liner N-liner One-liner One-liner One-liner One-liner One-liner One-liner N-liner N-liner
ARIS Methods
11-1584
Attribute Type Name Height Help file Help text code Help text code 2 Hidden Hide cost driver Hierarchy level Hierarchy number History Home directory Home page Horizontal Hyperlink Icon path Identifier Identifying Identifying characteristics Ignore Impart frame Implementation help Important tasks
Type No. 784 862 1043 1044 898 1309 1285 1390 1472 732 965 1446 1589 787 55 151 932 1506 927 1042 546
Attribute Type Length 4/ABT_FLOAT 512/ABT_MULTILINE 32/ABT_SINGLELINE 32/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 5/ABT_INTEGER 10/ABT_MULTILINE 10000000/ABT_MULT ILINE 128/ABT_MULTILINE 256/ABT_SINGLELINE 2/ABT_BOOL 512/ABT_SINGLELINE 256/ABT_SINGLELINE 32/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 20/ABT_VALUE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
Data Type Floating point number N-liner One-liner One-liner Boolean Boolean Integer N-liner N-liner N-liner One-liner Boolean One-liner One-liner One-liner Boolean Boolean Boolean Value N-liner N-liner
ARIS Methods
11-1585
Attribute Type Name Improvement potential Imputed interest In the toolbar In use since Incoming process folders Index Index 1 Index 2 Index 3 Index 4 Index unit 1 Index unit 2 Index unit 3 Index unit 4 Indicator type Individual access privileges Individual usage factor specification per model InDoc Information object class
Type No. 1427 163 522 129 1121
Attribute Type Length 10000000/ABT_MULT ILINE 0/ABT_MULTILINE 2/ABT_BOOL 12/ABT_DATE 5/ABT_INTEGER
Data Type N-liner N-liner Boolean Date Integer
1172 915 918 921 924 914 917 920 923 1382 1241 1308
3/ABT_RANGEINTEGE R 12/ABT_FLOAT 12/ABT_FLOAT 12/ABT_FLOAT 12/ABT_FLOAT 50/ABT_SINGLELINE 50/ABT_SINGLELINE 50/ABT_SINGLELINE 50/ABT_SINGLELINE 20/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL
Integer domain Floating point number Floating point number Floating point number Floating point number One-liner One-liner One-liner One-liner Value Boolean Boolean
937 930
200/ABT_MULTILINE 2/ABT_BOOL
N-liner Boolean
ARIS Methods
11-1586
Attribute Type Name Information system Initial value Initial value language Initial wait time Initial wait time Input
Type No. 677 973 1703 641 666 1417
Attribute Type Length 2/ABT_BOOL 256/ABT_MULTILINE 500/ABT_SINGLELINE 0/ABT_TIMESTAMP 20/ABT_COMBINED 10000000/ABT_MULT ILINE
Data Type Boolean N-liner One-liner Point in time Combined N-liner
Installation status Instance creation time Instance value Integrity conditions Interaction template name Interface implementation Internal Internal entities Internal entity 1 Internal entity 2 Internal entity 3 Internal entity 4 Internal entity 5 Internal name
124 639 495 273 1395 1538 24 1475 1476 1477 1478 1479 1480 858
0/ABT_VALUE 20/ABT_TIMESTAMP 80/ABT_MULTILINE 100/ABT_MULTILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 2/ABT_BOOL 0/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 40/ABT_MULTILINE
Value Point in time N-liner N-liner N-liner N-liner Boolean N-liner N-liner N-liner N-liner N-liner N-liner N-liner
ARIS Methods
11-1587
Attribute Type Name Internal name (passive) Internal process (actual) Internal process (target) Interruptible Interruption time sum Interval duration Invariances Inventory number Inventory number Is preset Is read Is subprocess IsAbstract IsAbstract IsActive IsAsynchronous IsBinary IsChangeable (Src) IsChangeable (Trg) IsConcurrent IsDynamic
Type No. 859 542
Attribute Type Length 40/ABT_MULTILINE 20/ABT_FLOAT
Data Type N-liner Floating point number
543 1297 1306 1140 1601 227 315 669 670 1089 155 970 1646 1684 2084 1015 1010 1678 1695
20/ABT_FLOAT 2/ABT_BOOL 20/ABT_TIMESPAN 30/ABT_TIMESPAN 10000000/ABT_MULT ILINE 100/ABT_SINGLELINE 100/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 20/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
Floating point number Boolean Duration Duration N-liner One-liner One-liner Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean
ARIS Methods
11-1588
Attribute Type Name IsInstantiable IsLeaf IsMultipleTrigger IsNavigatable (Src) IsNavigatable (Trg) ISO 9000 relevance IsOrdered (Src) IsOrdered (Trg) IsPersistent IsPolymorphic IsQuery IsRoot IsSpecification IsStatic IsSynch IsTypeScope IsVolatile IT block attributes IT software attributes IT system attributes Iterator key Key Key (Y/N)
Type No. 1674 969 1198 1012 978 255 1014 980 1645 974 975 968 1650 1536 1679 982 1537 2100 2099 2097 1670 1415 39
Attribute Type Length 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 0/ABT_MULTILINE 0/ABT_MULTILINE 0/ABT_MULTILINE 255/ABT_SINGLELINE 10000000/ABT_MULT ILINE 2/ABT_BOOL
Data Type Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean N-liner N-liner N-liner One-liner N-liner Boolean
ARIS Methods
11-1589
Attribute Type Name Key performance indicator evaluation Keyword Knowledge advantage Knowledge usage
Type No. 1499 76 1183 1184
Attribute Type Length 512/ABT_VALUE 80/ABT_MULTILINE 3/ABT_RANGEINTEGE R 3/ABT_RANGEINTEGE R
Data Type Value N-liner Integer domain Integer domain
Language Language Languages Last change Last change (SAP) Last change (Workflow) Last change in R/3 release Last evaluation Last modification date Last status (CMA) Last user Last user (SAP) Latest end after instance creation Latest end date Latest end time
1242 1616 379 1175 1236 660 1239 1563 583 1430 1290 1235 715
3/ABT_MULTILINE 500/ABT_SINGLELINE 500/ABT_MULTILINE 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 32/ABT_TIMESTAMP 4/ABT_MULTILINE 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 20/ABT_VALUE 100/ABT_MULTILINE 10000000/ABT_MULT ILINE 20/ABT_TIMESPAN
N-liner One-liner N-liner Point in time Point in time Point in time N-liner Point in time Point in time Value N-liner N-liner Duration
395 730
20/ABT_DATE 20/ABT_TIMESTAMP
Date Point in time
ARIS Methods
11-1590
Attribute Type Name Latest release Latest release Latest start after instance creation Latest start date Latest start time LDAP backup server 1 LDAP backup server 2 LDAP login LDAP login server URL Leadability Left margin LeftMargin Length Length Length of entry field License number Line position Lines Lines at roots Link 1 Link 2 Link 3 Link 4
Type No. 1659 93 712 393 727 1580 1581 1619 1579 553 777 1440 213 29 868 216 138 1593 1594 152 153 154 872
Attribute Type Length 10000/ABT_MULTILIN E 15/ABT_INTEGER 20/ABT_TIMESPAN 20/ABT_DATE 20/ABT_TIMESTAMP 250/ABT_SINGLELINE 250/ABT_SINGLELINE 2/ABT_BOOL 250/ABT_SINGLELINE 20/ABT_VALUE 2/ABT_BOOL 10/ABT_INTEGER 100/ABT_INTEGER 10/ABT_INTEGER 3/ABT_INTEGER 100/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 512/ABT_FILE 512/ABT_FILE 512/ABT_FILE 512/ABT_FILE
Data Type N-liner Integer Duration Date Point in time One-liner One-liner Boolean One-liner Value Boolean Integer Integer Integer Integer One-liner Boolean Boolean Boolean Link/File Link/File Link/File Link/File
ARIS Methods
11-1591
Attribute Type Name Linked process LNC Link1 LNC Title1 Local control code Local descriptive text Location Location type LockFlag Logical value Logo Lower limit Maintenance cycle Mandatory Manually Manufacturer Manufacturer Mapping Mapping language Material costs Material number Material type Matrix column title
Type No. 1083 1225 1224 753 1665 1644 91 1282 1075 1293 1361 300 701 83 23 314 1651 1704 158 280 285 1620
Attribute Type Length 6/ABT_SINGLELINE 1000/ABT_MULTILINE 100/ABT_MULTILINE 300/ABT_MULTILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 512/ABT_VALUE 2/ABT_BOOL 2/ABT_INTEGER 0/ABT_BITMAP 20/ABT_FLOAT 0/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL 50/ABT_SINGLELINE 100/ABT_SINGLELINE 500000/ABT_MULTILI NE 500/ABT_SINGLELINE 0/ABT_MULTILINE 100/ABT_SINGLELINE 512/ABT_VALUE 81/ABT_SINGLELINE
Data Type One-liner N-liner N-liner N-liner N-liner N-liner Value Boolean Integer Bitmap Floating point number Value Boolean Boolean One-liner One-liner N-liner One-liner N-liner One-liner Value One-liner
ARIS Methods
11-1592
Attribute Type Name Matrix modeler Matrix row title Max. costs for depreciation/repair/maintenanc e Max. energy costs Max. imputed interest Max. material costs Max. number Max. operating supplies costs Max. orientation time Max. orientation time Max. other costs Max. personnel costs Max. processing time Max. processing time Max. throughput time Max. throughput time Max. total costs Max. total time Max. transmission time Max. various overhead costs
Type No. 1617 1621 180
Attribute Type Length 0/ABT_BLOB 81/ABT_SINGLELINE 20/ABT_COMBINED
Data Type BLOB One-liner Combined
179 181 176 32 178
20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 10/ABT_INTEGER 20/ABT_COMBINED
Combined Combined Combined Integer Combined
193 533 175 177 194 527 1463 195 183 648 198
20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined
182
20/ABT_COMBINED
Combined
ARIS Methods
11-1593
Attribute Type Name Max. wait time Max. wait time Maximum amount of damages Maximum capacity Maximum initial wait time Maximum processing time Maximum reduced relative probability Maximum relative probability Maximum total time Maximum value Maximum wait time after start Mean orientation time Mean processing time Measure
Type No. 192 530 1551
Attribute Type Length 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Data Type Combined Combined Combined
1128 644
10/ABT_INTEGER 20/ABT_COMBINED
Integer Combined
724 1638 1635 718 1372 719 534 528 1425
20/ABT_TIMESPAN 20/ABT_RANGEFLOAT 20/ABT_RANGEFLOAT 20/ABT_TIMESPAN 20/ABT_FLOAT 20/ABT_TIMESPAN 20/ABT_COMBINED 20/ABT_COMBINED 10000000/ABT_MULT ILINE
Duration Floating point number domain Floating point number domain Duration Floating point number Duration Combined Combined N-liner
Measurement unit Measurement unit (CDU) Measurement unit of acquisition costs
299 566
512/ABT_VALUE 20/ABT_SINGLELINE
Value One-liner
220
512/ABT_VALUE
Value
ARIS Methods
11-1594
Attribute Type Name Measurement unit of computer center costs Measurement unit of cost center rate Measurement unit of costs Measurement unit of costs Measurement unit of costs Measurement unit of costs (CD) Measurement unit of development costs Measurement unit of development effort Measurement unit of duration Measurement unit of expense Measurement unit of production quantity Measurement unit of time Measurement unit of time Measurement unit of time interval
Type No. 221 455
Attribute Type Length 512/ABT_VALUE 30/ABT_SINGLELINE
Data Type Value One-liner
294 398 70 569
512/ABT_VALUE 512/ABT_VALUE 512/ABT_VALUE 20/ABT_SINGLELINE
Value Value Value One-liner
222 230 426
512/ABT_VALUE 512/ABT_VALUE 20/ABT_VALUE
Value Value Value
73 306 536
512/ABT_VALUE 100/ABT_SINGLELINE 512/ABT_VALUE
Value One-liner Value
71 581
512/ABT_VALUE 20/ABT_VALUE
Value Value
ARIS Methods
11-1595
Attribute Type Name Measurement unit of wait time sum Measurement unit of work Measuring procedure Measuring unit Message number Message on error Message type key Method changes Milestone Milestone ID Min. costs for depreciation/repair/maintenanc e Min. energy costs Min. imputed interest Min. material costs Min. number Min. operating supplies costs Min. orientation time Min. orientation time Min. other costs
Type No. 746 424
Attribute Type Length 100/ABT_VALUE 512/ABT_VALUE
Data Type Value Value
562 563 1194 735 374 1005 1248 467 171
10000000/ABT_MULT ILINE 20/ABT_SINGLELINE 100/ABT_MULTILINE 2/ABT_BOOL 20/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 20/ABT_COMBINED
N-liner One-liner N-liner Boolean One-liner Boolean Boolean Boolean Combined
170 172 167 31 169 189 532 166
20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 10/ABT_INTEGER 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Combined Combined Combined Integer Combined Combined Combined Combined
ARIS Methods
11-1596
Attribute Type Name Min. personnel costs Min. processing time Min. processing time Min. throughput time Min. throughput time Min. total costs Min. total time Min. transmission time Min. various overhead costs Min. wait time Min. wait time Minimum amount of damages Minimum capacity Minimum initial wait time Minimum processing time Minimum reduced relative probability Minimum relative probability Minimum total time Minimum value
Type No. 168 190 526 1461 191 174 646 197 173 188 529 1553
Attribute Type Length 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED 20/ABT_COMBINED
Data Type Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined Combined
1129 642
10/ABT_INTEGER 20/ABT_COMBINED
Integer Combined
720 1636 1634
20/ABT_TIMESPAN 20/ABT_RANGEFLOAT 20/ABT_RANGEFLOAT
Duration Floating point number domain Floating point number domain
716 1373
20/ABT_TIMESPAN 20/ABT_FLOAT
Duration Floating point number
ARIS Methods
11-1597
Attribute Type Name Miscellaneous requirements Model Model Model attribute number Model status Modification mode Modify Module code Months/Year Most important competitor Multiple procedures Multiple value tag Multiplicity Multiplicity Multiplicity (Src) Multiplicity (Trg) Must be signed Mutually exclusive damages Name Name Name (passive)
Type No. 1608 30 313 1387 380 525 910 1364 773 544 1264 274 141 1615 1013 998 849 1629 1 1000 279
Attribute Type Length 10000000/ABT_MULT ILINE 10/ABT_SINGLELINE 100/ABT_SINGLELINE 10/ABT_INTEGER 0/ABT_MULTILINE 20/ABT_VALUE 2/ABT_BOOL 20/ABT_VALUE 2/ABT_INTEGER 20/ABT_FLOAT 30/ABT_VALUE 100/ABT_VALUE 20/ABT_VALUE 500/ABT_SINGLELINE 6/ABT_SINGLELINE 6/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 81/ABT_MULTILINE 81/ABT_MULTILINE 56/ABT_MULTILINE
Data Type N-liner One-liner One-liner Integer N-liner Value Boolean Value Integer Floating point number Value Value Value One-liner One-liner One-liner Boolean Boolean N-liner N-liner N-liner
ARIS Methods
11-1598
Attribute Type Name Name direction Name ext. system (alias) Navigators Nesting depth Network access procedure Network extension Network topology Network topology Network typification No. of occurrences No. of occurrences avg. No. of occurrences max. No. of occurrences min. No. of occurrences trend Non-functional requirements Norm days Norm time Not
Type No. 1528 271 1444 696 240
Attribute Type Length 100/ABT_SINGLELINE 33/ABT_SINGLELINE 2/ABT_BOOL 4/ABT_INTEGER 512/ABT_VALUE
Data Type One-liner One-liner Boolean Integer Value
237 233 239 238 223 50 48 49
512/ABT_VALUE 512/ABT_VALUE 512/ABT_VALUE 512/ABT_VALUE 0/ABT_VALUE 12/ABT_INTEGER 12/ABT_INTEGER 12/ABT_INTEGER
Value Value Value Value Value Integer Integer Integer
51 1602 1073 1074 1045
60/ABT_SINGLELINE 10000000/ABT_MULT ILINE 5/ABT_INTEGER 4/ABT_INTEGER 2/ABT_BOOL
One-liner N-liner Integer Integer Boolean
ARIS Methods
11-1599
Attribute Type Name Not (dynamic condition) NOT NULL Notation Notation 1 Notation 2 Notation 3 Notation 4 Notation 5 Notations Note Number 1 Number 2 Number 3 Number being processed Number carried out Number circle Number dynamic waiting Number in orientation Number of channels Number of compressed models
Type No. 1105 225 1503 1494 1495 1496 1497 1498 1493 761 429 436 437 623 1117 1097 625 626 235 659
Attribute Type Length 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 0/ABT_MULTILINE 512/ABT_MULTILINE 20/ABT_INTEGER 20/ABT_INTEGER 20/ABT_INTEGER 4/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 4/ABT_INTEGER 4/ABT_INTEGER 10/ABT_INTEGER 8/ABT_INTEGER
Data Type Boolean Boolean Boolean N-liner N-liner N-liner N-liner N-liner N-liner N-liner Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer
ARIS Methods
11-1600
Attribute Type Name Number of compressed object definitions Number of consuming function executions Number of employees
Type No. 505
Attribute Type Length 10/ABT_INTEGER
Data Type Integer
1132 3
5/ABT_INTEGER 10/ABT_RANGEINTEG ER
Integer Integer domain
Number of events not yet evaluated Number of false events Number of function executions Number of instances during last sim. Number of interruptions during orientation Number of interruptions during processing Number of lines Number of process instances Number of process markers Number of producing function executions Number of required employees
750 749 1135 588
10/ABT_INTEGER 10/ABT_INTEGER 5/ABT_INTEGER 10/ABT_INTEGER
Integer Integer Integer Integer
1300 1301 870 1142 589
8/ABT_INTEGER 8/ABT_INTEGER 2/ABT_INTEGER 10/ABT_INTEGER 10/ABT_INTEGER
Integer Integer Integer Integer Integer
1133 580
5/ABT_INTEGER 20/ABT_INTEGER
Integer Integer
ARIS Methods
11-1601
Attribute Type Name Number of synchronizations Number of true events Number of utilizing function executions Number static waiting O category name O category number O competitive situation name O competitive situation number O equipment name O equipment number O location name O location number O size Object access ID Object ID
Type No. 2073 748
Attribute Type Length 20/ABT_INTEGER 10/ABT_INTEGER
Data Type Integer Integer
1134 624 833 832 835 834 839 838 837 836 840 668 1663
5/ABT_INTEGER 4/ABT_INTEGER 512/ABT_SINGLELINE 2/ABT_INTEGER 512/ABT_SINGLELINE 2/ABT_INTEGER 512/ABT_SINGLELINE 2/ABT_INTEGER 512/ABT_SINGLELINE 2/ABT_INTEGER 2/ABT_INTEGER 1024/ABT_MULTILINE 10000/ABT_SINGLELI NE
Integer Integer One-liner Integer One-liner Integer One-liner Integer One-liner Integer Integer N-liner One-liner
Object instance selection Object number Object type selection Occurrence
903 1096 902 541
2/ABT_BOOL 5/ABT_INTEGER 2/ABT_BOOL 0/ABT_VALUE
Boolean Integer Boolean Value
ARIS Methods
11-1602
Attribute Type Name Occurrence frequency Occurrence frequency Occurrence frequency of the average amount of damages Occurrence frequency of the maximum amount of damages Occurrence frequency of the minimum amount of damages OID Oldest release Online Online central Online decentralized Only direct data visible Operand Operand (logical) Operand (numeric) Operand position Operating resource number Operating supplies costs
Type No. 1565 1626 1555
Attribute Type Length 0/ABT_TIMESTAMP 50/ABT_VALUE 20/ABT_FLOAT
Data Type Point in time Value Floating point number
1554
20/ABT_FLOAT
1556
20/ABT_FLOAT
1535 1658 1227 77 80 906 1160 1161 1162 517 296 160
200/ABT_SINGLELINE 10000/ABT_MULTILIN E 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 80/ABT_MULTILINE 2/ABT_BOOL 50/ABT_LONGTEXT 20/ABT_INTEGER 100/ABT_SINGLELINE 0/ABT_MULTILINE
One-liner N-liner Boolean Boolean Boolean Boolean N-liner Boolean Longtext Integer One-liner N-liner
ARIS Methods
11-1603
Attribute Type Name Operating system Operation Operation name Operation status Operation work Operations Operator Operator type Optimization kind Optimization phase Optional attribute Optional function Order criterion Order processing Ordered Ordinal Ordinal number Org. diagram key Org. type key Org. unit key Organization Organizational level Organizational unit Orientation (always)
Type No. 10 1195 414 406 435 208 1159 47 1077 1078 37 85 931 962 143 869 1618 1039 1038 1037 616 1533 1583 578
Attribute Type Length 30/ABT_SINGLELINE 100/ABT_MULTILINE 255/ABT_MULTILINE 512/ABT_VALUE 20/ABT_FLOAT 300/ABT_MULTILINE 2/ABT_VALUE 512/ABT_VALUE 512/ABT_VALUE 6/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 20/ABT_VALUE 60/ABT_SINGLELINE 4/ABT_INTEGER 50/ABT_INTEGER 6/ABT_SINGLELINE 6/ABT_SINGLELINE 6/ABT_SINGLELINE 500/ABT_MULTILINE 3/ABT_INTEGER 250/ABT_SINGLELINE 2/ABT_BOOL
Data Type One-liner N-liner N-liner Value Floating point number N-liner Value Value Value One-liner Boolean Boolean Boolean Value One-liner Integer Integer One-liner One-liner One-liner N-liner Integer One-liner Boolean
ARIS Methods
11-1604
Attribute Type Name Orientation time Orientation time Orientation time Orientation time Orientation time sum Origin Origin Original language (SAP) Original path Other Other applicable documents Other costs Output Overlap time Overtime cost rate PA ID Packaging instruction/rule Packaging material number Packaging type
Type No. 1111 185 367 539 1115 100 257 1237 1291 961 618 157 1467 492 486 453 287 286
Attribute Type Length 50/ABT_LONGTEXT 0/ABT_COMBINED 20/ABT_COMBINED 0/ABT_VALUE 30/ABT_TIMESPAN 512/ABT_VALUE 0/ABT_MULTILINE 2/ABT_MULTILINE 10000000/ABT_MULT ILINE 20/ABT_COMBINED 10000000/ABT_MULT ILINE 0/ABT_MULTILINE 10000000/ABT_MULT ILINE 20/ABT_COMBINED 20/ABT_FLOAT 5/ABT_VALUE 100/ABT_SINGLELINE 100/ABT_SINGLELINE
Data Type Longtext Combined Combined Value Duration Value N-liner N-liner N-liner Combined N-liner N-liner N-liner Combined Floating point number Value One-liner One-liner
289
512/ABT_VALUE
Value
ARIS Methods
11-1605
Attribute Type Name Parameter Parameter 1 Parameter 2 Parameter 3 Parameter 4 Parameter description Parameter entities Parameter entity 1 Parameter entity 2 Parameter entity 3 Parameter entity 4 Parameter entity 5 Parameter key Parameter list Parameter list Parameter value Percentage Percentage allocation Percentage utilization Percentage utilization Percentage utilization Percentage utilization
Type No. 519 938 939 940 941 1409 1487 1488 1489 1490 1491 1492 1408 508 75 1076 1066 826 1283 316 5 591
Attribute Type Length 10000000/ABT_MULT ILINE 260/ABT_MULTILINE 260/ABT_MULTILINE 260/ABT_MULTILINE 260/ABT_MULTILINE 10000000/ABT_MULT ILINE 0/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 512/ABT_MULTILINE 10000000/ABT_MULT ILINE 2048/ABT_MULTILINE 128/ABT_MULTILINE 30/ABT_SINGLELINE 3/ABT_INTEGER 512/ABT_VALUE 4/ABT_FLOAT 10/ABT_FLOAT 10/ABT_FLOAT 10/ABT_FLOAT
Data Type N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner N-liner One-liner Integer Value Floating point number Floating point number Floating point number Floating point number
ARIS Methods
11-1606
Attribute Type Name Perform activity Performance scale Performance standard Period Period of review Period of time Period of time Period of time Period of time Period of time Period of time measurement unit Period of time measurement unit Period of time measurement unit Period of time measurement unit Period of transaction analysis Period of validity Person responsible Person status Personnel costs Phase key
Type No. 1101 474 478 1146 1627 1169 203 302 307 311 204
Attribute Type Length 2/ABT_BOOL 20/ABT_SINGLELINE 20/ABT_FLOAT 30/ABT_TIMESPAN 100/ABT_COMBINED 100/ABT_MULTILINE 60/ABT_COMBINED 100/ABT_COMBINED 100/ABT_COMBINED 100/ABT_COMBINED 512/ABT_VALUE
Data Type Boolean One-liner Floating point number Duration Combined N-liner Combined Combined Combined Combined Value
303 308 312
Value Value Value
1654 383 1584 510 159 1098
10000/ABT_MULTILIN E 0/ABT_DATE 250/ABT_SINGLELINE 20/ABT_VALUE 0/ABT_MULTILINE 6/ABT_MULTILINE
N-liner Date One-liner Value N-liner N-liner
ARIS Methods
11-1607
Attribute Type Name Picture PIP PIP standard processing time [min] Pipeline type Plan duration Plan start Plan value Planned CC cost ratetotal Planned performance Planning constraint Planning status Position Position Potential PPM query
Type No. 966 769 847
Attribute Type Length 256/ABT_FILE 0/ABT_FLOAT 6/ABT_INTEGER
Data Type Link/File Floating point number Integer
1406 1148 1147 1374 471 477 418 468 1247 214 557 1577
30/ABT_VALUE 30/ABT_TIMESPAN 30/ABT_TIMESTAMP 20/ABT_FLOAT 20/ABT_FLOAT 20/ABT_FLOAT 512/ABT_VALUE 2/ABT_VALUE 15/ABT_VALUE 15/ABT_INTEGER 20/ABT_VALUE 10000000/ABT_MULT ILINE
Value Duration Point in time Floating point number Floating point number Floating point number Value Value Value Integer Value N-liner
Prefix management Previous object Previous user Price Price list number Primary affiliation Primary quantity
1179 629 630 963 90 1277 251
2/ABT_BOOL 8/ABT_INTEGER 8/ABT_INTEGER 20/ABT_COMBINED 15/ABT_MULTILINE 2/ABT_BOOL 100/ABT_MULTILINE
Boolean Integer Integer Combined N-liner Boolean N-liner
ARIS Methods
11-1608
Attribute Type Name PrintBold PrintItalic Priority Priority Priority Priority Priority Priority Priority change allowed Privileges Privileges can be changed by creator Privileges can be changed by current user Probability Process category Process characteristics Process cost rate (pai) Process cost rate (total)
Type No. 1450 1451 1072 1119 1423 419 577 631 1249 1265 1274 1273
Attribute Type Length 5/ABT_MULTILINE 5/ABT_MULTILINE 5/ABT_INTEGER 2/ABT_INTEGER 2/ABT_RANGEINTEGE R 512/ABT_VALUE 3/ABT_INTEGER 8/ABT_INTEGER 2/ABT_BOOL 0/ABT_VALUE 2/ABT_BOOL 2/ABT_BOOL
Data Type N-liner N-liner Integer Integer Integer domain Value Integer Integer Boolean Value Boolean Boolean
199 1572 548 356
20/ABT_RANGEFLOAT 512/ABT_VALUE 0/ABT_MULTILINE 20/ABT_FLOAT
Floating point number domain Value N-liner Floating point number
358
20/ABT_FLOAT
ARIS Methods
11-1609
Attribute Type Name Process costs Process costs (pai) Process description
Type No. 355 1205 1603
Attribute Type Length 20/ABT_FLOAT 20/ABT_FLOAT 10000000/ABT_MULT ILINE
Data Type Floating point number Floating point number N-liner
Process ID Process instantiations Process key Process management Process manager Process manager Process performance Process priority Process successor immediately Process type Process type Process volume Processes to be processed Processing code Processing time Processing time Processing time Processing time Processing time
928 1120 1084 674 555 657 354 656 514 1261 545 351 1299 7 1112 186 365 537 846
12/ABT_INTEGER 5/ABT_INTEGER 6/ABT_SINGLELINE 2/ABT_BOOL 20/ABT_VALUE 80/ABT_MULTILINE 20/ABT_FLOAT 8/ABT_INTEGER 2/ABT_BOOL 10/ABT_VALUE 20/ABT_VALUE 20/ABT_FLOAT 8/ABT_RANGEINTEGE R 30/ABT_SINGLELINE 50/ABT_LONGTEXT 0/ABT_COMBINED 20/ABT_COMBINED 0/ABT_VALUE 20/ABT_MULTILINE
Integer Integer One-liner Boolean Value N-liner Floating point number Integer Boolean Value Value Floating point number Integer domain One-liner Longtext Combined Combined Value N-liner
ARIS Methods
11-1610
Attribute Type Name Processing time sum Processing type Product quantity Production capacity Production quantity Products/Services Program code Project description Project description Project management attributes Project manager Project name Project name Project type Promet(r)BPR Properties Protocol Protocol layer Provision time Pseudostate kind Purpose
Type No. 1116 4 964 304 305 675 1051 1222 464 390
Attribute Type Length 30/ABT_TIMESPAN 0/ABT_RANGEINTEGE R 10/ABT_INTEGER 0/ABT_VALUE 100/ABT_SINGLELINE 2/ABT_BOOL 15/ABT_MULTILINE 1032/ABT_MULTILINE 2000/ABT_MULTILINE 0/ABT_ITEMTYPE
Data Type Duration Integer domain Integer Value One-liner Boolean N-liner N-liner N-liner Item type
463 1221 461 465 574 1412 1524 241 640 1675 620
49/ABT_MULTILINE 256/ABT_MULTILINE 255/ABT_MULTILINE 49/ABT_MULTILINE 0/ABT_FLOAT 0/ABT_MULTILINE 32000/ABT_SINGLELI NE 512/ABT_VALUE 20/ABT_TIMESTAMP 50/ABT_VALUE 10000000/ABT_MULT ILINE
N-liner N-liner N-liner N-liner Floating point number N-liner One-liner Value Point in time Value N-liner
ARIS Methods
11-1611
Attribute Type Name Qualification Qualifier Qualitative evaluation Quality of specialist support Quantitative evaluation Quantity Quantity structure Quarters/Year Quick help Quota RBE usage factor Read Read privilege Realized from Realized until Recipient can be changed on exit Recipient can be changed on forwarding Record type Recurrence
Type No. 1525 142 1624 113 1623 1203 88 774 882 827 1662 908 873 127 128 687 695
Attribute Type Length 32000/ABT_SINGLELI NE 20/ABT_SINGLELINE 0/ABT_MULTILINE 512/ABT_VALUE 0/ABT_MULTILINE 10/ABT_FLOAT 0/ABT_VALUE 1/ABT_INTEGER 50/ABT_SINGLELINE 6/ABT_FLOAT 30/ABT_FLOAT 2/ABT_BOOL 2/ABT_BOOL 12/ABT_DATE 12/ABT_DATE 2/ABT_BOOL 2/ABT_BOOL
Data Type One-liner One-liner N-liner Value N-liner Floating point number Value Integer One-liner Floating point number Floating point number Boolean Boolean Date Date Boolean Boolean
340 1685
2/ABT_SINGLELINE 10000000/ABT_MULT ILINE
One-liner N-liner
ARIS Methods
11-1612
Attribute Type Name Recurrence language Recursion depth Redesign priority Redesign urgency Redocumentation Scout Reduced amount of damages Reduced amount of damages Reduced average amount of damages Reduced maximum amount of damages Reduced minimum amount of damages Reduced occurrence frequency Reduced occurrence frequency Reduced occurrence frequency of the average amount of damages Reduced occurrence frequency of the maximum amount of damages
Type No. 1686 871 559 556 1664 1567 1640 1561
Attribute Type Length 500/ABT_SINGLELINE 4/ABT_INTEGER 4/ABT_INTEGER 0/ABT_VALUE 0/ABT_SINGLELINE 0/ABT_TIMESTAMP 50/ABT_VALUE 20/ABT_COMBINED
Data Type One-liner Integer Integer Value One-liner Point in time Value Combined
1562 1560 1566
20/ABT_COMBINED 20/ABT_COMBINED 0/ABT_TIMESTAMP
Combined Combined Point in time
1641 1558
50/ABT_VALUE 20/ABT_FLOAT
Value Floating point number
1559
20/ABT_FLOAT
ARIS Methods
11-1613
Attribute Type Name Reduced occurrence frequency of the minimum amount of damages Reduced relative probabilities Reducing the amount of damages in risks Reducing the occurrence frequency of risks Reference code Reference code can be changed Reference state Regulation for variable date calculation Reinterpreted Relationship category Relative cycle start Relative degree of activation Relative degree of fulfillment Relative degree of processing
Type No. 1557
Attribute Type Length 20/ABT_FLOAT
Data Type Floating point number
1632 1569 1570
0/ABT_TIMESPAN 20/ABT_COMBINED 20/ABT_FLOAT
Duration Combined Floating point number
649 686 1677 1260
80/ABT_MULTILINE 2/ABT_BOOL 1000/ABT_SINGLELIN E 1024/ABT_MULTILINE
N-liner Boolean One-liner N-liner
44 491 1144 1124 1109 1118
2/ABT_BOOL 2/ABT_VALUE 30/ABT_TIMESPAN 10/ABT_FLOAT 10/ABT_FLOAT 10/ABT_FLOAT
Boolean Value Duration Floating point number Floating point number Floating point number
ARIS Methods
11-1614
Attribute Type Name Relative frequency Relative interval start Relative probabilities Relative shift start Relative time limits Release Release Release Release (module type) Released by Released on Relevance to data protection act Remark
Type No. 1280 1139 1633 1157 721 1656 268 92 231
Attribute Type Length 20/ABT_RANGEFLOAT 30/ABT_TIMESPAN 0/ABT_TIMESPAN 30/ABT_TIMESPAN 0/ABT_TIMESPAN 10000/ABT_MULTILIN E 16/ABT_SINGLELINE 16/ABT_SINGLELINE 40/ABT_SINGLELINE
Data Type Floating point number domain Duration Duration Duration Duration N-liner One-liner One-liner One-liner
611 610 107 1429
100/ABT_MULTILINE 20/ABT_DATE 2/ABT_BOOL 10000000/ABT_MULT ILINE
N-liner Date Boolean N-liner
Remark/Example Replaces version Report element Reported on Required capacity Required capacity
8 386 747 1428 1307 489
10000000/ABT_MULT ILINE 20/ABT_SINGLELINE 2/ABT_BOOL 20/ABT_DATE 8/ABT_RANGEINTEGE R 20/ABT_FLOAT
N-liner One-liner Boolean Date Integer domain Floating point number
ARIS Methods
11-1615
Attribute Type Name Requirement ResCode Resource allocation Resources involved Responsibility Responsibility code Responsibility code 1 Responsibility code 2 Responsibility code 3 Responsibility code 4 Responsibility code 5 Responsibility code 6 Responsible Restrictive period Resubmission date Resubmission reason Result
Type No. 1230 483 1298 550 622 1100 1060 1061 1062 1063 1064 1065 1426 513 854 855 1604
Attribute Type Length 20/ABT_SINGLELINE 255/ABT_MULTILINE 20/ABT_VALUE 20/ABT_VALUE 200/ABT_MULTILINE 3/ABT_MULTILINE 3/ABT_SINGLELINE 3/ABT_SINGLELINE 3/ABT_SINGLELINE 3/ABT_SINGLELINE 3/ABT_SINGLELINE 3/ABT_SINGLELINE 20/ABT_SINGLELINE 40/ABT_MULTILINE 22/ABT_TIMESTAMP 2024/ABT_MULTILINE 10000000/ABT_MULT ILINE
Data Type One-liner N-liner Value Value N-liner N-liner One-liner One-liner One-liner One-liner One-liner One-liner One-liner N-liner Point in time N-liner N-liner
Return type Returning connection Revenues Right margin RightMargin Risk management
1465 953 956 778 1441 1568
60/ABT_MULTILINE 2/ABT_BOOL 0/ABT_MULTILINE 2/ABT_BOOL 10/ABT_INTEGER 0/ABT_TIMESTAMP
N-liner Boolean N-liner Boolean Integer Point in time
ARIS Methods
11-1616
Attribute Type Name Risk management Risk manager: E-mail address Risk manager: Name Role Role (Baan) Role binding Role data type Rounding to decimal places RowStatus Rule attribute Rules Safety class Safety class of specimens Sales product SAP Attributes SAP Degree of coverage SAP development class SAP Dominant SAP filter ID SAP function type
Type No. 1576 1575 1574 731 1079 1245 1163 806 1505 98 1605 387 276 1669 1226 1231
Attribute Type Length 0/ABT_SINGLELINE 512/ABT_SINGLELINE 81/ABT_MULTILINE 20/ABT_VALUE 6/ABT_SINGLELINE 2/ABT_BOOL 15/ABT_VALUE 2/ABT_INTEGER 2/ABT_INTEGER 512/ABT_VALUE 10000000/ABT_MULT ILINE 512/ABT_VALUE 100/ABT_SINGLELINE 2/ABT_BOOL 0/ABT_MULTILINE 5/ABT_RANGEFLOAT
Data Type One-liner One-liner N-liner Value One-liner Boolean Value Integer Integer Value N-liner Value One-liner Boolean N-liner Floating point number domain
743 1459 742 673
5/ABT_MULTILINE 40/ABT_MULTILINE 21/ABT_MULTILINE 20/ABT_VALUE
N-liner N-liner N-liner Value
ARIS Methods
11-1617
Attribute Type Name SAP GUID Groups SAP ID SAP ID original model SAP model type SAP Server SAP variant type SAP-ARIS Online Guide Scaling in % Scheduled date of occurrence Scheduled from Scheduled until Screen required? Script Script language Search attribute Search privilege for all previous WF users Search privilege for creators Search privilege for OU of the creator
Type No. 1240 1018 755 852 1585 853 1460 783 399 125 126 904 1687 1688 900 1272 1270 1271
Attribute Type Length 40/ABT_MULTILINE 40/ABT_SINGLELINE 10/ABT_MULTILINE 512/ABT_VALUE 80/ABT_SINGLELINE 512/ABT_VALUE 2/ABT_BOOL 4/ABT_INTEGER 20/ABT_DATE 12/ABT_DATE 12/ABT_DATE 2/ABT_BOOL 10000000/ABT_MULT ILINE 500/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
Data Type N-liner One-liner N-liner Value One-liner Value Boolean Integer Date Date Date Boolean N-liner One-liner Boolean Boolean Boolean Boolean
ARIS Methods
11-1618
Attribute Type Name Search privilege for OU of the current user Search privilege for Pos1 of all superior OU's of the current user Search privilege for Pos1 of the OU of the current user Secondary key Secondary quantity Security classification Selected Selected Semantics Sequence Service name Serviceable life Services Session mode Set by rule Shift duration Short description
Type No. 1267
Attribute Type Length 2/ABT_BOOL
Data Type Boolean
1269
2/ABT_BOOL
Boolean
1268
2/ABT_BOOL
Boolean
270 252 1223 101 205 1647 1500 507 318 1606 1391 1087 1158 593
2/ABT_BOOL 100/ABT_MULTILINE 256/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 10000000/ABT_MULT ILINE 100/ABT_INTEGER 20/ABT_MULTILINE 100/ABT_COMBINED 10000000/ABT_MULT ILINE 30/ABT_VALUE 6/ABT_MULTILINE 30/ABT_TIMESPAN 80/ABT_MULTILINE
Boolean N-liner N-liner Boolean Boolean N-liner Integer N-liner Combined N-liner Value N-liner Duration N-liner
ARIS Methods
11-1619
Attribute Type Name Short text Shortcut Show user management Significance Significance Simulation Since/on Size Size Size in KBytes Skipping allowed SKO data model Sorting sequence Source Source Source systems Sources used Space Specification Specification SQL data type
Type No. 799 786 1433
Attribute Type Length 20/ABT_MULTILINE 20/ABT_SINGLELINE 2/ABT_BOOL
Data Type N-liner One-liner Boolean
1181 540 575 382 1527 828 248 1250 936 215 1512 38 934 2 1509 1682 278 1971
3/ABT_RANGEINTEGE R 20/ABT_VALUE 0/ABT_FLOAT 20/ABT_DATE 32000/ABT_SINGLELI NE 512/ABT_VALUE 40/ABT_INTEGER 2/ABT_BOOL 400/ABT_MULTILINE 512/ABT_VALUE 0/ABT_BOOL 100/ABT_MULTILINE 0/ABT_BOOL 0/ABT_MULTILINE 600/ABT_SINGLELINE 1000/ABT_SINGLELIN E 200/ABT_MULTILINE 32/ABT_SINGLELINE
Integer domain Value Floating point number Date One-liner Value Integer Boolean N-liner Value Boolean N-liner Boolean N-liner One-liner One-liner N-liner One-liner
ARIS Methods
11-1620
Attribute Type Name SQL name Staff position Standard Standard annual working hours Standard COT Standard daily working hours Standard plan Standard prefix Standard weekly working hours Standardization capability Start Start after instance creation Start date Start date Start of complaint Start of compression Start of interruption Start processing immediately Start step Start time
Type No. 272 139 1093 452 899 328 935 1177 329
Attribute Type Length 32/ABT_SINGLELINE 2/ABT_BOOL 2/ABT_BOOL 20/ABT_FLOAT 2/ABT_BOOL 10/ABT_FLOAT 400/ABT_MULTILINE 20/ABT_SINGLELINE 10/ABT_FLOAT
Data Type One-liner Boolean Boolean Floating point number Boolean Floating point number N-liner One-liner Floating point number
551 1541 843 1153 369 886 661 888 702
20/ABT_VALUE 20/ABT_DATE 20/ABT_MULTILINE 30/ABT_TIMESTAMP 20/ABT_DATE 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 2/ABT_BOOL
Value Date N-liner Point in time Date Point in time Point in time Point in time Boolean
693 363
2/ABT_BOOL 20/ABT_TIMESTAMP
Boolean Point in time
ARIS Methods
11-1621
Attribute Type Name Start time after instance creation Startup capacity Static Static (Src) Static (Trg) Static condition key (Baan) Static wait time Static wait time sum Status Status Status Status Status Status (CMA) Status bar Stereotype Storage group Storage mode Storage type Storefront Strategic significance Strength of influence
Type No. 895 1130 1523 1518 1519 1094 1110 1113 381 499 511 627 665 1422 791 971 256 864 97 1401 549 1532
Attribute Type Length 20/ABT_TIMESPAN 10/ABT_INTEGER 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 6/ABT_MULTILINE 50/ABT_LONGTEXT 30/ABT_TIMESPAN 512/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 100/ABT_SINGLELINE 256/ABT_MULTILINE 100/ABT_MULTILINE 512/ABT_VALUE 512/ABT_VALUE 2/ABT_BOOL 20/ABT_VALUE 20/ABT_RANGEFLOAT
Data Type Duration Integer Boolean Boolean Boolean N-liner Longtext Duration Value Value Value Value Value Value One-liner N-liner N-liner Value Value Boolean Value Floating point number domain
ARIS Methods
11-1622
Attribute Type Name Structural change speed Subject Subject to management in batches Subpipeline Subsystem attributes Sum of interruption time while orienting Sum of interruption time while processing Summand Supported products Surcharge driver Synchronization time Synchronization type Synonyms System attributes System login System-external System-internal Tabindex Target Target
Type No. 1187 493 284 1404 2098 1302 1303 802 547 851 1107 1972 130 134 1104 259 258 1588 1513 1689
Attribute Type Length 3/ABT_RANGEINTEGE R 80/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 0/ABT_MULTILINE 8/ABT_TIMESPAN 8/ABT_TIMESPAN 12/ABT_FLOAT 10000000/ABT_MULT ILINE 2/ABT_BOOL 30/ABT_LONGTEXT 20/ABT_VALUE 512/ABT_MULTILINE 0/ABT_VALUE 8/ABT_MULTILINE 2/ABT_BOOL 2/ABT_BOOL 10/ABT_INTEGER 0/ABT_BOOL 10000000/ABT_MULT ILINE
Data Type Integer domain N-liner Boolean Boolean N-liner Duration Duration Floating point number N-liner Boolean Longtext Value N-liner Value N-liner Boolean Boolean Integer Boolean N-liner
ARIS Methods
11-1623
Attribute Type Name Target data Target duration Target language Target quantity Target scope Target time period Target value Target work Task duration Technical operating supply number Telephone number Template Template Template Template Temporary Tenth power Terms/Abbreviations Text Text 1 Text 2 Text 3
Type No. 391 420 1690 425 1649 1371 1379 422 433 317 245 1389 1413 1454 733 40 803 744 54 441 442 443
Attribute Type Length 0/ABT_ITEMTYPE 20/ABT_INTEGER 500/ABT_SINGLELINE 20/ABT_INTEGER 50/ABT_VALUE 20/ABT_SINGLELINE 20/ABT_FLOAT 20/ABT_INTEGER 20/ABT_COMBINED 100/ABT_SINGLELINE 512/ABT_MULTILINE 20/ABT_FOREIGN_ID 0/ABT_MULTILINE 10/ABT_RANGEINTEG ER 512/ABT_FILE 2/ABT_BOOL 3/ABT_INTEGER 500/ABT_MULTILINE 10000000/ABT_MULT ILINE 255/ABT_MULTILINE 255/ABT_MULTILINE 255/ABT_MULTILINE
Data Type Item type Integer One-liner Integer Value One-liner Floating point number Integer Combined One-liner N-liner External identifier N-liner Integer domain Link/File Boolean Integer N-liner N-liner N-liner N-liner N-liner
ARIS Methods
11-1624
Attribute Type Name Throughput time Throughput time Throughput/avg. access Time Time Time category Time entry Time expression Time expression language Time interval Time keys Time last used Time limit calculation Time limit with fixed date calc. Time limits Time of folder event Time of generation Time of generation (SAP) Timer event Times
Type No. 1464 187 131
Attribute Type Length 0/ABT_COMBINED 0/ABT_COMBINED 12/ABT_INTEGER
Data Type Combined Combined Integer
1531 524 760 759 1700 1701
32/ABT_SINGLELINE 20/ABT_COMBINED 2/ABT_VALUE 9/ABT_FLOAT 10000000/ABT_MULT ILINE 500/ABT_SINGLELINE
One-liner Combined Value Floating point number N-liner One-liner
579 758 636 1254 1257
20/ABT_COMBINED 2/ABT_BOOL 20/ABT_TIMESTAMP 256/ABT_MULTILINE 4/ABT_INTEGER
Combined Boolean Point in time N-liner Integer
709 637 1008 1234 1056 36
0/ABT_MULTILINE 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 20/ABT_TIMESTAMP 2/ABT_BOOL 0/ABT_INTEGER
N-liner Point in time Point in time Point in time Boolean Integer
ARIS Methods
11-1625
Attribute Type Name Times Timestamp Title Title Title Title 1 Title 2 Title 3 Title 4 Title/Name To be completed by Tolerance Tolerance Tolerance administration Tolerance control Tolerance decision Tolerance default processing Tolerance executive management Tolerance individual processing Tolerance range Tolerance sales
Type No. 680 1016 1244 594 617 942 943 944 945 794 371 809 810 813
Attribute Type Length 0/ABT_INTEGER 20/ABT_TIMESTAMP 64/ABT_MULTILINE 100/ABT_SINGLELINE 200/ABT_MULTILINE 100/ABT_MULTILINE 100/ABT_MULTILINE 100/ABT_MULTILINE 100/ABT_MULTILINE 50/ABT_SINGLELINE 20/ABT_DATE 0/ABT_VALUE 3/ABT_INTEGER 3/ABT_INTEGER
Data Type Integer Point in time N-liner One-liner N-liner N-liner N-liner N-liner N-liner One-liner Date Value Integer Integer
812 814 815 811
3/ABT_INTEGER 3/ABT_INTEGER 3/ABT_INTEGER 3/ABT_INTEGER
Integer Integer Integer Integer
817 1375 816
3/ABT_INTEGER 20/ABT_FLOAT 3/ABT_INTEGER
Integer Floating point number Integer
ARIS Methods
11-1626
Attribute Type Name Top margin TopCenter TopLeft TopMargin TopRight Total costs Total time Total time Total time Transaction Transaction Transaction code Transaction handling Transient Transmission medium Transmission speed Transmission time Transmission time Transmission time Transmission type
Type No. 779 1435 1434 1442 1436 165 645 667 845 1397 1421 89 1400 951 236 234 1202 196 535 105
Attribute Type Length 2/ABT_BOOL 1000/ABT_SINGLELIN E 1000/ABT_SINGLELIN E 10/ABT_INTEGER 1000/ABT_SINGLELIN E 0/ABT_MULTILINE 0/ABT_COMBINED 20/ABT_COMBINED 20/ABT_MULTILINE 30/ABT_VALUE 20/ABT_VALUE 10000000/ABT_MULT ILINE 30/ABT_VALUE 2/ABT_BOOL 100/ABT_SINGLELINE 50/ABT_SINGLELINE 20/ABT_LONGTEXT 0/ABT_COMBINED 20/ABT_COMBINED 0/ABT_MULTILINE
Data Type Boolean One-liner One-liner Integer One-liner N-liner Combined Combined N-liner Value Value N-liner Value Boolean One-liner One-liner Longtext Combined Combined N-liner
ARIS Methods
11-1627
Attribute Type Name Transmission type, batch Transmission type, manually Transmission type, online Transport instruction/rule Transport system number Trigger
Type No. 95 96
94 288 320 1607
2/ABT_BOOL 100/ABT_SINGLELINE 100/ABT_SINGLELINE 10000000/ABT_MULT ILINE
Boolean One-liner One-liner N-liner
Trigger Trigger function Trigger to be released Trigger type Type Type Type Type Type Type Type Type 1 Type 2
262 1255 1256 1279 1174 1366 1416 1508 389 43 972 819 820
2/ABT_BOOL 2/ABT_BOOL 1024/ABT_MULTILINE 50/ABT_VALUE 10/ABT_VALUE 10/ABT_VALUE 10000000/ABT_MULT ILINE 512/ABT_VALUE 50/ABT_ITEMTYPE 50/ABT_SINGLELINE 256/ABT_MULTILINE 2/ABT_SINGLELINE 2/ABT_SINGLELINE
Boolean Boolean N-liner Value Value Value N-liner Value Item type One-liner N-liner One-liner One-liner
ARIS Methods
11-1628
Attribute Type Name Type 3 Type 4 Type 5 Type 6 Type 7 Type ID Type of aggregation Type of organizational unit Type of organizational unit Type of origin Type of origin UML Action state UML Action type UML Actor UML Attribute UML Class type UML Display options UML Event UML Event type UML Function type UML Link UML Node
Type No. 821 822 823 824 825 866 372 1067 137 264 99 1696 1683 1668 1667 1597 1706 1702 1680 1614 1539 1707
Attribute Type Length 2/ABT_SINGLELINE 2/ABT_SINGLELINE 2/ABT_SINGLELINE 2/ABT_SINGLELINE 2/ABT_SINGLELINE 5/ABT_INTEGER 50/ABT_SINGLELINE 512/ABT_VALUE 0/ABT_BOOL 512/ABT_VALUE 512/ABT_VALUE 0/ABT_BOOL 50/ABT_VALUE 0/ABT_MULTILINE 0/ABT_MULTILINE 50/ABT_VALUE 10000000/ABT_MULT ILINE 0/ABT_SINGLELINE 50/ABT_VALUE 50/ABT_VALUE 1/ABT_INTEGER 0/ABT_MULTILINE
Data Type One-liner One-liner One-liner One-liner One-liner Integer One-liner Value Boolean Value Value Boolean Value N-liner N-liner Value N-liner One-liner Value Value Integer N-liner
ARIS Methods
11-1629
Attribute Type Name UML Node instance UML Operation UML Service type UML State UML Use case Unit Unit for date calculation Unit of capacity Unit of denominator Unit of numerator UpdateFlag Updating frequency Upper limit Usage factor Usage factor specification Usage time sum Usage type User attribute Application system type User attribute Boolean 1 User attribute Boolean 10
Type No. 1708 1199 1681 1200 1504 1380 1258 292 805 804 1281 1180 1360 454 1287 1305 1262 2096
Attribute Type Length 0/ABT_MULTILINE 0/ABT_BOOL 50/ABT_VALUE 0/ABT_BOOL 0/ABT_BOOL 15/ABT_SINGLELINE 20/ABT_VALUE 100/ABT_SINGLELINE 4/ABT_INTEGER 4/ABT_INTEGER 2/ABT_BOOL 15/ABT_VALUE 20/ABT_FLOAT 30/ABT_FLOAT 40/ABT_VALUE 20/ABT_TIMESPAN 10/ABT_VALUE 10000000/ABT_MULT ILINE
Data Type N-liner Boolean Value Boolean Boolean One-liner Value One-liner Integer Integer Boolean Value Floating point number Floating point number Value Duration Value N-liner
987 1342
Boolean Boolean
ARIS Methods
11-1630
Attribute Type Name User attribute Boolean 11 User attribute Boolean 12 User attribute Boolean 13 User attribute Boolean 14 User attribute Boolean 15 User attribute Boolean 16 User attribute Boolean 17 User attribute Boolean 18 User attribute Boolean 19 User attribute Boolean 2 User attribute Boolean 20 User attribute Boolean 21 User attribute Boolean 22 User attribute Boolean 23
Type No. 1343 1344
1772 1773 1774 1775
2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
Boolean Boolean Boolean Boolean
1776 1777 1778
2/ABT_BOOL 2/ABT_BOOL 2/ABT_BOOL
Boolean Boolean Boolean
988 1779 1780
1781 1782
Boolean Boolean
ARIS Methods
11-1631
Type No. 1783 1784
1785 1786 1787 1788
1335 1789 1790
1791 1792 1793
1794 1795
Boolean Boolean
ARIS Methods
11-1632
Type No. 1796 1797
1798 1336 1799 1800
1801 1802 1803
1804 1805 1806
1807 1808
Boolean Boolean
ARIS Methods
11-1633
Attribute Type Name User attribute Boolean 5 User attribute Boolean 50 User attribute Boolean 6 User attribute Boolean 7 User attribute Boolean 8 User attribute Boolean 9 User attribute Date 1
Type No. 1337 1809
1338 1339 1340 1341
993
256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_DATE 256/ABT_TIMESPAN
Date Date Date Date Date Date Date Date Date Date Duration
User attribute Date 10 1939 User attribute Date 2 User attribute Date 3 User attribute Date 4 User attribute Date 5 User attribute Date 6 User attribute Date 7 User attribute Date 8 User attribute Date 9 User attribute Duration 1 User attribute Duration 10 1966 1931 1932 1933 1934 1935 1936 1937 1938 996
256/ABT_TIMESPAN
Duration
ARIS Methods
11-1634
Attribute Type Name User attribute Duration 2 User attribute Duration 3 User attribute Duration 4 User attribute Duration 5 User attribute Duration 6 User attribute Duration 7 User attribute Duration 8 User attribute Duration 9 User attribute Float 1 User attribute Float 10 User attribute Float 11 User attribute Float 12 User attribute Float 13 User attribute Float 14
Type No. 1958 1959
Attribute Type Length 256/ABT_TIMESPAN 256/ABT_TIMESPAN
Data Type Duration Duration
1960 1961 1962 1963
256/ABT_TIMESPAN 256/ABT_TIMESPAN 256/ABT_TIMESPAN 256/ABT_TIMESPAN
Duration Duration Duration Duration
1964 1965 991 1550 1891
256/ABT_TIMESPAN 256/ABT_TIMESPAN 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Duration Duration Floating point number Floating point number Floating point number
1892 1893 1894
5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number Floating point number
ARIS Methods
11-1635
Attribute Type Name User attribute Float 15 User attribute Float 16 User attribute Float 17 User attribute Float 18 User attribute Float 19 User attribute Float 2 User attribute Float 20 User attribute Float 21 User attribute Float 22 User attribute Float 23 User attribute Float 24 User attribute Float 25 User attribute Float 26 User attribute Float 27
Type No. 1895 1896
1897 1898 1899 992 1900 1901
5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number
1902 1903 1904
1905 1906 1907
ARIS Methods
11-1636
Attribute Type Name User attribute Float 28 User attribute Float 29 User attribute Float 3 User attribute Float 30 User attribute Float 31 User attribute Float 32 User attribute Float 33 User attribute Float 34 User attribute Float 35 User attribute Float 36 User attribute Float 37 User attribute Float 38 User attribute Float 39 User attribute Float 4
Type No. 1908 1909
1543 1910
5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number
1911 1912 1913 1914
5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number Floating point number Floating point number
1915 1916 1917
1918 1919 1544
ARIS Methods
11-1637
Attribute Type Name User attribute Float 40 User attribute Float 41 User attribute Float 42 User attribute Float 43 User attribute Float 44 User attribute Float 45 User attribute Float 46 User attribute Float 47 User attribute Float 48 User attribute Float 49 User attribute Float 5 User attribute Float 50 User attribute Float 6 User attribute Float 7 User attribute Float 8 User attribute Float 9
Type No. 1920 1921
1922 1923 1924 1925
5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number Floating point number Floating point number
1926 1927 1928
1929 1545 1930 1546 1547 1548 1549
5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT 5/ABT_FLOAT
Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number Floating point number
ARIS Methods
11-1638
Attribute Type Name User attribute Functional cluster User attribute Int 1 User attribute Int 10 User attribute Int 11 User attribute Int 12 User attribute Int 13 User attribute Int 14 User attribute Int 15 User attribute Int 16 User attribute Int 17 User attribute Int 18 User attribute Int 19 User attribute Int 2 User attribute Int 20 User attribute Int 21 User attribute Int 22 User attribute Int 23 User attribute Int 24 User attribute Int 25 User attribute Int 26 User attribute Int 27 User attribute Int 28 User attribute Int 29
Type No. 2095 989 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 990 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831
Attribute Type Length 10000000/ABT_MULT ILINE 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER
Data Type N-liner Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer
ARIS Methods
11-1639
Attribute Type Name User attribute Int 3 User attribute Int 30 User attribute Int 31 User attribute Int 32 User attribute Int 33 User attribute Int 34 User attribute Int 35 User attribute Int 36 User attribute Int 37 User attribute Int 38 User attribute Int 39 User attribute Int 4 User attribute Int 40 User attribute Int 41 User attribute Int 42 User attribute Int 43 User attribute Int 44 User attribute Int 45 User attribute Int 46 User attribute Int 47 User attribute Int 48 User attribute Int 49 User attribute Int 5 User attribute Int 50
Type No. 1355 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1356 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1357 1852
Attribute Type Length 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER
Data Type Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer
ARIS Methods
11-1640
Attribute Type Name User attribute Int 6 User attribute Int 7 User attribute Int 8 User attribute Int 9 User attribute Link User attribute Point in time 1 User attribute Point in time 10 User attribute Point in time 2 User attribute Point in time 3 User attribute Point in time 4 User attribute Point in time 5 User attribute Point in time 6 User attribute Point in time 7 User attribute Point in time 8 User attribute Point in time 9 User attribute Text 1
Type No. 1358 1359 1810 1811 997 995
Attribute Type Length 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 5/ABT_INTEGER 256/ABT_FILE 256/ABT_TIMESTAMP
Data Type Integer Integer Integer Integer Link/File Point in time
1957 1949 1950 1951
256/ABT_TIMESTAMP 256/ABT_TIMESTAMP 256/ABT_TIMESTAMP 256/ABT_TIMESTAMP
Point in time Point in time Point in time Point in time
1952 1953 1954
256/ABT_TIMESTAMP 256/ABT_TIMESTAMP 256/ABT_TIMESTAMP
Point in time Point in time Point in time
1955 1956 985
256/ABT_TIMESTAMP 256/ABT_TIMESTAMP 10000000/ABT_MULT ILINE
Point in time Point in time N-liner
ARIS Methods
11-1641
Attribute Type Name User attribute Text 10 User attribute Text 100 User attribute Text 101 User attribute Text 102 User attribute Text 103 User attribute Text 104 User attribute Text 105 User attribute Text 106 User attribute Text 107 User attribute Text 108 User attribute Text 109 User attribute Text 11
Type No. 1214 1771
Attribute Type Length 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
1973 1974 1975 1976
10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
N-liner N-liner N-liner N-liner
1977 1978 1979
10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
1980 1981 1215
User attribute Text 110 User attribute Text 111
1982 1983
10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
N-liner N-liner
ARIS Methods
11-1642
Attribute Type Name User attribute Text 112 User attribute Text 113 User attribute Text 114 User attribute Text 115 User attribute Text 116 User attribute Text 117 User attribute Text 118 User attribute Text 119 User attribute Text 12
Type No. 1984 1985
1986 1987 1988 1989
1990 1991 1216
User attribute Text 120 User attribute Text 121 User attribute Text 122 User attribute Text 123 User attribute Text 124
1992 1993 1994
1995 1996
N-liner N-liner
ARIS Methods
11-1643
Attribute Type Name User attribute Text 125 User attribute Text 126 User attribute Text 127 User attribute Text 128 User attribute Text 129 User attribute Text 13
Type No. 1997 1998
1999 2000 2001 1310
User attribute Text 130 User attribute Text 131 User attribute Text 132 User attribute Text 133 User attribute Text 134 User attribute Text 135 User attribute Text 136 User attribute Text 137
2002 2003 2004
2005 2006 2007
2008 2009
N-liner N-liner
ARIS Methods
11-1644
Attribute Type Name User attribute Text 138 User attribute Text 139 User attribute Text 14 User attribute Text 140 User attribute Text 141 User attribute Text 142 User attribute Text 143 User attribute Text 144 User attribute Text 145 User attribute Text 146 User attribute Text 147 User attribute Text 148 User attribute Text 149 User attribute Text 15
Type No. 2010 2011
1311 2012 2013 2014
2015 2016 2017
2018 2019 2020
2021 1312
N-liner N-liner
ARIS Methods
11-1645
Type No. 2022 2023
2024 2025 2026 2027
2028 2029 2030
2031 1313 2032
2033 2034
N-liner N-liner
ARIS Methods
11-1646
Type No. 2035 2036
2037 2038 2039 2040
2041 1314 2042
2043 2044 2045
2046 2047
N-liner N-liner
ARIS Methods
11-1647
Type No. 2048 2049
2050 2051 1315 2052
2053 2054 2055
2056 2057 2058
2059 2060
N-liner N-liner
ARIS Methods
11-1648
Attribute Type Name User attribute Text 189 User attribute Text 19
Type No. 2061 1316
User attribute Text 190 User attribute Text 191 User attribute Text 192 User attribute Text 193 User attribute Text 194 User attribute Text 195 User attribute Text 196 User attribute Text 197 User attribute Text 198 User attribute Text 199 User attribute Text 2 User attribute Text 20
2062 2063 2064 2065
2066 2067 2068
2069 2070 2071
986 1317
N-liner N-liner
ARIS Methods
11-1649
Attribute Type Name User attribute Text 200 User attribute Text 201 User attribute Text 21 User attribute Text 22 User attribute Text 23 User attribute Text 24
Type No. 2072 2094
1318 1319 1320 1321
User attribute Text 25 User attribute Text 26 User attribute Text 27
1322 1323 1324
1325 1326 1207
1327 1328
N-liner N-liner
ARIS Methods
11-1650
Type No. 1329 1330
User attribute Text 34 User attribute Text 35 User attribute Text 36 User attribute Text 37
1331 1332 1333 1334
1709 1710 1208
1711 1712 1713
1714 1715
N-liner N-liner
ARIS Methods
11-1651
Type No. 1716 1717
1718 1719 1720 1209
1721 1722 1723
1724 1725 1726
1727 1728
N-liner N-liner
ARIS Methods
11-1652
Type No. 1729 1730
1210 1731 1732 1733
1734 1735 1736
1737 1738 1739
1740 1211
N-liner N-liner
ARIS Methods
11-1653
Type No. 1741 1742
1743 1744 1745 1746
1747 1748 1749
1750 1212 1751
1752 1753
N-liner N-liner
ARIS Methods
11-1654
Type No. 1754 1755
1756 1757 1758 1759
1760 1213 1761
1762 1763 1764
1765 1766
N-liner N-liner
ARIS Methods
11-1655
Type No. 1767 1768
User attribute Text 98 User attribute Text 99 User attribute Time 1 User attribute Time 10 User attribute Time 2 User attribute Time 3 User attribute Time 4 User attribute Time 5 User attribute Time 6 User attribute Time 7 User attribute Time 8 User attribute Time 9 User attribute Values 1 User attribute Values 10 User attribute Values 11
1769 1770 994 1948 1940 1941 1942 1943 1944 1945 1946 1947 1217
10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 256/ABT_TIME 20/ABT_VALUE
N-liner N-liner Time Time Time Time Time Time Time Time Time Time Value
1352 1353
Value Value
ARIS Methods
11-1656
Attribute Type Name User attribute Values 12 User attribute Values 13 User attribute Values 14 User attribute Values 15 User attribute Values 16 User attribute Values 17 User attribute Values 18 User attribute Values 19 User attribute Values 2 User attribute Values 20 User attribute Values 21 User attribute Values 22 User attribute Values 23 User attribute Values 24
Type No. 1354 1853
1854 1855 1856 1857
20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE 20/ABT_VALUE
Value Value Value Value
1858 1859 1218
Value Value Value
1860 1861 1862
Value Value Value
1863 1864
Value Value
ARIS Methods
11-1657
Type No. 1865 1866
1867 1868 1869 1345
1870 1871 1872
Value Value Value
1873 1874 1875
Value Value Value
1876 1877
Value Value
ARIS Methods
11-1658
Type No. 1878 1879
1346 1880 1881 1882
1883 1884 1885
Value Value Value
1886 1887 1888
Value Value Value
1889 1347
Value Value
ARIS Methods
11-1659
Type No. 1890 2074
2075 2076 2077 2078
2079 2080 2081
Value Value Value
2082 1348 2083
Value Value Value
1349 1350
Value Value
ARIS Methods
11-1660
Attribute Type Name User attribute Values 9 User event User exit User management User prefix Utility Utility Utilization Utilization Valid from Valid from Valid from Valid until Valid until Valid until Validity Validity Value Value Value
Type No. 1351 1054 457 1002 1176 1041 1053 1284 132 1046 384 764 1047 385 765 1540 621 1136 1369 1691
Attribute Type Length 20/ABT_VALUE 2/ABT_BOOL 2/ABT_SINGLELINE 2/ABT_BOOL 20/ABT_SINGLELINE 10000000/ABT_MULT ILINE 10/ABT_SINGLELINE 4/ABT_FLOAT 40/ABT_SINGLELINE 256/ABT_DATE 20/ABT_DATE 10/ABT_DATE 256/ABT_DATE 20/ABT_DATE 10/ABT_DATE 0/ABT_INTEGER 1000/ABT_MULTILINE 80/ABT_MULTILINE 10000000/ABT_MULT ILINE 10000000/ABT_MULT ILINE
Data Type Value Boolean One-liner Boolean One-liner N-liner One-liner Floating point number One-liner Date Date Date Date Date Date Integer N-liner N-liner N-liner N-liner
Value
291
100/ABT_SINGLELINE
One-liner
ARIS Methods
11-1661
Attribute Type Name Value Value (CDU) Value (logical) Value (numeric) Value 1 Value 2 Value language Value to compare Variable plan operation costs Variations Various overhead costs Version Version Version (Baan) Version status Version tree Version/Release View Virtual inheritance Visibility Visibility (Src)
Type No. 298 567 1138 1137 265 266 1692 1399 439 1609 164
Attribute Type Length 100/ABT_SINGLELINE 20/ABT_FLOAT 2/ABT_BOOL 10/ABT_FLOAT 2000/ABT_MULTILINE 2000/ABT_MULTILINE 500/ABT_SINGLELINE 10000000/ABT_MULT ILINE 20/ABT_FLOAT 10000000/ABT_MULT ILINE 0/ABT_MULTILINE
Data Type One-liner Floating point number Boolean Floating point number N-liner N-liner One-liner N-liner Floating point number N-liner N-liner
1405 1473 1030 1032 1033 242 1596 1511 981 1514
255/ABT_MULTILINE 20/ABT_SINGLELINE 10/ABT_SINGLELINE 512/ABT_VALUE 200/ABT_MULTILINE 100/ABT_SINGLELINE 50/ABT_VALUE 2/ABT_BOOL 20/ABT_VALUE 20/ABT_VALUE
N-liner One-liner One-liner Value N-liner One-liner Value Boolean Value Value
ARIS Methods
11-1662
Attribute Type Name Visibility (Trg) Volume Wait time Wait time Wait time Wait time sum Warehouse equip. number Weeks/Year Weighting Weighting
Type No. 1515 201 184 366 538 590 319 772 1206 1385
Attribute Type Length 20/ABT_VALUE 0/ABT_INTEGER 0/ABT_COMBINED 20/ABT_COMBINED 0/ABT_VALUE 10/ABT_COMBINED 100/ABT_SINGLELINE 2/ABT_INTEGER 20/ABT_FLOAT 20/ABT_RANGEFLOAT
Data Type Value Integer Combined Combined Value Combined One-liner Integer Floating point number Floating point number domain
Weighting factor With complaint Wizard code Work instruction Workflow Workflow Workflow class Workflow domain WPDL-external attribute list X position xxxxxxxxxxxxxxxxxx
122 892 1058 1040 321 459 1263 1246 848 788 1149
4/ABT_INTEGER 2/ABT_BOOL 4/ABT_SINGLELINE 10000000/ABT_MULT ILINE 0/ABT_SINGLELINE 2/ABT_SINGLELINE 2/ABT_BOOL 256/ABT_MULTILINE 512/ABT_MULTILINE 4/ABT_INTEGER 30/ABT_TIMESPAN
Integer Boolean One-liner N-liner One-liner One-liner Boolean N-liner N-liner Integer Duration
ARIS Methods
11.14 Columns (LaneTypeNum)
11-1663
Attribute Type Name Y position Zone attributes
Type No. 789 2085
Attribute Type Length 4/ABT_INTEGER 0/ABT_BOOL
Data Type Integer Boolean

Name 'belongs to' row 'consists of' column Accepts Accepts Application system Archives Batch Business participants Can be user Carries out carries out Carries out Carries out/Supports Cause-and-effect Changes competence Contributes to Contributes to Column No. 57/LT_BELONGS_TO 56/LT_CONS_OF 52/LT_AGREES_1 77/LT_AGREES_2 6/LT_APPL_SYS 86/LT_ARCH 10/LT_BAT 61/LT_BUS_PART 97/LT_CAN_BE_USER 22/LT_EXEC_1 60/LT_EXEC_3 68/LT_EXEC_4 28/LT_EXEC_SUPP 65/LT_CAUSE_EFFECT 85/LT_CHNG 99/LT_COMPETENCE 45/LT_CONTR_TO_1 69/LT_CONTR_TO_2
ARIS Methods
11-1664
Name Creates Creates creatives cross Data Data Data & Information carrier Decides on Decides on Default Deletes Dialog Distributes Event Function Functions Functions and key performance indicators Functions, competencies and objectives Functions, organization and improvements Has consulting role in Has consulting role in Has knowledge of Has output of Improvement potential, tools and objectives Input
Column No. 87/LT_CRT_1 91/LT_CRT_2 100/LT_CREATIVES 98/LT_CROSS 108/LT_DATA_8 3/LT_DATA_1 66/LT_DATA_INFO_CARR 46/LT_DECID_ON_1 72/LT_DECID_ON_2 9999/LT_DEFAULT 88/LT_DEL 11/LT_DLG 89/LT_DISTR 1/LT_EVT 2/LT_FUNC 109/LT_FUNC_1 101/LT_FUNC_KPI 106/LT_FUNC_KNOWL_TRG 104/LT_FUNC_ORG_IMPROV 53/LT_HAS_CONSLT_ROLE_IN_1 76/LT_HAS_CONSLT_ROLE_IN_2 92/LT_IS_AVAILABLE 84/LT_HAS_OUT 103/LT_TOOL_IMPROV_TRG 24/LT_INP
ARIS Methods
11-1665
Name Is approved by Is assigned to Is checked by Is input for Is IT responsible for Is IT responsible for Is required for Is technically responsible for Is technically responsible for Is used by Layout Main process column Manually Material/Packaging material Medium Must be informed about Must be informed about Must be informed on cancellation Must inform about result of Must inform about result of Objective Objects On cancellation, must be informed about Organization and competencies
Column No. 80/LT_IS_GRANT_BY 93/LT_IS_ASSIG 81/LT_IS_CHCKD_BY 79/LT_IS_INP_FOR 47/LT_IS_DP_RESP_1 71/LT_IS_DP_RESP_2 83/LT_IS_NEEDED_BY 48/LT_IS_TECH_RESP_1 70/LT_IS_TECH_RES_2 82/LT_IS_USED_BY 107/LT_LAYOUT 54/LT_MAIN_PRCS 12/LT_MAN 14/LT_MAT_PACK 4/LT_MEDIUM 51/LT_MUST_BE_INFO_ABT_1 74/LT_MUST_BE_INFO_ABT_2 49/LT_MUST_BE_INFO_ON_CNC_1 50/LT_MUST_INFO_ABT_RES_1 73/LT_MUST_INFO_ABT_RES_2 58/LT_OBJCTV 25/LT_OBJS 75/LT_MUST_BE_INFO_ON_CNC_2 102/LT_ORG_KNOWL
ARIS Methods
11-1666
Name Organization, key performance indicators and tools Organizational elements Organizational unit OrgElements/Application system Other Other Output Perspective Process Product/Service Reads Relationships Relevant perspectives Scenario line Screen Screen/List Strategy Supports Technical resources User
Column No. 105/LT_ORG_KPI_TOOL
26/LT_ORGELEM 7/LT_ORG_UNIT 29/LT_ORGELEM_APPSYS 59/LT_OTHERS_1 94/LT_OTHERS_2 23/LT_OUT 63/LT_PERSPEC 67/LT_PRCS 27/LT_PERF 90/LT_READ 9998/LT_RELSHP 64/LT_REL_PERSPEC 55/LT_SCENARIO 96/LT_SCRN 8/LT_SCRN_LST 62/LT_STRATEGY_2 78/LT_SUPP 13/LT_TECH_RES 95/LT_USER
ARIS Methods
11.15 Enumeration Values (AttrValueType)
11-1667

In ARIS databases boolean values are represented by the enumeration values 4 (= 0) and 5 (= 1). Attribute Type Contents = = (String) != != (String) #FIXED #IMPLIED #REQUIRED * + 0 00 No customer segment 1 10 Private customers 11 Standard private customers 12 Individual private customers 13 PC3 14 PC4 261 262 0 0 0 0 260 0 0 259 0 0 5 258 0 0 0 0 194 577 195 578 603 602 601 360 358 74 4 257 Enum. Value Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1668
Attribute Type Contents 2... 20 Commercial customers and companies 21 Commercial customers 22 Companies 23 Freelancers 24 CY4 30 Institutional customers 31 IC1 32 IC2 33 IC3 34 IC4 40 AC0 41 AC1 42 AC2 43 AC3 44 AC4 := < <= > >=
Enum. Value 96 263
Conversion Factor to Basic Unit 0 0
Basic Type (see Enum. Value) 0 0
264 265 266 267 268 269 270 271 272 273 274 275 276 277 359 198 199 196 197
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1669
Attribute Type Contents Aborted Absolute Action sequence Action state Active Active Actual Add only Add-on 1 Add-on 2 Add-on 3 Additive Aggregation Align left Align right Allowed Also subordinate units Alternative AND AND/OR AND/XOR Application Application component
Enum. Value 230 346 668 676 611 70 375 641 285 286 287 472 409 318 317 444 291
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
473 18 23 24 121 243
0 0 0 0 0 0
0 0 0 0 0 0
ARIS Methods
11-1670
Attribute Type Contents As early as possible As late as possible Ascending ASCII Association Asynchronous division ATS Automated Automatic Available Average Baan session Background job processor Backoffice Backward Batch begin Being processed BGN Binary Binary Binding BLOB
Enum. Value 164 165 97 130 649 425
Conversion Factor to Basic Unit 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0
31 6 136 210 56 336 565
0 0 0 0 0 0 0
0 0 0 0 0 0 0
564 178 1 559 148 469 1265 131 218 617
0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1671
Attribute Type Contents BND Boolean BPTS object Building Bus Business process Business travel By reference By value c CAD Calendar days Calendar months Calendar weeks Call action Call event Call state Can no longer be achieved Can no longer be completed Can no longer be maintained Cannot be achieved Cannot be changed
Enum. Value 585 77 208 64 107 335 355 613 612 12 39 433 435 434 670 660 677 205 241
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
238 213 220
0 0 0
0 0 0
ARIS Methods
11-1672
Attribute Type Contents Card Cascade Catastrophic CDATA Centered Change event Changeable Char Char (n) Check box CHF Choice Class ClassUtility Client cn Combo box commit Company area Company holiday Company-external Company-external Company-internal Company-internal
Enum. Value 100 307 648 592 319 662 639 76 78 624 40 658 604 607 439 13 278 561 575 354 129 73 128 72
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1673
Attribute Type Contents Complete Completed Completed Complex Composition Computer concurrent Confidential Constant Container for liquid materials Container for solid materials Contingency process Continue at first activation Continuing education Control activity Control process Copy Cost accounting Cost category Cost category diagram
Enum. Value 149 240 333 543 408 101 574 153 390 146 147 615 1061 356
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0
337 616 246 284 372 366
0 0 0 0 0 0
0 0 0 0 0 0
ARIS Methods
11-1674
Attribute Type Contents Cost center Cost driver Cost driver diagram Cost driver hierarchy Create action CSMA/CD Customized function CZK D Daily Data Data type Date Date Day(s) Decimal (n,m) Decision table Deep history Default Delivery channel DEM Descending Destroy action Details
Enum. Value 371 370 367 453 669 117 59 1064 251 377 126 633 476 79 46 80 15 653 315 480 25 98 674 631
ARIS Methods
11-1675
Attribute Type Contents Determined Dialog DKK Do Do not compare Done Drop-down combo box Drop-list combo box Duration Dynamic DZD Elementary function Empiric data End End not after End not before End product Endif ENTITIES ENTITY Enumeration Enumeration type Equal distribution
Enum. Value 228 2 34 442 166 572 626 627 193 340 37 8 646 156 161 160 140 441 597 596 634 191 391
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1676
Attribute Type Contents Erlang distribution error ESP Ethernet EUR Execution-related Expert estimation Expired Exponential distribution Extended list box Extension External External (not IT) External client call on forwarding External client call on opening External function External program External server call on forwarding External server call on opening Falling
Enum. Value 395 570 33 111 331 544 645 334 394 622 349 54 69 449 451
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
61 338 450 452
0 0 0 0
0 0 0 0
386
ARIS Methods
11-1677
Attribute Type Contents False False FDDI Few FF File FIM Final state Finished Fiscal Fixed Float Floating point number Fork Forward FRF From confirmation of activity From process begin Frozen FS Fulfilled Full reference variant
Enum. Value 1059 204 114 388 187 206 330 666 216 312 348 81 189 656 177 29 436 437 640 186 226 301
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1678
Attribute Type Contents Function Function (ADW) Gamma distribution GBP General Good Graphic variant GRD Group based Guarded H Has confirmed Has error status Hex High Higher Highest HKD Holiday Hour(s) Hourly Hours HRK HUF
Enum. Value 369 9 541 38 545 55 300 455 362 322 255 181 235 82 170 169 167 589 351 45 376 432 466 467
ARIS Methods
11-1679
Attribute Type Contents ID IDR IDREF IDREFS If ILS Implementation In In development Inactive Initial Initialize Inout INR InstantiatedClass InstantiatedClassUtility Integer Integer Integration Integration component Interface Intermediate product
Enum. Value 593 584 594 595 440 458 327 636 332 71 652 245 638 457 606 609 190 83 410 411 632 141
ARIS Methods
11-1680
Attribute Type Contents Internal Internal client function Internal server function Inversely proportional Is active Is defined Is inactive Is not defined Is planned Item based ITL Join Junction Justify KPW Label and text box Label only Lagging indicator LAN Large icons Last change Leading indicator
Enum. Value 53 447 448 591
Conversion Factor to Basic Unit 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0
182 179 183 579 180 361 30 655 657 320 42 280 281 552 108 628 151 551
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1681
Attribute Type Contents List Log-normal distribution Low Low Lower Lowest LUF M MAD Maintained MAN Man-day(s) Man-hour(s) Man-month(s) Man-year(s) Management process Manager Mandatory Manually Maximum May MDEM Meeting
Enum. Value 630 393 171 222 172 174 35 253 461 237 110 50 49 51 52 225
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 24 1 720 8640 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 49 49 49 49 0
414 221 3 389 94 27 123
0 0 0 0 0 1000000 0
0 0 0 0 0 25 0
ARIS Methods
11-1682
Attribute Type Contents Meshed network MetaClass Minute(s) Modified standard system function Modify Month(s) Monthly Multiple list box Must Must end on Must start on MYR n Network Network component Never next NLG NMTOKEN NMTOKENS No no NOK
Enum. Value 116 610 44 60 244 47 379 621 95 163 162 460 14 125 102 382 567 41 598 599 310 569 470
ARIS Methods
11-1683
Attribute Type Contents Non-automated Non-automated Non-unique none None Normal Normal distribution Not allowed Not allowed simultaneously Not assigned Not binary Not determined Not fulfilled Not maintained Not set Not synchronized Not yet achieved Not yet completed NOTATION Number (n) Number (n,m) Number carried out attribute Object flow state
Enum. Value 137 7 104 558 75 341 392 445 446 571 1266 229 227 236 201 1063 202 239 600 84 91 454
667
ARIS Methods
11-1684
Attribute Type Contents Oct Office On a business trip On leave Operation Optional OR OR/AND OR/XOR Organization-related Organizational chart Other Other Other Other Other currency Out Outstanding Package pai pan ParameterizedClass ParameterizedClassUtility
Enum. Value 85 65 214 212 643 219 16 20 19 547 368 115 120 209 357 464 637 549 635 364 365 605 608
ARIS Methods
11-1685
Attribute Type Contents Partitioned Performance process Permanent Permanent session persistent Person-related Personal leave Personnel planning PHP Physical Plan Plant PLZ Point in time Poor Postponed Presentation Private Pro rata Probability Process Process Process (ADW) Process component
Enum. Value 135 223 302 303 554 548 353 283 586 127 373 63 465 192 57 573 122 326 157 475 293 478 10 413
ARIS Methods
11-1686
Attribute Type Contents Process group Process manager Process selection matrix for components Process selection matrix for organizational units Process starter Product Project Model Proportional Protected Provide PTE Public Public Purchased product Q QAR Quota Quota in driver relation Quota in EMC relation R$
Enum. Value 576 249 295
Conversion Factor to Basic Unit 0 0 0
Basic Type (see Enum. Value) 0 0 0
296
248 479 345 590 325 328 462 154 324 139 254 459 288 290 289 582
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1687
Attribute Type Contents Radio button Radio button Raw (n) Raw (n,m) Ready Real Recipient Record Reference model Rejected Relative Released Remaining quantity recyclable Remaining quantity reusable Remove only Replacement Require required Resize proportionately Restricted Retail outlet Return
Enum. Value 279 623 92 93 215 86 415 207 344 581 347 150 143 142 642 350 329 556 316 306 62 650
ARIS Methods
11-1688
Attribute Type Contents Return action Rich text box Ring network Rising RMB rollback RUB Sales product Same width savepoint Scenario Scenario component Scenario process Scenario selection matrix Second(s) Secret Segmented SEK Seldom Selection variant Send action Sequential Sequential process (ADW)
Enum. Value 671 619 106 384 587 562 468 138 314 560 242 412 294 297
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0 0 0 0
43 152 134 32 381 298 672 321 11
1 0 0 0 0 0 0 0 0
43 0 0 0 0 0 0 0 0
ARIS Methods
11-1689
Attribute Type Contents Server Set Set null SF SGD Shallow history Sharply falling Sharply rising Sick leave Signal event Simple Simple Single list box SIT Slotted ring protocol Small icons Smallint Sovereign SS Stable Staff Standard combo box Standard system function
Enum. Value 438 200 305 185 583 654 387 383 211 659 133 542 620 471 119 629 87 311 184 385 342 625 58
ARIS Methods
11-1690
Attribute Type Contents Standard text box Star network Start Start not after Start not before State Static Storefront Stub state Subdiagramm Subordinate units only Subpipeline Support process supported Suspended Synch state Synchronic division Synchronize all active paths Synchronized Synchronous Synonym 1 Synonym 2 Synonym 3
Enum. Value 618 105 155 159 158 663 339 563 665 343 292
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0 0 0
566 224 557 232 664 426 1060 1062 323 416 417 418
0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0
ARIS Methods
11-1691
Attribute Type Contents Synonym 4 Synonym 5 Synonym 6 Synonym 7 Synonym 8 Synonym 9 System-external System-internal Target Task-related TDEM Temporary Terminate action Text Text Text box only THB Time Time Time event Timestamp To be edited Token bus Token passing
Enum. Value 419 420 421 422 423 424 68 67 374 546 26 304 673 132 188 282 463 477 88 661 89 651 113 118
ARIS Methods
11-1692
Attribute Type Contents Token ring transient Transport Triangular distribution True True TWD Type based Unimportant Uninterpreted action Unique Unspecified Until Usage factor attribute USD Use case Vacation Value 1 Value 10 Value 100 Value 101 Value 102 Value 103
Enum. Value 112 553 124 396 1058 203 588 363 647 675 103 614 443 474 28 644 352 397 406 707 708 709 710
ARIS Methods
11-1693
Attribute Type Contents Value 104 Value 105 Value 106 Value 107 Value 108 Value 109 Value 11 Value 110 Value 111 Value 112 Value 113 Value 114 Value 115 Value 116 Value 117 Value 118 Value 119 Value 12 Value 120 Value 121 Value 122 Value 123 Value 124 Value 125
Enum. Value 711 712 713 714 715 716 481 717 718 719 720 721 722 723 724 725 726 482 727 728 729 730 731 732
ARIS Methods
11-1694
Enum. Value 733 734 735 736 483 737 738 739 740 741 742 743 744 745 746 484 747 748 749 750 751 752 753 754
ARIS Methods
11-1695
Enum. Value 755 756 485 757 758 759 760 761 762 763 764 765 766 486 767 768 769 770 771 772 773 774 775 776
ARIS Methods
11-1696
Enum. Value 487 777 778 779 780 781 782 783 784 785 786 488 787 788 789 790 791 792 793 794 795 796 489 797
ARIS Methods
11-1697
Enum. Value 798 799 800 801 802 803 804 805 806 398 490 807 808 809 810 811 812 813 814 815 816 491 817 818
ARIS Methods
11-1698
Enum. Value 819 820 821 822 823 824 825 826 492 827 828 829 830 831 832 833 834 835 836 493 837 838 839 840
ARIS Methods
11-1699
Enum. Value 841 842 843 844 845 846 494 847 848 849 850 851 852 853 854 855 856 495 857 858 859 860 861 862
ARIS Methods
11-1700
Enum. Value 863 864 865 866 496 867 868 869 870 871 872 873 874 875 876 497 877 878 879 880 881 882 883 884
ARIS Methods
11-1701
Enum. Value 885 886 498 887 888 889 890 891 892 893 894 895 896 499 897 898 899 900 901 902 903 904 905 906
ARIS Methods
11-1702
Enum. Value 399 500 907 908 909 910 911 912 913 914 915 916 501 917 918 919 920 921 922 923 924 925 926 502
ARIS Methods
11-1703
Enum. Value 927 928 929 930 931 932 933 934 935 936 503 937 938 939 940 941 942 943 944 945 946 504 947 948
ARIS Methods
11-1704
Enum. Value 949 950 951 952 953 954 955 956 505 957 958 959 960 961 962 963 964 965 966 506 967 968 969 970
ARIS Methods
11-1705
Enum. Value 971 972 973 974 975 976 507 977 978 979 980 981 982 983 984 985 986 508 987 988 989 990 991 992
ARIS Methods
11-1706
Enum. Value 993 994 995 996 509 997 998 999 1000 1001 1002 1003 1004 1005 1006 400 510 1007 1008 1009 1010 1011 1012 1013
ARIS Methods
11-1707
Enum. Value 1014 1015 1016 511 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 512 1027 1028 1029 1030 1031 1032 1033 1034 1035
ARIS Methods
11-1708
Enum. Value 1036 513 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 514 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 515
ARIS Methods
11-1709
Enum. Value 1057 1065 1066 1067 1068 1069 1070 1071 1072 1073 516 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 517 1084 1085
ARIS Methods
11-1710
Enum. Value 1086 1087 1088 1089 1090 1091 1092 1093 518 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 519 1104 1105 1106 1107
ARIS Methods
11-1711
Enum. Value 1108 1109 1110 1111 1112 1113 401 520 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 521 1124 1125 1126 1127 1128
ARIS Methods
11-1712
Enum. Value 1129 1130 1131 1132 1133 522 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 523 1144 1145 1146 1147 1148 1149 1150
ARIS Methods
11-1713
Enum. Value 1151 1152 1153 524 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 525 1164 1165 1166 1167 1168 1169 1170 1171 1172
ARIS Methods
11-1714
Enum. Value 1173 526 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 527 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 528
ARIS Methods
11-1715
Enum. Value 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 529 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 402 530 1214
ARIS Methods
11-1716
Enum. Value 1215 1216 1217 1218 1219 1220 1221 1222 1223 531 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 532 1234 1235 1236
ARIS Methods
11-1717
Enum. Value 1237 1238 1239 1240 1241 1242 1243 533 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 534 1254 1255 1256 1257 1258
ARIS Methods
11-1718
Enum. Value 1259 1260 1261 1262 1263 535 1264 536 537 538 539 403 540 678 679 680 681 682 683 684 685 686 404 687
ARIS Methods
11-1719
Attribute Type Contents Value 81 Value 82 Value 83 Value 84 Value 85 Value 86 Value 87 Value 88 Value 89 Value 9 Value 90 Value 91 Value 92 Value 93 Value 94 Value 95 Value 96 Value 97 Value 98 Value 99 VarChar (n) Variant with extensions Very high
Enum. Value 688 689 690 691 692 693 694 695 696 405 697 698 699 700 701 702 703 704 705 706 90 299 168
ARIS Methods
11-1720
Attribute Type Contents Very low Very poor View volatile Voluntary W Waiting WAN Waste (waste management compulsory) Waste disposable Week(s) Weekly Will abort Will be suspended Will no longer be achieved Work days Work hours Work list Work months Work weeks Workflow administrator
Enum. Value 173 550 580 555 313 252 234 109 145
Conversion Factor to Basic Unit 0 0 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 0 0 0 0
144 175 378 231 233 217
0 0 0 0 0 0
0 0 0 0 0 0
429 428 427 431 430 247
0 0 0 0 0 0
0 0 0 0 0 0
ARIS Methods
11-1721
Attribute Type Contents Workstation XOR XOR/AND XOR/OR Y Year(s) Yearly YEN Yes yes Yes, not itself ZAR _
Enum. Value 66 17 22 21 256 48 380 36 308 568 309 456 250
Conversion Factor to Basic Unit 0 0 0 0 0 31536000 0 0 0 0 0 0 0
Basic Type (see Enum. Value) 0 0 0 0 0 43 0 0 0 0 0 0 0
ARIS Methods
Literature List
12-1
12 Literature List
12.1 General Literature List
Brombacher, R.; Bungert, W.: Company modeling practise 1992 Company modeling practise, a seminar by IDS Prof. Scheer GmbH, Bad Soden/Taunus, 12 - 13 November 1992.
Chen, P. P.: Entity-Relationship Model 1976 The Entity-Relationship model: Toward a Unified View of Data, in: ACM Transactions on Database-Systems, Vol. 1 (1976), No. 1, Pages 9 - 36.
Hoffmann, W.; Kirsch, J.; Scheer, A.-W.: Modeling with event driven process chains 1993 Modeling with event driven process chains (Method book, as at : December 1992), in: Scheer, A.-W. (Edit.), Publications of the Institute for Business Process Engineering, Vol. 101, Saarbrcken January 1993.
Keller, G.; Hechler, H.-J.: Information model 1991 Design for an integrated information model for cost accounting in the SAP system, in: Scheer, A.-W. (Edit.): 12th Saarbrck Conference for Accounting and IT. Crucial critical factors in accounting and controlling, Heidelberg 1991, P. 67 - 106.
Scheer, A.-W.: Architecture of integrated information systems 1992 Architecture of integrated information systems - bases for company modeling, 2nd edition, Berlin et al. 1992.
ARIS Methods
Literature List
12-2
Scheer, A.-W.: EDP-oriented business management studies 1990 EDP-oriented business management studies - bases for efficient information management, 4th edition, Berlin et al. 1990.
Scheer, A.-W.: Business process re-engineering 1994 Business process re-engineering- Reference models for industrial business processes, 5th edition, Berlin et al. 1994.
Schlageter, G.; Stucky, W.: Database systems 1983 Database systems: Designs and models, 2nd edition, Stuttgart 1983.
Seubert, M.: SAP data model 1991 State of development and design of the SAP data model, in: Scheer, A.-W. (Edit.): Databases 1991 - Relational database practise: from data model to implementation, Specialist conference on 04.-05.06.1991 in Saarbrcken, Saarbrcken 1991, P. 87 - 109.
Sinz, E. J.: Entity Relationship Model 1990 The Entity Relationship Model (ERM) and its extensions in: HMD Theory and Practise of Business Process Re-engineering, 27 (1990), Vol. 152, P. 17 29.
Scheer, A.-W.: ARIS From the business process to the application. 3rd edition, Berlin et al. 1998
Scheer, A.-W., Jost, W.: ARIS in Practice 2002 Design, Implementation and Optimization of Business Processes, Berlin, Heidelberg, New York 2002.
ARIS Methods
Literature List
12-3
Scheer, A.-W., Abolhassan, F., Jost, W., Kirschmer, M.: Business Process Excellence 2002 ARIS in Practice , Berlin, Heidelberg, New York 2002.
ARIS Methods
Literature List
12-4
12.2 Chapter-Related Literature List

12.2.1 12.2.1.1 Chapter 5, Unified Modeling Language in ARIS Standard Definitions for UML
UML Summary, Version 1.1, September 1997, http://www.omg.org or http://www.rational.com/uml. UML Glossary, Version 1.1, September 1997, http://www.omg.org or http://www.rational.com/uml. UML Notation Guide, Version 1.1, September 1997, http://www.omg.org or http://www.rational.com/uml. UML Semantics, Version 1.1, September 1997, http://www.omg.org or http://www.rational.com/uml.
12.2.1.2
Using UML
R.: UML Unified Modeling Language, Object-oriented
Burkhardt,
modeling for the office, Bonn 1997. Fowler, M.; Scott, K.: UML Distilled - Applying the Standard Object Modeling Language, Reading et al. 1997. Oesterreich, B.: Object-oriented software development with UML, 3rd edition, Munich-Vienna 1997.
12.2.1.3
UML and Business Process Modeling
Ambler, S. W.: What's Missing from the UML? Techniques that can help model effective business applications, Object Magazine 7(1997)8, http://www.sigs.com/publications/objm/9710/ambler.html.
ARIS Methods
Literature List
12-5
Loos, P.; Allweyer, Th.: Process Orientation and Object-Orientation - An Approach for Integrating UML and Event-Driven Process Chains (EPC), Publication of the Institut fr Wirtschaftsinformatik, Paper 144, Saarbrcken 1998, http://www.iwi.uni-sb.de/public/iwi-hefte/heft144.zip.
12.2.2
Chapter 6, Using the Object Modeling Technique (OMT) Modeling Methods
Rumbaugh, J.; Blaha, M.; Premerlani, W.; Eddy, F.; Lorensen, W.: Objectoriented modeling and designing. Mnchen et al.1993.
12.2.3 12.2.3.1
Chapter 7, Methods for Knowledge Management Knowledge Management, General
Probst, G.; Raub, S.; Romhardt, K.: Managing knowledge. How companies use their most valuable resource to the best advantage. Frankfurt Wiesbaden 1998. Brgel, H. D. (Hrsg.): Knowledge management. Steps for achieving an intelligent company. Berlin et al. 1998.
12.2.3.2
Using ARIS for Knowledge Management

Th.: Model-based knowledge management. In: IM
Allweyer,
Information Management & Consulting 13 (1998) 1, S. 37-45. Allweyer, Th.: Knowledge management with ARIS models. In: Scheer, A.-W.: ARIS - From the business process to the application system. 3. edition, Berlin et al 1998, P. 162-168.
ARIS Methods
Literature List
12-6
12.2.3.3
Kaplan, Robert/Norton, David: The Balanced Scorecard-Measures that drive Performance, Harvard Business Review January/February 1992.
ARIS Methods
List of Figures
List of Figures
ARIS Method Figure 2.2-1: Model of a Business process .....................................................2-3 Figure 2.2-2: Process Model Views................................................................2-4 Figure 2.2-3: ARIS Analytical Views of the Process Model.................................2-6 Figure 2.3-1: Descriptive Levels of an Information System...............................2-9 Figure 2.3-2: ARIS Concept ....................................................................... 2-10 Figure 3.2-1: Example of a Process Chain Diagram .........................................3-2 Figure 4.1.1-1: Representation of the "Check customer inquiry" function ...........4-1 Figure 4.1.1-2: Function Tree (Extract) .........................................................4-3 Figure 4.1.1-3: Object-oriented Function Tree ................................................4-4 Figure 4.1.1-4: Process-oriented Function Tree ..............................................4-5 Figure 4.1.1-5: Execution-oriented Function Tree ...........................................4-6 Figure 4.1.1-6: Y Diagram...........................................................................4-8 Figure 4.1.1-7: SAP Applications Diagram......................................................4-9 Figure 4.1.1-8: Example of an Objective Diagram ......................................... 4-10 Figure 4.1.2-1: Graphic representation of an application system type .............. 4-12 Figure 4.1.2-2: Modular Configuration of an Application System Type .............. 4-12 Figure 4.1.2-3: Graphical Representation of an IT Function Type..................... 4-13 Figure 4.1.2-4: Allocation of Functions to Application System Types ................ 4-14 Figure 4.1.2-5: Configuring the Application System Type ............................... 4-15 Figure 4.1.2-6: Mask and List Assignments .................................................. 4-16 Figure 4.1.3-1: Graphical Representation of the Application System and the Module............................................................................................. 4-17 Figure 4.1.3-2: Allocation of Application Systems to their Application System Types .............................................................................................. 4-18 Figure 4.1.3-3: Different Modular Structure of Two Application Systems of the Same Type .............................................................................. 4-19 Figure 4.1.3-4: Assignment of Application System Types, Program Module Types and Program Modules................................................................ 4-20 Figure 4.2.1-1: Examples of Entity Types .................................................... 4-23 Figure 4.2.1-2: Examples of Attributes for the CUSTOMER Entity Type............. 4-24 Figure 4.2.1-3: Example of a Relationship Type ............................................ 4-25 Figure 4.2.1-4: Cardinalities of Relationships between Two Entity Types .......... 4-26
ARIS Methods
List of Figures
Figure 4.2.1-5: Representation of Cardinalities in the ERM ............................. 4-27 Figure 4.2.1-6: ERM for a Bill of Materials .................................................... 4-28 Figure 4.2.1-7: Assignment of Attributes in the ERM ..................................... 4-29 Figure 4.2.1-8: Classification of Customers .................................................. 4-31 Figure 4.2.1-9: Generalization/Specialization ............................................... 4-32 Figure 4.2.1-10: Completely Described Specialization.................................... 4-33 Figure 4.2.1-11: Example of Aggregation .................................................... 4-34 Figure 4.2.1-12: Aggregation with Reinterpreted Relationship Types................ 4-35 Figure 4.2.1-13: Data Cluster (Graphic Symbol) ........................................... 4-36 Figure 4.2.1-14: Data Cluster View of Several Objects................................... 4-36 Figure 4.2.1-15: Grouping......................................................................... 4-37 Figure 4.2.1-16: Upper/Lower Limit (1)....................................................... 4-37 Figure 4.2.1-17: Upper/Lower Limit (2)....................................................... 4-37 Figure 4.2.1-18: Upper/Lower Limit (3)....................................................... 4-38 Figure 4.2.1-19: Upper/Lower Limit (4)....................................................... 4-38 Figure 4.2.1-20: Existential Dependence ..................................................... 4-39 Figure 4.2.1-21: Technical Terms ............................................................... 4-40 Figure 4.2.1-22: Connections between Technical Terms ................................. 4-41 Figure 4.2.1-23: Allocation of ERM Attributes to an Entity Type....................... 4-42 Figure 4.2.1-24: Illustration of an Attribute Type Group ................................. 4-43 Figure 4.2.1-25: eERM and SAP ERM Representations ................................... 4-46 Figure 4.2.1-26: Data Model in IE Notation .................................................. 4-47 Figure 4.2.1-27: Data Model in SeDaM Notation ........................................... 4-48 Figure 4.2.1-28: eERM: Concepts and Forms of Representation ...................... 4-50 Figure 4.2.1-29: DTD Element Type with Pure Text Content ........................... 4-52 Figure 4.2.1-30: Element Types with Mixed Content and Conversion in the DTD ................................................................................................ 4-53 Figure 4.2.1-31: Element Type with an Enumeration Attribute Type................. 4-57 Figure 4.2.1-32: Example of a Material Diagram ........................................... 4-62 Figure 4.2.1-33: Data Warehouse in the Star Scheme ................................... 4-63 Figure 4.2.1-34: Authorization Hierarchy ..................................................... 4-64 Figure 4.2.1-35: Example of a CD Diagram .................................................. 4-65 Figure 4.2.1-36: Example of a Cost Category Diagram................................... 4-67 Figure 4.2.1-37: Information Carrier Diagram .............................................. 4-68 Figure 4.2.2-1: Graphical Representation of the Relation................................ 4-69
ARIS Methods
List of Figures
Figure 4.2.2-2: Assignment of Requirements Definition Attributes and Data Objects ............................................................................................ 4-70 Figure 4.2.2-3: Attribute Allocation Diagram ................................................ 4-71 Figure 4.2.2-4: Definition of a View ............................................................ 4-72 Figure 4.2.2-5: Allocation of ERM Relationship Type to the Attribute ................ 4-72 Figure 4.2.2-6: Example of "System Attributes" Model................................... 4-74 Figure 4.2.2-7: System Attribute Domain .................................................... 4-74 Figure 4.2.3-1: Graphical Representation of Table and Field ........................... 4-75 Figure 4.2.3-2: Field Allocations ................................................................. 4-76 Figure 4.2.3-3: Allocation of Objects of the Requirements Definition and the Design Specification........................................................................... 4-77 Figure 4.2.3-4: Table Specimens ................................................................ 4-78 Figure 4.3.1-1: Organizational Breakdown by Products .................................. 4-80 Figure 4.3.1-2: Hybrid Organizational Forms ................................................ 4-81 Figure 4.3.1-3: Organizational Chart........................................................... 4-83 Figure 4.3.1-4: Organizational Chart with Position and Person Allocation .......... 4-84 Figure 4.3.1-5: Person Types..................................................................... 4-85 Figure 4.3.1-6: Location Allocations ............................................................ 4-86 Figure 4.3.1-7: Location Hierarchies ........................................................... 4-87 Figure 4.3.1-8: Example of a Shift Calendar................................................. 4-90 Figure 4.3.2-1: Grafical Representation of a Network Type ............................. 4-91 Figure 4.3.2-2: Network Topology .............................................................. 4-92 Figure 4.3.3-1: Network Diagram with Location Allocation.............................. 4-94 Figure 4.3.3-2: Network Diagram with Hardware Components and Location Allocation ......................................................................................... 4-95 Figure 4.3.3-3: Example of a "Technical Resources" Model ............................. 4-99 Figure 4.4.1-1: Allocation of Organizational Elements to Functions ................ 4-101 Figure 4.4.1-2: Events (Graphical Representation) ...................................... 4-103 Figure 4.4.1-3: Example of an EPC ........................................................... 4-104 Figure 4.4.1-4: Examples of Rules ............................................................ 4-105 Figure 4.4.1-5: Operators ....................................................................... 4-106 Figure 4.4.1-6: AND Operator for Triggering Events .................................... 4-107 Figure 4.4.1-7: OR Operator for Triggering Events ...................................... 4-107 Figure 4.4.1-8: XOR Operator for Triggering Events .................................... 4-108 Figure 4.4.1-9: AND Operator for Created Events ....................................... 4-108
ARIS Methods
List of Figures
Figure 4.4.1-10: OR Operator for Created Events........................................ 4-109 Figure 4.4.1-11: XOR Operator for Created Events...................................... 4-109 Figure 4.4.1-12: AND Operator of Functions with Created Events .................. 4-110 Figure 4.4.1-13: OR Operator of Functions with Created Events .................... 4-110 Figure 4.4.1-14: XOR Operator of Functions with Created Events .................. 4-111 Figure 4.4.1-15: AND Operator of Functions with Triggering Events............... 4-111 Figure 4.4.1-16: Example of a Function Allocation Diagram (I/O) .................. 4-113 Figure 4.4.1-17: Function Allocation Diagram. ............................................ 4-114 Figure 4.4.1-18: EPC with Input/Output Data ............................................. 4-115 Figure 4.4.1-19: PCD with Input/Output Data ............................................ 4-116 Figure 4.4.1-20: Information Flow Diagram with Open Assignment Wizard ..... 4-117 Figure 4.4.1-21: Example of an Event Diagram .......................................... 4-118 Figure 4.4.1-22: Example of a Process Chain (Requirements Definition) ......... 4-120 Figure 4.4.1-23: eEPC with Functions, Data, Organizational Units and Events . 4-121 Figure 4.4.1-24: Value-Added Chain ......................................................... 4-122 Figure 4.4.1-25: Illustration of Complex Operators in the Rule Diagram ......... 4-123 Figure 4.4.1-26: Input/ Output Diagram.................................................... 4-125 Figure 4.4.1-27: Class Diagram for the Customer Order Class ...................... 4-127 Figure 4.4.1-28: Process Selection Matrix (Extract from the SAP AG R/3 Reference Model) ............................................................................ 4-129 Figure 4.4.1-29: Extract from an eEPC (Material Flow) ................................ 4-131 Figure 4.4.1-30: eEPC (column display) .................................................... 4-133 Figure 4.4.1-31: Role Allocation Diagram (RAD - Role Allocation Diagram) ..... 4-135 Figure 4.4.1-32: Example of a Business Controls Diagram............................ 4-136 Figure 4.4.1-33: DW transformation - Data Transformation for a Data Warehouse ..................................................................................... 4-138 Figure 4.4.1-34: Example of an eBusiness Scenario for the Motor Industry ..... 4-141 Figure 4.4.1-35: Example of a Structuring Model (Extract from VDA 6.2 Standard)....................................................................................... 4-142 Figure 4.4.1-36: Comparison of symbols for the eEPC, Industrial Process, and Office Process model types. ........................................................ 4-145 Figure 4.4.1-37: Example of facts being represented in the eEPC, Industrial Process, and Office Process model types. ............................................ 4-146 Figure 4.4.1-38: Example of a PPC created from an eEPC. ........................... 4-148 Figure 4.4.1-39: Process Instantiation Model.............................................. 4-150
ARIS Methods
List of Figures
Figure 4.4.1-40: Example of a RAMS Diagram ............................................ 4-151 Figure 4.4.1-41: Role Diagram................................................................. 4-154 Figure 4.4.1-42: Structure of a c3 Model ................................................... 4-157 Figure 4.4.1-43: Example of a Screen Design for a Registration Dialog and Implementation in in C++. ............................................................... 4-159 Figure 4.4.1-44: Example of Screen Navigation with Events ......................... 4-161 Figure 4.4.2-1: Information Flow between Application System Types ............. 4-162 Figure 4.4.2-2: I/O Data at the Design Specification Level ........................... 4-163 Figure 4.4.2-3: Access Privileges .............................................................. 4-164 Figure 4.4.2-4: Definition of Responsibilities .............................................. 4-164 Figure 4.4.2-5: Access Diagram (excerpt).................................................. 4-166 Figure 4.4.2-6: Example of a Program Flow Chart (PF) ................................ 4-168 Figure 4.4.2-7: Example of a Screen Diagram ............................................ 4-170 Figure 4.4.2-8: Screen derived from the Figure 4.4.2-7 Screen Diagram ........ 4-171 Figure 4.4.3-1: Data Flow ....................................................................... 4-173 Figure 4.4.3-2: Input/Output Relationships ................................................ 4-174 Figure 4.4.3-3: Assignments to Hardware Components................................ 4-176 Figure 4.4.3-4: Hardware Component as Platform....................................... 4-177 Figure 4.4.3-5: Users and Application System ............................................ 4-178 Figure 4.4.3-6: Location Allocations .......................................................... 4-179 Figure 4.5-1: Example of Products/Services Exchange in a Software Company ....................................................................................... 4-182 Figure 4.5-2: Product/Service Tree ........................................................... 4-184 Figure 4.5-3: Example of a Product Allocation Diagram................................ 4-185 Figure 4.5-4: Product Allocation Diagram - Current Account ......................... 4-186 Figure 4.5-5: Product Allocation Diagrams - Sales Products .......................... 4-187 Figure 4.5-6: Classification of the "Citizenry and Nationality Affairs" Product Group Using a Product Tree .............................................................. 4-188 Figure 4.5-7: Product Selection Matrix of the Social Security Office ............... 4-189 Figure 4.5-8: Competition in the Sports Car Market .................................... 4-190 Figure 5.2.1-1: UML Class Diagram - Associations...........................................5-3 Figure 5.2.1-2: UML Class Diagram - Inheritance Relationships.........................5-4 Figure 5.2.3-1: UML Use Case Diagram .........................................................5-7 Figure 5.2.4-1: UML Activity Diagram ...........................................................5-9 Figure 5.2.5-1: UML Statechart Diagram ..................................................... 5-10
ARIS Methods
List of Figures
Figure 5.2.6-1: UML Collaboration Diagram.................................................. 5-12 Figure 5.2.7-1 : Example of a UML Component Diagram ................................ 5-14 Figure 6.3.1-1: Representation of Instances...................................................6-3 Figure 6.3.1-2: Representation of Classes......................................................6-3 Figure 6.3.1-3: Assigning Instances to Classes ...............................................6-3 Figure 6.3.1-4: Assigning Attributes to Classes...............................................6-4 Figure 6.3.1-5: Assigning Operations to Classes .............................................6-4 Figure 6.3.1-6: Associations between Instances .............................................6-5 Figure 6.3.1-7: Associations between Classes .................................................6-5 Figure 6.3.1-8: Ternary Relationship between Classes .....................................6-6 Figure 6.3.1-9: Modeling an Association as a Class .........................................6-6 Figure 6.3.1-10: Illustration of a Qualified Association .....................................6-7 Figure 6.3.1-11: Illustration of Orders for Associations ....................................6-7 Figure 6.3.1-12: Aggregation between Classes ...............................................6-8 Figure 6.3.1-13: Representation of the Generalization/Specialization Relationship between Classes ...............................................................6-8 Figure 6.3.1-14: Illustration of Constraints on Attributes..................................6-9 Figure 6.3.1-15: Illustration of Constraints on Associations ..............................6-9 Figure 6.3.1-16: Example of an OMT Object Model........................................ 6-10 Figure 6.3.2-1: Representation of Initial, Final, and Transition States .............. 6-11 Figure 6.3.2-2: Representation of the Transition between States..................... 6-11 Figure 6.3.2-3: Representation of Additional Information with State Transition......................................................................................... 6-12 Figure 6.3.2-4: Example of an OMT Dynamic Model ...................................... 6-13 Figure 6.3.3-1: Representation of DataStores............................................... 6-14 Figure 6.3.3-2: Representation of Processes ................................................ 6-14 Figure 6.3.3-3: Representation of Actors ..................................................... 6-14 Figure 6.3.3-4: Representation of Data Flows............................................... 6-15 Figure 6.3.3-5: Representation of Data Flow Splitting .................................... 6-15 Figure 6.3.3-6: Example of an OMT Functional Model .................................... 6-16 Figure 7.3.1-1: Knowledge Structure Diagram................................................7-6 Figure 7.3.2-1: Knowledge mapRelating to Organizational Unit .......................7-8 Figure 7.3.2-2: Knowledge MapMatrix Representation....................................7-9 Figure 7.3.3-1: Knowledge Processing in an eEPC ......................................... 7-11 Figure 9.2.2-1: The BSC as a Structure for Strategic Management ....................9-3
ARIS Methods
List of Figures
Figure 9.2.2-2: The Perspectives of BSC........................................................9-6 Figure 9.3.2-1: BSC Cause-and-Effect Diagram ............................................ 9-15 Figure 9.3.2-2: BSC Key Performance Indicator Allocation Diagram ................. 9-18 Figure 9.3.2-3: Key Performance Indicator Tree ........................................... 9-23 Figure 10.1-1: Transaction Possibilities in e-Business .................................... 10-2 Figure 10.2-1: The Objects in the e-Business Scenario Diagram...................... 10-5 Figure 10.4-1: Detail of the E-Business Scenario "online shop" ....................... 10-9 Figure 10.4-2: Detail from the pipeline diagram.......................................... 10-10 Figure 10.4-3: Detail from DTD - Ordering................................................. 10-11 Figure 11-1: Process, IS, IT and Data Views ................................................ 11-6 Figure 11-2: Zones of a Company's Information System ................................ 11-8 Figure 11-3: Zones Divided into Districts ..................................................... 11-8 Figure 11-4: District Divided into Building Clusters........................................ 11-9 Figure 11-5: "Personnel Support" Building Cluster Divided into Functional Blocks............................................................................................ 11-10 Figure 11-6: IS Functions and IS Services of the "Salaries" Building Cluster ... 11-11 Figure 11-7: "is owner of" Connection between Symbols of the IS View and Relationship and Entity Types............................................................ 11-12 Figure 11-8: "supports" Connection between IS Elements and Function ......... 11-13 Figure 11-9: Subsystem Structure of the DATEV System ............................. 11-15 Figure 11-10: Detailed Description of IT Elements in the Access Diagram ....... 11-16 Figure 11-11: Influences and Effects of the IT Infrastructure ........................ 11-17 Figure 11-12: Integration of IS and IT Elements in a Chronological Procedure....................................................................................... 11-18
ARIS Methods
Index
A
A2A 10-2 A2B 10-2 A2C 10-2 Access diagram 4-162 Access diagram (physical) 4-172 Access privilege 8-8 Organizational units 4-77 Access privileges 8-8 Action program 9-8 Activity-based cost calculation 8-6 Performance scale 4-66 Activity-Based Cost calculation 8-9 Activity-based cost calculation instance 4-67 Actors 5-5 Actual Situation 4-119 Actual situation 3-3, 8-11 Actual value 9-11 Added value Company 8-5 Aggregation 4-30, 4-33 Aggregation operator 4-34 Alarm limit 9-12 Analysis 8-12 Strategy 9-3 Analysis phase, Spezification (Project preparation) 8-12 And operator 4-105 Application modules 8-8 Application scenario Overview 8-1 Solution 8-1 Tasks 8-1 Application system 3-3, 4-17
Component 3-3 Definition 4-17 Definition of technical (physical) conversion 4-19 Element 4-132 Modular structure 4-18 Application system diagram 4-17 Application system type 4-11 Definition 4-11 Existing copies of an application system type 4-17 Information flows between application system types 4-162 Modular structure 4-12 Application sytem type diagram 4-13 Applications 8-8 Architecture of integrated Information Systems (ARIS) Organization view - Requirements definition 4-79 Architecture of integrated Information Systems (ARIS) 1-2, 2-1 ARIS architecture 2-1 ARIS concept 2-1, 2-10 ARIS tools 1-2 Control/Process view of ARIS House 4-79 Architectures General concepts 1-2 ARIS ABC 4-67 Architecture of integrated Information Systems 1-2 ARIS for R/3 8-12 Integration of Lotus Notes 8-7 Object orientied, extended concept 4-126
ARIS Methods
Index
II
ARIS concept 2-10 ASAP 8-12 Association 5-2, 5-6 Attribut Value range 4-28 Attribute 4-28, 4-30, 4-69 Coverage quality 7-7 Degree of coverage 7-7 Distinction from entity type 4-24 Domain 4-28 Attribute allocation Diagram 4-70 Attribute allocation diagram 4-69 Authorization concept 4-135 Authorization conflict 4-63 Authorization type 4-153
Balanced Scorecard system 9-7 Barrier 9-10 Commitment barrier 9-10 Concretizing barrier 9-10 Implementation barrier 9-10 Operational barrier 9-10 Vision barrier 9-10 Basic strength 9-3 Batch processing 3-3 Bottom-up process 9-9 Break 4-88 Breakdown Organizational 4-80 Breaks Media breaks 3-3, 8-11 Organizational 3-3, 8-12 BSC Cause-and-effect diagram 9-13, 9-14 symbols 9-16 BSC Key performance indicator allocation diagram 9-17 Symbols 9-19 Budget Budgeting process 9-8 Projection 9-9 Budgeting 8-9 Budgeting process 9-10 Business Goal 9-4 Strategy 9-4 Business blueprint 8-12, 8-13 Business components 10-4 Business Components 4-139 Business controls diagram 4-136 Business documents 10-4 Business management-related problems 2-1 Business participant 10-3 Business problem 3-1, 8-1
B
B2A 10-2 B2B 4-139, 10-1, 10-2 B2C 4-139, 10-2 Balanced Scorecard Approach 9-1 BSC Cause-and-effect diagram 9-13, 9-14 BSC Key performance indicator allocation diagram 9-17 Concept 9-1 E-Business scenario 10-8 Function tree 9-14 Method 9-1 Object relation to ARIS models 9-24 Organizational chart 9-13 Performance management 9-14 Performance measurement 9-14 Stages 9-3 Structural model 9-13 Value creation chain diagram 9-14 Balanced Scorecard approach 9-2, 9-10
ARIS Methods
Index
III
Business procedure Redundancies and breaks 3-3 Business process 2-1, 2-3, 3-3, 4-2, 10-1, 10-4 Chronological-logical procedure 4-103 Design 8-13 Knowledge 8-6 Modeling 1-2 Modeling objectives 4-9 Models 8-16 Views 3-2 Business to Business 10-1 Business to Consumer 10-2 Business units 9-4 Business/Consumer to Administration 10-2 Businss process Optimization 8-12
Change management project 4-156 Change speed 7-4 Chronological-logical procedural sequence 3-3 CIM 4-79 Class diagram 4-126 Classes 4-126, 5-2 Classification 4-30 Classification diagram 4-124 Cluster 4-35 Cluster instance 4-147 Collaborative Business Maps 10-7 Collective writing 8-7 Column Swimlane 5-8 Communication structure 4-137 Company Motif 9-4 Perspectives 9-2 Philosophy 9-4 Points of view 9-2 Strategy 9-2 Vision 9-2 Company added value 8-5 Company analysis 4-151 Company data In databases 8-6 Company decisions 8-5 Company documentation 8-5 Company objectives 8-5 Company functions 8-5 Company goals 4-151 Company model 8-12 Creation, analysis, and evaluation 1-2 Company objectives 8-5 Hierarchical alignment 8-5 Support using application system type 4-11 Company targets 4-9
C
C++ development environment 4-158 C2A 10-2 C2B 10-2 c3 method 4-156 Calculation method 4-67 Calculation table 8-9 Capital investment 9-8 Cardinality Lower limit 4-37 Cash flow 9-4 Cataloging 8-8 Categorization of knowledge 8-15 Cause-and-effect chain 9-5, 9-6 Cause-and-effect relations 9-6 Cause-and-effect relationship 9-8, 9-11 Cause-and-effect relationships 9-6 Certification 4-142, 8-7, 8-11 Documents 8-10 Procedures 8-10
ARIS Methods
Index
IV
Company's strategic goal 9-1 Comparison plan and actual value 9-11 Competition model 4-190 Competitive situation 4-190 Competitive strategy 9-2 Complex relationships 4-44 Complexity 4-39 Complexity reduction 9-10 Configuration Organizational 4-79 Connection 4-28 Type _is superior_ 4-66 Connection type DTD 4-53 Connector 4-103 Consensus seeking 9-10 Constraint 5-6 Constraint object 5-4 Control instrument 8-9 Control view 2-5, 3-3 ARIS 4-102 ARIS House 4-79 Control/Process view Design specification: 4-162 Cost Reduction 8-11 Structures 8-9 Transparency 8-9 Volumes 4-67 Cost accounting 8-9 Cost categories Hierarchy 4-66 Cost center 4-67 Performance 4-67 Utilization 8-9 Cost center analysis 8-9 Cost driver 4-65, 8-9 CD diagram 4-64 Hierarchy 4-64
Cost rates 4-67 Cost reduction 9-8 Coverage 7-7 Critical factor 4-9, 4-10, 8-5, 9-11 Definition 4-10 Cyclical repeat Shift calendar 4-88
D
Data Cluster 4-35 Data cluster 3-3 Graphical representation 4-35 Data model Creation process 4-45 Data object Dependent and primary 4-44 Data source 9-12, 9-17 Data structures Logical 8-6 Data structuring/database design 8-6 Data view 3-2, 4-22 Implementation 4-75 Requirements definition 4-22 Data warehouse method 9-17 Data warehousing 8-6 Database administration/access administration 8-7 Database management system 4-11 Database management system type 4-14 Database system 4-75 Database systems Object-oriented 8-7 Decision table 4-105 Decision-making power 4-100 Definition E-business 10-1 Hardware component type 4-92 Network type 4-91
ARIS Methods
Index
Degree Goal accomplishment 9-8 Degree of complexity 4-38 Degree of coverage 7-7 Desired 7-4 Knowledge 7-3 Degree of goal accomplishment 9-11 Dependence Existential 4-39, 4-44 Description of the IT processes 8-14 Descriptive Level 2-7 Descriptive ERM attribute 4-42 Descriptive level 2-7, 2-10 Design Business processes 8-13 Organizational design of business processes 8-13 Organizational design of the SAP system 8-13 Design of interfaces Between SAP R/3 and non-SAP applications 8-13 Design operator 4-30 eERM 4-49 Design process 4-30 Design specification 2-5, 2-7 Control/Process view 4-162 Function view 4-11 Organization view 4-91 Determination of application systems and modules 8-13 Development of interfaces 8-13 Development of QM documentation 8-10 Development of the system interface 814 Diagram Process chain 3-2 Direction 9-11
Document 8-6 Document type definition 4-51 Documentation Company added value 8-5 Company functions 8-5 Company objectives 8-5 Organizational structure 8-5 Documented knowledge 7-1 Domain 4-28, 4-75 Double loop learning 9-2, 9-9 Draft list 4-15 DTD 4-51, 10-10 Attribut default 4-56 Connection type 4-53 Elementtyp 4-51 DTD model 4-51 DW structure 9-24 DW transformation 9-24 Dynamic modeling 6-1
E
E-business 10-1 Definition 10-1 E-Business scenario Balanced Scorecard 10-8 Report 10-6 E-Business scenario diagram 10-1, 10-3 Idea 10-3 Security 10-6 Transaction security 10-6 Transmission path 10-6 eEPC 4-142, 4-181 Symbols 4-143 eEPC as column display implicit relationships 11-1488 eEPC Material flow 4-61 eEPK 9-24 eERM Approach 4-44
ARIS Methods
Index
VI
Concepts and forms of representation 4-49 Design operators 4-49 Method 4-44 Structural elements 4-49 eERM Attribute allocation diagram 4-42 Effect 9-11 Either/Or operator 4-105 Electronic marketplaces 10-3 Element Application system 4-132 Organizational 4-132 Elementary function 4-2 Elementary process 4-153 Elementary role 4-155 e-mail 10-4 Employee role 10-4 Entities Of the same type 4-23 Entity 4-23 Occurrence level 4-22 Type 4-22, 4-23 Type level 4-22 Entity relationship model Extensions 4-30 Original model 4-22 Entity Relationship Model ERM 4-22 Structured 4-44 Entity type 4-23, 4-42 Distinction from attribute 4-24 Weak 4-44 Enumeration Literal 5-4 Environment 4-79 EPC 4-103 ERM attribute 4-42 ERM Attribute allocations 4-42 ERM Relationship type 4-42 ERP system
Connection 10-10 XML 10-10 Event 2-2, 2-3, 2-5, 3-2, 4-7, 4-102 Control 4-119 Grapical representation 4-102 Event control event-driven process chain(EPC) 4-102 Event diagram 4-118 Event driven process chain (EPC) 4-6 Event-driven Process chain 4-103 Event-driven process chain (EPC) 4-103 Branches and processing loops 4-103 Example Network 4-91 Execution-oriented 8-5 Existential dependence 4-39 Existential dependency 4-44 Extensible markup language (XML) 10-10 Extension Point 5-6 External key 4-42 Extranet 10-4
F
Fact hierarchy 4-142 Feedback process 9-9 Field 4-75 Field (specimen) 4-78 Financial key performance indicator 9-1 Financial objective 9-7 Form 4-11 Form field 4-160 Forms 8-7 Frame 4-160 Function 4-1, 4-2, 4-7 Assignment to data 4-102 Batch run 4-7 Compression levels 4-2 Degree of integration 4-100
ARIS Methods
Index
VII
Execution 4-7 Grouping criteria 4-3 Hierarchy levels 4-2 Procedure 2-2, 3-2 Process-oriented breakdown 4-5 Quantity structure 4-7 Sequence 4-102 Specificaton of execution 3-3 View 2-5, 4-100 Function allocation diagram 4-112, 4-134 Function tree 4-2, 4-3 Object-oriented 4-3 Operation-oriented 4-3 Process-oriented 4-6 Function view 3-2, 4-1 Design specification 4-11 Implementation 4-17 Requirements definition 4-1 Function/organizational level diagram 4-100 Functional modeling 6-1 Functions Procedural sequence 4-6 Future significance 7-4
H
Hardware component type 4-91 Definition 4-92 Hierarchy Critical factors 4-10
I
Identification Dependence 4-39 IE data model 4-47 Image 8-6 Implementation 2-5 Data view 4-75 Function view 4-17 Implementation description 2-8 Implicit relationship 1-3, 4-132, 11-1487, 11-1488, 11-1492, 11-1493 Indicator Lagging indicator 9-7 Leading indicator 9-7 Indicator type Lagging indicator 9-12 Leading indicator 9-12 Industrial process 4-142 Symbols 4-143 Industry 8-5 Influencing factor 9-11 Information carrier 3-3 Information carrier diagram 4-68 Information carrier symbol 4-125 Information object Change of status 4-102 Information system 4-151 Lifecycle 2-7 Procedural model for development 2-7 Support 7-5 Information systems 3-1 Information technology 9-5
G
General resource 4-147 General rule Operators 4-105 Generalization 4-30, 4-32, 4-142 Occurrences 4-33 Goal accomplishment Degree 9-8 Goods shipment 10-4 Graph Directional 4-44 Group decision support systems 8-7 Grouping 4-30, 4-36, 4-39 Groupware 8-7
ARIS Methods
Index
VIII
Initial business process 3-1 Initial state 5-7 Innovations 9-5 Input and output data 3-3 Input data 8-16 Input/Output diagram 4-125 Input/Output Diagram 4-112 Implicit Relationships 11-1492 Integration concept 2-1 Intellectual capital 8-15 Interaction 9-5, 9-11 Interactive processing 3-3 Internet 10-1, 10-4 Interrelation 9-9 Interviews 8-11 Intranet 10-4 ISO 8-10 IT function type Definition 4-13 IT infrastructure requirements Documentation 8-8 Identification 8-8 IT Processes 8-14 IT support Degree 3-3
Documentation 7-1 Knowledge category 7-1 Significance 7-3 Knowledge management 7-1, 7-4, 8-14 Knowledge map 7-7, 8-15 Knowledge map or yellow page 8-14 Knowledge structure diagram 7-6 Knowledge structure diagram 7-2 Knowledge utilization 7-3
L
Lagging indicator 9-7 Layout model 11-1482 model classification 11-1482 Leading indicator 9-7 Lean Management 4-79 Lean Production 4-79 Level or phase concept 2-7 Lifecycle Model 2-1, 2-5 Lifecycle model 2-7 Line position 4-82, 4-83 Link 4-82 Operator 3-3 List 4-11, 4-15 Lotus Notes Integration in ARIS 8-7
K
Key Complex 4-34 Simple 4-34 Key attribute 4-28, 4-42 Key performance indicator 9-8, 9-11 Financial 9-10 Performance measure 9-11 Key performance indicator system 9-9 Key performance indicators Channelling 9-16 Knowledge Degree of coverage 7-3
M
Main process 4-9 Make-or-buy-desicions 8-9 Management 9-9 Management bottleneck 9-10 Management information 9-1 Management process 9-1 Strategy 9-3 Management support systems 8-6 Management system 1-3, 9-2
ARIS Methods
Index
IX
Manual processing 3-3 Market growth 9-14 Maskendesign.rsm 4-158 Material class Definition 4-61 Material diagram 4-61 Material flow eEPC 4-61 In Process models 4-61 PCD 4-61 Material resource 4-88 Material type 4-61 Definition 4-61 Maximal value 9-12 Measure 9-12 Media 3-3 Media breaks 8-11 Methods 4-126 Selection criteria 2-11 Minimal value 9-12 Model eBusiness scenario diagram 10-1 Model Access diagram 4-162 Access diagram (physical) 4-172 Application system diagram 4-17 Application system type diagram 4-11 Attribute allocation diagram 4-69 Authorization hierarchy 4-63 Business controls diagram 4-136 c3 method 4-156 Class diagram 4-126 classification 11-1482 Classification diagram 4-124 Collaborative business maps 10-7 Communications diagram 4-124 Competition model 4-190 Cost driver diagram (CD diagram) 4-64 DTD 4-51
eEPC (Extended event-driven process chain) 4-102 eEPC with material flow 4-130 eERM 4-30 eERM Attribute allocation diagram 4-42 ERM basic model 4-22 Function allocation diagram 4-112 Function tree 4-2 Function/organizational level diagram 4-100 IE Data model 4-47 Industrial process 4-142 Information carrier diagram 4-68 Input/Output diagram 4-125 Input/Output Diagram 4-112 Knowledge map 7-7 Knowledge structure diagram 7-6 layout 11-1482 Material diagram 4-61 Network diagram 4-94 Network topology 4-91 Objective diagram 4-9 Office process 4-142 OMT Data Value Decomposition 6-17 OMT Dynamic model 6-11 OMT Functional model 6-14 Organizational chart 4-82 PCD (process chain diagram) 4-119 Privileges diagram 8-16 Product allocation diagram 4-185 Product tree 4-188 Product/service exchange diagram 4-181 Program flow-chart (PF) 4-168 Program structure chart 4-167 Project process chain (PPC) 4-147 Quick model 4-156 RAMS 4-151 Relations diagram 4-69
ARIS Methods
Index
Rule diagram 4-123 SAP ALE filter model 4-134 SAP ALE message type model 4-134 SAP applications diagram 4-9 Screen diagram 4-169 SeDaM model 4-48 Semantic 2-8 Shift calendar 4-88 Structuring model 4-142 Swimlane 1-3 System attribute domain 4-73 System attributes 4-73 Table diagram 4-75 Technical resources 4-96 Technical term model 4-40 UML Activity diagram 5-7 UML Class description diagram 5-5 UML Class diagram 5-2 UML collaboration diagram 5-11 UML Component diagram 5-13 UML Statechart diagram 5-10 UML use case diagram 5-5 Value-added chain diagram 4-122 Y diagram 4-7 Model type Screen design 4-158 Screen navigation 4-160 Modeling Material flow in material diagram 4-61 Methods 1-2 Modeling support 5-2 Modelling Semantic 2-7 Module 4-17 Definition 4-17 Module type 4-11 Definition 4-13 Money transaction 10-4 Motif 9-4
N
Network 4-94 Example 4-91 Type 4-91 Network connection 4-94 Network connection type 4-91 Network diagram 4-94 Network example 4-91 Network management 8-8 Network node 4-94 Network node type 4-91 Network topology 4-91 Network type Definition 4-91 Notation 4-38, 4-39
O
Object central 11-1482 Hierarchical alignment 6-17 structurally relevant 11-1482 Object model Multi-level 4-88, 4-149 Shift calendar 4-88 Object modeling 6-1 Object modeling technique 6-1 Object Modeling Technique 8-7 Object oriented Extended ARIS concept 4-126 Modeling 4-126 Object types Documented knowledge 7-4 Knowledge category 7-2 Objective Operational monetary 9-10 Strategic 9-10 Strategic 9-1 Objective diagram 4-9
ARIS Methods
Index
XI
Object-oriented 8-5 Object-oriented database systems 8-7 Office process 4-142 Symbols 4-143 OMT 6-1 OMT Data Value Decomposition 6-17 OMT Dynamic model Representation of initial, final and transition states 6-11 OMT Dynamic Model 6-11 OMT Functional model Representation of actors 6-14 Representation of data flows 6-15 Representation of processes (processes) 6-14 Splitting data flows 6-15 OMT Functional Model 6-14 OMT Object model Aggregation between classes 6-7 Assignment of attributes to classes 6-4 Assignment of instances to classes 6-3 Assignment of operations to classes 6-4 Associations between classes 6-5 Generalization and inheritance 6-8 Modeling and association as a class 6-6 N-Associations between classes 6-6 Representation of a qualified association 6-7 Representation of classes 6-3 Representation of instances 6-2 Representation of orders for associations 6-7 Online shop 10-2 Example 10-8 Model 10-8 Operating resource class Definition 4-96 Operating resource type
Definition 4-96 Operating resources Definition 4-96 Operating system 4-11 Operating system type 4-14 Operational business problem 2-7 Operations 5-2 Operator And 4-105 Complex relationships 4-105 Either/Or 4-105 Event 4-105 Function 4-105 Logical And operator 4-105 Logical OR operator 4-105 Or 4-105 OR 4-105 Rules 4-105 XOR 4-105 Or operator 4-105 OR operator 4-105 Organization 4-79 View 4-79, 4-119 Organization view 2-5, 3-2 Design specification 4-91 Requirements definition 4-79 Organizational Break 8-12 Breakdown 4-80 Configuration 4-79 Element 4-132 Unit 4-79 Organizational chart 4-82, 4-100 Organizational form Hybrid 4-81 Organizational modeling 4-63 Organizational structure 4-79, 8-5, 9-13 Organizational unit 2-3, 4-82 Assignment to functions 4-102
ARIS Methods
Index
XII
Organizational unit type 4-84, 10-4 Organizational units Structuring 4-79 Orientation to the past 9-10 Output data 8-16
Learning and development perspective 9-2 Learning perspective 9-5 Person-oriented 9-11 Process perspective 9-2, 9-5 Standard 9-5 Phase design (business blueprint) 8-12, 8-13 Philosophy 9-4 Pipeline diagram 10-9 Place Virtual 10-3 Plan value 9-11 Planned progress figure 9-9 Planning Strategic 8-11 Planning process 9-10 Position 4-83 PPC 4-68, 4-147 Pricing 8-9 Privileges diagram 8-16 Problem Business 8-1 Procedural model 2-7 Procedural sequence 4-6 Chronological-logical 4-6 Procedural structure 4-79 Procedure 2-3, 4-2 Bottom-up 4-32 Top-down 4-35 Top-down 4-32 Procedure concept 1-2 Procedure model 8-10, 8-11, 8-13 Proces view ARIS House 4-79 Process 2-2, 4-2 Costs 9-5 Feedback 9-9 Performance amount-neutral 4-65
P
Parameter 5-4 Partial objective 9-7 Partial strategy 9-3 Path Specify 4-148 PCD 3-2 Implicit relationships 11-1493 Material flow 4-61 With material flow Implicit relationships 11-1493 Performance 4-180 Performance amount-induced 4-65 Performance amount-neutral 4-65 Performance driver 9-7 Performance management 9-14 Performance measurement 9-14 System 9-1 Performance Measurement Approach 9-1 Performance scale 4-66 Period 4-88 Shift calendar 4-88 Person type 4-84 Personnel development 9-5 Personnel resource 4-88 Perspective 9-11 Client perspective 9-2 Customer perspective 9-5 External performance perspective 9-2 Financial 9-5 Financial and ecomomic 9-2 InternaI performance perspective 9-2
ARIS Methods
Index
XIII
Prioritiation 4-149 Times 9-5 Process and organizational structures 8-9 Process and/or function deficits 8-12 Identified in the SAP R/3 reference model 8-12 Process calculation 8-9 Process chain 4-2, 4-80, 4-102 Creation, analysis and evaluation 2-1 Event-driven 4-103 Process chain analysis 3-1 Process chain diagram 3-3 Requirements definition 4-119 Process chain diagram (PCD) 3-1, 3-2 Process cost rates 8-9 Process customizing Workflow management systems 8-16 Process descriptions 8-7 Process documentation 8-5 Process instantiation cycle 4-149 Process instantiation interval 4-149 Process instantiation model Interval 4-149 Process instantiation cycle 4-149 Process Instantiation Model 4-149 Process instantiation plan 4-149 Process knowledge 8-6 Process management 8-10 Process models Material flow 4-61 Process scenarios 4-9 Process selection matrix 4-9, 4-128 Process type 8-5 Process variants 8-12 Process view ARIS 4-102 Process warehousing 8-6 Processing knowledge in business processes 8-15
Processor 2-3 Process-oriented 8-5 Process-oriented function tree 4-3 Product 4-180 Product allocation diagram 4-185 Product selection matrix 4-189, 8-10 Product tree 4-188, 8-10 Product/Service 2-2 Product/service exchange diagram 4-181, 4-185 Product/service tree 4-183 Production level 9-8 Program code 8-14 Program file 4-19 Program flow-chart 4-167 Program flow-chart (PF) 4-168 Program module Definition 4-20 Program module type Assignment of application system types 4-20 Assignment to program modules 4-20 Definition 4-20 Programming language 4-14 Project documentation 8-11, 8-13 Planning 8-13 Project management 4-68, 8-10 Project preparation 8-12 Project process chain 4-68, 4-147 Project structural elements 4-147 Provision of products/services Commercial 8-9 Publicity campaign 9-8
Q
QM documentation 8-10 QM manual 8-11 Quality Assurance 8-10
ARIS Methods
Index
XIV
Control 8-10 Control 8-10 Criterion 4-142 Documents 8-10 Enhancement 8-10 Improvement 8-10 Management 4-142, 8-10 Planning 8-10 Policy 8-10 Quick model 4-156 Quick object 4-156
Formation 4-33 Reinterpreted 4-34, 4-39 Reorganization Carrying out 8-11 Measures 8-11 Report E-Business scenario 10-6 Maskendesign.rsm 4-158 Requirements definition 2-7 Data view 4-22 Function view 4-1 Organization view 4-79 Resource 4-88 Information technology 2-2 Information technology 2-3 Material resource 4-88 Object 4-147 Personnel resource 4-88 View 2-5 Resource view 3-2 Resources Categories 9-4 Restrictions (constraints) for classes, attributes and associations 6-9 Result indicator 9-9, 9-12 Results quality 8-11 Retrieval functionality 8-8 Return on capital 9-4 Risk Control 4-136 Risk 4-136 Solution 4-136 ROI 9-4 Role 4-134 Role name 4-28 Rule Operator 4-105
R
RAMS Vorgehensmodell 4-152 Redundancy Data redundancies 3-3 Multiple entries 3-3 Time delays 3-3 Reference field States 2-5 Referential data integrity 4-39 Reinterpreted relationship type 4-34 Relations diagram 4-69 Relationship B2B 4-139 B2C 4-139 Complexity 4-25 Existence of 4-25 Hierarchical 4-44 implicit 11-1487, 11-1488, 11-1492, 11-1493 eEPC as column display 11-1488 Implicit 1-3, 4-132, 11-1493 Type 4-22, 4-39 Relationship occurence Lower limit 4-37 Relationship type 4-25 Distinguishing criteria 4-25
ARIS Methods
Index
XV
S
Sales revenue 9-4 SAP ALE filter model 4-134 SAP ALE Message Flow Model 4-134 SAP ALE message type model 4-134 SAP applications 8-5 SAP applications diagram 4-9 SAP R/3 reference model 4-9 SAP-System 8-13 Scheduling basis 8-9 Screen 4-15, 4-169, 8-14 Screen design 4-15, 4-158 Screen diagram 4-169 Derive automatically 4-169 Screen navigation 4-160 Security protocol 10-4 SeDaM model 4-48 Semantic generator 4-156 Senior management 9-4 SER Approach 4-44 Model 4-44 Services 4-180 Shareholder value 9-4 Shift 4-88 Shift calendar 4-88 Assignment 4-88 Break 4-88 Cyclical repeat 4-88 Period 4-88 Shift 4-88 Shift cycle 4-88 Shift plan 4-90 Shift cycle 4-88 Shift plan 4-90 Significance Future 7-4 Knowledge category 7-3
Similar entity 4-23 Simulation 8-5 Sorting index 4-75 Specialization 4-32, 4-44, 4-142 Completeness 4-32 Disjunctiveness 4-32 Occurences 4-33 Specify Path 4-148 Spezification 8-12 Staff position 4-82, 4-83 Standard perspective 9-5 Start and end events 4-102 State 5-10 Status 2-3 Steps Strategy-oriented 9-1 Strategic objective 9-11 Strategy 9-11 Analysis 9-3 Business strategy 9-4 Business units 9-4 Competition 9-2 Execution 9-9 Higher-level 9-8 Implementation 9-8 Inconsistency 9-9 Information technology 9-5 Innovations 9-5 Learning 9-9 Management process 9-3 Market-oriented 9-4 Modes of action 9-10 Objective 9-11 Partial strategy 9-3 Personnel development 9-5 Planning process 9-10 Specific business segment 9-3 Theoretical formulation 9-10
ARIS Methods
Index
XVI
Structural change speed 7-4 Structural element 4-142 Structuring model 4-142 Generalization 4-142 Specialization 4-142 Stuctural elements of the eERM 4-49 Subcategory Knowledge 7-6 Subfunction 4-2 Substitution relationship 4-183 Swimlane 5-8 Swimlane model eEPC as column display 11-1488 Swimlane model 1-3, 4-132, 11-1487 Input/Output diagram 11-1492 PCD 11-1493 PCD with material flow 11-1493 UML activity diagram 11-1492 symbol BSC Cause-and-effect diagram 9-16 Symbol BSC Key performance indicator allocation diagram 9-19 Synergy effect 9-9 System attribute domains 4-73 System attributes 4-73 System interface 8-14 System interface models 4-73 Systems Management support 8-6
Group 9-10 Individual 9-10 Target concept 8-11 Target diagram 9-24 Target guideline 9-8 Target hierarchies 4-9 Target procedure 3-3 Target time period 9-12 Target value 9-12 Task Access privileges 8-8 Analysis phase, Spezification (Project preparation) 8-12 Carrying out the reorganization 8-11 Categorization of knowledge 8-15 Certification documents 8-10 Certification procedures 8-10 Cost center analysis 8-9 Data structuring/database design 8-6 Database administration/access administration 8-7 Description of process and organizational structures 8-9 Description of the IT processes 8-14 Determination of application systems and modules 8-13 Development of QM documentation 8-10 Development of the system interface 8-14 Documentation of company functions 8-5 Documentation of company objectives 8-5 Documentation of IT infrastructure 8-8 Documentation of organizational structure 8-5 Documentation of the company added value 8-5
T
Table 4-75 Table (specimen) 4-78 Table diagram 4-75 Target 9-8 Concept 3-1 Definition 4-9 Financial 9-12
ARIS Methods
Index
XVII
Identification of IT infrastructure requirements 8-8 Integration of Lotus Notes 8-7 Knowledge map or yellow page 8-14 Phase design (business blueprint) 8-12, 8-13 Process calculation 8-9 Process customizing of workflow management systems 8-16 Process documentation 8-5 Process warehousing 8-6 Processing knowledge in business processes 8-15 Project documentation 8-11, 8-13 Task performer 4-79, 4-82, 4-100 Technical operating supply Definition 4-97 Technical operating supply class Definition 4-97 Technical operating supply type Definition 4-97 Technical resources 4-96 Technical terms model 4-40 Term Actual value 9-11 Alarm limit 9-12 Critical factor 9-11 Data source 9-12 Key performance indicator 9-11 Maximal value 9-12 Measure 9-12 Minimal value 9-12 Perspective 9-11 Plan value 9-11 Strategic objective 9-11 Strategy 9-11 Target value 9-12 Tolerance range 9-12 Vision 9-11
Warning limit 9-12 Time interval 4-88 Time reduction 8-11 Tolerance range 9-12 Top-down approach 9-8 Training 8-7 Transaction 4-13, 4-134 Transaction steps 4-11 Transfer structure 4-137 Transitions 5-8 Transport system Definition 4-98 Transport system class Definition 4-98 Transport system type Definition 4-98 Type Entity 4-22, 4-23 Network 4-91 Type level 4-22
U
UML 5-1 Actors 5-5 Aggregation 5-3 Assignable UML object types 5-17 Attribut Operation 5-11 Parameter 5-11 Attribute Condition 5-11 Message number 5-11 Operation 5-11 Parameter 5-11 Attributes 5-3, 5-5 Classes 5-4 Composition 5-3 Initial state 5-7 Integration in ARIS 5-15
ARIS Methods
Index
XVIII
Interfaces 5-4, 5-5 Notes 5-4, 5-5 Objects 5-4, 5-5 Operations 5-3, 5-5 Packages 5-4 Relationships of UML diagrams to ARIS models 5-21 Symbol Split/Synchro 5-8 Transitions 5-8 UML class diagram 5-2 UML collaboration diagram 5-11 UML Glossary 5-1 UML Notation Guide 5-1 UML Semantics 5-1 UML Summary 5-1 UML use case diagram 5-5 Use cases 5-5 UML 1.4 5-4 UML activity diagram Implicit relationships 11-1492 UML Activity diagram 5-10 UML modeling support 5-2 UML Statechart diagram 5-10 UML version 5-1 Unified Modeling Language 5-1, 8-7 Unit Organizational 4-79 Update cycles 2-8 User groups 8-8 User interface 4-11, 4-14 User privileges 8-8 User profile 4-135 Users 8-8
VDA 8-10 Video 8-6 View 2-4 Business process 3-2 Formation 2-10 Person-oriented 9-11 View (physical) 4-76 Virtual places 10-3 Vision 9-11
W
Warehouse equipment Definition 4-97 Warehouse equipment class Definition 4-97 Warehouse equipment type Definition 4-97 Warning limit 9-12 Weak point 8-12 Current problem solution 3-3 Weak point analysis 8-5 Web form 4-158 Work instructions 8-7 Work quality 8-11 Workflow 8-5 Workflow management systems Process customizing 8-16 Workflow model 8-16 Workgroup computing 8-7 Workshop 9-11
X
XML 10-10 XML Document 4-51 XOR operator 4-105, 4-148
V
Value range 4-69 Attribute 4-28 Value-added chain diagram 4-181, 8-13 Variant 4-187
Y
Y diagram 4-7
ARIS Methods
Index
XIX
Y-CIM model 4-7
Yellow page 8-14
ARIS Methods

JobAid ARIS Method Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

JobAid ARIS Method Manual

Uploaded by

Copyright:

Available Formats

ARIS Method

Process Chain Analysis .......................................................................... 3-1

Data View................................................................................... 4-22

Alternative Forms of Representation............................ 4-44

4.2.1.3.2 4.2.1.3.3 4.2.1.4 4.2.1.5

IE Data model ............................................... 4-47 SeDaM model................................................ 4-48

4.2.1.5.3.1 4.2.1.5.3.2 4.2.1.5.4 4.2.1.6 4.2.1.7 4.2.1.8 4.2.1.9

Testing DTDs ................................................ 4-60

Project Management Data Model................................. 4-68

4.2.1.10.1 4.2.2.1 4.2.2.2 4.2.3 4.3 4.3.1

Organization View........................................................................ 4-79

Design Specification - Network Topology ................................ 4-91 Implementation .................................................................. 4-94

4.3.3.1 4.3.3.2 4.4 4.4.1

Functions - Organization - Data ................................ 4-119

SAP ALE Models ..................................................... 4-134

Role Allocation Diagram (RAD) ................................. 4-134

Implementation - Access Diagram (physical)........................ 4-172 4.4.3.1 4.4.3.2 4.4.3.3

4.5.5 4.5.6 5 5.1 5.2

Product Selection Matrix .................................................... 4-189 Competition Model ............................................................ 4-190

Integrating UML Diagrams and Other ARIS Models............................ 5-15

Relationships to Other ARIS Models ....................................... 5-21

Model Types for Modeling Knowledge Processing ................................ 7-6

Balanced Scorecard Method.................................................................... 9-1 9.1 9.2

9.2.3 9.3 9.3.1 9.3.2

Development of a Balanced Scorecard with ARIS BSC ....................... 9-11

9.3.3 10.1 10.2

Relationship to Other Models ................................................ 9-24

10.2.1 10.2.2 10.2.3 10.3 10.3.1 10.3.2 10.3.3

Evaluations Using Reports............................................................. 10-6

Collaborative Business Maps ................................................. 10-7

11 IT City Planning .................................................................................. 11-1

11.2.91 11.2.92 11.2.93 11.2.94 11.2.95 11.2.96 11.2.97 11.2.98 11.2.99

11.7.1 11.7.2 11.8 11.8.1 11.8.2 11.8.3 11.8.4 11.8.5 11.9

Implicit Relationships in Swimlane Models .................................. 11-1487

Model Types (ModelTypeNum) .................................................. 11-1494

12.2.3.1 12.2.3.2 12.2.3.3 List of Figures Index

Architecture of integrated Information Systems (ARIS)

2 Architecture of integrated Information Systems (ARIS)

Architecture of integrated Information Systems (ARIS)

2.2 Descriptive Views

Architecture of integrated Information Systems (ARIS)

Figure 2.2-1: Model of a Business process

Architecture of integrated Information Systems (ARIS)

Figure 2.2-2: Process Model Views

Architecture of integrated Information Systems (ARIS)

Architecture of integrated Information Systems (ARIS)

Figure 2.2-3: ARIS Analytical Views of the Process Model

Architecture of integrated Information Systems (ARIS)

2.3 Descriptive Levels

Architecture of integrated Information Systems (ARIS)

Architecture of integrated Information Systems (ARIS)

Figure 2.3-1: Descriptive Levels of an Information System

Architecture of integrated Information Systems (ARIS)

Figure 2.3-2: ARIS Concept

Architecture of integrated Information Systems (ARIS)

Process Chain Analysis

3 Process Chain Analysis

Process Chain Analysis

3.2 Process Chain Diagrams (PCDs)

Figure 3.2-1: Example of a Process Chain Diagram

Process Chain Analysis

Process Chain Analysis

4 Modeling within the Views and Levels of the ARIS Concept

Functions are displayed as rectangles with rounded corners: