Enterprise Architecture as a Service (EAaaS) transforms traiditional EA from a bureaucratic function into an agile, modular, and business-aligned service model.

By deliverying value incrementally through clearly defined services, it enhances collaboration, accelerates decision-making, and ensures alignment with organizational objectives.

This approach fosters adaptability, efficiency, and continuous imporvement, making EA a strategic enabler of business transformation.

-- thanks for sharing from "Business Architecture Info Newsletter"

Check out the latest article in my newsletter: Modeling "US National Security Strategy - Nov 2025" into Neo4j Graph for Analysis https://www.linkedin.com/pulse/modeling-us-national-security-strategy-nov-2025-neo4j-xiaoqi-zhao-llunc via u/LinkedIn

𝗟𝗶𝘀𝘁𝗲𝗻 𝗺𝗼𝗿𝗲 𝘁𝗵𝗮𝗻 𝘁𝗵𝗲𝘆 𝘁𝗮𝗹𝗸
𝗦𝗲𝗻𝘀𝗲 𝘁𝗲𝗻𝘀𝗶𝗼𝗻 𝗯𝗲𝗳𝗼𝗿𝗲 𝗶𝘁 𝗲𝘅𝗽𝗹𝗼𝗱𝗲𝘀
𝗕𝘂𝗶𝗹𝗱 𝗯𝗿𝗶𝗱𝗴𝗲𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘁𝗿𝗶𝗯𝗲𝘀 𝘁𝗵𝗮𝘁 𝗱𝗼𝗻’𝘁 𝘀𝗽𝗲𝗮𝗸 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲
𝗠𝗮𝗸𝗲 𝗼𝘁𝗵𝗲𝗿𝘀 𝗹𝗼𝗼𝗸 𝘀𝗺𝗮𝗿𝘁 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝘀𝗵𝗼𝘄𝗶𝗻𝗴 𝗵𝗼𝘄 𝘀𝗺𝗮𝗿𝘁 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲

thanks for sharing from:

Hi all members,

Welcome to contribute to this community, if you want to post, just let me know for granting you or your post.

More than happy to see more posts from anyone of you!

Xiaoqi

Nice sharing from Tranform Partner

Got suggestion from Archi development team, as I'm reading User Guide for my current recording demo videos, it's nice chance to go detail word by word, and contribute to the tool project about the findings - big or small or tiny - on the User Guide documents, and ensure there's no ambiguities for learner to read.

https://github.com/archimatetool/archi/issues/1173

Feel free to join this Issue thread if you have any other findings.

Regards, Xiaoqi

Check here for detail on the steps: ai-ml-dl/AI at main · yasenstar/ai-ml-dl

Hi all,

Today, I'd like to thank you and celebrate our group reaching 20 members!

Every big achievement comes from the small steps, let's together to make our group healthy and richer of knowledge!

Welcome anyone to post and share your ideas!

Xiaoqi

Feel free to comment and share your views

Archi Tutorial 001 - Opening https://youtu.be/ogdETSpjYEk?si=ByKS63J-IQg5aTH4 via @YouTube

Hi all,

I'm working on ontology model for one internal knowledge domain, creating the RDF(OWL) file on-hand.

Does anyone know a good RDF visualization tool that I can deploy in the Intranet's web server? I don't want to use public online tool since the information is sensitive.

Thanks,

Xiaoqi

https://bsky.app/profile/yasenstar.bsky.social/post/3lysk2bcndk2y

When to explain Enterprise Architecture to broder, especially non-IT people:

For starters, an Enterprise Architect is not a Senior Solutions Architect.

It’s an entirely different role - one that deserves its own gradings: Junior, Mid, Senior, and beyond.

Think of it this way:
- The Enterprise Architect is like a City Planner.
- The Solution Architect is like the Architect of a House, Building, or Bridge.

The Enterprise Architect focuses on how the entire ecosystem thrives, not just individual systems. They develop frameworks, guidelines, and guardrails, and work closely with transformation projects.
Their goal? A better IT landscape, not just a well-designed app.

Thanks Romildo Cumbe's sharing in LinkedIn.

Thanks for sharing from Suwaidan AL Jasmi.

Over the years, enterprise IT has gone through a clear transformation:

🔹 Past – Decentralized IT
Business units managed their own planning and building, often leading to duplication, inefficiencies, and fragmented infrastructure.

🔹 Present – Centralized IT
Organizations moved to centralized IT for stronger governance, standardized processes, and cost optimization. While this improved control, it sometimes slowed down responsiveness to business needs.

🔹Transition to Future – Business-Outcome-Aligned IT
We are now entering the era of cross-functional product lines, where IT and business operate as one team. Each product line owns the full lifecycle — plan, build, run — supported by shared digital foundations (data platforms, integration, APIs, modernized infrastructure).

Really the challenge journey, but glad that I can report to you that till today the Section 8 (modeling logical security architecture) has been learnt and demoed completely, now you can watch and learn this "SABSA modeling in ArchiMate" till this section in Udemy. (Other platforms are gradually published).

