Knowledge Engineering
Unifying Knowledge Base and Database Design
Published on 6. December 2012
XIV, 466 pages
978-3-642-72034-5 (ISBN)
Description
This monograph describes a methodology for the design of knowledge-based systems. A knowledge-based system contains knowledge as well as information and data. The information and data in such a system can be modelled and imple mented as a database. The knowledge in such a system can be implemented either in a programming language or in an expert systems shell. This methodology has two distinguishing features. First, it is "unified". A unified methodology repre sents the data, information and knowledge in a homogeneous manner, as well as the relationships between them. Second, the methodology builds a maintenance mechanism into the design. In knowledge engineering terms, the representation used by this methodology to model knowledge bases applies equally to databases. In database terms, the representation used by this methodology to model databases applies equally to the database rules. The unified methodology unifies the design of the "knowledge base compo nent" and the "database component". "Unification" is achieved in five senses.
More details
Other editions
Additional editions
Book
04/1998
1st Edition
Springer
€139.09
Article exhausted; check different version
Content
1 Fundamentals.- 1.1 Introduction.- 1.2 Formalisms.- 1.3 Data, information and knowledge.- 1.4 Knowledge-based systems.- 1.5 Summary.- 2 Non-unified design.- 2.1 Introduction.- 2.2 Non-unified methodology.- 2.3 Non-unified representation.- 2.4 Classification.- 2.5 Representation.- 2.6 Specification.- 2.7 Summary.- 3 Items.- 3.1 Introduction.- 3.2 Unified representation.- 3.3 Item structure.- 3.4 Data items.- 3.5 Information items.- 3.6 Knowledge items.- 3.7 Algebra of items.- 3.8 System items.- 3.9 Summary.- 4 Objects.- 4.1 Introduction.- 4.2 Limitations of items.- 4.3 Object structure.- 4.4 Data objects.- 4.5 Information objects.- 4.6 Knowledge objects.- 4.7 Algebra of objects.- 4.8 Inheritance.- 4.9 Summary.- 5 Schemas.- 5.1 Introduction.- 5.2 i-schemas.- 5.3 r-schemas.- 5.4 From r-schemas to i-schemas.- 5.5 o-schemas.- 5.6 o-schemas as operators.- 5.7 t-schemas.- 5.8 Summary.- 6 Normalisation.- 6.1 Introduction.- 6.2 Meaning of normal.- 6.3 Normalisation of items.- 6.4 Normalisation of objects.- 6.5 Classical normal forms.- 6.6 Non-classical normal forms.- 6.7 Normal forms for groups.- 6.8 Summary.- 7 Specification.- 7.1 Introduction.- 7.2 Methodology structure.- 7.3 Item behaviour.- 7.4 r-schema construction.- 7.5 Application representation.- 7.6 Requirements identification.- 7.7 Summary.- 8 Analysis.- 8.1 Introduction.- 8.2 Conceptual model.- 8.3 Basis.- 8.4 Conceptual view.- 8.5 c-coupling map.- 8.6 Constraints.- 8.7 Summary.- 9 Function.- 9.1 Introduction.- 9.2 Functional model.- 9.3 Analysis of transactions.- 9.4 Functional view.- 9.5 f-coupling map.- 9.6 Constraints.- 9.7 System function problem.- 9.8 Summary.- 10 Layout.- 10.1 Introduction.- 10.2 Internal model.- 10.3 Operational requirements.- 10.4 Internal view.- 10.5 i-coupling map.- 10.6 Constraints.- 10.7System layout problem.- 10.8 Summary.- 11 Maintenance.- 11.1 Introduction.- 11.2 Methodology.- 11.3 Set constraints.- 11.4 Strategy for maintenance.- 11.5 Significance of normalisation.- 11.6 System constraints.- 11.7 Management of maintenance.- 11.8 Summary.- 12 Case study.- 12.1 Introduction.- 12.2 Requirements specification (1).- 12.3 Analysis (1).- 12.4 Function (1).- 12.5 Second prime r-schema.- 12.6 Layout.- 12.7 Maintenance.- References.
