My approach and My training

My paradigm is ADDD (Abstract Domain Driven Development).

(see: https://jukkatamminen.wordpress.com/2009/08/06/my-contribution-to-addd/)

This starts with abstract domain modeling. The next thing is logical 3-tier architecture and the third is agile application development.

First my working principles on abstract modeling are:

  1. Abstract OO models from reality.

I am specialized to create abstract object-oriented domain model. These models are representations of reality –not any application. The models actually have very little to do with applications and even that little is pretty indirect.

  1. Modeling process

These models are always done from scratch. It takes always from 3 to 15 working days from a modeling team. The only way this can be done is a workshop that every participant participates practically every session. The technical modeling and the required facilitation is done be the modeler ( in this case be me). The session length is 3 to 6 hours.

  1. The deliverables

The end product of this activity is always a class model and a few collaboration diagrams. The class model is represented most desirable as one class diagram. This class model contains 20 to 70 classes and their associations.

Second thing is 3-tier architecture.

  1. The layers are: Application, Domain & Persistence
  2. Domain layer has no references out side itself.
  3. The best persistence layer implementation is a object database.
  • Consulting  domain modeling

The most important element in this process is abstract domain (or business) model.

The main purpose of this model to see the forest from  the trees – understand the structure and deepest behavior of the chosen world. This model must (always) be created from scratch with the group of business people with best knowledge current business behavior and also the ideal ( or wanted) business behavior.

This work will take from such group 3 – 15 working days to finish. By then they have full understanding of the structure of their world and the most important business behavior with minimum amount of detail. This model has no application aspects what so ever! At this state most of the details are deadly poison for the modeling and the model.  The outcome (technically) is a class model typically 30 – 60 classes and their relationships (association, aggregation, inheritance etc.) and a few  (3 – 10) collaboration diagrams showing examples of  the most profound behavior  mechanisms of the domain.

This is a skeleton model and forms the bases for all application development around the model.

I am ready to facilitate the whole modeling phase. The modeling group must have basic knowledge on object-oriented paradigm and UML.

  • Training OOA and perhaps OOD

I have been giving Abstract Domain Modeling for more than 10 years time.

The training is conducted as one or two day training but the two day version with more exercises have proved to be better.   The amount of detail in Object Oriented Modeling is very limited. The whole content can be presented within two days. The first half day is theory starting from the meaning of modeling and the idea of OO paradigm. Then I will present the definitions and elements of OO and how these are used. Within this section I will also cover the UML notation. Then I introduce the student to abstract object-oriented domain modeling. In the afternoon the class is divided into exercises small group size 2 – 4 participants. These groups do the first exercise and then the results are worked trough together.  Next morning I will start with first day’s summery and then the groups will do the next more complicated exercise. Finally I will give an overview of application development starting from abstract domain model.

I have trained this way around thousand people both IT- professionals and business people. The evaluations of this training have been very good.

The size of an optimal class is from 9 to 16 student –preferably with homogenous background.

Then I have also given training to small amount of people on “pattern and techniques of OO modeling”. There are a small set of rules of thumb and best practices that gives vision of how to do the modeling. This is for junior modeling professionals with some working experience as a modeler. This is sort of a master class and can and should be tailored according to participants’ situation and skills. This training in total is 1 – 4 days.

  • I am willing to do this globally on-site as long as the working language is English (or Finnish).
Advertisements

One Response

  1. Bravo, magnificent phrase and is duly

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: