Software Quality Assurance Engineer

Software Quality Control Nomenclature:

- Verifying: comparing the code predictions

- Validating: Comparing the prediction of code with test data

- Version Testing: Comparing output of the current version with output of the previous version

- Installation Testing: Comparing the result with newly installed code to the sample result code

- Development Code: Code tested only by the software developer.

- Alpha Code: Testing of the software product internally by selected users.

- Beta Code: Code testing internally by a large numbers of users.

- Released Code: Well tested and documented code that is officially distributed.

A paradigm that is Goal Question centric.

- A method that control the overall risk.

- Quality Control that involves Plan, Perform, Check, Action Model.

- Complete Software Quality Control.

- Software Development Method that involve the Spiral Model.

Includes the activities that are designed to determine the level of quality.

- QC is a reactive means which measures and monitors the quality

- Includes operational activities and techniques to meet the quality needs.

- QC involves in verifying the desired quality levels.

The very common function size is Function Point Analysis.

- FPA is all about measuring the software deliverables.

- FPA is based on the requirements of the user and presents accurate representation of developer and estimator.

- FPA reflects the functionality that is delivered to the client.

- FPA involves in identifying and weighting of inputs, outputs and data storage.

Quality being part of every day operations, is the internal impact.

- Quality becomes as a part of setting and managing the objectives, practices.

- The open up of operations to customer audits, is the external impact.

- Procedures and record-keeping improve dramatically.

- The implementation of this standards will obviously takes the work to keep audits and the appropriate follow-ups fluent.

The following are the activities of project control:

- Verify the integrity of the database files.

- Check the transcription errors while inputting and referencing the data.

- Verify the data consistency.

- Perform the internal review of documents.

- Perform the completeness check.

- Compare the existing results with previous results.

Control charts are suitable for tracking items such as:

Production failures

Defects by life cycle phase

Complaint/failures by application/software

Response time to change request

Cycle times/delivery times

Mean time to failure

The CMM is a way to communicate capabilities.

The ISO is a way to communicate the process.