Zachman介紹中文修訂實(shí)用教案VIP

1、2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework1Based on work by John A. ZachmanVA Enterprise ArchitectureDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhyDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhySCOPE(CONTEXTUAL)PlannerENTERPRISEMODEL(CONCEP

2、TUAL)OwnerSYSTEM MODEL(LOGICAL)DesignerTECHNOLOGYMODEL(PHYSICAL)BuilderDETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)Sub-ContractorFUNCTIONINGENTERPRISESCOPE(CONTEXTUAL)PlannerENTERPRISEMODEL(CONCEPTUAL)OwnerSYSTEM MODEL(LOGICAL)DesignerTECHNOLOGYMODEL(PHYSICAL)BuilderDETAILEDREPRESENTATIONS(OUT-OF-CONTEXT

3、)Sub-ContractorFUNCTIONINGENTERPRISEThings Important to the BusinessEntity = Class of Business ThingProcesses PerformedFunction = Class of Business ProcessSemantic ModelEnt = Business Entity Rel = Business RelationshipBusiness Process ModelProc = Business Process I/O = Business ResourcesBusiness Log

4、isticsSystemNode = Business Location Link = Business LinkageWork Flow ModelPeople = Organization Unit Work = Work ProductMaster ScheduleTime = Business Event Cycle = Business CycleBusiness PlanEnd = Business Objective Means = Business StrategyImportantOrganizationsPeople = Major OrganizationsBusines

5、s locationsNode = Major Business LocationsEvents Significantto the BusinessTime = MajorBusiness EventBusiness Goalsand StrategyEnds/Means =Major Business GoalsLogical DataModelEnt = Data Entity Rel = Data RelationshipApplication ArchitectureProc = Application Function I/O = User ViewsDistributed Sys

6、temArchitectureNode = IS Function Link = Line CharacteristicsHuman InterfaceArchitecturePeople = Role Work = DeliverableProcessingStructureTime = System Event Cycle = Processing CycleBusiness RuleModelEnd = Structural Assertion Means = Action AssertionPhysical DataModelEnt = Segment/Table Rel = Poin

7、ter/KeySystemDesignProc = Computer Function I/O = Data Elements/SetsTechnologyArchitectureNode = Hardware/Software Link = Line SpecificationsPresentationArchitecturePeople = User Work = Screen FormatControlStructureTime = Execute Cycle = Component CycleRuleDesignEnd = Condition Means = ActionDataDef

8、initionEnt = Field Rel = AddressProgramProc = Language Statement I/O = Control BlockNetworkArchitectureNode = Addresses Link = ProtocolsSecurityArchitecturePeople = IdentityWork = JobTiming DefinitionTime = InterruptCycle = Machine CycleRuleDesignEnd = Sub-Condition Means = StepDataEnt = Rel = Funct

9、ionProc =I/O =NetworkNode = Link =OrganizationPeople = Work =ScheduleTime = Cycle =StrategyEnd = Means =Based on work by John A. ZachmanVA Enterprise ArchitectureDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhyDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhySCOPE(CONTEXTUAL

10、)PlannerENTERPRISEMODEL(CONCEPTUAL)OwnerSYSTEM MODEL(LOGICAL)DesignerTECHNOLOGYMODEL(PHYSICAL)BuilderDETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)Sub-ContractorFUNCTIONINGENTERPRISESCOPE(CONTEXTUAL)PlannerENTERPRISEMODEL(CONCEPTUAL)OwnerSYSTEM MODEL(LOGICAL)DesignerTECHNOLOGYMODEL(PHYSICAL)BuilderDETAILED

11、REPRESENTATIONS(OUT-OF-CONTEXT)Sub-ContractorFUNCTIONINGENTERPRISEThings Important to the BusinessEntity = Class of Business ThingProcesses PerformedFunction = Class of Business ProcessSemantic ModelEnt = Business Entity Rel = Business RelationshipBusiness Process ModelProc = Business Process I/O =

12、Business ResourcesBusiness LogisticsSystemNode = Business Location Link = Business LinkageWork Flow ModelPeople = Organization Unit Work = Work ProductMaster ScheduleTime = Business Event Cycle = Business CycleBusiness PlanEnd = Business Objective Means = Business StrategyImportantOrganizationsPeopl

13、e = Major OrganizationsBusiness locationsNode = Major Business LocationsEvents Significantto the BusinessTime = MajorBusiness EventBusiness Goalsand StrategyEnds/Means =Major Business GoalsLogical DataModelEnt = Data Entity Rel = Data RelationshipApplication ArchitectureProc = Application Function I

