Enterprise architecture demands the collection, definition and management of a wide range of complex sets of information. Users need business-centric information, including business goals, mission statements, vision and direction. They also need more detailed information like business requirements and business process definitions. All this business-centric information must be aligned to the IT it supports in the form of technical metadata, data about systems and technologies. Many organizations will face unique and different sets of standards, regulations, and environmental and technological considerations, meaning that the details needed for each organization will be unique and diverse.

Simply having the definitions and descriptions of all the elements of the enterprise architecture is a good start, but users also need to relate dependent artifacts. What requirements fulfill what parts of a business strategy, or what parts of the information back end are fulfilling what concepts of information movement? And who decides how it all relates?

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access