theknowledgeacademy
Enterprise Architecture
Black Belt
About Us
theknowledgeacademy
The world's largest provider of classroom and
online training courses
✓ World Class Training Solutions
✓ Subject Matter Experts
✓ Highest Quality Training Material
✓ Accelerated Learning Techniques
✓ Project, Programme, and Change Management, ITIL®
Consultancy
✓ Bespoke Tailor Made Training Solutions
✓ PRINCE2®, MSP®, ITIL®, Soft Skills, and More
theknowledgeacademy
Objectives
1. To provide Enterprise Architects with a broad
framework that covers the range of architecture work
that precedes and steers system development, and to
focus attention on areas where the Architect is
responsible for effective design and risk management
2. To provide Architects with a vendor neutral grasp of
the terms, concepts, structures, and processes used in
developing Enterprise Architecture
3. To help candidates prepare for the Black Belt exam
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:3
theknowledgeacademy
Introductions
• Name/Role/Company
• Experience in
Enterprise Architecture
• Course Objectives
• One thing of interest
about yourself
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:4
theknowledgeacademy
The Course at a Glance
Day 1
Day 3
•
•
•
•
•
•
Architecture and Architects
Enterprise Architecture Principles
Establishing Enterprise
Architecture
Architecture Frameworks
•
Applications Architecture
Infrastructure
Architecture
Black Belt Exam
Day 2
•
•
•
•
•
Architecture Management
Architecture Precursors
Architecture Domains
Business Architecture
Data Architecture
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:5
theknowledgeacademy
The Exam
•
•
•
•
•
1 Hour
30 Questions
Multiple choice
Pass Mark 66%
Usually scheduled on
the afternoon of the last
day
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:6
theknowledgeacademy
Tools
• Course workbook
• Case study
o Optional Exercises
• Class discussion
• Class experience
• Evening work
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:7
theknowledgeacademy
Course Workbook
• Presentation slides
(arranged in day order)
• Appendix A: Case Study &
Optional Exercises
• Appendix B: Practice
Questions & Answers
• Appendix C: Architecture
Frameworks
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:8
theknowledgeacademy
Day 1 Agenda
• Architecture and Architects
• Enterprise Architecture
Principles
• Establishing Enterprise
Architecture
• Architecture Frameworks
• Evening Work
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:9
theknowledgeacademy
Architecture and Architects
•
•
•
•
What is an Enterprise?
Architecture granularity
Architecture domains
Hierarchical/layered
architecture
• Architect roles, goals, and skills
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:10
theknowledgeacademy
What is an Enterprise?
• Enterprise defined
• What do we mean by
“architecture”?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:11
theknowledgeacademy
Enterprise Defined
• A group of organisations that share common goals and
information
• Organisations can be anything from teams, to divisions, to
separate businesses
• Examples:
o
o
o
o
The government
Armed forces
Large corporations
Multi-national organisations
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:12
theknowledgeacademy
What do we mean by “Architecture”?
•
•
•
In the IT/Business Architecture viewpoint an architecture
“describes the fundamental organisation of a system embodied in
its components, their relationships to each other, and to the
environment, and the principles guiding its design and evolution”
Documentation describing the structure (components) and
behaviour (processes) of a system. A detailed plan of the system to
guide its implementation
The process for describing the architecture of a system to meet
given requirements and under given constraints
Descriptions based on IEEE-1471-2000 [01]
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:13
theknowledgeacademy
What is an Architecture Framework?
• A structured collection of guidance and techniques
• A methodology, designed to help people create
architecture descriptions and use them to good effect
• A comprehensive framework contains:
o A development process (a process framework)
o A classification of architecture descriptions (a content or
documentation framework)
o Advice on organisation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:14
theknowledgeacademy
What does an Architect do?
• Architect
o One whose responsibility is the design of an architecture and
the creation of an architectural description
• Architectural description
o A collection of products (artifacts) that document an
architecture from a conceptual viewpoint
Descriptions based on IEEE-1471-2000 [01]
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:15
theknowledgeacademy
Architecture Granularity
• Enterprise Architecture
• Domain Architecture
• Solutions Architecture
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:16
theknowledgeacademy
The Architect Role
•
An Architect is:
o
o
o
•
An individual who designs structures and supervises planning and
construction
An individual who describes the architecture of a system in enough detail for
work to be planned and thorough design and construction to continue
Governs the building work
Architecture is granular so there are several different types of
Architect each with their own:
o
o
o
o
Definition of a structure
Specific goals
Knowledge
Skill sets
Note: In this context, the term “Architect” is used to describe the work and roles that catalogue,
model, and plan for change to the high-level business systems and the information systems that
support them (not work and roles related to buildings). Legally you should not describe yourself as
an “Architect” without a qualifier as you would be representing yourself as a “traditional”
Architect (one who architects buildings)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:17
theknowledgeacademy
Architecture Granularity
•
•
Technology/
Infrastructure
Applications
© The Knowledge Academy Ltd
Information/
Enterprise Architecture Black Belt
Domain Architecture
Data
•
Enterprise Architecture
Business
•
A scale that ranges from
coarse-grained or high level to
fine-grained or detailed
Generally speaking, the
narrower the scope of the
system, the finer-grained the
description that can be written
in a given time
There are three levels to
consider
Domain Architecture covers a
specific area of interest
Solution Architecture
v1.1.3 Slide:18
theknowledgeacademy
Enterprise Architecture
•
•
A strategic approach to
architecture that addresses a
whole enterprise
The maximum level, widest scope,
longest term kind of architecture
1.
2.
Documentation describing the
assembly and behaviour of an
enterprise and its information
systems
A procedure for describing an
enterprise and its information
systems and designing changes to
improve the integrity and flexibility of
the enterprise
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:19
theknowledgeacademy
Principles of Enterprise
Architecture
Enterprise Architecture principles provides organisations’ with basic value
statements that can push the potential of their operations.
Following are a list of some principles:
• Importance of Principles
• Compliance with Constitutional Requirements
• Maximise Advantages for the Organisation
• Information Management for Everyone
• Business Endurance
• Information Technology Responsibility
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:20
theknowledgeacademy
Principles of Enterprise
Architecture
• Importance of Principles
Applying all principles to an enterprise is important, to be able to maximise its
potential and grow. Personnel should not only apply them, but it is important that all
staff of the enterprise recognise and utilise these given principles.
• Compliance with Constitutional Requirements
It is important the enterprise complies with internal and external laws, especially
those provided by regulatory bodies and governmental bodies.
• Maximise Advantages for the Organisation
Enterprises that make decisions that regard the whole hierarchy itself, rather than a
particular department or perspective, have longer lasting benefits.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:21
theknowledgeacademy
Principles of Enterprise
Architecture
• Information Management for Everyone
Employees are essentially part of the stakeholder group, thus making it important for
them to apply Information Management to their duties. All departments of an
enterprise need to align themselves with information management to ensure they
meet business needs.
• Business Endurance
Businesses need to be able to still continue their functional operations regardless of
their system status. This means in the case of a system failure, staff should be able to
continue their core tasks that doesn’t depend on the system.
• Information Technology Responsibility
Information Technology infrastructure and personnel play a critical role in a business,
to be able to operate the business efficiently. Good IT services leads the business to
become cost-effective and increase their potential to be more productive.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:22
theknowledgeacademy
Establish Enterprise Architecture
A well established Enterprise Architecture Framework
provides businesses with a structure of how they
operate, who they are and a direction to move towards.
Following are steps to establish an EA:
1. EA Purpose
Defining the purpose of building an Enterprise Architecture.
Identifying the answer to questions such as, what information is
vital for the EA? What is the scope of the detail needed to
support examination and form decisions? Who are the key
stakeholders to use the EA? How will the EA be maintained?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:23
theknowledgeacademy
Establish Enterprise Architecture
2. Business Queries
Identifying and finding a process to answer some of the vital
questions about ones business is necessary before the
implementation of an EA. What are the key focuses of the business?
What is the impact on the business if an application retires, if the
business needs to move location, or if IT networks need to be
replaced? What gaps are their in business at the moment and how
will EA help? Who is the main audience of the EA?
3. Hypotheses and Business Guidelines
What kind of rules will there be once this architecture has been
established? What existing rules of the business will be preventing
the EA from taking off, and how can these blockades be overcome
without manipulating the business guidelines?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:24
theknowledgeacademy
Establish Enterprise Architecture
4. Choose a Framework
Choosing a framework to work with when establishing an EA will
provide the process with a guideline. It will help identify what
information is needed, how to organise information at hand and so on.
Frameworks should be chosen depending on the objective of the
organisation, the intellect of the personnel and how flexible of a
structure is desired. Some industry standard frameworks are; TOGAF,
Zachman, DoDaf, etc.
5. Generate a Metamodel
A metamodel is a model of a model, and creating one will provide a
better understanding of the information that is needed and how each
set of data links with the other. It’s a foundation for better alignment.
Create logical relationships between the resources of the business. E.g.
link between a process and an application, however there may be no
direct link between an application and location.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:25
theknowledgeacademy
Establish Enterprise Architecture
6. Models Required in EA
Once all the basic necessities have been identified before integrating an EA,
such as answering the critical questions, choosing frameworks and
metamodels, a model needs to be chosen. To choose a model, base it on these
factors; audience, the elements of the previously determined metamodel, and
the diagrams needed to be created. Understand that using more than one
diagram to model different perspectives, and more than one tool is necessary.
7. Integrate the EA
The last step is to link the information that was gathered before, to create
relationships with the models. Integrating an EA from the bottom up is the
suggested method of implementation. Next, stabilising the framework and
synchronising it with business function and personnel will help speed up the
implementation.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:26
theknowledgeacademy
Architecture Domains
•
A wide-ranging area of architectural interest such as business, data,
applications, and technology infrastructure
•
A facet of an architecture description
•
A partial representation of a complete system that addresses
apprehensions of a number of stakeholders
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:27
theknowledgeacademy
Primary Architecture Domains
Domain
Covers
Business
Architecture
Business strategy, governance, organisation, key business
processes
Information/Data
Architecture
Structure of the organisation’s logical and physical data assets.
Data management resources
Applications
Architecture
A blueprint for the individual application systems to be deployed,
their interactions, their relationships to the core business
processes of the organisation
Technology/
Infrastructure
Architecture
The software and hardware capabilities that are required to
support the deployment of the other three architectures.
Includes IT infrastructure, middleware, networks,
communications, processing, standards
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:28
theknowledgeacademy
Case Study Exercise
Elevator Pitch
Exercise 1
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:29
theknowledgeacademy
Architecture Frameworks
•
•
•
•
•
•
Architecture Process Frameworks
Zachman Framework
Selecting an EA Framework
Hierarchical/Layered Architecture
Architecture Content Framework
Architect roles, goals and skills
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:30
theknowledgeacademy
Architecture Process Frameworks
Examples:
Definition:
•
•
A description of a process that
advances a target architecture to
meet a range of requirements,
under some constrictions, plans
the move from the baseline state
to the target state, and manages
that change
Architecture states:
o
o
o
•
•
•
•
•
DoDAF
FEAF
Gartner
TOGAF
Vendor specific
Baseline: Current
Target: Where the organisation
wants to be
Intermediate: A transitional state
between Baseline and Target
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:31
theknowledgeacademy
Zachman Framework
•
•
•
“A logical structure for classifying and organising the descriptive
representations of an Enterprise that are significant to managers and
to developers of Enterprise systems.”
Drawn as table or 6x6 grid:
Columns
o
o
•
Rows
o
o
•
The 6 columns are mostly analysis questions (What?, How?, When? etc.)
Also interpreted as architecture domains (data, process, network etc.)
The 6 rows are chiefly levels of idealisation-realisation from highest level context
to operational systems (Scope, Enterprise Model, System Model etc.)
Also interpreted as stakeholder groups and architecture viewpoints
Zachman says the rows should not be interpreted as levels of
decomposition
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:32
theknowledgeacademy
Selecting an Enterprise Architecture
Framework
•
•
•
•
Choosing the most suitable Enterprise Architecture Framework for an
organisation is a difficult task
Comparing different frameworks is difficult as they have occasionally
very different approaches to EA
Few comparative reports available
In terms of popularity, the ‘big’ five are TOGAF, FEAF, DoDAF,
Zachman, and Gartner
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:33
theknowledgeacademy
Frameworks Advantages and
Disadvantages
Following are the advantages of implementing an EA framework:
•
Simplify the complexity of the enterprise
•
Breaks down areas of the business that need extra attention, examination of the
existing processes, and clearer communication
•
Organise business elements and create and identify relationships between
business processes
•
Aids the EA establishment process to identify the scope, making sure vital factors
aren’t neglected
•
Provide customisation of the existing framework to fit in with specific businesses,
adding or taking away elements after great consideration
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:34
theknowledgeacademy
Frameworks Advantages and
Disadvantages
Following are the disadvantages of implementing an EA framework:
• Majority of the implementation method would be based on processes, rather
than the tools and framework that is chosen
• Frameworks do not provide the information for you, they simply just instruct you
on what information to gather and how to organise them. E.g. being mindful and
implementing culture and business politics into the EA
• The framework should not be the main drive of what is done at work, that should
be based on goals and objectives
• Framework adaptation demands a lot of creativity and proactive thinking, thus,
any framework that is used needs to be adapted to the business and its needs
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:35
theknowledgeacademy
A Basic Enterprise Architecture Process
Governance
Risk & Change
Precursors
Architecture
Domains
Governance
Board
Transition
Planning
Scope
Governance
EA Team formed
Statement of
Architecture Work (EA
Plan)
For all 4 Domains:
Model Baseline
Model Target
Identify Gap
Identify candidates to
fill the gap
Consolidate the Gaps
Select candidates &
write specifications
Create the Migration
Plan
Enterprise Architects
Domain Architects
Solution Architects
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Implementation
Oversight
Implementation Projects
v1.1.3 Slide:36
theknowledgeacademy
Architecture Content Framework
•
•
•
The Content Framework is
often an important part of an
EA Framework
It delivers a detailed model
of architectural work
products
It helps to increase the
consistency of the EA
outputs
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:37
theknowledgeacademy
Benefits of A Content Framework
•
•
•
It provides an all-inclusive
checklist of architecture
outputs
It encourages improved
integration of work products
if implemented across an
enterprise
It provides a detailed open
standard for how
architectures should be
described
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:38
theknowledgeacademy
Architecture Description Hierarchy
Architecture Deliverables
•
•
Anything delivered from the
architecture project is considered
an architecture deliverable
This includes:
o
o
o
•
Architecture Description
Architecture Artifacts
Architecture Entities
At the highest level of abstraction
is the Architecture Description.
This is “assembled” out of Entities
which are combined into Artifacts
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Architecture
Description
Can contain Architecture
Artifacts
Architecture
Artifacts
Composed of Architecture
Entities & Artifacts
Architecture
Entity
Entity
v1.1.3 Slide:39
theknowledgeacademy
Additional Examples of Architecture
Deliverables
• Deliverables include management and project documents
as well as architecture descriptions that contain
architecture artefacts
• Deliverable examples:
o
o
o
o
o
o
Request for Work
Statement of Work
Architecture Requirements Specification
Architecture Definition
RAID Log
Implementation & Migration Plan
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:40
theknowledgeacademy
Statement of Architecture Work (SAW)
•
The aim of the SAW is to act as a
“control pack” for the Architecture
definition project.
•
That is the work needed to identify
what needs to be changed and plan
a programme of works to implement
that change (this is basically what
takes place in the second and third
blocks on the preceding slide).
•
•
•
•
Typical sections of a SAW are listed
to the right as bullet points.
•
•
•
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Architecture project request
and background
Architecture project
description and scope
Change of scope procedures
Risk procedures
Periodic reports
Roles, responsibilities and
deliverables
Acceptance criteria and
procedures
Architecture project plan and
schedule
Approvals
v1.1.3 Slide:41
theknowledgeacademy
Architecture Description
•
•
Describes the structure and behaviour of an
enterprise or system
Many architecture frameworks define the
Architecture Description as the main deliverable
from a cycle of architecture work
o
•
•
•
A comprehensive knowledge structure that
contains more than just Architecture Artifacts
It is common to describe an architecture using
three levels as shown in the graphic
Architecture Deliverables contain Architecture
Artefacts, which are in turn composed from
Architectural Entities and other Architectural
Artifacts
An Architectural Entity can appear in several
Architecture Artifacts; an Architecture Artifact
can be composed of Architecture Artifacts
and/or Architecture Entities
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Architecture
Description
Architecture
Artifacts
Architecture
Entity
Entities
v1.1.3 Slide:42
theknowledgeacademy
Architecture Artifacts
•
•
Can be built up from
other architectural
artifacts
Are used to describe the
relationships between
architectural entities
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
Typical architectural
artifacts are:
o Catalogues (Lists)
o Matrices
o Diagrams
v1.1.3 Slide:43
theknowledgeacademy
Architecture Artifact Examples (1)
Precursors
Business
•
•
•
•
•
Goal or requirements
hierarchy
Goal or requirements
traceability
Process Map
Context Diagram
•
•
•
•
Data
•
•
•
•
•
Data Migration Diagram
Data Lifecycle Diagram
Data Entity/Business Function Matrix
Application/Data Matrix
Data Dissemination Diagram
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
Business Service/Function
Catalogue
Business Process Diagram
Organisation Decomposition
Diagram
Location Catalogue
Business Function Dependency
Matrix
Business Data Model
v1.1.3 Slide:44
theknowledgeacademy
Architecture Artefact Examples (2)
Applications
• Application Portfolio
Catalogue
• IS Context Diagram
• Application/Organisation
Matrix
• Applications Architecture
Diagram
• Application Decomposition
Diagram
• Software Layering Diagram
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Infrastructure
•
•
•
•
Application/Technology
Matrix
Technology Standards
Catalogue
Technical Environments
Diagram
Hardware Configuration
Diagram
v1.1.3 Slide:45
theknowledgeacademy
Architectural Entities (1)
•
•
•
•
Often referred to as “Building
Blocks”
A single describable
“component” of the
Enterprise
Can be divided into subentities
Examples:
o
o
o
o
Contact Centre
Contact Centre Manager
Contact Centre Operator
New Contact Process
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:46
theknowledgeacademy
Architectural Entities (2)
•
•
•
A discrete architectural constituent, an object in an architecture
repository that can be reused in various artifacts, and is definable
using a standard template
An entity instance may be decomposed into finer-grained
instances of the equivalent type
Most architectural entity types can be categorised as belonging to
an architecture domain
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:47
theknowledgeacademy
Architectural Entity Examples
• Precursors
o Stakeholder, Business goal/objective, Principle, Standard
• Business
o Organisation unit, Business function, Business process, Role,
Actor, Business service, Location
• Data
o Data entity, Data event, Data flow, Data quality, Data source
• Applications
o Application, Use case, Automated service, Component
• Infrastructure
o Technology, Computer, Network
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:48
theknowledgeacademy
Views and Viewpoints
•
•
•
•
System
Stakeholders and concerns
Viewpoint
View
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:49
theknowledgeacademy
System
• A system is a
collection of
components
organised to
achieve a specific
function or set of
functions
Enterprise Architecture Black Belt
Subsystem X
Subsystem Y
Module
Component
B
Module
Component
Entry
Point
© The Knowledge Academy Ltd
Subsystem X
A
Wire
Implementation
Module A
Wire
External
Service
Wire
Implementation
Module B
v1.1.3 Slide:50
theknowledgeacademy
Stakeholders & Concerns
Stakeholders
Concerns
•
•
Stakeholders are people
who have key roles in, or
concerns about, the system
e.g. users, developers etc.
Stakeholders can be
individuals, teams,
organisations, etc.
•
•
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
A general type of interest
(e.g. availability, usability)
that is significant to one or
more stakeholders in the
system, and controls the
acceptability of the system
to those stakeholders
A concern may be addressed
in several viewpoints
A viewpoint may address
several concerns
v1.1.3 Slide:51
theknowledgeacademy
Viewpoints
•
•
•
A viewpoint defines the perspective
from which a view is taken i.e. what
the stakeholders want to witness
and how they want to witness it
“What views of the same kind look
like… a schema or template…
describing the purpose and
intended audience of the view”
Defines a view’s scope (the concerns
addressed) and style
(documentation conventions)
o
Should be stored for reuse by Architects
in the same organisation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:52
theknowledgeacademy
Views
•
•
•
“A view is the representation of a system from the perspective of a
related set of concerns, to demonstrate to one or more
stakeholders that their concerns are addressed in the design of
the system.”
Views are decomposable. Views can share content. Views can
contain parts of other views
An instance of a viewpoint.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:53
Views & Viewpoints
New Help Desk
theknowledgeacademy
Viewpoint/
concerns
View
Organisation
Chart
Network
Diagram
Costs
Spreadsheet
HR Manager
IT Manager
Finance Director
Staffing?
Location of
computers?
Cost?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:54
theknowledgeacademy
Quick Quiz:
Which of the following statements are most likely to be from a view or a
viewpoint?
A. I need to know the projected staffing levels of the Help Desk
B.
Current projection is one CS manager. An assistant, three shift leaders
and three teams of six CSOs
C.
What is the cost of the staff kitchen?
D. The car park will have space for eighteen cars
E.
Two standby generators will be needed
F.
What is the “Go live” date?
G. How many trained First Aiders will be needed?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:55
theknowledgeacademy
Evening Assignment
Revision of the slides covered today
Attempt Black Belt Practice Questions & check answers
(Appendix B)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:56
theknowledgeacademy
Day 2 Agenda
• Architecture
Management
• Architecture Precursors
• Architecture Domains
• Business Architecture
• Data Architecture
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:57
theknowledgeacademy
Architecture Management
• Architecture Partitioning
• Architecture Governance
• Architecture Change
Management
• Risk Management
• Gap Analysis
• Architecture Implementation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:58
theknowledgeacademy
Introduction to Architecture Partitioning
Partitioning is the practice by which large Enterprise Architectures are
broken down or ‘partitioned’ into numerous smaller ‘sub architectures’.
This usually results in an Architecture Landscape that has three levels of
Architecture: Strategic, Segment and Capability
Strategic
Segment
Segment
Segment
Capability
Enterprise Architecture Black Belt
Capability
© The Knowledge Academy Ltd
v1.1.3 Slide:59
theknowledgeacademy
The Reasons to Partition
• Managing Complexity
• Managing Parallel developments
• Managing Re-use
As a result of partitioning, conflicts may need to be managed
due to sub architectures having overlying objectives etc.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:60
theknowledgeacademy
Introduction to Architecture Governance
Governance is the practice by which Enterprise
Architectures are managed and controlled.
This includes:
• Controls on the creation and monitoring of components and
events
• Ensuring compliance with internal and external standards and
regulatory requirements
• Warranting accountability to stakeholders
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:61
theknowledgeacademy
Architecture Governance Board
• The Board oversees implementation of the governance
strategy
• The Board includes representative stakeholders
accountable for review and preservation of architecture
o Typically about half a dozen permanent members
o Additional ‘legislative experts’ etc. as required
• Board has identifiable and articulated:
o Responsibilities and decision-making abilities
o Remit and authority limits
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:62
theknowledgeacademy
Architecture Board Responsibilities
• Deciding on changes to the architectures and ensuring
flexibility of the architecture to change
• Ensuring consistency between sub-architectures
• Setting targets for re-use of architectural content and
components
• Enforcement of Architecture Compliance
• Ensuring that the discipline of architecture-based
development is adopted
• Supporting a visible escalation capability for dealing with
requirements etc. that do not fall within the scope of a
particular architecture partition
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:63
theknowledgeacademy
Conceptual Structure
• The Architecture Governance Framework is essential to an
architecture framework, and manages all the content for
both the architecture and the architecture governance
processes
• Architecture Governance covers management and control
of all facets of the development of Enterprise Architectures
• The Architecture Governance Framework is generic and
typically involves the implementation and alteration of an
existing governance environment. It aids identification of
operative processes and organisational structures, so that
the business responsibilities can be clarified,
communicated, and managed
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:64
theknowledgeacademy
Architecture Governance Framework Conceptual Structure
• Architecture Governance is a method, a succession of
processes, a cultural orientation, and a collection of
responsibilities that safeguard the integrity and efficiency
of architectures
• The division of process, content, and context is crucial to
supporting an architecture governance initiative. It
permits introduction of new governance material without
affecting the processes and guarantees framework
flexibility
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:65
theknowledgeacademy
Organisational Structure
CEO/CIO/CTO
Stewardship
Develop
Deploy
Implement
Architect
Manager
Architecture
Board
Program
Management Office
Guidance
Service
Management
Risk Management
Monitoring
Enterprise Architects
Architect
Architect
Architect
Manager
Domain
Manager
Manager
Architects
Architect
Architect
Implementation
Manager
Manager
Projects
Change
Conformance
Architect
Architect
Operational
Manager
Manager
Systems
Architecture Repository
Reference
Library
Architecture
Landscape
Enterprise Architecture Black Belt
Standards
Information
Base
© The Knowledge Academy Ltd
Governance
Log
Requirements &
Solutions
v1.1.3 Slide:66
theknowledgeacademy
Levels of Governance
The Hierarchy of Governance domains includes:
o Technology Governance
o IT Governance
o Architecture Governance including business
governance
Each domain may exist at multiple geographic
Global
levels:
Tech IT Arch
o Global
o Regional
o Locals
S. America
Asia
Europe
Tech IT Arch
Tech IT Arch
Tech IT Arch
Tech IT Arch
Brazil
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Tech IT Arch
China
Tech IT Arch
Mexico
Tech IT Arch
India
Tech IT Arch
Malaya
Tech IT Arch
Germany
Tech IT Arch
UK
v1.1.3 Slide:67
theknowledgeacademy
Benefits of Architecture Governance
• Links processes, resources, and information to
organisational strategies and aims
• Assimilates and institutionalises best practices
• Aligns with industry frameworks
• Allows the organisation to take full advantage of its assets
• Protects the underlying digital assets of the organisation
• Supports regulatory and best practice requirements
• Promotes visible risk management
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:68
theknowledgeacademy
Architecture Contracts
•
Cooperative agreements between development partners and
sponsors on the deliverables, value, and fitness-for-purpose of an
architecture
•
Use of Architecture Contracts ensures
o
o
o
o
o
Continuous monitoring to inspect integrity, alterations, decision-making, and
audit of all architecture-related activities
Compliance to the standards, principles, and requirements of the existing or
emerging architectures
Identification of risks
A group of processes and practices that confirm accountability, responsibility,
and discipline with regard to the development and practice of all architectural
artifacts
A formal understanding of the governance organisation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:69
theknowledgeacademy
Architecture Compliance
Two processes are defined to ensure alignment of projects
with the Enterprise Architecture:
1. Prepare Project Impact Assessments - project-specific views that
demonstrate how the Enterprise Architecture affects a project
2. Perform an Architecture Compliance Review
• Typical levels of conformance include Consistent,
Compliant, Conformant, and Fully Conformant as well as
non-conformant
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:70
theknowledgeacademy
Architecture Change Management
•
The goal of an Architecture Change Management process is to
make certain that the architecture attains its original target
business value
•
This can be completed by:
1.
2.
•
The process will determine the circumstances under which:
1.
2.
•
Ensuring that changes to the architecture are managed properly
Supporting a dynamic architecture
The architecture will be allowed to change after deployment, and
the procedure for this
The architecture development processes will be re-visited again
Typical categories of architecture change include simplification,
incremental, and re-architecting
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:71
theknowledgeacademy
Risk Management
•
Management of
susceptibilities that threaten
the aptitude of a target system
to meet requirements,
particularly non-functional
requirements such as security
•
Risk Management is required
before architecture definition
begins in earnest, and then
several times later in the
process, and at several levels
of design
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:72
Risk Management
There are usually two levels of risk that should be considered:
1.
2.
Initial Level of Risk: Risk categorisation before determining and
implementing mitigating actions
Residual Level of Risk: Risk categorisation after implementation of
mitigating actions
The process for Risk Management typically includes:
•
•
•
•
•
Risk Identification
Risk Assessment
Risk Planning
Risk Mitigation and Residual Risk Assessment
Risk Monitoring
Enterprise Architecture Black Belt
© 2017 The Knowledge Academy Ltd
v1.1.3 Slide:73
theknowledgeacademy
Gap Analysis
•
Generally, a technique for
comparing two similar lists or
structures, to find potentially
missing items. It can be used to
compare two optional
solutions, and identify gaps in
one or both
•
Often used to compare the
gaps between baseline and
target architectures i.e. things
to be removed, upgraded, or
newly developed
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:74
theknowledgeacademy
Gap Analysis Example
Intentionally
eliminated
Same
Different
Unintentionally
eliminated –
gap in target
architecture
Gap – To be
modified or
upgraded
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Gap – To be
developed or
procured
v1.1.3 Slide:75
theknowledgeacademy
Case Study Exercise
Gap Analysis
Exercise 8
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:76
theknowledgeacademy
Architecture Precursors
•
•
•
•
•
•
•
Drivers, aims, and directives
Solution descriptions and plans
Standards
Scope of architecture work
Requirements
Regulatory requirements
Business case
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:77
theknowledgeacademy
Architecture Precursors
•
Before the Architect can get started, certain things need to be put in
place:
o A need must be identified and explained
o The scope of the work should be defined
o Standards, constraints, and principles need to be established
o Requirements need stating
•
Once this information is acquired, the EA can issue a “statement of
architecture work” describing how the change will be produced
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:78
theknowledgeacademy
Drivers, Aims, and Directives
• Drivers
• Aims and Directives
• Aim Hierarchy
o Balanced scorecard
• Directive Hierarchy
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:79
theknowledgeacademy
Drivers
• A pressure (internal or external)
that assists with the shaping of
plans
• The force that makes an
Enterprise want to change in
some way
• Examples:
o
o
o
o
Customer Feedback (likes/dislikes)
Changing markets
Competitor behaviour
New opportunities
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:80
theknowledgeacademy
Aims & Directives
Aims
Directives
•
•
Statements of what a
project is trying to achieve
• Aims are often broken
down into hierarchies of:
o Goals
o Objectives
o Requirements
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Act as a guidance framework
so that the way the project
runs meets business
obligations
• Directives are statements that
guide individuals to reach their
goal
• Directives can be used as a
governance tool
• Directives are often broken
down into hierarchies of:
o Principles
o Policies
o Rules
v1.1.3 Slide:81
Aim Hierarchy
theknowledgeacademy
Goal
• Goal
o Top level
o Can be qualitative or
quantified (SMART)
o Can be Business or Technical
• Objective
We need to reduce energy
costs
Objective
o Middle level
o Supports one or more goals
• Uses SMART KPIs
Heating costs to be reduced
by 10%
• Requirement
o Last level
Requirement
Building insulated to BS5467
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:82
theknowledgeacademy
SMART
• When writing Goals or
Objectives it is practical to
make them “SMART”
• This acronym helps us stop
writing vague or unclear
statements
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Specific
Measurable
Actionable
Realistic
Time-bound
v1.1.3 Slide:83
theknowledgeacademy
Balanced Scorecards
•
Developed in the early 1990s as a response to the issue of an
organisation’s tendency to manage their businesses based
exclusively on financial matrices
o
•
Financial measures are retrospective – they show the business as it was in
the past, however, we need to obtain a picture of where the business is
heading in the future!
Designed as a management system (not a measurement system)
o
Allows businesses to set, track, and achieve its vision by focusing on four
specific areas (the “Four Legs”)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:84
theknowledgeacademy
Directive Hierarchies
Principle
• Directives are often
grouped into
hierarchies:
o Principles
o Policies
o Business Rules
Data Security is paramount
Policy
USB Ports disabled
Business Rule
AccessLevel = Low if
UserType = Public
Reference Model: 2.2.1
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:85
theknowledgeacademy
Directive Hierarchy: Principles
•
•
•
•
A strategic, abstract, and notdirectly-actionable directive
that originates from high-level
objectives
A statement of a result that
reflects goals
A tool used in governance of
architecture work
Principles can be related to
business, data, applications,
infrastructure, or security
Principle
Data Security is paramount
Policy
USB Ports disabled
Business Rule
AccessLevel = Low if
UserType = Public
Reference Model: 2.2.1
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:86
theknowledgeacademy
Directive Hierarchy: Policies
Principle
•
•
•
A tactical directive that stems
from objectives
A tool used in governance of
day-to-day work
It directs the behaviour that
the business plans will lead to
anticipated outcomes
o
E.g. Members of the public have
minimal access to data
Data Security is paramount
Policy
USB Ports disabled
Business Rule
AccessLevel = Low if
UserType = Public
Reference Model: 2.2.1
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:87
theknowledgeacademy
Directive Hierarchy: Business Rules
Principle
• A rule directs and limits a
process
• Appears in specifications of
automated data processing
• A Term, Fact, Constraint or
Derivation Rule used in the
explanation of data
processing
Data Security is paramount
Policy
USB Ports disabled
Business Rule
AccessLevel = Low if
UserType = Public
Reference Model: 2.2.1
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:88
theknowledgeacademy
Solution Descriptions and Plans
• High-level descriptions
• Target solution hierarchy
• Plans
o Plan hierarchy
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:90
theknowledgeacademy
Descriptions are the Foundations of Plans
High level
Business mission
Mission statement
Business vision
Target
Solution
Descriptions
Solution vision
Solution outline
Solution to be built
Plans
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Strategy
Programme plan
Project plan
v1.1.3 Slide:91
theknowledgeacademy
High-Level Descriptions
Business Mission
• What an organisation is about
• Its reasons for existing
• The essential products and
services it offers to customers
Business Vision
• A high-level outline of an
ambitious target state for an
enterprise
o
o
Mission Statement
•
A declaration of mission,
vision, main goals, and
values
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
“What an organisation wants to be
or become”
Business Motivation Model
The target state is meant to meet
the goals of one or more
stakeholders
o
o
The state may be achievable and
associated with specific aims
The state may be unachievable, used
only as a guiding principle for
planning
v1.1.3 Slide:92
theknowledgeacademy
Quick Quiz
For each of the terms in the left column, identify the correct description
in the right column:
1. A plan to channel efforts towards
achieving a goal
A. Mission
Statement
B. Business Mission
C. Strategy
D. Business Vision
Enterprise Architecture Black Belt
2. A high-level outline of an ambitious
target state for an enterprise
3. A declaration of mission, vision, main
goals, and values
4. What an organisation is about, its
reasons for existing
© The Knowledge Academy Ltd
v1.1.3 Slide:93
theknowledgeacademy
Target Solution Hierarchy
This…
Describes this…
An outline of a target system, just enough to enable
options to be compared and/or work to proceed.
May be a response to a business problem or an
elaboration of how to reach a business vision.
Solution Outline A high-level outline of a target system, produced after
a first pass architecture definition, enough to pass risk
assurance.
Solution to be built A project-ready architecture, completed in adequate
detail for the project to be scheduled and resourced,
and the building team to start work.
Solution Vision
Solutions may be mapped to aims and directives
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:94
theknowledgeacademy
Plans
•
•
•
•
A document that defines the
process to reach an aim
It should consist of timescales,
costs, and resources for each
stage
There can be a strategy for an
organisation, a project, or
person, at any level of detail
Plans are often organised in a
hierarchy, increasing in number
and in detail from strategic to
tactical
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:95
theknowledgeacademy
Plan Hierarchy
Strategy
“A plan to channel efforts towards achieving a goal”.
A relatively high-level and/or long-term plan to reach a new state
and so accomplish some moderately high-level and/or long- term
goals.
Programme Plan A plan for a programme of projects.
In the context of architecture, the plan via which the
Enterprise Architecture is developed and implemented.
Project Plan
A plan for a project to develop and/or implement a resolution.
In the context of architecture, the strategy via which a relatively
independent solution architecture is developed and/or
implemented.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:96
theknowledgeacademy
Standards
• Standards definitions
• Common standards
bodies
• Enterprise Information
Base (SIB)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:97
theknowledgeacademy
Standards: Definitions
Standard
A widely-accepted measure or set
of qualities that is intended to
increase uniformity between
distinct systems and processes
Standards Body
An enterprise with a mission to set
standards and assess compliance to
them
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:98
theknowledgeacademy
Common Standards Bodies
•
•
•
•
•
•
•
American National Standards
Institute (ANSI)
BCS The Chartered Institute for
IT (BCS)
Information Systems
Examination Board (ISEB)
Institute of Electrical and
Electronic Engineers (IEEE)
Information Systems Audit and
Control Association (ISACA)
International Standards
Organisation (ISO)
Office of Government
Commerce (OGC)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
•
•
•
•
•
Open Applications Group
Standards (OAGIS)
Organisation for Advancement
of Structured Information
Standards (OASIS)
The Object Management Group
(OMG)
The Open Group
US National Institute of
Standards and technology
(NIST)
Software Engineering Institute
(SEI)
v1.1.3 Slide:99
theknowledgeacademy
Enterprise Standards Information Base
•
A repository that contains the standards mandated across the
enterprise
o
•
Profile
o
•
E.g. The Open Group’s SIB
The standards (and perhaps options and parameters of those standards)
necessary for a system, application or component to do its job
Profiling
o
Selecting standards for a particular system, application, or component
SIB
Profile
Standard1
Standard2
Standard3
Standard4
Profiling
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Standard2
Standard4
Component
v1.1.3 Slide:100
theknowledgeacademy
Scope of Architecture Work
• Scope of Architecture
Work
• Context Diagram
• External Entities
o Actors & Roles
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:101
theknowledgeacademy
Scope of Architecture Work
•
•
•
The effort needed to change a system
May be separated between small changes controlled through
Change Management and big changes that require an extensive
architecture effort
Architecture work has three dimensions of scope:
1.
2.
3.
Breadth: Scope of the enterprise, system, or solution
Focus: Business, application, or infrastructure change
Depth: The detail to which deliverables will be produced
The three dimensions are limited and given
boundaries by Constraints
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:102
theknowledgeacademy
Breadth of Enterprise or System
This dimension of scope could be defined in a number of ways:
•
•
•
•
•
Aim View:
goal/objective/requirement
catalogue
Service View: a service catalogue
System View: a top-level context
diagram
Process View: a top-level process
map or use case diagram
Data View: a
conceptual/domain/business data
model
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:103
theknowledgeacademy
Context Diagram
Customers
•
Illustrates a system as a ‘black box’. The inputs are consumed and the
outputs are produced by that system, with the external entities (actors
and/or roles) sending inputs and receive outputs
Inputs
Web
Skype
Chat
Enterprise Architecture Black Belt
Booking System
© The Knowledge Academy Ltd
Outputs
Slot allocated (Schedulers)
Rep allocated (Representative)
v1.1.3 Slide:104
theknowledgeacademy
Constraint (On Work)
•
•
A factor that restricts work
to be completed or
potential solution options,
such as time, budget, and
resources
(Not a constraint in the
sense of a data type or
business rule)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:105
External Entities
theknowledgeacademy
External Entity
An actor or role that inputs to and/or intakes outputs from a system or process.
Defining external entities as actors has a tendency to make a model more
comprehensible.
Defining external entities as roles has a tendency to make a model more stable and
flexible.
Actor/
Role
Input
Enterprise Architecture Black Belt
Process
© The Knowledge Academy Ltd
Output
Actor/
Role
v1.1.3 Slide:106
Actors and Roles
theknowledgeacademy
External
Entity
Actor
Role
An identifiable individual that plays
one or more roles in relation to a
system or process.
May be a person, a human activity
system. or a software system.
E.g. BACS, salesforce.com, a sales
executive a customer, an auditor
A part played by one or more actors in
relation to a system or a process. When
considering software systems, the part is
often to enter or consume data and so
named after the input or output data
flow.
E.g. loan applicant, expense claim
approver, an auditor
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:107
theknowledgeacademy
Quiz: Actors vs Roles
Identify the following External Entities as either Actors or Roles:
A. Clint Eastwood
B. The Man with no name
C. Challenges’ Managing Director
D. Stakeholders
E. Desktop computer #456
F. Data Entry Assistant
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:108
theknowledgeacademy
Requirements
• Requirement statement
• Functional and nonfunctional requirements
• Types of requirements
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:109
theknowledgeacademy
Requirement Statement
•
A statement of need with which compliance must be demonstrated
o
•
•
Often expressed as an entry in a requirements catalogue or a Use
Case Description
Requirements attributes are likely to include:
o
o
o
o
o
o
o
•
This implies an acceptance test and an acceptance authority
Reference number
Description
Source
Owner
Type
Priority
Deadline
A requirement should be SMART, which implies the definition of
acceptance tests
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:110
theknowledgeacademy
Functional & Non-Functional Requirements
Functional
Non-Functional
•
•
A requirement related to
data input or output from a
system, and to processes
and business rules for input
and output
•
Think Scope
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
A requirement about the
ability of a system to
perform its functions
(whatever they are)
effectively and efficiently
Usually quantitatively
measurable
Think Quality
v1.1.3 Slide:111
theknowledgeacademy
Types of Requirements (1)
•
•
Audit requirement
o
A requirement to do with ensuring an auditor can find the
o
when/where/how/who of a process or stored data, and can replay events
Considered by some to be a functional requirement and others to be nonfunctional
Performance
o
Subdivides into two measures, often in opposition:
1.
2.
•
Throughput: number of services executed in a time period
Response or cycle time (aka latency): time taken from request to response
Availability
o
The amount or percentage of time that the services of a system are ready for
use, excluding planned down time
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:112
theknowledgeacademy
Types of Requirements (2)
• Recoverability
o The ability of a system to be restored to live operations
after a failure
• Reliability
o The mean time between failures
o Usually applied to the technologies in the
Infrastructure, ignoring the more likely risk of
application failure
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:113
theknowledgeacademy
Types of Requirements (3)
•
Integrity
o
•
Scalability
o
•
The ability of a system to prevent unauthorised access to its contents
Serviceability
o
•
The ability of a system to grow to provide for the needs of increased work
loads
Security
o
•
A term with several meanings defined under Data Integrity and Data flow
Integrity
The ability of the operations team to monitor and manage a system in
operation
Usability
o
The ability of actors to use a system
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:114
theknowledgeacademy
Types of Requirements (4)
•
Maintainability/ Extensibility
o
•
Portability
o
o
•
The ability to move a component from one platform to another, or convert it
to run on another platform
In practice, it can be difficult to set or estimate this quality metric realistically
Interoperability
o
o
•
The ability of maintenance teams to revise or enhance a system
The ability for subsystems to exchange data at the technical level using shared
protocols and networks
Sometimes embraces data integratability
Integratability
o
The ability of interoperable subsystems to understand each other, which
requires either common data types or brokers to translate between data
types
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:115
theknowledgeacademy
Types of Requirements (5)
•
•
Service Level Agreement (SLA)
o
“Written agreement between an IT service provider and customer(s) that
o
documents agreed-to service levels.” (ITIL)
A document defining the requirements that services must meet, often
focused on non-functional requirements
Service Level Requirement (SLR)
o
o
“Criteria for level of service required to meet business objectives.” ITIL
Although included here a SLA is not strictly a type of requirement . It is best
considered as an operational contract from which Service Level
Requirements (often NFRs) can be determined and mapped to
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:116
Case Study Exercise
theknowledgeacademy
Identifying Requirements
Exercise 5
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:117
theknowledgeacademy
Regulatory Requirements
•
A law or other
regulation that adds
to the requirements
for or constraints on
any solution to be
developed or
maintained
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:118
theknowledgeacademy
IT Accountability and Procurement
Regulations
•
•
Regulation that makes public sector, IT directors, and CIOs
accountable for justifying investment in IT and for fair
procurement from suppliers
US legislation of this kind was the stimulus for many early
Enterprise Architecture initiatives:
o
o
o
•
Government Performance Results Act (GPRA) of 1993, P.L. 103-162
Federal Acquisition Streamlining Act (FASA) of 1994, P.L.103-355
Information Technology Management Reform Act (ITMRA) of 1996,
Division E, P.L. 104-106
Various EU directives have followed suit
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:119
theknowledgeacademy
Data Protection and Freedom Regulations
•
UK's Data Protection Act:
http://www.opsi.gov.uk/ACTS/acts1998/19980029.htm
•
Freedom of Information act 2000:
http://www.opsi.gov.uk/ACTS/acts2000/20000036.htm
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:120
theknowledgeacademy
Disability and Accessibility Regulations
•
UK Disability Discrimination Act:
http://www.opsi.gov.uk/acts/acts1995/1995050.htm. W3C Web
Content Accessibility Guidelines: http://www.w3.org/TR/
WAIWEBCONTENT/
o
o
•
Now superseded by the UK Equality Act 2010
www.gov.uk/equality-act-2010-guidance
US Americans with Disability Act
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:121
theknowledgeacademy
Shareholder Protection and Audit
Regulations
•
•
US Sarbanes-Oxley Act of 2002
Basel II
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:122
theknowledgeacademy
Intellectual Property Rights Regulations
•
International and national
laws protect people and
enterprises from theft of
intellectual property
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:123
theknowledgeacademy
Business Case
• Business Case (before
Architecture)
• Business Scenario
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:124
theknowledgeacademy
Business Case (Before Architecture)
What it is
Typical Contents
•
•
•
•
•
•
•
•
Justification for work
Should be outlined at the
beginning and updated as
required
o
•
It will be reviewed and
refined multiple times while
architecture work is done
Return on Investment (ROI)
Cost-benefit Analysis
Solution options
Risk Analysis
Gap Analysis (options)
Trade-off Analysis
It may break down into
business cases for specific
options, stages, or projects
within the total solution
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:125
theknowledgeacademy
Business Scenario
•
A process, or story, to which are attached the details of the actors,
applications, and technologies involved
•
A useful method used to create and present an architecture
description
•
May be defined to support a solution vision or business case
•
May be defined during the business architecture definition
•
May be presented as an example case of a business process
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:126
theknowledgeacademy
Template for a Business Scenario
•
•
•
•
•
•
•
•
•
Business scenario problem description
Detailed objectives
Views of environments and processes
Actors, their roles and responsibilities
Principles and constraints
Requirements
Next steps
Glossary of terms and abbreviations
References
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:127
theknowledgeacademy
Exercise
Write a Business Scenario describing how you would choose a new car.
Include the following in your answer:
•
•
•
•
•
•
•
Problem description
Detailed objectives
Views of environments and processes
Actors, their roles and responsibilities
Principles and constraints
Requirements
Next steps
Make the objectives SMART
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:128
theknowledgeacademy
Business Architecture
• Business Architecture
Structure & Behaviour
• Business Process
Decomposition &
Automation
• Design for Business
Security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:129
theknowledgeacademy
Business Architecture
Structure and Behaviour
• Business Functions
• Business Capability &
Capability Based Planning
• Business Model
• Business Terms & Concepts
• Value Chain Diagram
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:130
Business Functions
theknowledgeacademy
An idealised or logical subdivision of an Enterprise’s capability
Function
Description
Core business
functions
A business function that is focused on the development, marketing,
sales, creation and delivery of business products and services.
Core competency
A business function or capability that differentiates one business
from another, if only in the manner that the activities are carried
out. It should be difficult for competitors to imitate.
Support business
function
A business function that serves core business functions. E.g.
personnel, procurement or finance. Often similar in different
businesses, so an obvious candidate to be out-sourced and/or
delegated to a “shared service”.
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:131
theknowledgeacademy
Value Chain Diagram
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:132
theknowledgeacademy
Business Function Catalogue or Portfolio
•
•
•
•
A list of business functions, usually arranged in hierarchical
structure
Functions may be arranged into two or more hierarchies
Functions may be arranged in a matrix in which the rows or
columns may be titled function, capability, or domain
To authenticate and complete the business process and business
function structures, some break them down into the same level so
that every elementary business process step is also an elementary
business function
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:133
theknowledgeacademy
Business Capability &
Capability-Based Planning
Business Capability
Capability-Based Planning
•
•
A business function whose
performance is the subject of
management attention
o
o
•
E.g. Capability Maturity Models
or Capability-Based Planning
It is usually a high-level and
cross-organisational business
function
E.g. legal compliance, customer
service, security, emergency
response. (The examples in this
section overlap because the
concepts overlap)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
Planning where the focus of
managers is to establish or
advance a business function
regardless of present organisation
unit boundaries
The end result of capability-based
planning may be that a business
capability is allocated a manager
and becomes an organisation unit
v1.1.3 Slide:134
Business Model
theknowledgeacademy
The term “Business Model” is often used differently by Technical Staff and
Business Managers
Business Managers:
1. The way an enterprise delivers products and/or services to its
customers, determined by its business strategy
2. The operating model, sometimes expressed in terms of how far
the business processes are or should be standardised and
integrated
3. A what-if model of business operations, perhaps in spreadsheets
or animated workflow models
Technical Staff:
A diagram showing the Business Architecture
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:135
theknowledgeacademy
Additional Business Terms & Concepts (1)
•
Business Domain
o
•
•
A process that is significant to an
enterprise, leading to an objective of the
enterprise, or involves people in the
enterprise
Business Service (Business Sense)
o
A service or product provided by an
organisation unit or business function to
its customers, internal or external.
Defined for its consumers by an interface
or service contract, instead of by internal
processes required to deliver it
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Business Data Model
o
The chief business function of an
enterprise or organisation unit
Business Process
o
•
•
A conceptual model of
business terms and details
Business Semantics
o
A definition of business rules:
that is, terms, facts,
restrictions (on data values
and process steps) and
derivation rules (for data
items)
v1.1.3 Slide:136
theknowledgeacademy
Additional Business Terms & Concepts (2)
•
Service-oriented architecture
(business sense):
o
o
o
A method that segments a
business into distributed
components that offer
business services to each other
and to customers
Each component (business
function or organisation unit)
may be defined by a Service
Level Agreement
(Corresponding to SOA in
software systems, but actually
different in practice)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
•
Value stream
o
•
A chain of activities; an end-toend business process that
yields a result valued by the
customer
Value chain
o
A specific kind of value stream
featuring core business
functions (inbound,
operations, outbound,
marketing, sales, and service)
and support business
functions (HR, R&D,
Procurement)
v1.1.3 Slide:137
theknowledgeacademy
Case Study Exercise
Value Chain Diagram
Exercise 6
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:138
theknowledgeacademy
Business Process Decomposition
and Automation
• Process Maps
• Process Automation
Hierarchy
• Information System Service
• Workflow
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:139
theknowledgeacademy
Process Maps
• A top-level picture of a business in which its processes are
named
o The processes are not connected, or connected by dependencies
rather than control flow
• Might be drawn as a use case diagram
• Might be arranged in swim lanes
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:140
theknowledgeacademy
Process Maps
•
•
•
Process Maps are
characteristically associated
with production, however
they are useful for other
areas such as maintenance
Start at the very start of the
process and follow the flow of
the process from one step to
the next
Carefully record these steps
paying very close attention to
every task
While there are many symbols you
can manage with just three:
Decision
Action
Arrows indicate flow
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:141
theknowledgeacademy
Swim Lanes
Sales Team
Sales Manager
Start
You can insert swim
lanes (vertical or
horizontal) onto a
Process Map to
define zones of
authority.
Credit
Agency
?
Stop
Stop
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:142
theknowledgeacademy
Business Process Decomposition
•
The hierarchical decomposition of a process into lower-level
processes
o
•
Every business process step may be defined as a process in its own right
To authenticate and complete the business process and business
function structures, some decompose them to the same level so
that each straightforward business process step is also an
elementary business function
OPOPOT
One person, one place, one time
A rule of thumb used to define the bottom level of business process
decomposition
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:143
theknowledgeacademy
Workflow
Three Definitions:
1. The assignment of business process steps to actors in an
organisation
2. The logic or control flow of a process
3. A technology that helps people to define or change one or both of
the above
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:144
theknowledgeacademy
Design for Business Security
Design for Human and
Organisational Security
•
Definition of all the things
that can be done outside of
software systems to secure
business information such
as security guards, locks,
definition and roll out of
policies and procedures
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:145
theknowledgeacademy
Data Architecture
•
•
•
Data Architecture
Data Qualities &
Integration
Design for Data Security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:146
theknowledgeacademy
Data Architecture
•
•
Data Terminology
Data Model
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:147
theknowledgeacademy
Data Terminology (1)
•
o
•
o
o
•
o
•
o
A Database Management System that
enables direct access to any part of
the Database’s data structure
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
A data structure that is transported
from sender to receiver
Data format
A persistent data structure that is
accessible by applications
DBMS
Aspects of data architecture relating
to the movement of data
Data flow
Database
o
•
•
A data structure that is fixed in
persistent memory
Any file or database from which data
can be extracted by an application
Data in motion
o
Features of data architecture relating
to data that persists in a location
Data store
o
•
•
Data in storage
A format or language for presenting
data flow structures. E.g. Comma
Separated Values (CSV), Extensible
Mark Up Language (XML)
Data format standard
o
A standard for the content of data
flow structures. E.g. EDIFACT,
domain-specific XML Schema
v1.1.3 Slide:148
Data Terminology (2)
•
o
•
The data structure
maintained inside the
memory of a process or
component
Canonical Data Model
o
o
Cache
o
•
•
State
A local store of data copied
from a master data store
Regular Expression
o
A hierarchical structure of
elements organised so that
each element is part of a
sequence, or is an option of
selection or is an occurrence
of an iteration
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
theknowledgeacademy
o
o
The “one true definition” of data types
(e.g. customer address, order value,
tax reference number) utilised by an
enterprise
A logical data model that defines the
data types that appear in messages
between applications, and in the
signatures of automated business
services
Typically applied to data in data flows,
as a standard for integration of
applications, but could apply to data in
data stores as well
A canonical data may be defined at a
physical level using XML schema and
other data format standards
v1.1.3 Slide:149
theknowledgeacademy
Data Model
•
Data Model
o
o
o
•
Business Data or Conceptual or Domain Model
o
•
A schematic that assembles data items into a data structure
and defines the type of each data item
A structure that defines the qualities of entities and the
relationships between them
It may include derivation rules for some data items
A vehicle for recording business semantics
Logical Data Model
o
A definition of the data that must persist for the processes
of an application to work
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:150
Quick Quiz
theknowledgeacademy
For each of the terms in the left column, identify the correct description
in the right column:
1.
Those aspects of data architecture relating to
the movement of data
2.
The data structure maintained inside the
memory of a process or component
3.
A persistent data structure that can be accessed
by applications
E. Data in motion
4.
F. Data flow
A local store of data that has been copied from a
master data store
5.
A data structure that is held in persistent
memory
6.
A data structure that is transported from sender
to receiver
7.
The “one true definition” of data types
A. Database
B. Canonical data
C. State
D. Data store
G. Cache
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:151
theknowledgeacademy
Data Qualities and Integration
• Data Quality
• Data Integrity
• Terminology
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:152
theknowledgeacademy
Data Quality
•
•
A characteristic of a data item, data structure, or data store
Notably CIA:
Confidentiality
Shielded from unauthorised people
Integrity
If it gets changed we know about it
The sender is genuine (not an imposter)
Availability
Enterprise Architecture Black Belt
Data where you need it when you need it
© The Knowledge Academy Ltd
v1.1.3 Slide:153
theknowledgeacademy
Data Confidentiality
• Encryption
o Symmetrical key
o Public/Private key
• Anti-tampering
o Hash algorithms
• Authentication
o Access Control lists
o Challenge/Response
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:154
theknowledgeacademy
Data Integrity
•
A data item has the same value in every part of a distributed system
o
•
A data item follows relevant business rules, occasionally in relation to
another data item
o
•
The value of a data item is consistent with all unwavering business rules e.g. an
order must be for a known customer
A data item accurately signifies a fact about an entity or event
o
•
•
A fact, for example a customer name has the same value in all locations that a
data item is stored
The value of a data item in a data processing system is consistent with a fact in
the real world
Data disintegrity is a problem
Data integrity solutions can encompass one-off data quality
improvement exercises, data warehouses, and master data
management
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:155
theknowledgeacademy
Data Quality & Integrity Terminology
•
Data Flow (or message) Integrity
o
•
Data Dissemination View
o
o
•
The condition that a data flow has the
same data content when it reaches its
destination as it did when it left its
source
A view showing the dispersal (and
perhaps duplication) of data between
locations or data stores
Useful in investigation of change
impacts, data mastering and security
vulnerabilities
•
Master Data Management
o
o
The systems and processes that
allow an enterprise to maintain
and/or find one “master” version
of any data item or data structure,
usually customer or product data
Supported by a range of
approaches and technologies, with
middleware technologies that hide
the reality of multiple disparate
data sources from data consumers
Data Warehouse
o
A type of database system designed to
hold a non-normalised data structure
that is optimised for the production of
management information reports
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:156
theknowledgeacademy
Quiz: Identifying CIA
Examine the following statements and decide whether they are
most likely to refer to Confidentiality, Integrity, or Availability.
A. We will enable roaming profiles
B. Please write to me in French because, apart from me, nobody here
understands French
C. The message was delivered in a sealed envelope guaranteed to be
tamper-proof
D. Deliver this message only into the hands of the King personally
E. My darling, I have enclosed a lock of my hair so you know this
message comes from your beloved!
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:157
theknowledgeacademy
Design for Data Security
Data Security Terms (1)
•
Data Security
1. Confidentiality alone
2. A combination of Confidentiality, Integrity, and
Availability
•
Security Protection
o
•
Prevention of access to data designed to
preserve the required data qualities of
confidentiality, availability, and integrity
•
Security Policy
o
A policy that defines which
actors have (or do not have)
Access Rights to objects in a
given domain - along with any
other protections
Security Feature
o
o
A feature of a system that enables its
data and processes to be protected
E.g. Encryption, Checksum, https
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:158
theknowledgeacademy
Data Security Terms (2)
•
Information Domain
o
o
•
o
One or more data items (or attributes)
that distinctively label an entity or
actor instance
E.g. passport number or user name
Encryption
o
A process to encode data items (in a
data store or data flow) so that they
are worthless to any actor who cannot
decipher them
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
Checksum
o
A distinctively identified group of
objects with a common security policy
Access to any data within the domain is
limited and constrained by common
rules
o
Identity
o
•
•
o
•
A redundant data item added to a message
that is the result of adding up the bits or
bytes in the message and applying a
formula
This allows the receiver to detect if the
message content has been altered
It protects against accidental data
corruption, but does not ensure data flow
integrity, as it relies on the formula being
known only to sender and receiver
Digital Signature
o
o
A cryptographic scheme that simulates the
security properties of a handwritten
signature
More secure than a check sum, it is said to
ensure the data flow integrity of a
message, since the signature is corrupted if
the message content is changed
v1.1.3 Slide:159
theknowledgeacademy
Day 3
• Applications Architecture
• Infrastructure Architecture
• Black Belt Exam
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:160
theknowledgeacademy
Applications Architecture
• Applications architecture
structure
• Applications architecture
behaviour
• Applications Integration
• Design for applications
security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:161
theknowledgeacademy
Applications Architecture Structure
• Managing applications
• Applications models
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:162
theknowledgeacademy
Managing Applications
• Application catalogue or portfolio
o A list of applications, usually arranged in hierarchical structure
that reflects the business function hierarchy
• Application portfolio management
o An organisation and processes designed to catalogue, describe,
and value the applications of an enterprise, with a view to
rationalisation or optimisation of those applications
• Often models are used
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:163
theknowledgeacademy
Applications Architecture Models
• Applications Architecture Structural Model
o
o
o
A diagram that displays applications and the data flows that pass between
them
Typically drawn using some kind of Data Flow Diagram
Where there are too many data flows, they may be abstracted into
dependencies in some kind of dependency diagram
• Applications Architecture Behavioural Model
o
o
o
A diagram that shows how a process works by illustrating the interaction of
users and applications
Often drawn using some kind of interaction diagram
Frequently used to inspect where time is lost in or between application
processing stages
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:164
theknowledgeacademy
Applications Architecture Behaviour
• Use Case
• Information System Service
• Automated Service (SOA
sense)
• Transactions
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:165
Use Case
theknowledgeacademy
•
A process in which an actor uses a system: an arrangement
of transactions
•
•
Usually supports an OPOPOT business process step
Typically has one main path and several alternative (or
exception) paths
o
The details of each step (including any automated services invoked)
may be recorded independently from the use case itself
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:166
theknowledgeacademy
Use Case Diagrams
Use Case diagrams are used to gather the requirements of a system
including actors and illustrate, at a high level, how the actors interact with
the use cases
Perform credit check
Use Case
Boundary
Actors
Use Case Diagram
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:167
theknowledgeacademy
Information System Service (Repeat)
•
A Use Case or automated
service provided by one
application to another, or
to an end user
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:168
theknowledgeacademy
Automated Service (SOA sense)
A software process that a client can invoke. May be classified as a
business service or data service. Often a transaction.
•
Business Service (SOA sense)
o
o
o
•
An automated service where input and output data is defined in a canonical
data model
Can be provided either by a broker application or an application that captures
a data source, since it is the interface that matters, not the deployment
location
(Generally at a very much lower level of design than “business” business
service)
Data Service (SOA sense)
o
An automated service whose input and output data items are defined
according to the parochial physical data model of a specific data source
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:169
theknowledgeacademy
Transaction
•
Definitions
1.
2.
•
Database Transactions
o
o
•
An exchange between a user and a computer in which the user inputs a
command and receives a result
A process or unit of work that can be rolled back, for example if what was
specified as a precondition is dishonored
In this context, a transaction is a single logical operation on the data
For example, a transfer of funds from one bank account to another that
involves several modifications such as debiting one account and crediting
another, in a single transaction
ACID
o
o
The properties of a transaction that guarantee that database transactions are
processed reliably
Atomic, Consistent, Isolated, and Durable
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:170
ACID
theknowledgeacademy
Describes a set of four properties that together guarantee that database
transactions are processed reliably.
A: Atomic
“All or nothing": if one part of the transaction fails, the entire
transaction fails, and the database state is left unchanged (rolled-back)
C: Consistent
Ensures that any transaction will bring the database from one valid
state to another
Any data written to the database must be valid according to all defined
rules for the database concerned
I: Isolated
Ensures that the concurrent execution of transactions gives the same
results as if they had been executed serially
D: Durable
Once a transaction has been committed, it will remain so, even in the
event of power loss, crashes, or errors
Many RBDMs use a journaling system
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:171
theknowledgeacademy
Compensating Transaction
• A backtracking, undo, or correction procedure
o It may undo updates committed to databases, remove
messages located in message queues, send follow-up
correction messages, report cases of data disintegrity
• A process to handle the side effects of regular
process (or workflow) that started but could not
complete successfully
o Where that process cannot be implemented as an
ACID transaction
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:172
theknowledgeacademy
Quick Quiz
Match the terms in the left column to the correct descriptions on the
right
A. Data service (SOA sense)
B.
Applications architecture
structural model
C.
Use Case
D. Applications architecture
behavioural model
E.
Business service (SOA
sense)
Enterprise Architecture Black Belt
1.
A diagram that shows applications and the
data flows that pass between them
2.
An automated service whose input and output
data items are defined according to the
parochial physical data model of a specific
data source
3.
A process in which an actor uses a system: a
sequence of transactions
4.
An automated service whose input and output
data is defined in a canonical data model
5.
A diagram that shows how a process works
through the interaction of users and
applications
© The Knowledge Academy Ltd
v1.1.3 Slide:173
theknowledgeacademy
Quick Quiz
Which property of an ACID
transaction ensures that any
transaction will bring the
database from one valid state to
another?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:174
theknowledgeacademy
Application Integration
• Application integration
• Batch process
• ETL (Extracting, Transforming,
Loading)
• Application consolidation &
integration
• Boundaryless information
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:175
theknowledgeacademy
Application Integration
•
The ends or means of
linking one application to
another so that they
contribute to the same
output data flow, or store
the same data
•
Often reinforced by one or
more of the component
interoperation and
communication styles
defined in the Software
Architecture section
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:176
theknowledgeacademy
Batch Process
• A type of process that
handles a collection of
messages that have
been gathered in
advance in a file or
queue
o Opposite of online or
transactional process
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:177
theknowledgeacademy
Extracting, Transforming, Loading (ETL)
•
•
•
A pattern and/or set of tools for manipulating and cleaning
data
Tends to be used when transferring, consolidating, or
upgrading databases
Extracting (E)
o
•
Transforming (T)
o
•
Extracting data from data sources
The extracted data items are converted from one format to another
Loading (L)
o
o
The reformatted data is uploaded back into data stores
Often requires data to be cleaned up before or after the transformation
stage
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:178
theknowledgeacademy
Application, Consolidation, and Integration
•
Application consolidation
o
•
Point-to-point application integration
o
•
This involves the amalgamation of applications by a merger of distinct
databases into one, so that the previously separate applications can also be
viewed as one. Not always a good idea, since a hub application can become a
bottleneck in Change Management
An arrangement in which subsystems communicate with each other directly
(rather than via a central hub component, broker, or bus)
Hub and spoke application integration
o
A pattern in which subsystems communicate by using a central hub
component, broker, or bus (rather than talk to each other directly)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:179
theknowledgeacademy
Boundaryless Information
• Boundaryless Information Flow™
o A trademark of the Open Group envisioned to indicate the vision
of delivering any data, any time, any place to any individual who
is authorised to view the data
• Integrated Information Infrastructure Reference Model
(III-RM)
o A pattern in TOGAF for a service-oriented architecture
o User applications invoke services provided by broker
applications, which in turn invoke services provided by
applications that encapsulate data sources
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:180
theknowledgeacademy
Quick Quiz
What does the
abbreviation “ETL” stand
for?
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:181
theknowledgeacademy
Design for Applications Security
• Identification
• Authentication
• Authorisation & Access
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:182
theknowledgeacademy
Identification
• A process via which
an entity or actor
reveals their identity
o Usually followed by
authentication
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:183
theknowledgeacademy
Authentication
• A process to confirm or deny that an actor is trusted - is
the entity to which an identity was given
o E.g. A password check. Usually followed by authorisation
• Authentication of an actor produces one of four
results:
o
o
o
o
True positive
True negative
False negative
False positive
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:184
theknowledgeacademy
Three-factor Authentication
• Authentication that involves inspecting three facts
about an identified actor
• Factors can include something they:
o Remember (e.g. password, mother’s name)
o Carry (e.g. credit card or key)
o Are (e.g. biometric data)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:185
theknowledgeacademy
Authorisation & Access
Authorisation
• A process giving access to a
trusted actor, based on that
actor’s known access rights
• Usually followed by Access
Access Control Lists
• A method of linking
identified entities to an
access permission (provides
Authorisation)
Access
• A procedure used to look
inside a system to find data (or
processes) of interest
• Data can include files
comprising executable
processes
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:186
theknowledgeacademy
Quick Quiz
Match the application terms in the left column to the correct
descriptions on the right.
1. A list of applications, usually arranged in
hierarchical structure that reflects the
business function hierarchy
A. Hub & spoke
application
integration
B. III-RM
C. Business Service (SOA
sense)
D. Point-to-point
application
integration
E. Application portfolio/
catalogue
Enterprise Architecture Black Belt
2. An automated service whose input and
output data is defined in a canonical data
model
3. A pattern in which subsystems
communicate via a central hub
component
4. A pattern in which subsystems talk to
each other directly
5. A pattern in TOGAF for a service-oriented
architecture
© The Knowledge Academy Ltd
v1.1.3 Slide:187
theknowledgeacademy
Quick Quiz
If an authentication system provides a
positive result is the requester…?
A) Allowed access to a system
B) Denied access to a system
C) Depends on whether the
authentication is true or false
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:188
theknowledgeacademy
Infrastructure Architecture
•
Infrastructure Services and
Components
•
Enterprise Technology
Rationalisation
•
Enterprise Technology Definition
•
Connecting Applications to Networks
•
Design for Infrastructure Security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:189
theknowledgeacademy
Infrastructure Services and Components
• Infrastructure services
• Platform service
• Technology catalogue
portfolio
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:190
theknowledgeacademy
Infrastructure Service
• A term that can be interpreted at several different levels
and in various ways
• For example:
o A basic service such as computing power or memory, provided by
real or virtual computers
o A platform service
o An operational service such as one provided by an IT services
management tool or organisation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:191
theknowledgeacademy
Platform Service
•
A service such as
transaction
management or user
access control, provided
by one or more
platform technology
components to
applications
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:192
theknowledgeacademy
Technology Catalogue or Portfolio
•
A list of technology components types in a baseline or target
architecture, usually arranged in the hierarchical structure of an
enterprise technology classification
Platform Services
ID
TA_PS_01
Name
Description
Date
Category
Source
Created/
Amended
Standards
Class
TA_PS_02
TA_PS_03
TA_PS_04
TA_PS_05
TA_PS_06
TA_PS_07
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:193
theknowledgeacademy
Enterprise Technology Rationalisation
•
•
•
•
Technology rationalisation
Enterprise technology
classification
Virtual machine
Server consolidation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:194
theknowledgeacademy
Technology Rationalisation
A process for studying the services provided by a baseline technology
infrastructure and defining a de-duplicated target architecture:
1.
2.
3.
4.
5.
6.
7.
8.
Classify baseline platform technologies
Catalogue baseline technologies
Classify baseline platform services
Catalogue baseline platform services
Define target platform services
Define target technology components
Plan baseline-to-target migration
Govern delivery of the change
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:195
Quick Quiz
theknowledgeacademy
Arrange the following into the correct order:
A. Catalogue baseline technologies
B. Plan baseline-to-target migration
C. Classify baseline platform services
D. Govern delivery of the change
E. Classify baseline platform technologies
F. Define target platform services
G. Catalogue baseline platform services
H. Define target technology components
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:196
theknowledgeacademy
Enterprise Technology Classification
A structure for a catalogue of technology components, with headings
such as those below:
•
•
•
•
•
•
•
•
•
•
•
•
Client (user access) devices
Generic user applications
Application platform
Software development
Integration tools
Data management
Servers
Data storage
Networks
IT Services Management/operations
Environment
Security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:197
theknowledgeacademy
Technical Reference Model (TRM)
Applications
•
•
A logical and hierarchical
classification of the platform
services provided by
infrastructure technologies
to applications
The TRM can provide a
requirement specification for
technology rationalisation
Application Platform Interface
Application
Platform
Communications Infrastructure
Interface
Communications
Infrastructure
Diversity
The TOGAF Technical
Reference Model (TRM)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:198
theknowledgeacademy
Virtual Machine
•
Software that enables application programs to run above –
decoupled from - the underlying operating system and/or
hardware processor
•
Allows applications to be moved between different
operating systems and/or processors; and enables server
consolidation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:199
theknowledgeacademy
Server Consolodation
•
A programme of work
to deploy current or
baseline applications
to fewer servers,
usually involving
virtualisation
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:200
theknowledgeacademy
Solution Technology Definition
•
•
A process that travels through stages from a logical applicationinformation view through progressively more physical views, up to a
hardware configuration diagram
A process for defining the technologies that will support and run an
application that includes the activities such as:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Clarify the precursors, requirements, and context
Establish baseline opportunities and target constraints
Define client-end devices
Define data servers
Define intermediate servers
Map software layers to platform and hardware tiers
Define the network
Iteratively refine to handle non-functional requirements
Define the environment strategy
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:201
theknowledgeacademy
Hardware Configuration View
• 1: A physical system. A
structure of nodes
connected by one or
more networks
• Or 2: A logical model
of one
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:202
theknowledgeacademy
Connecting Applications to Networks
• Network Address
• Services, Ports, Sockets
• Active Process
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:203
Network Address
theknowledgeacademy
The address of a computer on a network. This can be any of a variety of
address types, mostly notably MAC address and IP address:
MAC Address
•
•
IP Address
A quasi-unique identifier (physical •
address) allocated to most
network adapters or network
interface cards (NICs) by the
manufacturer for identification
If assigned by the manufacturer, a
MAC address normally encodes
•
the manufacturer's registered
identification number
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
A numerical identification
(logical address) assigned to
a node in a computer
network using the Internet
Protocol for communication
between its nodes
Typically shown in DDN
(Dotted Decimal Notation)
v1.1.3 Slide:204
theknowledgeacademy
•
Service Type
o
•
A protocol for computer I/O (e.g. file transfer, web access, or email)
Port
o
o
o
o
•
Services, Ports, Sockets
A computer’s network address has thousands of logical ports for sending and
receiving data. Each port sends or receives data using one protocol or service
type
An international standard defines default port numbers. E.g. An http: (unsecured)
URL typically uses port 80
An https: (secured) URL typically uses port 443. An SMTP server typically uses
port 25.- A POP3 server typically uses port 110
However, the choice of port number is an architectural design decision. E.g. A
security architect might ban the use of port 80 for http
Socket
o
A socket (a software thing) involves the use of a port to input/output a service
type via a network. A socket is recognized by a logical network address and a port
number (utilised for a service type). E.g. Socket = port 80 for http: at IP address
nnnn.nnnn.nnnn.nnnn
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:205
theknowledgeacademy
Active Process
•
•
•
A computer can run several
applications (e.g. browser
instance, email software) at one
time, each has a process number
A process can use multiple
sockets, for different kinds of
input and output
Several processes can use the
same socket
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:206
theknowledgeacademy
Design for Infrastructure Security
Techniques for protecting client and server computers from malicious
access
• Major terms
• Public/Private keys
• Website security
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:207
theknowledgeacademy
Infrastructure Security Concepts
•
Client security
o
•
Server security
o
•
Features that protect server computers and databases from malicious clients
Firewall
o
•
Features that protect client-end computers from malicious access
Software at the boundary of a network that is used to detect, filter out and
report messages that are unauthorised and/or not from a trusted source
De-Militarised Zone (DMZ)
o
An area of a network, usually between the public internet and the enterprise
network. It uses firewalls to filter out messages that fail security checks. It
contains servers that respond to internet protocols like HTTP and FTP
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:208
theknowledgeacademy
HTTPS
• The combination of a normal HTTP interaction over an
encrypted Secure Sockets Layer (SSL) or Transport Layer
Security (TLS) connection
o This ensures reasonable protection of data content from those
who intercept the data flow in transit
• An https URL may specify a TCP port
o If it does not, the connection uses port 443 (whereas unsecured
HTTP typically uses port 80)
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:209
theknowledgeacademy
Public/Private keys
•
Public key certificate
o
o
•
Certificate authority
o
•
An electronic document that enables a web server to accept https
connections, or to verify that a public key belongs to an individual
It incorporates a digital signature to bind together a public key with an
identity (the name of a person or an organisation, their address, and so forth)
The website administrator must get a public key certificate signed by a
certificate authority. This signature certifies (authenticates) that the
certificate holder is the entity it claims to be
Web browsers are generally distributed with the signing certificates
of major certificate authorities, so that they can verify web-server
certificates
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:210
theknowledgeacademy
Website Security
•
•
•
Typically, a process whereby a web browser checks the public key
certificate of a web server at the other end of an https connection
The objectives are to check the web server is authentic (who it
claims to be) and that messages to/from with the web server
cannot be read by unauthorised individuals
Usually, web servers identify themselves by using a Public key
certificate
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:211
theknowledgeacademy
Exam
Exam Details
•
•
•
•
1 Hour
30 Questions
Multiple choice
Pass Mark 66%
Enterprise Architecture Black Belt
© The Knowledge Academy Ltd
v1.1.3 Slide:212
The World’s Largest Global Training Provider
theknowledgeacademy.com
info@theknowledgeacademy.com
/The.Knowledge.Academy.Ltd
/TKA_Training
/the-knowledge-academy
/TheKnowledgeAcademy
Congratulations