The best software to define enterprise architecture, easy to use and easily customizable
Use Cases and Deployment Scope
<p>Today Mega is used to map processes, create connectionions between process and business services and from between business services and applications. In the future, we are planning to connect applications and infrastructure. We are using TOGAF, Process, architecture and we plan to use strategic and data governance modules. From MEGA, we generate a web site, the service catalog accessible by our client end partners.
</p><p>
</p>
Pros
- Define business architecture
- Design processes
- Tailoring business services attributes
Cons
- API for external use
- Query engine (join between metaclass)
- Export tools
- Web site generator
Likelihood to Recommend
MEGA is well suited for
<ul><li>Service Architecture definition</li></ul><ul><li>Service relationships</li></ul><ul><li> Service that supports process and vice versa</li></ul><ul><li> Business process definition</li></ul><ul><li>Definition of Business Entities</li></ul><ul><li>Management of business entities</li></ul><ul><li>Business Entity managed by services</li></ul><ul><li> Creation of service reports</li></ul>
MEGA is less appropriate for:
<ul><li>Business Service management information (who is “developing, responsible, etc.” for business services)</li></ul><ul><li>Business services contracts</li></ul><ul><li> Business services performance management</li></ul>
