LECTURE 1.1: Enterprise Architecture

Transcription

1 LECTURE 1.1: Enterprise Architecture Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 1 Ent. Cnt. The Enterprise: A Definitin f Sme Terms Any cllectin f crprate r institutinal task-supprting functinal entities with a set f cmmn gals/ single mandate. (Minli, 2008) Architect: One designing f an architecture & creating an architectural descriptin Architecture: Basic system rg embdied in its cmpnents, their relatinships t each ther & the envirnment, and principles guiding its design and evlutin Enterprise architecture: Arch where system is whle enterprise, especially its BPs, technlgies, and inf systems. Sme (Enterprise) Architectural definitins: Artefact: A reprt, analysis, mdel etc. cntributing t an architectural descriptin Descriptin: A cllectin f artefacts dcumenting an architecture Framewrk: A skeletal structure defining particular artefacts, describing hw they are related and prviding generic definitins fr what thse they might lk like Methdlgy: Generic term fr any structured slutin t prblems n architectures Arch taxnmy: A methdlgy fr rganizing and categrizing artefacts Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 2 CA4 BPM - Enterprise Architecture 1

2 Ent. Cnt. Enterprise Architecture What is Enterprise Architecture? A blueprint defining the structure and peratin f an rganizatin. Object: t assess hw rg can best reach current, future bjectives Cntains: a permitted structure; cnfiguratin; capabilities functinal grupings; interfaces, data, prtcls; lgical functinality; the integratin and technlgy f IT resurces; t supprt an rg, business functin r missin (Minli, 2008). Fcus is n the human element: hw t architect /plan rg fr ptimum human perfrmance & utput Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 3 Ent. Cnt. What is The Pint f Enterprise Architecture? Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 4 CA4 BPM - Enterprise Architecture 2

3 Ent. Cnt. What is The Pint f Enterprise Architecture? (/2) Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 5 Ent. Cnt. An Enterprise Architecture (EA) Case-Study: The Rise & Fall f MedAMre MedAMre is a pharmacy chain, started as a US reginal chain in In 1995 it develped an IT system (MedAManage r MAM) with sme innvative business ideas allwing it t run chemists very efficiently. MAM cnsisted f three prgrams MAM/Stre which ran n a small cmputer in a chemist; MAM/Warehuse running n a server in a reginal Warehuse; MAM/Hme which ran n a large server in the Hme Office. By 2000 MedAMre was ding well: Due t cst cutting enabled by MAM, it expanded by buying three reginal chains. With these purchases MedAMre extended its reach thr SE US Hwever by 2002, clear that IT systems that fuelled MedAMre s success nw hampered it's future MAM mdules cmprised 10 6 lines f cde! Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 6 CA4 BPM - Enterprise Architecture 3

4 Ent. Cnt. MedAMre : The Rise & Fall Sme prblems MedAMre were running int included: 1. MAM/Stre needed reginal specialisatins: e.g. different insurance plans had t be supprted in different regins, needing t MAM/Stre s mdule 2. Newly-acquired reginal warehuses each had wn different ways: a. t receive rders frm the retail stres & b. t rder supplies frm whlesalers, all needing changes t the MAM/Warehuse mdule 3. Fr inf sharing MedAMre used File Transfer. When cmpany was 30 pharmacies, 1 reginal Warehuse & 1 hme ffice wrked well; 200 pharmacies, 4 reginal Warehuse, 2 Gegraphic ffices and ne hme ffice, wrked badly. => files were: delivered late, smetimes never ccasinally multiple times hard fr hme ffice t get reliable up-t-date financial inf especially in the areas f sales and inventry Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 7 Ent. Cnt. MedAMre (/3): A Cmpany in Crisis Brett (business VP) Cath (CEO) Irma (CIO) Prblems, prblems All functins accessed ne db =>ne recrd change culd cause chas Business wanted mre acquisitins but IT already struggling By 2005 Irma nt seen as executive team member anymre Brett tried t bypass IT sectin at every pprtunity Little input by business int IT, cstly IT prjects ignred & scrapped By 2006, crisis! Cath met with Irma, Brett t annunce an EA initiative t save MedAMre MAM-EA had t unite IT, business & give full business value fr investment Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 8 CA4 BPM - Enterprise Architecture 4

