presentation from july 12, 2006 dinner meeting

8/9/2019 Presentation from July 12, 2006 Dinner Meeting

1/13

Use of Architecture for Engineering Systems;Use of Architecture for Engineering Systems;

The Good, The Bad, and The UglyThe Good, The Bad, and The Ugly

Gundars OsvaldsGundars Osvalds

Technology FellowTechnology Fellow

Red Arch SolutionsRed Arch Solutions

[email protected]@redarchsolutions.com

July 12, 2006July 12, 2006


2/13

ContentsContents

Architecture PerspectivesArchitecture Perspectives

Use of ArchitectureUse of Architecture

The Good; The Bad; The UglyThe Good; The Bad; The Ugly

Architecture Development IssuesArchitecture Development Issues Curse of PowerPointCurse of PowerPoint

Use and Misuse of ToolsUse and Misuse of Tools

Contractor ResponsibilitiesContractor Responsibilities

Government ParticipationGovernment Participation ConclusionConclusion


3/13

Architecture PerspectivesArchitecture Perspectives

The Emperors New Architecture

Gundar s

Osvald

s,RedArchSolutio n

s

I love

architecture.

Can you

create me a

new one?

I will createyou a great

architecture

!

It will show

everyone

my

greatness! Contractor

Emperor

Emperor

Its progressing nicely.

I am using

the best ofbreedframeworks. I needmore goldto finish.

It is

incomparable

!

FRAMEWORKS:

FEAF, DoDAF,

TOGAF,

Zachman

Emperor

Contractor

Manager

Look at my

great

architecture!

Engineer

I do not

recognize the

architecture, butI cant let on.

I am

determined to see

this

through,

after all I

am the

Emperor.

But its not

an

architecture!

Emperor

Contractor


4/13

Use of ArchitectureUse of Architecture

To represent the needs of the StakeholdersTo represent the needs of the Stakeholders

Provides information on which decisions can beProvides information on which decisions can be

mademade

Models business conceptsModels business concepts Basis for effort cost and schedule estimatesBasis for effort cost and schedule estimates

Supports definition of objectivesSupports definition of objectives

Create component specifications used inCreate component specifications used in

implementationimplementation

Emperor


5/13

The GoodThe Good

It is generally recognized that one must develop anIt is generally recognized that one must develop an

architecture because it provides a description of how thearchitecture because it provides a description of how the

needs of the stakeholder will be metneeds of the stakeholder will be met

Before a Federal program is approved an architecture isBefore a Federal program is approved an architecture is

requiredrequired

The Department of Defense Architecture Framework DoDAF isThe Department of Defense Architecture Framework DoDAF is

mandated for DoD programsmandated for DoD programs

Federal Enterprise Architecture Framework and ConsolidatedFederal Enterprise Architecture Framework and Consolidated

Reference Models are required by the Office of ManagementReference Models are required by the Office of Management

and Budget because of the Clinger-Cohen Actand Budget because of the Clinger-Cohen Act

Industry has developed architecture frameworks to be usedIndustry has developed architecture frameworks to be usedas architecture development referencesas architecture development references

The Zachman Framework, referenced by DoDAF, FEAF, andThe Zachman Framework, referenced by DoDAF, FEAF, and

tool vendorstool vendors

The Open Group Framework, supported and used by industryThe Open Group Framework, supported and used by industry

consortiumconsortium


6/13

The BadThe Bad

Focus is on delivery of products notFocus is on delivery of products not resultsresults Its a paper exercise not focused on addressing theIts a paper exercise not focused on addressing the

needs of the:needs of the: Stakeholder,Stakeholder,

Owners,Owners, Users,Users,

Developers,Developers,

Managers.Managers.

An architecture process in itself does notAn architecture process in itself does not

necessarily result in a useable architecturenecessarily result in a useable architecture What matters is how one uses it and what resultsWhat matters is how one uses it and what results

come from itcome from it


7/13

The UglyThe Ugly

Engineering principles are not followedEngineering principles are not followed

Architecture processes are ignored or not understoodArchitecture processes are ignored or not understood

If architecture doesn't produce results they will be de-If architecture doesn't produce results they will be de-

fundedfunded

Lack of:Lack of: Planning and vision of what architecture products and processesPlanning and vision of what architecture products and processes

are needed to support the needs of the customers of theare needed to support the needs of the customers of the

architecture,architecture,

Management support,Management support,

Technical oversight and control,Technical oversight and control, Understanding of goals and requirements of system to beUnderstanding of goals and requirements of system to be

