Enterprise Architecture Roles And Competencies V9

Enterprise ArchitectureRoles and Competencies

Presented by Paul Johnson

21 September 2009

Delivering pragmatic solutions for a changing world...

o Enterprise Architecture Role Guiding Questionso Enterprise Architecture Roles Definedo Aspects of Perspectives and Roleso Architecture Scope and Domaino Architectural Role Competencieso Bloom’s Taxonomy Describedo Defining the Continuumo Role Descriptions

Overview

04/08/23 2Delivering pragmatic solutions for a changing world...

o What defines the ‘boundaries’ of a particular Enterprise Architecture role in the EA profession?

o Within each role what knowledge, skills, abilities (competencies), tools, and resources do they need to accomplish their work?

o Where do certification & qualification requirements fit in?

o Are methodologies part of this role or does a methodological approach offer other ‘types’ of roles or paths within roles?

o When, along a continuum, do they need to acquire each competency?

o By what standards are they measured to be competent?

Enterprise Architecture Role Guiding Questions


Enterprise Architecture Roles Defined

o There are two primary categories of architecture roles – producers and consumers. o Producers could include:

o Operational or Businesso System or Information Technologyo Data or Informationo Modelso Analysis

o Consumer examples may include:o Capital Planners (CPIC)o Portfolio Managers (PfM)


Architectural Role Competencies

o To assess competency of an individual role it is necessary to measure knowledge they possess.

o To facilitate this measurement we need to use an educational standard “Bloom’s Taxonomy”.

o Blooms’ (cognitive knowledge) taxonomy is a good fit to describe a role’s knowledge levels.


Enterprise Architecture Roles Defined

Enterprise Architecture

Portfolio ManagersCapital Planners

Enterprise ArchitectsBusiness ArchitectsSystem ArchitectsData ArchitectsSolution ArchitectsSoftware ArchitectsCompliance ArchitectsInfrastructure ArchitectsFinancial Architects

Producers

Consumers

Architectural Analysts


Bloom’s Rose


Bloom’s Taxonomy Described

o Using a supportive color scheme (and numbering) to illustrate how Bloom’s Taxonomy applies to the framework will enable visualization of the cognitive knowledge required of a particular role.

o There are six levels in the taxonomy, for the purpose of defining roles only the first four will be used, moving from lowest order to highest

1

2

3

4

Knowledge

Comprehension

Application

Analysis

5

6

Evaluation

Synthesis

Out of scope

1

2

3

4

o Bloom's is hierarchical; learning at higher levels is dependent on having attained prerequisite knowledge and skills at lower levels.

o Action ‘verbs’ within each level will be used to construct the grammar of work statements required to achieve competency at each level.


1

2

3

4


o Knowledge o Exhibit memory of previously-learned materials by

recalling facts, terms, basic concepts and answers o Knowledge of ways and means of dealing with specifics -

conventions, trends and sequences, classifications and categories, criteria, methodology

o Key words: know, label, recognize, relate, recall


1


o Comprehension o Demonstrate understanding of facts and ideas by

organizing, giving descriptions and stating main ideas o This may be shown by translating material from one form

to another (words to numbers) or by interpreting material (explaining or summarizing).

o Key words: comprehend, classify, describe, explain, translate.


2


o Application o Apply new knowledge. Solve problems by applying

acquired knowledge, facts, techniques and rules.o Use methods, concepts, theories in new situations o Key words: apply, illustrate, interpret, demonstrate,

examine


3


o Analysis o Examine & break information into parts by identifying

motives or causes. o Make inferences & find evidence to support

generalizations.o Identify parts, analyze relationships between parts, &

recognize organizational principles involved. o Key words: analyze, appraise, calculate, compare,

contrast


4

Defining the Continuumo Entry - A person who is beginning to learn an activity or who is

school trained with little to no hands-on experience. o Beginner - A person who may have a basic knowledge of the trade,

and may have practical experience to perform proficiently on an independent basis.

o Intermediate - A person considered experienced who has proven practical proficiency in a trade or skill and completed all entry level requirements. The individual should be expected to perform work independently with limited supervision.

o Advanced - A person considered to have mastered a trade or skill who may be an overseer or foreman. A worker qualified to teach others and carry on the craft independently.

o Continuum - A continuous nonspatial whole or extent or succession in which no part or portion is distinct or distinguishable from adjacent parts

o Banding - Segmenting information along a continuum.

Baseline Definitions

o Knowledge - Familiarity, awareness, or understanding committed to memory that was gained through experience or study.

o Skills - Developed capacities that facilitate learning or the more rapid acquisition of knowledge or that facilitate performance of activities.

o Abilities - Enduring attributes of the individual that influence performance and enable the performance of tasks.

o Resources - Informational sources or reference materials used to locate information or that house information about processes that support or describe task execution.

o Tools - Implements used in the practice of a vocation or to perform a task.

o Work Context - The set of facts or circumstances that surround a situation or work (the totality of surrounding conditions).

Baseline DefinitionsCompetency – The combination of skills, abilities, and knowledge

needed to perform a specific task consistent with conditions or standards.

Competency Standard - The set of critical elements and performance criteria which describe the means of measuring a competency and the standard by which it is judged.

