This section will include detail for the design of the second iteration of the project; it is based upon the requirements from the previous section.
The Jmol API defines the structure of this increment. The Jmol API requires only one class therefore a class diagram is not needed. The Jmol Wiki states, “A very good start is the Integration.java out of Jmol SVN” about embedding the Jmol Application into your own applications. This java file can be accessed from Here.
The integration of the 3D viewer will need to fit in with the current architecture of the first increment, the other consideration to take into account is deployment, there are two options to consider, whether the Jmol jar file is distributed within the FAHView Application making a larger file size or implemented as a modular plug-in that is downloaded separately. Embedding the Jmol viewer within the application has its advantages, it ensures compatibility between the versions however the final file size of the application will be larger. Having the Jmol viewer as a plug in has the advantages of a smaller file size but the possibility of compatibility issues between versions of Jmol.