With a formal governance board and documented decisions it would be useful to include these within MEGA with links to designs. How are these best represented in MEGA, should they be documented as standards, requirements or something else? Do you import (or copy and paste) the decisions or just link out to a file based repository?
On Mega International LinkedIn page they mention "We have developed a unique set of enterprise governance software".
- Where could I find overview information what this contains?
- How is it related to Cobit framework?
I actually have sent this question to Mega University manager via LInkedIn, but he has not replied yet.
Does any of you (the community members) know the answer?
We created a custom "Finding" MetaClass, that could be assigned to different objects in the repository, like an Application, or a Project, based on the context. Custom MetaAttributes allow us to capture the type/source of the finding, data, expected resolution date, etc.
We have worked at MEGA to be able to provide a global Architecture Framework, embedding:
Please find below a global view of this framework.
I believe that your question is in regard to EA Governance Repository that is today included in MEGA HOPEX.
We provide :
All these mechanism are standard in HOPEX, as we also have a focus on the governance repository.
Specifically for your request,
All these mechanism are of course linked to every object, so the link to the object is made automatically.
That sounds great. How do we get started to use it. Is there any documentation, what version of the product does it apply to and are there any online tutorials.