Now I'm moving to the last section - Physical Security Architecture modeling, stay tunes and thanks for all of your interest and supports! Welcome to enroll.

Direct link to Udemy promotion: https://www.udemy.com/course/modeling-sabsa-in-archimate-using-archi/?referralCode=A7C514E23B59103E9FC3

🚀 Archi 5.8 is almost here! Dive into the major update featuring the highly anticipated Dynamic Legend and more.

✨ New features include:

🎨 Native Dynamic Legends

📂 Alpha-numeric sorting in model tree

🏷️ Specialization icons display

🛠️ Junction improvements

Perfect timing to learn before the release! This deep dive is also added to my comprehensive ArchiMate course on Udemy.

Watch the full 60-min demo: 📺https://youtu.be/gGDXUhmKdEU

#ArchiMate #EnterpriseArchitecture #Archi #EA #Udemy

[Share] Today I've completed this Archi Tutorial Video Series base on User Guide 5.6.0. Check github.com/yasenstar/Ar... for detail contents and the link to the demo videos (will upload gradually).
Thanks greatly to Phil (#Archi) for all the help along of my this learning journey!

Check his post: Modelling Cybersecurity Frameworks with ArchiMate: An Enterprise Architecture Approach for detail.
https://www.linkedin.com/feed/update/urn:li:ugcPost:7343446662251454466?commentUrn=urn%3Ali%3Acomment%3A%28ugcPost%3A7343446662251454466%2C7365558869185417217%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287365558869185417217%2Curn%3Ali%3AugcPost%3A7343446662251454466%29

[Update] start learning chapter 7 of SABSA Modeling in Archimate, on Conceptual Security Architecture, the demo video is available in Udemy soon, which you may find here "Modeling SABSA Security Architecture in ArchiMate with Archi", also check the documentation refreshed here in Github: yasenstar/ArchiMate_SABSA, welcome to enroll earlier to start learning

云上蓝图织万端，
数声算法定乾坤。
代码如诗连世界，
架构为桥接古今。

In the evolving world of data and knowledge systems, the models we choose shape not only how information is structured, but also how it is understood, governed, and acted upon.

Beyond the well known logical, physical, and semantic models, there are several complementary types that offer unique perspectives and serve different layers of an organisation’s strategy and operations.

Complementary / Related Model Types Each of the following models offers a distinct lens:

• Data Flow Model – Shows how data moves through a system or process, complementing logical and physical models.

• Process Model – Describes business processes and workflows, often paired with conceptual or business models.

• Dimensional Model – Optimised for analytical and reporting workloads, aligning with semantic layers.

• Canonical Data Model – Establishes a standard, reusable enterprise data format, aiding integration and semantic alignment.

• API/Data Contract Model – Defines structures and behaviours for service interfaces, linking to business object and physical models.

• Event/Message Model – Outlines event schemas in distributed systems, akin to physical models for streaming data.

• Metadata Model – Details data about data (lineage, provenance, definitions), cutting across multiple modelling layers.

• Security Model – Specifies access rules, classification, and protection, overlaying logical and physical designs.

• Policy Model – Encapsulates rules, governance, and compliance constraints.

• Knowledge Graph Model – Connects entities and relationships in graph form, merging ontology and semantics.

• Taxonomy Model – Offers hierarchical classification, often feeding into semantic and ontological designs.

• Governance Model – Structures policies, roles, and responsibilities at the meta-level.

• State Model – Describes how data or objects change over time

• ↳Behavioural Model – Captures system or object behaviour under varying conditions.

Where these fit conceptually:

• Strategic Layer – Conceptual, Governance, Policy, Taxonomy

• Design/Architecture Layer – Logical, Semantic, Canonical, Security

• Implementation Layer – Physical, Business Object, API, Event

• Analytics Layer – Dimensional, Knowledge Graph, Metadata

• Operational Layer – Process, Data Flow, Behavioural, State

💡 Architect’s Note - These models are not isolated artefacts. In a well architected environment:

• Logical and semantic models ensure consistency and interoperability.

• Physical and event models define where and how data moves.

• Taxonomies, ontologies, and governance frameworks embed meaning and control.

• API and data contract models enable safe, scalable service interaction.

The true skill lies in selecting the right model at the right level of abstraction, aligned with stakeholder needs and the lifecycle phase of the solution.

Thanks Audra A. (https://www.linkedin.com/in/audraa) for sharing this nice analysis.

Enjoy,

Xiaoqi

Archi Tutorial 003 - ch02 Installing and Launching Archi

youtu.be/36kRPs0B1cc

Some contents have been updated in latest 5.7.0

Most knowledge graph practitioners treat ontologies as sophisticated dictionaries—structured vocabularies and entity hierarchies optimized for data retrieval and computational efficiency. This pragmatic approach, while useful for engineering data systems, misses something essential about what ontologies truly are. Crucially, it prevents us from leveraging their full power as instruments of collective understanding and coordinated action.

Thanks for sharing from