ADA - Architecture Blueprint For Solution or Technology Template v1.101

<Technology ABC or solution
ABC> Reference Architecture
Accenture Delivery Architecture
15/09/2015 , v0.120 -- DRAFT
Copyright © 2015 Accenture All rights reserved. 1

Executive Summary

Content
• <Solution ABC or Technology ABC> Vision

– Challenges
– Strawman
• <Solution ABC or Technology ABC> Reference Architecture Blueprint
– Non-Functional Requirements
– Principles
– Patterns
– Architecture Capabilities
– Architecture Components
– Architecture Views
• Case-Study
• Reference Implementation

<Solution ABC or Technology ABC> Challenges

Architecture Strawman of <Solution ABC or Technology ABC>
• Layer A 1. XXX
2. XX
Aa1 3. XX
• Layer B 1
Bb1 Bb2
• Layer C 3
Cc3

<Solution ABC or Technology ABC> Description
• Component Aa1
– Description
• Component Bb1
– Description
• Component Bb2
– Description
• Component Cc1
– Description

Content

– Challenges
– Strawman
– Principles
– Patterns
• Implementation Options
– Reference Implementation
– Project Case-Study

The Cube represents all key aspects of a Technology Blueprint:
Components Capabilities and Principles & Patterns
To support the elaboration of the Project Vision and

Strategy Solution, the Accenture Delivery Architecture
is structured as a cube with three dimensions Principles
– Principles & Patterns contains the set of principles and & Patterns
patterns to make, sponsor and enforce the right decisions
Components
to Deliver Architecture. This should guide Architect to
Capabilitie
formally agree, document the Technology Principles and
Key Technology Decisions.
s
– Capabilities contains the architecture capability reference
models to capture architecture needs to deliver
Architecture;
– Components contains the architecture component
reference models to consistently deliver architecture
based on past experience and emerging technologies.

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Functional and Non-Functional Requirements
To be successful, Technology Architects must

understand both types of requirements for the
solutions they are working on, and challenge Principles
unrealistic and very costly ones. & Patterns
Functional Requirements:
Components
Capabilitie
– are typically produced by Business teams, and tend to
focus on what an application should do;
s
– may sometimes “hide” technical requirements, e.g.
“should be always available” and “should immediately
respond” are actually ill-defined technical requirements
listed as functional ones.
Non-Functional Requirements:
– are usually produced by Technology people, and tend to
be expressed in clear, measurable ways;
– sometimes they are not available, so we have to define
assumptions

Template slide – Remove and replace by your content
Key Functional and Non-Functional Requirements
<Describe the key non-functional requirements Sample Architecture Framework for Non-
driving the solution> Functional requirements
Non-Functional requirements are are typically aligned
with Architecture Concerns (“- ilities”).
Some of the most frequently encountered concerns
include:
– Scalability: how many users or transactions can it process
concurrently?
– Performance: how fast does it respond? what is the max
throughput?
– Recoverability: how does the application recover from a
fault?
– Security: can it sustain attacks? is data protected?
– Maintainability: how easy is it to maintain?
– Operability: how easy is it to use and managed? how is it
operated?
– Availability: is it available 24×7? and is it 99.9% or 99.99%?

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Architecture Principles
An Architecture Principle is a statement of belief,

approach or intent which directs the formulation of
the architecture
Principles
Principles are guidelines for the construction of the
architecture:
Components
Capabilitie
– They are derived from or linked to the Architecture
assumptions, scope, constraints and objectives, or
s
Business mission / Strategy / Business objectives
– They will be used to justify the decisions made about the
patterns, components & capabilities in the architecture
– They will ensure that the architecture defined is consistent
and do not spread

Technology Architecture Principles are developed from
Architecture Principles and drive implementation
Strategy
Reference Business Principles for the Business Principles & Decisions chosen
L0
industry by the enterprise
Drives
Drives
Reference Architecture Usage of the Reference Architecture
Enterprise Architecture
Reference Enterprise Architecture Enterprise Architecture Principles &
L1
Principles for Cloud Integration Decisions chosen for the solution
Drives
Drives
Technology Architecture
Reference Technology Architecture Technology Architecture Principles &
L2
Principles for Cloud Integration Decisions chosen for the solution
Drives
Drives
Update to
Technology Design illustrate which
family of
principles are Design Principles & Decisions chosen
L3 Reference Design Principles
described
for the solution
Drives

Content

– Challenges
– Strawman
– Principles
– Patterns
• Implementation Options
– Reference Implementation
– Project Case-Study

Key Architecture Patterns
An Architectural Pattern (also called Architectural

Style or Application Style) defines types of elements
and relationships that work together and provide in
order to solve a particular problem. Patterns
An architecture pattern is not an architecture. It is a
Components
concept which defines the vocabulary, constraints and
Capabilitie
principles and how it can be combined with other
patterns.
s
ADA v4 categories Architecture Patterns in two types:
– Business Solution Pattern: a combination of Tech
Components (and/or patterns) to do something specific
for a given business use,
– Technical Solution Pattern: a typical combination of Tech
Components (and/or patterns) that can be used for
multiple business solutions
ADA v4 also define the Implementation patterns for
Run-time capability (also called Design Pattern),
Development and Operation capability.
The next slides provides X Business/Technical Solution
Patterns for <Solution ABC or Technology ABC>
Key solution pattern: Microservice

