I am a Systems Engineer and Model-Based Systems Engineering practitioner focused on process architecture, MBSE adoption and model-based architecture development.
My current focus is on helping organisations define, structure and improve how architecture development is performed. I see process architecture as a way to make roles, activities, artefacts, artefact relationships, modelling expectations, traceability, review points and delivery outputs explicit, reviewable and easier to improve.
A recurring theme in my work is that engineering problems are not only caused by technical complexity. Many difficulties appear when teams do not share the same understanding of how architecture work should be performed, what information should be captured, how models should be structured, how outputs should be reviewed, and how architecture should support delivery.
In the context of MBSE, this means going beyond notation and tools. It means defining the modelling approach for a project: which views and artefacts are needed, how they relate to each other, what level of detail is expected, and how the model supports traceability, reviews and decision-making.
A significant area of my work is the implementation and continuous improvement of MBSE practices. This includes practical modelling approaches, reusable templates, modelling guidance, architecture development guidance and lessons learned to help teams create models that are structured, traceable, understandable and useful for delivery.
My background combines electronics engineering, computer science, systems engineering, requirements engineering and model-based approaches. I have applied these across domains including energy, defence, automotive, rail and Air Traffic Management, using tools and methods such as SysML, Cameo, Arcadia, Capella and UML. My experience includes operational process capture, system architecture definition, functional analysis, requirements-to-architecture alignment, model-based traceability and MBSE mentoring. This has shaped my interest in architecture development processes that are practical, adaptable across modelling approaches, and able to improve consistency between textual requirements and architecture models.
I created the MBSE with Arcadia step-by-step guide to support practitioners moving from textual requirements towards system design using Arcadia and Capella. More recently, I developed the Simple Process for Architecture Development, which describes the flow between requirements engineering and system architecture, including roles, activities, artefacts and artefact relationships. This work was recognised by the Institute for Systems Engineering at ASEC 2025.
Through this blog, I share practical MBSE guides, modelling examples, process architecture ideas and reflections from real project experience. The objective is not to promote a single tool or framework, but to show how model-based approaches can help engineering teams improve clarity, consistency, traceability and shared understanding.
If this is relevant to your organisation or project, feel free to use this contact form to discuss MBSE adoption, process architecture or architecture development support.