SQA Implementation

SQA Implementation

Developers and the SQA team create a development plan before they build an application. The developers write following the SDLC plan while the SQA team writes the Software Quality Assurance Plan to ensure that the SDLC plan was executed. If these documents by the developers and the SQA is well written and organized, the application that is about to be developed is already half-way done.

Even though the documents are well written, these are all nothing when those written are not followed. That is why equally important to the SQA Planning is SQA Implementation. If you are familiar with the most of the SDLC models, implementation means the integration of the developed application to the operations. The preparation and the coding culminate with the implementation of the application to the operations department.

However, SQA treats implementation in an entirely different manner. In every stage of software development, SQA team develops their plan and with it a specific plan of implementation. Every stage of software development is very important to the SQA team. Because of its importance, every stage should be scrutinized and an action plan is very important.

If one of the stages is not checked properly, there is a very good chance the application may not perform as planned. Every stage of the application development process is considered an independent program that planning for each stage is very important.

Although each stage is related and would eventually compliment the next, SQA will treat them as independent entity, each of them having their own implementation plan. We take a look at each of the development stage and see how each stage is implemented.

Requirements Phase

In the User Requirements phase (UR) the SQA team has to ensure that the users or the management list all the possible functionality they are looking for the application. The SQA team should be able to gauge these functions whether they are realistic or not. A document should be made detailing the need of functionality so that it could be easily presented to the developers.

Once the UR document is complement, the developers receive the document and use it as a basis for the SR stage. The developers have to propose the appropriate software configuration to cater to the user’s need. The SQA team’s function in this stage is to ensure that each proposed user function will be dealt with.

The SQA team has to ensure that the User Requirements will be addressed and should be traced. When traceable, the SQA should be able to logically gauge if the User Requirements has been address or not. Aside from being logical, the software requirement proposed should be verifiable.

In this phase, testing the proposed SR is encouraged. The SQA team could even use CASE tools so that it could easily prove the functionality’s worthiness in answering the User Requirements. CASE tools could quicken the verification of the functionality although monetary concerns should be considered.