Designing and Developing Decision Support Systems Chapter 4.

Slides:



Advertisements
Similar presentations
Information Systems Systems Development Chapter 6.
Advertisements

MIS 2000 Class 20 System Development Process Updated 2014.
CS487 Software Engineering Omar Aldawud
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved BUSINESS DRIVEN TECHNOLOGY Chapter Nineteen: Building Software to Support.
BUSINESS DRIVEN TECHNOLOGY
Systems Analysis and Design II
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Transforming Organizations
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas The primarily goal of a system is to create value for the organization. Many failed systems were abandoned.
Chapter 12 Systems Development Three common methods for MIS development: The systems development life cycle (SDLC) Prototyping End-user development Five.
Alternate Software Development Methodologies
Steps, Tools, and Techniques
Acquiring Information Systems and Applications
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
System Analysis and Design (SAD )
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Fundamentals of Information Systems, Second Edition
CHAPTER 19 Building Software.
Its Phases and Overview 1.  This document describes the (SDLC) for small to medium database application development efforts. o This chapter presents.
Acquiring Information Systems and Applications
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Transforming Organizations
Laudon & Laudon: Canadian Edition
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
SYSTEMS ANALYSIS FORM 4 Included in this topic: Information Systems Systems Analysts System Life Cycle (incl. Case Study) Documentation.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development.
Introduction to Systems Analysis and Design
CHAPTER 13 Acquiring Information Systems and Applications.
Systems Life Cycle A2 Module Heathcote Ch.38.
Formulating a Simulation Project Proposal Chapter3.
The Traditional System Development Life Cycle There are a number of important steps in the creation of a system, regardless of which approach you use.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Large Scale Systems Design G52LSS
KUFA UNIVERSITY Department of Computer Science. Fundamentals of Software Engineering Presented By Neamah Hassan Presented By Neamah Hassan.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Systems Development Life Cycle
11 ADM2372 Management Information Systems (MIS) Chapter 10 – Part I Systems Development Chapter 10 – Part I Systems Development.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Building Information Systems
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Information Systems Development
Introduction to Systems Analysis and Design
Systems Analysis & Design N106
Transforming Organizations
Information Systems Development
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

Designing and Developing Decision Support Systems Chapter 4

Chapter overview Understand the decision process What type of DSS will it be? Decide on what to focus Redesign Business process Determine requirements Make or buy the system? What development approach to use? How to manage the project?

Understand the decision process Diagnosis of current decision making process Collect data by interviewing, observation, or historical records Describe the decision process Specify a norm for how decisions SHOULD be made There can be limitations to the process May use an Audit plan Determine what type of DSS it is going to be Focus changes depending on what type of DSS it will be Redesign business processes to include new DSS

DSS Audit plan 1.Define the decisions. Identify a primary contact. 2.Examine the formal design of the decision process. 3.Examine the actual use of the decision process. 4.Assess performance of the actual decision process. 5.Reporting and recommendations.

Decide on what type of DSS will it be? Communication-driven DSS Data-driven DSS Document-driven DSS Knowledge-driven DSS Model-driven DSS. Will it be a combination of the types? Focus varies depending on the type of DSS

Focus and types of DSS Model driven DSS –Uses a statistical, financial, optimization, or simulation model. –Parameters are provided by the user Prior assumptions are stated (about distributions of data or relationships between variables) Diagnosis of decision making focuses on assumptions

Focus and types of DSS Data driven DSS emphasizes access to and manipulation of large amounts of structured data Mostly presents data in different formats Examples: Management reporting systems, Executive information systems, data warehousing systems Focus is on Critical Success Factors

Critical success factors Short list of factors that are critical to the success of the organization Find out by interviewing the executives Based on the CSF, determine what Key Performance Indicators must be included in the outputs –E.g. Customer satisfaction, market share Base the design and development process on these KPI’s

Redesign business process New decision process might require new business processes Based on the analysis recommend changes in the business process Tradeoff between what processes will the DSS support – existing or new ones Business process redesign is difficult for organizations

Requirements Document Describes what the software will do (not how it will do it) It is a written document An agreement between the developers and the intended users Must have for projects that take longer than 1 month, involve more than one developer and more than one set of users

Parts of a Requirements Document Part I – Application overview Objectives Business processes and how this application will be used User roles and responsibilities Interaction with other systems Terminology used

Parts of a Requirements Document Part II – Functional Requirements Functionality –Process requirements, and data requirements Performance Usability Concurrency requirements

Requirements document Document must be READ by people Update the document based on feedback Record what, who, when, why and how of feedback (Requirements Document Notes is based on s/is208/s02/ReqsDoc.pdf)

Feasibility study Is it worth going forward with the solution Financial feasibility (Benefits and costs) –Money, time, human resources Advantages and disadvantages Technical feasibility Anticipated impacts Timeframe and workplan Leads to Make or Buy decision

Choice of methods for development Systems Development Lifecycle (Waterfall model) Prototyping End-user development Outsourcing

SDLC Waterfall model Seven distinct steps 1.Requirements specification 2.Design 3.Construction (aka: implementation or coding) 4.Integration 5.Testing and debugging (aka: verification) 6.Installation 7.Maintenance

Waterfall model Requirements Design Development Implementation Verification Maintenance

Waterfall model Purely sequential Sign-off at each stage Little chance to revise requirements Suitable for large, mission critical applications Inability to revise requirements is a major problem Projects cancelled at later stages – huge losses

Prototyping Basic requirements, not detailed ‘Quick and dirty’ prototype Client reviews More requirements Refine prototype Client reviews Reduced costs than traditional method Rapid Application Development (RAD) tools help

Prototyping Requirements gathering Identify objectives, Functionality and performance requirements Develop Prototype User demo and testing ProductionDeployment

Spiral model Proposes to resolve the problem of run- away projects Feasibility evaluated more frequently Iterative method Multiple phases – each beginning with design goals and ends with review by clients

End user development User is also the developer Single user systems Fast, and to the user’s specifications User may not use proper development techniques / tools May have many errors in design User may need extensive support from IT people May not be systematic

Project Management Completing the project on time within budget On-time delivery of deliverables Project team –From many different areas –Users, project manager, staff, analysts, sponsors, specialists

Read “MIDS at Lockheed” case study for discussion in class