Data and information visualization: Difference between revisions

Revision as of 22:30, 25 February 2009

Revision as of 20:38, 9 March 2009

Line 61:

It has been described as "the nontrivial extraction of implicit, previously unknown, and potentially useful [[information]] from [[data]]"<ref>{{cite journal |author=W. Frawley and G. Piatetsky-Shapiro and C. Matheus |title=Knowledge Discovery in Databases: An Overview |journal=AI Magazine |date=Fall 1992 |pages=pp. 213–228 |id={{ISSN|0738-4602}}}}</ref> and "the science of extracting useful information from large [[data set]]s or [[database]]s."<ref>{{cite book |author=D. Hand, H. Mannila, P. Smyth |title=Principles of Data Mining |publisher=MIT Press, Cambridge, MA |year=2001 |isbn=0-262-08290-X}}</ref> Data mining in relation to [[enterprise resource planning]] is the statistical and logical analysis of large sets of transaction data, looking for patterns that can aid decision making.<ref> {{cite book |author=Ellen Monk, Bret Wagner |title=Concepts in Enterprise Resource Planning, Second Edition |publisher=Thomson Course Technology, Boston, MA |year=2006 |isbn=0-619-21663-8}}</ref>

=== Data modeling ===

[[Image:4-3 Data Modelling Today.jpg|320px|thumb|The data modeling process.]]

[[Data modeling]] in [[software engineering]] is the process of creating a data model by applying formal data model descriptions using data modeling techniques. Data modeling is a technique for defining business [[requirement]]s for a [[database]]. It is sometimes called ''database modeling'' because a data mode] is eventually implemented in a database.<ref name= "WBD04"> Whitten, Jeffrey L.; Lonnie D. Bentley, Kevin C. Dittman. (2004). ''Systems Analysis and Design Methods''. 6th edition. ISBN 025619906X.</ref>

The figure illustrates the way data models are developed and used today. A [[conceptual data model]] is developed based on the data [[requirements]] for the application that is being developed, perhaps in the context of an [[activity diagram|activity model]]. The data model will normally consist of entity types, attributes, relationships, integrity rules, and the definitions of those objects. This is then used as the start point for interface or database design.<ref name="MW99"> Matthew West and Julian Fowler (1999). [http://www.matthew-west.org.uk/documents/princ03.pdf Developing High Quality Data Models]. The European Process Industries STEP Technical Liaison Executive (EPISTLE).</ref>

== See also ==