Enterprise Architecture Learning Track...Enterprise Architecture Governance V. Architecture Principles and their Development VI. Architecture Views and Viewpoints VII. An Introduction

EnterpriseArchitectureLearning Track

DIGILEAF Inc. is a solutions providerfounded to alleviate the level ofservice quality awareness andpractices in an organization. Itsmission is to help businesses achieveorganizational excellence throughthe development of its humanresources and leveraging the use oftechnology in business.

DIGILEAF - Leading ExcellenceAmong Fellows, provides costeffective quality training programs,audit, management, and consultingservices. The company is servicing200+ companies to date.

International Alliance of QualityProfessionals (IAQP), registered inThe Netherlands, was founded in2009 by representatives of threecountries namely, The Philippines,The Netherlands & Iran. The Alliancebelieves that by sharing policy,information and training, it will beable to strengthen the work ofquality professionals embedded inany role in any organization, tofoster the good practices in eachindustry in a specific region and toelevate these to an internationallevel, thus forming best practicesthat could be replicated in otherregions of the world as well.

Enterprise Architects or other Domain Architects (such as Solutions Architect,Business Architect, Data Architect, Technology Architect) in general, need thecompetencies in architecture frameworks, methods, business modeling, datamodeling, designing information structures, integrating applications anddata, and infrastructure modeling.

In Enterprise Architecture, several frameworks are available, which can beused for developing a broad range of different architectures. EnterpriseArchitecture describes a method for designing an enterprise in terms of setbuilding blocks, and for showing how the building blocks fit together.

The Enterprise Architecture Learning Track is composed of various modulesthat would equip learners both in architecting the enterprise, and designingsolution architectures. Distinct modules are designed to cater to diverse typeof audience with varying levels of competencies.

Learning Track Description

CourseTitle TotalDuration

IntroductiontoEnterprise Architecture Frameworks (Seminar Approach) 1day

Enterprise Architecture– ValueofAligning Business ArchitecturewithTechnologyArchitecture(Seminar Approach)

1day

Enterprise ArchitectureSeminar-Workshop(DocumentationandMapping Business, Stakeholder, Architectural,andSolutionRequirements) (Seminar-Workshop Approach)

2days

UsinganEnterprise Architecture Framework – TOGAF® 9.1(Overview ofTOGAF9.1)(Seminar-Workshop Approach)

2days

TOGAF ®9.1(Level 1and2)(Seminar-Workshop Approach) 4days

ArchiMate® 2.1(Seminar-Workshop Approach) 2days

ApplicationofArchiMate® 2.1forTOGAF Requirements(IntroductorytoAdvanced LevelCombined)(WorkshopApproach)

5days

Business Architecture (WorkshopApproach) 3days

RelatingBusiness ScenariosandBusiness GoalstotheADM (WorkshopApproach)

4days

AdaptingTOGAF Architecture DevelopmentMethod (WorkshopApproach) 6days

SecurityArchitecture(WorkshopApproach) 4days

MigrationPlanning(WorkshopApproach) 4days

DataArchitecture (WorkshopApproach) 3days

DomainModel: VisualizingConcepts(WorkshopApproach) 3days

DomainModel:AddingAssociations (WorkshopApproach) 3days

DomainModel:AddingAttributes(WorkshopApproach) 3days

DomainModel: ModelingGeneralization(WorkshopApproach) 3days

RefiningDomainModel: AddingAssociationClasses (WorkshopApproach) 4days

DataModeling:UsingEntityRelationships (WorkshopApproach) 4days

DataAnalyticsEssentials (WorkshopApproach) 4days

Course CatalogEnterprise Architecture Learning Track

CourseTitle TotalDuration

Designing Service-Oriented Architectures (SOA) (WorkshopApproach) 4days

Service-Oriented Architecture withJava(WorkshopApproach) 4days

SoftwareArchitecture – ADeveloper’s Perspective (Seminar-WorkshopApproach)

2days

Java ApplicationArchitecture(WorkshopApproach) 4 days

Course CatalogEnterprise Architecture Learning Track

Enterprise Architecture

Modules

Introduction to Enterprise Architecture FrameworksEnterprise Architecture (EA) defines the currentcapabilities of an organization. EA serves as a guide inproposing solutions that may or may not includetechnology. Without Enterprise Architecture, anorganization employs change in a trial-and-errormode.

This course is designed to fully understand EAFrameworks, techniques and tools. The focus of thiscourse is on the essential elements required to deliverresults-driven EA programmes, tailored to meet yourorganizational needs and directions. This course shallequip the participants how to assess an organization’sarchitectural maturity and how to select anappropriate Enterprise Architectural Framework.

While the focus is on Enterprise Architecture, thiscourse also explains the relationship between theconstituent architectures (such as BusinessArchitecture, Information Systems Architecture – DataArchitecture & Application Architecture, andTechnology Architecture), and shows how eachcontributes to managing architectural evolution.

Target AudienceTargetAudience(combinationofBusinessUsersandITrepresentatives):• TechnologyHeads• HeadofDivisions/Departments• BusinessStrategyExperts• BusinessandOperationsManagers• ProductManagersandProjectManagers• EnterpriseArchitects• ITArchitects• PolicyandStandardsPractitioners• Anyone who will be involved in designing an

EnterpriseArchitecture, Enterprise IT Architecture,Enterprise Information Systems Architecture, andother sub-sets of EnterpriseArchitecture.

Training Objectives• Explain Enterprise Architecture from the business

perspective, how it supports the business strategyand its alignment with the technology perspective.

• Describe Enterprise Architecture Frameworks andits associated processes.

TopicsI. Introduction to Enterprise Architecture

a) MajorEnterprise-levelActivitiesb) EnterpriseArchitectureDefinedc) ScopeandElementsofEnterprise

Architectured) BenefitsofEnterpriseArchitecture

II. An Architecture of Enterprise ArchitectureIII. Perspectives on the Role of Enterprise

Architecturea) Regulation-orientedb) Design-orientedc) Patterns-oriented

IV. Enterprise Architecture Frameworksa) Tapscott &Caston’s Viewsb) TheIntegratedArchitectureFramework(IAF)c) ArchiMateFrameworkd) TheZachman Frameworke) TheOpenGroup’sArchitectureFramework

(TOGAF)V. Processes of Enterprise ArchitectureVI. Architecture Maturity Level of the EnterpriseVII. Organizing the Architecture Function

