Home > Ask the Data management / BI Experts > Data architecture / Data modeling Questions & Answers > Data architect vs. application architect: Segregate the duties
Ask The Data Management Expert: Questions & Answers
EMAIL THIS

Data architect vs. application architect: Segregate the duties

Pete Stiglich EXPERT RESPONSE FROM: Pete Stiglich

Pose a Question
Other Data Management Categories
Meet all Data Management Experts
Become an Expert for this site


Enterprise IT tips and expert advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 29 July 2008
I have been asked to provide justification for a data architect to do the XSD modeling of data entities. I have prepared the Conceptual Entity Model and have elaborated on each entity (attributes and attribute properties) in a spreadsheet. The application architect has now requested that I help develop the XSDs for the model and also that I be the data architect and take ownership. The senior enterprise architect, though, believes that this responsibility is that of the application architect. What is your suggestion in this matter?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



RELATED CONTENT
Data architecture / Data modeling
Enterprise versus project level conceptual data modeling
XML schema definition versus conceptual data model
Data model conversion: Conceptual design to logical design using an ER model
Four guidelines for enterprise conceptual data model (ECDM) entity selection
Data modeling for data warehouse projects
Data architecture vs. information architecture
What are the benefits of a conceptual data model?

Data modeling tools and techniques
Understanding five major enterprise information management benefits
Data modeling concepts: How settings can increase application success
Advantages and disadvantages of XML shredding
How to shred XML with the DB2 XMLTABLE function
Shredding XML docs into relational tables with annotated XML schemas
Examples of single and bulk XML shredding of XML documents
Improving ODBC application performance and coding
How to capture metadata information, ETL rules with CA Erwin Data Modeler
Data Warehouse Platforms Product Directory
Data models serve as blueprint for business intelligence, master data management projects

Enterprise data architecture best practices
Advantages and disadvantages of XML shredding
How to shred XML with the DB2 XMLTABLE function
Shredding XML docs into relational tables with annotated XML schemas
Teradata takes a logical approach to data warehousing appliances
Examples of single and bulk XML shredding of XML documents
What is the difference between a logical and physical warehouse design?
What are some emerging data warehouse and DBMS trends?
Teradata VP talks data warehouse appliances, reveals cloud and SSD plans
Selecting ODBC functions for optimized SQL statements
Guidelines for managing data updates to optimize ODBC performance

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
data modeling  (SearchDataManagement.com)
predictive modeling  (SearchDataManagement.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


Would an application architect be responsible for designing a database implemented on a DBMS platform? The answer is almost always no. In the same manner, an application architect should not be responsible for designing an XML data store (whether that data store persists for seconds or months). The data architect's duties are to thoroughly understand the data (whether at rest or in transit), ensure that it is used correctly and securely, ensure that it meets business requirements and ensure that the models have sufficient semantic meta data (business meta data). The data architect must also ensure conformity to data standards, identify opportunities for reuse, and help to ensure that data, an enterprise asset, is properly leveraged (ideally, in conjunction with a Data Governance program).

In short, the data architect should be an objective third party, somewhat independent of the application team who is empowered with oversight and design of the data in the application. Just as an application architect is expected to be well-versed in software architecture, programming languages, programming methodologies, so must the data architect specialize in the field of data and meta data. There is usually too much involved to have one person be responsible for delivering a robust, scalable, reusable, high quality data architecture AND deliver a robust, high performance, high-quality application at the same time.

More information about data architecture and the duties of data architects




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2005 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts