• Common vision
• Flexibility and extensibility
• Model system behavior using principles of OOAD
• Consistency and risk mitigation
• Successful management of artifacts
• Interactive knowledge base and communication
  

The benefits of standardization have given us Unified Modeling Language (UML) and defines twelve types of diagrams to model with, representing static application structure, aspects of dynamic behavior, and ways you can organize and manage your application modules, otherwise known as: Structural Diagrams, Behavior Diagrams, Model Management Diagrams.

1) ETM will help you select a methodology: A methodology formally defines the process that you use to gather requirements, analyze them, and design an application that meets them in every way. There are many methodologies, each differing in some way or ways from the others. There are many reasons why one methodology may be better than another for your particular project: For example, some are better suited for large enterprise applications while others are built to design small embedded or safety-critical systems. On another axis, some methods better support large numbers of architects and designers working on the same project, while others work better when used by one person or a small group. 

2) ETM will help you select a UML Development Tool: Because most UML-based tools implement a particular methodology, in some cases it might not be practical to pick a tool and then try to use it with a methodology that it wasn't built for.