Duration 1 day

Course OutlineEnterprise Architecture Learning Track

Enterprise Architecture – Value of Aligning Business Architecture with Technology ArchitectureThis is a on e-day executive briefing covering essential aspect s o f Ent erprise Architecture, outlines th eenterprise architecture ro admap, present s how to design th e four do main architectures, namely: Busin essArchitecture, Dat a Architecture, Application Architecture, and Technolog y Architecture. This briefing sh allpresent the rel ationships and d ep end encies o f each o f th e four do main architectures and will also explainhow enterprise architecture encap sulat es syst em architecture. Prior to selecting domain sp ecific systemarchitecture, it is r equired to p ass through thi s briefing to put th e right context of architecture and pr eventmisalignment when integrating architectures.

What is the value and what are the benefits?

This module will provide an overview aboutEnterprise Architecture, which has the followingbenefits and value:1. You will get an extensive overview about

Enterprise Architecture from the business andtechnology perspective and how it supports thebusiness strategy and finally ensures the successof your organization.

2. You will know the composition of EnterpriseArchitecture, thereby preventing you fromdesigning layers of architecture in silos.

3. You avoid expensive and wasteful ad hoc systemarchitecture investments.

4. You reduce the risk of failure.

Who is this module for?

Enterprise Architecture Awareness is designed for arange of Professionals, Managers and Executiveswishing to get ideas on how to establish anarchitecture function the organization, get directionson how to start technological migrations andimprovement, overview about the value ofenterprise architecture for the organization and howit is linked to the business and IT strategy.

Potential candidates for this module are:• Anyone who heads an organization• Head of Divisions/Departments• Business Strategy Experts• Business and Operations Managers• Business/Systems Analyst• Product Managers and Project Managers• Enterprise Architects• IT Architects• Technology Officers• Information Systems/Information Technology

Staff


TopicsI. Introduction to Enterprise Architecture and The Open Group Architecture Framework 9II. Business and IT AlignmentIII. Architecture, Governance, FrameworksIV. Enterprise Continuum and Architecture Re-use

a) Architecture Continuumi. Foundation Architecturesii. Common Systems Architecturesiii. Industry Architecturesiv. Organization-Specific Architectures

1) Java Architecture in Organization-Specific Architectureb) Solutions Continuum

i. Foundations Solutionsii. Common Systems Solutionsiii. Industry Solutionsiv. Organization-Specific Solutions

1) Java Architecture in Organization-Specific SolutionsV. Enterprise Architecture OrganizationVI. Enterprise Architecture RoadmapVII. Architecture PartitioningVIII. Allocation of Teams to Architecture ScopeIX. Architecture Integration

Enterprise Architecture – Value of Aligning Business Architecture with Technology Architecture

Duration 1 day

This one (1) day course introduces the major topics of Enterprise Architecture and critical parts of The OpenGroup Architecture Framework (TOGAF® 9.1).


Enterprise Architecture Seminar-Workshop (Documentation and Mapping Business, Stakeholder, Architectural, and Solution Requirements)

Duration 2 Days

This is a two-day course covering essential aspects of Enterprise Architecture and Requirements Documentation. Itdiscusses how the tools and techniques stated in the Business Analysis Body of Knowledge (BABOK 3.0) areapplied when architecting the enterprise. This course presents the alignment of the four domain architectures:Business, Data, Application, and Technology, the relationships and dependencies of each of the four domains. Thiscourse also explains how enterprise architecture provides directions in portfolio, program, and projectmanagement. Prior to selecting domain specific system architectures, it is essential to understand the rightcontext of architecture design to prevent misalignment when integrating architectures and designing solutions.This course includes practical skills necessary to document requirements including architecture, business andsolution requirements. Participants will have a better understanding on how to communicate better with variousstakeholders, including architects, subject matter experts, business process owners, solution designers andsolution implementers. Participants will learn how to identify and translate business needs into features andcapabilities, and use them to derive both functional and non-functional requirements.

Training Objectives

At the end of the course, the participants will be ableto:

1. Describe the components of EA and TOGAF.2. Explain the importance of having a cohesive

Enterprise Architecture.3. Identify EA deliverables, artifacts, and building

blocks.4. Present various types of requirements.5. Write good requirements based on international

standards and best practices.

Who is this module for?

Potential candidates for this module are:• Anyone who heads an organization• Head of Divisions/Departments• Business Strategy Experts• Business and Operations Managers• Business/Systems Analyst• Product Managers and Project Managers• Enterprise Architects• IT Architects• Technology Officers• Information Systems/Information Technology

Staff


TopicsDay 1I. Introduction to Enterprise Architecture and

TOGAF 9.1II. What is Enterprise Architecture & Why is it

important?III. Enterprise EssentialsIV. Pressures Driving Business and IT ChangeV. Definitions in Enterprise ArchitectureVI. Why Manage Enterprise Architecture?VII. TOGAF Architecture Development MethodVIII. Enterprise Architecture DomainsIX. Justifying the Investments in EAX. Risks Inherent in EA InvestmentsXI. EA ManagementXII. Linkages of Enterprise Architecture to Over-

all Business StrategyXIII. Enterprise, Domain, and Project

ArchitecturesXIV. Framework for Enterprise Architecture

ManagementXV. The Architectural BoardXVI. Architecture GovernanceXVII. Measurement Frameworks for EA

ManagementXVIII. Measuring Qualitative and Quantitative

Value from EAXIX. Techniques for Architecture DevelopmentXX. Enterprise Architecture Roadmap

Day 2I. Requirements – Concepts, Principles, and

ClassificationsII. Introduction to the Business Analysis Body of

Knowledge 3.0III. Requirements DefinedIV. Requirements Classification Scheme

a) Business Requirementsb) Stakeholder Requirementsc) Solution Requirementsd) Transition Requirements

V. Standard used in Writing Requirementsa) IEEE/ISO/IEC 29148-2011

VI. Guidelines in Writing Goals and Objectives derived from TOGAF

VII. Writing Architectural RequirementsVIII. Requirements Analysis and Design DefinitionIX. Modeling Requirements using Archimate

a) Modeling the Motivation AspectX. Requirements Life Cycle ManagementXI. Requirements Engineering CycleXII. Linking Requirements and ArchitectureXIII. Role of Requirements Engineering Cycle in the

