Define non-programmed decision. Give examples of non-programed decisions.

  Programmed decisions: A decision which is fairly structured or recurred with some frequency is called programmed decisions. Such decisions deal with repetitive and routine problems. If a particular situation occurs, managers will often, develop a routine procedure for handling it. Decision makers know in advance what decisions he/she has to take in particular set of situations. Generally middle level and operating level managers deal with such decision and have short-term impact. There is great deal of certainty in programmed decisions.

 Programmed decisions are those that are made using standard operating procedures or other well-defined methods. Hence, they are structured.

The following are the features of programmed decisions.

  • Decisions are made using standard operating procedures.
  • Deals with frequently occurring situations
  • Used to handle similar and frequent situations 
  • They are normally taken by the lower and middle level management.

 Non-Programmed decisions: These decisions are relatively unstructured and occur less frequently. Such decisions are required for unique problems and take more time, energy and resources into exploring the situation from all perspective. Intuition, experience, creativity and judgment are major factors in non-programmed decisions. Most of the decisions made by top level management involving organizational missions, goals, strategies, structure and exceptional issues require in this type of decision.

Non-programmed decisions are unstructured and do not occur very often. They are based on judgment, intuition, and creativity. The decisions regarding new facilities, new products, labor contracts, and legal issues decisions. are non-programmed

The following are the features of non-programmed decisions. 

  • They are made in unique and unstructured situations.
  • They do not take very often.

Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Discuss classification or taxonomy of virtualization at different levels.

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)