5 SECTION 1.1: A FIRST ENTERPRISE ARCHITECTURE FRAMEWORK Lecture 1: Enterprise Architecture: Fundamentals 9 Ent. Cnt. Apprach 1: Zachman s Enterprise Architecture (EA) Framewrk s Framewrk is a widely used apprach fr develping r dcumenting an enterprise-wide architecture. EA dates t Framewrk fr infrmatin systems architecture paper in 1987 Main gal: lgical cnstructs t manage increasing cmplexity f IS in rgs. The framewrk * is a tw dimensinal matrix representing the viewpints n the Y axis; and the views n the X axis. In this framewrk viewpints are represented by: different stakehlders; and clearly defined deliverables; * Actually, mre f a taxnmy than a framewrk Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 10 CA4 BPM - Enterprise Architecture 5

6 Ent. Cnt. Zachman Framewrk Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 11 Ent. Cnt. Zachman & Enterprise Architecture (EA) 3 suggestins frm Zachman: 1. Each architectural artefact shuld be in nly 1 cell. If unclear in which cell a particular artefact lives, the prblem is with the artefact itself. 2. Architecture is cmplete nly when every cell is cmplete: i.e. cell has enugh artefacts t fully define the system fr a player lking at ne specific descriptive fcus, s each player knws all system aspects; with all cells full we have enugh detail t fully describe the system frm each SH s perspective, s cmpany knws they can all take part in talks; 3. Cells in clumns are related t each ther e.g. the first (data) clumn: frm business wner s (Brett) perspective, data is inf abut business; frm the db admin s perspective it s db rws & clumns. Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 12 CA4 BPM - Enterprise Architecture 6

7 Ent. Cnt. Can Help: Hw Zachman Can/nt Help MedAMre Ensure every SH s perspective is examined fr every descriptive fcal Pint Imprve the MAM-EA artefacts themselves by sharpening each f their fcus pints t ne particular cncern fr ne particular audience Ensure all f Brett s business needs are traceable t sme technical impln Cnvince Brett that Irma s IT team wn't plan n building useless functinality Cnvince Irma that the business team will include her IT team in their planning But nt full answer fr rg - many issues fr MAM-EA success unaddressed: N step-by-step way t create a new architecture prvided Little help given in deciding if ur future architecture is the ptimal pssible N apprach given t shw the future architecture is necessary! Fr these and thers we are ging t need t lk at ther methdlgies Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 13 SECTION 1.2: A SECOND ENTERPRISE ARCHITECTURE FRAMEWORK Lecture 1: Enterprise Architecture: Fundamentals 14 CA4 BPM - Enterprise Architecture 7

8 Ent. Cnt. Apprach 2: The Open Grup Architecture Framewrk (TOGAF) The Open Grup Architecture Framewrk s EA view 1. Business Architecture: the BPs the rg uses t meet its gals 2. Applicatin Architecture: design f specific apps & hw they interact 3. Data Architecture: rganizatin f & access t enterprise datastres 4. Technical Architecture: h/w, m/w, s/w infrastructure supprting the interacting apps Key part: Architecture Develpment Methd (ADM) cmplements Zachman: Zachman says hw t categrise artefacts; TOGAF is a prcess t create them Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 15 Ent. Cnt. Basic TOGAF Cncepts Cnceptual framewrk f IEEE 1471 (partial view) Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 16 CA4 BPM - Enterprise Architecture 8