Phases of TOGAF ADM

Enterprise Architecture Seminar-Workshop (Documentation and Mapping Business, Stakeholder, Architectural, and Solution Requirements)


Using an Enterprise Architecture Framework – TOGAF®9.1(OverviewofTOGAF9.1)The latest version of TOGAF features significant enhancements to key capabilities of the architecture framework.This includes new materials that show in detail how the Architecture Development Method (ADM) can be applied tospecific situations, such as service-oriented architecture (SOA) and security architecture.

TOGAF 9 is a detailed method and set of supporting resources for developing an Enterprise Architecture. Developedand endorsed by the memb ership of The Open Group's Architecture Forum, TOGAF 9 represents an industryconsensus framework and method for Enterprise Architecture that is available for use internally by any organizationaround the world - members and non-members of The Open Group alike - subject to license conditions.

As a comprehensive, open method for Enterprise Architecture, TOGAF 9 complements, and can be used inconjunction with, other frameworks that are more focused on specific aspects of architecture or for vertical sectorssuch as Government, Defense, and Finance.

Who is this module for?This module is designed for a range ofprofessionals wishing to get an overview and basicskills in designing architectures. This course is fitfor those who are moulded to be an enterprisearchitect, solution architect, IT architect or anydomain architect that leads to the career path ofarchitecting the organization.

Potential candidates for this module are:• Head of Division/Departments• Enterprise Architects• Solution Architects• IT Architects• Technology Officers


TopicsI. The Business Rationale for Enterprise

Architecture and TOGAFII. The TOGAF Architecture Development Method

and its deliverables, including Business, Data, Applications and Technology Architecture

III. The Enterprise ContinuumIV. Enterprise Architecture GovernanceV. Architecture Principles and their DevelopmentVI. Architecture Views and ViewpointsVII. An Introduction to Building BlocksVIII. Architecture PartitioningIX. Content Framework and Meta ModelX. Capability Based PlanningXI. Business Transformation ReadinessXII. Architecture Repository

Duration 2 day(s)

TOGAF ® 9.1 (Level 1 and 2)TOGAF, an Open Group standard, is a proven enterprise architecture methodology and framework used by theworld's leading organizations to improve business efficiency. TOGAF helps practitioners avoid being locked intoproprietary methods, utilize resources more efficiently and effectively, and realize a greater return on investment.

In this course, you will gain the knowledge needed to prepare for both TOGAF 9.1 Level 1 certification, known asTOGAF 9.1 Foundation, and TOGAF Level 2 certification, known as TOGAF 9.1 Certified. You will learn thetechnology, structure, and concepts of TOGAF 9.1. In addition to gaining the knowledge and comprehension ofTOGAF 9.1, you will learn to analyze and apply this knowledge.

Training ObjectivesAt the end of the course, the participants will be able to: 1. Describe the components of TOGAF.2. Explain the importance of having a cohesive

Enterprise Architecture framework and technology perspectives.

3. Identify deliverables, artifacts, and building blocks.

Learning Methodologies:1. Interactive Lecture/Demonstration2. Workshops

Duration 4 days

Who is this module for?1. Individuals who require a deeper

understanding of TOGAF 9.1.2. Professionals who are working in an

organization where TOGAF 9.1 has been adopted.

3. Architects who will be responsible for developing architecture artifacts.

4. Architects who wish to introduce TOGAF 9.1 into an architecture practice and who want to achieve a recognized qualification to demonstrate their detailed knowledge of TOGAF 9.1.

TopicsI. Introduction

a) Foundations of Enterprise Architectureb) Enterprise Architecture Frameworks

II. Architecture Capability Frameworka) Establishing an Architecture Capabilityb) Architecture Boardc) Architecture Complianced) Architecture Contractse) Architecture Governancef) Architecture Maturity Modelsg) Architecture Skills Framework

III. Architecture Content Frameworka) Content Metamodelb) Architectural Artifactsc) Architecture Deliverablesd) Building Blocks

IV. Architecture Development Method (ADM)a) Preliminary Phaseb) Phase A: Architecture Visionc) Phase B: Business Architectured) Phase C: Information Systems Architectures – Data

& Application Architecture e) Phase D: Technology Architecturef) Gap Analysisg) Phase E: Opportunities & Solutionsh) Phase F: Migration Planningi) Phase G: Implementation Governancej) Phase H: Architecture Change Managementk) ADM Architecture Requirements Management

V. Architecture PartitioningVI. ADM Guidelines and TechniquesVII. Architecture Maturity ModelsVIII. Architecture Skills Framework


ArchiMate® 2.1 This course covers how to use an enterprise architecture modeling language, ArchiMate®. This course shallenable a participant to use appropriate models within TOGAF® ADM. The discussions of the topics of thiscourse are incorporated within TOGAF® 9.1 from conceptual to practical applications.

ArchiMate®, an Open Group Standard, is an open and independent modeling language for enterprisearchitecture that is supported by different tool vendors and consulting firms. ArchiMate provides instrumentsto enable enterprise architects to describe, analyze and visualize the relationships among business domains inan unambiguous way.

The ArchiMate modeling language has evolved to be fully aligned with the TOGAF® standard:● By providing a vendor-independent set of concepts, that helps to create a consistent, integrated model

“below the waterline”, which can be depicted in the form of TOGAF views.● The ArchiMate® language enables modeling throughout the TOGAF® Architecture Development Method.● The language structure of the ArchiMate Core corresponds with the three main architectures as addressed

in phases B, C & D in the TOGAF® ADM.● The extensions to the Core closely correspond with the main aspects to b e addressed in the Preliminary

phase, Phase A and the Central Requirements management repository, as well as Phases E, F, G and H.

Training ObjectivesAt the end of the course, the participants will be able to:1. Model Enterprise Architecture deliverables and artifacts.2. Use appropriate notations in designing enterprise architecture models within TOGAF® ADM.

Duration 2 day(s)


TopicsI. Introduction to ArchiMateII. Language Structure

a) Core Concepts of the ArchiMate Languagei. Active Structure Elementii. Behavioural Elementiii. Passive Structure Elementiv. Servicev. Interface

b) Collaboration and Interactioni. Collaborationii. Interaction

c) Relationshipsd) Layeringe) The ArchiMate Framework

