1 CONCENTRXSept 2000 Our Perspective “Integration without an architecture is like doing a jigsaw puzzle on your lap “ – R Tessier We look at the big picture.

Slides:



Advertisements
Similar presentations
Module 13: Performance Tuning. Overview Performance tuning methodologies Instance level Database level Application level Overview of tools and techniques.
Advertisements

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 19: Network Management Business Data Communications, 5e.
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Objectives/ Scope List of things important to the enterprise List.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
A Tutorial on the Zachman Framework for Enterprise Architecture
All Rights Reserved: JusticeExperts.com Enterprise? What Enterprise? Enterprise Development.
9/6/2001Database Management – Fall 2000 – R. Larson Information Systems Planning and the Database Design Process University of California, Berkeley School.
Oracle Database Administration
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
SLIDE 1IS Fall 2010 Information Systems Planning and the Database Design Process Ray R. Larson University of California, Berkeley School.
Chapter 10: Analyzing Systems Using Data Dictionaries Instructor: Paul K Chen.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
The Use of Zachman Framework Primitives for Enterprise Modeling
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 2: IS Building Blocks Objectives
CHAPTER 3 DATABASES AND DATA WAREHOUSES. 3-2 STUDENT LEARNING OUTCOMES 1.Describe business intelligence and its role 2.Compare databases and data warehouses.
Lecture Nine Database Planning, Design, and Administration
The database development process
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Chapter 9 Overview  Reasons to monitor SQL Server  Performance Monitoring and Tuning  Tools for Monitoring SQL Server  Common Monitoring and Tuning.
Module 8: Monitoring SQL Server for Performance. Overview Why to Monitor SQL Server Performance Monitoring and Tuning Tools for Monitoring SQL Server.
Database Administration Chapter 16. Need for Databases  Data is used by different people, in different departments, for different reasons  Interpretation.
BUSINESS INTELLIGENCE/DATA INTEGRATION/ETL/INTEGRATION AN INTRODUCTION Presented by: Gautam Sinha.
Geog 463: GIS Workshop May 15, 2006 Information Systems Architecture Reading: Zachman 1987.
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Chapter 2 CIS Sungchul Hong
DATABASE UTILITIES. D ATABASE S YSTEM U TILITIES In addition to possessing the software modules most DBMSs have database utilities that help the DBA in.
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 2 (Chapter 2) Information System Building Blocks.
1 Introduction to Database Systems. 2 Database and Database System / A database is a shared collection of logically related data designed to meet the.
1 Adapted from Pearson Prentice Hall Adapted form James A. Senn’s Information Technology, 3 rd Edition Chapter 7 Enterprise Databases and Data Warehouses.
Oracle9i Performance Tuning Chapter 1 Performance Tuning Overview.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
1 Data Warehouses BUAD/American University Data Warehouses.
Chapter 2 Database Environment. Agenda Three-Level ANSI-SPARC Architecture Database Languages Data Models Functions of DBMS Components of DBMS Data Dictionary.
MIS 327 Database Management system 1 MIS 327: DBMS Dr. Monther Tarawneh Dr. Monther Tarawneh Week 2: Basic Concepts.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved. Computer Software Chapter 4.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
Database Environment Chapter 2. Data Independence Sometimes the way data are physically organized depends on the requirements of the application. Result:
Organizing Data and Information
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 2 Information System Building Blocks.
Database Administration
3/6: Data Management, pt. 2 Refresh your memory Relational Data Model
Lecture 4: Enterprise Architecture
25 April Unified Cryptologic Architecture: A Framework for a Service Based Architecture Unified Cryptologic Architecture: A Framework for a Service.
ARCH-04 Before You Begin Your Transformation Project… Phillip Magnay Architect – Applied Technology.
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
Managing Data Resources File Organization and databases for business information systems.
Ver 1,12/09/2012Code :CIS-131-SIS.-ENTERPRISEFASILKOM Architecture ENTERPRISE Systems By Kundang K Juman, Ir. MMSI Pertemuan-1.
Information System Applications
Zachman Framework Lecture 2.
The Components of Information Systems
PLM, Document and Workflow Management
Physical Data Model – step-by-step instructions and template
Data Warehouse.
Software Architecture in Practice
The Components of Information Systems
A Tutorial on the Zachman Framework for Enterprise Architecture
Developing solutions, building businesses
Metadata The metadata contains
Information System Building Blocks
System architecture, Def.
Presentation transcript:

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

3 CONCENTRXSept 2000 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 CONCENTRXSept 2000 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 CONCENTRXSept 2000

6 CONCENTRXSept 2000

7 CONCENTRXSept 2000 Sources of Information Business Units/Users Management Vision Technical Support Forms, Screens, Reports Systems and workflows Documents The Data

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