OUR RECIPE FOR YOUR SUCCESS

Changing from structured to object oriented programming with UML represents a challenging paradigm shift for every company which is not possible without careful planning and preparation of necessary prerequisites and the right implementation steps.

The agreed goal is clear: to significantly increase the productivity of the trained and proven team by introduction of OOP/UML. Everybody in the developers team agrees to the need for it. But: how to get there?

Questions you might ask yourself:

When is best suited point in time to start with an OOP/UML project?
How do I prepare for it?
What do I have to learn?
What are the risks? How can I avoid them?
Where do I start in the project?
Do I start with a complete project or just a small part of it?

CARNICA TECHNOLOGY provides you with answers to these questions and with guidance to a harmonic way of introducing UML into your development team and your first UML project.

Click picture to enlarge

Derived from the above picture, several ingredients are necessary to prepare for and to understand the impact for the change in methodology. It is just not good enough to buy the tools, a couple of books about UML and to learn the notation. Making this transition, without proper education on all facettes of the change and a competent guidedance through this first phase, you will find yourself at risk. There is impact not only on the way you will write code, but on the software architecure and the entire software development process. You will maximize the productivity gain you expect only, if you develop all required elements in a harmonic way. The important step in the second phase is the experienced advise of a technical coach, helping your initial UML team to shoehorn their newly learned expertise into day-to-day project work.

Check the next pages for details.

"Präzise zu planen kostet auch nicht mehr Energie
als träumen, wünschen und hoffen."

"Precise planning costs as much energy,
as dreaming, wishing and hoping."
- Henry Cohen