extending ArchiMate meta model introducing "composite" and "containment" patterns: the problem here is that it should be done through the Open Group standardization process, which can be time consuming but also not obvious, as it will go against the requirement consisting in making ArchiMate simpler enough for discussion with non specialist and people not used to modelling.not using ArchiMate but other open standard for Enterprise Modelling: assessment of other enterprise modelling standard didn't allow to find a suited standard for blueprinting, as ArchiMate is. " Advanced usage of ArchiMate for Dynamic Manufacturing Living Lab"), I really missed support of "composite" and "containment" patterns by ArchiMate. Unfortunately, when using ArchiMate for creation of blueprint of PLM Manufacturing Digital Business Ecosystem or Digital Manufacturing Networks (cf. Finally, as aiming at supporting collaboration of the different kind of architects impacting the information system accuracy with the motivation of the enterprise, it relies on viewpoints, as defined by ISO/IEC/IEEE 42010:2011, Systems and software engineering - Architecture description. The underlying modelling patterns don't include the "composite" and "containment" patterns, which are more difficult to understand for those who don't model. In order being easily useable, without having the same learning curve than other specialised modelling languages such as UML (Software Architects and Engineers), SysML (System Engineering) or BPMN (Business Process Architect), the choice was made at the origin not to provide too much modelling constructs: about 60 for ArchiMate, 150 for BPMN and 250 for UML. " PLM interoperability: the potential of ArchiMate viewpoints" ) makes ArchiMate not only a modelling language, but a framework suitable for addressing the strategic nature of PLM interoperability manufacturing standards. GanttProject, as illustrated in the " Project management and ArchiMate viewpoints". It is a very good complement to project management tools (e.g. Strength and weakness of ArchiMateįor those following me and who had a look at my previous post, ArchiMate is really suited for blueprinting. But something was missing in order taking advantage of the results of this framework: an open standard for enterprise modelling. It became obvious for me after reading " The Enterprise Architecture IT Project: The Urbanisation Paradigm" by Christophe Longépé, which motivated my involvement in the development of the ATHENA framework. The reason: such standards are considered by many as technical solutions, when they should be considered as strategic solutions for mastering the evolution and consistency of enterprises' information system. After demonstrating the technical feasibility, I witnessed an important resistance for their usage, resulting in a very slow adoption. I've been working on PLM (Product Lifecycle Management) interoperability based on the usage of open manufacturing standards for years. If you like this post, don't hesitate to share and to validate my skills -) Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |