1 / 23

MANAGEMENT INVOLVEMENT IN DSS

Learn the crucial role of management in Decision Support Systems (DSS) development, from planning to utilization, for effective decision making. Explore stages, considerations, and guidelines for successful DSS implementation.

mwestphal
Download Presentation

MANAGEMENT INVOLVEMENT IN DSS

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. . MANAGEMENT INVOLVEMENT IN DSS Dr. Ir. Sudaryanto, MSc. sudaryanto@staff.gunadarma.ac.id

  2. Computer Generated Business Model • As generator of resources • As links in an economic chains • As society’s organ for the creation of wealth • As creatures an creators of material environment • Opportunities and threats

  3. Management Involvement in DSS • Purpose of DSS: • To support managerial decision making • Management involvement is crucial • Management involvement • From the inception to ongoing use • Role of management in DSS • Approval and administration • Development • Operation • Utilization of output

  4. Management Involvement in the Development of DSS (%) Stage Lower Middle Top • Idea • Information requirement • Building • Testing • Demonstration • Acceptance 0 0 11 11 11 0 61 78 72 72 78 72 61 61 6 6 28 27 Scale 1 to 5

  5. APPROVER AND ADMINISTRATOR OF DSS • Planning for DSS tend to be dezentralized • should be incorporated into corporate planning • Management involvement is crucial • DSS needs strong management support and involvement • Sense of ownership by manager • Need organizational unit to administer DSS

  6. APPROVER AND ADMINISTRATOR OF DSS • Basic planning for DSS development • Quick hit • Single DSS application without subsequent application • Staged development • First DSS is reused in developing the second • Complete • Complete DSS tools and generators is acquired • Organizational issue is decided

  7. Operation Of DSS • How much does management operate the DSS ? • How is the management decision approach maintained by the DSS ? • easy access of the intermediary to the manager • easy access of the intermediary to the DSS • fast turnaround time on DSS output

  8. Utilization Of DSS • Is use of DSS required ? • What level of management utilize the DSS? • Decision structure (structure / unstructure) • Source of information (internal / external) • Accuracy of information (deterministic/probabilistic) • Scope of decision (narrow/ broad) • How does the DSS support the phases of decision making?

  9. INFORMATION REQUIREMENT • Increasing EIS implementation • Many success story • EIS still viewed as a high risk system • 21 of 51 had failed • Need organizational unit to administer DSS

  10. Guidelines for Designing EIS Interfaces Dr. Ir. Sudaryanto, MSc. Ir. (IPB), MSc (AIT-Thailand), Dr. rer.pol. (Aachen-Germany)

  11. Development of EIS • Challenges in building EIS • Must be addressed on technical, organizational • and managerial issue • How to create EIS that easy to use • Attention on designing user interface

  12. Development of EIS • EIS user interface • How the user direct the operation the system • keyboard, mouse, touch screen, question/ • answer, commandlanguage, menu, voice) • How the output is given to the user • graphical, textual, tabular, color, paper, online • Due to the nature of the user • the system should be user friendly and • user intuitive • the system should flexible

  13. Design Guidelines • Designing an EIS: • Involve executives in design of the user interface • Setting standard for screen layout, format, color • Use the system should be intuitive • Use standard definition of terms • Design the main menu as a gateway to all • computer use • Design the system for ease of navigation • Strive to make response times as fast as possible • Expect preferences in user interface to change

  14. Design Guidelines The Considerations • Involve executives in design of the user interface • Challenge: limited experience working directly with • computer • Important to involve executive users in the process • Prototyping approach • A full screen interface with large buttons and icons • A multiple windows interface with pull-down menus • and dialog boxes • Multiple windows conform with interface design • standard

  15. Design Guidelines The Considerations • Most of commercial EIS run under windows • Must be tailored according to the “computer literacy” • of executive users and their preference • Executive involvement in screen content and design • Option: train in windows and its application or • design application without windows • Must compromise between different requirements

  16. Design Guidelines The Considerations • Setting standard • Layout Standards • graphical: visual presentation, • tabular: specific number • textual: explanation, assessment, action • Graph standard • type of graphics : bar chart, line graphs, • pie chart • avoid vertical wording

  17. Design Guidelines The Considerations • Standard • Color standards • different color indicates different meaning • Traffic light-pattern for comparison, indicator • Combination of layout, format and color • consistent look and feel • reduce misinterpretation and misunderstanding • Use of text • To make the information displayed more useful • Advance capabilities • Voice commentaries, animation

  18. Design Guidelines The Considerations • Using the System Should Be Intuitive • Ideally, executive can use without or with • minimum training • Operate by point- and click technology • Very rare use of command language • time consuming and • difficult to learn and remember • Must be customized for each executive

  19. Design Guidelines The Considerations • Using Standard Definition of Terms • Data dictionaries for transaction operations • Terms that are widely used should be • standardize • To avoid misunderstanding/ misinterpretation • sign-up by Lockheed • Dictionary of term used in the IES

  20. Design Guidelines The Considerations • Designing the Main Menu as a Gateway • As the “main door” to a variety of applications • for executive • e-mail, e-filing • external news, stock price • To avoid unnecessary procedures, difficulty • and inconvenience • Use of picks (menus, icons, buttons)

  21. Design Guidelines The Considerations • Designing the System for Ease of Navigation • Facilitate in moving from one to other application • Understanding the mental model of executive • The decision was business rather than technical • Navigation features: • one screen shows where the user in the system • a home key or pick to back to the main menu • a single menu to provide direct access to • different screens

  22. Design Guidelines The Considerations • Response Time as Fast as Possible • Monitor the response time of the system for each query • Trend to degrade (2.8 sec (1988) to 5.3 sec(1991) • despite increase use of more powerful computer and LAN • satisfaction with response time was extremely low • Response time will faster if the screens are static • Trade-off between timeliness of data on the screen • and response time • Executive usually tolerate a slow response to ad hoc queries • still acceptable when compared to “conventional” method • to gather the same information

  23. END

More Related