SYST 542 Decision Support Systems Engineering

1y ago
5 Views
1 Downloads
1.12 MB
31 Pages
Last View : 23d ago
Last Download : 3m ago
Upload by : Jerry Bolanos
Transcription

Department of Systems Engineering and Operations ResearchSYST 542Decision Support SystemsEngineeringInstructor: Kathryn Blackmond LaskeyFall Semester, 2006Unit 1: Decision Makingand Decision SupportSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 1 -

Department of Systems Engineering and Operations ResearchLearning Objectives Understand course objectives &requirements Define a DSS Describe the history of DSS Name and define the major functionalcomponents of a DSS Describe the DSS lifecycle Describe the role of DSS in decisionmaking and the kinds of decisions mostamenable to DSSSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 2 -

Department of Systems Engineering and Operations ResearchCourse Objectives Introduce decision support systems Provide sound basis for:– Designing DSS– Managing DSS lifecycle process– Evaluating DSS Provide systems view of DSS developmentand integration into organizationSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 3 -

Department of Systems Engineering and Operations ResearchCourse Requirements Weekly discussion question (30% of grade)––––Asynchronous discussionIn-class discussion with assigned facilitatorWritten summary50% participation, 50% content Project (50% of grade)––––Small groupsDesign and implement DSS for problem of your choiceWritten reportOral presentation Paper review (15% of grade)– Read a paper from the literature– Write report on paper– Give oral presentation Lead discussion session (5% of grade)SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 4 -

Department of Systems Engineering and Operations ResearchA decision support system is acomputer-based system that supportsthe decision making process Assist decision makers in semi-structured tasksSupport not replace human judgmentHighly interactiveImprove effectiveness of human decision makers“A decision support system is a system under the control of oneor more decision makers that assists in the process of decisionmaking by providing an organized set of tools to impartstructure to portions of the decision-making situation andimprove the ultimate effectiveness of the decsion outcome”- MarakasSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 5 -

Department of Systems Engineering and Operations ResearchWhy DSS? Increasing complexity of decisions– Technology– Information:» “Data, data everywhere, and not the time to think!”– Number and complexity of options– Pace of change Increasing availability of computerized support– Inexpensive high-powered computing– Better software– More efficient software development process Increasing usability of computers– COTS tools– CustomizationComputer support for decision makingSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 6 -

Department of Systems Engineering and Operations ResearchRational Decision Making Rationality is the use of reason to make the bestchoice one can in the circumstances– What does “best” mean? Aspects of rationality (Kant)– Cognitive rationality: What to believe?– Practical rationality: What to do?– Evaluative rationality: What to value? GOOD-D mnemonic for rational decision making–––––Identify the goal to be achieved by the decisionIdentify the options available to the decision makerEvaluate the likely outcomes if each option is chosenDecide which option is best And then Do it! Decision makers need support with all GOOD-DelementsSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 7 -

Department of Systems Engineering and Operations ResearchDecision Making ProcessDefine andStructure theProblemGenerateOptionsGather, Collectand Fuse dOptionSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 8 -

Department of Systems Engineering and Operations ResearchTypes of Problems Structured– Repetitive– Standard solution methods exist– Complete automation may be feasible Unstructured––––One-timeNo standard solutionsRely on judgmentAutomation is usually infeasible Semi-structured– Some elements and/or phases of decision making processhave repetitive elementsDSS most useful for repetitive aspectsof semi-structured problemsSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 9 -

Department of Systems Engineering and Operations ResearchHistory of DSSOperations ResearchInformation Systems Management Science AI/Expert Systems1940’sOptimizationCognitive ScienceTransactionProcessing SystemsExpert SystemsSimulationMISKnowledgeRepresentation2000 Judgment &Decision MakingHuman/ComputerInteractionDecision Support SystemsGoal: Use best parts of IS, OR/MS, AI & cognitivescience to support more effective decision makingThanks to Andy LoerchSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 10 -

