Team BLT
CS 4500
March 14, 2008
version: 1.0
Verification & Validation Results
1.0 Introduction and overview- 1.1 Purpose of this Document The results of the VVP are presented here in the VVR, which outlines our testing results on Daz Studio Easy.
- 1.2 Scope of the Development Project Currently, DAZ Studio is a professional quality product. Though it is great to have a high quality product it can make it difficult for an new user to get accustomed to it and be able to use it to its full potential. Many users have already acheived this and enjoy using DAZ Studio. However, there is a large community of people that want an application that they can download and within 15 minutes they can be manipulating their own models for use in online virtual communities, video games, and other applications that allow users to utilize their own models. DAZ 3D would like to make another application that will target these users. We are going to work in cooperation with DAZ 3D to acheive this goal. DAZ 3D has provided us with suggested enhancements for the application. We also bring a fresh perspective to the table and have many great ideas that will enhance the application as well. We will have the responsibility of implementing changes that will help achieve the end goal. We will also simplify many of the tools and make the user experience a more pleasant one in less time.
- 1.3 Definitions, Acronyms, and Abbreviations
- 3D - three-dimensional
- DAZ Studio - a 3D posing application for 3D models.
- QT - framework that makes it possible for Daz Studio to be cross-platform.
- Sprint - development process in which a certain number of tasks are scheduled to be accomplished within a given time period. At the end of the time period progress is evaluated, new tasks are assigned, and a new time period is established.
- UI - user interface.
- 1.4 References www.daz3d.com
- 1.5 Overview of Document This document describes the testing results, procedures, and fullfillment of requirements of the project.
Software Requirements Specification
Software Design Specification
- We thoroughly tested each added enhancement component prior to committing the code to the respository, and following the committ as well. We found in all such cases that we were able to ensure that the code was functioning just as anticipated and the enhancenments did cause any negative repercussions.
- Each team member has taken ownership of an equal number of documents. That team member was responsible for the completion of the document. All team members participated in the preparation and review of the content for each document prior to delivery. Changes were discussed and the documents revised as necessary.
- 4.1 Summary of Component Test
- Viewport: Tested by Brandon, minimum overall changes were done on the viewport, and the changes that were done were tested quite easily. There are no outstanding bugs for the viewport currently
- DockArea Column: Tested by Travis, components were all sufficently tested, there were no adverse effects. There are no outstanding bugs associated with the changes made
- Pane: Tested by Tony, All pane dragging and docking were tested as outlined and are function properly. There are no known issues or bugs related to the pane at this time.
- Menu: Tested by Travis, one menu item was changed only, and it was tested properly. All tests indicated normal funcationality. There are no current bugs for this item
- 4.2 Summary of Integration, Test/Testing Product as a Whole
- Due to the nature of our project, we are working on an existing code base. Therefore all components are working seamlessly, because as we add new features, and re-design other features we make certain that all changes do not affect the overall functioning code base.
- 5.1 Evaluation of Test Cases
- The test cases we have been using have been quite sufficent and helpful in ensuring that our code is functioning as good as possible. We have been very happy with results produced from our testing.
- 5.2 Results from Defect Tracker
- To this point in our project our defect tracker as served primary as a tool for keeping track of future enhancements, and keeping everything organized.
- 5.3 Lessons Learned
- We have learned that working with interfaces provides easy to do, straight forward testing. It is much easier to test UI enhancements than testing underlying functionality.
- We have thorougly tested all work done on the project. Daz engineering team and management has also reviewed the code and found all work done to be satisfactory.
-
We do not have any open issues. We have no outstanding defects. Our bug list contains only enhancements that we will implement in the future.
| Date | Version | Description |
|---|---|---|
| March 14, 2008 | 1.0 | Create VVR |