![]() It then proposes some improvement we should expect concerning the ArchiMate specifications or implementations in order to achieve the targeted operational interoperability between Enterprise Modeling applications based on ArchiMate.įinally, it will propose a test data set and an approach for testing interoperability. Evolution of the ArchiMate language and associated specifications.The strategies adopted by modeling solution providers supporting ArchiMate with several other languages, etc.The strict compliance with the specifications (if not under specified),.The physical breakdown (or organization) of an ArchiMate model,.With an open specification of a simple language delivered by a mature community, and an open format for interchange, some may think that interoperability between software products implementing ArchiMate and import/export based on this open format is something acquired.īased on simple and concrete examples, this article will show that it is not so easy when considering different issues, such as: And don't hesitate reflecting my skills on my LinkedIn profile if you think it is appropriate :) Introduction If you think this article creates value, don't hesitate to share it and like it. What do we learn from exchange format schemas study?ĭon't hesitate sharing you comments, knowledge, viewpoints and experience/best practices on the topic. ![]() From models to linked data using semantic web technologies?.Potential issues illustrated with practical cases with Archi, EA, Modelio (this article).This is the first article of a series about ArchiMate Interoperability, which includes:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |