Started by ville_seppanen, November 06, 2021, 09:14:37 AM
QuoteHowever, due to (Archi's) current technical limitations (e.g., the lack of database repository, and multi-user support) it obviously has its shortcomings when considering more complex and demanding use cases akin to real-world EA modeling problems.
QuoteIn this regard, the students quite unanimously agreed that Archi was the easiest to learn, and also that the logic of Archi was the easiest to understand....students found Archi easier to learn and use than Arter Arc and Microsoft Visio. Furthermore, Archi was seen to more effectively facilitate the process of learning modeling than the other tools. We concluded that it is crucial for information technology students to understand the high level view, and to learn to model enterprise architecture landscapes with more than just one tool in order to facilitate deep understanding of modeling languages and convention.
QuoteFor the ability to support communication between the different EA stakeholders (e.g., business and IT), the otherwise well-evaluated Archi was assessed to perform quite poorly in this regard combined mean 1.95). This is probably due to its strong orientation towards the ArchiMate modeling, which students considered not being an optimal medium for communicating with business stakeholders.
QuoteArchi, on the other hand, is built on the ArchiMate metamodel and therefore allows a user to only create models that adhere to the standard (although there are some errors in the current implementation).
QuoteI can say for sure that there are (and were) no errors in Archi which implements strickly the ArchiMate specification (which turned out to be faulty in their 3.0 version and were corrected in the 3.0.1), so could you provide more information about these "errors" mentioned?