c
c

 
 
 


u
   



 

The technical architecture of data warehouses is somewhat similar to other

systems, but does have some special characteristics. There are two border areas in
data warehouse architecture - the single-layer architecture and the N-layer
architecture. The difference here is the number of middleware between the
operational systems and the analytical tools. The data warehouse architecture
described here is a high level architecture and the parts in the architectures
mentioned are full bodied systems and not system-parts.







aÊ The art and science of designing and erecting buildings and other physical
structures.
aÊ The practice of an architect, where architecture means to offer or render
professional services in connection with the design and construction of a
building, or group of buildings and the space within the site surrounding the
buildings, that have as their principal purpose human occupancy or use.[1]
aÊ  general term to describe buildings and other structures.
aÊ  style and method of design and construction of buildings and other
physical structures.

Ê
u 
rom Wikipedia, the free encyclopedia
Jump to: navigation, search

Data Warehouse Intelligence is a general term to describe a system used in an

organization to collect data, most of which are transactional data, such as purchase
records and etc., from one or more data sources, such as the database of a
transactional system, into a central data location, the Data Warehouse, and later
report those data, generally in an aggregated way, to business users in the
organization. This system generally consists of an ETL tool, a Database, a
Reporting tool and other facilitating tools, such as a Data Modeling tool.

    (DW) is a database used for reporting. The data is offloaded

from the operational systems for reporting. The data may pass through an
operational data store for additional operations before it is used in the DW for
reporting.

 data warehouse maintains its functions in three layers: staging, integration, and
access. 
 is used to store raw data for use by developers (analysis and
support). The  
 layer is used to integrate data and to have a level of
abstraction from users. The
 layer is for getting data out for users.

This definition of the data warehouse focuses on data storage. The main source of
the data is cleaned, transformed, catalogued and made available for use by
managers and other business professionals for data mining, online analytical
processing, market research and decision support (Marakas&OBrien 2009).
However, the means to retrieve and analyze data, to extract, transform and load
data, and to manage the data dictionary are also considered essential components
of a data warehousing system. Many references to data warehousing use this
broader context. Thus, an expanded definition for data warehousing includes
business intelligence tools, tools to extract, transform and load data into the
repository, and tools to manage and retrieve metadata.

[  

[c 
  [c
  refers to a (generally IT based)
system for managing knowledge in organizations for supporting creation, capture,
storage and dissemination of information. It can comprise a part (neither necessary
nor sufficient) of a Knowledge Management initiative.

The idea of a KM system is to enable employees to have ready access to the

organization's documented base of facts, sources of information, and solutions. or
example a typical claim justifying the creation of a KM system might run
something like this: an engineer could know the metallurgical composition of an
alloy that reduces sound in gear systems. Sharing this information organization
wide can lead to more effective engine design and it could also lead to ideas for
new or improved equipment.

 KM system could be any of the following:

1.Ê Document based i.e. any technology that permits

creation/management/sharing of formatted documents such as Lotus Notes,
web, distributed databases etc.
2.Ê Ontology/Taxonomy based: these are similar to document technologies in
the sense that a system of terminologies (i.e. ontology) are used to
summarize the document e.g. uthor, Subj, Organization etc. as in DML
& other XML based ontologies
 å.Ê Based on I technologies which use a customized representation scheme to
represent the problem domain.
4.Ê Provide network maps of the organization showing the flow of
communication between entities and individuals
5.Ê Increasingly social computing tools are being deployed to provide a more
organic approach to creation of a KM system.

KMS systems deal with information (although Knowledge Management as a

discipline may extend beyond the information centric aspect of any system) so they
are a class of information system and may build on, or utilize other information
sources. Distinguishing features of a KMS can include:

1.Ê Purpose: a KMS will have an explicit Knowledge Management objective of

some type such as collaboration, sharing good practice or the like.
2.Ê Context: One perspective on KMS would see knowledge is information that
is meaningfully organized, accumulated and embedded in a context of
creation and application.
å.Ê Processes: KMS are developed to support and enhance knowledge-intensive
processes, tasks or projects of e.g., creation, construction, identification,
capturing, acquisition, selection, valuation, organization, linking, structuring,
formalization, visualization, transfer, distribution, retention, maintenance,
refinement, revision, evolution, accessing, retrieval and last but not least the
application of knowledge, also called the knowledge life cycle.
4.Ê Participants: Users can play the roles of active, involved participants in
knowledge networks and communities fostered by KMS, although this is not
necessarily the case. KMS designs are held to reflect that knowledge is
developed collectively and that the ³distribution´ of knowledge leads to its
continuous change, reconstruction and application in different contexts, by
different participants with differing backgrounds and experiences.
5.Ê Instruments: KMS support KM instruments, e.g., the capture, creation and
sharing of the codifiable aspects of experience, the creation of corporate
knowledge directories, taxonomies or ontologies, expertise locators, skill
management systems, collaborative filtering and handling of interests used
to connect people, the creation and fostering of communities or knowledge
networks.
 KMS offers integrated services to deploy KM instruments for networks of
participants, i.e. active knowledge workers, in knowledge-intensive business
processes along the entire knowledge life cycle. KMS can be used for a wide range
of cooperative, collaborative, adhocracy and hierarchy communities, virtual
organizations, societies and other virtual networks, to manage media contents;
activities, interactions and work-flows purposes; projects; works, networks,
departments, privileges, roles, participants and other active users in order to extract
and generate new knowledge and to enhance, leverage and transfer in new
outcomes of knowledge providing new services using new formats and interfaces
and different communication channels.

The term KMS can be associated to Open Source Software, and Open Standards,
Open Protocols and Open Knowledge licenses, initiatives and policies.


  
n 
   is software that attempts to provide an answer to a problem, or
clarify uncertainties where normally one or more human experts would need to be
consulted. Expert systems are most common in a specific problem domain, and are
a traditional application and/or subfield of artificial intelligence (I).  wide
variety of methods can be used to simulate the performance of the expert; however,
common to most or all are: 1) the creation of a knowledge base which uses some
knowledge representation structure to capture the knowledge of the Subject Matter
Expert (SME); 2) a process of gathering that knowledge from the SME and
codifying it according to the structure, which is called knowledge engineering; and
å) once the system is developed, it is placed in the same real world problem
solving situation as the human SME, typically as an aid to human workers or as a
supplement to some information system. Expert systems may or may not have
learning components.

Expert systems were introduced by researchers in the Stanford Heuristic

Programming Project, including the "father of expert systems" Edward
eigenbaum, with the Dendral and Mycin systems. Principal contributors to the
technology were Bruce Buchanan, Edward Shortliffe, Randall Davis, William
vanMelle, Carli Scott, and others at Stanford. Expert systems were among the first
truly successful forms of I software. [1][2][å][4][5][6]

The topic of expert systems also has connections to general systems theory,
operations research, business process reengineering, and various topics in applied
mathematics and management science.