architecture centric engineering and togaf to · pdf fileexample reference architecture ......

Architecture Centric Engineering and TOGAF to Platform

G. Edward Roberts

eroberts@elparazim.com

Engineering “V”

Allocation of Effort

Standard Definition of Architecturearchitecture: the fundamental organization of a system embodied in its

components, their relationships to each other and to the environment and the principles guiding its design and evolution. - ISO 42010:2007

In TOGAF 9, "architecture" has two meanings depending upon its contextual usage:

1. A formal description of a system, or a detailed plan of the system at component level to guide its implementation

2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.

Version 1.0

Evolution

Version 2.0

Design

Implementation

My DefinitionArchitecture: “Capturing the Larger Context (Meta-level)”

Non-Functional Functional

SystemTo be built

Non-Functional (Software/Hardware Example):Memory FootprintLatencyExecution Time“Security”RiskMTF – Mean Time to Failure

“Capturing The Larger Context (influencers) that effects the system to be built.”

Enterprise Architecture’s Effect

Enterprise

TechnicalArchitecture

BusinessGoals

Governance

OrganizationBusinessRequirements

Influencers

QualityV&VMission

Assurance

ACE (Architecture Centric Engineering)

http://www.sei.cmu.edu/library/abstracts/brochures/aceinitiativeinformation.cfm

ACE@SEI: to improve product development and quality by using architecture to gain early confidence in achieving system-related business and mission goals.

One component of the SEI Architecture is AADL (Architecture Analysis and Design Language)

ACE View of Architecture

• Architecture is the primary carrier of system qualities, such as performance, modifiability, and security, none of which can be achieved without a unifying architectural vision.

• Architecture is an artifact for early analysis to make sure that the design approach will yield an acceptable system.

• Architecture holds the key to post deployment system understanding, maintenance, and mining efforts.

• Architecture is the conceptual glue that holds every phase of the project together for all its many stakeholders.

Example: Medical Imaging Company

Fundamental Questions (for an architect):1. Is the Architecture Scalable?... Why? they wantto do twice the business they now have ,but can they do it?

2. Is the Architecture Repeatable?... Why? They want to openUp new business centers

3. Is the Architecture Replaceable?... Why? They have a lot of old systems that are coming due to be changed out… and some“single point of failure” people

From Elparazim, my consulting business

Architectural Description

“illities”http://www.softwarearchitecturenotes.com/architectureRequirements.html

An "ility" is a characteristic or quality of a system that applies across a set of functional or system requirements. So, performance is an "ility" because it is applied against some of the functional or system requirements. Anything that can be expressed in the form "for a set of functional or system requirements, the system must fulfill them this way (this fast, this reliable, etc.)" is an "ility."

The architecture has other requirements. It is the job of the software architect to find and talk to the right people about them -- the system "ilities.“

Some “illities”

• accessibility

• accountability

• accuracy

• adaptability

• administrability

• affordability

• auditability

• autonomy

• availability

• credibility

• process capabilities

• compatibility

•composability•configurability•Correctness•customizability•debugability•degradability•determinability•demonstrability•dependability•deployability•discoverability•distributability

http://en.wikipedia.org/wiki/Ilities

Architecture Tradeoff Analysis Method (ATAMTM)

Quality Attribute Goals

Capture at a Conceptual Meta-Level

Detonation

Weapon SystemCommand Center

DetonationMessage

ReliabilitySecurityLatency

Architecture “illities”

“Channel”

ContinuouslyTransmitting

Launch Vehicle

Operation Policy

“Requirement”

Capturing a Domain Issue

Abstractions

Merger 1

Merger 2

Merger 3

This takes skill and experience

“Eliminate x% of CO2 emissionsFrom our cars.”

Is this really the business goal?

Be careful you may not be at anAbstract enough level.

Outside the Box thinking

1 kg of meat from produces kg CO2e

beef 34.6

lamb 17.4

pork 6.35

chicken4.57

A Cow releases 70 and 120 kg of Methane per year. Methane is 23 times higher than the effect of CO2.

