The ArchiSurance Case Study is a fictitious example developed to illustrate the use of
the ArchiMate® modeling language in the context of the TOGAF® framework. The
Case Study concerns the insurance company ArchiSurance, which has been formed as
the result of a merger of three previously independent companies. The Case Study
describes the baseline architecture of the company and then a number of change
scenarios.
This Case Study is required to be used as an example throughout accredited
ArchiMate training courses. However, it is not part of the definition of TOGAF. This
work supports The Open Group vision of Boundaryless Information Flow by
illustrating the combined use of the TOGAF and ArchiMate standards for consistent
representation of architectural information across diverse organizations, systems, and
initiatives.
This Case Study demonstrates the value of the ArchiMate® 2.1 modeling language for planning and expressing complex business transformation. The Case Study is about a fictitious manufacturer named ArchiMetal. Through high-level architecture modeling, the ArchiMate language illuminates the coherence between an organization, and its processes, applications, and infrastructure. This Case Study presents examples of ArchiMate models that can be elaborated as necessary for analysis, communication, decision support, and implementation.
Value analysis with Value Stream and Capability modelingCOMPETENSIS
The new Archimate 3.1 has improved the strategy layer with major modeling objects related to value analysis: value stream and capability.
These objects are linked and answer major questions :
- [VALUE STREAM] What value do we deliver to customers ? What value do we want to deliver to customers ? This is the enterprise business model.
- [CAPABILITY] What operational model do we need to deliver value ? The capability model describes the operational model required to deliver value to customers.
You cannot succeed to transform a business model, enterprise activities without considering Value Stream & Capability analysis. Technology considerations are necessary but not sufficient.
Feel free to contact if you wish to get more support with your transformation projet.
In this presentation Bruno Vandenborre, The Open Group accredited trainer at Real IRM, explores the purpose and utility of the new version of the ArchiMate standard. As well as a look at the updates and changes to the new version, he discusses the various responses and critiques to ArchiMate, and provide insight into how ArchiMate benefits the South African market.
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
This Case Study demonstrates the value of the ArchiMate® 2.1 modeling language for planning and expressing complex business transformation. The Case Study is about a fictitious manufacturer named ArchiMetal. Through high-level architecture modeling, the ArchiMate language illuminates the coherence between an organization, and its processes, applications, and infrastructure. This Case Study presents examples of ArchiMate models that can be elaborated as necessary for analysis, communication, decision support, and implementation.
Value analysis with Value Stream and Capability modelingCOMPETENSIS
The new Archimate 3.1 has improved the strategy layer with major modeling objects related to value analysis: value stream and capability.
These objects are linked and answer major questions :
- [VALUE STREAM] What value do we deliver to customers ? What value do we want to deliver to customers ? This is the enterprise business model.
- [CAPABILITY] What operational model do we need to deliver value ? The capability model describes the operational model required to deliver value to customers.
You cannot succeed to transform a business model, enterprise activities without considering Value Stream & Capability analysis. Technology considerations are necessary but not sufficient.
Feel free to contact if you wish to get more support with your transformation projet.
In this presentation Bruno Vandenborre, The Open Group accredited trainer at Real IRM, explores the purpose and utility of the new version of the ArchiMate standard. As well as a look at the updates and changes to the new version, he discusses the various responses and critiques to ArchiMate, and provide insight into how ArchiMate benefits the South African market.
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
Wilbert Kraan introduces Archimate and Enterprise Architecture modelling.
Presented at the first JISC Emerging Practices workshop (2012/03/29).
http://emergingpractices.jiscinvolve.org/wp/doing-ea-workshop/
ArchiMate 3.0: A New Standard for ArchitectureIver Band
This keynote presentation from the July 2016 Open Group Austin Conference introduces the new version of the ArchiMate standard. ArchiMate 3.0 extends the language with various concepts that help enterprise architects tackle challenges in digital transformation and business change. This major new version introduces explicit support for capability-based planning, and improves linkage between business strategy and all architecture layers. ArchiMate 3.0 also enables modelers to describe the Internet of Things and the systems of the physical world, such as manufacturing and logistics. In addition, the new version supports more compact and intuitive visual models. This presentation includes examples that use these improvements and demonstrates how architects can benefit from them.
Modeling Big Data with the ArchiMate 3.0 LanguageIver Band
Health care enterprises use big data methods and technologies to gain insights for improving the efficacy, efficiency, and accessibility of their services. Effective big data initiatives require shared understanding among diverse stakeholders of business challenges and the often complex architectures required to address them. Enterprise and solution architects can use the ArchiMate language to build this understanding with compelling visual models.
This presentation introduces the ArchiMate 3.0 language, and uses it to explore the US National Institute of Standards and Technology (NIST) Big Data Reference Architecture (NBDRA), and to present a health care case study based on the NBDRA. Participants will learn how to use the ArchiMate 3.0 language, in alignment with the TOGAF framework, to propose, justify and plan big data initiatives, and to guide their successful implementation.
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
What Can We Do With The ArchiMate Language?Iver Band
Last year, the Open Group released version 3.0 of the ArchiMate® standard, which provides a language with concepts for describing enterprise and solution architectures, a framework for organizing these concepts, a graphical notation for these concepts, and recommendations for viewpoints, which are visualization templates that address the concerns of particular stakeholders. The standard is public and free for end users. It can be extended through specialization of its concepts and relationships, and is supported by an increasing number of tools, consultancies and training organizations.
We use a fictitious—but realistic—case study to describe what we can do with the ArchiMate language. Each of the sections in this article presents one or more views of an ArchiMate model that tells a story about the collection and analysis of Big Data to create business value. Big Data consists of datasets that cannot be handled efficiently with traditional centralized data architectures due to their extensive volume, variety, velocity and variability. These characteristics demand scalable architectures for efficient storage, manipulation and analysis.
Presentation given by Wilbert Kraan at the second JISC Emerging Practices workshop (2012/07/03). Provides a basic overview of ArchiMate.
http://emergingpractices.jiscinvolve.org/wp/doing-ea-workshop-2/
Overview of the IT4IT tooling market in 2022.
Key trends in the IT4IT / DevOps tooling market are:
- Strategic portfolio management / portfolio backlog management (scaling agile on the enterprise level integrating with Enterprise architecture and Application / Product Portfolio Management)
- On-line collaboration & communication tools supporting team of team planning, problem solving, etc.
- Value stream management (an emerging tooling category) providing visibility across the end-to-end IT value streams
- Multi-cloud discovery & visibility on usage, costs and compliance
- Integrating DevOps tool chain (e.g. CICD pipeline) with the ITSM platform and CMDB
- Integrating security, risk and compliance management into the DevOps tool chain
- AIOps and observability management, consoliding metrics, logs, events mapped to a real-time service model
- Security operations, integrating security monitoring, vulnerability scanning, etc. into end-to-end detect to correct value streams
- Enterprise Service Management (ITSM vendors providing omni-channel services across IT, HR, Facilities, Finance, etc.)
- Leveraging AI/ML in various capabilities such test management, security operations, incident management, etc.
- Sustainability management integrated in IRM/GRC platforms
And last but not least:
- Service / Product portfolio management (managing the portfolio of service/applications, supporting product centric operating models, linked to business capabilities, product owners and teams)
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Using the TOGAF® 9.1 Architecture Content Framework with the ArchiMate® 2.0 M...Iver Band
A thorough comparison of the ArchiMate 2.0 metamodel with the Content Metamodel
from the TOGAF 9.1 Architecture Content Framework reveals that these two Open
Group standards are highly compatible. The ArchiMate 2.0 visual modeling language
is therefore well suited for architecture initiatives guided by the TOGAF 9.1 standard,
and this White Paper provides both theoretical preparation and practical guidance for
users of the ArchiMate language working on such initiatives.
This work supports The Open Group vision of Boundaryless Information Flow by
further enabling the combined use of the TOGAF standard and the ArchiMate
modeling language for consistent representation of architectural information across
diverse organizations, systems, and initiatives.
Wilbert Kraan introduces Archimate and Enterprise Architecture modelling.
Presented at the first JISC Emerging Practices workshop (2012/03/29).
http://emergingpractices.jiscinvolve.org/wp/doing-ea-workshop/
ArchiMate 3.0: A New Standard for ArchitectureIver Band
This keynote presentation from the July 2016 Open Group Austin Conference introduces the new version of the ArchiMate standard. ArchiMate 3.0 extends the language with various concepts that help enterprise architects tackle challenges in digital transformation and business change. This major new version introduces explicit support for capability-based planning, and improves linkage between business strategy and all architecture layers. ArchiMate 3.0 also enables modelers to describe the Internet of Things and the systems of the physical world, such as manufacturing and logistics. In addition, the new version supports more compact and intuitive visual models. This presentation includes examples that use these improvements and demonstrates how architects can benefit from them.
Modeling Big Data with the ArchiMate 3.0 LanguageIver Band
Health care enterprises use big data methods and technologies to gain insights for improving the efficacy, efficiency, and accessibility of their services. Effective big data initiatives require shared understanding among diverse stakeholders of business challenges and the often complex architectures required to address them. Enterprise and solution architects can use the ArchiMate language to build this understanding with compelling visual models.
This presentation introduces the ArchiMate 3.0 language, and uses it to explore the US National Institute of Standards and Technology (NIST) Big Data Reference Architecture (NBDRA), and to present a health care case study based on the NBDRA. Participants will learn how to use the ArchiMate 3.0 language, in alignment with the TOGAF framework, to propose, justify and plan big data initiatives, and to guide their successful implementation.
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Stepping-stones of enterprise-architecture: Process and practice in the real...Tetradian Consulting
What do we do when we’re doing enterprise architecture? What issues do we tackle, in what sequence, for what business reasons, for what business value? And how do we get results fast? This presentation describes how to adapt the Architectural Development Method (ADM) from The Open Group Architecture Framework (TOGAF) for use in all types of enterprise architecture - for IT and beyond - and at all architecture maturity-levels.
[Presentation at TOGAF Conference, London, April 2009. Applies to TOGAF versions 8.1 and 9. Copyright (c) Tetradian Consulting 2009]
What Can We Do With The ArchiMate Language?Iver Band
Last year, the Open Group released version 3.0 of the ArchiMate® standard, which provides a language with concepts for describing enterprise and solution architectures, a framework for organizing these concepts, a graphical notation for these concepts, and recommendations for viewpoints, which are visualization templates that address the concerns of particular stakeholders. The standard is public and free for end users. It can be extended through specialization of its concepts and relationships, and is supported by an increasing number of tools, consultancies and training organizations.
We use a fictitious—but realistic—case study to describe what we can do with the ArchiMate language. Each of the sections in this article presents one or more views of an ArchiMate model that tells a story about the collection and analysis of Big Data to create business value. Big Data consists of datasets that cannot be handled efficiently with traditional centralized data architectures due to their extensive volume, variety, velocity and variability. These characteristics demand scalable architectures for efficient storage, manipulation and analysis.
Presentation given by Wilbert Kraan at the second JISC Emerging Practices workshop (2012/07/03). Provides a basic overview of ArchiMate.
http://emergingpractices.jiscinvolve.org/wp/doing-ea-workshop-2/
Overview of the IT4IT tooling market in 2022.
Key trends in the IT4IT / DevOps tooling market are:
- Strategic portfolio management / portfolio backlog management (scaling agile on the enterprise level integrating with Enterprise architecture and Application / Product Portfolio Management)
- On-line collaboration & communication tools supporting team of team planning, problem solving, etc.
- Value stream management (an emerging tooling category) providing visibility across the end-to-end IT value streams
- Multi-cloud discovery & visibility on usage, costs and compliance
- Integrating DevOps tool chain (e.g. CICD pipeline) with the ITSM platform and CMDB
- Integrating security, risk and compliance management into the DevOps tool chain
- AIOps and observability management, consoliding metrics, logs, events mapped to a real-time service model
- Security operations, integrating security monitoring, vulnerability scanning, etc. into end-to-end detect to correct value streams
- Enterprise Service Management (ITSM vendors providing omni-channel services across IT, HR, Facilities, Finance, etc.)
- Leveraging AI/ML in various capabilities such test management, security operations, incident management, etc.
- Sustainability management integrated in IRM/GRC platforms
And last but not least:
- Service / Product portfolio management (managing the portfolio of service/applications, supporting product centric operating models, linked to business capabilities, product owners and teams)
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
Using the TOGAF® 9.1 Architecture Content Framework with the ArchiMate® 2.0 M...Iver Band
A thorough comparison of the ArchiMate 2.0 metamodel with the Content Metamodel
from the TOGAF 9.1 Architecture Content Framework reveals that these two Open
Group standards are highly compatible. The ArchiMate 2.0 visual modeling language
is therefore well suited for architecture initiatives guided by the TOGAF 9.1 standard,
and this White Paper provides both theoretical preparation and practical guidance for
users of the ArchiMate language working on such initiatives.
This work supports The Open Group vision of Boundaryless Information Flow by
further enabling the combined use of the TOGAF standard and the ArchiMate
modeling language for consistent representation of architectural information across
diverse organizations, systems, and initiatives.
An Introduction to the ArchiMate 3.0 SpecificationIver Band
This White Paper provides an overview of the ArchiMate® 3.0 Specification, an Open Group Standard, including the role of the language in Enterprise Architecture, a description of its structure and content, and a summary of the new features of this major update.
The ArchiMate 3.0 Specification is a major update to the ArchiMate 2.1 Specification, and was published as an Open Group Standard in June 2016. New features included in Version 3.0 include elements for modeling the enterprise at a strategic level, such as capability, resource, and outcome. It also includes support to model the physical world of materials and equipment. Furthermore, the consistency and structure of the language have been improved, definitions have been aligned with other standards, and its usability has been enhanced in various other ways.
How the ArchiMate Modeling Standard Helps Enterprise Architects Deliver Grea...Dana Gardner
Transcript of a discussion on how companies and governments can better produce rapid innovation and manage complexity across their IT and business operations.
O novo Portfolio de formatos IAB (IAB New Standard Ad unit portfolio) pode contar agora com formatos de Rich Media, Video, Audio, Native Ads e VR Realidade Virtual, 360º e Emoji and Sticker content.
In this presentation Michael Payne debates the merits of placing Business Architecture within an organisation’s Business, IT or Enterprise Architecture departments. He examines some of the options available to organisations starting out with Business Architecture, and touches on Business Architecture engagement models. In addition, Michael provides a sneak peak into the new developments in the Open-BA Framework.
In this presentation Michael Payne debates the merits of placing Business Architecture within an organisation’s Business, IT or Enterprise Architecture departments. He examines some of the options available to organisations starting out with Business Architecture, and touches on Business Architecture engagement models. In addition, Michael provides a sneak peak into the new developments in the Open-BA Framework.
Instant cube : Generating OLAP cube using C# Ramy Frikha
This report contains a presentation for my 2 internships that i passed in the summer of 2018
* 1st Internship : Development of a desktop application called "Instant Cube" to generate a Multi-Dimensional Cube using C#
* 2nd internship : Development of a BI solution for a french company within Proximind . Using MS BI : SSIS , SSAS , SSRS , power BI
SharePoint Wiki Feasibility Report (Draft) - Travis Barker.pdfInnovate Vancouver
A feasibility study (draft) report on using SharePoint to build a SharePoint Wiki, similar to confluence, for the IT Department.
Knowledge Management in Sharepoint - Article:
https://innovatevancouver.org/2022/10/10/knowledge-management-in-sharepoint/
Travis Barker, MPA GCPM
Consulting@innovatevancouver.org
http://innovatevancouver.org
INCOSE ASEC 2010. Human Factors - On the Right TRAK? Companion PaperNic Plum
Companion paper to presentation given at the UK INCOSE Annual Systems Engineering Conference (ASEC) 2010 at Heythrop Park, Oxfordshire by Chris Lowe (Liv Systems Ltd.) and Nic Plum (Eclectica Systems Ltd.).
http://www.incoseonline.org.uk/Program_Files/Calendar/Show_Event_Details.aspx?CatID=Events&EventID=138
It describes the application of human factors/user-centred design in unusual places - in the design of an architecture framework (TRAK) and the use of TRAK for human factors tasks.
Enhancing Organizational Performance by Creating a Culture of Stewardship wit...Iver Band
Genesis Financial Solutions (GFS), a leading nonprime consumer credit platform, has created a culture of stewardship with LeanIX. Stewardship at GFS includes acquiring, creating, sustaining, enhancing, and retiring assets. Stewards are the primary decision-makers for their assigned assets. They collaborate with consumer lending and technology leaders to guide the evolution of business capabilities, applications, and IT components.
Chronic Absenteeism Rate Prediction: A Data Science Case StudyIver Band
This was my capstone project for the Coursera Advanced Data Science with IBM Specialization. It demonstrates all phases of a data science project, including modeling with a neural network and a decision tree ensemble using Keras and scikit-learn.
The ArchiMate Language for Enterprise and Solution ArchitectureIver Band
The ArchiMate standard provides:
* A language with concepts to describe architectures
* A framework to organize these concepts
* A graphical notation for these concepts
* Guidance on visualizations for different stakeholders
* An open standard maintained by The Open Group
This presentation illustrates the value of ArchiMate modeling with a Big Data case study.
Cloud architecture with the ArchiMate LanguageIver Band
Today's commercial cloud platforms enable the migration of on-premises architectures to environments that offer increased flexibility, resilience, and security. These platforms also offer innovative managed services that enable architects, designers and developers to focus on business logic and user experience rather than underlying infrastructure.
Enterprise Architects can use the ArchiMate language to guide the use of cloud platforms to meet business and technical goals. This presentation models an architecture based on a leading cloud platform. The model uses all layers and aspects of the ArchiMate language as well as its customization mechanisms, which express vendor-specific platform elements and relationships. It provides an appreciation of the depth and versatility of the ArchiMate 3.0 language, and an introduction to developing architectures that use commercial cloud platforms.
Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate...Iver Band
Today's enterprise web portals are complex beasts. Leading portals deliver fresh and relevant personalized experiences to multiple audiences, each with their own branding, content, and interactions. They aggregate content from multiple sources and present it using components, some of which are are reused across audiences. They make users productive by interacting with core transactional systems, and secure themselves with role-based access control. Web portals require careful management to ensure they deliver robust, personal, agile, and sustainable experiences in the face of continuous change.
The ArchiMate language is ideal for elucidating the structure and function of web portal applications and infrastructure, and linking them to the consumer experiences and internal operations they support. Modelers can also link critical business stakeholders, drivers, and goals to requirements for new investments, link these requirements to changes in applications and infrastructure that satisfy them, and show how these changes can be implemented over time.
Join practicing Enterprise Architect and ArchiMate Forum Vice Chair Iver Band and portal expert Ryan Kennedy to learn how to use the TOGAF Framework and the ArchiMate language to depict complex architectures and the changes they require.
An Introduction to Enterprise Architecture Visual Modeling With The ArchiMate...Iver Band
A half-day introduction to the ArchiMate language, including core concepts, a visual Overview, and a case study. Introduces the entire language, including the Business, Application and Technology layers as well as the Motivation and implementation and Migration extensions. Ideal for enterprise and solution architects and other architecture contributors.
The case study uses the free Archi tool, and includes download instructions. Those interested in learning the language can attempt each case study exercise using Archi, and flip to the next slide to check their work.
Using the TOGAF® 9.1 Framework with the ArchiMate® 2.1 Modeling LanguageIver Band
This White Paper describes the TOGAF®
9.1 framework and the ArchiMate®
2.1 modeling language, showing at a high level how these two open standards from The Open Group can
be used together.
The main observations are:
The TOGAF framework and the ArchiMate language overlap in their use of viewpoints, and the concept of an underlying common repository of architectural artifacts and models; i.e., they have a firm common foundation.
The two standards complement each other with respect to the definition of an architecture development process and the definition of an Enterprise Architecture modeling language.
The ArchiMate 2.1 standard supports modeling of the architectures throughout the phases of the TOGAF Architecture Development Method (ADM).
The combined use of the TOGAF framework with the ArchiMate modeling language can support better communication with stakeholders inside and outside organizations supporting The Open Group vision of Boundaryless Information Flow™.
Always-On Services for Consumer Web, Mobile and the Internet of ThingsIver Band
US healthcare payers must develop innovative consumer businesses while continuing their core business operations
This requires a bimodal IT architecture with an Adaptive Service Layer between consumer and core business applications
This layer must enable reliable, scalable and reusable services
These Always-On services must protect core business systems and data
Organizations must understand service usage to build successful consumer apps
An Adaptive Service Layer can consist of an API Platform, BaaS and ESB
The Read, Publish, and Subscribe patterns enable a broad range of services
The Pass-Through pattern gives existing services added reusability, visibility and security
An Enterprise Repository can facilitate service reuse
Standards-based Enterprise Architecture can persuasively link business strategies to specific IT investments
Effective Strategy Execution with Capability-Based Planning, Enterprise Arch...Iver Band
The difficulty of strategy execution should not be underestimated
Capability-based planning helps make strategy concrete
Enterprise architecture closes the remainder of this gap, and ensures alignment and coherence
Enterprise portfolio management allows managing large enterprise landscapes based on business value
ArchiMate models tie it all together, providing a clear line of sight from strategy definition to realization
Powerful tool support makes this a strong combination!
Thought Leader Interview: Atefeh Riazi on the Past, Present and Future of Met...Iver Band
Atefeh Riazi, currently Assistant Secretary-General and Chief Information Technology Officer at the United Nations, has also led IT at the advertising agency Ogilvy and Mather, the New York City Housing Authority, and the New York City Transit Authority (NYCTA), an agency of the New York State Metropolitan Transportation Authority (MTA). This interview focuses on Ms. Riazi's work at the MTA leading the implementation of MetroCard, a fare collection system that serves 8.5 million daily commuters. MetroCard collects fares on bus and rail transit systems operated by the MTA and other government agencies serving New York City and surrounding counties in New York, New Jersey and Connecticut.
Thought Leader Interview: Atefeh Riazi on the Past, Present and Future of Met...Iver Band
Atefeh Riazi, currently Assistant Secretary-General and Chief Information Technology Officer at the United Nations, has also led IT at the advertising agency Ogilvy and Mather, the New York City Housing Authority, and the New York City Transit Authority (NYCTA), an agency of the New York State Metropolitan Transportation Authority (MTA). This interview focuses on Ms. Riazi's work at the MTA leading the implementation of MetroCard, a fare collection system that serves 8.5 million daily commuters. MetroCard collects fares on bus and rail transit systems operated by the MTA and other government agencies serving New York City and surrounding counties in New York, New Jersey and Connecticut.
Modeling Enterprise Risk Management and Security with the ArchiMate LanguageIver Band
Enterprise Architects can use the ArchiMate® language to model Enterprise Risk Management (ERM) and security concepts and relationships. This widely accepted open standard provides the modeling constructs to describe and interconnect business and technical architectures. Applying the ArchiMate language to represent risk and security concepts results in the ideal vehicle to consider these aspects in an integral way. The ArchiMate language fits well with other Enterprise Architecture (EA) frameworks and standards, such as the TOGAF® standard and the Zachman framework, as well as enterprise security management frameworks such as the Sherwood Applied Business Security Architecture (SABSA).
Through its Motivation extension, the ArchiMate language makes it possible to link control measures to security requirements, principles, and goals, as well as to the results of a risk analysis. On the other hand, ArchiMate models can be linked to design languages for business processes and IT solutions such as BPMN and UML. These linkages enable precise gathering of a set of broadly accepted risk and security concepts, analysis of their semantics, and consensus regarding the most important ones of the full scope of enterprise risk.
This White Paper, a joint project of The Open Group ArchiMate Forum and The Open Group Security Forum, demonstrates this approach and identifies opportunities for future work that would enhance it.
Guiding Agile Solution Delivery with the ArchiMate LanguageIver Band
Solution Architects can develop clear and actionable guidance for Agile development teams using the ArchiMate language. They can rapidly leverage Enterprise Architectures, and specify just the right amount of detail to constrain the solution while leveraging developers' expertise, initiative and creativity. As solutions are developed, architectural models can be enriched with additional implementation details, enabling Solution Architects to contribute high-quality baseline architectures and reusable building blocks to their enterprise repositories. This presentation prepares Enterprise and Solution Architects to lead Agile implementation of their architectures and roadmaps.
Enterprise Architecture with the Zachman Framework and the Archimate LanguageIver Band
The ArchiMate visual modeling language enables modelers to create views for all columns and rows of the Zachman Framework. This brief presentation shows how the language and framework can be used together for business, data, application and technology architecture.
Book Review: Making Technology Investments ProfitableIver Band
In “Making Technology Investments Profitable”,
management consultant Jack Keen diagnoses and treats
business and IT leaders that expect value but let it slip
away. “On-value” is the essential companion to “on-time”
and “on-budget”. Too often, leaders choose inferior
investments, assume that on-time and on-budget
programs1 are also on-value, and are forced to shut
down programs after they disrupt or disappoint their
intended beneficiaries.
From Capability-Based Planning to Competitive Advantage: Assembling Your Bus...Iver Band
Many organizations are investing in capability-based planning, portfolio management, architecture and agile development processes. While they derive value from each practice, many struggle with getting all of them to work together. In rapidly evolving industries such as healthcare, businesses need to change continuously. Instead of programs and projects, they need transformation value networks that adapt to dynamic organizational and external drivers.
This presentation will use a unified framework and method to define and relate the ingredients for continuous transformation. The presenters will also demonstrate the value of standards-based visual modeling for integrating, expressing and improving business transformation practices. Visual models will show how American and European healthcare payers are improving quality and efficiency in response to demographic, economic and regulatory pressures.
Learning Objectives:
• Understand how to integrate capability-based planning, portfolio management, architecture and agile development processes
• Identify and position key frameworks for capability-based planning, portfolio management, architecture and agile development processes
• Understand core concepts and key applications of the ArchiMate language for visual modeling, an Open Group standard
• Understand the basics of visually modeling business strategy and organizational transformation
• Become familiar with the objectives and methods for an example of business transformation
• Understand how and when to integrate strategic guidance into agile development processes
Thought Leader Interview: Dr. William Turner on the Software-Defined Future ...Iver Band
As the Vice President, Datacenter Architecture at Presidio,
William Turner, PhD has more than 20 years of hand-son,
full-project-cycle experience in strategizing, designing and
deploying large-scale Fortune 500 networks and security
solutions. His extensive background in banking, security,
and government has yielded several well regarded industry
standards and noted reference models.
Dr. Turner envisions and drives a future in which sophisticated software provisions and de-provisions IT infrastructure automatically in response to business needs. The specialized appliances enterprises traditionally rely upon will be replaced by industry-standard hardware playing necessary roles on demand.
EAPJ conducted this interview from the perspective of an infrastructure architect considering a software-defined future for the networking, hosting and storage underlying a
major upcoming application investment.
Thought Leader Interview: Allen Podraza on Records ManagementIver Band
Allen Podraza is a Certified Information Professional who believes that organizations benefit from developing a strategy for managing their information. He serves as the Director of Records Management & Archives for the American Medical Association in Chicago. He is an active member of a number of professional associations including the Association for Information and Image Management (AIIM), ARMA International and the Society of American Archivists (SAA), and has advised organizations on the development and administration of records management and archive programs. He also provides a wealth of “How To” advice though his blog, posts, and tweets.
This interview uses the Architecture Development Method (ADM) of The Open Group Architecture Framework (TOGAF®) as a template for interviewing Allen Podraza. As shown in the figure below, the ADM cycle focuses successively on the establishment of an architecture capability, the development of an architecture, planning for the transition to the new architecture, and architecture governance. Allen has responded to this unusual interview format with expert advice relevant to all aspects of the architecture lifecycle.
Visualizing IT at the Department of Homeland Security with the ArchiMate® Vi...Iver Band
Department of Homeland Security (DHS) Chief Information Officer (CIO) Luke McCormack recently
submitted testimony to a US Senate Subcommittee. This case study, which is based on CIO
McCormack’s testimony, demonstrates how enterprise architects using the ArchiMate® language can
quickly capture business situations using viewpoints defined in the ArchiMate specification. These
viewpoints are templates for views that address particular sets of stakeholder concerns. This case study
contains views based on and named after standard templates.
This issue focuses on how EA can empower organizations to achieve their goals. EA and quality expert Mike Novak compares the TOGAF®1 framework for enterprise architecture with the Baldrige approach to organizational performance assessment and improvement, and shows how organizations could benefit from integrating the two paradigms. This is a great article for all those who have wondered about the relationship between EA and quality practices, or would like to learn more about either paradigm. The article assumes a bit of familiarity with the TOGAF standard, so novices should consult one of the references at the bottom of this page. This issue also features an interview with Mike Callahan, a senior partner in AgileLayer, a business architecture methodology, software and consulting provider. Mike Callahan introduces us to his area of expertise, and explains how business architects practice many of the methods Mike Novak describes in his TOGAF/Baldrige article.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
3. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 3
Table of Contents
Executive Summary...................................................................5
Introduction..............................................................................6
The ArchiMate and TOGAF Standards...........................................................6
Background .....................................................................................................7
Rationalization ................................................................................................8
Digital Transformation....................................................................................9
Phase A: Architecture Vision................................................... 10
Longer-Term Vision...................................................................................... 12
Solution Concept........................................................................................... 13
Phase B: Business Architecture................................................ 15
Organization Structure .................................................................................. 15
Capabilities.................................................................................................... 16
Business Functions........................................................................................ 17
Capabilities versus Business Functions......................................................... 18
Business Processes ........................................................................................ 19
Requirements Realization.............................................................................. 20
Gap Analysis ................................................................................................. 21
Capability Realization ................................................................................... 22
Phase C: Information Systems Architectures (Application)....... 24
Application Cooperation ............................................................................... 24
Business-Application Alignment................................................................... 27
Application Behavior .................................................................................... 28
Gap Analysis ................................................................................................. 28
Phase C: Information Systems Architectures (Data) ................. 30
Phase D: Technology Architecture ........................................... 32
4. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 4
Infrastructure ................................................................................................. 32
Gap Analysis ................................................................................................. 36
Phases E & F: Opportunities & Solutions and Migration Planning
............................................................................................... 38
References............................................................................... 40
About the Authors................................................................... 41
Acknowledgements.................................................................. 42
About The Open Group........................................................... 43
5. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 5
Boundaryless Information Flow
achieved through global interoperability
in a secure, reliable, and timely manner
Executive Summary
The ArchiSurance Case Study is a fictitious example developed to illustrate the use of
the ArchiMate®
modeling language in the context of the TOGAF®
framework. The
Case Study concerns the insurance company ArchiSurance, which has been formed
as the result of a merger of three previously independent companies. The Case Study
describes the Baseline Architecture of the company and then a number of change
scenarios.
Even though the concepts presented in this Case Study could be applied to different
situations, the example addresses typical concerns corresponding to the insurance and
financial sectors.
This work supports The Open Group vision of Boundaryless Information Flow™ by
illustrating the combined use of the ArchiMate and TOGAF standards for consistent
representation of architectural information across diverse organizations, systems, and
initiatives.
This document is an update of the pre-existing ArchiSurance Case Study [5], to
reflect the changes and additions in the ArchiMate 3.0 Specification.
6. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 6
Introduction
This fictitious Case Study illustrates the realistic use of the ArchiMate enterprise modeling language in the
context of the TOGAF framework. The Case Study concerns the insurance company ArchiSurance, the result
of a merger of three previously independent companies based in different metropolitan areas.
This Case Study shows Baseline and Target Business, Application, Data, and Technology Architectures,
making use of the appropriate ArchiMate or TOGAF viewpoints. The study incorporates two change
scenarios: Rationalization and Digital Transformation.
This document is an update of the pre-existing ArchiSurance Case Study [5], to reflect the changes and
additions in the ArchiMate 3.0 Specification. The Open Group expects the Case Study to evolve over time,
and encourages its members to add new aspects and views or create new change scenarios, as long as they are
consistent with the original case description and models.
The ArchiMate and TOGAF Standards
Frameworks for Enterprise Architecture cover different aspects of architecture practice. They may have,
among others, any combination of the following ingredients:
• A method for creating architectures
• A set or classification of viewpoints
• A language for describing architectures including language element definitions and notations
The Open Group maintains two open standards for Enterprise Architecture: the TOGAF framework [1] and
the ArchiMate modeling language [2]. The core of the TOGAF framework is a method for Enterprise
Architecture development and implementation: the Architecture Development Method (ADM). The TOGAF
framework also describes viewpoints, techniques, and reference models, as well as a content framework that
identifies the types of building blocks that make up an architecture. However, the TOGAF framework does
not prescribe the use of a specific modeling language to create architectural views.
The ArchiMate standard is a graphical language that provides a uniform representation for models that can
support the complete architecture development cycle. The ArchiMate 3.0 Specification consists of a core
language, aimed at the description of Business, Information Systems, IT, and physical Technology
Architectures, and their inter-relationships. The ArchiMate 3.0 Specification also contains elements to model
business and technology strategy; motivations driving architecture development; and plans for architecture
implementation and migration.
Figure 1 sketches how the core language and additional elements support the TOGAF ADM. In addition, the
ArchiMate 3.0 language contains elements for modeling the physical aspects of an enterprise, such as
facilities and equipment, which the TOGAF framework does not address. This Case Study considers physical
elements part of the ArchiSurance Technology Architecture using viewpoints chosen from both the TOGAF
framework and the ArchiMate language.
The ArchiMate and TOGAF standards share a firm foundation in their core ideas and their use of viewpoints
to capture and communicate different aspects of a single underlying architecture model. The standards
7. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 7
complement each other in that the TOGAF standard focuses on a method for developing and implementing
architectures, while the ArchiMate standard focuses on a uniform language for modeling architectures.
The ArchiMate language, as described in The Open Group standard [2], complements the TOGAF
framework [1] in that it provides a vendor-independent set of concepts and relationships, including a
graphical representation that helps to create a consistent, integrated model, which can be depicted in the form
of views. While the ArchiMate language defines its own example viewpoints that serve as templates for a
broad range of views, the language can also be used to construct the diagrams defined in the TOGAF
Architecture Content Framework.
Figure 1: Approximate Correspondence between the ArchiMate Language and the TOGAF ADM
Background
ArchiSurance [3, 4] is the result of a merger of three previously independent insurance companies:
• Home & Away, specializing in homeowners’ insurance and travel insurance
• PRO-FIT, specializing in auto insurance
• Legally Yours, specializing in legal expense insurance
The company now consists of three divisions with the same names and headquarters as their independent
predecessors.
8. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 8
Figure 2: ArchiSurance: The Result of a Merger of Three Insurance Companies
ArchiSurance was formed to take advantage of numerous synergies between the three organizations. While
the three pre-merger companies sold different types of insurance, they had similar business models. All three
sold direct to consumers and businesses through the web, email, telephone, and postal mail channels.
Although based in different cities, each was completely housed in a modern office complex in a major
metropolitan area. Each had loyal customer bases and strong reputations for integrity, value, service, and
financial stability. All three companies were privately held by interlocking groups of institutional and
individual investors.
The lead investors of the three companies began merger talks after they noticed that lower-cost competitors
were entering their markets, that there were new opportunities in high-growth regions, and that each company
required significant new IT investments to remain competitive. They realized that only a larger, combined
company could simultaneously control its costs, maintain its customer satisfaction, invest in new technology,
and take advantage of emerging markets with high growth potential. The merger negotiations and regulatory
approvals took 18 months, but two years ago the papers were signed and the merger was complete.
The new company offers all the insurance products of the three pre-merger companies, and intends to
frequently adjust its offerings in response to changing market conditions. Like its three predecessors,
ArchiSurance sells directly to customers via web, email, telephone, and postal mail channels, and indirectly
via intermediaries.
Rationalization
The inflexibility of the ArchiSurance Application Architecture makes it difficult to adapt to changes in
business conditions. Partly as a result of the merger, the application landscape has become scattered, resulting
in data redundancy and functional overlap, as well as point-to-point application integration using a variety of
data formats and methods. These problems cause internal instabilities, increased application maintenance
costs, and obstacles to sharing information across the company and with partners. Consequently, the IT
department has a sizable backlog of work requests. ArchiSurance top management is very concerned about
the backlog, particularly an unmet need to share information automatically with high-volume contracted sales
partners and influential insurance consultants.
Home & Away
Homeowner’s and
Travel insurance
PRO-FIT
Auto insurance
LegallyYours
Legal Expense
insurance
ArchiSurance
9. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 9
The ArchiSurance lead investors and CEO support these initiatives on the condition that all changes are
invisible to ArchiSurance customers and partners. The insurer’s products and services must not be affected,
and all customer and partner interactions must proceed uninterrupted and unchanged.
As part of this effort, the technical infrastructure will also be simplified. The separate back-office servers will
be replaced by a shared server cluster located in the data center at Home & Away headquarters. However, to
ensure business continuity, there will also be a back-up server cluster located in the data center at PRO-FIT
headquarters.
Digital Transformation
In addition to the more immediate goals related to post-merger integration, ArchiSurance also sees the rapid
pace of technology as both a challenge and an opportunity. It wants to embark on a digital transformation and
has defined a new Digital Customer Intimacy strategy, which employs a combination of Big Data and the
Internet of Things (IoT). ArchiSurance intends to acquire more detailed customer data and use it to improve
customer interaction and satisfaction, and to adjust insurance premiums based on risk.
To this end, for insurance products sold to consumers, ArchiSurance intends to use data from smart,
connected devices such as fitness trackers, vehicle tracking systems, or home automation gateways. In
various B2B markets ArchiSurance intends to use data from sources such as fleet management systems,
energy networks, in-store RFID1
devices, or smart building sensors. Ultimately, this may result in real-time
insurance products where customers receive direct feedback on the financial consequences of their behavior,
and advice on adjusting this behavior to lower their insurance premium.
The next chapters, describe how ArchiSurance approaches the Rationalization and Digital Transformation
change scenarios.
1
See https://nl.wikipedia.org/wiki/Radio-frequency_identification.
10. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 10
Phase A: Architecture Vision
To guide future changes in their business and information technology, ArchiSurance has decided to develop
an Enterprise Architecture based on the ArchiMate 3.0 and TOGAF 9.1 standards.
As part of Phase A, the main stakeholders in the architecture engagement and their concerns (modeled as
internal drivers in the ArchiMate standard) are identified. The TOGAF standard defines a Stakeholder Map
matrix to represent this. In the ArchiMate standard, this can be expressed using the Stakeholder viewpoint:
The Stakeholder viewpoint allows the analyst to model the stakeholders, their concerns, and the assessments
(in terms of strengths, weaknesses, opportunities, and threats) of these concerns. Also, the links to the initial
high-level goals that address these concerns and assessments may be described.
Figure 3 shows a part of such a diagram, identifying two stakeholders (the ArchiSurance board of directors
and its current and potential customers) and their concerns, modeled as drivers. Customer satisfaction is a
shared concern of both stakeholders. Stakeholder satisfaction can be refined into more detailed concerns; e.g.,
profitability.
Figure 3: Fragment of a Stakeholder View
Drivers motivate the development of specific business goals, as shown in Figure 4 for profitability. The two
assessments show that profitability of ArchiSurance is suffering from customers defecting to competitors
with superior digital experiences or lower premium costs. Goals such as reduction of costs have a positive
influence on this driver. This goal can in turn be partitioned into the reduction of maintenance costs and the
reduction of personnel costs.
11. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 11
Figure 4: Business Goals Associated with the Driver Profitability
Based on its business goals, ArchiSurance defines a set of principles to guide its architecture development.
The ArchiMate standard defines a principle as a realized qualitative statement of intent that must be met by
the architecture. Note that the systems here include, for example, organizations and organization units, not
only IT systems. Principles, therefore, help realize business goals. The TOGAF standard also defines a
principle as a qualitative statement of intent that should be met by an architecture. A TOGAF principle must
have at least a supporting rationale and a measure of importance.
The ArchiMate Principles viewpoint, an example of which is shown in Figure 5, depicts principles, their
dependencies, and the goals they realize:
The Principles viewpoint allows the analyst or designer to model the principles that are relevant to the design
problem at hand, including the goals that motivate these principles. In addition, relationships between
principles, and their goals, can be modeled. For example, principles may influence each other positively or
negatively.
The TOGAF standard defines a Principles catalog to provide an overview of principles.
Figure 5: Principles View (Fragment)
12. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 12
Goals and principles are the basis for concrete requirements, as shown in a Goal Refinement viewpoint:
The Goal Refinement viewpoint allows a designer to model the refinement of high-level goals into more
concrete goals, and the refinement of concrete goals into requirements or constraints that describe the
properties that are needed to realize the goals. The refinement of goals into sub-goals is modeled using the
aggregation relationship. The refinement of goals into requirements is modeled using the realization
relationship.
Figure 6 shows an example of such a view for the Rationalization change scenario.
Figure 6: Goal Refinement View for Rationalization Strategy
Longer-Term Vision
In addition to the short-term need for rationalization, ArchiSurance has defined a longer-term Digital
Customer Intimacy strategy that combines Big Data and the Internet of Things (IoT). ArchiSurance intends to
use more detailed customer data to improve customer interaction and satisfaction, and to customize insurance
premiums based on insights into the customers’ behavior. The company will capture this data with smart,
connected devices such as personal fitness trackers, black boxes in vehicles, home automation gateways, fleet
management systems, in-store RFID devices, or smart building sensors.
13. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 13
The Strategy viewpoint allows the Business Architect to model an overview of the courses of action chosen
or considered by the enterprise, the capabilities and resources supporting them, the envisaged outcomes, and
how these contribute to the organization’s goals and drivers.
Figure 7: Strategy View for Digital Customer Intimacy Strategy
Ultimately, this new strategy should of course also contribute to the main drivers of the organization, as
outlined in part in Figure 3. The relationships between strategy, capabilities, envisaged outcome, and
stakeholders’ drivers is shown in Figure 7. The Digital Customer Intimacy strategy requires ArchiSurance to
develop a number of new capabilities and resources, including digital customer management, data
acquisition, and data analysis.
Solution Concept
An important element of the Architecture Vision is a high-level representation of the Target Architecture and
how this provides a solution to the needs of the enterprise, to explain the added value of the architecture
effort to stakeholders. The TOGAF Solution Concept diagram can be created with the ArchiMate language
for this purpose. Figure 8 highlights the most important aspects of the Target Architecture, showing
requirements and outcomes derived from both the Rationalization and the Digital Customer Intimacy
strategies:
• Enterprise-wide CRM automation in the front-office, to replace individual CRM systems.
14. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 14
• Integrated back-office automation will replace the separate back-office applications for the different lines
of business.
• The outcome Detailed insights in customer behavior will be supported by acquiring customer behavior
data from external data sources, which will be fed into a solution for automated data analysis, which in
turn will deliver customer profiles to the new back-office solution. The business intelligence gained from
that will be used in setting insurance premiums for individual customers as part of the Claim
management capability, and the development of new insurance products. This will also require the
development of organizational competencies in data analysis.
• Various social media apps in combination with the requisite social media competencies of the
organization will realize the envisaged excellent online customer interaction.
Figure 8: Solution Concept View
15. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 15
Phase B: Business Architecture
After the merger, ArchiSurance set up a shared front-office as a multi-channel contact center for sales and
customer service, with a primary contact center at the pre-merger headquarters of Home & Away. There are
still three separate back-offices that handle the insurance products of the three original companies. A Shared
Service Center (SSC) has been established for document processing at the pre-merger headquarters of PRO-
FIT. The center administers the central document repository as well as all automated document workflows. In
addition, it performs all scanning, printing, and archiving for legally binding documents as they enter or leave
ArchiSurance. To ensure business continuity and handle periods of peak activity, the SSC also hosts trained
personnel and equipment to perform the functions of the front-office, which is similarly prepared to
reciprocate.
In Phase B (Business Architecture) of the TOGAF ADM, the ArchiMate language can express and relate
ArchiSurance organizational structure, products, services, functions, processes, and information. The
Business Architecture provides context for the Data, Application, and Technology Architectures.
Organization Structure
For describing the organization structure, the ArchiMate standard defines the Organization viewpoint:
The Organization viewpoint focuses on the organization of a company, a department, a network of
companies, or of another organizational entity. It is possible to present models in this viewpoint as nested
block diagrams, but also in a more traditional way, such as organizational charts. The Organization viewpoint
is very useful in identifying competencies, authority, and responsibilities in an organization.
The TOGAF counterpart of this viewpoint is the Organization Decomposition diagram.
The organization structure is often represented as a tree, as shown in Figure 9, although the organizational
decomposition approach used by both the ArchiMate and TOGAF standards has far more options than a
simple tree-style organizational chart. This view shows the high-level organization structure of ArchiSurance,
with its main locations and departments. Alternatively, a nested diagram can depict the subdivision of the
organization’s departments (Figure 10).
16. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 16
Figure 9: Organization View
Figure 10: Organization Decomposition (Nested)
Capabilities
ArchiSurance needs to improve or change several of its capabilities to implement the strategic and
operational changes it envisages. To that end, it has created a capability map to get a clear view of its current
capabilities, inspired by the Panorama360 reference model for the insurance industry.2
This is shown in
Figure 11.
2
See www.insuranceframeworks.com/what_is_panorama360.aspx.
17. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 17
The Capability Map viewpoint allows the Business Architect to create a structured overview of the
capabilities of the enterprise. A capability map typically shows two or three levels of capabilities across the
entire enterprise. It can, for example, be shaded to create a heat map that identifies areas requiring
investment.
The capabilities are realized by the behavior of the organization, as shown in Figure 13. These capabilities
need to be supported by the right resources.
Figure 11: Capability Map View (Baseline)
Business Functions
An ArchiMate business function groups behavior based on a chosen set of criteria, typically required
business resources, and/or competencies.
The main business functions that ArchiSurance distinguishes are:
• Marketing, which studies, plans, promotes, and manages products and market segments, and works with
Actuarial to design products
• Actuarial, which determines product prices and reserve levels, works with marketing to design new
products, and analyzes enterprise risk
• Customer Relations, which includes the interactions between ArchiSurance and its customers; it handles
customer questions, captures incoming claims, and conducts direct marketing campaigns
• Underwriting, which sets prices for individual policies and generates insurance proposals and policies
18. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 18
• Claims, which formulates and executes a response to each claim against an ArchiSurance policy
• Sales, which manages a pipeline of opportunities, and closes contracts with customers
• Finance, which handles regular premium collection and the payment of insurance claims
• Document Processing, which supports other functions through document scanning, printing, and
archiving
• Investment Management, which manages financial and real estate assets for maximum returns within
corporate and regulatory liquidity and risk constraints
Some of these business functions are replicated in the three divisional back-offices of ArchiSurance.
To model business functions and their relationships, we can define a Business Function viewpoint and
specify its contents using the viewpoint mechanism defined in the ArchiMate specification:
The Business Function viewpoint shows the main business functions of an organization and their
relationships in terms of the flows of information, value, or goods between them.
The TOGAF counterpart of this viewpoint is the Functional Decomposition diagram.
Figure 12 shows the main business functions of ArchiSurance, as well as the most important information
flows between the functions and external roles. It also shows the replication of business functions in the
back-offices of the different divisions.
Figure 12: Business Function View (Baseline)
Capabilities versus Business Functions
Note that business functions are distinct from capabilities. Capabilities represent the current or desired
abilities of an organization, realized by its people, processes, information, and technology. They are focused
on specific business outcomes, and are used for strategic planning purposes, as described in Phase A:
19. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 19
Architecture Vision (on page 10). In contrast, business functions describe what the organization actually
does; they are explicitly managed, and are more closely aligned to the organization structure. Multiple
business functions may (together with other elements) contribute to the realization of a capability.
An example is the new capability Digital Customer Management that ArchiSurance wants to establish as part
of their Digital Customer Intimacy strategy (see Figure 11). This capability will in part be realized by the
Customer Relations business function, but also by a (yet-to-be realized) business function Business
Intelligence, and by various resources such as data analysts, risk managers, data acquisition and analysis
applications, and customer behavior data.
Of course, when drawing a map of the current capabilities of the organization, its current business functions
will often figure prominently, since what an organization does must be something it is able to do. In
describing the Baseline Business Architecture, the value of a capability map therefore mostly lies in the
analysis of the current versus desired levels of capability on the one hand, and in uncovering capabilities that
the organization already possesses but does not recognize or manage as business functions on the other.
Figure 13 shows some of these relationships between the main capabilities of ArchiSurance as listed in
Figure 11 and the business functions mentioned in this section. Note that not all capabilities are listed, since
the business functions in this section are focused on the primary operations of ArchiSurance and not on, for
example, its management. Figure 13 also shows the letter notation that signifies the layer of a concept (‘S’ for
strategy and ‘B’ for business layer).
Figure 13: Capability Realization (Baseline)
Business Processes
An ArchiMate business process groups behavior based on an ordering of activities. It produces a defined set
of products or services. A process architecture shows the most important business processes and their
relationships, and possibly the main steps within each of the processes. It usually does not show all the details
20. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 20
of a process flow, which is the purpose of business process design languages. We can define a Business
Process viewpoint and specify its contents using the viewpoint mechanism defined in the ArchiMate
specification:
The Business Process viewpoint is used to show the high-level structure and composition of one or more
business processes.
The TOGAF counterpart of this viewpoint is the Process Flow diagram.
Figure 14 shows the two central business processes of ArchiSurance, with their high-level sub-processes:
Issue new policy, which is performed when selling a new insurance product, and Handle claim, which is
performed when a damage claim has been received. While the details of these processes may differ for the
different types of insurance product, the main steps are the same.
Figure 14: Business Process View (Baseline)
Requirements Realization
In the Business Architecture, we also show how the Target Architecture realizes the key business
requirements. For this purpose, the TOGAF standard specifies a Business Footprint diagram. In the
ArchiMate language, this can be expressed using the Requirements Realization viewpoint, defined as
follows:
The Requirements Realization viewpoint allows the designer to model the realization of requirements by the
core elements, such as business actors, business services, business processes, application services, application
components, etc. Typically, these requirements result from the Goal Realization viewpoint.
The example below shows how the business requirements established in the Architecture Vision phase are
realized by elements in the architecture.
21. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 21
Figure 15: (Partial) Requirements Realization View
Gap Analysis
The Digital Customer Intimacy strategy of ArchiSurance also requires changes to the Business Architecture.
First of all, new capabilities are needed, as identified before. Figure 16 shows these new capabilities in the
context of the pre-existing Customer care and Claim management capabilities.
Figure 16: Capabilities Gap Analysis
22. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 22
Capability Realization
These capabilities require personnel with the right knowledge and skills for the digital age, smart devices for
data acquisition, and the customer data itself.
The Resource Map viewpoint allows the Business Architect to create a structured overview of the resources
of the enterprise. A resource map may also show relationships between resources and the capabilities they
support.
On the left-hand side in Figure 17, you see the capabilities and resources related to the Rationalization
strategy, and on the right are those linked to the Digital Customer Intimacy strategy.
Figure 17: Resource Map View (Target)
These resources themselves are realized by the rest of the Business, Information Systems, and Technology
Architectures that are the subject of Phases B, C, and D of the TOGAF ADM. A small part of what this may
result in is shown in Figure 18. Note that this does not depict all elements needed to realize these resources,
but only a representative sample, again showing the implementation of the Rationalization strategy on the left
and the Digital Customer Intimacy strategy on the right. In practice, separate views will often be created to
show how individual capabilities and resources are realized.
24. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 24
Phase C: Information Systems Architectures (Application)
Since the merger, the three divisions have adopted a common web portal, contact center software suite, and
document management system. Also, the company has selected a strategic CRM solution and implemented it
for both Home & Away and PRO-FIT. However, due to management’s focus on minimizing post-merger
risks while continually improving the day-to-day performance of each division, core business application
rationalization has not begun. Now that ArchiSurance has met post-merger performance expectations,
investors expect substantial IT cost savings through the adoption of a common set of product and customer-
focused applications. Therefore, a number of challenges remain. Home & Away still uses its pre-merger
policy administration and financial application packages, while PRO-FIT and Legally Yours still use their
own pre-merger custom monolithic applications.
Application Cooperation
The ArchiMate standard defines an Application Cooperation viewpoint to show an overview of the
application landscape and the dependencies between the applications:
The Application Cooperation viewpoint describes the relationships between application components in terms
of the information flows between them, or in terms of the services they offer and use. This viewpoint is
typically used to create an overview of the application landscape of an organization. This viewpoint is also
used to express the (internal) co-operation or orchestration of services that together support the execution of a
business process.
The TOGAF counterpart of this viewpoint is the Application Communication diagram.
Figure 19 shows the main applications of ArchiSurance and the main data flows between them.
25. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 25
Figure 19: Application Cooperation View (Baseline)
The Application Cooperation view in Figure 20 shows the proposed target situation for the application
landscape.
26. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 26
Figure 20: Application Cooperation View (Target)
This comprises the following application components, that together realize the Rationalization scenario:
• An integrated back-office suite for functions such as policy administration and financial transactions. The
suite consists of:
o AUTO-U, an automated underwriting system that generates proposals and policies.
o P-ADMIN, a packaged policy administration system that integrates with the automated
underwriting system to issue, modify, and renew policies; this system also handles customer
accounting and billing for all lines of business, replacing the policy administration functionality of
the Home & Away, Auto, and Legal Expense legacy systems.
o VERSA-CLAIM, a packaged claims system with screens and workflow that can be configured to
support the three lines of business of ArchiSurance, replacing the claims processing functionality
of the Home & Away, Auto, and Legal Expense legacy systems.
o P-CONFIG, a product configurator management system used to define all insurance products, and
27. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 27
expose these definitions to AUTO-U, P-ADMIN, and VERSA-CLAIM through web services.
o BRIMS, a Business Rule Management System (BRMS) consisting of a rules repository, a
processing engine, a rule development environment, and an authoring tool for rule management
user interfaces. The business rule engine exposes rule execution capabilities to AUTO-U, P-
ADMIN, VERSA-CLAIM, and P-CONFIG through web services.
• A general CRM system, to be used by the entire organization.
Business-Application Alignment
The TOGAF standard does not define diagrams for business-application alignment. However, it does specify
matrices to show the links between the Business and the Application Architecture; e.g., an
Application/Organization matrix and an Application/Function matrix.
The relationships between application components can also be modeled graphically. The ArchiMate standard
defines the Application Usage viewpoint:
The Application Usage viewpoint describes how applications are used to support one or more business
processes, and how they are used by other applications. It can be used in designing an application by
identifying the services needed by business processes and other applications, or in designing business
processes by describing the services that are available. Furthermore, since it identifies the dependencies of
business processes upon applications, it may be useful to operational managers responsible for these
processes.
The Application Service concept plays a central role in this viewpoint. Figure 21 shows a subset of the
services offered by the applications used by the Home & Away division of ArchiSurance, and which of the
sub-processes of the claim handling process make use of which of these services.
Figure 21: Application Usage View (Baseline)
28. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 28
Application Behavior
The behavior of the data warehousing solution, in the context of data acquisition on the one hand and the
business processes and functions on the other, is shown in Figure 22. The insurance premium of individual
customers is based in part on the data they acquire from different devices. This data is processed to create
customer-specific profiles that are input to the calculation of their insurance premiums. At an aggregated
level, this data is also used to develop new kinds of insurance products and to assess and adjust the overall
risk exposure of the company.
Figure 22: Application Behavior View (Target)
Gap Analysis
The results of a global gap analysis for the Application Architecture are visualized below. Several application
components that exist in the Baseline Architecture are no longer present in the Target Architecture: the
separate back-office applications and the separate Legal Expense insurance CRM system. The CRM
functionality for Legal Expense insurance customers is taken over by the general CRM system; therefore, this
does not require new components (although it may be necessary to adapt or reconfigure the existing general
CRM system, this is not shown in the gap analysis). In addition, a completely new back-office application
suite and new data warehousing solution are introduced.
30. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 30
Phase C: Information Systems Architectures (Data)
The ArchiSurance Data Architecture describes the major relationships between its conceptual business
objects and its logical data objects. The ArchiMate standard defines the Information Structure viewpoint for
this purpose:
The Information Structure viewpoint is comparable to the traditional information models created in the
development of almost any information system. It shows the structure of the information used in the
enterprise or in a specific business process or application, in terms of data types or (object-oriented) class
structures.
One of the data viewpoints that the TOGAF standard defines is the Logical Data diagram.
Figure 24 shows a subset of the business objects that ArchiSurance defines. Part of the customer information
is an insurance file, which is composed of insurance requests, insurance policies, and damage claims. A
number of specializations of the insurance policy object are defined, one for each type of insurance that
ArchiSurance sells.
Figure 24: Information Structure View Showing Main Business Objects
Another data viewpoint that the TOGAF standard defines is the Data Dissemination diagram:
The purpose of the Data Dissemination diagram is to show the relationship between data entity, business
service, and application components. The diagram shows how the logical entities are to be physically realized
by application components. This allows effective sizing to be carried out and the IT footprint to be refined.
Moreover, by assigning business value to data, an indication of the business criticality of application
components can be gained.
31. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 31
Figure 25 shows a Data Dissemination diagram for one ArchiSurance application.
Figure 25: Data Dissemination Diagram
32. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 32
Phase D: Technology Architecture
In the ArchiSurance front-office, located at the Home & Away headquarters, there is a general-purpose server
and one dedicated to web hosting. The Shared Service Center (SSC), located at the PRO-FIT headquarters,
has its own server for the document management system. Each of the three back-offices has a server for its
applications.
A Local Area Network (LAN) connects servers and personal computers at each of the three ArchiSurance
locations, which are in turn connected by a corporate Wide Area Network (WAN).
For an overview of the infrastructure landscape, the ArchiMate standard defines the Infrastructure viewpoint:
The Infrastructure viewpoint contains the software and hardware infrastructure elements supporting the
Application Layer, such as physical devices, networks, or system software, such as operating systems,
databases, and middleware.
The TOGAF counterpart of this viewpoint is the Environments and Locations diagram.
Infrastructure
Figure 26 shows the main infrastructure components of ArchiSurance, grouped by location and department.
Also the networks that connect the different devices, and the (application) artifacts deployed on the devices,
are shown in this view.
33. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 33
Figure 26: Infrastructure View (Baseline)
The Infrastructure view in Figure 27 shows the proposed target situation for the technical infrastructure
landscape.
34. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 34
Figure 27: Technology Architecture: Infrastructure View (Target)
In a separate set of views, ArchiSurance has visualized the IoT-based data acquisition in Figure 28, as
outlined in its new Digital Customer Intimacy strategy. To support this, ArchiSurance establishes a data
acquisition gateway that can connect to all kinds of smart devices that generate relevant data. These devices
are modeled as Equipment. In turn, equipment can be located at a Facility; in Figure 28 we see a Home alarm
system and Smart thermostat within a Smart home. Finally, the Smart thermostat itself is connected to the
Energy Network, modeled as a Distribution network in the ArchiMate language.
35. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 35
Figure 28: Data Acquisition from IoT Sevices (Target)
The implementation of ArchiSurance data acquisition is based on a microservices architecture. IoT devices
can register themselves with the gateway via a REST3
API. It also uses services on the API to notify the
gateway of the data it acquires. For each registered device, an instance of the data acquisition functionality
will run in a container. The gateway itself is supported by a Platform-as-a-Service (PaaS), providing services
for deployment, integration, service lifecycle management, accounting, security, load balancing, storage,
virtualization, and more. This is shown in Figure 29.
3
See https://en.wikipedia.org/wiki/Representational_state_transfer.
36. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 36
Figure 29: IoT Device Services (Target)
Gap Analysis
Figure 30 visualizes the results of a global gap analysis for the Technology Architecture. The separate
general-purpose back-office servers are slated for removal. The original server cluster of Home & Away is to
become the central ArchiSurance back-office service cluster, and an additional back-up server cluster is to be
placed in the SSC at PRO-FIT headquarters. There is also a back-up document management server to be
placed in the Home & Away back-office. The new back-office suite and the document management system
are to be replicated on their respective main servers and back-up servers.
38. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 38
Phases E & F: Opportunities & Solutions and Migration Planning
The TOGAF 9 standard introduces for Phases E and F the Transition Architecture, representing a possible
intermediate situation or plateau between the Baseline Architecture and the Target Architecture.
In the ArchiMate standard, the Baseline, Target, and Transition Architectures, as well as their relationships,
are shown using the Migration viewpoint:
The Migration viewpoint entails models and concepts that can be used for specifying the transition from an
existing architecture to a desired architecture.
Figure 31 shows an example for the current scenario. The IT department of ArchiSurance does not have
sufficient resources to carry out the standardization of the back-office systems and the integration of the
CRM systems in parallel. One Transition Architecture therefore replaces two CRM systems with one, but has
separate back-office systems. Another has a single back-office suite but two CRM applications. After that,
the data warehousing and IoT solution will be implemented.
Figure 31: Migration View
Transition Architectures enable the planning of implementation projects such as CRM integration and back-
office application integration. The sequence of these projects depends on which of the Transition
Architectures is selected. This can be is shown in a TOGAF Project Context diagram (Figure 32):
A Project Context diagram shows the scope of a work package to be implemented as part of a broader
transformation roadmap. The Project Context diagram links a work package to the organizations, functions,
services, processes, applications, data, and technology that will be added, removed, or impacted by the
project.
40. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 40
References
The following documents are referenced in this Case Study:
(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)
[1] TOGAF®
Version 9.1, an Open Group Standard (G116), published by The Open Group, December 2011;
refer to: www.opengroup.org/togaf.
[2] ArchiMate®
3.0 Specification, an Open Group Standard (C162), published by The Open Group, June
2016; refer to: www.opengroup.org/archimate.
[3] Doest, H., Iacob, M.-E., Lankhorst, M.M. (Ed.) & van Leeuwen, D.: Viewpoints Functionality and
Examples, ArchiMate Deliverable D3.4.1a v2, TI/RS/2003/091, Telematica Instituut, Enschede, The
Netherlands, 2004.
[4] van den Berg, H., Moelaert, F.: PRO-FIT Autoschade Open Case Testbed, Testbed Deliverable
WP3/N004/V001, TRC, Enschede, The Netherlands, 1997.
[5] ArchiSurance Case Study, White Paper, Y121, January 2012, published by The Open Group; refer to:
www.opengroup.org/bookstore/catalog/y121.htm.
41. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 41
About the Authors
Henk Jonkers is a Senior Research Consultant at BiZZdesign. In this capacity, he is
involved in the company’s new developments in the area of Enterprise Architecture and
enterprise engineering. He also participates in multi-party research projects, contributes
to training courses, and performs consultancy assignments. Previously, he worked as a
Member of Scientific Staff at Telematica Instituut (currently Novay), where he was
involved in various applied research projects in the areas of business process modeling
and analysis, Enterprise Architecture, service-oriented architecture, and model-driven
development. Henk was one of the main developers of the ArchiMate modeling
language and an author of the ArchiMate Specification, and is actively involved in the
activities of the ArchiMate Forum of The Open Group.
Iver Band is a practicing Enterprise Architect and a developer and communicator of
Enterprise Architecture standards and methods. At Cambia Health Solutions, he has
guided initiatives focusing on provider systems, web and mobile experiences, and
architecture methods and tools. He is currently focused on solutions that provide
information about healthcare consumers and groups. Iver also is the elected Vice-Chair
of the ArchiMate Forum. He has led development of several Open Group White Papers
and contributed to the second and third major versions of the ArchiMate modeling
language. He is TOGAF 9 and ArchiMate 2 Certified, a Certified Information Systems
Security Professional (CISSP), a Certified Information Professional (CIP), an AHIP
Information Technology Professional, and a Prosci Certified Change Consultant.
Dick Quartel is a Senior Research Consultant at BiZZdesign. In this role he contributes
to the development and improvement of BiZZdesign’s products and services, is involved
in research projects, supervises MSc students and interns, and performs consultancy
assignments. In addition, he is an author of many scientific and professional
publications, and an author of the ArchiMate Specification. Previously, he worked as a
Senior Researcher at Novay (formerly Telematica Instituut), where he acted as
researcher and project manager and contributed to the definition and acquisition of
research projects, and as an Assistant Professor at the University of Twente in the
areas of distributed systems design, protocol design and implementation, and
middleware systems.
Marc Lankhorst is Managing Consultant at BiZZdesign. He is responsible for market
development, consulting, and coaching on digital business design and Enterprise
Architecture, and spreading the word on the ArchiMate standard for Enterprise
Architecture modeling. His expertise and interests range from enterprise and IT
architecture and business process management to agile methods, portfolio
management, and digital business design. In the past, he has managed the ArchiMate
R&D project, a major cooperation between several partners from government, industry,
and academia which developed the initial version of the ArchiMate language, and he
currently leads the ArchiMate development team within the ArchiMate Forum of The
Open Group.
42. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 42
Acknowledgements
The authors wish to thank the following individuals for their assistance with this Case Study:
• R. Allampalli, Cognizant Technology Solutions
• Karen Lindokken, Standard Insurance Company
43. ArchiSurance Case Study
www.opengroup.org A Case Study Published by The Open Group 43
About The Open Group
The Open Group is a global consortium that enables the achievement of business objectives through IT
standards. With more than 500 member organizations, The Open Group has a diverse membership that spans
all sectors of the IT community – customers, systems and solutions suppliers, tool vendors, integrators, and
consultants, as well as academics and researchers – to:
• Capture, understand, and address current and emerging requirements, establish policies, and share best
practices
• Facilitate interoperability, develop consensus, and evolve and integrate specifications and open source
technologies
• Offer a comprehensive set of services to enhance the operational efficiency of consortia
• Operate the industry’s premier certification service
Further information on The Open Group is available at www.opengroup.org.