Challenge Overview
ConfigGen is a tool which pulls product and price data out of a DB/2 database and writes it into two flat text files for use in a standalone configurator application.
The two flat text files are:
configurator.txt (product data)
prices.txt (price data)
Recently, a major incident was reported which noted the configurator application was missing prices for some products. Analysis of this incident revealed the missing prices were occurring because the price data, as it is currently being stored in the underlying database columns of ConfigGen, was being truncated. The root cause of this problem is the current database column, t_compats, which stores the price data, is poorly designed. The temporary fix for this incident was to simply increase the length of the problematic database column. However, a permanent fix is now desired that will provide a much improved database design approach (and associated logic) for storing the price data.
The objective of this module is to deliver re-designed ConfigGen price generator sub-components which will:
· provide re-designed database table(s) that will define an improved approach for storing the price data in a way that will prevent the truncation issue noted above
· provide enhancements to the existing ConfigGen stored procedures and processing logic, so they are adapted to use the newly designed database
· ensure there is no degradation of performance due to the changes
The scope of the documentation is constrained to just any update required to fulfill these requirements.
Conventions:
When referring to bean properties in this component, the standard bean dot notation is used in lieu of quoting the actually get/set methods. So instead of having
initiationResponse.getProblem().getId()
We will write
initiationResponse.problem.id
Final Submission Guidelines
N/A