In my September 2001 column, I offered that data architecture was an orderly arrangement of parts to do four things: organize, store, access and move data. In this column, I want to look at this subject from a different perspective: the vantage point of the systems development life cycle (SDLC).

This exercise is important because people too rarely think comprehensively about the data-focused deliverables that a data architect needs to worry about. The documentation and activities are diverse and scattered, and few people bring them together and think about them as a set. Generally, a team's perspective is application-oriented; and unless we think more systematically, data architecture thinking risks becoming ad hoc and uncoordinated.

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