From the figure, we can observe that both the statistical packages researched about i.e. ‘Statistical Product and Service Solutions (SPSS Statistics)’ and ‘R Statistical Package’ require the column headers to be present in as the first line of the column data. The application writes the data into the CSV file in the exact same way. Hence, the application can now be extended to be tested in any statistical package for observing biases. Since MySQL proposed a lengthy method for establishing this, OpenCSV was used to export the data in the required format. A good point to be noted here is that although the functionality of comparing samples for biases could not be realised completely, this step covered well for it as now the user can use this application as a medium to compare various samples given the data.
6.3 Limitations The following section evaluates the various limitations of the application with some factors contributing to such drawbacks. It highlights the requirements that couldn’t be completed, the proposed solutions to some of these limitations and the alternative tools and techniques which could be used to efficiently achieve the application targets.
6.3.1 Undelivered Requirements & Proposed Solutions The requirements analysis chapter throws light on the various requirements the user required the application to perform. The previous section highlighted the requirements which were judiciously satisfied. However, some of the requirements couldn’t be met due to time constraints which restricted some insight into the various techniques of realising them. These included: analysing samples for biases, creating criteria to remove biases and reporting results to the user in a graphical manner (or alternate visualisation). These are discussed in detail below. i)
Analysing samples for biases: Due to the model adopted which caused the implementation phase to be carried out in the end, the application had a major drawback of setting up one set of samples for comparison. This is to essentially say that the tables can be queried only once before they get deleted in the end of the application when samples are exported. Given the time, I would probably try to alter this significantly to help the user re-query the table multiple times to store data in temporary memory or Views as compared to 66