Overview Benefits / Force
• Strong Module Boundaries: Microservices reinforce modular structure,
The microservice is an approach to developing a single application as a suite of small which is particularly important for larger teams.
services, each running in its own process and communicating with lightweight mechanisms, • Independent Deployment: Simple services are easier to deploy, and since
often an HTTP resource API. they are autonomous, are less likely to cause system failures when they go
Microservice is an Technical Solution Pattern or software Application Style. wrong.
• Technology Diversity: With microservices you can mix multiple languages,
development frameworks and data-storage technologies.
Conceptual View
Risks & Issues
• Distribution: Distributed systems are harder to program, since remote calls
are slow and are always at risk of failure.
• Eventual Consistency: Maintaining strong consistency is extremely difficult
for a distributed system, which means everyone has to manage eventual
consistency.
• Operational Complexity: You need a mature operations team to manage lots
of services, which are being redeployed regularly.
Case Study
Netflix
• They handle over a billion calls per day to their video streaming API from over
800 different kinds of devices.
• Each microservice is quite simple, being focused on one business capability
Enabling Principles
Smart endpoints and dumb pipes. Applications built from microservices aim to be as • Each API call fans out to an average of six calls to backend services.
decoupled and as cohesive as possible - they own their own domain logic and act more as
filters in the classical Unix sense - receiving a request, applying logic as appropriate and Amazon.com
producing a response
• They originally had a two-tier architecture. In order to scale they migrated to a
Decentralized Governance and Data Management. Teams are responsible for all aspects of service-oriented architecture consisting of hundreds of backend services.
the software they build including operating the software 24/7.Decentralizing decisions about
• The Amazon.com website application calls 100-150 services to get the data
conceptual models and decentralize data storage decisions
that used to build a web page.
Design for failure. Any service call could fail due to unavailability of the supplier, the client
has to respond to this as gracefully as possible. This is a disadvantage compared to a
monolithic design as it introduces additional complexity to handle it.

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Architecture Capabilities
Capabilities are often designated as Business,

Technical or Functional
Principles
& Patterns
Architects defining the blueprint of an IT System are
responsible of identifying the Capabilities they need
Components
Capabilitie
to implement in the solution, and specifically
– Functional Capabilities, which are very solution- and
s
industry-dependent, and require industry expertise. In
general, Functional Capabilities are all Run-time
(Execution) Capabilities.
<Highlight key Functional capabilities>
– Technical Capabilities, which tend to be more
standardized. Technical Capabilities are usually grouped in
3 families, depending on when they are used:
Development Capabilities, Run-time (Execution)
Capabilities and Operations Capabilities.
<Highlight the key technical capabilities>

Capabilities Overview in <Solution ABC or Technology ABC>
Introduce Capabilities in <Solution ABC or Technology ABC> context
• Describe key Development

Development
Capabilities and their usage in
<Solution ABC or Technology
ABC>
• Describe key Runtime Capabilities

Runtime and their usage in <Solution ABC
or Technology ABC
• Describe key Operation

Operation Capabilities and their usage in
<Solution ABC or Technology ABC
Required Runtime Functional Capabilities for <Solution or

Technology ABC>
• Describe the functional capabilities for the Solution ABC or Technoloy ABC
Runtime Capability required Runtime Capability typically not required

Copyright © 2015 Accenture All rights reserved. Source : Accenture – Runtime Capability Architecture Reference Model v4 21
Required Runtime Architecture Capabilities for <Solution

or Technology ABC>
Technical Run-time (Execution) Capabilities
Presentation (User Interface) Capabilities Security Enforcement Capabilities
Identification & Identity & Access Confidentiality &

Authentication Cap. Management Cap. Compliance Cap.
If all top-level capabilities Identification Authorisation Encryption
are not required, remove (Transport & Storage)
them all and shade out the Identity & Digital

parent capability Authentication Access
Management
Signature
(incl. Non-Repudiation)
I&AM Transaction
Single Sign-on Federation Audit &
Traceability
Compliance
Validation
Shade out top-level

Step1: shade out
capabilities
componentsthat are
Processing Illustrative use the Visio ADA ARMs version
n/a & Logic Execution Capabilities Data Management & Integration Capabilities
not required
Logic Execution
Capabilities
Custom Code
Execution Control &
Failure Mgmt Cap.
Atomic
to create a fit to purpose version
Process Timing
Capabilities
Execution
Partitioning Cap.
Data Processing Capabilities Data Storage
Capabilities
Integration & Data Transport
End-point
Capabilities
Service Lookup
Execution https://kx.accenture.com/repositories/ContributionForm.aspx?path=C29/26/51&mode=Read&origin=search
(Transactional) Synchronous
Processing Clustering Data
Access
Encoding &
Decoding
Data
Caching Enablement & Indirection
(e.g. via JVM, Interpreter) Execution (for Services & APIs) (via Registry, Directory)
Workflow Resource Scheduled Data Data Enrichment Data Transport & Message
Execution Locking Processing Load-balancing Abstraction & Aggregation Persistence Delivery Routing
(e.g. Process Automation) (incl. Batch) (for Data & Messages)
Rule Auditing, Queued & Fail-over Data Data Data Transport Type Guaranteed
Interpretation Logging &
Tracing
Asynchronous
Processing (& fail-back) Validation RenameSchemaor Add additional
Transformation Indexing Bridging Delivery
capabilities required by the
(e.g. via Rule Engine) (incl. adapters)
(Complex) Event Interrupted

Execution Re- Real-Time Redundant
Execution Report solutionData
Compression & Data Publishing & Replication &
Correlation Start/Recovery Processing (for high-resiliency)
Generation Decompression Versioning Subscribing Synchronisation
Exception Stream Work Media Encoding, Data Sequencing &

Processing Partitioning Decoding & Partitioning & Automated Retry
Management (by region, user group,
Segregation Correlation
(image, video, etc.) via Map-Reduce...) Transcoding
Execution Multi-version
Profiling Parallel
Execution
Runtime Capability required Runtime Capability typically not required

Copyright © 2015 Accenture All rights reserved. Source : Accenture – Runtime Capability Architecture Reference Model v4 22
Presentation Capabilities
Presentation (User Interface) Capabilities
Describe L2 Capability in <Solution or Rendering & Interaction Capabilities Presentation Adaptation Capabilities Content Sourcing
Capabilities
UI (Web)
Technology X> context Composition &
Rendering
Form
Management Help Multi-channel
Presentation
Customisation
(by the user)
Content
Management
Session & State

Management
Input Validation
(incl. spell checking)
Illustrative
Notification
Management
use thePersonalisation
Responsive
Presentation
Visio
& Targeting ADA UI Layout &
Template
Illustrative
ARMs versionuse the Visio ADA
(for the user) Management
Conversation & Gesture Multi-variant &
Navigation
Management
Management &
Manipulation to create ARMs
AB a fit to
Testing
Enablement
version
Localisation
purpose
(incl. location
detection)
Content
Syndication
(incl. Drag & Drop, etc.)
Media Document &

