Threads
Páginas: 35 (8619 palabras)
Publicado: 28 de marzo de 2012
Software Quality Assurance Plan
Introduction
Scope and intent of Software Quality Assurance (SQA) activities
The SQA team’s objective is to ensure that the product does not deviate far from the original design specifications. If it is discovered that deviation has occurred, the SQA team will notify the development team to prevent future deviations and to correct the previousdeviations. Also, the SQA team will perform a walkthrough to analyze the product’s quality at any particular stage of development. Error detection and possible enhancements are also expressed to the development team.
SQA organizational role
The SQA organizational role is to review the product(s) at specific times during product implementation. Upon reviewing, the SQA team’sduties will be to evaluate the software at its current development stage and recognize any defects in the subsequent stage (design or implementation). The SQA team will directly interact with the software engineering team in group discussions, discussing any errors or possible enhancements that have been identified. In addition, the SQA team will ensure that the software engineering team has notdeviated in any way from the initial design specifications.
SQA Tasks
Task Overview
Description of SQA Task 1
The Engine Software Engineer will check with the Requirements Specification on a weekly basis to make sure that what he is coding conforms to the original design. This process will ensure that the product meets the client’s expectations and standards andthat the engine, up to its current point, is working properly.
Critique: This is a reasonable approach, but we need to be more specific. How will the “check” be conducted? It is important that this activity be conducted in a systematic way so that things don’t fall into the cracks.
Work products and documentation for Task 1
As a result of Task 1, anymajor deviations that occur will be expressed to the other group members and documented on a separate defect log. Documentation will ensure that each group member is aware of the change(s) made to the engine so that each part of the project can be adjusted accordingly.
Comment: Good idea. The log should be available to all, on-line.
Description of SQA Task 2The User-Interface Software Engineer will check with the Requirements Specification on a weekly basis to make sure that what he is coding conforms to the original design. This process will ensure that the product meets the client’s expectations and standards and that the user-interface, up to its current point, is working properly.
Critique: See critique for Task 1.Work products and documentation for Task 2
As a result of Task 2, any major deviations that occur will be expressed to the other group members and documented on a separate defect log. Documentation will ensure that each group member is aware of the change(s) made to the interface, so that each part of the project can be adjusted accordingly.
Description of SQA Task 3Each member of the group will routinely perform a hands-on evaluation of the user-interface. Noted evaluation criteria will be: ease of use, principle of least astonishment, unobtrusiveness, and overall attractiveness. This is done to ensure that the user-interface is evaluated honestly, and remains easily understandable and attractive.
Work products and documentation for Task 3As a result of Task 3, all suggestions or concerns are expressed to the User-Interface Engineer. These are recorded in the defect log. Based on these concerns, the User-Interface Engineer takes note and makes the appropriate adjustments to the user-interface to make sure that the final product is satisfactory.
Description of SQA Task 4
Each member of...
Introduction
Scope and intent of Software Quality Assurance (SQA) activities
The SQA team’s objective is to ensure that the product does not deviate far from the original design specifications. If it is discovered that deviation has occurred, the SQA team will notify the development team to prevent future deviations and to correct the previousdeviations. Also, the SQA team will perform a walkthrough to analyze the product’s quality at any particular stage of development. Error detection and possible enhancements are also expressed to the development team.
SQA organizational role
The SQA organizational role is to review the product(s) at specific times during product implementation. Upon reviewing, the SQA team’sduties will be to evaluate the software at its current development stage and recognize any defects in the subsequent stage (design or implementation). The SQA team will directly interact with the software engineering team in group discussions, discussing any errors or possible enhancements that have been identified. In addition, the SQA team will ensure that the software engineering team has notdeviated in any way from the initial design specifications.
SQA Tasks
Task Overview
Description of SQA Task 1
The Engine Software Engineer will check with the Requirements Specification on a weekly basis to make sure that what he is coding conforms to the original design. This process will ensure that the product meets the client’s expectations and standards andthat the engine, up to its current point, is working properly.
Critique: This is a reasonable approach, but we need to be more specific. How will the “check” be conducted? It is important that this activity be conducted in a systematic way so that things don’t fall into the cracks.
Work products and documentation for Task 1
As a result of Task 1, anymajor deviations that occur will be expressed to the other group members and documented on a separate defect log. Documentation will ensure that each group member is aware of the change(s) made to the engine so that each part of the project can be adjusted accordingly.
Comment: Good idea. The log should be available to all, on-line.
Description of SQA Task 2The User-Interface Software Engineer will check with the Requirements Specification on a weekly basis to make sure that what he is coding conforms to the original design. This process will ensure that the product meets the client’s expectations and standards and that the user-interface, up to its current point, is working properly.
Critique: See critique for Task 1.Work products and documentation for Task 2
As a result of Task 2, any major deviations that occur will be expressed to the other group members and documented on a separate defect log. Documentation will ensure that each group member is aware of the change(s) made to the interface, so that each part of the project can be adjusted accordingly.
Description of SQA Task 3Each member of the group will routinely perform a hands-on evaluation of the user-interface. Noted evaluation criteria will be: ease of use, principle of least astonishment, unobtrusiveness, and overall attractiveness. This is done to ensure that the user-interface is evaluated honestly, and remains easily understandable and attractive.
Work products and documentation for Task 3As a result of Task 3, all suggestions or concerns are expressed to the User-Interface Engineer. These are recorded in the defect log. Based on these concerns, the User-Interface Engineer takes note and makes the appropriate adjustments to the user-interface to make sure that the final product is satisfactory.
Description of SQA Task 4
Each member of...
Leer documento completo
Regístrate para leer el documento completo.