Department of Systems Engineering and Operations ResearchHistory: Business Computing World War II Era 1980-90’s– Introduction of computers - Military andscientific applications– Computers were for “numbercrunching” 1950’s– Business applications– Transaction processing systems:billing & payroll– Large mainframe computers 1960-70’s– Use of computers in management– Large volumes of data stored incomputers– Invention of relational databases andSQL– Management Information Systems born– Automation of paper-and-pencilprocesses for repeatable tasksSYST 542– Movement towardcustomization & flexibility– Movement toward new userinteraction metaphors– Increasing emphasis onintelligent systems 21st Century– Move from “stovepipes” tointeroperable systems– Distributed systems– Web servicesCopyright 2006, Kathryn Blackmond LaskeyUnit 1 - 11 -

Department of Systems Engineering and Operations ResearchHistory: Artificial Intelligence 1950’s 1980-90’s– Introduction of symboliccomputing– Newell and Simon: GeneralProblem Solver– Differentiation fromscientific computing» “AI is about symbols andnot numbers”Commercialization of AIExpert system shellsConnectionist movementMachine learningIncorporation of methodsfrom decision theory andoperations research 21st Century 1960-70’s– First expert systems» e.g., HEARSAY I (Speechrecognition); MYCIN(Medical diagnosis)– Knowledge representation e.g., frames, rules– Fuzzy logicSYST 542–––––– Agent-based systems– Distributed AI– Semantic Web & Intelligent“Web Bots”Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 12 -

Department of Systems Engineering and Operations ResearchHistory: OR/MS 1980-90’s World War II Era– Application of scientific method tooperational problems» e.g., efficient movement of troops &equipment 1950’s– OR/MS established as a discipline– Standard methods developed 1960-70’s––––Expansion of OR/MSBusiness applicationsGovernment: McNamara’s “whiz kids”Problems with appropriate use andacceptance» Limited computing power» Exclusion of factors not easilyquantified» Human factors issues in how OR/MSintegrated into organizationsSYST 542– Movement towardcustomization & flexibility– Attention to organizationaland human factors– Incorporation of methodsfrom artificial intelligence– Model bases and modelmanagement 21st Century– Embedded systems– Agile, reconfigurable supplychains– OR for everyone» Excel Solver» OR in middle school– OR in a Web Services worldCopyright 2006, Kathryn Blackmond LaskeyUnit 1 - 13 -

Department of Systems Engineering and Operations ResearchDecision Support Trends IT is increasingly pervasive Users are increasingly computer savvy Computer hardware is increasingly smallerand more powerful Systems are increasingly interconnected The Web is increasingly interwoven into allaspects of our lives Demand for usable, flexible, powerful decisionsupport will continue to grow Decision support will be embedded into a widevariety of consumer and business productsSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 14 -

Department of Systems Engineering and Operations ResearchDiscussion Give an example of some decision supportsystems you have encountered– What kind of decision was supported?– How did it work?– How helpful was it? What makes for successful decision support? What pitfalls should be avoided?SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 15 -

Department of Systems Engineering and Operations ResearchSome Terminology DBMS - System for storing and retrieving data andprocessing queries Data warehouse - Consolidated database, usuallygathered from multiple primary sources, organized andoptimized for reporting and analysis MIS - System to provide managers with summaries ofdecision-relevant information Expert system - computerized system that exhibitsexpert-like behavior in a given problem domain Decision aid - automated support to help users conformto some normative ideal of rational decision making DSS - provide automated support for any or all aspects ofthe decision making process EIS (Executive information system) - A kind of DSSspecialized to the needs of top executivesSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 16 -

Department of Systems Engineering and Operations ResearchTraditional EmphasisDataDialogueModelDBMS/DWMISESDADSS/EISSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 17 -

Department of Systems Engineering and Operations ResearchHumans and Computers:Complementary Strengths Human decision makers––––––Good at seeing patternsCan work with incomplete problem representationsExercise subtle judgment we do not know how to automateOften unaware of how they perform tasksPoor at integrating large numbers of cuesUnreliable and slow at tedious bookkeeping tasks andcomplex calculations Computers– Still inferior to humans at pattern recognition, messyunstructured problems– Good at integrating large numbers of features– Good at tedious bookkeeping– Rapid and accurate at complex calculationsSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 18 -