100 kg Methane per year for each cow is equivalent to about 2'300 kg CO2 per year.

Let's compare this value of 2'300 kg CO2: The same amount of carbon dioxide (CO2) is generated by burning 1'000 liters of petrol. With a car using 8 liters of petrol per 100 km, you could drive 12'500 km per year (7'800 miles per year).

Business Goal: Eliminate Y amount of CO2

Maybe our problem is makingChicken taste like beef?

MDA: Tool Support

MDA: Model Driven Architecture From the OMG (Object Modeling Group)

Concept Independent Model

Platform Independent Model

Platform Specific Model

Why Does This Type of Architecture Not Happen

“Its Hard”

Business-ist Technology-ists

The Great Divide

Language 1 Language 2

“They Play Golf, WeSit in Cubicles”

“We take risks, theyplay it safe”

Much of architecture is having to Deal with the personalities involved.

Architects

Team Dimension Profile

C - Creators

A - AdvancersR - Refiners

E - Exectors

TOGAF 9 Parts(The Open Group Architecture Framework)

Enterprise Architecture

These are items to develop Architecturesand Architecture Capabilities

TOGAF 9 Part Relationships

History of TOGAF

TOGAF 9 Phases

Views of TOGAF

6/30/2011 23

Prelim (Capability and Tailoring)

VisionPhase A

DomainSpecificationPhase B,C,D

Solutions and DevelopmentPhase E,F,G

GoverancePhase H

WHAT HOW CHANGE

B - BusinessC - Data/ApplicationD - Technology

Preliminary Phase

Phase A: Architecture Vision

Stakeholder Map

Stakeholders and Views

Business Cost View

What does it cost to collect entity data?What does it cost to store data?What Revenue are we generating from the data?

Legal Risk View

What potential risk is there in havingthe data?What is the cost of those risks?

Phase B: Business Architecture

Phase B: Workproducts

“Standard” Domains in TOGAF 9

General Process over Domain Specification

6/30/2011 31

Identify Stakeholders

Produce Views of the Architecture

Select Reference Models

Select Tools

Develop BaselineArchitecture Description

DevelopTargetArchitecture Description

Do Gap AnalysisRoadmap

Components

Impact on Architecture

Review with Stakeholders

ArchitectureDefinition Document

Finalize Architecture

Phase C: Information System Architecture

Workproduct: Data Migration Diagram

Workproduct: Application Communication Diagram

Phase D: Technology Architecture

Phase E: Opportunities and Solutions

Phase F: Migration Planning

Phase G: Implementation Goverance

Phase H: Architecture Change Management

Phase Interation

Content Metamodel

Enterprise Continuum

Architecture Repository

Capability Framework

Example Reference Architecture

TOGAF 9 People Certification

Architecture at a Glance

Performance & Quality Attributes

Key Dimensions of an Architecture Verification&

ValidationData Structure Behavior

SA) Business / Operational Layer

Service (Capability) Layer

Logical System Layer

Physical System (Hardware, Software) Layer

•An Architecture Has Breadth and Depth•Breath covers as a minimum the Data, Structure and Behavior (Service)•Depth includes the Business/Operational, Service, & System Layers (logical and Physical)

•Trades are used to derive an optimum solution to solve the Business Problems•Gray scale shows relative emphasis to the Layers

Trades

Drives Verifies

The Matrix – Section 1

Architecture Conceptual Layers

Architecting Methods & Tools

Framework / Method

Modeling Language(Covering: Use Cases, Behavior, Data,

and Structure)

Enterprise / Operational Architecture

Service Architecture (Abstract)

System Architecture (Abstract)

Implementation Physical Architecture (Architecting To The Edge) A

**Quality Attributes (QA) Principles & Standards

Information Security(Confidentiality ,Integrity,

Availability)Safety

(Reliability…)

Openness (Cost reduction,

Open Competition) Timeliness

Enterprise / Operational ArchitectureCyber Security Policy

Threat / Risk Assessment

Safety Policy Threat / Risk Assessment

Service Architecture (Abstract)Cross Domain Security

Implementation Physical Architecture(Architecting To The Edge)

