Business Intelligence Integration Joel Da Costa, Takudzwa Mabande, Richard Migwalla Antoine Bagula, Joseph Balikuddembe.

Slides:



Advertisements
Similar presentations
CONCEPTUAL WEB-BASED FRAMEWORK IN AN INTERACTIVE VIRTUAL ENVIRONMENT FOR DISTANCE LEARNING Amal Oraifige, Graham Oakes, Anthony Felton, David Heesom, Kevin.
Advertisements

3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
ITIL: Service Transition
ATTENTION This presentation breaks down the purchasing process into 6 steps, which are then detailed in the subsequent slides. While responding from either.
The System Development Life Cycle
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
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.
Lecture 13 Revision IMS Systems Analysis and Design.
Your Presentation Title Names of Team members Advisor name EE496A Midterm Presentation Fall, 2006.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Review 4 Chapters 8, 9, 10.
CSE Information Systems 1 IMS Information Systems 1 Revision.
8 Systems Analysis and Design in a Changing World, Fifth Edition.
Introduction to Systems Analysis and Design
The Systems Analysis Toolkit Project Management Tools.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
What is Business Analysis Planning & Monitoring?
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Continuation From Chapter From Chapter 1
Enabling Organization-Decision Making
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Software Testing Lifecycle Practice
Project Management: Still More Art Than Science Presented By Donald W. Larson AC Bronze, CL June 6, 2007.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Managing the development and purchase of information systems (Part 1)
Software Project Planning CS470. What is Planning? Phases of a project can be mostly predicted Planning is the process of estimating the time and resources.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 1.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Leaders in Asset Management Big Plans for your Property System? How to plan for a Property System Project Prepared by: Yudiann Carlo, CPPS
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Approaching a Problem Where do we start? How do we proceed?
Improving Student Engagement With Educational Material Deon Takpuie Reitumetse Chaka Project Proposal.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
The Systems Development Life Cycle
Example Template for Project Presentation
Chapter 1 Introduction to Databases. 1-2 Chapter Outline   Common uses of database systems   Meaning of basic terms   Database Applications  
Pre-Project Components
I Robot.
Project Scope Management Information Technology Project Management, Fifth Edition Note: some slides have been removed from the author’s original presentation.
Developing Business/IT Solutions Chapter 12 McGraw-Hill/IrwinCopyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
CSCI321 : IT2/1A : Physical Network Aid Mr Ee Kiam Keong Lim Willie, Chua Shui Li Tan Yong Meng Shirley Chin Noraizah Naftalia.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems Dr. Ken Cosh Lecture 10.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Smart Home Technologies
IS2210: Systems Analysis and Systems Design and Change Twitter:
SoftwareServant Pty Ltd 2009 SoftwareServant ® Using the Specification-Only Method.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
1 Software Testing and Quality Assurance Lecture 17 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
InLoox PM Product Presentation Slide 1 InLoox PM Product Presentation © InLoox, Inc. InLoox PM 8 for Outlook Product Presentation The Project.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
System Development Life Cycle (SDLC). Activities Common to Software Projects Planning : Principles Principle #1. Understand the scope of the project.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
ITIL: Service Transition
Data Center Infrastructure
Systems Analysis and Design
Guidance notes for Project Manager
Unit 5 – eProject – Starting to look at projects Unit 5
Presentation transcript:

Business Intelligence Integration Joel Da Costa, Takudzwa Mabande, Richard Migwalla Antoine Bagula, Joseph Balikuddembe

Business Intelligence What How Why

Current BI Trends Predictive Analysis Real-Time Monitoring In-Memory Processing Software as a Service

Problem Statement Previously ‘one size fits all’ Which are actually the most effective ? ▫Bayesian Belief Networks (GA) ▫Neural Networks (GA) ▫Artificial Immune Systems

Cases Profiling Customers Predictive Sales Forecasting

Aim See variance of results on same data Define strengths and weaknesses in BI technologies

Approach Brief Look into the rationale behind our proposed solution

Overview (Yet to add Diagram here…)

Input Previous Works ▫S. Mahfoud and G. Mani ▫P.-C. Chang Sanlam Specification ▫Sales ▫Income

Interface Simplified Interface ▫Graphical Display ▫Relevant information ▫Technical Data Hiding

System Approach 1: Bayesian Belief Networks Joel De Costa (Diagram here)

System Approach 2: Neural Networks (NN) Takudzwa Mabande

System Approach 3: Artificial Immune Systems (AIS) Richard Migwalla Overview ▫Abstraction of Human immune System (Diagram here)

Output: Sanlam Specification ▫Predicted sales ▫Customer Profile  Likely Purchase based on current income

Division Of Work Bayesian Networks Joel Neural Networks Takudzwa Artificial Immune System Richard Connecting To Database Joel Customer DB Interface Richard Sales DB Interface Takudzwa Sales & Customer Visualisation Takudzwa GUI Richard

Timeline

Risks RiskMatrix EvaluationAvoidanceMitigation 1. Loss of a project team member. D. Serious/ Low Probability Pressure to stay on the project as failure to do so means not graduating. Have sufficiently independent deliverable modules for each team member. 2. Delay in Delivery of test data. C. Disastrous/ Low Probability Pressure Sanlam to provide data as soon as possible. Create random test data or use alternative available data. 3. Scope creep (Plan too many tasks, Cannot complete tasks in time) E. Marginal/ Low Probability Project planned in detail with supervisor and department approval. Start with fundamental features first and leave other things to the end. 4. Data loss due to hardware failure, (External Factor) C. Serious/ Medium Probability Frequent backups of all progress on different machines or storage devices. Roll back to last backup. 5. Missing project deadlines C. Serious/ Medium Probability Constant reference to the project timeline and clear communication between project members Review and reassess deadlines; readjusting where necessary- as cost-effectively as possible. 6. Misunderstanding User requirements. (Resultant of miscommunication/ ambiguity in user-team interaction) D. Serious/ Low Probability Constant communication with Sanlam and providing them with project plan and design in order to detect flaws. Iterations through development so that inconsistencies can be detected early.

Resources Lab PC’s Access to Sanlam Database Java Development Enviroment Project team

Anticipated Outcomes We will create a package that will: Read in data from the Sanlam database. Use different machine learning techniques to profile customers and forecast sales. Compare the accuracy of the different techniques using actual data. Identify the best technique for use in each particular scenario.

Key Success Factors Identifying the best technique for Customer Profiling Identifying the best technique for Sales Forecasting All techniques performing approximately the same amount of work (i.e. same data, about the same time, relatively the same complexity)