Department of Systems Engineering and Operations ResearchThe Challenge:Find and Exploit Synergy Computers provide cognitive tools– You would not build a house without appropriate tools– Complex decision problems require cognitive tools to assist with:» Collecting and organizing relevant information» Weighing multiple factors relevant to choice» Integrating large numbers of factors and combining to form overallevaluation» Presenting results so rationale for choice is clear» Analyzing multiple “what-if” scenarios Goal of DSS:– Use strengths of computer to augment strengths of human– Improve overall effectiveness of decision making processSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 19 -

Department of Systems Engineering and Operations ResearchDanger: The Worst of Both Worlds A poorly designed or improperly deployeddecision support system can be– Worse than leaving users unassisted– Worse than replacing the users with automated system Can you explain why? How do we keep this from happening?SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 20 -

Department of Systems Engineering and Operations ResearchAchieving the Promise Understand the stakeholders– Involve stakeholders early and often– Listen to feedback (especially negative!) Understand the task– Objectives to be achieved by decision– Current decision making process– Human and organizational factors Understand the technology– What parts of current process can be automated– COTS versus custom development– Integration of components and non-automated functions Understand the DSS development process– Co-evolution of process, DSS, human skill sets– Why change is resisted– Importance of good systems engineeringIterate! Evaluate! Improve!SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 21 -

Department of Systems Engineering and Operations ResearchDSS Characteristics Supported task– Structurability– Level (strategic / tactical /operational)– Decision process phase– Application area– Real-time / non real-time Supported user(s)– Type of job– Single user / multiple users» Distributed?» Interactive?– Sophistication withcomputers– Mode of interactionSYST 542 Level of support––––Display information?Suggest solutions?Select solutions?Modify suggestions withuser feedback? Information sources–––––User inputInternal databaseExternal databaseInternet (web / email)Sensor observationsCopyright 2006, Kathryn Blackmond LaskeyUnit 1 - 22 -

Department of Systems Engineering and Operations ResearchFunctionalComponentsof a DSSLibrary ntDialogueManagementUser & ExternalEnvironmentExternalData SourcesSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 23 -

Department of Systems Engineering and Operations ResearchSystem Life CycleIdentificationof NeedProduction perationMaintenanceDetailedConfigurationItem DesignRefinementTimeAnalyzeDesignFigure 1.1: Buede, 2000SYST 542BuildTestOperateSystems engineersplay major roleCopyright 2006, Kathryn Blackmond LaskeyUnit 1 - 24 -

Department of Systems Engineering and Operations ResearchLifecycle Models There are many lifecycle models– Can you name some and describe their properties? All have phases for:– Definition– Development– Deployment Lifecycle model for DSS development mustprovide for:– User involvement and evaluation throughout design &development– Iterative evaluation-centered redesignSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 25 -

Department of Systems Engineering and Operations ResearchStakeholder Involvement Most system errors can be traced to poorrequirements definition Problems caught early are much lessexpensive to fix Communication gaps are inevitable andshould be planned for– Users understand current process but can’t imagine howtechnology can change process– Developers understand technology but not user’s job– Each party thinks its expertise is most important Requirements definition must be iterative andevolutionary– “I can’t tell you what I want but I’ll know when I see it”SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 26 -

Department of Systems Engineering and Operations ResearchFocus on Constant Improvement Improvements happen because we learn fromexperience We can learn from experience only if:– We can tell whether we have succeeded or failed– We can tell why we have succeeded or failed Good engineering involves interplay between– Theory– Analysis– Reality testing Document your experience––––Identify problemsTrace causesIdentify lessons learnedIncorporate lessons learned into next project Many of the most difficult problems are interpersonal &organizational, not technicalSYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 27 -

Department of Systems Engineering and Operations ResearchCase Study:Planning A Program of Study The Problem:– Students at GMU must plan a program of study to meet degreerequirements– Existing PatriotWeb system provides degree evaluation tocheck whether requirements have been met but no planningfunction to help students plan courses that meet requirements– There are constraints on feasible schedules»»»»»Requirements (major and concentration)PrerequisitesWork and childcare constraintsCourse time conflictsWhen courses are offered The Users:– GMU students (graduate and undergraduate) DSS Objective:– Provide a decision support tool to help students plan a programof studySYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 28 -