Network Security Platform Security

MILSMILS Profile, API

SC JAVARTSJ

Multi-Core API

**Quality Attributes are Non-Functional Characteristics of an Architecture

**Quality Attributes are Assured through V & V and Associated Methods and Testing

Quality Attributes Assurance: Validation & Verification (V&V)

Information Security(Confidentiality, Integrity,

Availability)Safety

(Reliability…)

Openness (Cost reduction,

Open Competition) Realtime-ness

Enterprise / Operational Architecture

Vulnerability Assessment

Safety Assessment

Service Architecture (Abstract)Cross Domain

SecurityMLS Use Case

Verification

CC Evaluation DO-178B

Implementation Physical Architecture (Architecting To The Edge)

RTESF: TOGAF to the Platform

WorkproductProducer

BusinessVisionary

Descriptive

Prescriptive

Traceable?

Complete Process for Multiple Domains

Toolable

…process

If one removed that Business Goal would the workproduct stop?

Workproduct

BusinessGoal

Assurance Additions

Assurance has extra Roles, Skills, Process Steps, and Workproducts to add to ADM

Assurance has its ownReference models to Add

Assurance has its ownMeta-models to AddTo the Content Framework

Assurance has extendedGuidance on how to developAssured Systems

Assurance has extraThings that must be stored in a repository

Assurance has extraThings that must be done to ensure an Assurance capability is built in an organization

RTESF TOGAF to the Platform Big Picture

TOGAF(Modeled)

RTESF Plugin

