Marc Lankhorst

Lankhorst's foundational claim is that a *coherent* description of architecture provides insight, enables communication among different stakeholders, and guides complicated business-and-ICT change processes, and that no prior language fully enabled integrated enterprise modelling. ArchiMate supplies generic, organization-independent concepts that can be specialized or composed, deliberately conforming to existing standards (e.g., UML) where possible and complementing them with the *missing concepts* needed to model the relationships among architectural domains rather than reinventing each domain language (Lankhorst 2004, "Towards a language for coherent enterprise architecture descriptions," doi:10.1109/edoc.2003.1233835). Key work: *Enterprise Architecture at Work: Modelling, Communication and Analysis* (Lankhorst et al., Springer; multiple editions).

ArchiMate's structuring principle is a small set of layers (business, application, technology), each offering *services* to the layer above, with a consistent active-structure / behaviour / passive-structure metamodel running through all of them. This is what makes cross-domain traceability possible: a strategic concern can be linked, through services and realization relations, down to the infrastructure that supports it. Key work: "The Anatomy of the ArchiMate Language" (doi:10.4018/jismd.2010092301) and the ArchiMate 3.x standard analyzed in "A Deep Perspective on the ArchiMate Enterprise Architecture Modeling Language" (doi:10.18417/emisa.15.2).

Lankhorst and colleagues argued that EA methods (TOGAF) acknowledge requirements but provide little support for modelling the *underlying motivation* of architectures: stakeholder concerns and the high-level goals that address them. They built a goal-and-requirements modelling language (later the ArchiMate Motivation extension) so that the *why* of an architecture is captured and reasoned about, not just the products, services, processes, and applications (Quartel, Engelsman, Jonkers, van Sinderen 2009, doi:10.1109/edoc.2009.22; Engelsman, Quartel, Jonkers, van Sinderen 2010, "Extending enterprise architecture modelling with business goals and requirements," doi:10.1080/17517575.2010.491871).

A distinctive thread is using EA to bridge strategy and implementation through *capabilities*. Lankhorst contributed a well-founded, ontology-based treatment of resources and capabilities in ArchiMate, giving the language formal semantics for what an organization *can do* (Azevedo, Iacob, Almeida, van Sinderen, Pires, Guizzardi 2015, doi:10.1016/j.is.2015.04.008), and the program produced capability-based-planning methods that let architects link motivation to implementation (Aldea et al. 2015, doi:10.5220/0005468103520359). Capability-based planning is explicitly positioned as the link between strategy and enterprise architecture.

Beyond description, Lankhorst insists the model must *do work*: support impact-of-change analysis, quantitative/functional analysis, and alignment checks across architecture levels. *Enterprise Architecture at Work* devotes chapters to architecture analysis and architecture alignment, treating the model as the substrate for reasoning, not merely communication.

Lankhorst's school connects architecture upward to the business model and value proposition, formally mapping Osterwalder's Business Model Canvas/ontology into ArchiMate so that design begins with a business model translated to architecture "to ensure fitness for market," rather than starting from technology (Meertens, Iacob, Nieuwenhuis, van Sinderen, Jonkers, Quartel 2012, doi:10.1145/2245276.2232049).

A meta-principle running through all of the above: rather than inventing siloed notations, align to and extend open standards (UML, TOGAF, BPMN, the Business Model Canvas) so models interoperate and the ecosystem compounds. This is both a modelling stance and a governance stance.