T.J. Teorey, D. Yang and J.P. Fry. A Logical Design Methodology for relational databases using the extended entity-relationship Model. ACM Computing Surveys, 18(2):197-222 (1986).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....database. A third group of tools requires a fixed database schema to work with. These tools often store all the pages of a Web site in the database, not only the actual content and cannot be viewed as general purpose database management tools. For WebCUS, we chose the approach to define the EER[4] of the database to be managed in an external XML file that is the central source of information about the database schema. 2.2 Layout Independence The ability to customize the graphical appearance of WebCUS depending on an organization s corporate identity and the input devices being used was ....

T. Teorey, D. Yang, and J. Fry. A logical Design Methodology for Relational Databases Using the Extended Entityrelationship Model. ACM Computing Surveys, 18(2):197-- 222, 1986.

....technique used in Pegasus to import relational schemas. The importance of translating the schemas of imported external databases to a common data model is discussed in [23] which gives a survey of federated database systems. Descriptions of previous work on data model translation can be found in [10, 12, 13, 14, 16, 17, 18, 20, 21, 22, 24, 25, 26, 27]. Our contribution is a demonstration that schema translations to a semantically rich data model from the relational model can be automatic, and derived from the semantic constructs in the relational model. The rest of the paper is organized as follows. In section 2, we describe in detail the ....

T. Teorey, D. Yang, and J. Fry, "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model", ACM Comp. Surv. 18:2, June 1986, pp. 197-222.

....and its successor HDM2 [63] Unlike HDM which is a data model in its own right, RMDM is embedded in a methodology that shows how to create and use the data model. RMM method defines seven phases starting with the definition of the entity relationship (ER) design. The well documented E R approach [139] was chosen since it is easy to use and already commonly applied in database design. Just as for databases, the diagram defines entities representing the actual information items that have attributes fields holding the content. Also derived from database design, one to many and many to many ....

Toby J. Teorey, D. Yang, and J. Fry. A logical Design Methodology for Relational Databases Using the Extended Entity-relationship Model. ACM Computing Surveys, 18(2):197--222, 1986.

....schema, the layout and access control description is necessary. In WebCUS, the database schema is represented in an XML file. This XML information uses a special syntax to describe the tables, columns, rows and relations between tables in the database. We use the Extended Entity Relationship (EER)[8] SYSTEM . resources myeer.dtd alias= Id type= key alias= Book Title type= text alias= Author type= text alias= Publisher type= text alias= ISBN type= text Figure 1: EER description in XML methodology in our projects for modeling the database information. ....

T. Teorey, D. Yang, and J. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197--222, 1986. 4

....and associative abstractions. Some modeling schemes also include an aggregation relationship which represents the situation where one entity is composed of instances of other entities. A number of graphical representations have been used for ER and ERA models. Examples include: Chen, 1977 #114] [Teorey, 1986 #520] Blaha, 1988 #62] and [Shlaer, 1988 #475] 4.1.2 Class Diagrams Class diagrams are used by most object oriented methods to show the object classes that make up an application domain and the relationships among them. Class diagrams are essentially extended ERA diagrams that include ....

T. J. Teorey, D. Yang, and J. P. Fry, "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model," ACM Computing Surveys, vol. 18, no. 2, pp. 197-222, 1986.

....in the alternative output formats of light weight HTML and PDF. 5 Related Work The Relational Management Methodology (RMM) and the Object Oriented Hypermedia Design Methodology (OOHDM) are two well known Web site development methodologies. RMM [17] is based on the Entity Relationship (ER) model [18] and focuses on database backed Web development. A severe restric tion of the original RMM is that the mapping of contents from several entities onto a single Web page was not possible. The extended RMM [19] explicitly (a) b) Fig. 4. Additional output formats (a) light weight HTML for ....

Teorey, T., Yang, D., Fry, J.: A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys 18 (1986) pp. 197-222.