III. Business Layera) Structural Conceptsb) Behavioural Conceptsc) Informational Conceptsd) Example

IV. Application Layera) Structural Conceptsb) Behavioural Concepts

V. Technology Layera) Structural Conceptsb) Behavioural Conceptsc) Informational Conceptsd) Example

Topics continuation...

VI. Relationships and Cross-Layer Dependenciesa) Relationships

i. Structural Relationshipsii. Dynamic Relationshipsiii. Other Relationshipsiv. Example

b) Cross-Layer Dependenciesi. Business-Application Alignmentii. Application-Technology Alignment

VII. The Motivation Extensiona) Motivation Extension Concepts

VIII. ArchiMate Viewpoints

ArchiMate® 2.1


Application of ArchiMate® 2.1 for TOGAF Requirements(Introductory to Advanced Level Combined)

This course is an integration of foundation to advanced level EA modeling. It covers how to use anenterprise architecture modeling language, ArchiMate® and enables a participant to use appropriatemodels within TOGAF® ADM. The discussions of the topics of this course are incorporated withinTOGAF® 9.1 from conceptual to practical applications. This course includes modeling viewpoints andassociated analysis techniques, concepts of requirements management including their relationshipsto the ArchiMate core concepts. It covers the discussions of a reference method that identifies andstructures requirements management activities in relation to the TOGAF ADM phases. It alsodescribes how to apply the concepts for modeling goals, architecture principles, requirements,stakeholders, their concerns, and assessments of these concerns, as well as relationships betweenthese concepts. This course includes the techniques for viewing and analyzing requirements modelsand tool support for creating and working with these models.

Training ObjectivesAt the end of the course, the participants will be able to:1. Create Enterprise Architecture deliverables and artifacts.2. Use appropriate notations in designing enterprise architecture models within TOGAF® ADM.3. Model TOGAF ADM outputs using ArchiMate Extensions.4. Apply techniques in ArchiMate modeling.5. Present artifacts at each phase of the ADM using ArchiMate viewpoints.

Duration 5 day(s)


TopicsDay 1-2I. Introduction to ArchiMateII. Language Structure

a) Core Concepts of the ArchiMate Languagei. Active Structure Elementii. Behavioural Elementiii. Passive Structure Elementiv. Servicev. Interface

b) Collaboration and Interactioni. Collaborationii. Interaction

c) Relationshipsd) Layeringe) The ArchiMate Framework

III. Business Layera) Structural Conceptsb) Behavioral Conceptsc) Informational Conceptsd) Example

IV. Application Layera) Structural Conceptsb) Behavioral Concepts

V. Technology Layera) Structural Conceptsb) Behavioral Conceptsc) Informational Conceptsd) Example

VI. Relationships and Cross-Layer Dependenciesa) Relationships

i. Structural Relationshipsii. Dynamic Relationshipsiii. Other Relationshipsiv. Example

b) Cross-Layer Dependenciesi. Business-Application Alignmentii. Application-Technology Alignment

Topics continuation...

VII. The Motivation Extensiona) Motivation Extension Concepts

VIII. Introduction to ArchiMate Viewpoints

Day 3-5I. ArchiMate and Requirements ManagementII. Viewpoints and Analysis TechniquesIII. Problem Chains (Way of Thinking)IV. Requirements EngineeringV. Linking Requirements and ArchitectureVI. Distinction Between Principles and

Requirements VII. Effect of a Principle on the Design ProcessVIII. Motivation and Architecture (Way of Working)IX. Relation Between Enterprise Architecture and

Requirements ManagementX. Requirements Engineering CycleXI. Application of the Requirements CycleXII. Role of RE Cycle in the Phases of TOGAF ADMXIII. Motivation Concepts (Way of Modeling)XIV.Modeling the Motivation AspectXV. ArchiMate Techniques and Tools

a) Views and Viewpointsb) Techniques for Identifying Completeness of

Modelsc) Techniques to Use in Analyzing Consistency

of a Requirements Model

Application of ArchiMate® 2.1 for TOGAF Requirements(Introductory to Advanced Level Combined)


Business ArchitectureEnterprise Business Architecture is a critical componentof a successful Enterprise Architecture approach, bridgingthe chasm between strategic business vision and thedelivery of successful solutions to fulfill those visions. Thiscourse focuses on business-oriented views andperspectives of the enterprise.

Training Objectives1. Describe business architecture principles. 2. Prepare business architecture catalogs, matrices, and

diagrams. 3. Create business architecture deliverables.

Target Audience• Business Architects• Enterprise Architects• Anyone who will be involved in creating/maintaining

business architecture.

Learning Methodologies• Interactive Lecture/Demonstration• Workshops

Duration 3 day(s)

TopicsI. Common Definitions of Business Architecture II. Conceptual Business/Technology Model

a) Business Model b) Business Capabilities c) Technology Model d) Technology Capabilities e) Putting the Core Components To Work

III. Enterprise Business Architecture as Prioritization Driver / Change Agent

IV. Enterprise Business Architecture in a Model Driven Context a) Model Assisted Development b) Model Driven Development c) Model Driven Paradigms d) Model Repository e) Business Architecture Modeling

V. Enterprise Business Architecture Value Proposition

VI. Using ArchiMate in Business Architecture Modeling

VII. Business Scenario and Business GoalsVIII. Capability Assessment

a) Business Capabilityb) IT Capabilityc) Architecture Maturityd) Business Transformation Readiness

IX. Compliance Assessment


Relating Business Scenarios and Business Goals to the ADM

A business scenario is a complete description of abusiness problem, which enables individual requirementsto be viewed in relation to one another in the context ofthe overall problem. This course covers the discussionsand shows how to use business scenarios as a formalmethod for identifying and articulating the businessrequirements implied in new business capability toaddress key business drivers, and the implied architecturerequirements. This course will show how businessscenarios play an important role in gaining the buy-in ofbusiness line management and other stakeholders to theoverall EA project and its end product.

Training ObjectivesIn groups, participants will be able to:1. Identify and specify the business needs.2. Derive the business requirements that the

architecture development and ultimately the IT, hasto address.

Individually, the participants will be able to:1. Use a method for deriving business requirements for

architecture and the implied technical requirementsusing business scenarios and goals.

2. Write guidelines on defining goals and objectives forarchitecture development.

3. Use a method to aid IT vendors in deliveringappropriate solutions.