9 Ent. Cnt. TOGAF, Its Wrldview & the Architecture Devpt Methd (ADM) s EA wrldview (The Enterprise Cntinuum) is shwn belw: Enterprise Cntinuum: TOGAF sees EA cntinuum frm generic t very specific Fundatin Archs: Generic principles, applicable t any rganisatin Cmmn Systems Archs: Mre specific principles (e.g. fr security, mgmt) - all incmplete in verall system functinality, but cmplete in particular prblem dmain Industry Archs: Principles fr dmain (e.g. data mdel with business functins & BPs) Org Architectures: Principles, specific t a specific enterprise (e.g. MedAMre) shws hw t g frm the generic t the specific Each cycle, EA cnsiders what Arch resurces are available frm the EC (e.g. business mdels fr the rg's industry sectr) t build enterprise-specific archs & slutin(s) Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 17 Ent. Cnt. The Enterprise Cntinuum (/2) Classifies arch/slutin artefacts ging frm Generic t Org-Specific Archs. Architecture Repsitry (AR) Supprts EC by string different classes f arch utput at different levels f abstractin, created by ADM Stres artefacts frm prir EA runs (internals), industry ref mdels/ arch patterns (externals) S TOGAF facilitates understanding/ c-peratin between SHs and practitiners Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 18 CA4 BPM - Enterprise Architecture 9

10 Ent. Cnt. Enterprise Cntinuum A Mdel fr Structuring a Virtual Repsitry + Methds fr Classifying Arch, Slutin Artefacts in the: The Enterprise Cntinuum (/3) Architecture Cntinuum (lgical repn) Slutins Cntinuum (physical repn) generic tls, prducts, services, slutin cmpnents i.e. fundamental prviders f capabilities. impln f CSA with a set f prducts & services (may be certified/ branded. impln f an IA prviding re-usable packages f cmmn industry-specific cmpnents & services Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) Impln f OSA prviding required business functins; cntain as much uniqueness t suit actrs & BPs in rgs 19 Ent. Cnt. Establishing and Maintaining an Enterprise Architecture Capability Develping an EA Capability Requires f an Organizatin: Org Structures Rles & Respnsibilities Skills Prcesses & RE-ITERATION! Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) CA4 BPM - Enterprise Architecture 10

11 Ent. Cnt. Establishing and Maintaining an EA Capability (/2) What des RE-ITERATION! mean here? Cycles f TOGAF ADM Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 21 Ent. Cnt. s ADM is Shwn: TOGAF s Architecture Develpment Methd (ADM) Generic methd used t realize an EA frm business requirements. First sme Preliminary Investigatin Then cycle thr the 8 phases A-H At ALL stages cnfrm t requirements But MedAMre needs TOGAF expertise befre starting n ADM: MedAMre can train itself r Can buy in TOGAF expertise (specialist TOGAF cnsultants) E.g. Teri Architecture Develpment Methd (ADM), Adapted frm TOGAF (2011) Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 22 CA4 BPM - Enterprise Architecture 11

12 Ent. Cnt. ADM Preliminary Phase Fr this phase f MAM-EA ADM Teri needs t: Make sure everyne is nside with the TOGAF/ADM prcess Sunds easy but isn t a given! Smetimes getting buy-in n EA s need is hard Especially if IT side is driving, &/r bad bld between IT & business, as here Teri is lucky as Cath is behind EA but still Teri must wrk with: Brett t understand MedAMre s business philsphy, mdels & strategic drivers Irma t set ut arch principles driving tech architectures & put in TOGAF frmat Culd lk at Zachman Rw 1 t suggest candidate items here fr key issues Mdify TOGAF as necessary t fit in with MedAMre culture Any MedAMre-specific cnsideratins? E.g. use nly pen-surce sftware? Set up the gvernance system t versee future architectural wrk Teri may nt wrk n TOGAF at MedAMre after the first pass Key peple in the cmpany must be able t take it frward frm there Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 23 Ent. Cnt. ADM Phase A: Architecture Visin Fr Phase A: Teri issues a Request fr Architecture Wrk Teri helps spnsring rg here (as MedAMre has never dne ne befre) Includes business reasns fr EA request + budget, persnnel, cnstraints & scpe Establish high-level definitins fr baseline & target architectures (Phases B-D) These include the fur EA sub-architectures: Business Architecture: the BPs the rg uses t meet its gals Applicatin Architecture: design f specific apps & hw they interact Data Architecture: rganizatin f & access t enterprise datastres Technical Architecture: h/w, m/w, s/w infrastructure supprting the interacting apps Prduces Statement f Architecture Wrk t be blessed by SHs befre next phase Phase A Output: create Arch Visin fr ADM 1st Pass Statement f Architecture Wrk utlines hw t develp / deply the architecture described in the Architecture Visin Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 24 CA4 BPM - Enterprise Architecture 12

