We could increase these lists much more, but in the context of this article are sufficient the above criteria. Let us now examine for example some of the problems involved. Ohio Senator spoke with conviction. Properly calibrate the complexity and risks of problem. The possibly more complicated to solve problem is the problem of the heterogeneity of the information, this is due to the inherent nature of the usual (relational) databases. His virtues have evolved towards a capacity to manage amazing volumes of information, but with relatively homogenous information structures, such as those employed in the field of classical management.
I.e. in ERP and CRM. However, very heterogeneous information structures, as it is the case of a large catalogue, are not natural to implement them. In this sense have appeared interesting proposals, for example, DB-based using XML natively, but they do not have the maturity of the relational classic. We face a major risk factor, it is usual to find severe limitations in this sense in standard cataloging solutions.
A satisfactory solution requires a sophisticated system capable of solving the obstacles inherent to the use of a relational database. Not detected this limitation in choosing or designing a solution, assumes the unpleasant surprise of being one insufficient solution precisely at the most critical point: the richness of its content. We find a similar example for the calculated information. Taking the example of prices, it is common to be faced with a situation in which the undertaking concerned has developed a system of rates based on multiple very custom variables, cataloging solution must respect this price system. Possible solutions would be the catalog may request the prices to the existing ERP system or incorporate mechanisms that allow reasonably implement with an effort under the prices in the catalog system. The first option requires advanced on both sides integration capacity, new technologies such as XML can provide much help. The second demands a high flexibility to the solution of cataloging as regards the handling of policies of calculation of attributes, even though it means the inconvenience of replicating work, which means a double maintenance before changes in pricing policies. Suffice it to these two examples, the does article not intended to be a tutorial on analysis of projects of new technologies, but to illustrate the analytic work that apparently trivial problems as a simple catalog 2? they require to ensure the success of the project. Compiled by. Javier Mejia T.