TAR Object Model

Object Models and Class-diagramming are probobly the most important facet in Enterprise Architecture today. The reason they are so important is because

• provide a means of code-reusability
• provide a level of modularity and abstraction thus providing a better focus on functionality
• make code more re-usable and easier to maintain
• easier to document code

Object models provide a working "blueprint" of an Enterprise System. They visually define how operations interact with each other clarify the results that are achieved by these interactions.

TheObjectIs.com is steeped in learning, knowing and advancing its knowledge in all aspects of Enterprise Level Object Oriented Analysis and Design.

As an example of our dedication to Enterprise Architectural Design, we have posted the Object Model of the WGD TAR System, below.

Driver Object Model

As noted in the WGD TAR Help Files Drivers are the workhorses of the TAR System; and therefore, the many constructs pertaining to their duties must be known.

• Their association with an Instigation Move
• how many
• which ones
• Time they have allotted for moves
• When were they assigned

TAR Exceptions Object Model

The TAR Exceptions Object Model clearly shows how a "best-practices" approach to identifying, tracking and debugging the source of errors has been taken by allocating specific handler-routines depending upon the type of exception that has been thrown

History Change-Order Object Model

History change-orders keeps track of any edits or modifications that were performed on an Instigation move item.

As there are several modifiable-parameters on any given move

• Add/remove drivers
• Change move priority
• Change manpower required
• Change date-time of move

... then lists of these changes can be built-up quickly.

The History Change Order Object Model clearly shows how different operations with these lists is performed

Instigation/Regulation Object Model

The Instigation/Regulation Object Model is at the heart of the WGD TAR System. An Instigation move holds all the parameters designated by a move.

Since Regulators are only modifying objects that have already been created; then it makes sense to inherit all the functionality exposed by this class.

Location Object Model

The Location Object Model is a very complicated one; simply because of the various methods and types of locations that can be ascertained.

For instance:

• Searching for a location
• Selecting a location
• Choosing an exact location

And when it is figured that each location is composed of five different parts:

• Building
• Floor
• Column
• Common name
• Optional Custom-name

Then the complexity adds up rather quickly.

Nevertheless, this Object Model describes quite accurately, at a glance, and in detail; all of the actions that can be performed on the different properties.

Move Description Object Model

Each Instigation move has certain parameters associated with it. However, of importance to note, is the fact that this Object Model has a common design feature that follows all of the other Object Models in this system.

That common design feature is this: the Business Logic is clearly separated from the underlying properties and methods that interact with Client code. This is called the "Separation of Concerns" and can be noted by the fact that all of the Business Logic elements are contained within an associated and unique "business_class_nameDB" class.

Furthermore, all Data Access functions are futher abstracted from the Business Logic functions by being contained in their own separate module. This design-philosopy is what is known as "Three-Tiered Architecture" more commonly known as Enterprise Level Architecture and is a part of the Business Process Requirements.

TAR ID Generator And TAR User Object Models

These two object models show the control of the generation of Instigation move IDs and also the authorization, identity and contact details of the users of the WGD TAR System.

Data Access Object Model

TheObjectIs.com created it's own custom Data Access Layer Class in order gain the best possible performance characteristics.

This simple yet powerful class is capable of performing all CRUD operations; being realized through object arrays which are used as passing parameters to Stored Procedures in the database.