home *** CD-ROM | disk | FTP | other *** search
/ Developer Source 3 / Developers_Source_Vol_03_1996.iso / dbprd / apr94 / hall11.gif < prev    next >
Graphics Interchange Format  |  1996-06-11  |  215KB  |  1028x719  |  4-bit (16 colors)
Labels: text | map | screenshot | diagram | rectangle | plan | parallel | square | circuit
OCR: DATA FUNCTION NETWORK PEOPLE TIME VALUES OBJECTIVES List of Things List of Processes List of Locations in List of Organization List of Business List of Business Important to the the Business Which the Business Units ... or "Users" Events/Cycles Goals/Strategies SCOPE Business Performs Operates ENTITY = Class of Process = Class of Mode = Business User - "Class" of User Event/Cycle - MaforBusiness Goal/Strategy = lastor Business Business Thing Business Process Location Events/Cycles Goals/Strategies ... "CSFs" MODEL e.g ., "ER Diagram" e.g ., "Function Flow e.g ., Logistics e.g ., Organization e.g ., Pert Chart e.g. , Business Plan Diagram' Nelwork Chart (continuous) OF THE BUSINESS Process = Business Process Node = Business Unit Entity = Business Entity 1,0 = Business Resources Link = Business Relationship User - Organization Unit Event = Business Event End = Business Objective Relationship - Business Rule (Including Into). (Orp. Product, Info) Work = Business "Transaction" Cycle - Business Cycle Means = Business Strategies MODEL e.g ., "Data Model" e.g .. "Data Flow Diagram e.g ., Distributed System Architecture e.g ., Human Interface e.g ., State Transition/ Dependency Diagrams e.g ., "Business Rules" Architecture OF THE INFORMATION SYSTEM Process = Application Function Node - US Function Eality - Data Entliy 1/0 - User Views (Processor, Storage, dic) User = Role Event - Trigger End & Condition Relationship = Data Relationship {Set of Data Elements) Link - Line Char Work = Deliverables Cycle = Processing Cycle Means - Actlona TECHNOLOGY e.g ., Data Design e.g ., "Structure Chart" e.g ., System Architecture e.g ., Human/Technology e.g ., Control Flow e.g ., Knowledge Design Interface Diagrams MODEL Node # Hardware/Systern Entity = Segment/Row Process = Computer Function Software User = Individuals Event = Execute End Relationship = Pointer/Key I/O = Screen/Device Formais Link = Line Specifications Work = System Transaction Cycle = Device Control Cycle Means DETAILED e.g ., Data Design e.g ., "Program" e.g ., Network Architecture e.g ., Security Architecture e.g e.g. Description REPRESEN TATIONS -- - Entity x Fields Process = Language Statements Node = Addressos User = Identity. Event = laterrupt Eng Relationship - Addresses 10 - Control Blocks Link = Protocols Work = Valld Comm. Cycle = Machine Cycle Means FUNCTIONING SYSTEM e.g .; DATA e.g .. FUNCTION e.g ., COMMUNICATIONS USERS DEPENDENCIES RULES Reprinted from IBM Systems Joumel, volume 31. 1992 FIGURE 1. Six-column Information Systems Architecture Framework ..