ArchiMate - Software and Computer Technology

More documents

Recommendations

Info

Generic Structure at Each Layer External Internal Passive structure Behavior Active structure Similar concepts at each layer make the language easier to learn <strong>and</strong> more consistent in use
Notation • Most concepts have two notations: • Icon • Box with icon • Sharp corners = structure • Rounded corners = behavior • Notation resembles UML <strong>and</strong> BPMN • to stay close to what architects already know • but for other stakeholders, different notations may be used! • Relations (arrows etc.) are also mostly taken from existing languages, with a few exceptions
Page 1 and 2: ArchiMate: Past, Present and Future
Page 3 and 4: Novay • Independent, not-for-prof
Page 5 and 6: Together investing in ICT-driven in
Page 7 and 8: Role of Enterprise Architecture pro
Page 10 and 11: Support for Enterprise Architecture
Page 12 and 13: The ArchiMate Research Project •
Page 14 and 15: Integrated Modelling with ArchiMate
Page 16 and 17: The ArchiMate Language High-level m
Page 18 and 19: ArchiMate and UML/BPMN/… • Arch
Page 20 and 21: Services as Binding Concept Custome
Page 24 and 25: Business Functions and Roles
Page 26 and 27: Processes and Services
Page 28 and 29: Information
Page 30 and 31: Infrastructure
Page 32: Layered Architecture
Page 35 and 36: ArchiMate Now • Applications at m
Page 37 and 38: Active User Community • NAF worki
Page 39 and 40: ArchiMate’s Future
Page 41 and 42: TOGAF, ArchiMate and Extensions Mot
Page 43 and 44: Another Example
Page 45 and 46: Implementation & Migration Example
Page 47 and 48: Process • ArchiMate version 2.0 s
Page 49: Summarizing: Benefits of ArchiMate

ArchiMate - Software and Computer Technology

Create successful ePaper yourself

Delete template?

Save as template?