Used Dr. comments on the interim report to polish the Fox’s final report. Updated the prototype section to reflect the final product. Updated the testing section to reflect the final product. People Jishnu Renugopal Documented design, project overview and – involved methodologies used. Mattin Zargarpur Documented implementation and testing – procedure Lessons It is crucial that the project report meticulously document all parts learned of the product development. This ensures that the end user is able to set up the application with ease. Additionally, this also helps subsequent developers working on VR4GETAR to use the report to gain some context about the project without much effort. 4.3.3 Testing Work done Formative testing was done to ensure that the VR interface works as expected without any issues like lag, low frame rate, etc. Unit testing was done to ensure that the internal logic of the application is performing as expected. People Mattin Zargarpur Lead tester – involved Willem Schmidt, Haiyu Zhao, Kevin Zhang Assisted testing – Lessons Applications developed for a 2D interface such as a desktop might learned not transfer well onto a 3D interface such as VR. 5.0 Future Work Due to time constraints, the user-generated collection feature is limited to three total collections. Support for an arbitrary number of collections would provide an improvement to the application. Further, tracking collection metadata such as name, author, and time of creation, would add polish. Another possible improvement to the application, given sufficient development time, would be to add more visualizations. Currently, the application allows users to view data directly, but showing the relationships between various pieces of data could also be insightful.
Used Dr. Fox’s comments on the interim report to polish the final report. Updated the prototype section to reflect the final product. Updated the testing section to reflect the final product. People involved Jishnu Renugopal – Documented design, project overview and methodologies used. Mattin Zargarpur – Documented implementation and testing procedure Lessons learned It is crucial that the project report meticulously document all parts of the product development. This ensures that the end user is able to set up the application with ease. Additionally, this also helps subsequent developers working on VR4GETAR to use the report to gain some context about the project without much effort. 4.3.3 Testing Work done Formative testing was done to ensure that the VR interface works as expected without any issues like lag, low frame rate, etc. Unit testing was done to ensure that the internal logic of the application is performing as expected. People involved Mattin Zargarpur – Lead tester Willem Schmidt, Haiyu Zhao, Kevin Zhang – Assisted testing Lessons learned Applications developed for a 2D interface such as a desktop might not transfer well onto a 3D interface such as VR. 5.0 Future Work Due to time constraints, the user-generated collection feature is limited to three total collections. Support for an arbitrary number of collections would provide an improvement to the application. Further, tracking collection metadata such as name, author, and time of creation, would add polish. Another possible improvement to the application, given sufficient development time, would be to add more visualizations. Currently, the application allows users to view data directly, but showing the relationships between various pieces of data could also be insightful.