3.3.3 Communication Interfaces
This software is going to have a web server which will be connected to whenever any web service is needed. This server is also going to contain the database. Thus in needs for data also, system will communicate with this server. This communication is capable with the help of JDBC. The data will be synchronized and consistent data will be kept in the server.
The data will be fetched everyday by using a scheduler and will be partitioned in a required manner to store in the database in the required format. Further whenever the data is need it will be fetched from the database using the JDBC Connectivity.
The communication with the server will occur in the following cases:
1) When the user fills out the …show more content…
3.4.4 Software Quality Attributes
The graphical user interface of the software is to be designed with first priority as the usability. The software will be presented in such a way that it is both visually appealing and easy for the user to navigate through the application.
For the correctness and reliability there will be zero tolerance for any errors in the improved ID3 algorithm that is being implemented. The algorithm will work efficiently in all cases.
Every day at a specified time, the server will be updated so the software may produce some inconsistent data. The layout and the UI of the software will be easy enough so that even users who have no idea will be able to use the software.
In addition, the user can edit the information provided to the software. For e.g. he can increase the number of mutual funds, change the tenure and so on. He can do this any number of times. The user can use the questionnaire also any number of times, so as the take advice from the software dependent on the past data.
Application code and comments should be written descriptively. The names of classes, methods and variables should be self-descriptive. Methods and classes will be commented to detail their