3 Agenda Why architect The process of architecture Identifying the right people - toolsetsAligning and Delivering Architecture - Frameworks and modelsOrganizational Insight - Understanding your organizationDo’s and Dont’s
4 Definition - Architect Architecture is a business in which technical knowledge, management, and an understanding of business are as important as design.the developer of the structure of a computer system or programThe enterprise architect handles business-related software decisions that frequently can involve multiple software systems within an organization, spanning several projects teams, and often at more than one site.The architect makes high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms, so as to advance business goals rather than to place arbitrary restrictions on the choices of developers.
5 Why do I need an Architect The Winchester House -
6 No architectural Blueprint Exists Winchester House Facts38 Years of Construction147 Builders0 Architects160 Rooms40 Bedrooms6 Kitchens2 Basements950 DoorsCost $5,5millionWinchester House Facts65 Doors to blank walls13 Abandoned Staircases24 Skylights in the floorNo architectural Blueprint Exists
7 Interpretation of the Objective Tuscany - BusinessTuscany - IT
8 Evolution of Enterprise Architecture EA = TAReduce IT cost and enhance operationsEA = EWITA Enhance Value ManagementEA = BA + EWITAEnhance Business/IT AlignmentValueScope
9 Challenges Business CIO Operations CFO I know what my business does... How long is it going to take?Why do you want to change it, we have been doing things like this for years and it worksShow me how this will effect the bottom line...Isn’t that an IT role...Let me decide on what is the right direction...What you are proposing is impossible...How did you get to that number?Surely the process is optimised...How must I know, I was in finance before this job....You want to get rid of Unix?Let me worry about the budgets...We cannot do this improve this any further...You want to pay him what???!!!!The mainframe will always be here...
11 Architecting Process Design Requirements Design Analysis Conscious effort to create something that is both functional and aesthetically pleasingAll architecture is design.Not all design is architecture.
12 Design all things by considering them in their larger contexts Architectural LevelsDesign all things by considering them in their larger contexts1Financial Services2Retail BankingIndustryEnterprise in an industrySystem in an EnterpriseComponent in a systemObject in a component13Procurement42Identity Management35User45Put the large rocks in the place first
14 Objectives of an Architect Creating the right ArchitectureVision and strategyRequired architecture and prioritiesSpecifications and standardsUsing the architectureGovernance and alignmentScorecards and measurementArchitecture Adoption through deploymentGovernance and feedbackValue calculation and ratification
15 The role of an architect BusinessITOrganization MissionProviding Banking Services to unbanked South AfricaProvide people, process and technology solutions to enable banking the unbanked in South AfricaProviding banking services to 40% of all unbanked South Africans over the next 10 years by providing affordable banking in the medium most suited.Architect, Plan, Design and Build the systems to cater for 12 million users within the next 10 years with system availability of 90%Organization VisionProvide access to the unbanked South African market through delivery of low cost banking services through retail bank branches, ATM and cellular phone channels.Systems for branch and cellular phone banking will be delivered in the Plan, Build Run Model and will ensure 90% availability through appropriate HA and DR policiesOperating Model
16 Mapping IT To Business Business IT IT How? 1.Improve customer satisfaction by 15% in next 12 months by reducing customer wait time in branches.Ensure branch systems service level SLA at 90% over the next 12 monthsRemove single points of application failure.Remove single points of hardware failure.Address network SLA and guarantee 95% availability2.Grow cell phone banking from to users in 18 months.Ensure cell phone banking functionality is availableIs application multi platform?Ease of use of application?Reliability of the application?3.Improve the turnaround time for customer loan applications from 12 hours to 1 hour.Straight through electronic processing of application will reduce processing timeWorkflow scanned documents with electronic application.Understand approval process and messaging requirements4Reduce Operational CostReduce infrastructure, operational and licensing cost.VirtualizeConsolidateOptimise
18 Roles and Responsibilities of Architect The RACI model is a powerful tool utilized to define roles and responsibilities. In general, you match up roles and responsibilities with processes. The tool is extremely useful when rolling out a new change management program, or just uncovering the processes that make your organization function and identifying the participation in those processesR Responsible – owns the project/problem.A To whom “R” is Accountable who must sign off (approve) on the work before it is effective.C To be Consulted – has information and/or capability necessary to complete the work.I To be Informed – must be notified of the results but need not be consulted.T - TimeActivityResponsibleAccountableConsultedInformedBy whenFinalize strategic middleware providersHOD – Technology ArchitectureCTOOperationsSupportDevelopmentSecurityCIOCOOPartner Manager1 June 2010
19 Delivering Architecture - Frameworks and models
20 FrameworksThe Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture.The architecture is typically modelled at four levels or domains; Business, Application, Data, Technology. A set of foundation architectures are provided to enable the architecture team to envision the current and future state of the architectureThe Zachman Framework is a framework for enterprise architecture, which provides a formal and highly structured way of viewing and defining an enterprise
23 Responsibilities of the Architect PerceptionTechnicalSolving interesting technical problemsUsing different design pattersChoosing technologyNon Technical Related WorkRealityNon Technical Related WorkSurviving the politics and hidden agendasEnsuring buy in and participationFoster support and agreementTechnical
24 Who Does What Best? Requirements Design Analysis Business Analyst Developer IT Professional .ArchitectRequirementsAnalysisDesign
25 Skills and Attributes - Roles ArchitectRoadmap and PlanningDesignDeployMaintainHighMedLowCLPCLPCLPCLPCLP
26 Individual Competencies BusinessOrganizational politicsStrategyProcess and tactical approachTimingPersonalLeadershipCommunicationPerseveranceEthicsEQIQTechnicalTechnology StrategyTechnology MBA – MCA InfrastructureTechnology Detail/MCA
27 Identifying Architectural candidates Myers-Briggs (MBTI Indicator)The Myers-Briggs Type Indicator (MBTI) assessment is a psychometric questionnaire designed to measure psychological preferences in how people perceive the world and make decisions.Fundamental to the Myers-Briggs Type Indicator is the theory of psychological type as originally developed by C. G. Jung. Jung proposed the existence of two dichotomous pairs of cognitive functions:The "rational" (judging) functions: thinking and feelingThe "irrational" (perceiving) functions: sensing and intuitionThe 4 DichotomiesExtraversionIntroversionSensingiNtuitionThinkingFeelingJudgingPerceiving
28 Architect Profiles Why is it so difficult to find? What should I be looking for?
29 Organizational Insight - Understanding the one you are in
30 Organizational Structure – friend or foe IT as a cost centreIT as a necessary evilStrategic PartnerCEOCFOCOOCIOCTOArchitectureIT OperationsDevelopmentCEOCFOCOOCIOCTOArchitectureIT OperationsDevelopmentEnable BusinessReduce CostSLA UptimeCEOCFOCIOCTOArchitectureIT OperationsDevelopmentCOO
32 Do’s and Don’ts Communication is paramount. Executive and Business buy in for architecture is a necessity.Governance structure is important – Prescriptive vs. ParticipativeKeep it relevant and delivery focussed.Get involved up front.Measure, Measure and Measure.Something does not exist until it is documented....Effective lobbying saves a lot of timeUnderstand your audience.Hire the right people for the right jobs.Be tough, bit not ignorant.Become the trusted advisor of the CEO and CIO.Don’t forget the legacy
33 In conclusion What is Architecture Why we architect The process of architecture and how we align business objectivesIdentifying the right peopleLooking at architectural toolsetsUnderstood organizational structureCovered some high level do’s and don’ts
35 10 pairs of MP3 sunglasses to be won Required Slide10 pairs of MP3 sunglasses to be wonComplete a session evaluation and enter to win!
36 Resources Required Slide Speakers, www.microsoft.com/teched TechEd 2009 is not producinga DVD. Please announce thatattendees can access sessionrecordings from Tech-Ed website. These will only be available after the event.ResourcesTech·Ed Africa 2009 sessions will be made available for download the week after the event from:International Content & CommunityMicrosoft Certification & Training ResourcesResources for IT ProfessionalsResources for Developers