Answers.Body: <p>No, I don't think there's any reason to say that - in general - CRUD apps "are" expert systems. A given CRUD app <em>could</em> incorporate an expert system, but by and large CRUD apps are considered among the "dumbest" of applications exactly because they don't feature much intelligence... you can just Create, Read, Update and Delete entities.  From what I've seen, the closest you get to seeing anything like an expert system in a typical enterprise CRUD app is some validation / business rules logic built using something like <a href="http://www.jboss.org/drools" rel="nofollow noreferrer">Drools</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-11T05:51:09.103Z
Answers.LastActivityDate: 2016-12-11T05:51:09.103Z
Answers.UserDisplayName: mindcrime
Answers.Body: <p>CRUD applications today can't be considered expert systems.</p>
  <p>However, even the so-called expert systems, which are currently developed, are implemented using normal programming statements, but what is important is the architecture that is built.</p>
  <p>Current expert systems use only if-then types of rules, which produce data results that can be used as inputs to other rules, and an engine to step through them. This is quite limited, and it is greatly fragile.</p>
  <p>What I do consider as expert systems are ones that can reason about variables (logical and numerical ones) and can use the limited formation of hypotheses and attempt a proof of them.</p>
  <p>But, unfortunately, even what you might analyze and describe as an expert system is not really able to form models by itself, so it can easily run up against knowledge boundaries beyond which it cannot go.</p>
  <p>Therefore, CRUD web applications today are not a modern version of the expert systems.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-08-17T14:48:56.370Z
Answers.LastActivityDate: 2020-12-31T20:46:26.490Z
Answers.LastEditDate: 2020-12-31T20:46:26.490Z
Answers.UserDisplayName: quintumnia
Answers.Body: <p>What you're describing is a CRUD app <em>plus</em> a <a href="https://en.wikipedia.org/wiki/Recommender_system" rel="nofollow noreferrer">recommender system</a>. A CRUD app on its own doesn't perform any similarity ranking or recommendation functions. Stack Exchange is doing at least keyword matching and possibly semantic parsing as a feature layer on top of the basic CRUD functions.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-31T19:24:16.097Z
Answers.LastActivityDate: 2020-12-31T19:24:16.097Z
Answers.UserDisplayName: Adam Acosta
Answers.Body: <p>The key feature of an expert system is that the knowledge base is structured to be traversed by the inference engine.  Web sites like Stack Exchange don't really use an inference engine; they do full-text searches on minimally-structured data.  A real inference engine would be able to answer novel queries by putting together answers to existing questions; Stack Exchange sites can't even tell if a question is duplicate without human confirmation.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-11T05:24:25.783Z
Answers.LastActivityDate: 2016-12-11T05:24:25.783Z
Answers.UserDisplayName: antlersoft
Body: <p><a href="https://en.wikipedia.org/wiki/Expert_system" rel="nofollow noreferrer">From Wikipedia</a>, citations omitted:</p>
  <blockquote>
  <p>In artificial intelligence, an expert system is a computer system that emulates the decision-making ability of a human expert. Expert systems are designed to solve complex problems by reasoning about knowledge, represented mainly as if–then rules rather than through conventional procedural code. The first expert systems were created in the 1970s and then proliferated in the 1980s. Expert systems were among the first truly successful forms of artificial intelligence (AI) software.</p>
  <p>An expert system is divided into two subsystems: the inference engine and the knowledge base. The knowledge base represents facts and rules. The inference engine applies the rules to the known facts to deduce new facts. Inference engines can also include explanation and debugging abilities.</p>
  </blockquote>
  <p>CRUD webapps (websites that allows users to <strong>Create</strong> new entries in a database, <strong>Read</strong> existing entries in a database, <strong>Update</strong> entries within the database, and <strong>Delete</strong> entries from a database) are very common on the Internet. It is a vast field, encompassing both small-scale blogs to large websites such as StackExchange. The biggest commonality with all these CRUD apps is that they have a knowledge base that users can easily add and edit.</p>
  <p>CRUD webapps, however, use the knowledge base in many, myriad and complex ways. As I am typing this question on StackOverflow, I see two lists of questions - <strong>Questions that may already have your answer</strong> and <strong>Similar Questions</strong>. These questions are obviously inspired by the content that I am typing in (title and question), and are pulling from previous questions that were posted on StackExchange. On the site itself, I can filter by questions based on tags, while finding new questions using StackExchange's own full-text search engine. StackExchange is a large company, but even small blogs also provide content recommendations, filtration, and full-text searching. You can imagine even more examples of hard-coded logic within a CRUD webapp that can be used to automate the extraction of valuable information from a knowledge base.</p>
  <p>If we have a knowledge base that users can change, and we have an inference engine that is able to use the knowledge base to generate interesting results...is that enough to classify a system as being an &quot;expert system&quot;? Or is there a fundamental difference between the expert systems and the CRUD webapps?</p>
  <p>(This question could be very useful since if CRUD webapps are acting like &quot;expert systems&quot;, then studying the best practices within &quot;expert systems&quot; can help improve user experience.)</p>
  
