<img alt="dcsimg" id="dcsimg" width="1" height="1" src="//www.qsstats.com/dcsuuvfw300000gkyg9tnx0uc_3f7v/njs.gif?dcsuri=/index.php/c/a/Research/Data-Architecture-2002/8&amp;WT.js=No&amp;WT.tv=10.4.1&amp;dcssip=www.cioinsight.com&amp;WT.qs_dlk=XGjm0re6DlP0V8ZdSAmaogAAABQ&amp;">
 

Conclusion 05

By CIOinsight  |  Posted 07-19-2002 Print

Conclusion 05: Practices

Top IT execs demonstrate the importance of data architecture to them in part by how frequently they give it attention. They also make a statement about its importance by hiring professionals who can deal with it exclusively. But it isn't just IT that needs to focus on data architecture: By getting involved in defining business requirements that drive architectural choices, business units can have a substantial impact.

The top IT exec reviews data architecture issues quarterly or more frequently 62% of the time. But 28% of those surveyed say they look at data architecture issues once a year or less.

About 63% of our respondents say the business units at their organizations are extremely involved or involved in data architecture decisions. That number drops to 51% in organizations less satisfied with data access, versus 73% in more satisfied.

Only 44% of those surveyed keep data architecture professionals on their staffs—a pretty low percentage. But they're more frequently turned to in companies with more satisfied employees, 52% to 34%, indicating that their contributions to user satisfaction with data are significant.



 

Submit a Comment

Loading Comments...
eWeek eWeek

Have the latest technology news and resources emailed to you everyday.