Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumSoftware Testing @ OneStopTestingBeginners @ OneStopTesting

Message Icon Topic: Basics of Quality Assurance (QA) in Sofware Develo

Post Reply Post New Topic
Author Message
Mithi25
Senior Member
Senior Member
Avatar

Joined: 23Jun2009
Online Status: Offline
Posts: 288
Quote Mithi25 Replybullet Topic: Basics of Quality Assurance (QA) in Sofware Develo
    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



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.172 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting