Enterprise Architecture - eaonapage.com

1 System 2 Application 2 Database 1 System 4 Application 3 Database 4 System 5 Step 1 Step 2 Process 1 Client 11. Brief Overview ..2. Goals and Objectives ..3. Detailed Requirements ..Server 1 App 1DB 14. Solution ContextServer 2 App 2DB 25. Data Architecture6. Application Architecture7. Infrastructure ArchitectureDB 1 Table 2 Table 1 Column 1: IntColumn 2: CharColumn 3: ByteColumn 1: CharColumn 2: ClobColumn 3: Blob1*CallReplyStoreReadFormApp 1 App 2DB 1 Linux Server 1VM 1VM 2 Linux Server 2 InternetSwitchFirewallHot StandbyCapability 1 Capability 3 ActiveLegacyStrategicSystem 1 Capability 2 System 1 Capability 1 System 2 System 3 System 1 System 2 System 1 Capability 1 System 1 Capability 1 System 2 Capability 2 System 1 Capability 1 System 1 Capability 1 Capability 4 System 1 Capability 1 System 1 Capability 1 System 2 System 2 System 2 System 3 System 2 ReuseDecommissionInvestAssetSystem 1 OwnersPurposeApplication 1 Database 2 CostSystem 3 Application 4 Database SponsoredEnterprise Service BusBUCRMC alls fromPartnersBackupQueueEJBApp 1 App 3 BinaryApp 2 UpdateDB 1 SOAApp 4 RESTApp 5 MessagingApp 7 (Plan)DB 2DB 3DB 4 (Plan)WarehouseETLR eportingRPCApp 6 (Plan)1.

2 Initiative Summary ..2. Goals and Objectives ..3. Anticipated Benefits ..6. Preliminary Estimations Time: 6-12 months Cost: $ millionClientsNew ERPM oduleProcess 15. Solution Sketch4. Scope and Stakeholders ..OptionScoreTime: 8-13 monthsCost: $ millionAdvantages: ..Disadvantages: ..Risks: ..Time: 4-7 monthsCost: $ millionAdvantages: ..Disadvantages: ..Risks: ..Time: 3-5 monthsCost: $ millionAdvantages: ..Disadvantages: ..Risks: ..Solution 1:Solution 2:Solution 3:Functionality: 3 Feasibility: 3 Alignment: 1 Total Score: 7 Functionality: 2 Feasibility: 5 Alignment: 2 Total Score: 9 ProcessUsersOld SystemNew SystemProcessUsersOld SystemExtra SystemProcessUsersEnhanced SystemFunctionality: 5 Feasibility: 2 Alignment: 4 Total Score: 11 CustomerNameDate of BirthLocationPhoneOrderDateQuantityDisco untProductTitleTypePrice1. Current Business Strategy2. Identified IT Capability Gaps3.

3 Recommended Strategic Direction for IT4. Anticipated OutcomesData WarehouseAnalytics Reporting SystemExecutivesRegional ManagersAnalystsAll Transactional IT Systems ..Inability to provide a timely and comprehensive trends analysis to relevant business stakeholdersIntroduce a data warehouse aggregating relevant data from all IT systems to enable the analytical capabilityPrinciple 1: Standardized Business ProcessesStatement: ..Rationale: ..Implications: ..Principle 2: Single Customer ViewStatement: ..Rationale: ..Implications: ..Principle 3: Business ContinuityStatement: ..Rationale: ..Implications: ..ApplicationsDataIntegrationInfrastruct ureSecurityMySQL(Master)1. Description: Simple Failover Cluster ..2. Applicability ..3. Rationale ..ApplicationJBossRed Hat LinuxNginx Load BalancedApplicationJBossRed Hat LinuxInbound RequestsReplicationMySQL(Slave)CurrentUn supportedEmergingInfrastructure and NetworksDatabases and Information ManagementSecurity and Access ManagementDeliveryApplications and IntegrationChannelsTechnology 1 Technology 2 Technology 1 Technology 2 Technology 1 Technology 2 Technology 3 Technology 4 Technology 1 Technology 2 Technology 3 Technology 4 Technology 1 Technology 2 Technology 3 Technology 4 Technology 1 Technology 2 Technology 3 Technology 4 Goal 1 Goal 3 Goal 2 Capability 1 Capability 2 Capability 3 Capability 4 Business StrategyCapability SystemCRM SystemCustomersRetail Outlet at Location 4 CustomersHead Officeat Location 3 Factory at Location 1 Warehouse at Location 2 Retail Outlet at Location 5 GoodsGoodsOrdersOrdersGoods DeliveryTransportationAll OrdersLogistic InformationFinancial DataOrders ForecastClient DataFundedApprovedPlannedBusiness