4. Use a language with which the vendor communitycan link customer problems and technical solutions.

TopicsI. Benefits of Business ScenariosII. Creating the Business ScenarioIII. Contents of a Business ScenarioIV. Contributions to the Business ScenarioV. Business Scenarios and the ADMVI. Developing Business Scenarios

a) General Guidelinesb) Questions to Ask for Each Area

VII. Business Scenario Documentationa) Textual Documentationb) Business Scenario Models

VIII. Guidelines on Goals and Objectivesa) Importance of Goals/Objectives

IX. Categories of Goals and Objectives

Duration 4 day(s)


Adapting TOGAF Architecture Development Method

ADM is a generic method for architecture developmentdesigned to deal with most system and organizationalrequirements. This course discusses the tools andtechniques necessary to modify or extend theArchitecture Development Method (ADM) to suit specificneeds by means of reviewing processes and outputs andtailoring them as appropriate. This course covers thediscussions of why an enterprise would need to tailor theADM. These reasons could be d epending on the maturityof the architecture discipline within the enterprise or maybe defined based on the business principles.

Training ObjectivesIn groups, participants will be able to:1. Design ADM artifacts and deliverables that create

value to the enterprise.2. Select horizontal and vertical scope, and the

horizons, accordingly.

Individually, the participants will be able to:1. Apply techniques in the Architecture Development

Method (ADM).2. Tailor the ADM to suit organizational needs.3. Apply tools on how to divide the enterprise into

several partitions.4. Write comprehensive business scenarios, goals and

objectives for the Architecture Vision.

TopicsPart 1 – Adapting the ADM (Iteration & Levels)I. Applying Iteration to the ADMII. Iteration CyclesIII. Classes of Architecture EngagementIV. Approaches to Architecture DevelopmentV. Architecture Definition StylesVI. Iteration ConsiderationsVII. Iteration Between ADM CyclesVIII. Applying the ADM Across the Architecture

Landscapea) Strategic Architectureb) Segment Architecturec) Capability Architectured) Architecture Continuume) Organizing the Architecture Landscapef) Developing Architectures at Different

Levels

Part 2 – Architecture Partitioning IX. Applying Classification to Create Partitioned

ArchitecturesX. Steps within the Preliminary Phase to Support

Architecture PartitioningXI. Allocation of Teams to Architecture ScopeXII. Integration of Architecture ArtifactsXIII. Architecture Content Aggregation

Duration 6 day(s)


Security Architecture

Security Archit ecture is a part o f th e Ent erpriseArchitecture that focu ses on infor mation securitythroughout the ent erprise. This course discusses thesecurity metho ds, discret e vi ew and vi ewpoints, flowsthrough systems an d among applications. This cour sealso co ver s th e unique, single-purpose c ompon ents inthe d esign, and unique set of skill requirement s for thearchitect. This c ourse includes th e di scussions ofarchitecture d ecisions r elat ed to security, which aretraceable to business and policy decision s and riskmanagement.

Training ObjectivesIn groups, participants will be able to Identify securityconsiderations that need to be addressed duringapplication of the TOGAF Architecture DevelopmentMethod (ADM).

Individually, the participants will be able to:1. Apply techniques in the Architecture Development

Method (ADM).2. Create security architecture artifacts.3. Integrate security artifacts with other deliverables

and artifacts in Enterprise Architecture.

TopicsI. Introduction to Security ArchitectureII. Security Architecture ArtifactsIII. Security Architecture Requirements

ManagementIV. Security Architecture in the following phases of

the ADM:a) Preliminary Phaseb) Phase A: Architecture Visionc) Phase B: Business Architectured) Phase C: Information Systems Architecturee) Phase D: Technology Architecturef) Phase E: Opportunities and Solutionsg) Phase F: Migration Planningh) Phase G: Implementation Governance

V. Phase H: Architecture Change Management

Duration 4 day(s)


Migration PlanningThis course shows how to create a viable Implementationand Migration Plan in cooperation with the portfolio andproject charters, assess the dependencies, costs, andbenefits of the various migration projects. This coursealso shows how to complete the architecturedevelopment cycle and document lessons learned toenable continuous process improvement.

Training ObjectivesIn groups, participants will be able to preparearchitecture roadmap, migration planning results,including work prioritization, and selection of major workpackages to reach the target enterprise architecture.

Individually, the participants will be able to:1. Finalize the Architecture Roadmap and supporting

Implementation and Migration Plan.2. Formulate a program on how to ensure that the

Implementation and Migration Plan is coordinatedwith the enterprise’s approach to managing andimplementing change in the enterprise’s portfolio.

3. Construct a plan that shows the business value, costof work packages and Transition Architectures.

Topics

I. Implementation Factor Assessment & Deduction Matrixa) Risksb) Issuesc) Assumptionsd) Dependenciese) Actionsf) Impacts

II. Consolidated Gaps, Solutions & Dependencies Matrix

III. Architecture Definition IncrementsIV. Transition Architecture State EvolutionV. Business Value Assessment TechniqueVI. Defining InteroperabilityVII. Interoperability Categories

a) Operational or Businessb) Informationc) Technical

VIII. Enterprise Application Integration (EAI)IX. Enterprise Operating ModelX. Refining InteroperabilityXI. Determining Interoperability RequirementsXII. Reconciling Interoperability Requirements

with Potential Solutions

Duration 4 day(s)


Data Architecture

Modules

Data ArchitectureThis course discusses data architectures anddesigning information structure necessary inbuilding solutions. This course covers how toorganize/structure data, and domain modeling. Thiscourse also includes the mapping of the businessglossary with data dictionary.

Training Objectives1. Describe data architecture principles. 2. Prepare data architecture catalogs, matrices,

and diagrams. 3. Create data architecture deliverables.

Target Audience• Business Architects• Enterprise Architects• Anyone who will be involved in

creating/maintaining data architecture.


Duration 3 day(s)

TopicsI. Principles of Data ArchitectureII. ObjectivesIII. Approach

a) KeyConsiderationsforDataArchitectureIV. Inputs

a) ReferenceMaterialsExternaltotheEnterprise

b) Non-ArchitecturalInputsc) ArchitecturalInputs

V. Stepsa) SelectReferenceModels,Viewpoints,and

Toolsb) DevelopBaseline&TargetDataArchitecture