13 Ent. Cnt. ADM Phase B: Business Architecture Input t Phase B is Phase A s Output (Architecture Visin) Fr Phase B, Teri wrks primarily with Brett (&/r team): Phase B describes & inputs the artefacts int Zachman Rw 2: detailed business analysis & mdelling, tech requirements dcumentatin (drivers fr Phase C,D): sets ut the implicatins fr wrk in the remaining architecture dmains (e.g. by a dependency/ pririty matrix). Fr gd Phase B, input frm many SHs needed (e.g. wh must d what, why, by when and hw is it dne?) Majr Outputs: Detailed baseline & target business architecture Full gap analysis n differences between them Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 25 Ent. Cnt. ADM Phase C,D: IS, Technical Architectures Phase C is t IS Architecture what B is t Business Architecture: Develp Target Architectures fr Data and Applicatin Systems dmains Fr Phase C, Teri wrks primarily with Irma (&/r team): Essentially, describing & inputting the artefacts int Zachman Rw 3: Develp baseline data-arch descriptin (e.g. need data t supprt the rg?) Review and validate principles, reference mdels, viewpints, and tls Create arch mdels, mapping business functins t CRUD data peratins Cnduct checkpint reviews f the arch mdel & building blcks with SHs Review qualitative criteria (e.g., perfrmance, reliability, security, integrity) Cmplete data architecture, Cnduct impact analysis & gap analysis Majr Outputs: Baseline & Target Inf and Applicatins Arch, Gap Analysis. Phase D finishes Tech Architecture: mainly with Irma's technical team Sets ut infrastructure needed t supprt prpsed new architecture. Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 26 CA4 BPM - Enterprise Architecture 13

