Google

Check Out These!!

Please check out posts at my other blogs too!!!



iNsAnItY iNtEnSiFiEdiNsAnItY iNtEnSiFiEd
My Tech Blog

Monday, August 13, 2007

Responsibilities of the information architect

Acknowledgment : http://searchdatamanagement.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid91_gci1267010_tax302190,00.html?track=NL-520&ad=600164&asrc=EM_USC_1978746&uid=5505931

QUESTION POSED ON: 03 August 2007
What are the typical responsibilities of an information architect? The aim is to have the information architect form part of the business intelligence team, and that this person will also have insights to our IT strategy.

>
EXPERT RESPONSE
Historically, information architects were responsible for the design and usability of Web sites and other software applications. More recently, we are beginning to think of information architects as the coordinators of information flow through the enterprise. This view encompasses much more than the user experience of a particular application. This information architect is responsible for modeling all applications across the enterprise and the logical data flows between them. In this sense, the information architect is an integral part of the business intelligence (BI) team, but their focus includes more than the BI and data warehouse components alone. I agree that this person should have insight into the IT strategy. In fact, the information architect should be partly, if not entirely, responsible for it. Information architecture, these days, spans disciplines of data warehousing, business intelligence, master data management, enterprise information integration (EII) and others.

I would list the following as the high level responsibilities for the information architect:

1. Responsible for expressing the enterprise vision for the applications and the data flows between them
2. Responsible for modeling and maintaining the enterprise data models
3. Responsible for extending the data models to the application architecture
4. Responsible for coordinating the integration and service-oriented architecture (SOA) between applications

No comments: