Introduction

The Object Model is a conceptual model that takes an Micro Finance Institution wide view of information.  The model reflects an idealized “to be” model of what the Business requirements are.  The model does not consider design and implementation details. 

The Object Model is expressed in UML notation.

The initial focus of the Object Model will be a static view of the data definitions and relationships.  Behavior will not be modeled until later.

Model Elements

Class Packages

The Object Model is organized into a hierarchy of Class Packages.  Each Class Package represents a collection of lower level Class Packages or one or more Class Diagrams and a collection of Classes.

Conventions:

• Class Diagrams containing Packages will be used to show the Hierarchy of the Object Model.  A Package may be broken down into other Packages using a Child Class Diagram.
• Each Class Diagram is contained in a Package.  
• Each Class will be contained in only one Package. 
• The lowest level of the hierarchy will be Packages representing Business Objects.
• Each Business Object Package will have one or more child Class Diagrams associated with it.
• Use the Symbol tab Graphical Comment field on the Package definition to denote which Packages are Business Objects.

Class Diagrams

There is at least one Class Diagram for each Business Object.  Complex Business Objects may require more than one diagram.    Class Diagram show how Classes relate to each other.  Each Class is shown with a name and attributes,.  On the Class Diagram, the Class is shown as a rectangle divided into three sections.  The top section contains the Class Name, the middle section contains the list of Attributes, and the lower section contains the list of operations (not currently used). The relationships among the Classes are shown with names, roles, and multiplicity.  The relationships may be used to express business rules such as must be one to one or a mandatory association.