to create a
version
Content fit to purpose Mash-ups &
Recognition &
Rendering &
Streaming
Page Generation
(e.g. for printing) version
Interpretation Accessibility
(OCR, Image, Voice, etc.)
Presentation
Integration
Capability (Level 3) Usage in <Solution or Technology ABC> Component(s)

Rendering & Interaction Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Presentation Adaptation Describe usage of L3 Capability. Introduce component(s) implementing the
Capability
Content Sourcing Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Required Typically not required

Security Enforcement Capabilities
Security Enforcement Capabilities

Describe L2 Capability in <Solution or
Identification & Identity & Access Confidentiality &
Technology X> context Authentication Cap. Management Cap. Compliance Cap.
Identification Illustrative
Authorisation Encryption
use the Visio (Transport
ADA & Storage)
ARMs version
to create
Identity a
& fit to purpose Digital
Authentication Access Signature
version
Management (incl. Non-Repudiation)
I&AM Transaction
Single Sign-on Federation Audit &
Traceability
Compliance
Validation

Identification & Describe usage of L3 Capability Introduce component(s) implementing the
Authentication Capability
Identity & Access Describe usage of L3 Capability. Introduce component(s) implementing the
Management Capability
Confidentiality & Describe usage of L3 Capability Introduce component(s) implementing the
Compliance Capability

Processing & Logic Execution Capabilities

Processing & Logic Execution Capabilities
Logic Execution Execution Control & Process Timing Execution
Technology X> context Capabilities
Custom Code
Failure Mgmt Cap.
Atomic
Capabilities Partitioning Cap.
Execution (Transactional) Synchronous Clustering

(e.g. via JVM, Interpreter) Execution Processing
Workflow Illustrative
Resource
use the Visio ADA
Scheduled
Execution Processing
Locking ARMs version Load-balancing
(e.g. Process Automation) (incl. Batch)
Rule to create a fit to

Auditing, purpose
Queued & Fail-over
Interpretation Logging & Asynchronous
(e.g. via Rule Engine) Tracing version Processing (& fail-back)
(Complex) Event Interrupted Real-Time Redundant

Correlation Execution Re- Processing Execution
Start/Recovery (for high-resiliency)
Exception Stream Work

Processing Partitioning
Management (image, video, etc.)
(by region, user group,
via Map-Reduce...)
Profiling Parallel
Execution

Logic Execution Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Execution Control & Describe usage of L3 Capability. Introduce component(s) implementing the
Failure Management Capability
Process Timing Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Execution Partitioning Describe usage of L3 Capability Introduce component(s) implementing the
Capability

Data Management & Integration Capabilities

Data Management & Integration Capabilities
Data Processing Capabilities Data Storage Integration & Data Transport
Technology X> context Capabilities
End-point
Capabilities
Service Lookup
Data Encoding & Data Enablement & Indirection
Access Decoding Caching (for Services & APIs) (via Registry, Directory)
Illustrative use the Visio Transport ADA&

Data Data Enrichment Data Delivery Message
Abstraction & Aggregation ARMs version
Persistence (for Data & Messages)
Routing
Data Data to create

Data
a fit to Transport
purpose Type Guaranteed
Validation Schema Indexing version (incl. Bridging Delivery
Transformation adapters)
Report Data Data Publishing & Replication &

Generation Compression & Versioning Subscribing Synchronisation
Decompression
Media Encoding, Data Sequencing &
Decoding & Partitioning & Correlation
Transcoding Segregation

Data Processing Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Data Storage Describe usage of L3 Capability. Introduce component(s) implementing the
Capability
Integration & Data Describe usage of L3 Capability Introduce component(s) implementing the
Transport Capability

Required DevOps Architecture Capabilities

for <Solution or Technology ABC>
Development & Operations Architecture Capabilities
Program & Project Management Capabilities Quality & Knowledge Management Capabilities IT Organisation, Asset & Service Management Capabilities
Planning & Project Management Resource & Collab. Agile Project

Capabilities Management Cap.s Management Cap.s
Deliv. Planning, Issue & Risk Staffing &
Scope & Release Management Resource
Management Planning
Progress Tracking Change Team
& Reporting Management & Collaboration
(incl. effort tracking) Control Enablement
Forecasting & Training &
Predictive Estimating Competency
Analysis Management
Productivity
Measurement &
Reporting
Illustrative use the Visio ADA ARMs version

Analysis & Design Capabilities Build & Test Capabilities Software Configuration & Release Management Capabilities Data Management Capabilities
Step1: shade out n/a
Analysis Enablement Software Generation Build & Integration Enablement Version, Release & Artefact Deployment Master, Reference & Data Quality Data Lifecycle Management
components
Capabilities Capabilities Capabilities Management Capabilities Capabilities Meta-data Mgt. Cap.s Management Cap.s Capabilities

Requirement Use Case/Story Code & Config. Software Build Version Continuous Del. Deployment Data Log & Audit
Capture Definition Writing Compilation & Orchestration Management Pipeline Orchestration Conversion & Trail
Enablement Enablement Validation (incl. branching) Management Migration Management
Requirement Prototyping, SW-Defined Software Linking Continuous Artefact Release Software Data Archiving Information
https://kx.accenture.com/repositories/ContributionForm.aspx?path=C29/26/51&mode=Read&origin=search
Validation Mock-ups & Infrastructure
& Packaging Management Integration
Distribution Management
& Retirement Security
Storyboarding Definition En.’t Enablement (incl. media) Management
Requirement AS-IS Code Generation Development Software VM & Container Data Retention
Traceability Assessment & Forward Environment Configuration Management & Management
Management Engineering Integration Management Distribution
Design Enablement Test Management Test Execution & Automation