DevelopmentProcess (e.g.

RTESFTechnologyProcess

MARTEINCOSE OOSEM?

RTESF ReferenceModel etc.

ADMDomain Specific GuidanceRoles (i.e. Skill Sets)Added WorkproductsAdded TasksEtc.

Assurance Cases

Process?

Acceleo

RT Java 5With Annotations

System

Enterprise

“Electronics”

Software

Implementations

Phase D

How: Modeling And Plugins

Base TOGAF Plugin

Tailoring Plugin

“weave”

Tailored Process (e.g. HTML)

1. Changes: Name changes (we call phase B task 2 “this” instead of “that”2. Replacements: Instead of doing Phase B task 2, we require one to do this task3. Additions: after doing Phase B task 2 , then we add this extra task4. Workproducts: you must do an additional workproduct out of that task5. Roles: there is a role on the team for a person with these real-time skill sets

New Task

New Role New Workproduct

Primitives

Value: Process Adoption is Quicker because one does not Have to start from scratch.

HTML output from EPF

Plugin TypesWhat if we could give a industry vertical version of TOGAF (e.g. Banking)? What about a domain version of TOGAF (e.g. Real-time)?

TOGAF Tailoring

Industry Domain( e.g. Banking)

Technology Domain( e.g. SOA)

Disipline Domain( e.g. Security, Realtime)

Techniques( e.g. ROI)

Modularized TOGAF

Specific Workproducts(e.g. DODAF)

More/Less Detailed Modules

Multi-Module Issue

Base TOGAF Plugin

e.g. SOA, Security, High Assurance

Extentsion Plugin

“weave”

“Requirement: need to be able to extend TOGAF with many different extensions at the same time”

e.g. HTML

Value: Less Risk of AdoptionWhat if we could make your investment in TOGAF sustainable (i.e. minimal changes when we go from version n to n+1)?

Base TOGAF Plugin

Future TOGAF Changes

“weave”

New TOGAF Plugin

Need to Retain investment in tailoring as new releases comeAlso mitigates rate-of-change issues

Base TOGAF Plugin $

Imagine This: Benchmarking

What if we could benchmark different configurations of TOGAF?

Isn’t this what every industry is trying to get to… Capability Maturity Models (CMM)That allow one to measure and improve a process…

Eclipse Process Framework (EPF)

EPF: Work Breakdown

RTESF TOGAF to the Platform Big Picture

TOGAF(Modeled)

RTESF Plugin

DevelopmentProcess (e.g.

RTESFTechnologyProcess

MARTEINCOSE OOSEM?

RTESF ReferenceModel etc.

ADMDomain Specific GuidanceRoles (i.e. Skill Sets)Added WorkproductsAdded TasksEtc.

Assurance Cases

Two Areas of Interaction with TOGAF

• (Area 1) Extend TOGAF to include Real-time and Embedded concepts (Requirement: Add Extentions into TOGAF)

• (Area 2) Integrate TOGAF with a much more prescriptive process such as RUP (Rational Unified Process) or openUp, for a complete Enterprise to working code approach to Real-time and Embedded projects

New Task

New RoleNew Workproduct

Requirement: Integrate TOGAF with other Processes and Lifecyces

Descriptive

Prescriptive

TOGAF Realm

e.g. RUP or openUP Realm

touchpoints

workproducts<<flow>>

<<produce>>

<<reference>>

openUP Model

TOGAF Model

Reference

• See http://www.aprocessgroup.com/products/product_02_010402.asp

• http://www.opengroup.org/architecture/togaf9-doc/epf/

Assurance Cases

SysA Metamodels of Interest• ARM (Argumentational Metamodel)

• SAEM (Software Assurance Evidence Metamodel)

These are being combined into one metamodel:

• SACM (Structured Assurance Case Metamodel)

Toulmin’s Model

the position or claim being argued for; the conclusion of the argument

exceptions to the claim; description and rebuttal of counter-examples and counter-arguments

reasons or supporting evidence that bolster the claim

specification of limits to claim, warrant and backing. The degree of conditionality asserted (Assumptions)

support, justification, reasons to back up the warrant

the principle, provision or chain of reasoning that connects the grounds/reason to the claim.

Implications

Toulmin’s Example

SAEM And ARM

Claims & Arguments

Evidence

artifacts

Statements

‘Leaf’ Statements

Things/Relations

Inferential support between

statements

Assurance Case

ISO 15026

Propositions are based on a particular

ontology

Leaf Claims require

non-inferential support

Who did What Whenontology/vocabulary

Evidence documentadministrative

Evidence element

from ARM

fact model

Claims and subclaims

ARM Metamodel

SAEM Meta-model

Toulmin: Warrant

Supported By

Strategy

A strategy describes the nature of the inference that exists between one or more goals and another goal.

presents a claim forming part of the argument.

SolutionToulmin: Evidence

Example: From D-CASE

D-CASE Tool

D-CASE: Assurance Case Process Metamodel (ACPM)

Yutaka MatsunoUniversity of Tokyo, Japanmatsu@cc.u-tokyo.ac.jp

D-CASE: Changing the Basic Process

Summary

RTESF (Real-Time Embedded System Forum) of The Open Group is forging TOGAF to the Platform, Why don’t you join us!

Questions we AnsweredWhy Architecture: Engineering “V” show us that we need to capture errors soonerWhat is Architecture: Capturing Larger ContextWhat do we do with Architecture: Manage the “illities”What Level do we want with Architecture: Enterprise, nothing less will doWhat Architecture Standard do we use: TOGAF 9

ProjectsTOGAF to the PlatformAssurance Cases with D-CASE

architecture centric engineering and togaf to · pdf fileexample reference architecture ......

Documents

sabsa and togaf enterprise security architecture at...

enterprise architecture implementation and the open group...

the open group architecture framework (togaf) · the open...

building business & it architecture roadmaps with archimate...

togaf simplified - part 7 - architecture capability...

introduction to enterprise architecture and togaf 9.1

the open group architecture framework (togaf)

togaf the open group architecture framework. togaf the open...

togaf 9 - security architecture ver1 0

architecture centric engineering and togaf to platform ·...

enterprise architecture & togaf

togaf – architecture development method (adm)

agile, togaf and enterprise architecture: will they blend?

penerapan togaf architecture development method pada

introduction to enterprise architecture framework and togaf

will they blend? - agile, togaf and enterprise architecture

togaf presentation for · pdf filetogaf presentation for...

the open group architecture framework (togaf)...

enterprise architecture togaf - introduction to... ·...

building it architecture for developing nations using togaf...