Tags: <definitions><expert-systems>
Title: Are CRUD webapps today the modern version of the "expert system"?
UserDisplayName: Left SE On 10_6_19
ThreadText: # Are CRUD webapps today the modern version of the "expert system"?
  
  (Asked by: username_0 on 2016-12-11)
  
  [From Wikipedia](https://en.wikipedia.org/wiki/Expert_system), citations omitted:
  
  > In artificial intelligence, an expert system is a computer system that emulates the decision-making ability of a human expert. Expert systems are designed to solve complex problems by reasoning about knowledge, represented mainly as if–then rules rather than through conventional procedural code. The first expert systems were created in the 1970s and then proliferated in the 1980s. Expert systems were among the first truly successful forms of artificial intelligence (AI) software.
  >
  > An expert system is divided into two subsystems: the inference engine and the knowledge base. The knowledge base represents facts and rules. The inference engine applies the rules to the known facts to deduce new facts. Inference engines can also include explanation and debugging abilities.
  
  CRUD webapps (websites that allows users to **Create** new entries in a database, **Read** existing entries in a database, **Update** entries within the database, and **Delete** entries from a database) are very common on the Internet. It is a vast field, encompassing both small-scale blogs to large websites such as StackExchange. The biggest commonality with all these CRUD apps is that they have a knowledge base that users can easily add and edit.
  
  CRUD webapps, however, use the knowledge base in many, myriad and complex ways. As I am typing this question on StackOverflow, I see two lists of questions - **Questions that may already have your answer** and **Similar Questions**. These questions are obviously inspired by the content that I am typing in (title and question), and are pulling from previous questions that were posted on StackExchange. On the site itself, I can filter by questions based on tags, while finding new questions using StackExchange's own full-text search engine. StackExchange is a large company, but even small blogs also provide content recommendations, filtration, and full-text searching. You can imagine even more examples of hard-coded logic within a CRUD webapp that can be used to automate the extraction of valuable information from a knowledge base.
  
  If we have a knowledge base that users can change, and we have an inference engine that is able to use the knowledge base to generate interesting results...is that enough to classify a system as being an "expert system"? Or is there a fundamental difference between the expert systems and the CRUD webapps?
  
  (This question could be very useful since if CRUD webapps are acting like "expert systems", then studying the best practices within "expert systems" can help improve user experience.)
  
  **Tags:** definitions, expert-systems
  
  ---
  
  ## 4 answers
  
  ### Answer by username_4 on 2016-12-11. Score: 5 | Accepted answer
  
  The key feature of an expert system is that the knowledge base is structured to be traversed by the inference engine. Web sites like Stack Exchange don't really use an inference engine; they do full-text searches on minimally-structured data. A real inference engine would be able to answer novel queries by putting together answers to existing questions; Stack Exchange sites can't even tell if a question is duplicate without human confirmation.
  
  
  ---
  
  ### Answer by username_1 on 2016-12-11. Score: 4
  
  No, I don't think there's any reason to say that - in general - CRUD apps "are" expert systems. A given CRUD app *could* incorporate an expert system, but by and large CRUD apps are considered among the "dumbest" of applications exactly because they don't feature much intelligence... you can just Create, Read, Update and Delete entities. From what I've seen, the closest you get to seeing anything like an expert system in a typical enterprise CRUD app is some validation / business rules logic built using something like [Drools](http://www.jboss.org/drools)
  
  
  ---
  
  ### Answer by username_2 on 2019-08-17. Score: 1
  
  CRUD applications today can't be considered expert systems.
  
  However, even the so-called expert systems, which are currently developed, are implemented using normal programming statements, but what is important is the architecture that is built.
  
  Current expert systems use only if-then types of rules, which produce data results that can be used as inputs to other rules, and an engine to step through them. This is quite limited, and it is greatly fragile.
  
  What I do consider as expert systems are ones that can reason about variables (logical and numerical ones) and can use the limited formation of hypotheses and attempt a proof of them.
  
  But, unfortunately, even what you might analyze and describe as an expert system is not really able to form models by itself, so it can easily run up against knowledge boundaries beyond which it cannot go.
  
  Therefore, CRUD web applications today are not a modern version of the expert systems.
  
  
  ---
  
  ### Answer by username_3 on 2020-12-31. Score: 0
  
  What you're describing is a CRUD app *plus* a [recommender system](https://en.wikipedia.org/wiki/Recommender_system). A CRUD app on its own doesn't perform any similarity ranking or recommendation functions. Stack Exchange is doing at least keyword matching and possibly semantic parsing as a feature layer on top of the basic CRUD functions.
  
  
  ---
  
  