1 july 26, 2008 copyright © 2008 joseph f iaquinto, pe. all rights reserved. enterprise...

1

July 26, 2008

Copyright © 2008 Joseph F Iaquinto, PE. All rights reserved.

Enterprise ArchitectingFor

The System Engineer

Introduction To ATutorialBy

Joseph F Iaquinto, [email protected]

September 19, 2008

2

July 26, 2008

IntroductionObjectives


SE Experience

SE Knowledge

DecisionSupport

3

July 26, 2008

Complete Tutorial’s Agenda

• Introduction: What is EA as Compared to SE• Fundamentals of EA Analysis• EA Visual Analysis• EA Numerical Modeling and Analysis• Reasoning About EAs• EA Information Modeling – Static• EA Information Modeling – Dynamic and Stochastic• EA Robustness• EA Special Topics


4

July 26, 2008

Introduction

What is EA as Compared to SE


5

July 26, 2008


Enterprise Architecting isSignificantly Different From

System Engineering

6

July 26, 2008


IntroductionA Different Vision

7

July 26, 2008


IntroductionA Different Mission

Describe how to make

Characterizes

8

July 26, 2008


IntroductionDifferent Products

CoordinatedRationalization

Insight

9

July 26, 2008


IntroductionComparison of Products

SE Doc Tree

EA Repository

10

July 26, 2008


IntroductionZachman Comparison

11

July 26, 2008


IntroductionProcess of Enterprise Architecting

DetermineMotivation

For TheEnterprise

Formulate The

Enterprise

Detail The

Enterprise

CertifyThe

Enterprise

ObtainStakeholder’s

ApprovalStrong Influence Moderate Influence

12

July 26, 2008


IntroductionProcess of Formulating The Enterprise

Formulate The

Enterprise

FormulateThe

DesiredResults

FormulateA

Course ofAction

FormulateThe

Governance

13

July 26, 2008


IntroductionSkills Required By The Enterprise Architect

LiberalArts

EngineeringAnalysis

ClericalSkills

14

July 26, 2008


IntroductionPractical Advice

Verify There Is Leadership Insight Versus ElaborationRapport Versus StandardsLearn the Business Versus Technical

CoolnessInnate Versus Artifacts

15

July 26, 2008


IntroductionSE A Springboard to EA

Now that we have a mapLet’s begin the journey

SystemEngineering

EnterpriseArchitecting

ExperienceAdditional Skills

Beware Basis of Success

16

July 26, 2008

Introduction:Tutorial Skills Applied To EA Process


Skill / Process Determine Motivation Formulate Enterprise Detail Enterprise Certify Enterprise Obtain Stakeholder Approval

Visual Analysis — Stakeholders /Concerns I Views

Primary— Who needs what and why do they want it. What is their

nomenclature?

Design general views to address general concerns of specific stakeholders

Design specific views to relate enterprise details to specific stakeholder concerns

Select specific stakeholder / concerns / views as "test cases"

Select stakeholderconcerns for supporting arguments.

Data Modeling and Analysis

Elaborate stakeholder concern into engineering problem statement.

Primary — perform general Deming / Ishikawa analysis to discover general problems — postulate their enterprise solutiondecisions

Perform specific Deming / Ishikawa analysis asrequired to support detailed enterprise solutiondecisions

Formulate experiments based upon Deming / Ishikawa to certify related concerns have been addressed

Utilize results of Deming / Ishikawa experiments in arguments.

Reasoning about EAs— The Art ofArgumentation

Provide warrants for changes to motivation (vision, goals, objectives)

Warrant each conceptual EA element andrelationship

Warrant each detailed EA element and relationship

Establish arguments that demonstrate the enterprise has been constructed according to the EA plans

Primary - Presentarguments to Stakeholders that the EA as built addresses their concerns.

Information (Data) Modeling — Static

Model influencers, vision, goals, objectives and their relationships

Model strategies, tactics and business functions

Model products, processes,

organization, locations, etc.

Model implemented enterprise for comparison to EA

Exploit entire model esp. relationships in warranting concerns satisfaction

Information Modeling — Dynamic and Stochastic

Model changes influencers, vision, goals, objectives and relationships

Model and forecast changes in strategies, tactics and business functions

Model changes in products, processes, organization, location, etc.

Provide potential change capability in EA per potential change in significant motivation

Exploit potential change in capability in EA per potential change in motivation in warranting concerns satisfaction

Robustness Failures / compensatory actions related tomotivation; Enterprise Politics; Sensitivity to Technology

Failures / compensatory actions related to modeling and analysis; political implications; Sensitivity to Technology

Failures / compensatory actions related to products, processes, organizations, locations, political implications, sensitivity to technology

Are compensatory actions implemented and do they work; politics work; proper isolation of technology

Exploit robustness analysis in warranting concerns are satisfied

17

July 26, 2008

IntroductionFoundations: System Theory


•CONOPS•Requirements•Specifications•Configuration Management•Project Management•Mapping and Tracing

•Modeling•Steady State & Transient•Deterministic vs. Non•Information Theory•Cybernetics

•Analysis•Calculus•Searches / Graph Theory •Stochastic Systems

18

July 26, 2008

IntroductionModeling the Effects of Time


Bus

ines

s O

bjec

tive

Time

Transient Behavior

Steady State Behavior

19

July 26, 2008

IntroductionModeling Uncertainty


Pro

babi

lity

Pro

duct

Qui

ts

510 105 15

Process A

Process B

20

July 26, 2008

IntroductionModeling Information


Relationships

Parent Verb Phrase Child

InformationTechnologyRequirement may be satisfied by Architecture

InformationTechnologyRequirement is supported by System

InformationTechnologyRequirement specifies Task

Materiel is related to Materiel

Materiel may be represented by MilitaryPlatform

Materiel is represented by Node

Materiel participates in Organization

MilitaryPlatform is related to MilitaryPlatform

MilitaryPlatform is employed in support of Mission

MilitaryPlatform is represented by Node

Organization controls payload for Satellite

Organization controls platform for Satellite

Organization participates in Materiel

OrganizationType is cited by Architecture

OrganizationType is cited for Node

OrganizationType is related to OrganizationType

OrganizationType is referenced in Document

OrganizationType classifies Organization

OrganizationType has responsibility for System

Satellite may serve as a MilitaryPlatform

Satellite is related to Satellite

System is responsibility of OrganizationType

System includes Satellite

21

July 26, 2008

IntroductionModeling Equilibrium or Tendencies


New Customers

Wear Outs

Stolen

Destroyed

Product Demand

Enterprise Measure

22

July 26, 2008

IntroductionAnalysis by Calculus


Optimization

Business Goal

Business Objective

Business Objective

ConsequentialAnalysis

23

July 26, 2008

IntroductionAnalysis by Graph Theory


A

B

24

July 26, 2008

IntroductionAnalysis of Uncertainty


Business Objective:Repair Turnaround

within 3 days

TechnicianAvailability

SparesAvailability

DiagnosisTime

Parts Change

Time

Shipping Time

?

25

July 26, 2008

IntroductionOur Example Enterprise


The Auto-Mower Company

Auto-Mower

Finance SalesEngineering

ManufacturingCustomer Service

Transportation

One CompanyLocation

1 july 26, 2008 copyright © 2008 joseph f iaquinto, pe. all rights reserved. enterprise...

Documents

joseph f iaquinto

se copyright

ea process copyright

introduction se

introduction skills

governance slide

system engineering slide

different vision slide