1 / 8

Our Perspective

Our Perspective. “Integration without an architecture is like doing a jigsaw puzzle on your lap “ R Tessier We look at the big picture to better insure that the project at hand will fit together with existing systems and corporate initiatives. 1. 2. 3. 4. 5. 6. DATA (WHAT). PROCESS

gil
Download Presentation

Our Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Our Perspective • “Integration without an architecture is like doing a jigsaw puzzle on your lap “ • R Tessier • We look at the big picture to better insure that the project at hand will fit together with existing systems and corporate initiatives

  2. 1 2 3 4 5 6 DATA (WHAT) PROCESS (HOW) NETWORK (WHERE) ROLE/PEOPLE (WHO) TIMING (WHEN) MOTIVATION (WHY) LIST OF THINGS IMPORTANT TO THE BUSINESS LIST OF PROCESSES THE BUSINESS PERFORMS LIST OF LOCATIONS IN WHICH THE BUSINESS OPERATES LIST OF BUSINESS RESPONSI- BILITIES LIST OF BUSINESS EVENTS LIST OF BUSINESS GOALS ENTITY: class of business things PROCESS: class of business processes RESP: class of business responsibilities EVENT: class of significant business events NODE: business location ENDS: missions / goals BUSINESS ENTITIES & THEIR INTER-RELATIONSHIPS FLOWS BETWEEN BUSINESS PROCESSES COMMUNICATIONS LINKS BETWEEN BUSINESS LOCATIONS BUSINESS ORGANIZATION BUSINESS CYCLES BUSINESS STRATEGIES ENTITY: business entity RELN: business rule NODE: business unit group LINK: business connection EVENT: business event CYCLE: lapse / lag ENDS: goals / mission MEANS: tactics / plans PROCESS: business process I/O: business product service RESP: work unit / structure WORK: business resources MODEL OF THE BUSINESS DATA & ITS INTER-RELATIONSHIPS FLOWS BETWEEN APPLICATIONS PROCESSES DISTRIBUTION NETWORK MODEL OF ACCESS REQUIREMENTS MODEL OF PROCESS CONTROL STRUCTURE SERVICE SUPPORT ENVIROMENT ENDS: service level agreements MEANS: I/S plans & change tactics NODE: set of I/S functionality (processor, storage, etc.) LINK: line characteristics PROCESS: application system I/O: user views (set of data elements) EVENT: logical process event CYCLE: precedence / timing ENTITY: data entry RELN: data relationship RESP: system privilege WORK: access requirements DATABASE DESIGN SYSTEM DESIGN CONFIGURATION DESIGN ACCESS DESIGN PROCESSING ENVIRONMENT AVAILABILITY DESIGN EVENT: physical process event CYCLE: processing calendar ENDS: benchmark models MEANS: availability windows & availability measures NODE: hardware, system, software LINK: line specifications RESP: access authorizations WORK: access group ENTITY: segment, row, recd RELN: pointer, key, index PROCESS: computer process I/O: screen/device formats DATABASE SCHEMA & SUBSCHEMA DEFINITION PROGRAM CODE & CONTROL BLOCKS CONFIGURATION DEFINITION ACCESS DEFINITION JOB PROCESSING DEFINITION PERFORMANCE DEFINITION EVENT: trans. job submittal CYCLE: job & region schedules ENDS: benchmark targets MEANS: benchmark testing system monitoring / tunning ENTITY: fields, data types RELN: addresses, access methods PROCESS: language statements I/O: control blocks NODE: addresses LINKS: protocols RESP: access object WORK: access profiles DATA STORAGE STRUCTURES EXECUTABLE CODE SYSTEM CONFIGURATION ACCESS PRIVILEGES PROCESSING SCHEDULES SYSTEM MANAGEMENT FACILITIES Programs Common modules Host, network, switches, monitors... Batch jobs, transactions, run/rerun instructions Monitoring facilities problem management Database data User ids, access controls ZACHMAN FRAMEWORK FOR ENTERPRISE ARCHITECTURE s 1 BUSINESS SCOPE (Planner) 2 BUSINESS MODEL (Owner) 3 INFORMATION SYSTEMS MODEL (Designer) 4 TECHNOLOGY MODEL (Builder) 5 TECHNOLOGY DEFINITION (Subcontractor) (HUMAN) (MACHINE) 6 INFORMATION SYSTEMS (Machine View)

  3. Key Points • The framework is a classification schema • Rows represent roles that use information • Columns respresent aspects of information • Must be understood • Must be controlled • Can be optimized • Cells represent unique types of components • The framework helps one see the bigger picture

  4. Definitions • Technique • How one manages the tasks for a cell • Methodology • Set of cells addressed • Tool • Mechanism (or tool) used for the tasks in a cell

  5. Sources of Information • Business Units/Users • Management Vision • Technical Support • Forms, Screens, Reports • Systems and workflows • Documents • The Data

  6. Provisioning Finance Data Mart DSS Data Warehouse (DW) Data Delivery Marketing Data Mart DSS Demographic Data Mart DSS Data Acquisition Data Mgt Sales Contact APP Message Delivery Operational Data Store (ODS) Service APP Billing Legacy Environment Metadata DSS Corporate Information FactoryParts and Pieces Refresh Collector Usage Collector Content Collector Security Utilization Content Log Tuning Cost Allocation Capacity Planning

More Related