This is a continuation from last months installment of the TeraTech Development Approach.
6. Unit Testing
As each fuse is coded, it is unit tested against the test harness. This gives the coder a way to ensure the correct behavior is produced by the fuse, without being in constant contact with the architect.
7. Application Integration/Final Testing
As the fuses are completed, they are returned to the architect, who integrates them into the final application. Daily builds are employed, gradually transforming the prototype into a working application.
After developer system integration testing, the new release is deployed to the NJ Sullivan center for final user acceptance testing following standard NJ Sullivan testing procedures.
8. Deployment
Deployment is the least exciting phase of the FLiP project. Thanks to the high degree of communication between the client and architect, and the architect and coders, deployment should hold no surprises for anyone.
Related Posts
TeraTech Development Approach – Application Architecting and Fusecoding- TeraTech Development Approach – Design in Fusebox and Database Access Components
- TeraTech Development Approach – Prototype/ Front-End Development
- TeraTech Development Approach – Database Review
- TeraTech Development Approach – System Decomposition
- TeraTech Development Approach – Web Form Prototype