14、/O = User ViewsDistributed SystemArchitectureNode = IS Function Link = Line CharacteristicsHuman InterfaceArchitecturePeople = Role Work = DeliverableProcessingStructureTime = System Event Cycle = Processing CycleBusiness RuleModelEnd = Structural Assertion Means = Action AssertionPhysical DataModel

15、Ent = Segment/Table Rel = Pointer/KeySystemDesignProc = Computer Function I/O = Data Elements/SetsTechnologyArchitectureNode = Hardware/Software Link = Line SpecificationsPresentationArchitecturePeople = User Work = Screen FormatControlStructureTime = Execute Cycle = Component CycleRuleDesignEnd = C

16、ondition Means = ActionDataDefinitionEnt = Field Rel = AddressProgramProc = Language Statement I/O = Control BlockNetworkArchitectureNode = Addresses Link = ProtocolsSecurityArchitecturePeople = IdentityWork = JobTiming DefinitionTime = InterruptCycle = Machine CycleRuleDesignEnd = Sub-Condition Mea

17、ns = StepDataEnt = Rel = FunctionProc =I/O =NetworkNode = Link =OrganizationPeople = Work =ScheduleTime = Cycle =StrategyEnd = Means =Zachman Framework第1頁/共11頁第一頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework2Zachman FrameworkRow 1 ScopeRow 1 Scope（范圍）（范圍）External Re

18、quirements and DriversExternal Requirements and Drivers（外部（外部(wib)(wib)需求和驅(qū)動力）需求和驅(qū)動力）Business Function ModelingBusiness Function Modeling（業(yè)務(wù)功能（業(yè)務(wù)功能模型）模型）nRow 2 Enterprise Model（企業(yè)(qy)模型）nBusiness Process Models（業(yè)務(wù)流程模型）nRow 3 System Model（系統(tǒng)模型(mxng)）nLogical Models（邏輯模型(mxng)）nRequirements Definition

19、（需求定義）nRow 4 Technology Model（技術(shù)模型）Physical Models（物理模型）Solution Definition and Development（解決方案定義和開發(fā)）nRow 5 As Built（構(gòu)建）As Built（構(gòu)建）Deployment（部署）nRow 6 Functioning EnterpriseFunctioning Enterprise（企業(yè)在IT上運(yùn)行的功能）Evaluation（評價）123456ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConce

20、ptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第2頁/共11頁第二頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework3Framework Rules（Zachman 框架框架(kun ji) 基本規(guī)則）基本規(guī)則） Rule 1: Columns have no order（列沒（列沒有有(mi yu)次序）次序） ContextualConceptualLogical

21、PhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHownRule 2: nEach column has a simple, basic model （每一列是一個(y )簡單的基本模型）nRule 3: Basic model of each column is unique（每一列的基本模型是獨(dú)一無二的） nRule 4: Each row represents a distinct view （

22、每一行表達(dá)特定方面的視圖）nRule 5: Each cell is unique（每個單元是唯一的） nRule 6: Combining the cells in one row forms a complete description from that view（每一行上的單元組合形成一個完整的視圖）Basic Model = Entities and RelationshipsEntityRelationshipEntity第3頁/共11頁第三頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture

23、Framework4Zachman Framework Row 1Scope/Planners View（范圍（范圍(fnwi)/規(guī)劃規(guī)劃者視圖）者視圖） External Requirements and Drivers（外部(wib)需求和驅(qū)動力） Business Function Modeling（業(yè)務(wù)功能模型）Motivation/Why（動因）Business goals, objectives and performancemeasures related to each function （業(yè)務(wù)目的/目標(biāo)，每個功能(gngnng)相關(guān)的性能度量指標(biāo)）nFunction/How（

24、功能）High-level business functions（高階業(yè)務(wù)功能）nData/What（數(shù)據(jù)）High-level data classes related to eachFunction（每個功能相關(guān)的高級數(shù)據(jù)分類）nPeople/Who（人）Stakeholders related to each function（每個功能相關(guān)的干系人）nNetwork/WhereVA locations related to each functionnTime/WhenCycles and events related to eachFunction（每個功能相關(guān)的業(yè)務(wù)周期和事件）1Co

25、ntextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第4頁/共11頁第四頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework5Zachman Framework Row 2Enterprise Model/Owners View（企業(yè)模（企業(yè)模

26、型型(mxng)/所有者視圖）所有者視圖） Business Process Models（業(yè)務(wù)流程模型） Business Function Allocation（業(yè)務(wù)功能分布(fnb)） Elimination of Function Overlap and Ambiguity（過濾重疊和不確定功能）Motivation/WhyPolicies, procedures and standards for eachprocess （每個流程相關(guān)的政策(zhngc)、規(guī)程和標(biāo)準(zhǔn)）nFunction/HowBusiness processes（業(yè)務(wù)流程）nData/WhatBusiness da

