SQA Management Plans

SQA Management Plans

In the planning and requirements phase, there will be four plans that will be created. These plans will be used in the next stage of software development which is the architectural phase. The Software Quality Assurance Plan (SQAP) for architectural design (AD) is basically the following list of activities to ensure that the preparation of the architectural plan is a success. If any tool or application will be used, the SQA team should point this out in this phase.

• Software Project Management Plans (SPMP) for Architecture Design

The SQA team should ensure that this management plan will have the specific budget for developing the software. Aside from being specific, the SQA team should also ensure that the estimate should be obtained using scientific methods.

• Software Configuration Management Plans (SCMP) for Architectural Design

SCMP is the plan on how the software will be eventually configured. In this phase, the SQA team should ensure that the configuration should have been established at the start.

• Software Verification Management Plan (SVMP) for Architectural Design

Like most of the management plans, this one has already been established. But extra information should be sought after by the SQA team. Since this document will be used in the architectural design phase more detailed information is needed. A test plan should be made to ensure that the Architectural Design phase is a success. Also, the SQA team should ensure a general testing system should be established.

Output and Principles

At the end of the planning phase, developers should be able to produce a document that has the details needed for the Architectural Design phase. The SQA team should check if the document has the following characteristics:

• Consistency – This is especially applicable if the output does not use any CASE tools. Case tools should easily figure out inconsistencies and it is up to the SQA team to determine this consistency if no CASE tools was used in this phase.

• Verifiable – Each specific requirement in this phase should be tested either by a popular tool or verifiable facts from the past.

• Complete – The SR or software requirements is the end of the requirement phase. To declare that this phase is complete, the SQA team should check with the UR (user requirements) and see to it that all the things needed by the user are answered. If possible, a matrix should be created to track each answer of the SR to the UR built by the users.

In the end, the SQA team, the developers and representatives of the users will come together for a formal review of the documents. By sitting together, everyone will know if the things needed in the software are covered or will come together with the application.