....of lower layer relations. 2. A set of generalization paths, each of which shows how a higher layer relation is generalized from one or a set of lower layer relations. Similar to many extended relational databases, a route map can be represented by an extended E R (entity relationship) diagram [24], in which the entities and relationships at layer 0 (the orig inal database) can be represented in a conventional E R diagram [19] whereas generalization is represented by a double line arrow pointed from the generalizing entity (or relationship) to the generalized entity (or relationship) For ....

T. J. Teorey, D. Yang, and J. P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Cornput. Surv., 18:197-222, 1986.

....the regularities of the data at a high level. KDT, a set of knowledge discovery tools, performs knowledge discovery efficiently in databases, when necessary. The first component, Schema, follows from a deductive entity relationship model [13] which extends an entity relationship model [5, 28] to incorporate rules, integrity con straints and complex data objects for deductive databases. Based on this model, a database schema consists of a set of entities and relationships, each of which (including their attributes) could be defined by physical data (i.e. data relations) virtual data ....

T. J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Cornput. Surv., 18:197 222, 1986.

....ER diagram is created, one can convert it to a relational database schema based on the set of standard translation rules that are available in most database textbooks [10, 11] The ER model was introduced as a tool for data modeling by P. Chen in 1976 [ 1 ] Together with its different variants [3, 4], it has been used successfully in data modeling and database design in more than two decades. Based on the notion of ER modeling which was generalized to conceptual modeling afterwards, an international conference was initiated in 1979 and has been held annually [5] thereafter. Several commercial ....

T. Teorey, D. Yang, and J. Fry, "A logical design methodology for relational databases using the extended entity-relationship model," ACM Computing Surveys, 18:197--222, 1986.

....hand held devices and (b) printable PDF for the same content. 5 Related Work The Relational Management Methodology (RMM) and the Object Oriented Hypermedia Design Methodology (OOHDM) are two well known Web site development methodologies. RMM [17] is based on the Entity Relationship (ER) model [18] and focuses on database backed Web development. A severe restriction of the original RMM is that the mapping of contents from several entities onto a single Web page was not possible. The extended RMM [19] explicitly introduces the separation of content, layout and application logic (storage ....

Teorey, T., Yang, D., Fry, J.: A logical Design Methodology for Relational Databases Using the Extended Entity-relationship Model. ACM Computing Surveys 18 (1986) pp. 197-222.

....richer (conceptual semantic data model, later object oriented) data model than the one provided by the DBMS was used for modeling the application data. The resulting data model was (sometimes automatically) transformed into the executable model on top of which the application was programmed (e.g. [13] [2] Thus, the overall intention was to provide a modeling approach close enough to easily model the phenomenon of the application world and being at the same time executable. In the nineties, the focus moved to process instead of data integration. Here, the approaches between modeling and ....

....integration issues (allowing for more finegrain stages in support and the integration of webcontent management systems and legacy systems) In regard to user interface design: improved facility for comparing a standard with an individual serviceflow and extended support for defining deviations. [13] ....

Teorey, T.J., Yang, D., Fry, J.P.: A logical design methodology for relational databases using the extended entity relationship model. ACM Computing Surveys, 18(2): 197-222, June 1986.

....[27] in our examples. QUICK uses knowledge extracted from the conceptual model to automate query generation, effectively eliminating the requirement that users be intimately familiar with the databases from which they retrieve data. QUICK relies on an extended entity relationship (EER) 4] 10] 22][37] model notation to conceptually describe a database. The extensions are drawn from semantic data modeling, object oriented, and knowledge representation approaches [14] 26] to extend the expressive power of the ER model. QUICK supports intuitive highlevel user requests similar to the request ....

T. J. Teorey, D. Yang, and J. P. Fry, "A logical design methodology for relational databases using the extended entity-relationship model", ACM Computing Surveys 18(2) (1986) 197-222.

