Method to identify object classes.
(Tutorial Page 20)
  • Identify Candidate Nouns from Problem Domain (Use Cases) as potential classes
  • Look for transactions, events, roles, and tangile items
    1. Transactions Loan, meeting, sale
    2. Events Landing, Request
    3. Roles Mother, Father, Teacher, Passenger
    4. Tangible Items Car, Sensor, Ingredient, Plane
    5. Classify Nouns as :People, Places, Things, Organizations, Concepts (principles, ideas, rules), Events (things that happen)

  • Identify nouns that have in-complete definitions
  • Categorize them as attributes or object classes
  • Identify potential collections
  • Some nouns imply collections & may become containers
    1. Example: Each access is recorded in Log.
    2. Log is a collection
    3. Important since collections are default for DB and will require special work in programming

  • Identify boundary objects
    1. All systems have interface to objects beyond the systems.
    2. Example Telephone billing system with the telephone line
    3. Customary to model periphery of systems with boundary or i/o objects

  • Characteristics of I/O Objects:
    1. Their attributes or object state is volatile
    2. They change due to external system influence
    3. Example: Indicator for schedule change
    4. Source of arriving messages from outside
    5. Tend to exist forever

    |-Previous Slide-| -Next Slide-| -Table of Contents-|-List of Tutorials-| -Home Page-|-Disclaimer-|
    If desired, insert comments for ooanly20
    Your Email Address(Optional)
    Action
    Copyright © 1997 Object Ideas Corporation --- Last Updated January 15, 1997