Business Intelligence Dr. Mahdi Esmaeili 1. Technical Infrastructure Evaluation Hardware Network Middleware Database Management Systems Tools and Standards.

Slides:



Advertisements
Similar presentations
Distributed Data Processing
Advertisements

Welcome to Middleware Joseph Amrithraj
Roadmap for Sourcing Decision Review Board (DRB)
Software Quality Assurance Plan
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Dr Gordon Russell, Napier University Unit Data Dictionary 1 Data Dictionary Unit 5.3.
Meta Data Repository Analysis Business Intelligence Road Map
Chapter 10: Analyzing Systems Using Data Dictionaries Instructor: Paul K Chen.
Chapter 2 Database Environment Pearson Education © 2014.
Chapter 5: Project Scope Management
Business Intelligence
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Project Management and Scheduling
Chapter 2 Database System Concepts and Architecture
Load Test Planning Especially with HP LoadRunner >>>>>>>>>>>>>>>>>>>>>>
What is Business Analysis Planning & Monitoring?
By N.Gopinath AP/CSE. Why a Data Warehouse Application – Business Perspectives  There are several reasons why organizations consider Data Warehousing.
System Analysis and Project Management Key terms and definitions Presentation.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Computer System Analysis
Systems Design. Systems Design Skills People skill (25%) - Listening, understanding others, understanding between two lines, conflict resolution, handling.
Web Development Process Description
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the differences between requirements activities and design activities.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Understanding Data Warehousing
Roles and Responsibilities
Announcements Homework 1 Due 9/15 Project: Step 1 Due 9/17 Reading for Wednesday –2.6 – 2.8.
Project ManagementDay 1 in the pm Project Management (PM) Structures.
CSC271 Database Systems Lecture # 4.
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie.
PRODUCT LOCATOR PresentedBy Richard Raehl November 13, 2001.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
Lecture4 : Project planning Lecturer: Kawther Abas 447CS – Management of Programming Projects.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Basic of Project and Project Management Presentation.
Software Project Management
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
Datawarehouse A sneak preview. 2 Data Warehouse Approach An old idea with a new interest: Cheap Computing Power Special Purpose Hardware New Data Structures.
Project Management Methodology Development Stage.
NMI End-to-End Diagnostic Advisory Group BoF Fall 2003 Internet2 Member Meeting.
Chapter 2 Database System Concepts and Architecture Dr. Bernard Chen Ph.D. University of Central Arkansas.
Bayu Adhi Tama, M.T.I 1 © Pearson Education Limited 1995, 2005.
Database Administration
PRJ566 Project Planning & Management Software Architecture.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
State of Georgia Release Management Training
Chapter 2 Database Environment.
Team-Based Development ISYS321 Managing the Information Systems Project.
Introduction to Core Database Concepts Getting started with Databases and Structure Query Language (SQL)
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Managing Data Resources File Organization and databases for business information systems.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Project Management Chapter 3.
Chapter 3 Managing the Information Systems Project
Software Project Management
فصل پانزدهم فاز پياده سازي مونا بخارايي نيا
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Business Intelligence Dr. Mahdi Esmaeili 1

Technical Infrastructure Evaluation Hardware Network Middleware Database Management Systems Tools and Standards Nontechnical Infrastructure Evaluation Logical Data Model Meta Data Standards, Guidelines, and Procedures Step 2: Enterprise Infrastructure Evaluation 2

Controlled Hardware Chaos New hardware platforms have to fit into the existing hardware configuration. The DBMS on the selected hardware platform must perform well as database access and usage grow. Scalability is therefore one of the major issues to be addressed. Platform selection is restricted by the need for interoperability between various hardware platforms (if required). Cost and return on investment (ROI) for the previous three qualifiers are controlling factors 3

Data volumes Updating frequencies Data access patterns Number of reports and queries Number of people accessing the BI target databases Number of tools running against the BI target databases Number of operational systems feeding the BI target databases Hardware must also be scalable because rapid changes will occur in: 4

Three-Tier Computing Architecture 5