Capabilities Capabilities Capabilities IT Operations Management Capabilities
Process Design Architecture Test Case & Functional Test UI Test
Enablement Design Script Creation & Enablement Enablement
Enablement Management System, Workstation & IaaS Management Performance & Availability Management Security Operations Management
Capabilities Capabilities Capabilities
UI Design Application Test Execution Unit Test Multi-Channel System & Server Environment(s) Capacity Performance Patch User Profile,
Enablement Design Tracking & Enablement Test Enablement Service Configuration & Configuration & Planning Tuning Management Ident. & Access
Enablement Reporting (incl. multi-browser) Monitoring Management Management Management
Development-
relevant Capabilities
Media Creation Environment(s) Test Data Service & API Security Test Semantic Workstation Performance Availability & Anti-Virus System
Enablement Specification Creation & Test Enablement Enablement Monitoring Configuration & Modelling Performance Management Hardening
(e.g. images, video) Enablement Management Management Monitoring Management Development &
Operations-
relevant
Data Modelling Performance Automation & IaaS Backup, Restore Performance IT Capacity Threat Security Capabilities
& Design Test Enablement Scheduling Configuration & & Archival Profiling Management Detection & Monitoring
Enablement (batch, scripts, etc.) Management Management
Operations-relevant
Capabilities
Environments
Build Environments Test Environments Production Environments Maintenance Environments
Development Unit Test Prototype & PoC System Test External User Acceptance Performance & Operational Live Disaster Recover Pilot Training Fix Development Fix Test
Environment(s) Environment(s) Environment(s) Environment(s) Integration Test Test Scalability Test Readiness Test Environment(s) Environment(s) Environment(s) Environment(s) Environment(s) Environment(s)
Environment(s) Environment Environment Environment
DevOps Capability required DevOps Capability typically not required

Copyright © 2015 Accenture All rights reserved. Source : Accenture – Development & Operations Capability Architecture Reference Model V4 27
Program & Project Management
Describe L2 Capability in Program & Project Management Capabilities
<Solution or Technology X> Planning & Project Management Resource & Collab. Agile Project
Capabilities Management Cap.s Management Cap.s
context Deliv. Planning, Issue & Risk Staffing &
Scope & Release Management Illustrative use the Visio ADA
Resource
Management Planning
ARMs version
Progress Tracking Change to create a fit to purpose
Team
& Reporting Management & Collaboration
(incl. effort tracking) Control version
Enablement
Forecasting & Training &
Predictive Estimating Competency
Analysis Management
Productivity
Measurement &
Reporting

Planning & Project Describe usage of L3 Capability Introduce component(s) implementing the
Resource & Describe usage of L3 Capability. Introduce component(s) implementing the
Collaboration Capability
Management
Agile Project Describe usage of L3 Capability. Introduce component(s) implementing the


Quality & Knowledge Management
Describe L2 Capability in <Solution or Technology X> Quality & Knowledge Management Capabilities
context Quality Management Knowledge & Colllab.

Capabilities Management Cap.s
Quality Assurance Policies &
Illustrative use the Visio ADAStandards
& Reviews
(incl. QA & peer reviews) Management
ARMs version
to create a fit to purpose IT Knowledge
Defect Tracking
version
& Management Management
Methodology IT Collaboration
Compliance Management
Management
Static SW
Analysis
Enablement

Quality Management Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Knowledge & Describe usage of L3 Capability. Introduce component(s) implementing the
Collaboration Capability
Management

IT Organization, Asset & Service Management

IT Organisation, Asset & Service Management Capabilities
Describe L2 Capability in <Solution IT Governance IT Asset Management Service Management Service Operation
or Technology X> context IT Service
Capabilities
IT Financial
Cap.s
IT Asset IT Service
Capabilities
IT Service
Capabilities
Portfolio Management Inventory & Catalogue Continuity Service Desk

Management Lifecycle Mgmt Management Management
IT Operations
Intelligence & IT Supplier
Management
IT Asset
Illustrative
Configuration use the Visio
Compliance
Management
Business
ADA
Service Level Event
Management
Analytics Management Management
ARMs version
Continuous IT Asset Usage Service Usage
Improvement IT Resource
Management Metering/ to create a fit
Metering and to purpose
Availability
Management
Incident
Management
Management Profiling Billing
IT Risk IT Facilities
version IT Service Level Problem
Management Management Management Management

IT Governance Describe usage of L3 Capability Introduce component(s) implementing the
Capability
IT Asset Management Describe usage of L3 Capability. Introduce component(s) implementing the
Capability
Service Management Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Service Operation Describe usage of L3 Capability. Introduce component(s) implementing the
Capability

Analysis & Design
Describe L2 Capability in <Solution Analysis & Design Capabilities
or Technology X> context Analysis Enablement Design Enablement

Capabilities Capabilities
Requirement Use Case/Story Architecture
Capture DefinitionIllustrative Process
use theDesign
Visio ADA Design
Enablement
Enablement Enablement
ARMs version
Requirement Prototyping, to create aUIfitDesign
to purpose Application
Mock-ups & Design
Validation Storyboarding version
Enablement Enablement
Requirement AS-IS Media Creation Environment(s)

Traceability Assessment Enablement Specification
Management (e.g. images, video) Enablement
Data Modelling
& Design
Enablement

Analysis Enablement Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Design Enablement Describe usage of L3 Capability. Introduce component(s) implementing the
Capability

Build & Test

Build & Test Capabilities
Describe L2 Capability in <Solution or Technology X> context Software Generation
Capabilities
Build & Integration Enablement
Capabilities
Code & Config. Software Build
Writing Compilation & Orchestration
Enablement Validation
SW-Defined Software Linking Continuous
Infrastructure Integration
Illustrative use the
Definition En.’t Visio ADA
& Packaging Enablement
ARMsEngineering
version Environment
Code Generation
& Forward
Development
Integration
to create a fit to purpose
version
Test Management
Capabilities
Test Execution & Automation
Capabilities
Test Case & Functional Test UI Test
Script Creation & Enablement Enablement
Management
Test Execution Unit Test Multi-Channel
Tracking & Enablement Test Enablement
Reporting (incl. multi-browser)
Test Data Service & API Security Test

Creation & Test Enablement Enablement
Management
Performance
Test Enablement

Software Generation Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Build & Integration Describe usage of L3 Capability. Introduce component(s) implementing the
Enablement Capability
Test Management Describe usage of L3 Capability Introduce component(s) implementing the
Capability
Test Execution & Describe usage of L3 Capability Introduce component(s) implementing the
Automation Capability

Software Configuration & Release Management
Describe L2 Capability in <Solution or Software Configuration & Release Management Capabilities

Technology X> context
Version, Release & Artefact Deployment
Management Capabilities Capabilities
Version Illustrative
Continuous Del. use the Visio ADA
Management Pipeline Deployment
ARMs version Orchestration
(incl. branching) Management
Artefact version
Management Release Software
(incl. media)
Management Distribution
Software VM & Container