14 Ent. Cnt. ADM Phase E, F: Opprtunities & Slutins and Migratin Planning Phase E identifies ways t deliver Target Arch identified in previus phases: Lks at varius impln pssibilities, identifies the majr impln prjects pssible, assessing business pprtunities assciated with each. TOGAF tells Teri t "fcus n prjects delivering shrt-term payffs and s create an impetus fr prceeding with lnger-term prjects." S Teri shuld lk fr prjects with maximum saving fr minimum staff inputs. Lk firstly t rg pain-pints guiding Cath (CEO) twards an EA riginally. These included difficulties in cmpleting reginal/warehuse specializatin and unreliability in data sharing. Phase F takes this t the next stage: Teri (with MedAMre's gvernance bdy) priritises the prjects frm Phase E Include nt nly the cst & benefits (frmphase E), but als the risk factrs. Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 27 Ent. Cnt. ADM Phase G, H: Implementatin Gvernance & Arch Change Management Phase G: Implementatin Gvernance: arch versight f implementatin Teri ensures accrd with Target Arch by setting arch specs fr pririty prjects These specificatins will include acceptance criteria and lists f risks and issues. Outputs: Ppulated AR, Architecture Visin, updated pst-implementatin Phase H: Arch Change Mgmt: methds t manage change t new arch Teri alters the arch change-mgmt with new artefacts & new inf frm last cycle She ensures arch lifecycle is maintained & Gvernance Framewrk is executed Teri is then ready t start the cycle again. First cycle gal is inf transfer s Teri's services needed less with mre cycles Results depend as much n Teri s relatinship with MedAMre as TOGAF itself TOGAF is meant t be very adaptable & sparse n details fr varius artefacts Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 28 CA4 BPM - Enterprise Architecture 14

15 SECTION 1.4: TOGAF AT WORK IN HELIPARTS Lecture 1: Enterprise Architecture: Fundamentals 29 Case Study #2: TOGAF at Heliparts The Envirnment/ Prblem: Funded in mid-1990 s in small Helicpter Cnstructin, Repair & Maintenance area By late 2000 s Heliparts was a SME in Crisis Ecnmic dwnturn, Increased cmpetitin cmbined with Rise f drnes => perfect strm fr cmpany Result: Heliparts must reduce cst by 10% Slutin? EA (with TOGAF) suggested fr Change Mgmt Heliparts hped t respnd t changing market & identify new pprtunities Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 30 CA4 BPM - Enterprise Architecture 15

16 Case Study #2: Applicatin f ADM Architecture Change Management Luckily Heliparts had existing Architecture Bard Need t decrease csts taken as necessary change Bard mandated an ADM cycle t lk int arch changes needed t realise this change Thus rg respnded t changing market & seeking new pprtunities: Part f nrmal cycle f change! Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 31 Case Study #2: ADM Preliminary Phase Architecture Bard Fcus: "where, what, why, wh, & hw we d architecture" in Heliparts See in this ADM cycle what parts f Heliparts are in/ ut f scpe Define the Stakehlders & get all nside Reassess use f TOGAF, make changes t BPs needed If after first phase f TOGAF, might need t use rg s wn EA team Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 32 CA4 BPM - Enterprise Architecture 16

17 Case Study #2: ADM Phase A Architecture Bard Fcus: Statement f Architecture Wrk Says hw t develp/deply arch set ut in Architecture Visin Interview stakehlders and agree timings f architectural wrk Develp Arch Visin cvering Business, Applicatin & Technlgy Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 33 Case Study #2: ADM Phases BCD Bard Fcus: Develp Baseline and Target Business, Applicatin, Technlgy Architectures Als Each develp phase develp Target Architecture as-is architecture accrding t Architectural Visin Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 34 CA4 BPM - Enterprise Architecture 17

18 Case Study #2: ADM Phases BCD (/2) Bard Fcus: Develp Baseline and Target Business, Applicatin, Technlgy Architectures Gap Analysis pints t what needs t be dne t get t business gals Fr instance, can see that: 1. Develping standard Prject Parts db 2. Aligning departments t a new management structure 3. Decmmissining certain site-specific applicatins wuld help realise ur gal Nte each ne f these cmes frm ne f ADM phases BCD Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 35 Case Study #2: Phase E Opprtunities & Slutins Arch Bard Fcus: Gap analysis utput f B-D cnslidated int wrk packages & prjects Nw lk at prducts & services available t us frm suppliers & partners Key here Extract value frm prjects Organizing them t help firm g frm as-is t t-be state in structured manner Fund that these can run at same time: Rerganize mgmt & departments Align a prduct Parts catalgue But the latter was dependent n Mth-balling site-specific applicatins Mving t a single supplier Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 36 CA4 BPM - Enterprise Architecture 18

19 Case Study #2: Phase F Migratin Planning Arch Bard Fcus: Prject Priritisatin If plan is acceptable as realistic & achievable start t develp prject charters, stating: scpe, bjectives, and participants in a prject) Included, in particular, are: Time Cst Dependencies Resurce Requirements Take stakehlders views int cnsideratin Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 37 Case Study #2: Phases G, H Phase G: Implementatin Gvernance Arch Bard Fcus: Oversee pririty prjects t accrd with Target Arch Set arch specs fr prjects (eg acceptance criteria & lists f risks, issues) Bard als supprts them by verseeing: Their initiatin Prject cmpliance with guideline specs Phase H: Arch Change Management Kick Off Cmpliance Review This stage allws the architecture t be develped in a stable envirnment Prvides a mechanism t deal with changes in a cntrlled manner Saw that changes as firm transitined int a stable state had enabled us t save >10% Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 38 CA4 BPM - Enterprise Architecture 19

20 Questins?? Lecture 1: Enterprise Architecture: Fundamentals CA4101 Lecture Ntes (Martin Crane 2017) 39 CA4 BPM - Enterprise Architecture 20