Alexander von Zitzewitz
Founder and Managing Director, Hello2morrow
Alexander von Zitzewitz is founder, managing director of the company and CEO of the US subsidiary. He has more than 20 years of project and management experience. In 1993 he founded ootec - a company focused on project services around object oriented software technology. This company was sold to the French Valtech group in March 2000 and served customers like Siemens, BMW, Thyssen-Krupp-Stahl and other well known names in German industry. From 2003 to early 2005 he was working as Director of Central Europe for the French company Xcalia S.A. Since the summer of 2008 he is living in Massachusetts. His areas of expertise are object oriented system design and large scale system architecture. Alexander has a degree in Computer Science from the Technical University of Munich.
Presentations
How to organize your code - Modules vs. Architecture
Thursday, 9:00 AM EST
Most nontrivial software systems suffer from significant levels of technical and architectural debt. This leads to exponentially increasing cost of change, which is not sustainable for a longer period of time. The single best thing you can do to counter this problem is to carefully manage and control the dependencies among the different elements and components of a software system.
This session will first look at the major reasons why so many systems end up in an unmaintainable state and then show how to address the problem by defining an enforceable architectural blue-print for a software system using an innovative domain-specific language for the description of software architecture. I the workshop part you will be able to create an architectural blueprint for a system of your choice. See workshop requirements for details.
Here are a couple things we will go over:
- Modules vs. Architecture - how do modules fit into architectural models.
- Micro services vs. smart monoliths.
- Describing architectural blueprints with a domain specific language for architecture.
How to organize your code - Modules vs. Architecture
Thursday, 10:45 AM EST
Most nontrivial software systems suffer from significant levels of technical and architectural debt. This leads to exponentially increasing cost of change, which is not sustainable for a longer period of time. The single best thing you can do to counter this problem is to carefully manage and control the dependencies among the different elements and components of a software system.
This session will first look at the major reasons why so many systems end up in an unmaintainable state and then show how to address the problem by defining an enforceable architectural blue-print for a software system using an innovative domain-specific language for the description of software architecture. I the workshop part you will be able to create an architectural blueprint for a system of your choice. See workshop requirements for details.
Here are a couple things we will go over:
- Modules vs. Architecture - how do modules fit into architectural models.
- Micro services vs. smart monoliths.
- Describing architectural blueprints with a domain specific language for architecture.