What does an architect need to know

What does an Architect

need to know?

Jim Wilt

Børge HansenArchitect EvangelistMicrosoft Norway

[email protected]://borge3000.no

What does an Architect

need to know?

Jim Wilt

Thank You(please remember to fill out an

evaluation)

(including the kitchen sink)

Are you (or is your organization) looking for an end-all fix-everything for-every-situation approach?

To effectively do this, an Architect Needs...

• An Architectural Body of Knowledge (ARBOK)

What is the Business Strategy?

How is this communicated to all involved?

Is an Enterprise Architecture Needed?

Are you up on Zachman, TOGAF, FEAF, PBA, EATK?

Which SDLC models will Reduce Risk/Add Value?

Are your model choices aligned with business needs, team skills and stakeholder understanding?

Balancing your Architectural Practices

• Are Patterns part of your practices?

Is your Maturity Model more than a buzz-word?

It all works together!

Did you Design for Operations?

Wow! That’s a lot to Know!• How do I stay educated on all this?

Pres

crip

tive

Driv

en Adoptive Driven

CollaborativCollaborativee

Community Community DrivenDriven

CollaborativCollaborativee

Community Community DrivenDriven

Succeeding by Failing Less…

If we reduce our un-success by 30% (that’s still 46% failure)we can save $M annually (small, medium, and large)

By using our architectural smarts, we can reclaim lost ground to both misperceptions and actual performance…

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after

the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Our Architectural Knowledge is the Key to our Success…

…the Fruits of this Knowledgeare only found in

Our Practice of Architecture

References & LinksWhere to Learn More:

http://msdn.microsoft.com/en-us/architecture/default.aspx

http://www.iasahome.org/web/home/taxonomy

http://www.omg.org/technology/documents/spec_catalog.htm

References & LinksThe Total Solution Life Cycle (TSLC)http://msdn.microsoft.com/en-us/library/bb756611.aspx

Bijay K. Jayaswal, Peter C. Patton, "Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software", Prentice Hall, 2007

Kaplan, Robert S. and Norton, David P., Strategy Maps: Converting Intangible Assets into Tangible Outcomes, Boston: Harvard Business School Press, 2004

Kim, W. Chan, and Mauborgne, Renée, Blue Ocean Strategy: How to Create Uncontested Marketspace and Make the Competition Irrelevant, Harvard Business School Press, 2005

Christensen, Clayton M., The Innovator’s Dilemma, Harvard Business School Press, 1997

Schekkerman, Jaap. How to Survive in the Jungle of Enterprise Architecture Frameworks: Creating or Choosing an Enterprise Architecture Framework, Jaap Schekkerman, Trafford 2004

Sessions, Roger. “Comparison of the Top Four Enterprise Architecture Methodologies” whitepaper, http://www.objectwatch.com/whitepapers/4EAComparison.pdf

Sessions, Roger. Simple Architectures for Complex Enterprises, Microsoft Press 2008.