Chapter 14: Designing and Building Decision Support Systems

Slides:



Advertisements
Similar presentations
Chapter 13: The Systems Perspective of a DSS
Advertisements

© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Chapter 1 Assuming the Role of the Systems Analyst
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
© 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.
Chapter 1 Assuming the Role of the Systems Analyst
IMS3001 – BUSINESS INTELLIGENCE SYSTEMS – SEM 1, 2004 Identifying BI Opportunities and BIS Development Process Week 4 Dr. Jocelyn San Pedro School of Information.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
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.
DECISION SUPPORT SYSTEM DEVELOPMENT
1-1 © Prentice Hall, 2007 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
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.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Building and Implementing Decision Support Systems Week 6.
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.
Decision Support System Development By Dr.S.Sridhar,Ph.D., RACI(Paris),RZFM(Germany),RMR(USA),RIEEEProc. web-site :
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
Decision Support Systems Development
PRESENTAION TOPIC : DSS Development Presented TO: Sir Ahmad Tisman Pasha Presented BY : Uzma Noreen Roll # BSIT (6 th ) Department.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Software Prototyping Rapid software development to validate requirements.
Chapter 6 Decision Support System Development Turban, Aronson, and Liang Decision Support Systems and Intelligent Systems, Seventh Edition.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Principles of Information Security, Fourth Edition Chapter 1 Introduction to Information Security Part II.
Faculty Economics & Business EBS 2033 Systems Development Lecture 1 The Systems Development Environment Lecturer: Puan Asleena Helmi.
Chapter 6 Decision Support System Development
Chapter 1 The Systems Development Environment
Chapter 15 Finalizing Design Specifications
Appendix 2 Automated Tools for Systems Development
Software Prototyping.
Chapter 1 The Systems Development Environment
Chapter 1: Introduction to Systems Analysis and Design
Fundamentals of Information Systems, Sixth Edition
Fundamentals of Information Systems, Sixth Edition
Chapter 1 The Systems Development Environment
Introduction to System Analysis and Design
Decision Support System Development
Chapter 1 The Systems Development Environment
Object oriented system development life cycle
Chapter 1 The Systems Development Environment
Introduction to Software Engineering
Chapter 4 Automated Tools for Systems Development
Chapter 15 Finalizing Design Specifications
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 1: Introduction to Systems Analysis and Design
Chapter 6 Decision Support System Development
Chapter 1 The Systems Development Environment
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Chapter 14: Designing and Building Decision Support Systems Decision Support Systems in the 21st Century, 2nd Edition by George M. Marakas Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

14-1: Strategies for DSS Analysis and Design There are two common strategies for DSS development: Programming a customized DSS: either a general purpose language like C++ or a fourth-generation language like Delphi or Visual C11 can be used. This allows for development of special interfaces between the DSS and other applications. Employing a DSS generator: these range from spreadsheets such as Excel—perhaps with some add-ins—or a more sophisticated generator such as MicroStrategy’s DSS Architect. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

DSS Architect is Part of MicroStrategy’s 7i Suite Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

The DSS Analysis and Design Process Several approaches can be applied to the process of DSS development: System development life cycle –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” Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

The DSS Analysis and Design Process 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 DSS developer and the end users. The major complaint about SDL is its rigidity since requirements in a DSS can change rapidly. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Classical System Development Life Cycle Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

The DSS Analysis and Design Process Besides SDLC, there are two other approaches to DSS development: ROMC analysis – this approach asks the developer to understand representations (R), operations (O), memory aids (M), and controls (C). Representations include charts and tables. Functional category analysis – the developer identifies the specific functions necessary for a specific DSS from a broad list of available functions. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Functional Categories Selection – locating knowledge within the knowledge base for use as input Aggregation – creation or derivation of summary statistics, such as averages or totals Estimation – creation of model parameter estimates Simulation – creation of knowledge about expected outcomes or consequences of specific actions Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Functional Categories (cont.) Equalization – creation of knowledge regarding conditions necessary to maintain consistency Optimization – discovering what set of parameter values best meet a set of performance measures Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Generalized DSS Development Process Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