Configuration Management &
Management Distribution

Version, Release & Describe usage of L3 Capability Introduce component(s) implementing the
Artefact Management Capability
Deployment Capabilities Describe usage of L3 Capability. Introduce component(s) implementing the
Capability

Data Management
Describe L2 Capability in <Solution Data Management Capabilities
or Technology X> context Master, Reference & Data Quality Data Lifecycle Management
Meta-data Mgt. Cap.s Management Cap.s Capabilities
Data Log & Audit
Illustrative use the Visio
Conversion & ADA Trail
Migration Management
ARMs version
to create Data
a fit Archiving
to purpose Information
Security
& Retirement
version Management
Data Retention
Management

Master & Reference Describe usage of L3 Capability Introduce component(s) implementing the
Data Management Capability
Data Quality Describe usage of L3 Capability. Introduce component(s) implementing the
Data Lifecycle Describe usage of L3 Capability Introduce component(s) implementing the

IT Operation Management
IT Operations Management Capabilities
Describe L2 Capability in <Solution or Technology X> System, Workstation & IaaS Management
Capabilities
context System &
Service
Server
Configuration &
Environment(s)
Configuration &
Monitoring Management Management
Illustrative
Semantic
Monitoring
use the
Workstation
Configuration & Visio ADA
Management
Automation &
ARMs IaaS
version
Backup, Restore
Scheduling
to create
(batch, scripts, etc.) Management to purpose
a fit
Configuration & & Archival
version
Performance & Availability Management Security Operations Management
Capabilities Capabilities
Capacity Performance Patch User Profile,
Planning Tuning Management Ident. & Access
Management
Performance Availability & Anti-Virus System

Modelling Performance Management Hardening
Monitoring Management
Performance IT Capacity Threat Security

Profiling Management Detection & Monitoring
Management

System, Workstation & Describe usage of L3 Capability Introduce component(s)
IaaS Management implementing the
Capability
Performance & Describe usage of L3 Capability. Introduce component(s)

Availability Management implementing the
Capability
Security Operations Describe usage of L3 Capability Introduce component(s)

Management implementing the
Capability

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Architecture Components
Components are the actual building blocks of your

Solution, They can be:
– Technology Components, i.e. hardware, network, Principles
packaged or custom software, configuration, etc.; & Patterns
– Processes, including Task, Activities, etc. performed by
Components
people and;
Capabilitie
– People, who perform the Tasks & Activities and use the
Solution Components.
s
Most business Solutions will be built on a
combination of Technology, Processes and People.
In some cases a Capability can be delivered without
any People (if it’s really fully automated) or without
Technology Components (if it’s really fully manual).

Architecture Components Overview in <Solution ABC or

Technology ABC>
Introduce components required for <Solution ABC or Technology ABC>
• Describe key Applications and their usage in

Application <Solution ABC or Technology ABC>
• Describe key Applications and their usage in

Data <Solution ABC or Technology ABC>
• Describe key Platform Components and their

Platform usage in <Solution ABC or Technology ABC>
• Describe key Infrastructure Components and

Infrastructure their usage in <Solution ABC or Technology
ABC>

Identify the applications components and the logical

decomposition of application components
• Define and Identify the solution-specific and non-

solution-specific application components
• Define the decomposition of application
components in sub-components (when applicable)
• Decide and/or document the Package Buy vs
Cloud Buy vs Build for each application component
Application Usage in Solution X Vendors / Products

Component
<Component name> <Describe what is specific or not in the context of Solution X > <Vendors>, <Vendors>
Describe what is Describe the

specific with this vendor/product
component and the component or custom
attention points technology used for
implementation

Identify and list the key data entities in the solution
• Define and Identify the key data entities

used/owned/produced by the solution
• Categorize each data entity. And, more specifically
identify the data types, data structure types and
data states for each data entity.
• Identify which component owns the data,
capture/produce the data and consume the data
Key Data Entity Usage in Solution X Characteristic

<Key Data Entity> <Describe what is specific or not in the context of Solution X > <Key characteristic>
Describe the usage in

the solution. This Describe the key
should be extended in characteristic of each
later stage with which data entity.
application component And, more specifically
consume / produce / the data types, data
own the data structure types and
data states

Required Platform Components for <Solution or

Technology ABC>
Platform Components
Presentation Components Logic Execution Components Integration Components Data & Reporting Components
Web Intermediation Software Automation Software Integration Software Reporting Sofware
Web Caching Transcoding EAI Message

Server SW Server SW Server SW Brokers
(incl. CDNs)
Proxy Access Managed File

Server SW Management & ESBs Transfer SW
SSO SW (e.g. FTP)
If all top-level
capabilities are not API Service
required, remove them
Presentation Software Code Execution Server Software Management Directory SW Data Management Software
all and shade out the SW
parent capability
Web Content Language Virtual
Web Browsers Management Application Machines & ETL SW EDA & CEP MDM Search & ECM

Server SW Server SW Code Containers Server SW Server SW Server SW
Web Portal& Language Process Gateway Data Caching Enterprise

Server SW Collaboration
Server SW to create a fit to purpose version
Interpreters &
JIT Compilers
Partitioning
Server SW Server SW Server SW Archiving SW
Media
Streaming Search &
Presentation Frameworks & Libraries Indexing SW
ShadeRun-time
out n/aFrameworks & Libraries Integration Frameworks & Libraries Server SW
components
Multi-channel User Workflow Persistency Utility Integration
Frameworks Frameworks Frameworks Libraries Adapters Libraries
(e.g. MVC) Data Stores
Mash-up Augmented & Batch E2E Run-time Relational In-Memory

Frameworks Virtual Reality Frameworks Frameworks DBMSs Data Store SW
Support SW (e.g. JEE, .NET)
Speech No-SQL Directory

Recognition & Server SW Server SW
Generation SW (incl. Graph DB SW) (e.g. LDAP)
Datawarehouse Digital Asset