....among their members should exist so that the dictionary of system data can paralelly be constructed and this is the only way to check the strenght among models. 2.7. 1 Data Model The student will be based on the extended entity relatioship diagrams technique acording to Chen [2] and Teorey [13] in order to create this model. The generated documentation should contain: erx diagram, relational model and database squema. Together with the diagram, some forms will be designed with the following content for every one of the elements which take place: entity [name reference definition ....

Teorey, T.J., Yang, D., Fry, J.P. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. Computer Surveys, vol 18 n 2, 1986.

....an entity relationship diagram (ERD) into 4th normal form (4NF) Ling (1985a) discusses the idea of normalization of ERD s, and further investigates the relationship between ERD s, multivalued dependencies and join dependencies (Ling, 1985b) Jajodia et al. 1983) discuss the equivalence of ERD s. Teorey et al. 1986) states that a ternary relationship type should be used only when the association among three entity types cannot be represented by several binary relationships, but does not discuss specifically when this can occur, or if several binary relationships have an equivalent informational capacity. ....

Teorey, T.J., Yang, D., Fry, J.P. (1986) A logical design methodology for relational databases using the extended entity-relationship model. Computing Surveys, 18:12, June, pp. 197 -- 222.

....and the research literature. The driving force in the development of design techniques and methodologies from the very beginnings of entity relationship modeling and normalization were the reduction of data redundancy. Of less fame is the concept of a redundant relationship. Teorey, et al., [TEOR86] offers a short definition by stating that relationships that represent the same concept are considered to be redundant. They indicated that redundant relationships should be eliminated because they are likely to result in unnormalized relations when transforming the model in relational ....

....redundant. They indicated that redundant relationships should be eliminated because they are likely to result in unnormalized relations when transforming the model in relational schemas . They use an example of a transitive dependency to make their argument. Figure 1 is a reproduction from the [TEOR86] article. STUDENT CLUB SCHOOL ATTENDS LOCATED IN BELONGS TO FIGURE 1: Transitive relationships (Figure 5 in the [TEOR86] In this example the minimum cardinality (Participation) is mandatory for each relationship and the maximum cardinality is Many To One between STUDENT and CLUB, between ....

[Article contains additional citation context not shown here]

Teorey, Toby J., Dongqing Yang, and James P. Fry, 1986. "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model", Computing Surveys, 18(2)197222, June, 1986.

....level is independent of the ones in the other two. Conceptual data models provide concepts that are close to the way users perceive data. They provide a high level abstraction of the real world entities. The Entity Relationship (ER) model proposed by Chen [Che76] along with its various extensions [SS77, TYF86, Gog94] is the most widely used conceptual data model. Physical data models provide concepts that describe the low level details of how data is stored in the computer. Physical data models are usually invisible to database users. It is the database system designer s job to define the physical data ....

....2 D satellite image, aggregation results in a single relation, say next, by collapsing north, south, east, and west (see Figure 1(b) This simply reduces the second issue into the first issue above. Various other extensions to the ER model have been proposed to alleviate this inherent limitation [TYF86, Tha90, Gog94]. None of them succeeds in providing an effective mechanism to describe complex inter instance relationships in general. In summary, ER diagrams can not represent the regularities, constraints, or patterns of the relationships among instances of an entity. For example, from the ER schema, it is ....

T. J. Teorey, D. Yang, and J. P. Fry. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. ACM Computing Surveys, 18(2), June 1986.

....where the conceptual model is constructed directly from the requirements before creating the logical model. More recently, the E R approach has been extended to include O O features. The Extended E R (EER) model includes many constructs of O O modeling, including generalization and aggregation [7]. 2.1 Database Design We first address conceptual modeling for database design. Database design is an aspect of software engineering that involves defining the structure of the database in an application. As shown in Figure 1(a) in database design, conceptual modeling is one of many tasks [12] ....

....of the problem domain, then decomposing it into an E R model, and finally, transforming the ER model into candidate relations. The EER methodology produces database designs that are not only accurate representations of reality, but is flexible enough to accommodate future processing requirements [7]. The EER model has many advantages for database design, including: 1) Maps well to relational databases, 2) Provides a visual depiction of the model that is easy to understand, 3) Can be readily used as a design plan. Chen s original E R model included three fundamental constructs, which are also ....

[Article contains additional citation context not shown here]

