Commercial Offerings (Services)

Contact me on LinkedIn or via {consulting or mentoring or research} at ozimmer d o t ch if you are interested in professional services and/or project collaborations in my areas of expertise:

• Architectural coaching and architecture reviews; agile architecture practices
• Collaborative Modeling (CoMo) practices and Domain-Driven Design (DDD)
• API design and evolution (Web APIs, messaging, other protocols)
• Microservices architectures (for instance, service rightsizing)
• Cloud-native application design

Coaching and Mentoring (Community Giveback)

I will be happy to exchange thoughts and share experiences and advice regarding IT architecture, technical writing and other topics upon demand:

• Mentoring is one of the giveback activities of IT architects certified by The Open Group.
• Informal advice regarding research and development methods, project scoping, and technical writing:
  • Do’s and Don’ts in Technical Reports about Term and Thesis Projects summarizes advice and gives examples.
  • eprints, the institutional repository at OST, features student projects supervised.
• Opinions and pointers to existing work on all things software architecture, patterns and ethical values in software engineering.

Contributions to Open Source Projects

I lead or contribute(d) to the following projects (in alphabatical order):

• AD Mentor, a plugin to Sparx Enterprise Architect that supports architectural decision modeling and capturing (no longer maintained).
• Context Mapper, DSL and tools for strategic and tactic Domain-Driven Design (DDD).
  • Three paper publications describe the concepts and provide examples.
  • (in German) “Domain-Driven Design in der Praxis - Erfahrungen mit dem Open-Source-Tool Context Mapper”
• Design Practice Repository (DPR), a collection of method elements (activities, artifacts) for service design and beyond.
  • The Y-statement artifact for architectural decision capturing is a good starting point.
• Ethical Software Engineering, combining agile practices and the value-based systems engineering processes in IEEE 7000.
• Interface Refactoring Catalog, a collection of API and related architectural refactorings.
• Lakeside Mutual, a microservices sample application written in Java/Spring Boot and JavaScript (React, Vue, Angular).
• Markdown Architectural Decision Records (MADR), template and lightweight tools to capture any decisions and decision rationale in Markdown.
• Microservice API Patterns (MAP), design patterns to identify and specify and realize services and their message APIs.
  • A short introduction can be found in a tool tip column in JavaSpektrum (in German).
  • MAP evolved into “Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges”, Vaughn Vernon Signature Series, Addison-Wesley Professional.
• Microservice Domain-Specific Language (MDSL), a domain-specific language to specify (micro-)service contracts and their data representations (realizing the API Description pattern from MAP).
  • The MDSL Primer is a good starting point.
  • The project is no longer maintained actively.
• Value-Driven Analysis and Design (VDAD)

Drop me an email ({consulting or mentoring or research} at ozimmer d o t ch) or DM me in LinkedIn in case you are interested to talk!