Server SW Management
SW
Operating Systems & Cloud Enablement Software
File Server SW GIS
Operating Systems Cloud Enablement Software Server SW
(incl. the container and the control & auto-scaling SW)
Server OSs Desktop Tablet & Phone Embedded & Cloud PaaS IaaS
(incl. Mainframes) (& Laptop) OSs OSs Autonomous Management Enablement Enablement
Device OSs Software Software Software
Copyright © 2015 Accenture All rights reserved. Source : Accenture – Platform Component Architecture Reference Model V4 41
Presentation Components
Presentation Components
Describe L2 Component in <Solution or Technology X> Web Intermediation Software
Web Caching Transcoding

context Server SW
(incl. CDNs)
Server SW
Proxy Access
Management &
Illustrative use the Visio ADAServer SW SSO SW
ARMs version Presentation Software
to create a fit to purposeWeb Browsers Management

Web Content
Server SW
version Web Portal&
Server SW Collaboration
Server SW
Presentation Frameworks & Libraries
Multi-channel User Workflow

Frameworks Frameworks
(e.g. MVC)
Mash-up Augmented &

Frameworks Virtual Reality
Support SW
Speech
Recognition &
Generation SW
Component (Level 3) Usage in <Solution or Technology ABC> Vendor(s) & Products

Web Intermediation Describe usage of Component Introduce Vendor(s) and
Software Product(s)
Presentation Software Describe usage of Component Introduce Vendor(s) and
Product(s)
Presentation Describe usage of Component Introduce Vendor(s) and
Frameworks & Libraries Product(s)

Logic Execution Components

Logic Execution Components
Describe L2 Component in <Solution or Technology X> Automation Software
Workflow & Orchestration

context BPM Server SW Server SW
Business Rule Cognitive

Illustrative use the Visio ADA Engines Computing SW
ARMs version Code Execution Server Software
to create a fit to purpose Application

Server SW
Language Virtual
Machines &
Code Containers
version Language Process
Interpreters & Partitioning
JIT Compilers Server SW
Run-time Frameworks & Libraries
Persistency Utility
Frameworks Libraries
Batch E2E Run-time

Frameworks Frameworks
(e.g. JEE, .NET)

Automation Software Describe usage of Component Introduce Vendor(s) and
Product(s)
Code Execution Server Describe usage of Component Introduce Vendor(s) and
Product(s)
Runtime Frameworks & Describe usage of Component Introduce Vendor(s) and
Libraries Product(s)

Integration Components
Integration Components
Describe L2 Component in <Solution or Technology X> Integration Software
EAI Message
context Server SW Brokers
Managed File
ESBs Transfer SW
Illustrative use the Visio ADA (e.g. FTP)
API
ARMs version Management
SW
Service
Directory SW
to create a fit to purpose ETL SW EDA & CEP

Server SW
version Gateway
Server SW
Integration Frameworks & Libraries
Adapters Integration
Libraries

Integration Software Describe usage of Component Introduce Vendor(s) and
Product(s)
Integration Frameworks Describe usage of Component Introduce Vendor(s) and
& Libraries Product(s)

Data & Reporting Components
Describe L2 Component in <Solution or Technology X>

context
Illustrative use the Visio ADA
ARMs version
version

Reporting Software Describe usage of Component Introduce Vendor(s) and
Product(s)
Data Management Describe usage of Component Introduce Vendor(s) and
Software Product(s)
Data Stores Describe usage of Component Introduce Vendor(s) and
Product(s)

Operating Systems & Cloud Enablement Software
Describe L2 Component in <Solution or Technology X>

