DOCSLIB.ORG

The Archimate Standard for Enterprise Architecture Modelling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Archimate Standard for Enterprise Architecture Modelling Enterprise Architecture Modelling with ArchiMate Marc Lankhorst Principal Researcher Enterprise Architecture Utrecht University, January 11, 2010 Overview • Introduction • Enterprise architecture • The ArchiMate modelling language • Integration of business, applications, and technology • Role of service orientation • Example: ArchiSurance, merger of an insurance company • Relation with other developments • UML, BPMN • Zachman Framework • TOGAF Novay • Independent, non-profit research institute • Founded & funded by companies, the Dutch government, and universities • To create impact with ICT innovation • In projects together with industry and academia Enterprise Architecture Context • Business and ICT become closer • Ever higher demands on ICT: complexity, flexibility • Many changes, rapid time-to-market required • Management & control difficult • Architecture as a tool • for communication • for governance • for innovation Architecture IEEE Std 1471: Architecture = structure(s) of a system in terms of • components, • their externally visible properties, • their relations, • and the underlying principles “Structure with a vision” Role of Enterprise Architecture Mission Vision Strategy as is Goals to be enterprise architecture culture Actions leadership domain/aspect architectures people Operations products processes people IT … Enterprise Architecture: Describing Coherence Information architecture Product architecture ? Process architecture ? ? ? Application architecture Technical architecture ? Better Support for the Enterprise Architect • Increasing need for precise documentation on the enterprise architecture level • Integrating various aspect models in many languages (UML, IDEF, BPMN, ARIS, ...) • Communicating about architecture with others • Get away from the “fuzzy pictures” image • Analysis of architectures before their implementation • Needed: well-founded, practical, and vendor-independent standard for enterprise architecture modelling The ArchiMate Research Project • 2½ years, July 2002 - December 2004 • approx. 35 man-years, 4 million euro • Consortium of companies and knowledge institutes • Directed by Novay (then still Telematica Instituut) ArchiMate Focus Visualisation Analysis Integration ArchiMate Scope Formal models Analysis Communication with stakeholders Design Visualisation Napkin Architecture Whiteboard Idea Use Powerpoint process Link with implementation Management Maintenance Version control Main Benefits of ArchiMate • Lean and mean language: • just enough concepts, not bloated to include everything possible • Well-founded concepts & models give precision • clear communication about architectures • get away from the ‘fuzzy pictures’ image • Links to existing approaches • UML, BPMN, TOGAF • International vendor-independent standard • The Open Group • Tool support • several tools available Service Orientation Design Paradigms Increased focus on the ‘outside’: • Structured programming • Object orientation • Component-based development • Service-oriented architecture (SOA) • (Event-driven architecture?) Service Orientation Service • Unit of externally available functionality • Offered via clear interfaces • Relevant for the environment Web services as a prominent technological example Service-Oriented Architecture Is • A way of thinking • A bridge between business and IT Is not • Web services • Asynchronous communication • A software artefact (an ESB) Services are Central to ArchiMate Customer External business service Business Internal business service External application service Application Internal application service External infra. service Technology Internal infra. service Integrated Modelling Integration An architecture might encompass for example: • products & services • organisation • processes • information • applications • systems • networks This requires concepts for domains and relations, linked with existing techniques The ArchiMate Language High-level ArchiMate language modelling within a Basis for domain visualisations Modelling relations Basis for Relate to between domains analyses standards Abstraction Levels Object Generic concepts Relation Enterprise architecture Application Process concepts more generic more more specific more Company-specific concepts, standards, e.g. UML, BPMN Layers and Aspects Products & Services Business Functions Organisation Business Information Processes Application Data Applications Technology Technical Infrastructure Passive Behaviour Active structure structure “object” “verb” “subject” Generic Structure at Each Layer External Service Interface Object Internal Behaviour Structure element element Passive Behaviour Active structure structure Similar concepts at each layer make the language easier to learn and more consistent in use (cf. Fred Brooks’ “conceptual integrity”) Notation • Most concepts have two notations: • Icon • Box with icon • Sharp corners = structure • Rounded corners = behaviour • Notation resembles UML and BPMN • to stay close to what architects already know • Relations (arrows etc.) are also mostly taken from existing languages, with a few exceptions Business Functions and Actors business actor ArchiSurance assignment business function Insurance Claim Contracting policies Handling flow Product and Services business actor Customer assignment business role value Insurant Security product Travel Insurance Insurance Claim Customer Claim Policy application registration information payment service service service service business service contract Business Process Customer business actor Insurant business role business service used by Claim Customer Claim registration Information payment service service service business realisation object access Handle Claim Notification Damage occurred Register Accept Valuate Pay event Reject business process triggering junction Interfaces & Services business service Sell Buy Selling product product Seller Buyer business interface Interacties & Collaborations business interaction Complete transaction Sell Buy product product Seller Buyer business collaboration Information Customer aggregation Customer file composition realisation representation Insurance request Insurance policy Damage claim Claim form specialisation Travel insurance Car insurance Home insurance Liability Legal aid policy policy policy insurance policy insurance policy Application Concepts Policy application creation application service service interface application Policy Financial component administration administration Policy Policy Premium creation access collection application service function data object Policy Customer data file data Application Usage by Business Processes Handle claim Notifi- Register Accept Valuate Pay cation Customer Claim Payment administration administration service service service Notifi- CRM Policy Financial cation system administration application data Technology Concepts infrastructure service artifact Database access service Database tables IBM System z Sun Blade Fin. LAN DB2 iPlanet application Database App. server EJBs network system software association device Deployment CRM Customer Financial system data application Database access service Database tables IBM System z Sun Blade Fin. DB2 LAN iPlanet application Database App. server EJBs Derived Relations Weakest link determines Client Insurant composition: association 1 Claim registration access 2 service use 3 Damage claiming process realisation 4 ? Registration assignment 5 aggregation 6 Customer composition 7 administration service CRM system External processes, roles and actors Submit claim Insurant Customer Layered External business services Claim Customer Claims registration information payment Architecture service service service Internal processes, roles and actors Business layer Handle claim ArchiSurance Registration Acceptance Valuation Payment Insurer External application services Customer Claims Payment administration administration service service service Application components and services Customer Claim information information service service Application layer CRM Customer Policy Financial system data administration application External infrastructure services Claim Customer files files service service Infrastructure Customer IBM System z db-tables Blade Technology layer Financial Application DB2 application server EJBs LAN Overview of Core Concepts Meaning Value association Business Business Event service interface Business assignment Business object Business Business process role triggering Business Application Application actor aggregation service interface Data access Application object Application Application function component flow use composition Infrastructure Infrastructure realization service interface Technology System Artifact Device Network software Passive Behaviour Active structure structure Services as Binding Concept Customer External business service Business Internal business service External application service Application Internal application service External infra. service Technology Internal infra. service Example ArchiSurance – Integrating an Insurance Company after a Merger Business Functions Customer information Product information Insurer Product Insurance information Maintaining Maintaining information Intermediary Customer Customer Customer Relations Relations Claims information Customer information Claims Intermediary Contracts Insurance Claims Claim Contracting policies Handling information Insurance Claims policies Claim Money payments Asset Financial Customer’s Management Handling Insurance Bank Money premiums
Load more