Descriptionc) PerformGapAnalysisd) DefineCandidateRoadmapComponentse) ResolveImpactsAcrosstheArchitecture

Landscapef) ConductFormalStakeholderReviewg) FinalizetheDataArchitectureh) CreateArchitectureDefinitionDocument

VI. OutputsVII. Catalogs

a) DataEntity/DataComponentCatalogVIII. Matrices

a) DataEntity/BusinessFunctionmatrixb) System/Datamatrix

IX. Diagramsa) Classdiagramb) DataDisseminationdiagramc) DataSecuritydiagramd) ClassHierarchydiagrame) DataMigrationdiagramf) DataLifecyclediagram


Domain Model: Visualizing Concepts

The domain model provides a visual dictionary of thedomain vocabulary and concepts from which to drawinspiration for naming some things in solution design.This course discusses how to identify conceptualclasses – real-world concept or thing. This courseexplains the practical applications of the domainmodel.

Training ObjectivesIn groups, participants will be able to create a modelof the business domain depicting the business objectsthat interacts with each other

Individually, the participants will be able to:1. Identify conceptual classes related to the current

iteration requirements.2. Create a domain model.3. Distinguish between correct and incorrect

attributes.4. Add specification conceptual classes.5. Compare conceptual and implementation views.




Topics

I. Domain Models IntroductionII. Visual Dictionary of AbstractionsIII. Domain Models and DecompositionIV. Conceptual Class IdentificationV. Strategies to Identify Conceptual ClassesVI. Finding Conceptual Classes with Noun Phrase

IdentificationVII. Domain Modeling GuidelinesVIII. Modeling the Unreal WorldIX. Specification or Description Conceptual ClassesX. UML Notation, Models, and Methods: Multiple

PerspectivesXI. Lowering the Representational Gap

Duration 3 day(s)


Domain Model: Adding Associations

This course discusses how to identify associationsof conceptual classes that are needed to satisfy theinformation requirements of the current scenarios.This course covers the identification of suitableassociations, and adds associations to the domainmodel.

Training ObjectivesIn groups, participants will be able to createassociations of conceptual classes necessary inunderstanding the information model.

Individually, the participants will be able to:1. Identify associations for a domain model.2. Distinguish between need-to-know and

comprehension-only associations.




Topics

I. Associations DefinedII. Criteria for Useful AssociationsIII. The UML Association NotationIV. Finding Associations – Common Associations ListV. Association GuidelinesVI. RolesVII. Naming AssociationsVIII. Multiple Associations Between Two TypesIX. Associations and Implementation

Duration 3 day(s)


Domain Model: Adding Attributes

This course discusses how to identify the attributesof conceptual classes that are needed to satisfy theinformation requirements of the current scenariosunder development. This course explores theidentification of suitable attributes, and addsattributes to the domain model.

Training ObjectivesIn groups, participants will be able to specifyattributes of conceptual classes necessary inunderstanding the domain.

Individually, the participants will be able to:1. Identify attributes in a domain model.2. Distinguish between correct and incorrect

attributes.




Topics

I. Introduction II. UML Attribute NotationIII. Valid Attribute TypesIV. Conceptual vs. Implementation Perspectives: What

About Attributes in Code?V. Data TypesVI. Non-primitive Data Type ClassesVII. Illustrating Data Type ClassesVIII. Design Creep: No Attributes as Foreign KeysIX. Modeling Attribute Quantities and UnitsX. Domain Model Conclusion

Duration 3 day(s)


Domain Model: Modeling GeneralizationThis course covers the discussions and applications ofUML generalization and specialization.Generalization and specialization are fundamentalconcepts in domain modeling that support aneconomy of expression. This course shows howconceptual class hierarchies are often the basis ofinspiration for solution class hierarchies that exploitinheritance and reduce duplication of solutions.

Training ObjectivesIn groups, participants will be able to create classdiagrams containing generalizations andspecializations.

Individually, the participants will be able to:1. Create generalization-specialization hierarchies.2. Identify when showing a subclass is worthwhile.3. Apply the “100%” and “Is-a” tests to validate

subclasses.




Topics

I. Introduction II. New Concepts for the Domain ModelIII. Concepts Category ListIV. Noun Phrase Identification from the Use CasesV. Generalization DesriptionVI. Defining Conceptual Superclasses and SubclassesVII. Generalization and Conceptual Class DefinitionVIII. Generalization and Class SetsIX. Conceptual Subclass Definition ConformanceX. Conceptual Subclass Set ConformanceXI. When to Define a Conceptual SubclassXII. Motivations to Partition a Conceptual Class into

SubclassesXIII. When to Define a Conceptual SuperclassXIV.Abstract Conceptual ClassesXV. Abstract Class Notation in the UMLXVI.Modeling Changing StatesXVII.Class Hierarchies and Inheritance in Software

Duration 3 day(s)


Refining Domain Model: Adding Association Classes

This course discusses additional useful ideas andnotations available for domain modeling and appliesthem to refine aspects of other iterations of aDomain Model. This course covers how to identifydomain requirements that would set the stage forassociation classes.

Training ObjectivesIn groups, participants will be able to modelassociation classes, aggregation, and refine aspectsof the domain model.

Individually, the participants will be able to:1. Add association classes to the Domain Model.2. Add aggregation relationships.3. Model the time intervals of applicable

information.4. Choose how to model roles.5. Organize the Domain Model into packages.




Topics

I. IntroductionII. Association ClassesIII. Guidelines for adding association classesIV. Aggregation and Composition

a) Aggregation in the UMLb) Benefits of Showing Aggregationc) Roles as Concepts vs. Roles in Associationd) Derived Elementse) Association Role Namesf) Qualified Associationsg) Reflexive Associationsh) Ordered Elements

V. Using Packages to Organize the Domain Modela) UML Package Notationb) Ownership and Referencesc) Package Dependenciesd) Package Indication without Package

DiagramVI. How to Partition the Domain Model

a) Domain Model Packagesb) Core/Misc Package

Duration 4 day(s)


Data Modeling: Using Entity Relationships

This course discusses the importance and conceptsof Entity Relationship Diagrams (ERD) that hasemerged as one of the most popular techniques inthe design of databases due to its inherentadvantages. This course covers entities, attributes,relationships and its degrees, and cardinalities ofan Entity Relationship Diagram.

