Basics of Quality Assurance (QA) in Sofware Develo
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=7382
Printed Date: 27Dec2024 at 6:45pm
Topic: Basics of Quality Assurance (QA) in Sofware Develo
Posted By: Mithi25
Subject: Basics of Quality Assurance (QA) in Sofware Develo
Date Posted: 27Nov2009 at 12:39am
Basics of Quality Assurance (QA) in Sofware Development
Quality Assurance is the most important factor in any business or industry.
Same thing is applicable for Software development also.
Spending some additional money for getting high quality product will definitely give more profit.
But anyway, it is not true that expensive products are high-quality products. Even inexpensive product can be high-quality product if it meets Customer’s needs/expectation.
The quality assurance cycle consists of four steps: Plan, Do, Check, and Act. These steps are commonly abbreviated as PDCA.
The four quality assurance steps within the PDCA model are
* Plan: Establish objectives and processes required to deliver the desired results.
* Do: Implement the process developed.
* Check: Monitor and evaluate the implemented process by testing the results against the predetermined objectives
* Act: Apply actions necessary for improvement if the results require changes.
For getting appropriate quality output in software development we need to follow SQA (Software Quality Assurance) process in each phase (Planning, Requirement Analysis, Design, Development, Integration & Test, Implementation and Maintenance) of the software development lifecycle.
We should follow below solutions to avoid many software development problems.
* Solid requirements - Clear, complete, attainable, detailed and testable requirements that are agreed by all players (Customer,developers and Testers).
* Realistic schedules - Allocate enough time for planning, design,testing, bug fixing, re-testing and documentation.
* Adequate testing - Start testing early, re-test after fixes/changes.
* Avoid unnecessary changes in initial requirements once after starting the coding
* Require walk-through and inspections
-------------
http://www.quick2sms.com - Send Unlimited FREE SMS to Any Mobile Anywhere in INDIA,
Click Here
|
|