Browse Prior Art Database

Address Book Class Hierarchy

IP.com Disclosure Number: IPCOM000119547D
Original Publication Date: 1991-Feb-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 114K

Publishing Venue

IBM

Related People

Cavendish, CJ: AUTHOR [+2]

Abstract

Provided is class hierarchy of objects for an object-oriented design which will maximize code reuse and allow considerable flexibility in developing advanced address book-related functions. It overcomes the current difficulties in application development by building a set of classes providing basic address book behaviors within individual classes. Each class is responsible for its own methods. In addition, this address book design allows for items other than people to provide addressing information. In the following design, a distribution list can cause distribution to a printer, a file folder and other objects in addition to providing access to the addresses of people.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Address Book Class Hierarchy

      Provided is class hierarchy of objects for an
object-oriented design which will maximize code reuse and allow
considerable flexibility in developing advanced address book-related
functions. It overcomes the current difficulties in application
development by building a set of classes providing basic address book
behaviors within individual classes. Each class is responsible for
its own methods. In addition, this address book design allows for
items other than people to provide addressing information. In the
following design, a distribution list can cause distribution to a
printer, a file folder and other objects in addition to providing
access to the addresses of people.

      By subclassing the provided classes, application developers can
quickly produce an improved version of the address book application
and add new function. The amount of code to be added or changed is
minimized by the encapsulation of the classes. Existing code is
easily reused.

      The problem being addressed by this design is how to build an
object-oriented address book which will provide flexibility for an
electronic office system, such as distribution to electronic
addresses including printers, files, fax machines, telephones and to
people, as well. Current non-object-oriented architectures limit mail
distribution to mailboxes for people.

      The proposed class hierarchy consists of three categories of
objects. Classes are divides into model and view objects in a revised
Model-View-Controller scheme first published by ParkPlace Systems in
Smalltalk 80. In addition, database objects have been added.

      The model objects consist of the data portion of the object and
its behaviors. The classes in the design which are models are
AddressBook, AddressBookContainer, and the subclasses of
AddressBookContainer which are ConferenceRooms, DistributionLists,
People, PersonalEntries, Organizations, Printers, and Services. The
AddressBook class hierarchy for the model classes is s...