Training ObjectivesIn groups, participants will be able to construct afully attributed entity diagram relationship.

Individually, the participants will be able to:1. Identify entities and relationships.2. Differentiate between logical and physical data

models.3. Interpret an entity relationship model.




Topics

I. IntroductionII. Why Use Entity Relationship (E-R) DiagramsIII. Entity Relationship NotationsIV. Entity Relationship Diagram Development Process

a) Identify the entitiesb) Determine the attributes

V. Entity Relationship Diagram ComponentsVI. Degrees of a Relationship

Duration 4 day(s)


Data Analytics Essentials

This course covers the essentials of data analyticsfor business professionals seeking ways on how tomake use o f Analytics in decision-making and forthose who would like to be more effective in drivingquantitative-based decisions based on dataproduced. This course also discusses how to buildan analytics-focused organization, competenciesand skills for Analytics professionals. This coursefocuses on the underlying foundations in Analyticssuch as business analysis, data science, and howbusiness analytics guides effective decision-makingand strategy formation in an organization.

Training ObjectivesIn groups, participants will be able to present aData Analytics Framework.

Individually, the participants will be able to:1. Describe the data mining process.2. Identify appropriate data analytics

technologies.3. Use data science tools and techniques.

TopicsI. IntroductionII. Data Science, Engineering, and Data-Driven

Decision MakingIII. Data and Data Science Capability as a Strategic

AssetIV. Data Mining and Data Science DefinedV. From Business Problems to Data Mining TasksVI. Data Mining and Its ResultsVII. The CRISP Data Mining Process

a) Business Understandingb) Data Understandingc) Data Preparationd) Modelinge) Evaluationf) Deployment

VIII. Analytics Techniques and Technologiesa) Statisticsb) Database Queryingc) Data Warehousingd) Regression Analysise) Machine Learning and Data Mining

(Knowledge Learning and Data Mining)IX. Introduction to Predictive Modeling: From

Correlation to Supervised Segmentationa) Models, Induction, and Prediction

Duration 4 day(s)


Solution Architecture

Modules

Designing Service-Oriented Architectures (SOA)The course uses The Open Group ArchitectureFramework (TOGAF) as its core and applies itsmethods to the development of SOAs. This isenhanced by SOA specific developments of TheOpen Group and other industry recognizedorganizations (OASIS, OMG, W3C, etc.). Thesedevelopments include reference models, maturitymeasuring techniques, governance approachesand other capabilities to help develop SOAs.

The bulk of the course, takes and extends TheOpen Group Technical Guide "Using TOGAF toDefine and Govern Service-OrientedArchitectures" to detail how an organization caneffectively utilize SOA. It examines, from a holisticEnterprise Architecture perspective, how theconcepts of SOA can provide recognizablebusiness value to the organization by utilizing theproven techniques of TOGAF.

Training ObjectivesAt the end of the course, the participants will beable to:1. Recognize the relationship of TOGAF and

Service-Oriented Architecture.2. Apply the SOA Assessment Model.3. Use TOGAF for Enterprise Architecture

Service-Oriented Architecture.

Who is this module for?Potential candidates for this module are:• Head of Divisions/Departments• Enterprise Architects• IT Architects• Technology Officers

Learning Methodologies1. Interactive Lecture/Demonstration2. Workshops

Duration: 4 day(s)

TopicsI. Introduction to Service-Oriented Architectures

(SOA)II. The SOA Bandwagon

a) Serviceb) Messagec) Dynamic Recoveryd) Web Service

III. Objectives of SOAIV. SOA and Enterprise ArchitectureV. The Architectural Dimension of SOAVI. SOA Reference ArchitectureVII. Application of SOA Reference Architecture VIII. Architectural Building BlocksIX. Using TOGAF for Enterprise SOA – Preliminary

PhaseX. Service-orientation as an Architecture PrincipleXI. Implications of Service-oriented ArchitectureXII. SOA Maturity AssessmentXIII. The Open Group Service Integration Maturity

Model (OSIMM)XIV. Purpose of OSIMMXV. SOA Governance and Support StrategyXVI. Relationship of SOA Governance with IT and EA

GovernanceXVII. SOA Governance Reference ModelXVIII. SOA Governance Vitality MethodXIX. Initial Architecture Repository and SOA Reference

ArchitectureXX. Partitions & Centers of ExcellenceXXI. The SOA Center of Excellence (CoE)XXII. Service Litmus TestXXIII. How to Perform Service Litmus Test


Service-Oriented Architecture with JavaToday's IT organizations invariably employ disparatesystems and technologies. Creating applications thatleverage different technologies has historically been adaunting task. Service-oriented Architecture (SOA)provides a clear solution to application integrationissues by allowing systems to expose theirfunctionality via standardized, interoperableinterfaces. SOA offers several key advantages such asenabling applications to adapt to changingtechnologies, easily integrate applications with othersystems, leverag e existing investments in legacyapplications, Quickly and easily creat e a businessprocess from existing services. Service-orientedarchitecture (SOA) is popular because it lets you reuseapplications and it promises interoperability betweenheterogeneous applications and technologies.

This course explains and demonstrates how to buildand implement service-oriented solutions bycombining established Service-Oriented Architecture(SOA) principles, patterns, and practices with modernJava services t echnology. This course focuses onimplementing SOA using Web Services with theadoption of new, simpler protocols such as REST.

Training Objectives1. Implement web services with various degrees of

complexity and flexibility using Java.2. Describe the major web service platforms

available in the Java world, namely JAX WS 2.0,Apache Axis, Spring, and XFire.

3. Apply the concepts of SOA Core, the businesslayer, in creating SOA applications, with the helpof case studies and real-world examples.

4. Use Java Web Services to build effective SOAapplications.

TopicsPart 1 – The Mantra of SOA

I. ArchitectureII. Application ArchitectureIII. Enterprise Computing or ArchitectureIV. Loose CouplingV. ReusabilityVI. Seamless IntegrationVII. Return on Investment (ROI)

Part 2 – Web Services and SOAI. The SOA ApproachII. XML-Advantages and DisadvantagesIII. Introduction to Web Services, RESTful Services,

and Other Transport with XMLIV. RPC and Document Based-WS: How to

Communicate, Pros and Cons of the Two Approach

V. Why We Should Use Doc-WS?VI. Implementations: JAX-WS 2, Axis2, Spring-WS,

