What is enterprise governance anyway- April 28, 2004 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; While standards provide well known boundaries within which applications are expected to stay, standards will change and applications are.http://blogs.msdn.com/stcohen/archive/2004/04/28/122485.aspx Should an application architecture be forced to comply with the enterprise I think not.- April 22, 2004 Most of us can agree that there is always more than one way to achieve a given piece of functionality. Consider getting a phone number for a person from a Sql database. You can connect with integrated security, or pass in the username & password, or maybe implement application roles within the database. Once connected, you can pass in a fully formed SQL statement, execute a stored procedure, or make a direct http get against a named template file. Finally, how will you package...http://blogs.msdn.com/stcohen/archive/2004/04/22/118335.aspx The life of a living (enterprise architecture) document- April 15, 2004 A common phrase used to describe an enterprise architecture is a set of &8220;living documents&8221;. I like it. Short, simple, easy to understand &8230; a living document. Of course there is a dangerously complex implication lying just below the veneer of this simple metaphor. Living implies change and growth. It would seem to need to be feed and cared for. Most importantly it begins as an immature child and develops into a mature contributor to its...http://blogs.msdn.com/stcohen/archive/2004/04/15/113881.aspx |