> [!tldr] [[Simplicity]], needs over wants, people first, pointed > [!quote] > **Key risk for any standard**: It is the responsibility of the experts working on the standards to manage the desires and edge cases of specialists to prevent ***feature bloat***, which can harm the usability for regular users and eventually lead to its demise. To prevent this, we wrote the ***ArchiMate Manifesto*** years ago: > - Simplicity over Comprehensiveness > - Needs of the Many over the Wants of the Few > - Collaboration over Coverage > - People over Tools > - Communication Architecture over Other Use Cases **Simplicity over comprehensiveness** The most important design consideration is that the language has been explicitly designed to be as small as possible, but still usable for most Enterprise Architecture modeling tasks. Many other languages try to accommodate the needs of all possible users. In the interest of simplicity in learning and use, the ArchiMate language has been limited to the concepts that suffice for modeling the “80%” of practical cases. **• Needs of the many over wants of the few** Any change to the language shall cover a clearly identified and important use case of a substantial part of its users. In line with the previous principle, keeping things simple for the “80%” is more important than catering for the wants of the “20%”. **• Collaboration over coverage** If a need is already covered sufficiently by another modeling language, it is preferred to create a mapping to that language rather than incorporate those features into the ArchiMate Specification; for example, where a detailed software design model is better written in Unified Modeling Language™ (UML®), the ArchiMate application component concept can be used to map between both models. **• People over tools** Understandability is key. The language was designed for communication among human users rather than for technical usage. There are many more technical languages already and, in line with the previous principle, the ArchiMate Specification should work together with those rather than try to cover their scope and level of detail too. **• Communicating architecture over other use cases** The ArchiMate language was designed first and foremost to support communicating (enterprise) architecture. Accommodating other use cases should not get in the way of this key use case. **** # More ## Source - [[Archimate 4.0]] White Paper - https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.youtube.com/watch%3Fv%3DiqOdWnZzsxs&ved=2ahUKEwixpLid_dGTAxVnnGoFHXmMI6YQwqsBegQIPRAB&usg=AOvVaw0neDL6-sENF24MdF5TRrg3