27、ta（業(yè)務(wù)數(shù)據(jù)）nPeople/WhoVA roles and responsibilities in eachProcess（每個流程的角色和責(zé)任）nNetwork/WhereVA locations related to each processnTime/WhenEvents for each process and sequencingof integration and process improvements促使過程改進(jìn)和流程整合的事件2ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptua

28、lLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第5頁/共11頁第五頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework6Zachman Framework Row 3System Model/Designers View Logical Models（邏輯視圖） Project Management（項目管理） Requirements Definition（需求(xqi)定義

29、） Motivation/WhyVA policies, standards and proceduresassociated with a business rule model （與業(yè)務(wù)規(guī)則模型聯(lián)系的政策、標(biāo)準(zhǔn)(biozhn)和規(guī)程）nFunction/HownLogical representation of informationnsystems and their relationships （信息系統(tǒng)及其關(guān)系(gun x)的邏輯表達(dá)）nData/WhatLogical data models of data and datarelationships underlying VA i

30、nformation 表達(dá)數(shù)據(jù)之間關(guān)系的邏輯數(shù)據(jù)模型nPeople/WhoLogical representation of access privilegesconstrained by roles and responsibilities由角色和職責(zé)限制的訪問權(quán)限的邏輯表達(dá)nNetwork/WhereLogical representation of the distributedsystem architecture for VA locations（部署在VA位置分布式系統(tǒng)架構(gòu)的邏輯表達(dá)）nTime/WhenLogical events and their triggered resp

31、onses constrained by business events and their responses （由業(yè)務(wù)事件及其響應(yīng)約束的邏輯事件和響應(yīng)）3ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第6頁/共11頁第六頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise A

32、rchitecture Framework7Zachman Framework Row 4Technology Model/Builders View Physical Models（物理模型） Technology Management（技術(shù)管理） Solution Definition and Development （解決方案制定(zhdng)和開發(fā)）M o t i v a t i o n / W h yV A b u s i n e s s r u l e s c o n s t r a i n e d b y i n f o r m a t i o ns y s t e m s s

33、t a n d a r d s （ 由 系 統(tǒng) 信 息 標(biāo) 準(zhǔn) ( b i o z h n ) 約 束 的 V A 業(yè) 務(wù) 規(guī) 則 ）nFunction/HownSpecifications of applications that operatenon particular technology platforms （特定技術(shù)平臺(pngti)的應(yīng)用規(guī)格說明）nData/WhatDatabase management system (DBMS) typerequirements constrained by logical data models （由邏輯數(shù)據(jù)模型約束的數(shù)據(jù)管理系統(tǒng)）nPeo

34、ple/WhoSpecification of access privileges tospecific platforms and technologies針對 特定技術(shù)和平臺的的訪問權(quán)限規(guī)格說明nNetwork/WhereSpecification of network devices and theirrelationships within physical boundaries 在物理邊界范圍內(nèi)，網(wǎng)絡(luò)設(shè)備及其關(guān)系的規(guī)格說明nTime/WhenSpecification of triggers to respond to systemevents on specific platfor

35、ms and technologies （在特定平臺和技術(shù)上的系統(tǒng)事件和響應(yīng)的規(guī)格說明）4ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第7頁/共11頁第七頁，共12頁。2021年12月17日星期五A Tutorial on the Zachman Enterprise Architecture Framework8Zachman Fram

36、ework Row 5As Built/Integrators View As Built（構(gòu)建(u jin)） Configuration Management（配置管理） Deployment（部署） Motivation/WhyVA business rules constrained by specific technology standards （由特定的技術(shù)標(biāo)準(zhǔn)所限制的業(yè)務(wù)(yw)規(guī)則）nFunction/HownPrograms coded to operate on specific ntechnology platforms （在特定的技術(shù)(jsh)平臺上運(yùn)行的程序代碼）n

37、Data/WhatData definitions constrained by physical data models （由物理數(shù)據(jù)模型限制的數(shù)據(jù)定義）nPeople/WhoAccess privileges coded to control access to specific platforms and technologies （訪問權(quán)限代碼用來控制指定的平臺和技術(shù)）nNetwork/WhereNetwork devices configured to conform to node specifications （網(wǎng)絡(luò)設(shè)備被配置以適應(yīng)指定的節(jié)點(diǎn)）nTime/WhenTiming definitions coded to sequence activities on specific platforms and technologies（在指定的技術(shù)平臺上通過定義好的時序運(yùn)行一系列活動） 5ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第8頁/共11頁第八頁，共12頁。2021年12月17日星期五A Tut