4 Drivers:Strategic Links:Link to Strategy 1 Link to Strategy 2 Link to Strategy 3 Driver 1 Driver 2 Driver 3 Key Decisions:Decision 1 Decision 2 Decision 3 Architecture Changes:Business Outcomes:Outcome 1 Outcome 2 Outcome 3 Change 1 Change 2 Change 3 Customer Outcomes:Outcome 1 Outcome 2 Outcome 3 Customer Group 2 Local System 1 Customer Group 1 Local System 2 Channel 1 Channel 2 Simple ReportingGlobal SystemCustomer Group 2 Customer Group 1 Channel 1 Channel 2 Real-TimePredictiveAnalyticsCurrent Architecture :3-Year Target Architecture :Non-StrategicStrategicCore ActivitiesHuman Resource ManagementFinancial and Administrative ManagementInformation Technology ServicesProcurement and Supplier ManagementInbound LogisticsOperationsOutbound LogisticsMarketing and SalesServiceActivity 1 Activity 2 Activity 1 Activity 2 Activity 3 Activity 1 Activity 2 Activity 1 Activity 2 Activity 3 Activity 1 Enterprise ArchitectureRulesStructuresChangesBusine ss-FocusedIT-FocusedGenericWhat Artifacts Describe?

5 SpecificBusinessITHow Artifacts Describe?Analytical ReportsPoliciesPrinciplesContext DiagramsValue ChainsBusiness Capability ModelsTarget StatesRoadmapsInitiative ProposalsOptions AssessmentsSolution OverviewsPreliminary Solution DesignsSolution DesignsIT RoadmapsLandscape DiagramsEnterprise System PortfoliosInventoriesPatternsTechnology Reference ModelsGuidelinesLogical Data ModelsIT PrinciplesDirection StatementsConceptual Data ModelsContent: Global technical rules, standards, patterns and best practices relevant for IT systemsFormat: Can be expressed in various formats, often using strict notationsRepresent: Proven reusable means for IT systems implementationFocus: Do not focus on specific points in time or focus on the current stateUsage: Developed collaboratively by architects and technical subject-matter experts and used to shape architectures of all IT initiativesLifecycle.

6 Developed on an as-necessary basis and updated according to the ongoing technology progressPurpose: Help achieve technical consistency, technological homogeneity and regulatory complianceBenefits: Faster initiative delivery, reduced costs, risks and complexityContent: High-level technical descriptions of the organizational IT landscapeFormat: Expressed in strict formats, often as complex one-page diagrams using formal modeling notationsRepresent: Knowledge base of reference materials on the IT landscapeFocus: Often focus on the current stateUsage: Developed and maintained by architects and used to rationalize the IT landscape, manage the lifecycle of IT assets and plan new IT initiativesLifecycle: Developed on an as-necessary basis and updated according to the ongoing evolution of the IT landscapePurpose: Help understand, analyze and modify the structure of the IT landscapeBenefits: Increased reuse and agility, reduced duplication and legacyContent: Detailed technical and functional descriptions of specific IT projects actionable for project teamsFormat: Expressed as a mix of text, tables and complex diagrams, can be voluminous and often use formal modeling notationsRepresent: Communication interfaces between architects and project teamsFocus: Usually focus on the short-term future up to 1 year aheadUsage: Developed collaboratively by architects, project teams and business representatives and then used by project teams to implement IT projectsLifecycle: Developed at the later stages of IT initiatives to support implementation and then archivedPurpose: Help implement approved IT projects according to business and architectural requirementsBenefits.