T. J. Teory, D. Yang, J. P. Fry, "A Logical Design Methodology for Relational Databases Using the Entity-Relationship Model", ACM Computing Surveys, Vol. 18, No. 2, June 1986.

.... strict inheritance . Namely, a class definition can only add new properties or restrict the value of the property inherited from a superclass. Now the question is how to indicate to the system which of the two options gives the desired semantics for Car factory. Conventional data models, such as [1, 3, 13, 15, 27, 28, 29] provide specialization mechanisms that support only one of the two options (see also Section 7) We believe that both options should be supported, as the appropriate option depends on the desired class semantics. Moreover, we believe that an a priori choice of one or the other option can lead to ....

....p 0 and C be a subclass of C 0 . In extension data models, the only way that p can be related to p 0 through the Isa or Risa relation is by expressing their relation using a constraint language (outside the inheritance mechanism) Examples of extension data models are the extended ER model [29], the extended UI model [27] y and the Living in a Lattice data model [15] In refinement data models, on the other hand, properties inherited by a subclass may be refined by restricting the value of the original property. If a property p of a class C refines a property p 0 of a superclass ....

T.J. Teorey, D. Yang and J.P. Fry. A Logical Design Methodology for relational databases using the extended entity-relationship Model. ACM Computing Surveys, 18(2):197-222 (1986).

....study the complexity of the underlying computational problems. In the world of databases, Entity Relationship (ER) models play a similar role of high level design devices that classes play in the world of class based object oriented languages. 1 In particular, Extended ER (EER) models defined in [TYF86] incorporate the concepts of subset and generalization hierarchies. Our work on class abstraction can be carried on to the realm of EER models and the companion Logical Relational Design Methodology (LRDM) if we can find a mapping between our class notation and the EER notation. With such a ....

....in object oriented design given in Fig. 5. In database terminology, a class dictionary graph is an object base schema with only a minimal set of integrity constraints. Class dictionary graphs can be viewed as an adaptation of extended entity relationship diagrams for object oriented design [TYF86]. Definition 1 A class dictionary graph DG is a directed graph DG = V; EC;EA) with vertices V . is a finite set of labels. There are two defining relations EC;EA. EC is a ternary relation on V Theta V Theta , called the (labeled) construction edges: v; w; l) 2 EC Satellite Orbit orbit ....

[Article contains additional citation context not shown here]

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational data bases. ACM Computing Surveys, 18(2):197--222, June 1986.

....for the LabFlow 1 benchmark. 4 Benchmark Database Schema Like the OO1 benchmark [13] and the Sequoia 2000 benchmark [54] our benchmark is independent of the data model provided by the DBMS. We therefore describe the database schema abstractly, using an extended entity relationship (EER) diagram [57, 34]. An EER diagram is an ER diagram extended with is a links. The database itself can be implemented in any number of ways, e:g: as a relational database or as an object oriented database. As shown in Figure 1, the EER diagram has two levels (separated by a dashed line) The top level is abstract, ....

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18:197--222, June 1986.

....cases of invalid generalization. The result of the analysis is a cleaner taxonomy that clarifies the modeler s ontological commitments. 1 Introduction Taxonomies are an important tool in conceptual modeling, and this has been especially true since the introduction of the extended ER model [6,26]. Properly structured taxonomies help bring substantial order to elements of a model, are particularly useful in presenting limited views of a model for human interpretation, and play a critical role in reuse and integration tasks. Improperly structured taxonomies have the opposite effect, making ....

Teorey, T. J., Yang, D., and Fry, J. P. 1986. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. ACM Computing Surveys, 18(2): 197-222.

....facilities are generally not supported, with the notable exception of DV Centro. The compositional metaphor of BBW also allows designers to extend its built in iconic, connector and constraint components for reuse. Dynamic visualisation and repository querying tools include those of Teorey et al. [16], Bird [20] Consens and Mendelzon [24] and metaEDIT [5] Most use either graphical query languages, with results presented textually, or textual query languages with textual or graphical results. We have found the JVisualise approach of graphical structure representation and textual ....

