Modeling and Evolving a Web Portal with the TOGAF Framework and the ArchiMate Language

1

Modeling and Evolving a Web Portal

with the TOGAF Framework and the

ArchiMate LanguageIver Band and Ryan Kennedy

Open Group Conference, San Francisco, California

January 27, 2016

© 2016 Cambia Health Solutions, Inc.

22 © 2016 Cambia Health Solutions, Inc.

Iver Band

• Enterprise Architect at Cambia Health Solutions

• Web, mobile, analytics, campaign management, consumer data

• Architecture methods and tools

• Vice Chair, Open Group ArchiMate Forum

• TOGAF and ArchiMate certified, CISSP, AHIP Certified IT Professional, Certified Information Professional

[email protected]

http://www.linkedin.com/in/iverpdx

http://www.cambiahealth.com/

http://www.twitter.com/iverband

mailto:[email protected]

http://www.linkedin.com/in/iverpdx


http://www.twitter.com/iverband


Ryan Kennedy

• Digital Solutions Architect at Cambia Health Solutions

• Over a decade experience designing and implementing portal solutions

[email protected]


https://www.linkedin.com/in/rykennedy

mailto:[email protected]


https://www.linkedin.com/in/rykennedy

44

Agenda

•Background

•Case Study: Integrated Healthcare Delivery

•Conclusion and Discussion


55

BACKGROUND


66

About Cambia

22 companies

and growing


A tax-paying nonprofit

headquartered in

the Pacific Northwest

Nationally recognized:

Top 100 Healthiest

Workplaces

5,300 employees

in 30 states

100 million people

touched nationwide


88

Cambia Health Solutions


Senior

Services

Health

Insurance

Retail

Enablement

Provider

Enablement

99

What is a Horizontal Web Portal (“Portal”)?

• A personalized point of access to relevant information, business processes and people

• Supports a wide range of vertical markets and business activities

• Addresses various audiences, including employees, customers and partners, and citizens

• Delivers content to users of industry-standard web browsers

• Reuses, adapts and personalizes content and features for different audiences

• The “Swiss Army knife” of enterprise software


Adapted From Gartner Group: Magic Quadrant for Horizontal Portals, 15 Sep 2016

1010

What Are the Advantages of Portals?

Standardized Management of Segmented Experiences

User Experience Enabling Services

Personalization & Context Awareness Identity and Access Management

Navigation, Search and Discovery Content Management

Collaboration and Knowledge Mgmt Transaction & Commerce Support

Mobility and Multichannel Support Integration and Interoperability

Analytics and Experimentation

Standardized Architecture and Development


Adapted From Gartner Group: Critical Capabilities for Horizontal Portals, 10 Dec 2015

1111

What Are the Disadvantages of Portals?


Disadvantage Mitigation Strategy

Business Process Overhead Ensure retirement of legacy architectures and the processes that support them.

IT Process Overhead

Technical Complexity Use layered, component-based architecture that matches intended usage.

Technical Talent Requirements Maximize reliance on predominant web standards, open-source components, and preferred products and services. Apply standards to abstract proprietary interfaces.

Product Lock-In

1212

Portal Architectures Must Increasingly Meet Market

Demands for Always-On Services

Legacy Websites Market Demands

Availability Regular Maintenance Windows

Always Available

Scalability Thousands of UsersPredictable Peaks

Millions of UsersUnpredictable Bursts

Response Time Keep Users Productive No Wait

Identity and Access Management

Internal User Base with Centralized Administration

Infinite User Base with Multiple Identity Providers

Data Normalized for Integrity Cached for Performance and Availability

Integration Batch ETL and File Transfer

Lightweight, standards-based APIs


1313

CASE STUDY


1414

Fictitious Case Study: OmniHealth 365

• Integrated Delivery System

• Hospitals, Clinics, Urgent Care Centers

• Separate Websites for Each Audience

• Public, Providers, Consumers, Administrative Staff

• Challenges

• Expense and complexity of maintaining separate websites

• Experience consistency across websites

• Difficulties for users of multiple websites

• Goals

• Improve user experience

• Introduce new experiences more quickly

• Improve overall quality

• Share underlying services with emerging mobile applications

• Focus resources on developing features rather than overhead


1515

The TOGAF ADM Provides a Systematic

Approach to Portal Architecture


PPreliminary Phase

1616

The ArchiMate Language Complements

TOGAF With Standard Visual Modeling


PPreliminary Phase

1717

Language Elements & Specializations


PPreliminary Phase

The ArchiMate language can be adapted

1818

Vision


Delighted Web Audiences

Integrated Content, Technology & Lifecycles

Shared Data & Infrastructure

Agility Cost

Savings

AArchitecture Vision

1919

Stakeholder Motivation & Goals



ArchiMate modeling can capture politics and strategy

2020

Principles, Requirements, & Services



ArchiMate notation can connect motivations and the elements that realize them

2121

Baseline Business Architecture


BBusiness Architecture

Unique web processes with basic functionality

2222

Target Business Architecture BBusiness Architecture

Common web processes with advanced functionality

2323

Baseline Data Architecture


CInformation Systems Architecture

Four data silos

2424

Target Data Architecture



One shared data store

2525

Baseline Application Architecture



Redundant login component example

2626

Target Application Architecture



Standard portal login component

2727

Baseline Technology Architecture


DTechnology Architecture

Four unique web stacks

2828

Target Technology Architecture


DTechnology Architecture

One common web stack

2929

Solution Decisions


EOpportunities & Solutions

3030

Implementation and Migration Plan


FMigration Planning

Phased implementation beginning with public experience

3131

Work Plan


FMigration Planning

Each plateau is realized by specific deliverables

3232

Driving Agile Delivery

© 2016 Cambia Health Solutions, Inc. Work is broken down into story cards & assigned to Agile teams

GImplementation Governance

3333

CONCLUSION AND

DISCUSSION


3434

Conclusion

• Horizontal web portals address complex user experience challenges in healthcare

and many other industries

• Organizations must understand the needs of each of their audiences before

embarking on transformation projects

• Portal solutions are complex because portals have multifaceted and

interconnected responsibilities.

• Organizations should therefore develop portals incrementally as they build their

planning and implementation capabilities

• Architects can use the TOGAF framework and the ArchiMate language for

clarifying portal strategy, developing architecture and roadmaps, and driving agile

delivery

• The ArchiMate language can be adapted for different modeling challenges and

audiences


3535

Your Turn
