1 / 26

Architect Persona’s & Architecture – Demystified

Architect Persona’s & Architecture – Demystified. S. Srinivasa Sivakumar Enterprise Architect, Microsoft Consulting Services. Warring… . Introduction…. What is next?. ?. Is Architect role right for me? What types of architects are there? Where an I heading? Where is there growth?

fleur
Télécharger la présentation

Architect Persona’s & Architecture – Demystified

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Architect Persona’s & Architecture – Demystified S. Srinivasa Sivakumar Enterprise Architect, Microsoft Consulting Services

  2. Warring…

  3. Introduction….

  4. What is next? ? • Is Architect role right for me? • What types of architects are there? • Where an I heading? • Where is there growth? • What are the options? Technical Roles

  5. Session Theme 1 • Who is an architect? 2 • Architect’s persona’s 3 • Architect Career Path 4 • Technical Career Path

  6. Who Is An Architect? Philippe Kruchten, Grady Booch, Kurt Bittner, and Rich Reitman derived and refined a definition of architecture based on work by Mary Shaw and David Garlan (Shaw and Garlan 1996). Their definition is: “Software architecture encompasses the set of significant decisions about the organization of a software system including the selection of the structural elements and their interfaces by which the system is composed; behavior as specified in collaboration among those elements; composition of these structural and behavioral elements into larger subsystems; and an architectural style that guides this organization. Software architecture also involves functionality, usability, resilience, performance, reuse, comprehensibility, economic and technology constraints, tradeoffs and aesthetic concerns.” • Technology person • Visionary • Understands Strategy • Understands Business Drivers • Understands Domain very well • Has knowledge of your organization’s products • Understands relevant technologies • Understands development processes & lifecycle • Has Modeling skills • Has a view of organizational politics • Understands consulting such as teaching, mentoring, presenting, etc • Providers leadership to the team • Able to set vision for the team • Able to motivate people • Able to build and work with teams • Has excellent written and oral communication skills An Architect is a,

  7. Architect Persona’s

  8. Architect Persona’s Mapping to Business Types Business Types

  9. Application Architect 1 • Architecture • How deep the foundation has to be? • How many pillars are needed? • What are their sizes? • Which construction material to be used? • On what ratio material has to be mixed? • How would the home look? • What features would it have? • How the home will be secured? What type of security systems is needed? • Etc • Design • Structural design • Electrical design • Utility design • Interior design • Development • Construction of the home • Production • Hand over the property

  10. Application Architect 1 Role Application Architect, Software Architect, Technology Architect Owns Overall application architecture and design. Understands Looks up to Works with Defines • Technical depth in one or two technologies • Requirements and Business Impact • Project Management • Resourcing • Scheduling • Timelines • Risk & Risk Mitigation • POC • Rapid Prototyping • Solution architect • Enterprise architect • Project Managers • Business Analyst’s • Designers • Developers • Testers • Infrastructure Architect • Defines Standards for • Application Design • UI • Coding • Coding Templates • Naming convention • Software Patterns • Security • etc Produces • Application architecture (includes layering – both physical & logical, interfaces with external systems, etc.) • High and low level design’s • Database Model & Design Recommended Read • Microsoft Application Architecture Guide, 2nd Editionfrom Microsoft Patterns & Practices (Available on MSDN)

  11. Application Architect 1 Typical Application Architecture • Architecture • Layering – Presentation, Services, Business and Data Layers • Interfaces between layers • High availability of the layers • End to end application security • Design • Component design • Class Diagrams • Sequence Diagrams • etc • Services design • Entity design • Database design • Development • Application Development • Production • Go Live

  12. Infrastructure Architect 2 • Architecture • Type of Soil needed? • How deep can we go on foundation? • Which road connects? • How would we get connected to the water line? • Etc • Design • Complying with structural, electrical, utility design, etc • External infrastructure connectivity with the internal design

  13. Infrastructure Architect 2 Role IT Architect, Systems Architect, Security Architect, Network Architect Owns Overall infrastructure architecture and design with operational requirements. Understands Looks up to Works with Defines • Has good technical breath • Can work with heterogonous technologies • Resourcing • Scheduling • Timelines • Risk & Risk Mitigation • Solution architect • Enterprise architect • Application Architects • Project Managers • Business Analyst’s • Designers • Testers • Defines Standards for • Infrastructure Design • Component level interfaces • Naming convention for servers, objects, … • Security • Monitoring • Management • etc Produces • Manages and maintains infrastructure Risk • High and low level design’s for all the infrastructure components • Works with OEM vendors to mange integration challenges and risk Recommended Read • Windows Server System Reference Architecture (WSSRA) from Microsoft (Available on Microsoft Download Center)

  14. Infrastructure Architect 2 Typical Infrastructure Architecture • Architecture • Understands the operational requirements • Authentication & authorization. • Standard file server solutions. • Security services (such as firewall and IDs). • User provisioning services • PC Life cycle Management • Explicit and tacit knowledge systems. • Communication and collaboration services. • Design • Security design • Network design • Storage design • Support (L1, L2, L3) design • Etc • Development • Aggregating multiple systems together

  15. Solution Architect 3 • Architecture • How deep the foundation has to be? • How many pillars are needed? • What are their sizes? • Which construction material to be used? • On what ratio material has to be mixed? • How would the home look? • What features would it have? • How the home will be secured? What type of security systems is needed? • Etc • Design • Structural design • Electrical design • Utility design • Interior design • Development • Construction of the home • Production • Hand over the property

  16. Solution Architect 3 Role Information Architect, Integration Architect, Data Architect, Service Architect, Cloud Architect Owns Overall solution architecture and design. Understands Looks up to Works with Defines • Technical depth in one or two technologies • Has good technical breath (both Applications & Infrastructure) • Can work with heterogonous technologies • Architectural Trade-Off Matrix • Enterprise architect • Project Managers • Business Analyst’s • Designers • Developers • Testers • Application Architects • Infrastructure Architects • Defines Standards for • Solution Design • Common UI for solution • Software & Integration Patterns • End to end Security • etc Produces • Solution architecture (includes hardware, software, applications, infrastructure, etc.) • Sizing & Capacity planning • Bill of Material & Pricing Recommended Read • Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives by Nick Rozanski

  17. Solution Architect 3 Typical Solution Architecture * From Bredemeyer • Architecture • Layering – Presentation, Services, Business and Data Layers • Interfaces between layers • Design • Structural design • Electrical design • Utilitydesign • Interior design • Development • Construction of the home • Production • Hand over the property

  18. Enterprise Architect 4 • Architecture • How well my organization is running? • How many people are living? • How much land, water, air needed? • How clean is the natural resources? • Is my organization runs with in the corporate governance policy? • Design • Organization design • Electrical design • Utility design • Etc

  19. Enterprise Architect 4 Role Business Architect, Strategic Architect, Chief Architect Owns Overall organization architecture and design Understands Looks up to Works with Defines • Has good technical breath (Apps, Infra, network, etc) • Can work with heterogonous technologies • Understands the domain well • Regulatory compliance • Culture of the organization • CIO • CTO • Board • Application Architects • Solution Architects • Infrastructure Architects • OEM vendors • Project Managers • Business Analyst’s • Defines Standards for • Application and infrastructure portfolio • TCO of IT • Common Looks and feel for solutions • Data Governance and Policies • DR & BCP • Compliance Fx • etc Produces • Creates and runs “Architecture Review & Governance Board” • TCO planning and modeling • Application & infrastructure lifecycle management Recommended Read • Enterprise Architecture As Strategy: Creating a Foundation for Business Execution by Jeanne W. Ross, Peter Weill and David Robertson

  20. Enterprise Architect 4 EA Process • Driven by Business Strategy • CIO Creates multiple initiatives • Works with CIO/CTO creates the IT Strategy • Priorities the initiatives across business priority, cost and value • Drives initiatives with Solution & Infrastructure architects • Provides the governance

  21. Enterprise Architect 4 Enterprise Architecture Frameworks • Federal Enterprise Architecture Framework (FEAF):http://www.gao.gov/bestpractices/bpeaguide.pdf • Department of Defence Architecture Framework (DoDAF):http://cio-nii.defense.gov/docs/DoDAF_Volume_II.pdf • Zachman Framework:http://www.zifa.com/framework.html • TOGAF from Open Group • Gartner Enterprise Architect Framework • Microsoft Business Architecture

  22. Enterprise Architect 4 Enterprise Architect Value Model High Low Organization Maturity Enterprise Architect CIO High Business Highly Technical

  23. Domain Architect 5 • Architecture • How my product/solution will help my customers? • Does it address regulatory compliance • Who are the competitors in the market with similar solutions? • What are the delta advantages of our product with competitions? • Are these positive or negative? • To become positive, what would be the cost? • What would be the ROI? • Etc • Design • Structural design • Electrical design • Utility design • Development • Construction of the product/solution • Production • Presales, Sale of the solution and Deployment

  24. Certifications Enterprise Architecture Frameworks • Enterprise Architecture • Zackman • TOGAF 9 (Latest) • Solution Architecture • IT Architect Certification Program from Open Group • Certified IT Architect – Professional from IASA

  25. Technical Career Path CIO, CTO Business Enterprise Architect Solutions Architect Application Architect Infrastructure Architect Technical Roles Developers, Programmers, IT Administrators, IT Support, etc Technical

  26. © 2011 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.

More Related