and XFire/CXF 2.0

Part 3 – Web Services ImplementationsI. Web Service Using JAX-WS 2.0II. Web Service Using Apache AxisIII. Web Service Using SpringIV. Web Service Using Xfire

Part 4 – Data and ServicesI. JDOII. Data ServicesIII. Service Data ObjectsIV. Service Components ArchitectureV. Message-Oriented MiddlewareVI. Enterprise Service Bus

Duration 4 day(s)


Software Architecture – A Developer’s PerspectiveDesigning software given a vague set of requirements and a blank sheet of paper is a good skill to have,although not many people get to do this on a daily basis. With agile methods encouraging collectiveownership of the code, it's really important that everybody on the team understands the big picture. Todo this, you need to understand why you've arrived at the design that you have. In a nutshell, everybodyon the team needs to be a software architect.

This is a two-day training module about pragmatic software architecture. This module will present what"just enough" up front design is, how it can be applied to so ftware projects and how to communicate thebig picture through a collection of simple effective sketches. Aimed at so ftware developers, it fills the gapbetween software development and high-level architecture that probably seems a little "enterprisey" formost developers.

BenefitsThis module is useful if any of the following scenarios sound familiar:• I'm not sure what software architecture is about and how it's any different from design.• I don't understand why we need "software architecture.”• My manager has told me that I'm the so ftware architect on our new project, but I'm not sure what that

actually means.• I want to get involved in designing software but I'm not sure what I should learn.• I've been given some requirements and asked to design some software, but I'm not sure where to start.• I need to make some major enhancements to my system, but I'm not sure where to start.• I've been asked to write a software architecture document but I'm not sure what to include in it.• I'm not sure who to talk to in my organization about how best to integrate what we're building.• I understand what software architecture is all about, but I'm not sure how to tackle it on my project.• My project seems like a chaotic mess; everybody is doing their own thing and there's no shared vision.

Help!

Duration 2 day(s)


Software Architecture – A Developer’s PerspectiveTopicsDay 1I. Introductions and Expectation SettingII. Software Architecture Defined

a) Architecture and Software Architectureb) Design Versus Architecture

III. The Software Architecture Functiona) Software Architects in the Development

Teamb) Software Architecture Role Versus Lead

Developer Rolec) Other Roles and Responsibilities

i. Coding Architectsii. Soft Skills Needed by Software

Architectsiii. Avoiding “Ivory Towers”, Collaboration

and Coachingiv. Quality Attributesv. Constraintsvi. Principlesvii. Designing Software Given a Blank

Sheet of PaperIV. Software Design Exercise (1st Iteration)

Day 2I. Visualizing Software

a) Reviewing the Diagrams from the Software Design Exercise

b) UML vs. Informal Sketchesc) Ineffective Sketchesd) A Lightweight Approach for Effective No-

UML SketchesII. Software Design Exercise (2nd Iteration)III. Documenting Software Architecture

a) Importance of Documentationb) Project and Documentation Stakeholdersc) A Lightweight Approach to Software

Documentationd) Alternative Approaches for Documenting

SoftwareIV. Software Architecture in the Development Life

Cyclea) Software Architecture in Waterfall,

Iterative, and Agile Approachesb) “Just Enough” Up Front Designc) Risk-stormingd) Evaluating Software Architecture and

Prototypese) Guidance for Doing “Just Enough” in the

Real World


Java Application Architecture

Modularity is critical in software architecture. It fills a gap that has existed in developing enterprise softwaresystems in Java. This course discusses that gap and explores how modularity is an important intermediarytechnology that fills that gap. This course covers software architecture as applied to Java applications. Ithighlights modularity patterns. Participants will learn the importance and the techniques of modularity patternsin software architecture, which is used to increase modularity of Java-based applications to easily scale up largeapplication systems. This course shall provide the essential elements needed to incorporate modular designthinking into Java development initiatives. This course shall present why modularity is a critical tool in yourarsenal of d esign tools. A discussion of the OSGi framework is also covered to provide a holistic view of softwarearchitecture

Training ObjectivesAt the end of the course, the participants will be able to:• Use modularity in software architectures to control the increasing complexity of software systems.• Describe the different modularity patterns that can be used in software systems.• Apply the right pattern based on the system’s architectural needs.• Examine the advantages and disadvantages of each pattern for a given architectural problem.• Apply POMA and OSGi frameworks and use them in Java-based solutions.

Duration 4 day(s)


Java Application ArchitectureTopicsPart 1 (Day 1 & 2)I. Introduction

a) Logical versus Physical Designb) Pattern Formc) Pattern Catalogue

II. The Case of Modularitya) Defining a Module

III. Facets of ModularityIV. Enterprise Continuum and Architecture Reuse

a) Runtime Modelb) Development Modelc) Today’s Modularity

V. Architecture and Modularitya) Architecture Definedb) A Software Architecture Story

i. The Ivory Towerii. Turtles and the Tower

c) The Goal of Architectured) Modularity: The Missing Ingredient

VI. Complexitya) Enterprise Complexityb) Technical Debtc) Design Rotd) Cyclic Dependencies – The Death Knell

VII. Realizing Reusea) The Use/Reuse Paradoxb) The Reuse Disclaimer

VIII. Modularity and SOAa) Structural Flexibilityb) Granularity – Architecture’s Nemesisc) An Alternative View

IX. Reference Implementationa) Why No OSGi?b) Refactoring

Part 2 (Day 3 & 4)I. The PatternsII. Base Patterns

a) Manage Relationshipsb) Module Reusec) Cohesive Modules

III. Dependency Patternsa) Acyclic Relationshipsb) Levelize Modulesc) Physical Layersd) Container Independencee) Independent Deployment

IV. Usability Patternsa) Published Interfaceb) External Configurationc) Default Implementationd) Module Facade

V. Extensibility Patternsa) Abstract Modulesb) Implementation Factoryc) Separate Abstractions

VI. Utility Patternsa) Colocate Exceptionsb) Levelize Buildc) Test Module

VII. POMA and OSGiVIII. OSGi and ScalaIX. OSGi and GroovyX. Future of OSGi


EA Learning TrackTotal Number of Courses: 24

Documents

Enterprise Architecture Learning Track...Enterprise Architecture Governance V. Architecture Principles and their Development VI. Architecture Views and Viewpoints VII. An Introduction