Figure 4 - uploaded by Philip Henderson
Content may be subject to copyright.
![XML modeler XML document. It contains information similar to the Abstract Constraint Model. The XML document represents a domain model and contains information similar to the Product Constraint Model. In choosing XML processing API, we investigated standard models of SAX and DOM, and java language specific models of dom4j. SAX (Simple API for XML) provides an event-based framework for parsing XML data. However, it only provides access to the XML data and does not support creating a XML document. On the other hand, DOM (Document Object Model) is the official W3C standard for representing XML documents in a platform and language neutral manner. It is designed to provide a means of manipulating XML data. The DOM model makes heavy use of interfaces and inheritance for the different components of an XML document. This provides the advantage of using a common interface, but it also adds some complexity to the API. The java API dom4j provides an ease of use solution for Java development by making use of common Java components such as the Collections classes. It also supports XTSL integration. According to [10], dom4j has the performance advantage over DOM implementations. Therefore, the java model dom4j is chosen as our XML document processing API.](profile/Philip-Henderson-5/publication/44092625/figure/fig2/AS:669564538998784@1536648034048/XML-modeler-XML-document-It-contains-information-similar-to-the-Abstract-Constraint.png)
XML modeler XML document. It contains information similar to the Abstract Constraint Model. The XML document represents a domain model and contains information similar to the Product Constraint Model. In choosing XML processing API, we investigated standard models of SAX and DOM, and java language specific models of dom4j. SAX (Simple API for XML) provides an event-based framework for parsing XML data. However, it only provides access to the XML data and does not support creating a XML document. On the other hand, DOM (Document Object Model) is the official W3C standard for representing XML documents in a platform and language neutral manner. It is designed to provide a means of manipulating XML data. The DOM model makes heavy use of interfaces and inheritance for the different components of an XML document. This provides the advantage of using a common interface, but it also adds some complexity to the API. The java API dom4j provides an ease of use solution for Java development by making use of common Java components such as the Collections classes. It also supports XTSL integration. According to [10], dom4j has the performance advantage over DOM implementations. Therefore, the java model dom4j is chosen as our XML document processing API.
Source publication
This paper presents an approach for engineer-to-order product configurations where configuration problems are represented as constraint satisfaction problem (CSP) with n-ary constraints and variables with both discrete and continuous domains. Search space is considerably reduced by using controllable variables that are independently assigned with v...
Context in source publication
Context 1
... the user may supplement more information on constraints interactively through GUI. In this scenario, XML Adapters (Figure 4) can be designed to convert information from database into a XML document, as long as the conversion conforms to a XML schema defined for the product constraint model. In essence, the main purpose of the XML modeler is to generate XML files for defining variables and constraints. ...
Similar publications
This paper presents a new analysis of dynamic con- straint satisfaction problems (DCSPs) with finite domans and a new approach to solving them. We first show that even very small changes in a CSP, in the form of addition of constraints or changes in constraint relations, can have profound effects on search performance. These effects are reflected i...
We present a general algorithm which gives a uniform view of several state-of-the-art systematic backtracking search algorithms for solving both binary and nonbinary CSP instances. More precisely, this algorithm integrates the most usual or/and sophisticated look-back and look-ahead schemes. By means of this algorithm, our purpose is then to study...
Using a distributed constraint satisfaction problem (DCSP) model of distributed problem solving, we define a new texture measure, Imbalance in Variable Tightness, or IVT, unique to distributed systems. IVT is a measure of unevenness in distribution of local measures of variable tightness, a CSP texture measure, among agents. A non-zero IVT can be i...
This paper presents a new analysis of dynamic constraint satisfaction problems (DCSPs) and a new approach to solving them. We first show that even very small changes in a CSP, in the form of addition of constraints or changes in constraint relations, can have profound effects on search per-formance. These effects are reflected in the amenability of...
We investigate how the performance of search for solving - nite constraint satisfaction problems (CSPs) is aected by the level of in- terchangeability embedded in the problem. First, we describe a generator of random CSPs that allows us to control the level of interchangeability in an instance. Then we study how the varying level of interchangeabil...
Citations
... The proposed customer-driven product configurator offers very sophisticated modeling capabilities, which can handle mathematical formulae and computable procedures as design constraints [7]. Its advance in constraint modeling and search algorithms makes the configuration process very efficient. ...
The paper presents a customer-driven product configurator developed at the Integrated Manufacturing Technologies Institute (IMTI) of the National Research Council (NRC). Advanced with a constraint-based approach, the configurator is able to solve complex engineering configuration problems by allowing design constraints expressed as mathematical formulae and computable procedures. The paper also discussed issues related to implementing a configurator for a product family. The first is how to extract product knowledge to build a product model for configurator setup. The second is how to integrate configuration results into other application systems, such as CAD systems and ERP systems. Ce document présente un configurateur de produit axé sur la clientèle qui a été mis au point à l'Institut des technologies de fabrication intégrée (ITFI) du Conseil national de recherches du Canada (CNRC). Perfectionné avec une approche basée sur des contraintes, le configurateur peut résoudre des problèmes de configuration d'ingénierie complexes en permettant d'exprimer les contraintes liées à la conception comme des formules mathématiques et des procédures calculables. On y traite également de questions liées à la mise en ?uvre d'un configurateur pour une famille de produits donnée. La première de ces questions vise la façon d'extraire la connaissance des produits dans le but de bâtir un modèle de produit aux fins de la mise en place du configurateur. La seconde concerne la façon d'intégrer les résultats de configuration à d'autres systèmes d'application, comme les CAO et les systèmes ERP. RES