Teorey, T.J., Yang, D., and Fry, J.P., "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model," Computing Surveys, vol. 18, no. 2, 197-222, June 1986.

....the database, states whose cities are not part of the database, and identically named streets within a city. STATE(State Name, determined by State Name) 4.2. 3 Related Work on Vertical Shortcut Rules Vertical shortcut rules have been used in design algorithms proposed previously [KLUG79, TEOR86]. But without value determination, there is no formal information in the schema to enable a tool to determine whether a relationship is redundant. Full relational theory permits identification of redundant inclusions, but our conditions are more general. Consider the example in Figure 7 below, in ....

....in the schema to enable a tool to determine whether a relationship is redundant. Full relational theory permits identification of redundant inclusions, but our conditions are more general. Consider the example in Figure 7 below, in which Teorey recommends that the relationship ATTENDS be dropped [TEOR86]. STUDENT (1,1) IS MEMBER (1,N) CLUB(1,1) Segev observes that the above diagram does not itself determine whether ATTENDS is redundant [SEGE87] He therefore asks the user to provide additional constraints, such as: IS MEMBER(Student, Club) AND ATTENDS(Student, School) ....

T. Teorey, D. Yang, J. Fry, "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model," ACM Computing Surveys , June 1986.

....sample health care database after consistency and conflict managemsent 5. Logical design The logical design deals with the translation of a high level representation of a universe of discourse into a logical database schema; that is, a schema that can be implemented in a specific DBMS product [Tob86]. In our case, we will consider the translation from a representation in the semantic data model we described above [Per94c] The target model is a multilevel secure relational model, the Jajodia Sandhu model, an extension of the SeaView logical data model. Using the proposed semantic data model ....

Toby J. Teorey, Dongoing Yang, James P. Fry, A Logical Design Methodology for Relational Databases using the Extended Entity Relationship Model 1986, Association for Computing Machinery

....are presented in section 5. Section 6 contains some concluding remarks. 2 2 Data Model and Query language Underlying the LBL EER Database Tools The concepts of the Entity Relationship (ER) model have been defined originally in [1] Subsequently, several extensions of this model (e.g. [14]) as well as several ER based query languages (e.g. 2] 8] 12] have been proposed. The version of the Extended EntityRelationship (EER) schema constructs and query language underlying the LBL EER tools are briefly discussed bellow; they follow with slight modifications and extensions the ....

Teorey, T.J., Yang, D., and Fry, J.P., A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model, ACM Computing Surveys, 18, 2, (June 1986), pp. 197-222. 19

....and Attributes The analyst identifies potential entity sets, relations, and attributes from the problem statement, related documents, and his knowledge and experience about the application. There is a rich set of publications that provide guidelines for this task (see e.g. rumb91a] shla88a] [teor86a]) The presentation below has benefited from these publications. However, we have also provided new insight. In general, potential entity sets and attributes are identified by looking for nouns that appear in the documents. Entity sets are nouns that are: 1) used to refer to a collection of ....

T. J. Teorey, D. Yang and J. P. Fry, "A logical design methodology for relational databases the extended entity-relationship model," ACM Computing Surveys, Vol. 18, No. 2, pp. 197 - 222, 1986.

....Interpretation of class dictionary graphs In database terminology, a class dictionary graph is an object base schema with only a minimal set of integrity constraints. Class dictionary graphs can be viewed as an adaptation of extended entity relationship diagrams for object oriented design [TYF86] More recently, graphs have been used to model object oriented data bases in [LRV90, GPG90] The definition of a class dictionary graph is motivated by the interpretation in object oriented design given in Table 1. During the programming process, the alternation classes serve to define ....

....and grammars. Sometimes, when we want to talk about the construction and alternation vertices of a class dictionary, we describe a class dictionary graph as a tuple which contains an explicit reference to V C and V A: OE = V C; V A; EC;EA) We use the following graphical notation, based on [TYF86] for drawing class dictionary graphs: squares for construction vertices, hexagons for alternation vertices, thin lines for construction edges and double lines for alternation edges. Example 1 Fig. 7 shows a class dictionary graph for satellites. Satellites can either be military or civilian and ....

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational data bases. ACM Computing Surveys, 18(2):197--222, June 1986.

