Zachman介紹中文修訂PPT學(xué)習(xí)教案

1、會(huì)計(jì)學(xué)1Zachman介紹中文修訂介紹中文修訂2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework2Based on work by John A. ZachmanVA Enterprise ArchitectureDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhyDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhySCOPE(CONTEXTUAL)Planne

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

3、NTATIONS(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 = Busines

4、s 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 StrategyImportantOrganizationsPeople = Maj

5、or 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/O = Us

6、er ViewsDistributed SystemArchitectureNode = IS Function Link = Line CharacteristicsHuman InterfaceArchitecturePeople = Role Work = DeliverableProcessingStructureTime = System Event Cycle = Processing CycleBusiness RuleModelEnd = Structural Assertion Means = Action AssertionPhysical DataModelEnt = S

7、egment/Table Rel = Pointer/KeySystemDesignProc = Computer Function I/O = Data Elements/SetsTechnologyArchitectureNode = Hardware/Software Link = Line SpecificationsPresentationArchitecturePeople = User Work = Screen FormatControlStructureTime = Execute Cycle = Component CycleRuleDesignEnd = Conditio

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

9、epDataEnt = Rel = FunctionProc =I/O =NetworkNode = Link =OrganizationPeople = Work =ScheduleTime = Cycle =StrategyEnd = Means =Based on work by John A. ZachmanVA Enterprise ArchitectureDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVATIONWhyDATAWhatFUNCTIONHowNETWORKWherePEOPLEWhoTIMEWhenMOTIVA

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

11、HYSICAL)BuilderDETAILEDREPRESENTATIONS(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 =

12、Business Process I/O = 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 StrategyImpo

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

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

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

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

17、End = Sub-Condition Means = StepDataEnt = Rel = FunctionProc =I/O =NetworkNode = Link =OrganizationPeople = Work =ScheduleTime = Cycle =StrategyEnd = Means =第1頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework3nRow 2 Enterprise Model（企業(yè)模型）Business Process Models（業(yè)務(wù)流程模型）n

18、Row 3 System Model（系統(tǒng)模型）Logical Models（邏輯模型）Requirements Definition（需求定義）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（評(píng)價(jià)）123456Co

19、ntextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第2頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework4ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConc

20、eptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHownRule 2: Each column has a simple, basic model （每一列是一個(gè)簡單的基本模型）nRule 3: Basic model of each column is unique（每一列的基本模型是獨(dú)一無二的） nRule 4: Each row represents a distinct view （每一行表達(dá)特定方面的視圖）nRule 5: Each cell is unique（每個(gè)單元

21、是唯一的） nRule 6: Combining the cells in one row forms a complete description from that view（每一行上的單元組合形成一個(gè)完整的視圖）Basic Model = Entities and RelationshipsEntityRelationshipEntity第3頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework5nFunction/How（功能）High-level business function

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

23、alAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第4頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework6nFunction/HowBusiness processes（業(yè)務(wù)流程）nData/WhatBusiness data（業(yè)務(wù)數(shù)據(jù)）nPeople/WhoVA roles and responsib

24、ilities in eachProcess（每個(gè)流程的角色和責(zé)任）nNetwork/WhereVA locations related to each processnTime/WhenEvents for each process and sequencingof integration and process improvements促使過程改進(jìn)和流程整合的事件2ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhy

25、WhoWhoWhenWhenWhereWhereWhatWhatHowHow第5頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework7nFunction/HowLogical representation of informationsystems and their relationships （信息系統(tǒng)及其關(guān)系的邏輯表達(dá)）nData/WhatLogical data models of data and datarelationships underlying VA informati

26、on 表達(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 responses co

27、nstrained by business events and their responses （由業(yè)務(wù)事件及其響應(yīng)約束的邏輯事件和響應(yīng)）3ContextualConceptualLogicalPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第6頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Frame

28、work8nFunction/HowSpecifications of applications that operateon particular technology platforms （特定技術(shù)平臺(tái)的應(yīng)用規(guī)格說明）nData/WhatDatabase management system (DBMS) typerequirements constrained by logical data models （由邏輯數(shù)據(jù)模型約束的數(shù)據(jù)管理系統(tǒng)）nPeople/WhoSpecification of access privileges tospecific platforms and tech

29、nologies針對(duì) 特定技術(shù)和平臺(tái)的的訪問權(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 platforms and technologies （在特定平臺(tái)和技術(shù)上的系統(tǒng)事件和響應(yīng)的規(guī)格說明）4ContextualConceptualLogica

30、lPhysicalAs BuiltFunctioningContextualConceptualLogicalPhysicalAs BuiltFunctioningWhyWhyWhoWhoWhenWhenWhereWhereWhatWhatHowHow第7頁/共11頁2021年10月13日星期三A Tutorial on the Zachman Enterprise Architecture Framework9nFunction/HowPrograms coded to operate on specific technology platforms （在特定的技術(shù)平臺(tái)上運(yùn)行的程序代碼）nData/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)限代碼用來控制指定的平臺(tái)和技術(shù)）nNetwork/WhereNetwork devices configured to c