Department of Systems Engineering and Operations ResearchCase Study Objectives Use program of study DSS as an illustrativeexample of concepts discussed in course Use program of study DSS as focus forasynchronous discussions Project groups may (if they choose) do aproject on some aspect of the case studySYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 29 -

Department of Systems Engineering and Operations ResearchIn Summary.SYST 542Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 30 -

Department of Systems Engineering and Operations ResearchReferencesSYST 542 Andriole, S., Handbook of Decision Support Systems, TAB Books, Inc., 1989. Buede,D. The Engineering Design of Systems: Models and Methods. New York:Wiley, 2000. Marakas, G. Decision Support Systems, Prentice-Hall, 2003. Sprague, R.H. and Carlson, E.D. Building Effective Decision Support Systems.Englewood Cliffs, NJ: Prentice Hall, 1982. Turban, E., Aronson, J.E., Liang, T.P. Decision Support Systems and IntelligentSystems. Prentice Hall, 2005.Copyright 2006, Kathryn Blackmond LaskeyUnit 1 - 31 -

A decision support system is a computer-based system that supports . Decision Support Systems AI/Expert Systems Expert Systems Knowledge Representation Human/Computer Interaction Judgment & Decision Making History of DSS Thanks to Andy Loerch Goal: Use best parts of IS, OR/MS, AI & cognitive

Related Documents:

48 Ports (1/10G uplinks) Unicast MAC addresses 8000 8000 8000 8000 IPv4 unicast direct routes 542 542 542 542 . (RoHS) including Directive 2011/65/EU . Router-switch.com 12 Model 8 Ports 16 Ports 24 Ports (1/10G uplinks) 48 Ports (1/10G uplinks) . CAB-CONSOLE-USB Console cable 6 ft. wit

Notions de base des syst mes r partis Probl mes de la construction d !applications r parties Mod les d!organisation d!applications r parties Patrons et canevas de base pour le mod le client-serveur Syst mes asynchrones, coordination, programmation par v nements Exemples de syst mes asynchrones Syst ms coposant.ntergicels coposants.

Wheel Loaders L 524 – L 542. 2 L 524 – L 542 L 524 Tipping load, articulated: 16,535 lb Bucket capacity: 2.7 yd³ .

100 West Main Street, Du Quoin, IL 62832 Phone 618-542-3423 fax 618-542-5061 sacredheartduquoin@gmail.com www.sacredheart-duquoin.org Immaculate Conception Church 533 W. 2nd North Street, Tamaroa, IL 62888 Phone 618-496-5867 or 542-3423 Rev. Carl Schrage SEPTEMBER 25, 2022

Du Quoin, IL 62832. Attn: Danette Mohr. 618/542-1509 or 618/542-1525 . FAX 618/542-1541. Printed by Authority of the State of Illinois #22-138/6-16/200 copies . 2 . . CONTROL OF THE GENERAL LIVESTOCK SUPERINTENDENT AND RESPECTIVE LIVESTOCK DEPARTMENT SUPERINTENDENT.

Ce cours de premi ere ann ee a pour objectif d’introduire les principaux concepts de l’Automatique : la notion de mod ele d’un syst eme, la structure de commande a contre-r eaction et le concept de stabilit e des syst emes dynamiques et le probl eme de stabilit e 5

The Tivoli Decision Support 2.1 User’s Guide describes the features and concepts behind the Tivoli Decision Support 2.1 product. Step-by-step procedures for using the Tivoli Decision Support Discovery Interface are also provided. Hereafter, the Tivoli Decision Support Discover Administrator is called the

carmelita lopez (01/09/18), maria villagomez (02/15 . josefina acevedo (11/10/97) production supervisor silvia lozano mozo (03/27/17). folder left to right: alfredo romero (02/27/12), production supervisor leo saucedo (01/15/07) customer sales representative customer sales representativesroute build - supervising left to right: josefina acevedo (11/10/97) john perry (12/04/17), leo saucedo .