jump to navigation

BusinessObjects data quality XI January 17, 2008

Posted by Peter Benza in Data Accuracy, Data Analysis, Data Architecture, Data Assessment, Data Consolidation, Data Hygiene, Data Integrity, Data Profiling, Data Quality, Data References, Data Strategy, Data Templates, Data Tools.
Tags: , , ,
add a comment

Standardize, Identify Duplicates, Correct, Improve Match, Append, Consolidate, and more.    

http://www.businessobjects.com/products/dataquality/data_quality_xi.asp

Advertisements

SOA Governance At Bea: Essential to your enterprise transformation strategy January 17, 2008

Posted by Peter Benza in 1, Data Analysis, Data Architecture, Data Governance, Data Integration, Data Management, Data Optimization, Data Profiling, Data Security, Data Stewardship.
Tags: , ,
1 comment so far

Effective SOA governance is an essential element in any enterprise transformation strategy. It can help your organization achieve measurable, sustainable business value.

Read about this and other webcasts, whitepapers, etc… at Bea.

http://www.bea.com/framework.jsp?CNT=index.jsp&FP=/content/solutions/soa_governance/

SOA triggers innovation for your enterprise August 18, 2007

Posted by Peter Benza in Data Architecture, Data Processes, Data Tools.
add a comment

Say goodbye to those big applications and hello to function-specific services that IT departments can incorporate into their operating architecture with greater ease. 

This flexibility and re-design by vendors to package their solutions into bit-sized services also triggers innovation.  For example, as business requirements change both IT departments and vendors can be more responsive by offering a new service instead of waiting until the next product release.  IT can also win by telling management they are leveraging their current software asset (investment) with vendor XYZ.

What are some different ways your organizations data architecture can be illustrated? August 16, 2007

Posted by Peter Benza in Data Architecture, Data Security.
add a comment

One of the more common ways is with a data flow diagram.  A data flow diagram will allow the end-user to visualize the flow of data into four major sections – when it enters, when it is processed, when it is stored, and finally – utilized in the system.

This collection of diagrams represent the overall data architecture of your organization and useful when consolidating into a customer-centric single view.  Data architect’s are typically the creator’s or owners of this kind of information.  As a side note, the knowledge represented in a data flow diagram is sometimes summarized in a concept map.  A concept map is basically a data model of a data model.

You can also begin to see during this exhaustive excercise your organizations Intellectual Capital starting to being assembled and maybe even the foundation for some key data security policies and procedures to handling the same data.