DSS Development Process For unstructured problems, we employ an alternate development strategy. There are seven basic activities in this process (not all may be performed in every project). Problem diagnosis – formal identification of the problem context Identification of objectives and resources – specific objectives must be described and available resources identified System analysis – three categories of requirements (functional, interface, and coordination) are established. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

DSS Development Process The remaining steps are: System design – the determination of components, structure, and platform System construction – an iterative prototyping approach, with small but constant refinement employed System implementation – where testing, evaluation, and deployment occurs Incremental adaptation – this final stage is a continual refinement of the activities of the earlier six stages. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

SDLC versus DSS Development Process SDLC evolved out of developers’ experience with computer-based information systems. The sequential and structured nature of the process is one of its primary strengths. In practice, a more iterative, bottom-up design approach might work better. For DSS development—as opposed to general IS development—problems tend to be less structured and a more evolutionary design approach is needed. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Prototyping An increasingly popular method of system development. For DSS development, it is usually of an iterative or evolutionary nature. Early stages are similar to the classic SDLC methodology until the first prototype is in place. At that point the methods diverge as the prototype undergoes almost constant, small changes. This process requires a significantly higher level of interaction between analyst and user. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Prototyping versus SDLC Throwaway prototypes are used for demo purposes only and then discarded. In DSS development, 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 DSS 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. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall 14-2: The DSS Developer At one extreme, the DSS developer is an experienced professional trained in computer science or MIS. At the other is a managerial decision maker who perceives a need for computer support. Although the novices may be experiencing a development effort for the first time, they possess a more intimate knowledge of what they want the DSS to accomplish. With the right tools, this may give them an advantage. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

The Necessary Skill Set Regardless of experience, the developer needs to possess key skills: Understanding the problem domain Understanding specific user requirements Understanding the available development technologies Access to appropriate knowledge Because all of these skills may not be available in a single person, a team may be required. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

End-User DSS Development 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. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Factors Influencing Risks and Outcome Characteristics of End-User-Developed Applications Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Advantages and Risks to End-User Development Assuming the end user has the required skills and tools, a major advantage is reduction of delivery time. Others are reduced time in gathering end-user specifications and fewer implementation problems. All these lead to lower cost of development as well as faster implementation. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Advantages and Risks to End-User Development 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. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

14-3: Tools for DSS Development There are a variety of tools available, roughly falling into three categories: Primary development tools – these include programming languages and database query mechanisms. DSS generators – at a higher level of technology, these possess integrated, diverse functionality, including decision modeling, sophisticated reporting, and database management. Specific DSS applications – for some problem types there may be a commercially available package that can be acquired and customized. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

DSS Development Tool Classification Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Development Tool Selection Criteria These criteria are particularly important in selection of a DSS generator : Data management functions Model management functions User interface capabilities Compatibility and degree of connectivity Available hardware platforms Cost Quality and availability of vendor support Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

14-4: DSS User Interface Issues The unique characteristics of a DSS user interface stem from the unique characteristics of typical end users: They play an organizational role based on something other than computing skills. They have latitude in exercising judgment. Their decisions have impact. They spend more time on tasks that do not need a computer than do. The unique nature of the decisions they make means their personal preferences must be accommodated. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

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 DSS? Task-related time – how long is the typical task? System versatility – does it support a variety of end user tasks? Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

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 DSS enjoyable to use? Degree of guidance and structure – to what extent does the interface guide the user? Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall

Prescribed Sequence for Interface Development Table 14-4 lists 12-steps for developing the end user interface. In brief, these are: Steps 1-3: determine the users, what they do and how they accomplish their tasks. Steps 4-6: develop a process diagram for these tasks and study how they interact. Steps 7-9: select a set of basic interface approaches and implement them. Steps 10-12: test, analyze, update, and trap for unexpected actions. Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall