How to develop a Solution Architecture Enterprise Architecture Program 5
How to develop a Solution Architecture Enterprise Architecture Program 5 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. The Business Architecture Framework™ aligns strategic objectives with operational activities Business Strategy Business Models Business Processes Organization Management IT Q2 Application Q3 Q1 Information Service Q4 2 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Logical Solution Architecture Organizatio n Business Context Business Strategy Business Models Business Processes Managemen t IS Architecture Implementati on Transformation Support Define Business Context Analyze strategic impact Analyze business models and overall processes Scope the EA initiative Describe the Business Develop Business Domain Architecture Scope EA initiative based on architecture Model Process Architecture Model Process Capabilities Model Model Functional Determine Logical Estimate initiative Information Architecture Model AS-IS Capabilities areas Mapping Develop Solution Model driven requirements 3 Scan market for Technical solutions Solution Architecture Business Domain Plan Technical Physical Solution Architecture Identify change Develop Logical Solution Architecture © 2013 Ericsson Enterprise Architecture Program. All rights reserved Transitions Plan Transformation Develop Solution Architecture Develop the Service Architecture Perform Market scan Develop the Solution Architecture Create the Transformation plan Ta bort steget Develop the Service Architecture. Stegen bör alignas till slide nr 3. Byt namn på Vision Architecture till Business Domain Architecture genomgående i alla pass. Byt ut tumnageln i alla följande ”metodpilslides” mot den som är på denna slide i högra Internal and external hörnet Analysis and design of Develop L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L3 Hantera Kundorder L4 Hantera Kundfaktura L4 Hantera Kassa is the foundation for the Service Architecture 5 L4 Hantera Vara/Tjänst Leverantör L4 Hantera Sortimentsplan Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Apoteksvaruinleverans L4 Hantera Apoteksvarubeställning L4 Hantera Apoteksvaruutleverans Försäljning L4 L3 Vara/tjänst L4 L3 L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Hantera Kundavtal Kundärende L4 The Process architecture Kundavtal L4 L4 Hantera Tjänsteleveranstillfälle L4 Hantera Betalning L3 Kampanj L4 Hantera Kampanj L3 Bemanning L4 Hantera Bemanning market scan for applications and partners based on logical functional blocks applications, IT services and platforms based on the Vision Architecture, Target Application Architecture, analysis of non-functional and technical requirements, IT strategy and architecture principles © 2013 Ericsson Enterprise Architecture Program. All rights reserved. a plan where the Solution Architecture is implemented in phases Develop Solution Architecture – Perform Market Scan Develop the Service Architecture Perform Market scan Develop the Solution Architecture Develop Business Architectu re Scoping Business Modeling Develop Vision Architectu re Develop Solution Create the Transformation plan L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L3 Hantera Kundorder L4 Hantera Kundfaktura L4 Hantera Kassa is the foundation for the Service Architecture 6 L4 Hantera Vara/Tjänst Leverantör L4 Hantera Sortimentsplan Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Apoteksvaruinleverans L4 Hantera Apoteksvarubeställning L4 Hantera Apoteksvaruutleverans Försäljning L4 L3 Vara/tjänst L4 L3 L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Hantera Kundavtal Kundärende L4 The Process architecture Kundavtal L4 L4 Hantera Tjänsteleveranstillfälle L4 Hantera Betalning L3 Kampanj L4 Hantera Kampanj L3 Bemanning L4 Hantera Bemanning Internal and external market scan for applications and partners based on logical functional blocks Analysis and design of applications, IT services and platforms based on the Vision Architecture, Target Application Architecture, analysis of non-functional and technical requirements, IT strategy and architecture principles © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop a plan where the Solution Architecture is implemented in phases Develop Solution Architectu re Market Scan should increase our knowledge about possible solutions Main purpose of the market scan is to collect details about components that can be part of the future solution architecture In this phase of the EA process, focus is shifting into work with a lot of details – Collect information on all affected internal systems – Collect information on possible products out on the market Requirement work on a more technical level is introduced Knowledge from the software vendors will help us learn more about how the vision and solution architectures should be designed 7 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Perform Market scan Develop Business Architectu re Scoping Business Modeling Develop Solution Perform Market scan Model type Deliverables Description Define Solution Architecture Scope 8 Scan for Solutions Request for Solution Proposal Create Solution Proposal Prepare Evaluation Evaluate Solution Proposals • Analyze the AS-IS Solution Arch and identify possible scenarios • Select a scenario and scope based on AS-IS applications involved • Scan for Solutions, both internally and externally • Request for information and narrow down the list to a few ones • Create the Requirement Specification • Create the Request for Proposal • Analyze requirements • Respond to the RFP • Detail and communicate the evaluation plan • Prepare The Evaluation template • Develop the Software Competition Case • Perform vendor demos • Document score and findings from RFP, Demo and Software Competition • Write a recommendation • Solution architecture scenarios • Solution Scope Model • Mandatory and Optional Business Services • Solution Long List • Request for Information • Solution Short List • System Overview • Requirement Specification • RFP Response • Description of the Solution Draft • Evaluation Plan • Evaluation Template • Software Competition Case • Solution Demonstration • Evaluation Score • Software Competition Result • Recommendation MANDATORY • • • • • Functional Non-functional Technical Architecture Partner • Request for Proposal OPTIONAL © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Vision Architectu re Develop Solution Architectu re Scope the Market scan based on Service architecture and Target application architecture Service architecture Verify process scope from the vision architecture phase Rental Management Verify the stakeholders intentions regarding external market scan Byt namn på Target Application Define scope for the Market scan Architecture till Business Domain Architecture genomgående i alla pass? based on Service- and Target Target application architecture application architecture Decide on Market scan method – RFI and RFP? – Scope for long and short list Collect existing solution architecture documentation L1 Sales and Services L2 Vehicle Check-out 9 Vehicle Use Support Vehicle Check-in © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Perform Market scan Develop Business Architectu re Scoping Business Modeling Develop Solution Perform Market scan Model type Deliverables Description Define Solution Architecture Scope 10 Scan for Solutions Request for Solution Proposal Create Solution Proposal Prepare Evaluation Evaluate Solution Proposals • Analyze the AS-IS Solution Arch and identify possible scenarios • Select a scenario and scope based on AS-IS applications involved • Scan for Solutions, both internally and externally • Request for information and narrow down the list to a few ones • Create the Requirement Specification • Create the Request for Proposal • Analyze requirements • Respond to the RFP • Detail and communicate the evaluation plan • Prepare The Evaluation template • Develop the Software Competition Case • Perform vendor demos • Document score and findings from RFP, Demo and Software Competition • Write a recommendation • Solution architecture scenarios • Solution Scope Model • Mandatory and Optional Business Services • Solution Long List • Request for Information • Solution Short List • System Overview • Requirement Specification • RFP Response • Description of the Solution Draft • Evaluation Plan • Evaluation Template • Software Competition Case • Solution Demonstration • Evaluation Score • Software Competition Result • Recommendation MANDATORY • • • • • Functional Non-functional Technical Architecture Partner • Request for Proposal OPTIONAL © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Vision Architectu re Develop Solution Architectu re Market Scan – What parts can we build the solution on? Existing internal solutions Mainfra m e a pps- Blue PC/NT a pps- Gre e n Unix a pps- Ye llow 3 rd pa Crty inte rfapec ciaeOra nge olor s havenos l mean ing. Line They ar s et : oh elpmakethed iagr a me asier to AI S Repor t s AI S Cal enda r Due Dat es G ener al M ai nt enan ce Br oadcast Fi l t er St or es & Mrkts DRAFT Best Buy - Application Diagr am V4 DRAFT Novem ber 10, 1999 Vendor Set up Vendor M ai nt enan ce Budget Anal ysi sTool r ead. For M or eInf o r mati o n: See t hed ataba se cont aining inform a t iona bou t ea ch applicat ion: Applicat ion V4.mdb Pr ocess Serve rs ( I magi ng ) Pr i nt er M ai nt enan ce I nser t i on s O r der s NEW Soundscan NPD G r oup AI G Warr a nt yGu ar d M esa Dat a S20- Sal es Pol l i ng Pr i nt er PO I 17 Cust omerPerceive d I n- St ock I 13- Aut o Repl eni shment I 06 - Cus t ome r O r der S01 - Sales Cor r ect i ons Pa ge 1 of2 Deposi t or y Banks UAR - Uni versa l Acc ount Reconci l l iation St er l i ngVAN M ai l box( V alue) Roadshow I 15 Hand S can Apps I 06 Warehous e M anagem en t Pr i nt Costi n g I nvoi ce Ap E13 E3 I nt er fac e Fr i nge PO Smar t Plus M 03 - Mil e nnuim 3 .0 Sm ar t Plus Launcher S04 - SalesPo st ing S07 - Cell Phones P16 - TallyShee t I 03 Ret urn to Vendor D01 Post Lo ad Bi l l i ng M 02 - Mil e nnium S06 - Cr e di tApp Equi f ax St ock O ptions A04 - Cust Ref und Chks E01- EDI P14 O n- lineNew Hi r e Ent ry Resum i x Fr i ck Co CTS ACH V02- Pr i ce M ar ket ing Suppor t CTO 2. Best b uy. com V04- Si gn Syst em Pr odi gy Banks - ACHandPosto Pay I 04 Home Del i ver ies U18 - CTO I 02 Tr ansf er s B01 - St oc k St at us Spec Sour ce SKU Tr acki ng I nt er cept E02- Empl oy ee Pur chase S08 - Vert e x Sal es Tax I 11 Pr i c e Test i ng I 09 Cycl eCo unt s S02 Layaw ays NPD, SoundScan Spec Sour ce Scor ecar d- HR S03- Pol l ing K02 Cust om er Repair Tr acki ng ASI S I 18 SKU Rep Rebat e Tr ansf er Texl on 3.5 U16- Texl on SKU Sel ect ion Tool Ar t hur Pl a nning I 35 Ear lyWa r ning Syst em I 55 SKU I nf or m ati o n I 07 Pur cha se O r der Ad Expense G 02 - General Ledger St or e Scor ecar d Si gn Syst em NARM I 14 Count Cor rec t ions St or e Budget Repor t i ng Val l ey Med ia B02 M er ch andise Anal ysi s CopyWr i t er's Wor kspace BM P - Bus per f or m an ceMngt EDI Coor di nat or M er ch Mngr App r ov al Bat ch For ca st ing AI M S Ad M easur e ment AI M S Adm in Jour nal Entr yT ool Kit A05 - AP Cel l ul ar Rol l over AI M S Repor t i ng Ad Launcher S05 - House Char ges O pt i ka PSP C02 - Capit a l Pr oj ect s Dat a War e hous e ( I nt er f a cestoandf romt he Dat a War e hous ear en ot di spl ayedont h i sdiag r am) O THER APPS- PC AP - Col lecti o ns/Cr e di t TM - Cr e dit Card DB US Bank Recon Fi l e Connect 3 I CM S Cr edit Si t eSeer I n- Hom e Repai r War r ant y Bi l l i ng Syst em F06 - Fixed Asset s St ar Repair Future solutions SKU Per f or m an ce L60 M DF Coop I 05 I nvent or yInf o V01- Pr i ceMana gemen t Syst em I 35 - CEI ELT Pow er Sui te X92- X96 Host t o AS4 00 Com m uni ca t ion Suppl i er Compl i ance I 01 PO Recei vi ng V03- M kt React i ons P09 Bonus/ HR Washi ngt on, RG I S, Nt l Bus Sy st e ms S11 - I S P Tr acki ng I 10 Cycl eP hysica l I nvent or y PO S Pl an Adm inist rator s ( 401K, PCS,Li fe, Uni car e, Solomon Sm i t h Barney ) St or e M oni t or L01- Pr om o Anal ysi s 1 AAS P01Em pl oyee M ast er f ile P09 - 1 P7 Cybor g Cobr a S09 - Di g i tal Sat el l i te Syst em I 12 Ent ert a i nme nt Sof t w ar e P15 EES Employee Change Not i c e L02- Resour ce Schedul i ng ( Cam pbel l) Connect 3 PDF Tr ansf e Connect 3 Repor t s Cash O ver/ Shor t Cash Recei pts/Cr e dit M i sc Acc ounti ng / Fina nceApps-PC/ NT CO BA ( Cor p of f iceBud get Asist a nt ) PCBS( Pr of i t Cen t erBudgetSystem) M er chandisingBudget I NVENTO RY CONTROLAPPS- C P Code Al ar m Debi t Receivings Devo Sal es Di spl ay Inve nt o ry I n Home Junkout s M er chandiseWi thdrawl Pr om o Cr ed i ts RTV Accr ual Shr i nk AP Resear ch- InvCntr l AP Resear ch-Addl Rp ts Book t o PerpetualI nv entor y Cl ose O utReport ing Comput er Intel ige nceData Count Cor r ec t ions Cr oss Ref f or V CB Dnlds Dam age Writ eOf Debi t Receivings DFI Vendor Databas e Di spl ay Inve nt o r yRec oncil Di spl ay Inve nt o r yRep or ti n g I NVENTO RY CONTROLAPPS- C P DPI / CPI I C Bat chi n g I nvent or yAdj/ Co unt Corr e ct I nvent or yContr olReport s I nvent or yLev els I nvent or yRoll M er chandiseWi thdrawl O pen Receivings PI Count Re sult s PI Ti meRe sult sfr omInv Pr i ce Pr o t ec t ion Sal es Fl a shRepo r ti ng Shr i nk Report ing SKU G r ossMargi n SKU Shr i nkLeve l Detail USM VCB Dow nl oad s ACCTS REC APPS- PC 990CO R Bad Debt Benef i cal Fe es Benef i ci alReco ncil JEAXF JEBFA JEBKA JEDVA JESO A JEVSA JEVSF NSF Tel eCr edi t F ees Pr epar ed byMiche l leMil ls Possible external solutions 11 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Perform Market scan Develop Business Architectu re Scoping Business Modeling Develop Solution Perform Market scan Model type Deliverables Description Define Solution Architecture Scope 13 Scan for Solutions Request for Solution Proposal Create Solution Proposal Prepare Evaluation Evaluate Solution Proposals • Analyze the AS-IS Solution Arch and identify possible scenarios • Select a scenario and scope based on AS-IS applications involved • Scan for Solutions, both internally and externally • Request for information and narrow down the list to a few ones • Create the Requirement Specification • Create the Request for Proposal • Analyze requirements • Respond to the RFP • Detail and communicate the evaluation plan • Prepare The Evaluation template • Develop the Software Competition Case • Perform vendor demos • Document score and findings from RFP, Demo and Software Competition • Write a recommendation • Solution architecture scenarios • Solution Scope Model • Mandatory and Optional Business Services • Solution Long List • Request for Information • Solution Short List • System Overview • Requirement Specification • RFP Response • Description of the Solution Draft • Evaluation Plan • Evaluation Template • Software Competition Case • Solution Demonstration • Evaluation Score • Software Competition Result • Recommendation MANDATORY • • • • • Functional Non-functional Technical Architecture Partner • Request for Proposal OPTIONAL © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Vision Architectu re Develop Solution Architectu re Partners and systems are evaluated several times during the project Requirements 14 Solution RFI L3 N/A Partner and system evaluation L3 or L4 N/A Joint Solution Design L5 Yes © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Perform Market scan Develop Business Architectu re Scoping Business Modeling Develop Solution Perform Market scan Model type Deliverables Description Define Solution Architecture Scope 20 Scan for Solutions Request for Solution Proposal Create Solution Proposal Prepare Evaluation Evaluate Solution Proposals • Analyze the AS-IS Solution Arch and identify possible scenarios • Select a scenario and scope based on AS-IS applications involved • Scan for Solutions, both internally and externally • Request for information and narrow down the list to a few ones • Create the Requirement Specification • Create the Request for Proposal • Analyze requirements • Respond to the RFP • Detail and communicate the evaluation plan • Prepare The Evaluation template • Develop the Software Competition Case • Perform vendor demos • Document score and findings from RFP, Demo and Software Competition • Write a recommendation • Solution architecture scenarios • Solution Scope Model • Mandatory and Optional Business Services • Solution Long List • Request for Information • Solution Short List • System Overview • Requirement Specification • RFP Response • Description of the Solution Draft • Evaluation Plan • Evaluation Template • Software Competition Case • Solution Demonstration • Evaluation Score • Software Competition Result • Recommendation MANDATORY • • • • • Functional Non-functional Technical Architecture Partner • Request for Proposal OPTIONAL © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Vision Architectu re Develop Solution Architectu re Define evaluation Criteria 1 Process match Varubeställning Vara/ tjänst Leverans Lager Leverantör Varubeställning Vara/ tjänst Leverans Lager 2 Information match 21 Leverantör Services and Capabilities match 3 Non-functional requirements match 4 IT Strategy and architecture principles match 5 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Perform Market scan Develop Business Architectu re Scoping Business Modeling Develop Solution Perform Market scan Model type Deliverables Description Define Solution Architecture Scope 22 Scan for Solutions Request for Solution Proposal Create Solution Proposal Prepare Evaluation Evaluate Solution Proposals • Analyze the AS-IS Solution Arch and identify possible scenarios • Select a scenario and scope based on AS-IS applications involved • Scan for Solutions, both internally and externally • Request for information and narrow down the list to a few ones • Create the Requirement Specification • Create the Request for Proposal • Analyze requirements • Respond to the RFP • Detail and communicate the evaluation plan • Prepare The Evaluation template • Develop the Software Competition Case • Perform vendor demos • Document score and findings from RFP, Demo and Software Competition • Write a recommendation • Solution architecture scenarios • Solution Scope Model • Mandatory and Optional Business Services • Solution Long List • Request for Information • Solution Short List • System Overview • Requirement Specification • RFP Response • Description of the Solution Draft • Evaluation Plan • Evaluation Template • Software Competition Case • Solution Demonstration • Evaluation Score • Software Competition Result • Recommendation MANDATORY • • • • • Functional Non-functional Technical Architecture Partner • Request for Proposal OPTIONAL © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Vision Architectu re Develop Solution Architectu re Evaluate Internal Solutions Deep interviews with IT system managers, system developers and business owners. Collect technical and business information about the internal systems in-scope. Extended workshops with selected system managers for key systems. IT-budget review to extract all the costs for system in scope. Model workshops to create models Presentation for IT and business. Deliverables in this phase: 23 System Cost Model System Life Cycle Model System Evaluation Result System Overview Model Detailed System Integration Model System Landscape © 2013 Ericsson Enterprise Architecture Program. All rights reserved. System Cost Model (example) CarWiz 24 789 000 CRB2000 9 142 000 750 000 CompWiz 1 720 000 250 000 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. System Life Cycle 25 Introducing Not implemented but is planned or under development. Growing Recently put into production and business use is still increasing. Change requests are common. Maturing Has been in production for a long time. Few change requests. Declining Difficult and time consuming to implement changes. In need of modernization. Phasing out Will be shut down within a year. © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Evaluate External Solutions Phase 1a Phase 1b Phase 2 Phase 3 ACME ABC data Scan of vendors ACME CRM systems ABC data Great systems Greater systems Foolproof systems Foolproof systems Greater systems Greatest systems Timeframe 27 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. ACME Foolproof systems Mapping of vendor solution to functional blocks (example) 29 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Develop the Solution Architecture Develop the Service Architecture Perform Market scan Develop the Solution Architecture Develop Business Architectu re Scoping Business Modeling Develop Vision Architectu re Develop Solution Create the Transformation plan L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L3 Hantera Kundorder L4 Hantera Kundfaktura L4 Hantera Kassa is the foundation for the Service Architecture 32 L4 Hantera Vara/Tjänst Leverantör L4 Hantera Sortimentsplan Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Apoteksvaruinleverans L4 Hantera Apoteksvarubeställning L4 Hantera Apoteksvaruutleverans Försäljning L4 L3 Vara/tjänst L4 L3 L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Hantera Kundavtal Kundärende L4 The Process architecture Kundavtal L4 L4 Hantera Tjänsteleveranstillfälle L4 Hantera Betalning L3 Kampanj L4 Hantera Kampanj L3 Bemanning L4 Hantera Bemanning Internal and external market scan for applications and partners based on logical functional blocks Analysis and design of applications, IT services and platforms based on the Vision Architecture, Target Application Architecture, analysis of non-functional and technical requirements, IT strategy and architecture principles © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop a plan where the Solution Architecture is implemented in phases Develop Solution Architectu re Objectives Define the concept of Solution Architecture Show how to connect the SA to the IT Strategy Share ideas on how to analyze requirements Jag gillar kommande bilder! Walk through the method Provide an “SA check list” 33 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Solution Architecure A Solution Architecture consists of a well defined set of applications and services that together constitute the base for development towards the vision architecture Analysis and definition of applications, services and platforms based on the vision architecture and the solution architecture requirements A plan for phased realisation of the solution architecture with an estimate of the investment and the effects, for instance – Phase 1: 2 years – Phase 2: 4 years – Phase 3: >5 years 34 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Do not forget! The solution architecture can improve business flexibility and promote business model innovation… …but mistakes in the solution architecture will slow innovation down… In the solution architecture we are bringing all the pieces together! 35 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Solution Architecture Vision Architecture Solution Architecture (SA) Vision Architecture (VA) beror påon den givna SALA depends the given situationen situation SA based on a specific situation LA is beror på förutsättningar t.ex. arv, in terms of geography, legacy, begränsningar i tid kostnad och andra restrictions in time, cost and resurser resources MA logisk och en ideal ideal VA är is a logical and design påaen stabil designbaserad based on stable struktur --information structure information VA is more stable over time – but may change by change of position in the value chain or by larger changes in the business model The Solution Architecture is the foundation for realization – the Vision Architecture is more stable over time 36 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. IT cost distribution problem With a well-formed Solution Architecture we can avoid this problem and make IT an enabler of business innovation over time Cost Cost for development of new requirements Running cost 37 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Solution Architecture Requirements Business Requirements Resources Solution Architecture Processes IT Strategy Information models Architecture principles Logical applications Non-functional requirements Capabilities Technical requirements Internal solutions Identified external solutions The requirements must have a set priority and timeline to make it possible to define the solution architecture and the transformation plan 38 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Critical success factors for solution architecture definition Clear vision and strategy for the solution architecture Team of skilled business architects, enterprise architects and solution architects Same individuals involved in the entire process A well-designed vision architecture Prioritized requirements Involvement from business representatives Efficient tool support for the architecture work 39 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. IT Strategy Requirements Run a workshop with the IT managers group (and possibly other stakeholders) Make sure to understand what the wanted impact of the IT strategy is Discuss priorities Example of workshop questions: – Time horizon for implementation of a new solution architecture? – To what cost can we implement the desired quality of architecture? – For central statements in the IT strategy, ask how it should affect the solution architecture Make sure to understand the stakeholders expectations! 40 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Architecture principles, example 42 Name Architecture is business driven Statement All architecture decisions are based on business priorities. Rationale All solutions considered will have a clear business purpose. Technology decisions will never be made based only on technology considerations. Implications It should be possible to trace architecture decisions back to business strategy, goals and requirements. All architecture initiatives will have traceability to the process map. This will be achieved by a model-driven approach (with ARIS) to architecture that documents business architecture and creates traceability to the solution architecture. © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Solution Architecture Strategy L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L4 L3 L3 L4 Hantera Kundfaktura L4 Hantera Sortimentsplan L4 Hantera Apoteksvaruleverans Bemanning L4 Hantera Bemanning Hantera Betalning L3 Kampanj L4 Hantera Kampanj L4 Hantera Kassa Funktionell omfattning i Plogen-projektets första iteration 50% components from one supplier ? All components from one supplier 0% “Suite” 0% 43 100% © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Leverantör L4 Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Tjänsteleveranstillfälle Hantera Kundorder L4 All components from different suppliers L3 Försäljning L4 100% Hantera Vara/Tjänst L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Vara/tjänst L4 Hantera Kundavtal Kundärende L4 “Best of Breed” L3 Kundavtal L4 Hantera Apoteksvarubeställning Develop Solution Architecture – Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture • Analyze the Target Application Architecture, Business Services, Capabilities and Business Objects • Describe the Solution Architecture on a high level • Describe principles for system integration • Identify integrations • For each subdomain, identify IT-functions needed to support the Process and Info Capabilities • List of Target Applications and IT Services • Solution Architecture Overview • Solution Integration Reference Model • High-level Integration Model • Sub-domain Solution Architecture (detailed) Byt namn på ”Strategic Solution Architecture” till ”Logical Solution Architecture”? Jämför med materialet om TA Architecture Process Model type Deliverables Description Develop the Solution Architecture 44 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Develop Solution Architecture – Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture • Analyze the Target Application Architecture, Business Services, Capabilities and Business Objects • Describe the Solution Architecture on a high level • Describe principles for system integration • Identify integrations • For each subdomain, identify IT-functions needed to support the Process and Info Capabilities • List of Target Applications and IT Services • Solution Architecture Overview • Solution Integration Reference Model • High-level Integration Model • Sub-domain Solution Architecture (detailed) Model type Deliverables Description Develop the Solution Architecture 45 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Develop the Solution Architecture – Analyze the Vision and Service Architectures Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture The model describes the identified logical applications and IT services per sub-domain 46 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Target Applications and IT Services Target applications and IT Services are identified from an analyzing the Target Application Architecture, Business Services, Capabilities and Business Objects 47 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture • Analyze the Target Application Architecture, Business Services, Capabilities and Business Objects • Describe the Solution Architecture on a high level • Describe principles for system integration • Identify integrations • For each subdomain, identify IT-functions needed to support the Process and Info Capabilities • List of Target Applications and IT Services • Solution Architecture Overview • Solution Integration Reference Model • High-level Integration Model • Sub-domain Solution Architecture (detailed) Model type Deliverables Description Develop the Solution Architecture 48 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Develop the Solution Architecture – Analyze IT strategy Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture The models describe the Solution Architecture on a high level and the principles for system integration 49 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Description of the Solution Architecture on a high level There are different views of various level detail in the solution architecture. 50 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Principles for system integration Basic principles that form the base for implementation patterns. 51 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture • Analyze the Target Application Architecture, Business Services, Capabilities and Business Objects • Describe the Solution Architecture on a high level • Describe principles for system integration • Identify integrations • For each subdomain, identify IT-functions needed to support the Process and Info Capabilities • List of Target Applications and IT Services • Solution Architecture Overview • Solution Integration Reference Model • High-level Integration Model • Sub-domain Solution Architecture (detailed) Model type Deliverables Description Develop the Solution Architecture 52 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Develop the Solution Architecture – Develop the Strategic Solution Architecture Develop Business Architectu re Develop Solution Develop the Solution Architecture Analyze the Vision and Service Architectures Analyze IT strategy Develop the Strategic Solution Architecture The models describe the highlevel Integration and the detailed Solution Architecture for a specific sub-domain 53 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Tools for analysis of solution architectures Matrix for Processes and Systems Matrix for Systems and Information 54 Matrix for Functional blocks and Information Matrix for System functionality and Information © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Integrations High-level overview of integrations between applications and IT services 55 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. IT-functions needed to support the Process and Info Capabilities The functional scope of each Application is defined by allocation of Process Capabilities. IT-services implement Functional blocks with Information Capabilities as blueprint. 56 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Analyze Solution Architecture alternatives Identify architectural significant process flows based on vision architecture and strategic business requirements Analyze systems and services in the solution architecture cooperates in these process flows Describe in more detail how systems handle process components, capabilities and information objects More detailed analysis of integration flows between systems Document strengths and weaknesses for the alternative solution architectures Re-visit consequences from business perspectives Make “guesstimates” for the costs of the alternatives Finalize the design of the solution architecture Describe the recommendation of the preferred alternative Get the decision to continue! 57 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution Architecture – Create the Transformation Plan Develop the Service Architecture Perform Market scan Develop the Solution Architecture Develop Business Architectu re Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Develop Solution Create the Transformation plan L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L3 Hantera Kundorder L4 Hantera Kundfaktura L4 Hantera Kassa is the foundation for the Service Architecture 59 L4 Hantera Vara/Tjänst Leverantör L4 Hantera Sortimentsplan Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Apoteksvaruinleverans L4 Hantera Apoteksvarubeställning L4 Hantera Apoteksvaruutleverans Försäljning L4 L3 Vara/tjänst L4 L3 L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Hantera Kundavtal Kundärende L4 The Process architecture Kundavtal L4 L4 Hantera Tjänsteleveranstillfälle L4 Hantera Betalning L3 Kampanj L4 Hantera Kampanj L3 Bemanning L4 Hantera Bemanning Internal and external market scan for applications and partners based on logical functional blocks Analysis and design of applications, IT services and platforms based on the Vision Architecture, Target Application Architecture, analysis of non-functional and technical requirements, IT strategy and architecture principles © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop a plan where the Solution Architecture is implemented in phases Develop Solution – Transformation Planning Define Transformation Strategy Evaluate Transformation Projects • Identify different scenarios • Analyze each scenario • Consider constraints, dependencies, business value etc. • Transformation Scenarios • Transformation Strategy Create Project Timelines Define Transition Architectures • Evaluate planned projects based on Business Value and Risk • Identify projects that have strong dependencies • Analyze system Life-cycle • Create data-driven transformation • Plan realization bottom-up • Realize the solution architecture in steps through a number of transition architectures • Project assessment • (Program plan) • (Mitigation plan) • Transformation project plan • Transition architecture models • Transition scope description Model type Deliverables Description Transformation Planning 60 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Financial requirements on the transformation Rip and replace scenario Build up new solutions in parallel and then close down the old systems Cost Time 2012 61 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Financial requirements on the transformation Migration scenario One system and platform at a time Cost Time 2012 62 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Transformation Planning Examples of transformation plan creation: – Put the most important business requirement on the timeline to show the most critical dates. – Use the system life cycle analysis to create an IT based transformation plan. – Create a data driven transformation plan. For example, first implement systems that creates data, then followed by systems that update and read data. Complement with analysis of data migration possibilities for systems that will be phased out. – Top down design (vision architecture) can be followed by bottom-up realization. Start with infrastructure and platforms. Follow up with new applications and new business processes. 63 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. A Transition Plan from a real case TUI Nordic 64 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Transition Summary 65 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Develop Solution – Transformation Planning Define Transformation Strategy Evaluate Transformation Projects • Identify different scenarios • Analyze each scenario • Consider constraints, dependencies, business value etc. • Transformation Scenarios • Transformation Strategy Create Project Timelines Define Transition Architectures • Evaluate planned projects based on Business Value and Risk • Identify projects that have strong dependencies • Analyze system Life-cycle • Create data-driven transformation • Plan realization bottom-up • Realize the solution architecture in steps through a number of transition architectures • Project assessment • (Program plan) • (Mitigation plan) • Transformation project plan • Transition architecture models • Transition scope description Model type Deliverables Description Transformation Planning 66 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Business Value Assessment (example) One important aspect of the implementation of the solution architecture is the alignment to other projects in terms of size (resources), value and risk. 67 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Solution – Transformation Planning Define Transformation Strategy Evaluate Transformation Projects • Identify different scenarios • Analyze each scenario • Consider constraints, dependencies, business value etc. • Transformation Scenarios • Transformation Strategy Create Project Timelines Define Transition Architectures • Evaluate planned projects based on Business Value and Risk • Identify projects that have strong dependencies • Analyze system Life-cycle • Create data-driven transformation • Plan realization bottom-up • Realize the solution architecture in steps through a number of transition architectures • Project assessment • (Program plan) • (Mitigation plan) • Transformation project plan • Transition architecture models • Transition scope description Model type Deliverables Description Transformation Planning 68 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re Transformation Planning – Analysis Implementation of suites often result in much focus on a single key system. Pay extra attention to integration issues since there probably will be many integrations involved. Analyze if new solutions need to co-exist with old solutions, and the effects this will have on the transformation plan. For example, temporary integrations might be needed. Look for alternatives that can result in quick wins on business requirements. 69 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Transformation planning workshop Run this workshop with business and IT together Example workshop questions: – – – – – – – 70 What is the important dates for realization of this solution architecture? Are there periods where we cannot implement new solutions? What are the main obstacles? Are there any important licenses with expiration dates during this period? Are there systems that must be phased out or replaced during this period? Are there any plans on group level that might affect us? Other already planned projects? © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Transition Plan Overview 72 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Develop Solution – Transformation Planning Define Transformation Strategy Evaluate Transformation Projects • Identify different scenarios • Analyze each scenario • Consider constraints, dependencies, business value etc. • Transformation Scenarios • Transformation Strategy Create Project Timelines Define Transition Architectures • Evaluate planned projects based on Business Value and Risk • Identify projects that have strong dependencies • Analyze system Life-cycle • Create data-driven transformation • Plan realization bottom-up • Realize the solution architecture in steps through a number of transition architectures • Project assessment • (Program plan) • (Mitigation plan) • Transformation project plan • Transition architecture models • Transition scope description Model type Deliverables Description Transformation Planning 73 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop Business Architectu re Develop Solution Scoping Business Modeling Develop Vision Architectu re Develop Solution Architectu re EXAMPLE Transition 1 74 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Transition 1 - Summary 75 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Transition 1 – Business Impact 76 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Transition 1 - Plan 77 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Transition 1 – IT Impact 78 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE EXAMPLE Transition 2 79 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Master Data Ownership 80 © 2013 Ericsson Enterprise Architecture Program. All rights reserved. EXAMPLE Develop Business Architectu re Develop Solution Architecture Develop the Service Architecture Perform Market scan Develop the Solution Architecture Scoping Business Modeling Develop Vision Architectu re Develop Solution Create the Transformation plan L1 Detaljhandel L3 Kund L3 L4 Hantera Kund L3 L3 Hantera Kundorder L4 Hantera Kundfaktura L4 Hantera Kassa is the foundation for the Service Architecture 81 L4 Hantera Vara/Tjänst Leverantör L4 Hantera Sortimentsplan Hantera Leverantör Apoteksdistribution L4 Hantera Apoteksvarulager L4 Hantera Apoteksvaruinleverans L4 Hantera Apoteksvarubeställning L4 Hantera Apoteksvaruutleverans Försäljning L4 L3 Vara/tjänst L4 L3 L4 Hantera Reklamation/ Återköp Hantera Kundärende L3 Hantera Kundavtal Kundärende L4 The Process architecture Kundavtal L4 L4 Hantera Tjänsteleveranstillfälle L4 Hantera Betalning L3 Kampanj L4 Hantera Kampanj L3 Bemanning L4 Hantera Bemanning Internal and external market scan for applications and partners based on logical functional blocks Analysis and design of applications, IT services and platforms based on the Vision Architecture, Target Application Architecture, analysis of non-functional and technical requirements, IT strategy and architecture principles © 2013 Ericsson Enterprise Architecture Program. All rights reserved. Develop a plan where the Solution Architecture is implemented in phases Develop Solution Architectu re
© Copyright 2024