Competency Band - Segmenting competencies along a continuum. e.g., entry, beginner, intermediate, advanced

Conditions of Performance - The set of resources and tools which support a specific competency.

Performance Criteria - Measure of competence specified by band.Task - Any piece of work that is undertaken or attempted.

• Distinguishes when, along a career continuum, a competency might be expected to be achieved

Career Continuum

Assumptions

o All following roles are assumed to be at intermediate level using following as a career growth continuum

1

2

3

4

Role: Enterprise Architect

o Primary focus is on the context of entire architecture.

o Must understand conceptual enterprise and be able to bridge the gap between context and concept.

Why What How Where Who WhenPurpose Substance Causality Place Human Time

(contextual) strategy information activity location organization cycle

(conceptual) business planconceptual

data process logistic system work flow process timing

(logical) process rule logical data sub process distributed

systemhuman

interfaceprocess structure

(physical)process rule

design physical datasystem design infrastructure presentation

control structure

(elemental) process rule specification

data definition program network access timing definition

(atomic) rule database codeoperating system authentication availability

Role: Business Architect

o Primary focus is on the entire spectrum of the “human” or business areas of the architecture shown in green.

o Note the individual elements are prefaced with ‘human’ where applicable


(contextual) human strategyhuman information human activity location organization human cycle

(conceptual) human planconceptual data

human process locality work flow

human process timing

(logical) human rules logical datahuman sub-process infrastructure

human-system interface

human processing structure

(physical)human rule design physical data system design network presentation

human control structure

(elemental) human process rule specification data definition program network access

human timing definition

(atomic)human process rule database code

operating system role availability

Role: System Architect

o Primary focus is on the entire spectrum of the “system” areas of the architecture

o Note the difference in the elements – they are all prefaced with ‘system’


(contextual) system strategysystem information system activity location organization system cycle

(conceptual) system plan conceptual data system process logistic system work flow system schedule

(logical) system rules logical datasystem sub-process distributed system

human-system interface

system process structure

(physical)system rule design physical data system design infrastructure presentation

system control structure

(elemental) system process rule specification data definition program network access

system timing definition

(atomic) system logic database code operating system role system availability

Role: Data Architect

o Primary focus is in the information and data areas.

o Knowledge of How and Who is using the data to provide context is critical as well.



(conceptual) business plan conceptual data process logistic system work flow process timing

(logical) process rule logical data sub process distributed system human interfaceprocessing structure

(physical)process rule design physical data system design infrastructure presentation control structure

(elemental)process rule specification data definition program network access timing definition

(atomic) rule database code operating system authentication availability

Role: Solution Architect

o Primary focus is on the physical and logical across all interrogatives with a blended human-system approach.

o Knowledge of the logical and conceptual use of solution is important as well.



(conceptual) objective conceptual data process logistic system work flow process timing

(logical) rule logical data process distributed systemhuman-system interface

processing structure

(physical) rule design physical data design infrastructure presentation control structure

(elemental) rule specification data definition program network access timing definition

(atomic) logic database code operating system authentication availability

Role: Software Architect Primary focus is on the elemental and atomic across all interrogatives Knowledge of the logical and physical use of solution is of importance as well.


(contextual) system strategysystem information system activity location organization system cycle

(conceptual) system plan conceptual data system process logistic system work flow process timing

(logical) system rule logical data system process distributed systemhuman-system interface


(physical) system rule design physical data system design infrastructure presentation control structure

(elemental)system rule specification data definition program network system access timing definition


Role: Compliance & Financial Architect

o Knowledge of and influence on all aspects of the architecture with respect to compliance to standards and financial attributes.



(conceptual) business plan conceptual data process logistic system work flow process timing

(logical) process rule logical data sub process distributed system human interfaceprocessing structure

(physical)process rule design physical data system design infrastructure presentation control structure

(elemental)process rule specification data definition program network access timing definition


Role: Infrastructure Architect

o Primary focus is on the WHERE of the architecture

o Knowledge of the HOW and WHO is important to the infrastructure areas also.

What How Where Who When WhySubstance Causality Place Human Time Purpose

(contextual) information activity location organization cycle strategy

(conceptual) conceptual data process logistic system work flow process timing business plan

(logical) logical data sub process distributed system human interface process structure process rule

(physical) physical data system design infrastructure presentation control structure process rule design

(elemental) data definition program network access timing definitionprocess rule specification

(atomic) database code operating system authentication availability function

Role: Architecture Analyst

o Primary focus on the relationships between any or all the blocks of the architecture framework.

o Knowledge of the content underlying the framework is critical.



(conceptual) business planconceptual data process logistic system work flow process timing

(logical) process rule logical data sub process distributed system

human interface


(physical)process rule design physical data

system design infrastructure presentation

control structure

(elemental)process rule specification

data definition program network access

timing definition

(atomic) rule database codeoperating system authentication availability

Contact Information

Paul W. JohnsonCEO

[email protected]


Visit us on the Web at http://www.pragmatica-innovations.com

Backup slides

o Following slides are backup and supporting information


Documents

Enterprise Architecture Roles And Competencies V9