ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Decision Support Systems' Knowledge Bases

Updated on May 21, 2013

Once the concept and purpose of a DSS (decision support system) has been established, one must build a knowledge base (KB) from which to glean the information needed by applying processes.

Where to get this information? All over. People tend to run right to the Internet for the knowledge base, but the problem is that this is a single source (and one the decision maker could probably go to directly) – and the quality and veracity of the information is often doubtful.

I have used all kinds of information for a DSS, depending on its nature and purpose. One starts with the decision-maker’s normal avenue of information. But a good developer tries to find other sources as well.

Some sources of knowledge:

  1. personal interviews with involved people (this usually results in history information and information more valued in processes)
  2. manufacturers’ inventory databases
  3. real estate Multiple Listing Systems (MLS)
  4. libraries
  5. Chamber of Commerce
  6. Internet historical sites
  7. Human Resource Dept. records
  8. Accounting Dept. records
  9. Internal (company confidential) records
  10. Build-your-own-product WWW sites, as for cars, real estate and computers

In other words, find any sources related to the decision to be made. If a group of employees wants a DSS to help them decide where to have the Friday lunch each week, the developer would amass menus and prices from nearby eateries, and route to them, employee favorites (perhaps one of them never eats Mexican, or there has to be vegetarian meals available).

As the knowledge is amassed, it should all be pulled together into a single database, which could be a bunch of tables in Access or a collection of worksheets in Excel, set up in database format (row 1 is the field names, no blank columns or rows).

An example of a high-end DSS might be a LINK trainer – a flight simulator for pilots. While inside the trainer, the pilot sees the instrumentation and views through the window of an airplane. The pilot’s movements with the instruments (wheels, flaps, rudder, etc.) give input to the DSS, which in turn determines what would actually occur in real life, then simulates the same to the pilot. The pilot must then make a decision of what the next move would be.

One of the toughest problems is the Mars-vs-Venus problem – having the decision maker ask the questions so that the DSS can understand them, and having the DSS return answers in a way the decision maker can understand. For this reason, many DSSs are actually built for a particular person, or are so user-friendly that confusion is not a problem.

An example of a computer acquiring knowledge on its own – Web spiders. A Web spider is a program that is constantly running, wandering all over the World Wide Web, and collecting key words and URLs to add to a search engine database. If I remember right, AltaVista is a Web spider. A data mining company might design a spider to find particular subject matter. This is the concept behind copyright infringement monitors.

There are many more examples of this principle – collecting series of tips from newsletters into electronic documents; the use of a Microsoft Word Table of Contents to go directly to a page on the topic of interest, etc.

When I develop a database application for an organization, I also develop standard queries and reports. I then, usually over time and based on questions called into my office, develop queries the client can modify to handle ad hoc instances using the existing knowledge base.

Development of rules and modules takes a rather sophisticated user. Rules can be created in DBMSs (database management systems), spreadsheets, just about any application software. People are most familiar with rules in e-mail packages (“if the name of the sender is ‘big savings’, delete without opening”). Most rules are more familiarly known as macros; they can go further and can be modules (which are coded directly).

An example of a “problem processor” – a qualitative analysis system:

  1. Test for pH
  2. If pH is acid, start acidic run of tests
  3. If pH is alkaline, start lye tests
  4. If pH is acid, and there is a presence of sulfur…
  5. etc.

In this instance, the result of one test opens the avenue for the next test. By defining these decisions, choices and avenues, the developer can determine what information should be included in the knowledge base.


    0 of 8192 characters used
    Post Comment
    • Bonnie-Jean Rohne profile imageAUTHOR

      Bonnie-Jean Rohner 

      4 years ago from Williamson, New York

      I am flattered and encouraged by these responses. Thank you!

    • profile image


      4 years ago

      How could any of this be better stated? It co'ldnut.

    • profile image


      4 years ago

      Super exceitd to see more of this kind of stuff online.

    • Bonnie-Jean Rohne profile imageAUTHOR

      Bonnie-Jean Rohner 

      4 years ago from Williamson, New York

      That is a great compliment! Thank you!

    • profile image


      4 years ago

      Please teach the rest of these internet hoogalins how to write and research!


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)