middleware Distributed logic middleware Data management middleware 6

Gateway Example 7

Point-to-point gateways Gateways that can be used universally Gateways using Structured Query Language (SQL) Gateways based on application programming interfaces (APIs) DBMS Gateways 8

Degree of parallelism in handling queries and data loads Intelligence in handling dimensional data models and optimizers Database scalability Internet integration Availability of advanced index schemes Replication on heterogeneous platforms Unattended operations Criteria for Selecting a DBMS 9

10

1.Technical infrastructure assessment report - Servers - Client workstations - Operating systems - Middleware (especially DBMS gateways) - Custom interfaces - Network components and bandwidth - DBMS functionality and utilities (backup and recovery, performance monitoring) - Development tools such as computer aided software engineering (CASE) and ETL tools - Access and analysis tools such as OLAP tools and report writers -Meta data repository 2.I nstallation of selected products If you identified new products to purchase, write a request for proposal (RFP) or a request for information (RFI) Deliverables Resulting 11

BI infrastructure architect Database administrator Roles Involved in These Activities Technology advances occur every few months Risks of Not Performing Step 2 12

Conduct an extensive business analysis Adopt a system of peer reviews Resolve age-old disputes about data definitions and domains Standardize data names and data values Get agreement from the business people Create a regular forum for business people Create a meta data repository Create an inventory of source data Create and manage one expanding central staging area (per load periodicity) for the ETL processes Creating Nontechnical infrastructure involves cross-organizational activities such as: 13

Enterprise Architecture Group A central enterprise architecture group must manage and coordinate Enterprise infrastructure activities 14

Enterprise Architecture Components 15

Enterprise Standards 16

17

1.Nontechnical infrastructure assessment report - Standards - Use of a development methodology - Estimating guidelines - Scope management procedure - Issues management procedure - Roles and responsibilities - Security process - Meta data capture and delivery - Process for merging project-specific logical data models into the enterprise logical data model - Data quality measures and triage process - Testing process - SLAs - Support function - Dispute resolution procedure - Communication process Deliverable Resulting 18

BI infrastructure architect Data administrator Data quality analyst Meta data administrator Roles Involved 19

Step 3: Project Planning What will be delivered? When will it be done? How much will it cost?Who will do it? Quality 20

Effort (Time) Scope Budget Resources Quality Budget Resources Effort (Time) Scope Typical OrderRecommended Order 21

project charter Goals and objectives Scope (80/20 Data/Function) Risks Constraints Assumptions Change-control procedures Issues management procedures The project charter is the agreement made between the business sponsor and the IT staff for developing the BI application 22

preparing a project plan Create a work breakdown structure listing activities, tasks, and subtasks. Estimate the effort hours for these activities, tasks, and subtasks. Assign resources to the activities, tasks, and subtasks. Determine the task dependencies. Determine the resource dependencies. Determine the critical path based on the dependencies. Create the detailed project plan. 23

24

Deliverables Resulting 1.Project charter - Goals and objectives (both strategic goals for the organization and specific objectives for the BI project) - Statement of the business problem - Proposed BI solution - Results from the cost-benefit analysis - Results from the infrastructure gap analysis (technical and nontechnical) - Functional project deliverables (reports, queries, Web portal) - Historical requirements (how many years of history to store) - Subject area to be delivered - Entities (objects), significant attributes, relationships (high-level logical data model) - Items not within the project scope (originally requested but subsequently excluded from the scope) - Condition of source files and databases - Availability and security requirements - Access tool requirements - Roles and responsibilities - Team structure for core team and extended team members - Communication plan - Assumptions - Constraints - Risk assessment - Critical success factors 2.Project plan A project plan may contain multiple graphs (such as a CPM chart, a Pert chart, or a Gantt chart) detailing task estimates, task dependencies, and resource dependencies. Most project-planning tools can also produce additional tabular reports on resources and schedule. 25

Roles Involved in This Step Application lead developer Business representative Data administrator Data quality analyst Database administrator ETL lead developer Meta data administrator Project manager Subject matter expert 26