TOGAF Tool: Towards Customization

There is a need for a standardized and coherent instrumentation to every enterprise that utilizes architecture framework. Architecture domains such as business, data, applications, and technology should have metamodels and should be developed by architecture teams. Then, the end results which are architecture views and models need to be organized and be controlled to achieve customization.

Architecture practitioners should be aware that there two primary options in seeking tools to be used. It could be a single tool which is described as a tool that fits it all and a multi-tool which generates various architecture views.

Well since TOGAF has a wide range of knowledge in architecture frameworks it prefers to not to require or advocate specific tool. Nevertheless to address the dilemma of standardization, TOGAF architecture tool proposals that can be developed by individual enterprises which will cater particular needs and requirements that the enterprise necessitates.

Nonetheless, deciding which tool will be used, whether single tool or multi-tool it is as equally important as knowing what makes up these two tools so that there will be a greater understanding between the two.

The perceived advantages and benefits for a single tool are: reduced training, quantity discounts, shared licenses, maintenance and easier data trade-off. However for the disadvantages, there wouldn’t be any challenge for competition in commercial advancement since a single tool doesn’t encourage different architecture developments and there would be intricate undertakings just to comply with the needs of the whole organization.

As for the multi-tool the generation and creation of various architecture models and views seem to be infinite thus will absolutely encourage more competitions and advancement of the tools capabilities.