1 / 20

Decision Support System Development

Decision Support System Development. By Daniel Damaris NS. Learning Objectives. DSS user interface design and management. Understand the concepts of systems development. Learn PADI , the phases of SDLC. Describe prototyping. Understand which factors lead to DSS success or failure.

mrocky
Download Presentation

Decision Support System Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Decision Support System Development By Daniel Damaris NS

  2. Learning Objectives • DSS user interface design and management. • Understand the concepts of systems development. • Learn PADI, the phases of SDLC. • Describe prototyping. • Understand which factors lead to DSS success or failure. • Learn the importance of project management. • Describe the three technology levels of DSS. • Understand the learning process involved in DSS development. • DSS hardware, software, and technology Levels. • Decision support system construction methods

  3. The Traditional SDLC • A structured approach for managing the development of information systems. • Four phases (PADI) • Planning • Analysis • Design • Implementation • Cyclical • Can return to other phases

  4. DSS Project Management • Establish a time plan • Define scope of project and expected outcomes • Get support from senior management • Identify milestones and budgets based on realistic goals • Involve users (internal and external) • Document everything (all steps)

  5. Skill for Project Management • Technology and business knowledge • Judgment • Negotiation • Good communication • Organization

  6. Successful Project Management • Establish a baseline • Define scope of project • Manage change and scope creep • Get support from upper management • Establish timelines, milestones, and budgets based on realistic goals • Involve users • Document everything

  7. Project Failure • Lack of stakeholder involvement • Incomplete requirements • Scope creep • Unrealistic expectations • Project champion leaves • Lack of skill or expertise • Inadequate human resources • New technologies

  8. Evolutionary Disruptors • Development environment Organizational cultural factors Loss of top management support User and analyst attitude User experience Development team capability • Development process User education, support, involvement, training

  9. Alternative Development Methodologies • Rapid Application Development • Prototyping • Rapid development of portions of projects for user input and modification • Small working model or may become functional part of final system • Throwaway prototyping • Pilot test or simple development platforms

  10. Prototyping • Performing analysis, design, and implementation phasesconcurrently, and repeatedly • Users see system functionality quickly and provide feedback • Decision maker learns about problem • Problems are semi structured or unstructured • Managers and developers may not completely understandproblem

  11. Prototyping Development Process

  12. Throwaway Prototype Development • Analysis phase isthrough • Design prototypesassist in understanding thesystem

  13. DSS Prototyping • Short steps1. Planning2. Analysis3. Design4. Prototype • Immediate stakeholder feedback • Iterative1. In development of prototype2. Within the system in general3. Evaluation integral part

  14. DSS Prototyping (cont.) Advantages Disadvantages Changing requirements Poorly tested Security is an issue High uncertainty Reduction in quality Higher costs due to multiple productions • User and managementinvolvement in every phaseand iteration • Learning explicitly integratedand part of the design • Short intervals betweeniterations • Improved user understandingof system

  15. Change Management • Crucial to DSS • People resistant to change • Examine cause of change • May require organizational culture shift • Lewin-Schein change theory: three steps • Unfreeze • Create awareness of need for change • People support what they help create • Move • Develop new methods, attitudes and behaviors • Create and maintain momentum • Refreeze • Reinforce desired changes • Establish stable environment

  16. DSS Technology Levels • DSS primary tools Fundamental elements • Programming languages, graphics, editors, query systems • DSS generator (engine) Integrated software package for building specific DSS • Modeling, report generation, graphics, risk analysis • Specific DSS DSS application that accomplishes the work • DSS primary tools are used to construct integrated tools that are used to construct specific tools

  17. DSS Technology Tools

  18. DSS Tool Development Selection • Hardware • PCs to multiprocessor mainframes • Software • Involves multiple criteria (when selecting software) • Off the shelf software rapidly updated; many on market • Price changes are frequent • The desirability of staying with a few vendors • Technical, functional, end-user, and managerial issues are all considered

  19. DSS Developing Team • The systems are constructed by a team composed of users, DSS developers, technical support experts, and IS personnel. • Developing a DSS with a team is a complex, lengthy, costly process. • Since early 2000s, tools and generators have improved, smaller teams can handle complex DSS development.

  20. Thank You !

More Related