....objects and classes, and between two classes, resulting from the SG hierarchy. Recall that the SG hierarchy in OR model is somewhat different from the hierarchy definition in other SDMs. We allow only one kind of is a association and we do not incorporate the generalization or exclusive subclass [73, 36] is a in OR model. It is however possible to capture these notions in OR model by specifying a constraint in the schema that says that the domain of each of the subclasses of a generalized class is disjoint. This will then imply that no multiple subclass relationships are possible among the ....

T. J. Teorey, D. Yang, and J. P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197--222, 1986.

....also be extended to support other two schema evolution approaches. It should be pointed out that the ER diagrams have been extended in the past as we do here with EVER diagrams in order to incorporated new concepts. Examples include the Extended ER (EER) model that incorporates the class hierarchy [9, 14] and the Concept D, a graphical language that supports multilevel concept structures [10] The rest of the paper is organized as follows. In Section 2, we will analyze the attribute relationships among schema versions and discuss the issues in maintaining a consistent database which motivate the ....

T.J. Teorey, D. Yang, and J.P Fry. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. ACM Computing Survey, 18(2), June. 1986.

....step) For intermediate specifications F logic ( 20] a logic based abstract specification language for object oriented systems, is used. The problem of database design and implementation is not new. Much valuable previous work has been done to map semantic models to relational systems (e.g. [33], 27] and the results of this big amount of work have also been exploited in practice for long. The transformation of conceptual models to object oriented databases has been addressed by only few number of proposals ( 26] 22] 5] Although these proposals provide some step toward ....

....and OO) have been defined and implemented in commercial DBMSs. The question arises: What implementation environments to consider when transforming conceptual models The transformation of (extended) ER and NIAM models to relational structures in certain normal forms has been defined (see e.g. [33], 27] and has also been implemented in some CASE tools. In [7] and [6] a formalized variant of NIAM (an early simpler version of PSM) is mapped to nested (or flat) relational structures (see e.g. 28] In these papers internal models are captured in terms of a tree like intermediate ....

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197--222, 1986.

....been proposed extending the model by complex attributes, relationships on relationships and different kinds of generalization and specialization hierarchies. Most of them support at least key constraints and cardinality constraints. Cardinality constraints are denoted in form of the 1:n notation [21] or (min,max) notation [10] specifying how often an entity is allowed to participate in a relationship. ER model including generalization concepts support the specification of totality constraints of their subtypes. A detailed description of enhanced ER modeling features can be found in [10] The ....

T. Teorey, D. Yang and P.J. Fry, A logical design methodology for relational database using the extended Entity--Relationship model, ACM Computing Surveys 18 (1986) 197--222.

....into relations, it is no longer stored in the data model (i.e. the schema) Thus we have to use reverse engineering[12] to reconstruct the semantic model from a database schema. However, the mapping from a relational model to a semantic model, such as the extended entity relationship (EER) model [13], is not one to one. Therefore, in general human intervention is needed to construct the semantic model from the corresponding database schema. An initial semantic graph model can be automatically generated based on all the natural join links between relations. User defined links can then be ....

T. J. Teorey, D. Yang, and J. P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197--222, June 1986.

....in relational databases (RDBs) but little has been done in modeling fuzziness in conceptual data models. To fill this gap, we have proposed a design methodology for developing fuzzy RDBs [CMR94] This methodology, based on the Entity Relationship (ER) design methodology of Teorey et al. [TYF86], prescribes a sequence of steps to implement a fuzzy RDB from an extended fuzzy ER model. However, there seems to be no previous work in developing higher level conceptual models for fuzzy rules. In this paper, we propose a generic data model to represent fuzzy rules using the ER data model. The ....

