Banking Example 1 ODL Object Definition Language

 www.phwiki.com

 

The Above Picture is Related Image of Another Journal

 

Banking Example 1 ODL Object Definition Language

Armstrong University, US has reference to this Academic Journal, Object Definition Language CORBA ODMG ODL (design OQL (queries ODL Relational design OODMBS input Design language derived from the OO community: Can be used like E/R as a preliminary design in consideration of a relational DB. ODL Class Declarations interface < name > {elements = attributes, relationships, methods } Element Declarations attribute < type > < name > ; relationship < rangetype > < name > ; Method Example float gpa(in: Student) raises(noGrades) float = return type. in: indicates Student argument is read-only. Other options: out, inout. noGrades is an exception that can be raised by method gpa. Banking Example 1 customer loans branch borrower Belongs-to Customer-of Ss# name amount loandid branchid location type address Keys: ss#, loanid, branchid Cardinality constraint: each loan belongs so that a single branch

 Kennedy, Ian Armstrong University www.phwiki.com

 

Related University That Contributed for this Journal are Acknowledged in the above Image

 

Banking Example (II) interface Customer { attribute string name; attribute integer ss#; attribute Struct Addr {string street, string city, int zip} address; relationship Set borrowed inverse Loans::borrower; relationship Set has-account-at inverse Branch:patrons; key(ss#) } Structured types have names in addition to bracketed lists of field-type pairs. Relationships have inverses. An element from another class is indicated by < class > :: Form a set type alongside Set. Loans Example (III) interface loans { attribute real amount; attribute int loanid; attribute Enum loanType {house, car, general} type; relationship Branch belongs-to inverse Branch::loans-granted; relationship Set borrower inverse Customer::borrowed; key(loanid) } Enumerated types have names in addition to bracketed lists of values. Bank Example (IV) interface Branch { attribute integer branchid; attribute Struct Customer::Addr location; relationship Set loans-granted inverse Loans::belongs-to; relationship Set patrons inverse Customer::has-account-at; key(branchid); } Note reuse of Addr type.

ODL Type System Basic types: int, real/ float, string, enumerated types, in addition to classes. Type constructors: Struct in consideration of structures in addition to four collection types: Set, Bag, List, in addition to Array. Limitations on Nesting Relationship class collection Attribute collection struct Basic, no class ER versus ODL E/R: arrow pointing so that ?one. ODL: don’t use a collection type in consideration of relationship in the ?many” class. Collection type remains in ?one.? E/R: arrows in both directions. ODL: omit collection types in both directions ODL only supports binary relationship. Convert multi-way relationships so that binary in addition to then represent in ODL create a new connecting entity set so that represent the rows in the relationship set. Problems handling cardinality constraints properly!!

Today?s Agenda Who Are You? – 1 Who Are You? – 2 Today?s Assignment – 1 Today?s Assignment – 2 What You Will Do in this Seminar -3 NO What You Will Do in this Seminar -4 What You Will Do in this Seminar -5 How the Seminar Will Work; also Deadlines PTO PTO Patents != Copyright != Trademarks SUBSTANTIVE LAW TERMS OF ART Introduction/ Review of patent law The AIA Reading a Patent IT?S THE _______ STUPID. Reading a Patent CLAIM Reading a Patent ? Who asked you to? Major Issues of Liability in Patent Law Major Issues of Liability in Patent Law AI C&C PO Major Issues of Liability in Patent Law P-I-S v P.A. Your Patented Objects -1 Next Week

Roles in ODL No problem; names of relationships handle roles.? interface employee { attribute string name; relationship Set manager inverse Employee::worker; relationship Set worker inverse Employee::manager } employee works in consideration of manager worker Subclasses in ODL Subclass = special case = fewer entities/objects = more properties. Example: Faculty in addition to Staff are subclasses of Employee. Faculty have academic year (9 month salaries) but staff has a full-year (12 month salary). ODL Subclasses Follow name of subclass by colon in addition to its superclass. interface Faculty:Employee { attribute real academic-year-salary; } Objects of the Faculty class acquire all the attributes in addition to relationships of the Employee class. Inheritance in ODL in addition to ER model differ in a subtle way in ODL an object must be member of exactly one class in ER an object can be member of more than one class

Keys in ODL Indicate alongside key(s) following the class name, in addition to a list of attributes forming the key. Several lists may be used so that indicate several alternative keys. Parentheses group members of a key, in addition to also group key so that the declared keys. Thus, (key(a1; a2; : : : ; an )) = ?one key consisting of all n attributes.” (key a1; a2; : : : ; an ) =?each ai is a key by itself. Keys are not necessary in consideration of ODL. Object identity in addition to not keys differentiates objects

Kennedy, Ian General Manager

Kennedy, Ian is from United States and they belong to General Manager and work for KCFG-TV in the AZ state United States got related to this Particular Article.

Journal Ratings by Armstrong University

This Particular Journal got reviewed and rated by and short form of this particular Institution is US and gave this Journal an Excellent Rating.