How can you determine the appropriate level of abstraction for your enterprise software architecture?

I believe that though abstraction reduces the complexities but at the same time should not miss any information which is important for enterprise software architecture. So, abstract is the right balance between removing the complexities and keeping the information without which enterprise software architecture could be incomplete.

Abstraction is good technique but not a silver bullet and should carefully used, especially when communicated to stakeholders which may have different understandings depending on their roles and skills sets.

"Program to interfaces, not implementations" Start simple, don't try to create complex abstractions at first. Break down problems into smaller, manageable units. Focus on simplicity and clarity. Iterative & incremental development will help. It should be adaptable to changing requirements.Provide mechanisms for extension and modification without breaking the existing user interface. Aim for the right level of detail in your abstraction. Exposing too much of the internal workings can be confusing, while hiding too much can make it difficult to use.

Strive to strike a balance between simplicity and detail. Aim for an abstraction level that provides enough information to support decision-making and analysis, without overwhelming users with unnecessary complexity. Consider the cognitive load of the users and their familiarity with enterprise architecture concepts. Recognize that different stakeholders may require different levels of abstraction. For example, executives may need a high-level strategic view, while technical teams may require more detailed technical information. Tailor the abstraction levels to meet the specific needs of each stakeholder in the organisation

I believe employing iterative and incremental development should be used where Application Architecture or Solution Architecture are to be developed, for enterprise software architecture, all implemented software should be first understood and then carefully develop enterprise architecture before moving to make changes in system / systems.

Leverage industry standards and frameworks, such as TOGAF (The Open Group Architecture Framework) or ArchiMate, to guide your level of abstraction. These frameworks provide guidelines and best practices for structuring and representing enterprise architecture. Use visualization techniques, such as diagrams and models, to represent the enterprise architecture at different levels of abstraction. Visualizations can help users understand complex relationships and dependencies, facilitating effective communication and decision-making.