....we propose the fuzzy rule model. Some basic concepts and their ER representations are shown in Figure 4. 4.2. 1 Fuzzy Conceptual Design Methodology The following design methodology for fuzzy relational databases is an extension of the design methodologies for crisp relational databases, such as [TYF86]: Step 1: Constructing an extended fuzzy ER data model. Construct the traditional ER model. Attach f to the entities and relationships that are fuzzy (see Figure 5) Show the DBfuzzifier 1 construct for the crisp entities whose attributes need to be fuzzified. 1. DBFuzzifier is ....

T. Teorey, D. Yang and J. Fry, "A logical design methodology for relational databases using the extended entity-relationship model," ACM Computing Surveys 18, 2 (June 1986) 197-222.

....data, computer aided design or image processing. Current approaches to the transformation of conceptual models into internal models focus mainly on the relational model. The result of the transformation is a relational schema in a certain normal form (see for instance [11] 13] 17] 21] [22] and [24] Other approaches can be found in [2] 10] 20] and [25] In this paper we present a framework for the transformation of object role models. We describe a representation mechanism for internal structures, such that the conventional internal models can be represented. The advantage of ....

T.J. Teory, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. Computing Surveys, 18(2):197--222, 1986.

.... such as FDM [Shi81] and so called object role modeling techniques, such as NIAM [NH89] Complex application domains, such as meta modeling, hypermedia, and CAD CAM, have led to the introduction of advanced modeling concepts, such as present in the various forms of Extended ER (see e.g. TYF86, EGH 92] IFO [AH87] and object role modeling extensions such as FORM [HO92] and PSM [HW93, HPW93] This plethora of techniques reflects the general situation in the field of information systems development. In [AF88] this situation is described by the term Methodology Jungle. In [Bub86] it ....

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197--222, 1986.

No context found.

T.J. Teorey, D. Yang and J.P. Fry. A Logical Design Methodology for relational databases using the extended entity-relationship Model. ACM Computing Surveys, 18(2):197-222 (1986).

No context found.

T. Teorey, D. Yang, and J. Fry. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2):197-222, 1986.

No context found.

T.J. Teory, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. Computing Surveys, 18(2):197--222, 1986.

No context found.

T.Teorey, and J.P. Fry., "A Logical Design Methodology for Relational Databases using the Extended Entity-Relationship Model", ACM Computing Surveys, June 1986.

No context found.

T.J. Teory, D. Yang, and J.P. Fry. A logical design methodology for relational databases using the extended entity-relationship model. Computing Surveys, 18(2):197--222, 1986.

No context found.

T.J. Teorey, D. Yang, J.P. Fry, A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model, ACM Computing Surveys, 18(2), 197-222, (1986).

No context found.

T.J. Teorey, D. Yang, J.P. Fry, A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model, ACM Computing Surveys, 18(2), 197222 (1986).

No context found.

Teorey T. J., Yang D., Fry J. P.: `A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model', ACM Computing Surveys, Vol. 18, No. 2, 1986, pp. 197-229.

No context found.

T.J. Teorey, D. Yang, and J.P. Fry. A logical design methodology for relational data bases. ACM Computing Surveys, 18(2):197--222, June 1986.

No context found.

T. J. Teorey, D. Yang, and J. P. Fry. A logical design methodology for relational databases using the entity-relationship model. ACM Computing Surveys, 18(2):197-222, 1986.

No context found.

Teorey, T. J., Yang, D., and Fry, J. P. 1986. A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model. ACM Computing Surveys, 18(2): 197-222.

No context found.

Teorey, T.J., Yang, D., and Fry, J.P. 1986. A logical design methodology for relational databases using the extended entity-relationship model. ACM Computing Surveys, 18(2): 197--222. ACM press, New York.

No context found.

T.J. Teorey, D. Yang, and J. Fry, "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Mode," ACM Computing Surveys, vol. 18, no. 2, 1986, pp. 197-222.

No context found.

Teorey, T., Yang, D. and Fry, J., "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model," ACM Computing Surveys, 18(2), June 1996, 197-222.

No context found.

T.J. Teorey, D. Yang, and J.P. Fry. "A Logical Design Methodology for Relational Databases using the Extended Entity-Relationship Model." ACM Computing Surveys, 18, 2, pp. 197-222.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC