Jump to ContentJump to Main Navigation
Information Modeling: The EXPRESS Way$
Users without a subscription are not able to see the full content.

Douglas Schenck and Peter Wilson

Print publication date: 1994

Print ISBN-13: 9780195087147

Published to Oxford Scholarship Online: November 2020

DOI: 10.1093/oso/9780195087147.001.0001

Show Summary Details
Page of

PRINTED FROM OXFORD SCHOLARSHIP ONLINE (oxford.universitypressscholarship.com). (c) Copyright Oxford University Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in OSO for personal use. date: 12 June 2021

Usage notes

Usage notes

Chapter:
Chapter 22 Usage notes
Source:
Information Modeling: The EXPRESS Way
Author(s):

Douglas Schenck

Peter Wilson

Publisher:
Oxford University Press
DOI:10.1093/oso/9780195087147.003.0030

Now we discuss some of the potential uses of the EXPRESS-I language. In Object-Oriented terms, an EXPRESS entity would be called a class, and an instance of a class is termed an object. One object may reference another object. EXPRESS, though, distinguishes between entities and types (i.e., the enumeration, select and the defined data type) as entities may be subtyped whereas types cannot be. EXPRESS-I treats entity instances as objects in the OO sense. It also allows types to be treated as objects in that they can be instantiated and referenced. Alternatively, type values may be embedded in entity instances. The simplest use of EXPRESS-I is as a paper exercise in displaying examples of EXPRESS declarations that are populated with data. The language allows the display of entity instances as referenceable objects. Types instances may also be displayed as referenceable objects, or they may appear as unreferenceable values within other objects' values. Examples in this book show both forms of type instantiation. Values of explicit entity attributes are required. The values of derived or inverse attributes need not be displayed, except as exemplars, because as noted, these are essentially calculable from the values of the explicit attributes. Examples of EXPRESS schemas can also be displayed, as well as individual objects. The EXPRESS-I model construct is provided to enable the display of multiple schemas. Typically, a model would be used when two or more EXPRESS schemas interact with each other. Note that EXPRESS itself does not support such a construct. Note: We do not discuss models in this book. The test case construct is provided to assist in the formal specification of test cases against the implementation of an EXPRESS schema. EXPRESS itself does not provide an equivalent construct. For a test case, a base set of EXPRESS-I objects must be defined which will be the objects (and their supporting data) to be tested. The values of these objects may be in the form of parameters, whose formal definition are given in an enclosing context. A series of test cases may then be defined on the context, by providing actual parameter values.

Keywords:   Abstract test case, C++, Constraint, Eiffel, Information base, Object base, Test case

Oxford Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs , and if you can't find the answer there, please contact us .