Development and SQA teams work to create a development plan before they start developing the application.

Development Team writes; following the SDLC Plan and SQA team writers; following the SQA Plan. SDLC: SQA Plan: Requirements + Design and Coding + Testing SDLC + Configuration Management + Audit + Metrics + Continual Improvement

SQA Plan ensures that SDLC Plan was executed. If these two documents are well written and organized, application under build is half way done. SQA Implementation:1. User Requirements Phase:: SQA Team has to ensure that Users or concerned person/team list all the possible functionality that they are looking for; in the application. SQA team analyzes these functions whether they are realistic. Output of the above process should be a document that can be presented to the development team and development team can use it as basis for Software Requirements phase. Once User Requirements document is complete and is presented to development team, developers propose the appropriate software configuration to meet the users needs. SQA team has to verify that proposed user functions will be dealt with. SQA team also has to verify that User Requirements will be traceable and will be traced. A Traceability Matrix is designed and developed. 2. Prototype Design Phase:: After the User Requirements and Software Requirements are approved by all players, Business Development team develops a prototype that can be presented to Client/User for approval. In this phase SQA team will have to look into this prototype before it is presented to the client. SQA efforts will be focused to find any Missing Functionality, Analyze the Logical Flow of the application, Usability and Aesthetic Sense. After Prototype is finalized, it will be presented to the client. Meanwhile Management/Business development team is in process of forwarding prototype to client and getting feedback; SQA team will start designing the test cases for later use. 3. GUI Design Phase:: Once the client approves Prototype, Graphics Designing team designs a theme and GUI for the application. SQA team checks the GUI by focusing the factors like Usability, Aesthetic Sense and Over All Look of the application.

4. Development Design Phase:: Development Team designs database and development model. SQA team verifies the implementation of proposed functions, Process of the development will also be monitored by SQA Team. SQA team will implement the simplicity of the code and ensure that coding should be easily understandable. Along with the coding, comments in the code should also be checked thoroughly. Comments should clearly define purpose of each function. Software documentation is also checked by SQA team to verify that it is thorough and clearly states the functions of the application and samples from the functions are added so that documentation can be used for training purpose. 5. Unit Testing Phase:: In this phase, testing of the application will be performed concurrently with development. After a module is developed, developer is able to show how the application will react to certain commands and functions and at the same time SQA team should be able to work with traceability matrix to assure that all the user requirements; defined in User Requirement phase are met and only the given requirements are met. SQA team will report in both the cases if application misses some requirement or there is some extra functionality in the application that was not part of the User Requirements Document. Initially developer will test his/her own module, will fix any found issue(s) and then it will be handed over to SQA team for further testing. Developer s can also swap their modules for testing. All the issues/bugs will be logged into bug tracking system. 6. Integration Testing Phase:: At this stage application is ready to be integrated to perform it operation. SQA team will be responsible for performing Integration Testing of the application. Integration Test cases; designed by SQA Team in prototype designing phase will be run against the application. Any issues found; will be logged into the bug tracking system, will be assigned to concerned developer to resolve it. After the issue is resolved, SQA team will be responsible to retest it. 7. Beta Release Phase:: After Integration Testing is complete and Signoff is given by SQA team, a beta release will be generated for the client. Meanwhile client is working with Beta release, SQA team will be busy in performing Audits and producing Metrics.

8. Final Release: As in most of the cases our beta release has 60% to 70% of the agreed upon functionality, while moving towards final release we will be following the practices that we practiced for Beta release.