Because [[Enterprise Architecture]] is a fairly vague and fuzzy thing, there are a lot of arguments to be made about what does or does not constitute EA. [[Svyatoslav Kotusev]] says enterprise architecture is often confused with the following: > [!warning] Enterprise Architecture is **NOT**... > - purely technical planning > - a one-size fits all method > - automated planning > - a substitute for competence > - the work of dedicated experts (you need business & IT stakeholders, not _only_ EA people) > - a one-time planning project > - technology-specific (you can use any sort of technology to implement an EA) > - enterprise modeling (modeling may be a _part_ of it, but it's the communication piece & also many artifacts aren't model-based) > - enterprise engineering (in that it's not meant to achieve results via sophisticated calculations, which never really work out) > - [[Systems Thinking]] (again, it's _helpful_, but systems thinking doesn't involve the soft skills & collab necessary) > - a breakthrough solution (it won't magically fix all problems, it helps with [[IT-Business Alignment]]) > - a simple application of [[Enterprise Architecture Frameworks]] (which don't work) **** # More ## Source - [[The Practice of Enterprise Architecture]] ## Related