|
Aggregation rule
A rule for resolving duplicate entities or combining separate entities in some domain. The process might consist of selecting or combining entities from a set of duplicate candidates, possibly from different data sources, based on given rules or preferences. For example, an aggregation rule might specify how to derive a person's name from two data values that represent the name in different formats.
Business Integrity
The validity of data based upon business rules; conformance of a document's semantics to a particular set of business standards or processes. A document may have format integrity but may fail to represent the intended semantics of a business process.
Business Process Rule
A rule for evaluating some condition to answer a question posed by a business process. For example, a business process might ask, "Is the customer's address valid?" DataXtend SI shared data services would apply a set of specific rules defined by an analyst to the customer data and return an answer to the business process.
Class Map
A specification of correspondences between properties of one class and properties of another class. A class map contains a set of transformations.
Common Model
A model that represents the semantic structure that is common to multiple data sources and data services. Maps define correspondences between the common model's domain schema and the schemas in data sources and data services.
Data Service
A model that is deployed as a runtime service interacting with the business process. A data service has operations, which constitute its interface to the business process.
Data Source
A model that represents a set of data used by a business application. A data source can be a relational database, an XML file, a Java class, or other repository. A data source can also be an XML message via a Web service call or even a call to a method (represented as a Java control in BEA WebLogic Workshop).
DataXtend SI
enables business analysts, architects and developers to create, maintain and govern common-model-based data services in a service-oriented architecture (SOA). These services enable enterprises to reduce the complexity and cost of their SOA implementations while improving agility.
DataXtend SI Designer
A set of tools, integrated with Eclipse, that enable an analyst to import and create components of an exchange model and to deploy the resulting model as a set of shared data services.
DataXtend SI Engine
A collection of shared data services and the information and ancillary services that they need to operate at runtime. The DataXtend SI Engine includes logging services and a metadata repository that contains schemas, maps, and rules.
DataXtend SID Model Browser
Jump-start your learning about TM Forum's Shared/Information Data (SID) Model and speed your organization's adoption of this important industry standard. DataXtend SID Model Browser is a read-only version of DataXtend SI that contains the SID preloaded as the common data model. You will be able to use the SID Model Browser to gain an understanding of the structure and details of the SID.
Domain Schema
A specialized schema that an exchange model uses to describe the common model and possibly data services and data sources. A domain schema is often based on an industry-standard schema, such as ACORD for insurance or MISMO for mortgages. Although a domain schema may be derived from an XML schema, it uses DataXtend SI-specific types, properties, relationships, and rules to define the structure of a model.
Exchange Model
A representation of the semantic relationships between business processes and data, mediated by an intervening common layer. An exchange model has three corresponding tiers: data services, data sources, and a common model. Each tier is described by one or more models. The tiers are connected to each other by maps. Within each tier, maps can connect components, and rules can constrain them.
Expression Builder
A component of DataXtend SI Designer that provides a graphical interface for constructing expressions used in rules and transformations.
Format Integrity
Conformance of a document's syntax to a particular grammar. For example, an XML Schema validator that tests whether a document conforms to a given XML Schema definition measures the document's format integrity.
Integration Tax 
Technologists refer to the cost associated with bringing systems together as an integration tax. We believe that by deploping a common information model that will mediate data transfers and ensure data consistency across legacy, and new, systems, the enterprise will reduce their integration tax.
Metadata
Data that describe or accompany other data. DataXtend SI uses metadata at design time to describe components of the exchange model. It uses metadata at runtime to configure and manage the operation of data services. An analyst can incrementally redefine and redeploy components of the metadata, such as rules, without redeploying the services themselves.
Model
A component of any of the three tiers of the exchange model. A model is based on one or more schemas, and it can contain rules, relationships, and other elements.
Model map
A specification of correspondences between schemas in two models. A model map contains a schema map.
Operation
An externally visible procedure performed by a model, including input parameters and return values. A set of operations constitutes the model's interface.
Project
Contents of a DataXtend SI application component, including data sources, data services, the common model, schemas, schema and class maps, rules, and other information.
Rule
A predicate, constraint, or preference used to transform, validate, or aggregate data or to answer questions posed by business processes at runtime.
Schema
A specification of the structure of a set of objects, typically describing data types, elements, and attributes. The objects might be XML documents, Java instances, or data in a database. For XML representations, the schema type might be XML Schema or a document type definition (DTD). Java classes can often be generated from type definitions in an XML schema or from tables in a database schema.
Schema map
A specification of correspondences between classes defined by one schema and classes defined by another schema. A schema map contains a collection of class maps.
Semantic Integration
The process of using business semantics, or a common model, to automate the communication between systems and web services. Semantic integration focuses on the meaning of data that extends across the enterprise. Read more about semantic data integration.
Semantics
The meaning or interpretation of a production; often contrasted with syntax or form. Two productions that refer to the same object, action, or concept may have different syntax but similar semantics. For example, the name "John Smith" has the same semantics as the name "Smith, John" if the two names refer to the same person.
Shared Data Services
A set of services that use a deployed exchange model to associate business processes with data. Shared data services typically use maps and rules to combine data or enforce the integrity of data through processes such as aggregation and validation. In essence, DataXtend SI shared data services enforce contracts, defined by an exchange model, between business processes and data.
SID Model
The TM Forum's Shared Information/Data (SID) model provides a common vocabulary for Operational and Business Support Systems (OSS/BSS) that creates a bridge between the business and IT, which then simplifies the integration of IT systems. Using the SID Model can help you realize business benefits that create value for your customers and directly affect your bottom line. The DataXtend SID Model Browser can jump-start your learning about the SID and speed your organization's adoption of this important industry standard.
TM (Telemanagement) Forum
TM Forum is an industry association focused on transforming business processes, operations and systems
for managing and monetizing on-line Information, Communications and Entertainment services. Visit tmforum.org.
Transformation Rule
A rule for deriving one or more properties of a class (the target class) from one or more properties of another class (the source class). For example, a transformation might convert a value from one unit of measurement to another.
Validation Rule
A rule for ensuring that data meets given constraints, generally defined by schemas. For example, if a schema declares that an attribute must have one of three values, a validation rule can test whether the attribute has one of these values at runtime.
| 
Evaluate DataXtend SI