You have a privilege to create a quiz (QnA) related to this subject and obtain creativity score...
Rules and Knowledge-Driven Applications
Introduction to Knowledge-Driven Architecture and Knowledge-Driven Applications
Business and technical people don’t always understand each other. (That might be an understatement.)
While technology speaks XML and Web Services, business prefers natural language.
Translation from business to technology is called the development process.
“Cooking” an application involves several translation layers and teams.
We are still jumping through the same hoops after we have developed multiple services and promoted service-oriented architecture (SOA), after we’ve invested in the enterprise service bus, business modeling tools, and more…
Don’t take me wrong. I am for SOA. SOA saves budgets, and for bigger companies the savings are bigger.
But to fully benefit from SOA, we need to give subject matter experts the keys to Business Architecture.
This long shot will further the convergence of Business and Technology and will prevent the usual “lost in translation” and “too-late-for-market” effects.
The Knowledge-Driven Architecture, [1] describes a system, where business rules and scenarios directly drive applications.
Software Evolution had two major drivers.
From architecture perspectives it is driven by the Layers Design Pattern.
We started with spaghetti code, which included everything, from hardware support to data processing.
Then we added the Layer of Operating System, Data Layer and Application Layer.
And then we added Services Layer.
From the language point of view it was Semantic Software Evolution [2].
We started with numbers, went to Assembly, then to C/C++, and gradually moved to the languages that included even more of English. We are still progressing on the road to get closer to natural language, the best way of communications.
Was it clear so far?
The first step on this road is to replace the blocks of code most often changed by business with the rules.
Business can actively participate in writing rules. Rules syntax is much closer to natural language than Java, Python, Ruby on Rails or other programming languages.
There are more steps in enabling business partnerships and shifting the weight of IT efforts from infrastructure to knowledge engineering [3].
Will this shift endanger software engineering as a profession? Will we, current professionals, still have jobs?
Yes, we will move on to more intelligent applications, to Big Data Analytics, to cognitive computing, to the area we called artificial intelligence.
No one else can be a better partner for a business, which already started this move.
Our first step is to learn about Rules and Rule-based architecture and applications.
Assignments: 1. Answer QnA
2. Create 2 questions in the same manner and send to your instructor.
QnA template:
Question: ...question...
Answer: ... correct answer first ...
Answer: ... wrong answer ...
Answer: ... wrong answer ...
References:
1. Knowledge-Driven Architecture, US Patent US7774751, https://www.google.com/patents/US7774751
2. Software Semantic Evolution and the Next Step,
http://www.dataversity.net/software-semantic-evolution-and-the-next-step-part-1/
3. IT of the future, http://ITofTheFuture.com
2016-07-13_10:59 by Christian Nasr
I would be concerned to give IV insulin push if I do not know what the serum potassium is.
2016-07-16_12:43 by Ketan Dhatariya
In the UK we have a national guideline - free to download at http://www.diabetologists-abcd.org.uk/JBDS/Surgical_guideline_2015_summary_FINAL_amended_Mar_2016.pdf (all of our UK inpatient guidelines are free to download from http://www.diabetologists-abcd.org.uk/jbds/jbds.htm)
The surgical guideline says the following about using short acting insulin to correct pre and post operative hyperglycaemia. I am aware of some local audit data to show that this approach has led to far fewer procedures being cancelled / postponed.
Pre-operative hyperglycaemia: (blood glucose greater than 12mmol/L (216mg/dl) with blood ketones less than 3mmol/L or urine ketones less than +++)
Type 1 diabetes: give subcutaneous rapid acting analogue insulin (i.e. Novorapid®, Humalog® or Apidra®). Assume that 1 unit will drop the blood glucose by 3mmol/L. Recheck blood glucose 1 hour later to ensure it is falling. If surgery cannot be delayed commence a VRIII.
Type 2 diabetes: give 0.1 units/kg of subcutaneous rapid acting analogue insulin, and recheck blood glucose 1 hour later to ensure it is falling. If surgery cannot be delayed or the response is inadequate, commence a VRIII (variable rate intravenous insulin infusion).
Post-operative hyperglycaemia: (blood glucose greater than 12mmol/L with blood ketones less than 3mmol/L or urine ketones less than +++)
Type 1 diabetes: give subcutaneous rapid acting analogue insulin. Assume that 1 unit will drop blood glucose by 3mmol/L BUT wherever possible take advice from the patient about the amount of insulin
Type 2 diabetes: give 0.1 units/kg of subcutaneous rapid acting analogue insulin, and recheck blood glucose 1 hour normally required to correct a high blood glucose. Recheck the blood glucose 1 hour later later to ensure it is falling. Repeat the subcutaneous insulin after 2 hours if the blood glucose is still above12mmol/L. In this situation the insulin dose selected should take into account the response to the initial dose – consider doubling the dose if the response is inadequate. Repeat the blood glucose after another hour. If it is not falling consider introducing VRIII to ensure it is falling. Repeat the subcutaneous insulin dose after 2 hours if the blood glucose is still above 12mmol/L. In this situation the insulin dose selected should take into account the response to the initial dose – consider increasing the dose if the response is inadequate. Recheck the blood glucose after 1 hour. If it is not falling consider introducing VRIII.