Recommended publications
  • A New Golden Age for Computer Architecture: Domain-Specific
    A New Golden Age for Computer Architecture: Domain-Specific Hardware/Software Co-Design, Enhanced Security, Open Instruction Sets, and Agile Chip Development John Hennessy and David Patterson Stanford and UC Berkeley 13 June 2018 https://www.youtube.com/watch?v=3LVeEjsn8Ts 1 Outline Part I: History of Part II: Current Architecture - Architecture Challenges - Mainframes, Ending of Dennard Scaling Minicomputers, and Moore’s Law, Security Microprocessors, RISC vs CISC, VLIW Part III: Future Architecture Opportunities - Domain Specific Languages and Architecture, Open Architectures, Agile Hardware Development 2 IBM Compatibility Problem in Early 1960s By early 1960’s, IBM had 4 incompatible lines of computers! 701 ➡ 7094 650 ➡ 7074 702 ➡ 7080 1401 ➡ 7010 Each system had its own: ▪ Instruction set architecture (ISA) ▪ I/O system and Secondary Storage: magnetic tapes, drums and disks ▪ Assemblers, compilers, libraries,... ▪ Market niche: business, scientific, real time, ... IBM System/360 – one ISA to rule them all 3 Control versus Datapath ▪ Processor designs split between datapath, where numbers are stored and arithmetic operations computed, and control, which sequences operations on datapath ▪ Biggest challenge for computer designers was getting control correct Control Instruction Control Lines Condition?▪ Maurice Wilkes invented the idea of microprogramming to design the control unit of a PC processor* Datapath Registers Inst. Reg. ▪ Logic expensive vs. ROM or RAM ALU Busy? Address Data ▪ ROM cheaper than RAM Main Memory ▪ ROM much faster
    [Show full text]
  • Wake up with CPS 006 Program Design and Methodology I Computer Science and Programming What Is Computer Science? Computer Scienc
    Computer Science and Programming z Computer Science is more than programming ¾ The discipline is called informatics in many countries ¾ Elements of both science and engineering • Scientists build to learn, engineers learn to build Wake up with CPS 006 – Fred Brooks Program Design and Methodology I ¾ Elements of mathematics, physics, cognitive science, music, art, and many other fields z Computer Science is a young discipline Jeff Forbes ¾ Fiftieth anniversary in 1997, but closer to forty years of research and development ¾ First graduate program at CMU (then Carnegie Tech) in http://www.cs.duke.edu/courses/cps006/current 1965 http://www.cs.duke.edu/csed/tapestry z To some programming is an art, to others a science, to others an engineering discipline A Computer Science Tapestry 1.1 A Computer Science Tapestry 1.2 What is Computer Science? Computer Science What is it that distinguishes it from the z Artificial Intelligence thinking machines separate subjects with which it is related? z Scientific Computing weather, cars, heart, modelling What is the linking thread which gathers these z Theoretical CS analyze algorithms, models disparate branches into a single discipline? My answer to these questions is simple --- it is z Computational Geometry theory of animation, 3-D models the art of programming a computer. It is the art z Architecture hardware-software interface of designing efficient and elegant methods of z Software Engineering engineering, science getting a computer to solve problems, z Operating Systems the soul of the machine theoretical or practical, small or large, simple z Graphics from Windows to Hollywood or complex. z Many other subdisciplines C.A.R.
    [Show full text]
  • Reading List
    EECS 101 Introduction to Computer Science Dinda, Spring, 2009 An Introduction to Computer Science For Everyone Reading List Note: You do not need to read or buy all of these. The syllabus and/or class web page describes the required readings and what books to buy. For readings that are not in the required books, I will either provide pointers to web documents or hand out copies in class. Books David Harel, Computers Ltd: What They Really Can’t Do, Oxford University Press, 2003. Fred Brooks, The Mythical Man-month: Essays on Software Engineering, 20th Anniversary Edition, Addison-Wesley, 1995. Joel Spolsky, Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity, APress, 2004. Most content is available for free from Spolsky’s Blog (see http://www.joelonsoftware.com) Paul Graham, Hackers and Painters, O’Reilly, 2004. See also Graham’s site: http://www.paulgraham.com/ Martin Davis, The Universal Computer: The Road from Leibniz to Turing, W.W. Norton and Company, 2000. Ted Nelson, Computer Lib/Dream Machines, 1974. This book is now very rare and very expensive, which is sad given how visionary it was. Simon Singh, The Code Book: The Science of Secrecy from Ancient Egypt to Quantum Cryptography, Anchor, 2000. Douglas Hofstadter, Goedel, Escher, Bach: The Eternal Golden Braid, 20th Anniversary Edition, Basic Books, 1999. Stuart Russell and Peter Norvig, Artificial Intelligence: A Modern Approach, 2nd Edition, Prentice Hall, 2003.
    [Show full text]
  • ESD.33 -- Systems Engineering Session #1 Course Introduction
    ESD.33 -- Systems Engineering Session #4 Axiomatic Design Decision-Based Design Summary of Frameworks Phase Dan Frey Follow-up on Session #3 • Mike Fedor - Your lectures and readings about Lean Thinking have motivated me to re-read "The Goal" by Eliyahu M. Goldratt • Don Clausing – Remember that although set-based design seems to explain part of Toyota’s system, it also includes a suite of other powerful tools (QFD, Robust Design) • Denny Mahoney – What assumptions are you making about Ops Mgmt? Plan for the Session • Why are we doing this session? • Axiomatic Design (Suh) • Decision-Based Design (Hazelrigg) • What is rationality? • Overview of frameworks • Discussion of Exam #1 / Next steps Claims Made by Nam Suh • “A general theory for system design is presented” • “The theory is applicable to … large systems, software systems, organizations…” • “The flow diagram … can be used for many different tasks: design, construction, operation, modification, … maintenance … diagnosis …, and for archival documentation.” • “Design axioms were found to improve all designs without exceptions or counter-examples… When counter-examples or exceptions are proposed, the author always found flaws in the arguments.” Claims Made by Hazelrigg • “We present here … axioms and … theorems that underlie the mathematics of design” • “substantially different from … conventional … eng design” • “imposes severe conditions on upon design methodologies” • “all other measures are wrong” • “apply to … all fields of engineering … all products, processes, and services,
    [Show full text]
  • Compsci 6 Programming Design and Analysis
    CompSci 6 Programming Design and Analysis Robert C. Duvall http://www.cs.duke.edu/courses/cps006/fall04 http://www.cs.duke.edu/~rcd CompSci 6 : Spring 2005 1.1 What is Computer Science? Computer science is no more about computers than astronomy is about telescopes. Edsger Dijkstra Computer science is not as old as physics; it lags by a couple of hundred years. However, this does not mean that there is significantly less on the computer scientist's plate than on the physicist's: younger it may be, but it has had a far more intense upbringing! Richard Feynman http://www.wordiq.com CompSci 6 : Spring 2005 1.2 Scientists and Engineers Scientists build to learn, engineers learn to build – Fred Brooks CompSci 6 : Spring 2005 1.3 Computer Science and Programming Computer Science is more than programming The discipline is called informatics in many countries Elements of both science and engineering Elements of mathematics, physics, cognitive science, music, art, and many other fields Computer Science is a young discipline Fiftieth anniversary in 1997, but closer to forty years of research and development First graduate program at CMU (then Carnegie Tech) in 1965 To some programming is an art, to others a science, to others an engineering discipline CompSci 6 : Spring 2005 1.4 What is Computer Science? What is it that distinguishes it from the separate subjects with which it is related? What is the linking thread which gathers these disparate branches into a single discipline? My answer to these questions is simple --- it is the art of programming a computer.
    [Show full text]
  • The Computer Scientist As Toolsmith—Studies in Interactive Computer Graphics
    Frederick P. Brooks, Jr. Fred Brooks is the first recipient of the ACM Allen Newell Award—an honor to be presented annually to an individual whose career contributions have bridged computer science and other disciplines. Brooks was honored for a breadth of career contributions within computer science and engineering and his interdisciplinary contributions to visualization methods for biochemistry. Here, we present his acceptance lecture delivered at SIGGRAPH 94. The Computer Scientist Toolsmithas II t is a special honor to receive an award computer science. Another view of computer science named for Allen Newell. Allen was one of sees it as a discipline focused on problem-solving sys- the fathers of computer science. He was tems, and in this view computer graphics is very near especially important as a visionary and a the center of the discipline. leader in developing artificial intelligence (AI) as a subdiscipline, and in enunciating A Discipline Misnamed a vision for it. When our discipline was newborn, there was the What a man is is more important than what he usual perplexity as to its proper name. We at Chapel Idoes professionally, however, and it is Allen’s hum- Hill, following, I believe, Allen Newell and Herb ble, honorable, and self-giving character that makes it Simon, settled on “computer science” as our depart- a double honor to be a Newell awardee. I am pro- ment’s name. Now, with the benefit of three decades’ foundly grateful to the awards committee. hindsight, I believe that to have been a mistake. If we Rather than talking about one particular research understand why, we will better understand our craft.
    [Show full text]
  • Computer Science and Global Economic Development: Sounds Interesting, but Is It Computer Science?
    Computer Science and Global Economic Development: Sounds Interesting, but is it Computer Science? Tapan S. Parikh UC Berkeley School of Information Berkeley, CA, USA [email protected] OVERVIEW interventions from the bottom up, usually applying experi- Computer scientists have a long history of developing tools mental methods [1]. This includes prominent use of ICTs, useful for advancing knowledge and practice in other disci- both as the focus of new interventions (mobile phones for plines. More than fifty years ago, Grace Hopper said the making markets more efficient [6], digital cameras to moni- role of computers was “freeing mathematicians to do math- tor teacher attendance [2]), and as tools for understanding ematics.” [5] Fred Brooks referred to a computer scientist as their impact (PDAs and smartphones to conduct extensive a toolsmith, , making “things that do not themselves satisfy in-field surveys [8]). It is a wonderfully timely moment for human needs, but which others use in making things that computer scientists to engage with the state-of-the-art in enrich human living.” [4]. Computational biologists have ap- development research and practice. plied algorithmic techniques to process and understand the deluge of data made possible by recent advances in molecu- lar biology. WHY ACADEMIA? WHY CS? The proper way to approach this kind of research has never been clear within Computer Science. The refrain“Sounds Why do this work in academia, and within the disci- interesting, but is it Computer Science?” is frequently heard. pline of Computer Science? There are several motivations. In this paper I argue that it is crucial take an expansive Academia allows us to be more free, and take greater risks, view of what Computer Science is.
    [Show full text]
  • Industrial Product-Service Systems Engineering
    Download Workshop Material https://tinyurl.com/Jacaranda18 www.omilab.org Advanced Enterprise Architecture Modeling Support through Metamodeling Platforms Dr. Dominik Bork, University of Vienna [email protected] @BorkDominik University of Pretoria, Pretoria, September 25th 2018 www.omilab.org Outline • Welcome & Introduction • Metamodeling with ADOxx • Enterprise Architecture Management • ArchiMate 3.0.1 and TOGAF • EAM Case Study • Discussion & Evaluation www.omilab.org 3 WELCOME & INTRODUCTION www.omilab.org 4 Who we are • Dr. Dominik Bork Post-doctoral Researcher University of Vienna, RG Knowledge Engineering [email protected] Project Team: • University of Vienna – Prof. Dr. Dimitris Karagiannis – Dr. Dominik Bork – Elena-Teodora Miron, MSc – Anna Sumereder, BA • University of Pretoria – Prof. Dr. Alta van der Merwe – Prof. Dr. Aurona Gerber – Dr. Sunet Eybers – Dr. Phil van Deventer www.omilab.org 5 The Research Project • Austria - South Africa Scientific & Technological Cooperation Program • Goal: – Extend the reach of ArchiMate for EA management – Involve experts and practitioners of EAM for requirements engineering and evaluation of the modelling tool – Develop an open modeling tool for advanced EAM – Knowledge transfer through workshops, papers, and tutorials – Provide teaching and training material • Austrian project lead: – University of Vienna, Prof. Dr. Dimitris Karagiannis • South Africa project lead: – University of Pretoria, Porf. Dr. Alta van der Merwe • Duration: Jan. 2017 – Dec. 2018 www.omilab.org University
    [Show full text]
  • Systems Development Life Cycle
    Systems Development Life Cycle From Wikipedia, the free encyclopedia Jump to: navigation, search For other uses, see SDLC (disambiguation). Model of the Systems Development Life Cycle with the Maintenance bubble highlighted. The Systems Development Life Cycle (SDLC), or Software Development Life Cycle in systems engineering, information systems and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems. In software engineering the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system[1]: the software development process. Contents y 1 Overview y 2 History y 3 Systems development phases o 3.1 Requirements gathering and analysis o 3.2 Design o 3.3 Build or coding o 3.4 Testing o 3.5 Operations and maintenance y 4 Systems development life cycle topics o 4.1 Management and control o 4.2 Work breakdown structured organization o 4.3 Baselines in the SDLC o 4.4 Complementary to SDLC y 5 Strengths and weaknesses y 6 See also y 7 References y 8 Further reading y 9 External links [edit] Overview Systems and Development Life Cycle (SDLC) is a process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.[2] Computer systems are complex and often (especially with the recent rise of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors.
    [Show full text]
  • Teaching How to Engineer Software Teaching How To
    CSEE&T-03 Madrid, Spain, 20 March 2003 Teaching how to engineer software CSEE&T-03 Keynote Dieter Rombach University of Kaiserslautern Computer Fraunhofer Institute Science Department for Experimental Software Software Engineering Chair Engineering (IESE) Kaiserslautern, Germany Kaiserslautern, Germany Slide 0 CSEE&T-03 Madrid, Spain, 20 March 2003 Focus & Message • Teaching the engineering of software requires –Communicating existing proven best practices as a basis –Concentration on first-order principles –Practice and experience of benefits –Analysis before construction Slide 1 1 CSEE&T-03 Madrid, Spain, 20 March 2003 Contents • (Software) Engineering • Practice of software engineering • Today’s typical teaching curricula • Some (innovative?) Ideas for adequate teaching • Proven Best Practices • (Graduate) SE Curriculum at Kaiserslautern • Summary & Outlook Slide 2 CSEE&T-03 Madrid, Spain, 20 March 2003 (Software) Engineering (Expectations) • Engineering requires the ability to – Choose an appropriate approach to solve a given problem à No optimal solution exists! – Assure adherence to best (proven) practices (engineering principles) à Ignorance violates due diligence! – Apply the approach in a predictable way à Can customize to goals & characteristics! – Repeat results à Continuous success & improvement! – Guarantee success before regular use à Works first time! – etc. Slide 3 2 CSEE&T-03 Madrid, Spain, 20 March 2003 (Software) Engineering (Special Characteristics) • Software Engineering –Focuses on development (non- deterministic
    [Show full text]
  • Arxiv:2106.11534V1 [Cs.DL] 22 Jun 2021 2 Nanjing University of Science and Technology, Nanjing, China 3 University of Southampton, Southampton, U.K
    Noname manuscript No. (will be inserted by the editor) Turing Award elites revisited: patterns of productivity, collaboration, authorship and impact Yinyu Jin1 · Sha Yuan1∗ · Zhou Shao2, 4 · Wendy Hall3 · Jie Tang4 Received: date / Accepted: date Abstract The Turing Award is recognized as the most influential and presti- gious award in the field of computer science(CS). With the rise of the science of science (SciSci), a large amount of bibliographic data has been analyzed in an attempt to understand the hidden mechanism of scientific evolution. These include the analysis of the Nobel Prize, including physics, chemistry, medicine, etc. In this article, we extract and analyze the data of 72 Turing Award lau- reates from the complete bibliographic data, fill the gap in the lack of Turing Award analysis, and discover the development characteristics of computer sci- ence as an independent discipline. First, we show most Turing Award laureates have long-term and high-quality educational backgrounds, and more than 61% of them have a degree in mathematics, which indicates that mathematics has played a significant role in the development of computer science. Secondly, the data shows that not all scholars have high productivity and high h-index; that is, the number of publications and h-index is not the leading indicator for evaluating the Turing Award. Third, the average age of awardees has increased from 40 to around 70 in recent years. This may be because new breakthroughs take longer, and some new technologies need time to prove their influence. Besides, we have also found that in the past ten years, international collabo- ration has experienced explosive growth, showing a new paradigm in the form of collaboration.
    [Show full text]
  • Archimate® 2.1 – a Pocket Guide
    Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see www.vanharen.net ARCHIMATE® 2.1 – A POCKET GUIDE Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see www.vanharen.net The Open Group Publications available from Van Haren Publishing e TOGAF Series: TOGAF® Version 9.1 TOGAF® Version 9.1 – A Pocket Guide TOGAF® 9 Foundation Study Guide, 3rd Edition TOGAF® 9 Certi ed Study Guide, 3rd Edition e Open Group Series: Cloud Computing for Business – e Open Group Guide ArchiMate® 2.1 – A Pocket Guide ArchiMate® 2.1 Speci cation ArchiMate® 2 Certi cation – Study Guide e Open Group Security Series: Open Information Security Management Maturity Model (O-ISM3) Open Enterprise Security Architecture (O-ESA) Risk Management – e Open Group Guide All titles are available to purchase from: www.opengroup.org www.vanharen.net and also many international and online distributors. Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see www.vanharen.net ArchiMate® 2.1 A POCKET GUIDE Copyright protected. Use is for Single Users only via a VHP Approved License. For information and printed versions please see www.vanharen.net Title: ArchiMate® 2.1 – A Pocket Guide Series: The Open Group Series A Publication of: The Open Group Author: Andrew Josey et al. Publisher: Van Haren Publishing, Zaltbommel, www.vanharen.net ISBN Hard copy: 978 94 018 0001
    [Show full text]