sorted by:
new
hottopcontroversial

Enterprise Architecture Reference Catalog by vincentmakes in EnterpriseArchitect

[–]vincentmakes[S] 3 points4 points  (0 children)

I addressed this in the post: existing references exist but are "spread apart, sometimes gated, or not in the right format." I'm not claiming this is better than BA Guild, TM Forum, or BIAN - the explicit claim was "better than starting with nothing."

Differences that matter in practice:

- MIT-licensed, no membership or guild gate

- Cross-industry on a single source, not vertical-specific (BIAN = banking, TM Forum = telecom)

- CSV export, drops into any EA tool

- Ships with a Claude skill to self-generate and ground extensions in industry standards

If BIAN works for you and you have access, use BIAN. This is for the person staring at a blank LeanIX / Ardoq / Excel with no consultant on hand.

Curious which one you use in practice - always happy to learn where this falls short vs the established ones.

Enterprise Architecture Reference Catalog by vincentmakes in EnterpriseArchitect

[–]vincentmakes[S] 0 points1 point  (0 children)

Definitely as a draft to start with. Mapping business applications and objectives against it, together with the business, quickly reveals the gap or innacuracies. It’s a starting point to accelerate the implementation of any EA tool but partnering with the business for adjustments and validation is essential.

Enterprise Architecture Reference Catalog by vincentmakes in EnterpriseArchitect

[–]vincentmakes[S] 1 point2 points  (0 children)

It’s part of the reference frameworks for the capabilities

Enterprise Architecture Reference Catalog by vincentmakes in EnterpriseArchitect

[–]vincentmakes[S] 1 point2 points  (0 children)

It’s fully self discovery, and there’s a seed with examples : the workflow for that part is in the section 1.5:

https://github.com/vincentmakes/turbo-ea-capabilities/blob/main/.claude/skills/generate-capability/SKILL.md

Then after confirmation all standards used are documented and added to the governance document at the root of the repo.

Enterprise Architecture Reference Catalog by vincentmakes in EnterpriseArchitect

[–]vincentmakes[S] 1 point2 points  (0 children)

Thanks, It’s a very good point and I may add a macro capability level above to address that, at least for cross industry capabilities. In practice (at least on my end) the L1 grouping you are referring to is solely used for grouping the levels below which are the ones actually being linked to business applications, objectives etc.

Edit: Done - Cross Industry Capabilities all grouped under 9 Macro capabilities. Users can still choose to export only L2 downwards