IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, 2004 Identifying BI Opportunities and BIS Development Process Week 4 Dr. Jocelyn San Pedro School of Information.

Slides:



Advertisements
Similar presentations
MIS MANAGEMENT SUPPORT SYSTEMS CHAPTER 12 Fire your Customer
Advertisements

Chapter 1 Assuming the Role of the Systems Analyst
Decision Support Framework for BIS
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
DECISION SUPPORT SYSTEMS AND BUSINESS INTELLIGENCE
1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 14: Designing and Building Decision Support Systems Decision.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 13 Revision IMS Systems Analysis and Design.
F29IF2 : Databases & Information Systems Lachlan M. MacKinnon The Domain of Information Systems Databases & Information Systems Lachlan M. MacKinnon.
The use of information systems to add value to the organization is strongly influenced by organizational structure, culture, and change Identify the value-added.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, 2004 Summary and Revision Week 13 Dr. Jocelyn San Pedro School of Information Management & Systems Monash.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Designing and Building Decision Support Systems
Chapter 1 Assuming the Role of the Systems Analyst
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 3-1 Chapter 3 Decision Support Systems:
DECISION SUPPORT SYSTEM DEVELOPMENT
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Class 11 Decision Making, Decision Support Systems, & Executive Information Systems MIS 2000Decision Making and Information Systems.
Introduction to Systems Analysis and Design
Mgt 20600: IT Management & Applications Decision Support Systems Tuesday April 18, 2006.
The Academy of Public administration under the President of the Republic of Uzbekistan APPLICATION MODERN INFORMATION AND COMMUNICATION TECHNOLOGY IN DECISION.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Initiating and Planning Systems Development projects
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
1.Knowledge management 2.Online analytical processing 3. 4.Supply chain management 5.Data mining Which of the following is not a major application.
1 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Describing Methodologies PART II Rapid Application Development*
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Decision Support System Definition A Decision Support System is an interactive computer-based system or subsystem that helps people use computer communications,
Using Information Technology Chapter 11 Information Systems.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Decision Support System Development By Dr.S.Sridhar,Ph.D., RACI(Paris),RZFM(Germany),RMR(USA),RIEEEProc. web-site :
CHAPTER 13 Acquiring Information Systems and Applications.
Principles of Information Systems, Sixth Edition Information Systems in Organizations Chapter 2.
Ihr Logo Chapter 6 Decision Support System Development Turban, Aronson, and Liang Decision Support Systems and Intelligent Systems, Seventh Edition.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
Architecture of Decision Support System
Decision Support Systems Development
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 3-1 Chapter 3 Decision Support Systems:
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Fundamentals of Information Systems, Third Edition 1 Information and Decision Support Systems: Management Information Systems Management information system.
System A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Faculty Economics & Business EBS 2033 Systems Development Lecture 1 The Systems Development Environment Lecturer: Puan Asleena Helmi.
Chapter 3 Decision Support Systems: An Overview
Chapter 6 Decision Support System Development
Chapter 14: Designing and Building Decision Support Systems
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 (pages 4-9); Overview of SDLC
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 6 Decision Support System Development
Chapter 3 Decision Support Systems: An Overview
Chapter 1 The Systems Development Environment
Presentation transcript:

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, 2004 Identifying BI Opportunities and BIS Development Process Week 4 Dr. Jocelyn San Pedro School of Information Management & Systems Monash University

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The Assignment  Part 1 – Case Study (Marks 10%)  Part 2 – Prototype BIS (Marks 20%)  Report (15%)  Prototype (5%)  Due on May 3, Week 9, during tutorial  Please read Assessment notes on Unit Outline or Assessment page of Unit website.

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Lecture Outline  Summary of last week’s lecture  Identifying Business Intelligence Opportunities  The Business Intelligence Systems Development Process

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Learning Objectives At the end of this lecture, the students will  Have developed attitudes which enable them to  identify and evaluate business intelligence opportunities  plan for business intelligence solution  Have knowledge of major approaches to BIS development  Have an overall understanding of the BIS development

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Summary of last week’s lecture  Different Frameworks for DSS  DSS Framework for understanding BIS  Data-driven BIS – information systems that provide BI through access and manipulation of large databases of structured data  Model-driven BIS – information systems that provide BI through access and manipulation of models (mathematical, conceptual, etc)  Knowledge-driven BIS - information systems that provide BI through access and manipulation of predictive models and/or knowledge bases (containing expert’s domain knowledge)

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Summary of last week’s lecture  Document-driven BIS - information systems that provide BI through access and manipulation of unstructured, semi-structured or well-structured documents  Communications-driven and Group BIS - information systems that provide BI through communications, collaboration, negotiations among members of team, group, or organisation structure  Hybrid BIS – combination of any two or more of the above types of BIS

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Summary of last week’s lecture Some conclusions  Data becomes BI once they are placed onto the hands of decision makers  In analysing BIS, it is important to identify USERS, the TYPE of BI (or purpose) that it provides to the users, the DRIVING COMPONENT (data, model, knowledge, document, communications), the TECHNOLOGY, the expected BENEFITS (improve operational, tactical, or strategic decisions)

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying Business Intelligence Opportunities

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities A. Doing your homework Where will the BI application be used in the organisation?  Functional area – department of a business unit that is focused on a specific function – finance, marketing, sales, human resources, manufacturing, productions, etc.  Operational BI applications - e.g., smart manufacturing – ability of back-end production systems to listen to instructions and produce quality custom products  Tactical BI applications –customer relationship management

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Where will the BI application be used in the organisation?  Business unit - organisational structure in which a coherent set of functional activities rolls up into one line of business  Strategic BI application- cross-functional applications, e.g., product and product line contribution analysis; customer profitability analysis; corporate planning

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Some questions to ask:  What is working vs. what is broken?  Where are you spending too much money for the apparent return?  What processes are taking too much time?  Where do you think you are missing opportunities?  Where are you making bad decisions?  Where are you making good decisions?

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Who are the users, both within organisational units and at higher levels?  Lower user job classification – more detailed data needed  e.g. call center operators – need data on customer names and addresses, product numbers and descriptions  Higher user job classification – more summarised data needed, models, analysis of trends and patterns,  e.g., analysts, managers, executives

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities What information is needed?  Decisions or processes  Measures  base measures such as unit sales, unit price, count of orders;  calculated (or derived) measures –average sales, average price, total count of orders  Dimensions for analysis available raw data  Products, customers,  Mental model of how organisation works

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities B. Sharing and Collecting Ideas  Arrange a brainstorming team  Define the brainstorming team  Ask business questions  Identify information requirements  Organise Information Requirements

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Ask business questions

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Identify Information Requirements

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Organise Information Requirements

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities C. Evaluating Alternatives  Group requirements into opportunity areas  Grade opportunities by importance  Grade opportunities by difficulty

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Group requirements into opportunity areas

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Evaluating Alternatives  Grade opportunities by importance  Actionability  Materiality of impact  Operational vs. Tactical vs. Strategic focus  Applying the importance criteria to opportunity areas

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Evaluating Alternatives  Grade opportunities by difficulty  Cross-functionality of design  Existence and accessibility of data  Complexity of calculations  Applying the difficulty criteria

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Evaluating Alternatives  Rank Opportunities  Creating a BI Opportunity Scorecard  Costs, Benefits and Returns

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Creating a BI Opportunity Scorecard

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Identifying BI Opportunities Costs, benefits, returns  Project costs – cost of new hardware, software, internal development costs, external development costs, internal training, ongoing maintenance  Returns on investment – e.g., time saved in producing reports, operating efficiencies form specific information, lower investment levels, improved customer service  Intangible benefits – e.g., improved operational and strategic decisions from better and timely information, improved employee communications and job satisfaction resulting from greater sense of empowerment, improved knowledge sharing

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Varies with type of BIS  common approaches are  Systems Development Life Cycle (SDLC) Approach  Rapid Prototyping Approach  End-user Development Approach

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Systems Development Life Cycle (SDLC) approach  Confirm user requirements  Systems analysis  System design  Programming  Testing  Implementation  Use and Evaluation

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Another version of SDLC approach – Mallach (2002 )

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process SDLC Approach  employs a series of recursive phases each with its own inputs, activities and outputs. These phases begin with “Problem definition” then “Feasibility Analysis” and finish with “Implementation” and “Maintenance”  The primary advantage of SDLC is the structure and discipline it brings. It is often used today, especially in cases where there is a contractual relationship between the developer and the end users.  The major complaint about SDLC is its rigidity since requirements in a BIS can change rapidly.

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Rapid Prototyping Approach  Identify user requirements  Develop and test a first iteration BIS prototype  Create the next iteration BIS prototype  Test the BIS prototype and return to Step 3 if needed  Pilot testing, phased or full-scale implementation

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Rapid Prototyping Approach  Throwaway prototypes are used for demo purposes only and then discarded. An iterative prototype is more often used.  Prototyping often reduces development time and cost over the SDLC approach. Also, the higher level of user involvement can lead to greater support for the BIS from management.  Advantages to the more cautious approach of SDLC are that documentation is often more comprehensive and there is better understanding of the system’s benefits and corresponding costs

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process End-User Development Approach  End-user developers are those who fall outside the confines of the IS department.  End-user developers play a variety of organizational roles and exhibit a variety of computer skills.  They are as diverse as “just a guy with a problem to solve” to the “department computer guru”.  Most end-user-developed applications evolve from an informal process, which may cause problems if the application needs to be integrated into a larger DSS

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Advantages and Risks of End-User Development Approach  One disadvantage is that novice developers may bypass conventional control and testing procedures.  Another is lack of quality documentation, which can be a major problem if the developer leaves the organization.  Lack of security measures also tend to be a problem, especially on applications that access the Internet.

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process ROMC User Interface Design Approach  Representations for conveying information to the user  e.g. icon, chart, text document, form, spreadsheet, picture, table of numbers, equation, etc  Operations for manipulating data displayed as representations  e.g. gather data, generate report, retrieve alternatives rate alternatives, etc

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process ROMC User Interface Design Approach  Aids for a user’s Memory  e.g. symbolic link to data warehouse, triggers, alerts, user profile, data filters, user-established links or command sequences, help system  Aids for helping user to Control the system  e.g. standard conventions for user interaction (menus, guidelines; edit, delete, save operations

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Factors Related to the Quality of the User Interface  Learning curve – how fast does the user learn?  Operational recall – how long does it take the user to recall how to use the BIS?  Task-related time – how long is the typical task?  System versatility – does it support a variety of end user tasks?

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, The BIS Development Process Factors Related to the Quality of the User Interface  Error-trapping and support – what type of errors will users make?  Degree of system adaptability – will it adjust to individual use?  Management of cognitive overload – to what extent does the DSS reduce the need to remember things while using it?  Degree of personal engagement – to what extent is the BIS enjoyable to use?  Degree of guidance and structure – to what extent does the interface guide the user?

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, References  Mallach, E.G. (2003). Decision support and data warehouse systems, Irwin McGraw-Hill.  Marakas, G.M. (2002). Decision support systems in the 21st Century. 2nd Ed, Prentice Hall (or previous editions)  Turban, E. and Aronson, J. (2001) Decision Support and Intelligent Systems, 6th Ed, Prentice Hall (or previous editions)  Vitt, E., Luckevich, M. and Misner, S. (2002) Business Intelligence, Microsoft Corporation.

IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, Questions? School of Information Management and Systems, Monash University T1.28, T Block, Caulfield Campus