context
Operating Systems & Cloud Enablement Software ARMs version
Operating Systems
Cloud Enablement Software
versionthe control & auto-scaling SW)
(incl. the container and
Server OSs Desktop Tablet & Phone Embedded & Cloud PaaS IaaS
(incl. Mainframes) (& Laptop) OSs OSs Autonomous Management Enablement Enablement
Device OSs Software Software Software

Operating Systems Describe usage of Component Introduce Vendor(s) and
Product(s)
Cloud Enablement Describe usage of Component Introduce Vendor(s) and
Software Product(s)

Required Infrastructure Components for <Solution or Technology

ABC>
Infrastructure Components
Computing Components Network Components Storage Components

(Physical & Virtualised) (Physical & Virtualised)
End-User Back-end Autonomous Network Hardware Physical Network Storage Hardware Storage Supports
Computers Computers Computing Devices Connectivity Comps.
Personal Hubs & Directly- Direct Access
Computers Servers Mobile Phones Switches Cabling Attached Drives Storage
(incl. HDs and SSDs) Volumes
If all Mainframes
top-level Wearable Routers, Bridges Modems NASs Long-term
Workstations Computing & Gateways (Wire-line, Wireless, (Network-Attached Storage Volumes
capabilities are not Devices (incl. Access Points) Power-line, etc.) Storage) (e.g. AWS Glacier)
required, remove them
all and shade out the Smart Network
Interfaces SANs Removable
Laptops parentBlade Servers
capability Devices (Wire-line, Wireless, Antennas (Storage Area Disks
(e.g. Domotics) NFC, etc.) Networks) (incl. SSDs, USB Drives)
Tablets
Massively
Parallel
Computers
Embedded
Computers Load Balancers
CTI Hardware
(Computer-Telephony
Integration)
Removable
Disk Drives
(e.g. FDs, HD bays)
Tapes
Kiosks Platform
Appliances
Micro-Servers
Intrusion
Prevention & Tape Drives
Optical Media
(e.g. CD, DVD, Blu-Ray
Detection Sys. disks)
Shade out n/a Optical Drives

components Robots Firewalls (e.g. CD, DVD, Blu-Ray
drives)
Computing Accessories Data Centre Infrastructure Components
Peripherals Sensors & Actuators Data Centre Facility Components Data Centre Equipment
Displays Environmental Location HVAC

Printers (Monitors, Projectors, Sensors Detectors Data Centre Secure Physical (Heating, Ventilation, Power Supply
(2D & 3D) Wearable Displays)
(Temperature,
(GPS, Beacons, etc.)
Space Storage Space Air Conditioning) & UPS
Magnetic field, etc.)
Mice & Image & Video Biometric Modular Data Physical Access Facility
Keyboards Capture Devices Readers Actuators Centres Control Devices Maintenance Racks
(Fingerprint, Iris, etc.) (DC-in-a-Box) Equipment
Scanners Microphones RFID Detectors

& Tags
Copyright © 2015 Accenture All rights reserved. Source : Accenture – Infrastructure Component Architecture Reference Model V4 47
Computing Components
Computing Components
(Physical & Virtualised)
Describe L2 Component in <Solution or Technology X> End-User Back-end Autonomous
Computers Computers Computing Devices
context Personal Servers Mobile Phones
Computers
Wearable
ARMs version
Workstations Mainframes Computing
Devices
to create a fit to purpose Smart
Laptops
version
Blade Servers Devices
(e.g. Domotics)
Massively Embedded
Tablets Parallel Computers
Computers
Kiosks Platform Micro-Servers

Appliances
Robots

End-User Computers Describe usage of Component Introduce Vendor(s) and
Product(s)
Back-end Computers Describe usage of Component Introduce Vendor(s) and
Product(s)
Autonomous Computing Describe usage of Component Introduce Vendor(s) and
Devices Product(s)

Network Components
Network Components
(Physical & Virtualised)
Describe L2 Component in <Solution or Technology X> Network Hardware Physical Network
Connectivity Comps.
context Hubs & Cabling
Switches
Routers, Bridges Modems
ARMs version
& Gateways (Wire-line, Wireless,
Power-line, etc.)
(incl. Access Points)
to create a fit toNetwork
purpose
version Interfaces
(Wire-line, Wireless,
NFC, etc.)
Antennas
CTI Hardware
Load Balancers (Computer-Telephony
Integration)
Intrusion
Prevention &
Detection Sys.
Firewalls

Network Hardware Describe usage of Component Introduce Vendor(s) and
Product(s)
Physical Network Describe usage of Component Introduce Vendor(s) and
Connectivity Product(s)

Storage Components
Storage Components
Describe L2 Component in <Solution or Technology X> Storage Hardware Storage Supports
context Directly-
Attached Drives
Direct Access
Storage
(incl. HDs and SSDs) Volumes
Illustrative use the VisioNASs
ADA Long-term
ARMs version
(Network-Attached
Storage)
Storage Volumes
(e.g. AWS Glacier)

SANs Removable
(Storage Area Disks
version Networks) (incl. SSDs, USB Drives)
Removable
Disk Drives Tapes
(e.g. FDs, HD bays)
Optical Media
Tape Drives (e.g. CD, DVD, Blu-Ray
disks)
Optical Drives
(e.g. CD, DVD, Blu-Ray
drives)

Storage Hardware Describe usage of Component Introduce Vendor(s) and
Product(s)
Storage Support Describe usage of Component Introduce Vendor(s) and
Product(s)

Computing Accessories
Computing Accessories
Describe L2 Component in <Solution or
Peripherals Sensors & Actuators
Displays Environmental Location
Printers Sensors
(2D & 3D) Illustrative use the
(Monitors, Projectors,
Wearable Displays)
Visio ADA(GPS,Detectors
(Temperature,
Beacons, etc.)
Magnetic field, etc.)
ARMs version
Mice & to create a fit Biometric
Image & Video to purpose
Readers Actuators
Keyboards Capture Devices
version
(Fingerprint, Iris, etc.)
Scanners Microphones RFID Detectors

& Tags

Peripherals Describe usage of Component Introduce Vendor(s) and
Product(s)
Sensors & Actuators Describe usage of Component Introduce Vendor(s) and
Product(s)

Data Centre Infrastructure Components
Data Centre Infrastructure Components

Describe L2 Component in <Solution or
Data Centre Facility Components Data Centre Equipment
Data Centre Secure Physical HVAC Power Supply
Space Storage Illustrative
Space use theVentilation,
(Heating, Visio ADA
Air Conditioning) & UPS
ARMs version
Modular Data
Centres to create a Maintenance
Physical Access fit Facility
to purpose Racks
Control Devices
(DC-in-a-Box) version
Equipment

Data Centre Facility Describe usage of Component Introduce Vendor(s) and
Product(s)
Data Centre Equipment Describe usage of Component Introduce Vendor(s) and
Product(s)

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Runtime Architecture View
• Draw as many views of the Runtime Architecture as required (Application, Data, Platform,
Infrastructure)
• Duplicate this slide for each of the view
Legend
Name <Solution or Technology ABC> Runtime Architecture
Roles / Stakeholders
Target Why ? What is the intent?
Purpose Designing | Deciding | Informing
Abstraction Levels Details | End-to-End | Executive
Accenture Cube Technology Cube v4
Component Layer(s) Application | Data | Platform | Infrastructure Application
Capability Layer(s) Runtime Component
Pattern Cloud to On-Premise using On-Premise ESB
Runtime Capability

DevOps Architecture View
• Draw as many views of the DevOps Architecture as required (Application, Data, Platform,
Infrastructure)
Legend
Name <Solution or Technology ABC> DevOps Architecture
DevOps Capability

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Implementation Option: Client A case-study
Context Key Client Requirements
• What are the problems client tries to solve ? • Describe the Key Client Requirements
• What are the objectives of the project and
the expected benefits ?
• What are the key aspects of the solution ? Key Client Principles
• List the Principles, usually provided by the

Client Enterprise Architecture Team and/or
Client Program Management Team
Key Project Principles
• List the Principles from the Accenture Project

Team

Case-study: Key Functional and Non-Functional

Requirements
<Describe the key non-functional requirements Sample Architecture Framework for Non-
driving the solution> Functional requirements
Non-Functional requirements are are typically aligned
with Architecture Concerns (“- ilities”).
Some of the most frequently encountered concerns
include:
– Scalability: how many users or transactions can it process
concurrently?
– Performance: how fast does it respond? what is the max
throughput?
– Recoverability: how does the application recover from a
fault?
– Security: can it sustain attacks? is data protected?
– Maintainability: how easy is it to maintain?
– Operability: how easy is it to use and managed? how is it
operated?
– Availability: is it available 24×7? and is it 99.9% or 99.99%?

Case-study: Key Architecture Principles
• The key business principles driving the <Solution ABC or Technology ABC> are:
– <Describe the 5-7 key business principles / drivers>
• The Architecture Principles driving the <Solution ABC or Technology ABC> are:
– <Architecture Principles: embody the spirit and thinking of existing enterprise principles or solution
principles>
– <Format map of principles / list of principles>
Architecture
Architecture
Principles
Requirements
Meets Design
Instructions

Case-study: Vendor(s) profile

Case-study: Runtime Architecture Capabilities Heatmap
Partially
Provided Not provided
provided
Copyright © 2015 Accenture All rights reserved. Source : Accenture – ARM for Runtime Architecture 61
Case-study: Key Runtime Capabilities Gaps & Mitigations

Processing & Logic Execution Capabilities Data Management & Integration Capabilities
Logic Execution Execution Control & Process Timing Execution Data Processing Capabilities Data Storage Integration & Data Transport
Capabilities Failure Mgmt Cap. Capabilities Partitioning Cap. Capabilities Capabilities
Custom Code Atomic Synchronous Data Encoding & Data End-point Service Lookup
Execution (Transactional) Processing Clustering Access Decoding Caching Enablement & Indirection
(e.g. via JVM, Interpreter) Execution (for Services & APIs) (via Registry, Directory)
Workflow Resource Scheduled Data Data Enrichment Data Transport & Message
Execution Locking Processing Load-balancing Abstraction & Aggregation Persistence Delivery Routing
Illustrative
(e.g. Process Automation) (incl. Batch) (for Data & Messages)
Rule Auditing, Queued & Fail-over Data Data Data Transport Type Guaranteed
Interpretation Logging & Asynchronous (& fail-back) Validation Schema Indexing Bridging Delivery
(e.g. via Rule Engine) Tracing Processing Transformation (incl. adapters)
(Complex) Event Interrupted Real-Time Redundant Report Data Data Publishing & Replication &
Correlation Execution Re- Processing Execution Generation Compression & Versioning Subscribing Synchronisation
Start/Recovery (for high-resiliency) Decompression
Exception Stream Work Media Encoding, Data Sequencing &

Processing Partitioning Decoding & Partitioning &
Management (image, video, etc.)
(by region, user group,
Transcoding Segregation Correlation
via Map-Reduce...)
Profiling Parallel
Execution
Partially Provided (Key) Potential Gap Mitigation

Capability
Key Runtime Capability

Case-study: Platform Fit-for-Purpose Heatmap
Fit Partially Fit No Fit
Case-study: Platform Gaps & Mitigation

Capability
Case-study: Infrastructure Fit-for-Purpose Heatmap
Fit Partially Fit No Fit
Case-study: Infrastructure Gaps & Mitigation

Capability
Case-study: Runtime Architecture View
• Draw as many views of the Runtime Architecture as required (Application, Data, Platform,
Infrastructure)
• Map Vendor’s Software and other products, to the Components of the view
Legend
Name <Solution or Technology ABC> Runtime Architecture
Runtime Capability

Case-study: DevOps Architecture View
• Draw as many views of the DevOps Architecture as required (Application, Data, Platform,
Infrastructure)
• Map Vendor’s Software and other products, to the Components of the view
Legend
Name <Solution or Technology ABC> DevOps Architecture
DevOps Capability

Case-study: Lessons Learned & Recommendations
• Describe the Lessons Learned from this project, and the related recommendations

Content

– Challenges
– Strawman
– Principles
– Patterns
• Case-Study

Reference Implementation of <Solution ABC or Technology ABC>
• Describe where to find the reference implementation, what has been done, what can be used on
project to jumpstart the delievry.

Contacts
• ADA Leads
– Ezio Armando (Architecture Excellence Global Lead)
– Olivier Fortin (ADA Development Lead)
• Capability Development Team

– Mickie Moore
– Joyce Manuel-Casambros

ADA - Architecture Blueprint For Solution or Technology Template v1.101

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ADA - Architecture Blueprint For Solution or Technology Template v1.101

Uploaded by

Copyright:

Available Formats

<Technology ABC or solution

ABC> Reference Architecture

Accenture Delivery Architecture

15/09/2015 , v0.120 -- DRAFT

Copyright © 2015 Accenture All rights reserved. 1

Copyright © 2015 Accenture All rights reserved. 2

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 3

Copyright © 2015 Accenture All rights reserved. 4

Copyright © 2015 Accenture All rights reserved. 5

Copyright © 2015 Accenture All rights reserved. 6

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 7

To support the elaboration of the Project Vision and

Copyright © 2015 Accenture All rights reserved. 8

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 9

To be successful, Technology Architects must

Copyright © 2015 Accenture All rights reserved. 10

Key Functional and Non-Functional Requirements

Copyright © 2015 Accenture All rights reserved. 11

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 12

An Architecture Principle is a statement of belief,

Copyright © 2015 Accenture All rights reserved. 13

Copyright © 2015 Accenture All rights reserved. 14

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 15

An Architectural Pattern (also called Architectural

Key solution pattern: Microservice

Copyright © 2015 Accenture All rights reserved. 17

• <Solution ABC or Technology ABC> Vision

Copyright © 2015 Accenture All rights reserved. 18

Capabilities are often designated as Business,

Copyright © 2015 Accenture All rights reserved. 19

Capabilities Overview in <Solution ABC or Technology ABC>

Introduce Capabilities in <Solution ABC or Technology ABC> context

• Describe key Development

• Describe key Runtime Capabilities

• Describe key Operation

Required Runtime Functional Capabilities for <Solution or

Runtime Capability required Runtime Capability typically not required

Required Runtime Architecture Capabilities for <Solution

Presentation (User Interface) Capabilities Security Enforcement Capabilities

Identification & Identity & Access Confidentiality &

them all and shade out the Identity & Digital

Shade out top-level

(Complex) Event Interrupted

Exception Stream Work Media Encoding, Data Sequencing &

Runtime Capability required Runtime Capability typically not required

Session & State

Media Document &

Capability (Level 3) Usage in <Solution or Technology ABC> Component(s)

Required Typically not required

Security Enforcement Capabilities

Security Enforcement Capabilities

Capability (Level 3) Usage in <Solution or Technology ABC> Component(s)

Required Typically not required

Processing & Logic Execution Capabilities

Execution (Transactional) Synchronous Clustering

Rule to create a fit to

(Complex) Event Interrupted Real-Time Redundant

Exception Stream Work