Knowledge and Information in Nutrition Software Design

The intension of this paper is to point out that both Knowledge and Information can be persisted within ordinary database management systems. It is a well-known demand for codifying the knowledge versus of embedding it inside the business logic (the source code). The consequences are that knowledge can be extended, utilization of knowledge can be extended and that the application's evolution can be achieved, almost without programming. To achieve such a goal, database and system designers should distinguish what is information and what is knowledge for the system's domain of application. They should also foresee an abstract knowledge representation that will be able to hold the future knowledge in the domain. Our approach is based on an interesting domain of software technology, the nutrition software design.