Titlebook: Knowledge Engineering; Unifying Knowledge B John Debenham Book 1998 Springer-Verlag Berlin Heidelberg 1998 Datenbankentwurf.behavior.classi

Cerumen

Non-unified design,that take this approach are called “non-unified” design methodologies. This presentation of the basic traditional approach is intended to enable a comparison to be made between those traditional design methodologies and the methodology presented in subsequent chapters here. The methodology presented

要求比…更好

Bumble

Dungeon

Schemas,nted in the same way as “items”. Complex items may be constructed by applying objects to simpler items. Items and objects are named triples consisting of a “name”, “semantics”, “value constraints” and “set constraints”. At any particular time an item is associated with a particular value set.

低三下四之人

說笑

Specification,t conceptual model consists of two separate parts: a model of the data and information things and a model of the knowledge things. In that methodology data, information and knowledge things are modelled and treated differently from each other.

表皮

Analysis,epresentation for conceptual modelling developed in Chaps. 3 and 4. The system analysis step makes extensive use of the i-schema format for describing items (Sect. 5.2), and the o-schema format for describing objects (Sect. 5.5). The first step in the unified design methodology is requirements speci

Parallel

Function,rmat for describing items, the o-schema format for describing objects, and the t-schema format for describing transactions. These formats are discussed in Sects. 5.2, 5.5 and 5.7 respectively. The first step in the unified design methodology is requirements specification discussed in Chap. 7. The se

vocation

Layout,t for describing items discussed in Sect. 5.2. The first step in the unified design methodology is requirements specification discussed in Chap. 7. The second step in the unified design methodology is system analysis discussed in Chap. 8. The third step in the unified design methodology is system fu

exhilaration

Case study,ments. At present there are several databases on the organisation’s computer. The problem is to design a “personnel management system”. In this system the general intention is “to advise the Personnel Manager on staff structure and salaries”. Further, suppose this required advice should be derived f