modeled.modeled.

Focus is on products not what architecture goals theyFocus is on products not what architecture goals they

supportsupport


8/13

Architecture DevelopmentArchitecture Development

IssuesIssues

Products are defined by management withoutProducts are defined by management without

understanding or consultation with engineersunderstanding or consultation with engineers

Political needs mandate deliverablesPolitical needs mandate deliverables

Products become stylized PowerPoint presentations thatProducts become stylized PowerPoint presentations that

may not be traceable to the engineered architecturemay not be traceable to the engineered architecture

Need to conform to a specified framework that is notNeed to conform to a specified framework that is not

fully definedfully defined

Consensus does not always provide the desiredConsensus does not always provide the desired

solutionsolution A Chief Architect needs to be empowered to validate andA Chief Architect needs to be empowered to validate and

verify the resultsverify the results

ManagerEngineer


9/13

Curse of PowerPointCurse of PowerPoint

Reduces all subjects to a series of bulletsReduces all subjects to a series of bullets

Watering down of engineering issues reduces ability ofWatering down of engineering issues reduces ability of

management to make educated decisionsmanagement to make educated decisions

The Columbia Accident Board concluded that At NASA endemic useThe Columbia Accident Board concluded that At NASA endemic use

of PowerPoint has been substituted for rigorous analysisof PowerPoint has been substituted for rigorous analysis

Two recommended approaches in developing PowerPointTwo recommended approaches in developing PowerPointpresentations that are based on the engineered architecturepresentations that are based on the engineered architecture

Develop conceptual presentation slides and verify against theDevelop conceptual presentation slides and verify against the

architectural productsarchitectural products

Develop architectural products and then use them or illustrate forDevelop architectural products and then use them or illustrate for

presentationpresentation

Make sure that story told is consistent with the engineeredMake sure that story told is consistent with the engineered

productsproducts


10/13

Use and Misuse of ToolsUse and Misuse of Tools

A tool operator is not an architectA tool operator is not an architect

The architect can use a tool operator to developThe architect can use a tool operator to develop

the products under their guidancethe products under their guidance

It is the responsibility of the architect for the productIt is the responsibility of the architect for the product

deliverabledeliverable

It is not the tool vendor responsibility to defineIt is not the tool vendor responsibility to define

the processthe process

Diagrams may be incompatible because they areDiagrams may be incompatible because they are

based on different methodologiesbased on different methodologies Each tool may have custom implementation ofEach tool may have custom implementation of

industry specified diagramsindustry specified diagrams

Thus diagram interchange between tools may not beThus diagram interchange between tools may not be

possiblepossible


11/13

Contractor ResponsibilitiesContractor Responsibilities

Must state their concernsMust state their concerns ObjectivesObjectives

GoalsGoals

ResultsResults

PurposePurpose The contactor is the Doctor the customer theThe contactor is the Doctor the customer the

PatientPatient Need to listen to their needsNeed to listen to their needs

Educate the customerEducate the customer

Propose solutionsPropose solutions

Work with customer to determine their customerWork with customer to determine their customerarchitectural viewpointarchitectural viewpoint Propose custom products based on engineeredPropose custom products based on engineered

architecturearchitecture

Contractor


12/13

Customer ParticipationCustomer Participation

Needs to be knowledgeable in architectural conceptsNeeds to be knowledgeable in architectural concepts

Must have an engineering process that defines:Must have an engineering process that defines:

Which Framework will be used,Which Framework will be used,

Product description,Product description,

Relationships between products,Relationships between products,

Purpose and user of each product.Purpose and user of each product.

Should define project gatesShould define project gates

Intermediate results can be evaluatedIntermediate results can be evaluated

Effort should be redone if not satisfiedEffort should be redone if not satisfied

Emperor


13/13

ConclusionConclusion

Systems Engineers must be responsible for theSystems Engineers must be responsible for the

engineering integrity of the architecture productsengineering integrity of the architecture products

They need to educate the customers in theThey need to educate the customers in the

development and use of architecture productsdevelopment and use of architecture products

It must be the goal of all that the developedIt must be the goal of all that the developed

architectural description is usable forarchitectural description is usable for

Tradeoffs,Tradeoffs,

Planning,Planning,

Costing and,Costing and,

Implementation.Implementation.

The architecture must be useful to all of itsThe architecture must be useful to all of its

customerscustomers

ManagerEngineerEmperor Contractor

presentation from july 12, 2006 dinner meeting

Documents