14

Architects 101

Embed Size (px)

Citation preview

Page 1: Architects 101
Page 2: Architects 101
Page 3: Architects 101
Page 4: Architects 101

Who’s the Architect?

Page 5: Architects 101
Page 6: Architects 101
Page 7: Architects 101

Credential ProvisioningNetwork AccessDirectory ServicesAuthentication, Authorization and AccountingFederationSingle Sign-On (SSO)Data Access StrategyApplication LayeringArchitectural DescriptionArchitecture StylesArchitecture Viewpoint and ViewsAsset Management SystemsBusiness Strategy IdentificationGap AnalysisIdentifying De Facto Technology and Business

DirectionTechnology Strategy Evolution Approach DefinitionBusiness-Technology Strategy RationalizationIndustry Vertical Capability PerspectiveStrategy Canvas MethodsBusiness Capability MappingBusiness ConsiderationsBusiness Community Organizational AspectsBusiness FundamentalsBusiness IntelligenceBPE & BPMOpportunity Cost and ValueReturn on Investment CalculationTotal Cost of OwnershipViability AssessmentBusiness ValuationBusiness-Technology StrategyCapability Development, Training and ManagementCapability Mix IdentificationScaling SolutionsCapacity PlanningChange ControlSource Control SystemsDatabase ManagementIntranet and Internet ServicesCommon Application ServicesCompliance: Audits, Certification and RegulationConflict Management

Schedule/Effort EstimationCrisis ManagementCustomer Information and Relationship Management (CIM/CRM)Customer RelationsDependency Identification and ManagementDesign DiagramDesign Methodologies including reviewDesign SkillsDevelopment and Build EnvironmentsClient ManagementDevice ManagementServer ManagementStorage ManagementDomain-Specific LanguagesEnd-to-End (E2E) Test Design and ImplementationSoftware Development Life Cycle (SDLC)EngineeringGovernance FrameworksGovernance MethodologiesGovernance PoliciesTool IdentificationHuman DynamicsBalancing and Optimizing Design AttributesQuality Attributes for Post DeploymentBalancing and Optimizing Quality AttributesQuality Attribute Impact Across DomainsQuality Attributes for Delivery and PackagingImplementing Quality AttributesImplementing the User ExperienceUser Interface OptionsVisualizationWeb PortalsStandardsMajor Vendors and System IntegratorsTechnology Industry TrendingTool and Solution CategorizationCompetitive LandscapeIndustry Vertical AwarenessTechnologiesData ModelingData TransformationData WarehousingProduct Architecture ManagementContext in DesignCost Estimation and Tracking

Information Architecture StrategyMetadata ManagementRelational Database Management Systems (RDBMS)Information ArchitectureInfrastructure ArchitectureIntegrated Development Environments (IDEs) and Modeling ToolsIT EnvironmentKnowledge ManagementCoaching and InspiringLeadership StrategyThought LeadershipLeadershipInternationalization issuesLocalizationMainframe Development and DesignMaintenance and SupportIncident ResponseService Level Agreements (SLA)Manageability, Maintainability and SupportabilityMentorshipMessaging (protocols ,standards, technologiesTransportsMobile Platforms and FrameworksMonitoring Quality AttributesPersuasionNegotiation SkillsNetwork DesignNetwork Devices and AppliancesNetwork ProtocolsRouting, Load Balancing and Traffic PrioritizationNetwork Management ToolsAlerting, Operations Support and DashboardsSystem Management and Services Related ToolsService Change ManagementOperational ManagementOperations MethodologiesRequirements and Constraints AnalysisRequirements Analysis as a Design SkillResource Balancing and ManagementFrameworks, Components, Reference Implementations, Products, and SystemsHPC ComputingStakeholder DefinitionSystem’s theory

Release and Capacity ManagementOperations FrameworksInfrastructure Concerns in Solutions ArchitectureOptimization TechniquesOrganizational DynamicsAnti-Patterns Design PatternsEffective QuestioningListening SkillsMeeting SkillsPerformance, Extensibility, FlexibilityPersonalizationUser Profile and Relationship DesignRelationship/Power MapInterpersonal DynamicsPoliticsTeam ParticipationVisual and Diagrammatic CommunicationsPresentation , verbal and writing skillsprogrammingProgramming Language ConsiderationsProof of Concept DesignPrototypingAuditingQuality AttributesReliability, Availability, ScalabilityAnalysis and Opportunity IdentificationAutomation and ToolingCurrent Business EvaluationProcess Identification and CatalogingRefactoringBuilding Blocks of DesignSecurity AttributesSelling SkillsApplication and Service ManagementAutomated Policy ApplicationComponent ArchitectureEnterprise Service Bus (ESB)Event Driven ArchitectureService OrientationService NetworkUnderstanding PerspectiveAdaptationSolution ArchitectureSolution Architecture MethodologiesDistributed Computing

Page 8: Architects 101

ExplorerDesigner

Advocate

The role of the architect

From Ron Jacobs

Yeah – but a better analogy is

Page 9: Architects 101

The Role of the Architect – take II

Designer

Renaissance Man

Visionary & Leader

Mentor

Page 10: Architects 101

Software architecture is…

what the software architect does

Page 11: Architects 101

• collection of the fundamental decisions about a software collection of the fundamental decisions about a software product/solution designed to meet the project‘s quality attributesproduct/solution designed to meet the project‘s quality attributes

• Includes the main components, their main attributes, and their Includes the main components, their main attributes, and their collaborationcollaboration

• expressed in several levels of abstraction (depending on the expressed in several levels of abstraction (depending on the project's size).project's size).

• Architecture is communicated from multiple viewpointsArchitecture is communicated from multiple viewpoints

• Tradeoffs are made explicitTradeoffs are made explicit

Page 12: Architects 101
Page 13: Architects 101

Architecture

Quality Attributes

Technology

Patterns & Anti-patterns

Principles

Community experience

Stakeholders

Architect

Constraints

Page 14: Architects 101

The Tao of Software Architect

The architect doesn't talk, he acts.When this is done,the team says, "Amazing:we did it, all by ourselves!" (17)

The architect observes the worldbut trusts his inner vision.He allows things to come and go.His heart is open as the sky. (12)

By Philippe Kruchten - http://www.bredemeyer.com/tao_by_Kruchten.htm