Successfully reported this slideshow.

What does an architect need to know


Published on

What does an architect need to know

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

What does an architect need to know

  1. 1. What does an Architect need to know? Jim Wilt Børge Hansen Architect Evangelist Microsoft Norway [email_address]
  2. 7. What does an Architect need to know? Jim Wilt
  3. 8. Thank You (please remember to fill out an evaluation) (including the kitchen sink)
  4. 9. Are you (or is your organization) looking for an end-all fix-everything for-every-situation approach?
  5. 10. To effectively do this, an Architect Needs ... <ul><li>An Architectural Body of Knowledge (ARBOK) </li></ul>
  6. 11. What is the Business Strategy? <ul><li>How is this communicated to all involved? </li></ul>
  7. 12. Is an Enterprise Architecture Needed? <ul><li>Are you up on Zachman, TOGAF, FEAF, PBA, EATK? </li></ul>
  8. 13. Which SDLC models will Reduce Risk/Add Value? <ul><li>Are your model choices aligned with business needs, team skills and stakeholder understanding? </li></ul>
  9. 14. Balancing your Architectural Practices <ul><li>Are Patterns part of your practices? </li></ul><ul><li>Is your Maturity Model more than a buzz-word? </li></ul><ul><li>It all works together! </li></ul><ul><li>Did you Design for Operations? </li></ul>
  10. 15. Wow! That’s a lot to Know ! <ul><li>How do I stay educated on all this? </li></ul>Collaborative Community Driven Prescriptive Driven Adoptive Driven
  11. 16. 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…
  12. 17. © 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.
  13. 18. Our Architectural Knowledge is the Key to our Success… … the Fruits of this Knowledge are only found in Our Practice of Architecture
  14. 19. References & Links Where to Learn More:
  15. 20. References & Links The Total Solution Life Cycle (TSLC) Bijay K. Jayaswal, Peter C. Patton, &quot; Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software &quot;, 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, Sessions, Roger. Simple Architectures for Complex Enterprises , Microsoft Press 2008.