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 Solutionsgundars.osvalds@redarchsolutions.comgundars.osvalds@redarchsolutions.com

July 12, 2006July 12, 2006

AgendaAgenda

Architecture PerspectivesArchitecture Perspectives Use of ArchitectureUse of Architecture The Good; The Bad; The UglyThe Good; The Bad; The Ugly Architecture Development IssuesArchitecture Development Issues The Curse of PowerPointThe Curse of PowerPoint Use and Misuse of ToolsUse and Misuse of Tools Contractor ResponsibilitiesContractor Responsibilities Customer ParticipationCustomer Participation ConclusionConclusion

Architecture PerspectivesArchitecture Perspectives

The Emperor’s New Architecture by Gundars Osvalds

© G

un

da

rs.O

sva

lds@

Re

dA

rch

So

lutio

ns.

com

I love architecture.

Can you create me a new one?

I will create you a great architecture!

It will show everyone my greatness! Contractor

Emperor

Emperor

Its progressing nicely.

I am using the best of breed frameworks. I need more gold to finish.

It is incomparable

!

FRAMEWORKS:FEAF, DoDAF,

TOGAF, Zachman

Emperor

Contractor

Manager

Look at my great

architecture!

I do not recognize the architecture, but I can’t let on.

I am determined to see this through, after all I am the Emperor.

But its not an architecture!

Emperor

Contractor

Architect

Use of ArchitectureUse of Architecture

To represent the needs of the StakeholdersTo represent the needs of the Stakeholders Provides information on which decisions can be Provides 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 in Create component specifications used in

implementation implementation

Emperor

The GoodThe Good

It is generally recognized that one must develop It is generally recognized that one must develop an architecture to provide a description of how the an architecture to provide 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 Before a Federal program is approved an architecture is required architecture is required • The Department of Defense Architecture Framework The Department of Defense Architecture Framework

DoDAF is mandated for DoD programsDoDAF is mandated for DoD programs• Federal Enterprise Architecture Framework and Federal Enterprise Architecture Framework and

Consolidated Reference Models are required by the Office Consolidated Reference Models are required by the Office of Management and Budgetof Management and Budget

Industry has developed architecture frameworks to Industry has developed architecture frameworks to be used as architecture development references be used as architecture development references • The Zachman Framework, referenced by DoDAF, FEAF, The Zachman Framework, referenced by DoDAF, FEAF,

and tool vendorsand tool vendors• The Open Group Framework, supported and used by The Open Group Framework, supported and used by

industry consortiumindustry consortium

The BadThe Bad

Focus is on delivery of products not Focus is on delivery of products not resultsresults It’s a paper exercise not focused on addressing It’s a paper exercise not focused on addressing

• The needs of the Stakeholder, Owners, Users, The needs of the Stakeholder, Owners, Users, Developers, Managers.Developers, Managers.

• The use of the architecture: Portfolio Management, IT The use of the architecture: Portfolio Management, IT Investments, Identify Duplication and Gaps, Evaluate Investments, Identify Duplication and Gaps, Evaluate Business Functions Support, Develop Systems Business Functions Support, Develop Systems Specifications, Support System Design. Specifications, Support System Design.

An architecture process in itself does not An 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 results What matters is how one uses it and what results come from itcome from it

The UglyThe Ugly

Many times engineering principles are not followedMany times engineering principles are not followed Frequently architecture processes are ignored or Frequently architecture processes are ignored or

not understoodnot understood If architecture doesn't produce results it will be If architecture doesn't produce results it will be

“de-funded”“de-funded” There is a lack of:There is a lack of:

• Planning and vision of what architecture products and Planning and vision of what architecture products and processes are needed,processes are needed,

• Management support,Management support,• Technical oversight and control,Technical oversight and control,• Understanding of goals and requirements of system.Understanding of goals and requirements of system.

Focus is on products, not what architecture goals Focus is on products, not what architecture goals they supportthey support

Architecture DevelopmentArchitecture DevelopmentIssuesIssues

Products are defined by management without Products 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 that Products 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 not Need to conform to a specified framework that is not

fully defined (i.e., DoDAF, FEA, ZF, TOGAF)fully defined (i.e., DoDAF, FEA, ZF, TOGAF) Consensus does not always provide the desired Consensus does not always provide the desired

solutionsolution• A Chief Architect must be empowered to validate and A Chief Architect must be empowered to validate and

verify the resultsverify the results There needs to be a process for product sign-offThere needs to be a process for product sign-off

• Products are delivered on whose authority? Products are delivered on whose authority?

Manager Architect

The Curse of PowerPointThe Curse of PowerPoint

Reduces all subjects to a series of bulletsReduces all subjects to a series of bullets Watering down of engineering issues reduces ability of Watering down of engineering issues reduces ability of

management to make educated decisionsmanagement to make educated decisions• The Columbia space shuttle Accident Board concluded that “At The Columbia space shuttle Accident Board concluded that “At

NASA endemic use of PowerPoint has been substituted for NASA endemic use of PowerPoint has been substituted for rigorous analysis”rigorous analysis”

Two recommended approaches in developing PowerPoint Two recommended approaches in developing PowerPoint presentations that are based on the engineered architecturepresentations that are based on the engineered architecture• Develop conceptual presentation slides and verify against the Develop conceptual presentation slides and verify against the

architectural productsarchitectural products• Develop architectural products and then use them or illustrate Develop architectural products and then use them or illustrate

for presentationfor presentation Make sure that story told is consistent with the engineered Make sure that story told is consistent with the engineered

productsproducts

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 develop The architect can use a tool operator to develop

the products under their guidance the products under their guidance • It is the responsibility of the architect for the product It is the responsibility of the architect for the product

deliverabledeliverable It is not the tool vendor’s responsibility to define It is not the tool vendor’s responsibility to define

the processthe process Diagrams may be incompatible because they are Diagrams may be incompatible because they are

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

industry specified diagramsindustry specified diagrams• Thus diagram interchange between tools may not be Thus diagram interchange between tools may not be

possiblepossible

Contractor ResponsibilitiesContractor Responsibilities

The Contractor is the Doctor; the Customer is the The Contractor is the Doctor; the Customer is the PatientPatient• Listen to the customer; Educate the customer; Propose Listen to the customer; Educate the customer; Propose

solutions,solutions,• Contractors must state their concerns to the customer,Contractors must state their concerns to the customer,• Satisfying the customer is a delicate balance.Satisfying the customer is a delicate balance.

Work with customer to determine their customer Work with customer to determine their customer architectural viewpointarchitectural viewpoint• Such as: Contextual, Conceptual, Business, Logical, Such as: Contextual, Conceptual, Business, Logical,

PhysicalPhysical Customize framework models to address Customize framework models to address

customer needs customer needs

Contractor

Customer ParticipationCustomer Participation

Should be knowledgeable in architectural Should be knowledgeable in architectural conceptsconcepts

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 “gates”Should 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

ConclusionConclusion

Systems Engineers performing the duties of the Systems Engineers performing the duties of the Architect must be responsible for the engineering Architect must be responsible for the engineering integrity of the architecture productsintegrity of the architecture products

The architect should educate the customers in The architect should educate the customers in the development and use of architecture productsthe development and use of architecture products

It must be the goal of all that the developed It must be the goal of all that the developed architectural description is usable for architectural description is usable for • Tradeoffs,Tradeoffs,• Planning,Planning,• Costing,Costing,• Implementation.Implementation.

The architecture must be useful to all of its StakeholdersThe architecture must be useful to all of its Stakeholders

Emperor Contractor Manager Architect