I have mentioned in prior blogs my belief that an enterprise architecture is comprised of 3 intertwined components; standards, governance, and a repository of binaries. I will address standards and binaries later.
For now, I will focus on the concrete manifestation of governance.
Governance differs from standards in 2 important ways;
For example, the preferred development in the enterprise language might be C++, but applications written in C# or visual basic would be equally consumable by users. Making development language a clear candidate as a standard. Conversly. maintaining a measurably high level of security in an environment is a candidate for governance. Applications either are or are not meeting the security metrics.
I like to think of good governance as those policies focused on the management of shared resources as well as policies which provide safety and security to the participating applications in the enterprise.
For kicks, here are a few more candidate governance items;
The devil, as they say, is in the details. Creating and issuing governance for an enterprise requires carefully crafting statements without ambiguity yet reasonable enough to be implemented.