7 Improved quality of the project deliveryIT Principle 1: Prefer Open Source SolutionsDescription: ..IT Principle 2: Log All Main OperationsDescription: ..IT Principle 3: Use Scalable StorageDescription: ..IT Principle 4: Backup All Permanent DataDescription: ..IT Principle 5: Use Middleware for IntegrationDescription: ..IT Principle 6: Avoid Binary Integration ProtocolsDescription: ..IT Principle 7: Host in the CloudDescription: ..IT Principle 8: Dedicated Server for Each SystemDescription: ..IT Principle 9: Place Public Systems in DMZD escription: ..IT Principle 10: Secure by DefaultDescription: ..Bank CardTypeNumberExpiry DateCustomerid: Integername: Stringdate_of_birth: Datelocation: Stringphone: StringOrderid: Integercustomer_id: Integerproduct_id: Integerdate: Datequantity: Integerdiscount: FloatProductBank_Cardid: Integertitle: Stringtype: Stringprice: Floatid: Integercustomer_id: Integertype: Stringnumber: Stringexpiry_date: Date*1*11*AdoptTrialAssessHoldTechnology 1 Technology 2 Technology 4 Technology 3 Technology 5 Technology 7 Technology 10 Technology 9 Technology 13 Technology 12 Technology 11 Technology 6 Technology 8No ChangeMovedNewContent: Global conceptual rules and fundamental considerations important for business and relevant for ITFormat: Expressed in simple intuitive formats, often as brief written statementsRepresent: Overarching organizational context for information systems planningFocus.

8 Do not focus on specific points in time or focus on the long-term futureUsage: Developed collaboratively by senior business leaders and architects and then used to influence all architectural decisionsLifecycle: Developed once and then updated according to the ongoing changes in the business environmentPurpose: Help achieve the agreement on basic principles, values, directions and aimsBenefits: Improved overall consistency between business and ITContent: High-level conceptual descriptions of an organization from the business perspectiveFormat: Expressed in brief informal formats, often as simple one-page diagramsRepresent: Shared views of an organization and its future agreed by business and ITFocus: Often focus on the long-term future up to 3-5 years aheadUsage: Developed collaboratively by senior business leaders and architects and then used to guide IT investments, identify, prioritize and launch new IT initiativesLifecycle: Developed once and then updated according to the ongoing changes in strategic business prioritiesPurpose: Help achieve the alignment between IT investments and long-term business outcomesBenefits: Improved strategic effectiveness of IT investmentsContent: High-level descriptions of specific IT initiatives understandable to business leadersFormat: Expressed as a mix of textual descriptions and simple diagramsRepresent: Benefit, time and price tags for proposed IT initiativesFocus: Usually focus on the mid-term future up to 1-2 years aheadUsage: Developed collaboratively by architects and business leaders and then used to evaluate, approve and fund specific IT initiativesLifecycle.

9 Developed at the early stages of IT initiatives to support decision-making and then archivedPurpose: Help estimate the overall business impact and value of proposed IT initiativesBenefits: Improved efficiency and ROI of IT investmentsLanguage: Technology-neutral business languageDomains: Business domain and often other relevant domains at a high levelFormat: Brief, largely informal and include only the most essential informationStakeholders: Business leaders and architectsRole: Communication interfaces between business and ITPurpose: Help business leaders manage ITLanguage: Technical IT-specific languageDomains: Various technical domains and sometimes also business domainFormat: Can be voluminous, formal and include comprehensive detailsStakeholders: Architects and other IT specialistsRole: Internal IT tools invisible to businessPurpose: Help architects organize ITDescribe: Broad global rules defining an organization or its divisionsScope: Very wide, often cover an entire organizationFormat: Often textualQuestion: How do we work or want to work?

10 Lifecycle: Permanent, created once and then periodically updatedRole: Basis for all other planning decisionsPurpose: Help achieve consistency and homogeneity of all planning decisionsDescribe: High-level structures of an organization or its partsScope: Wide, often cover large parts of an organizationFormat: Usually graphicalQuestion: What approximately do we have or want to have?Lifecycle: Permanent, created once and then continuously updatedRole: High-level maps facilitating decision-makingPurpose: Help understand what changes are desirable and how to implement themDescribe: Specific proposed incremental changes to an organizationScope: Narrow, limited to separate IT initiatives or projectsFormat: Mix of textual and graphicalQuestion: What exactly are we going to change right now?Lifecycle: Temporary, created for specific purposes and then discardedRole: Tactical plans of an organizationPurpose: Help plan separate changes in detailConceptual messages communicating major organization-wide decisions with far-reaching consequencesHigh-level graphical descriptions of the current operational flows of an organizationStructured graphical representations of the added value chain of an organizationStructured graphical representations of all organizational business capabilities, their relationship and hierarchyGlobal high-level guidelines influencing all decision-making and planning in an organizationOverarching organizational norms typically of a restri