Sunday, August 1, 2010

SQA Process and Steps

Steps of SQA process
  1. Initiate SQA Process
  2. Planning
  3. Tracking
  4. Training
  5. Reviews
  6. Issue Resolution
  7. Testing
  8. Audit
  9. Process Improvement

    1-Initiate SQA Process

    QA manager to initiate SQA process for a project, once a P&C is signed off and a formal request is received from Director IT.
    This sub process covers the initiation of SQA process for complete SDLC. An estimation file is made to estimate SQA resources.

    Following Tasks will be performed at this stage
    • Director IT will send a formal request to QA Manager through email for implementation of SQA process.
    • QAM arrange resources, initiate SQA Process and performs SQA activities.
    • Interaction with Customers SQA personnel as per request

    Following personal will be involved
    • Director IT
    • QA Manager
    • QA Team Lead


    • The sub-process enables planning for SQA activities.
    • SQA group selects the activities for which to develop Plan(s), according to project and departmental needs.
    • Is made at the initial stage of SDLC
    • Define an organization, task and responsibilities within SQA process
    Following Tasks will be performed at this stage
    • Estimation of SQA activities will be done by the SQA Team.
    • The cost and work breakdown will be done by the SQA team.
    • The Timelines (in MS Project Format) will be made.
    • QA Team Lead will give an orientation to the SEG about QALC.
    • Activities are identified which have to be planned.
    • Resources are assigned for planning
    • QA TL prepares SQA + Test Plans.
    • Plans placed in VSS, Notification to PC / PM.
    • Plans are distributed to affected groups.
    Following personal will be involved

    • Project Manager
    • QA Manager
    • QA Team Lead
    • Project Coordinator
    • HR Department

    Test Plan:

    This plan focuses on controlled and managed test activities for any software work product.

    This Plan is developed normally when FS and Design phases are completed.

    Tasks Perform at this stage are:

    • TL prepare Test Plan.
    • Size and Cost estimation is performed.
    • Review report is generated and placed in VSS.
    • QAM will approve the Test Plan.
    • Plans are distributed to affected groups.

    Personals Involved at this stage are:

    • Project Manager
    • QA Manager
    • QA Team Lead
    • Project Coordinator


    • Black and White Box Testing.
    • Acceptance Testing.
    • Integration Testing.         1 Small         2 Large
    • Non-Functional System Testing.
    • Functional System Testing.
    • Component Testing (Unit Testing).
    • Maintenance Testing.
    • System Testing.
    • Shipment Assurance Testing.


    Developer’s Perspective

    • Correctness / Reliability / Accuracy
    • Integrity
    • Efficiency
    • Maintainability
    • Reusability

    User’s Perspective

    • Usability
    • Understandability
    • Robustness
    • Adaptability
    • Reports can be obtained

    3- Tracking

    This sub-process is used to track deviations and monitor progress against different plans, which can result into updating the timelines, reassignment of tasks.

    Tasks Perform at this stage are:

    • Tracking activities for SQA and Test Plan.
    • Progress Review Meeting is conducted.
    • Progress Review Report is prepared and stored in VSS.
    • If status meeting is postponed then give reason.
    • Deviations are recorded in tracking report.
    • PM will be presented SQA Analysis report on monthly basis.
    • Tracking report is placed in VSS.
    • Report against deviation is also generated.
    • Deviations are identified and issued to affected groups.
    • Issues will be forwarded to Issue Resolution.
    • Status report is dist. and cost effective sheet prepared.

    Personals Involved at this stage are:

    • Project Manager
    • QA Manager
    • QA Team Lead
    • Project Coordinator

    4- Training

    This sub-process includes Project specific and QA specific training.

    • Project specific training can be an orientation / training of a specific design tool for a specific project.
    • QA specific training can be an introduction to expertise that is required to perform activities beyond the existing skill set.

    Tasks Perform at this stage are:

    • Request for Training is placed or training needs are identified.
    • After review SQA Manager forwards the request to training manager.
    • SQAM/TL performs all the required coordination.
    • SQAM/TL implement training plan.
    • Feedback is provided by the affected group after training and updated in training program repository.

    Personals Involved at this stage are:

    • QA Manager
    • QA Team Lead

    5- Reviews

    The sub-process performs Peer reviews and Reviews at the project-level.
    • Peer Reviews will be performed for software related work products i.e. (SQA Plan, Test Plan, Test Cases and Code (Optional)).
    • The objective of peer reviews is to remove defects from the products early and efficiently. The results of the peer review are recorded and passed on to the author or person responsible for correcting defects discovered during the review.
    • Reviews at the project-level are necessary to determine that items are consistent, correct and of acceptable quality.

    Personals Involved at this stage are:

    • QA Manager
    • QA Engineers
    • QA Team Lead
    • Project Manager
    • Project Coordinator

    Tasks Perform at this stage are:

    • All the reviews will be performed as per plan.
    • Team lead will prepare RSSR and then updates it accordingly.
    • Review meeting is confirmed with the Review Team.
    • Review team members prepare review-report-points prior to meeting using the respective Review Check List available in PAD. That check list will be made available along with the software related work product.
    • Software Related Work Product is reviewed during review meeting.
    • After preparation and verification of Review Report team lead will update the respective RSSR.
    • A status is given to the work product being reviewed
    • This status can be: 
      -Accepted (To proceed forward for Approval)
      -Needs Rework (Rework required and then verification should be done)
      -Rejected (New work product is to be prepared). 
      -In case of any issue, “Issue Resolution” sub-process will be followed.

    6- Issue Resolution

    The sub process will help to resolve issues that can come across while performing SQA activities; these issues will be escalated or resolved.

    Is nonconformity or a deviation against standards, resolution of which cannot be agreed upon between SQA team and affected group while performing different SQA activities like Planning, Reviews, Audits and Testing.

    Personals Involved at this stage are:

    • QA Manager
    • QA Engineers
    • QA Team Lead
    • Project Manager
    • Senior Management

    Tasks Perform at this stage are:

    • ‘Issue Escalation and Resolution report’ and ‘Issue Tracking report’ are generated when unresolved issues are confronted.
    • SQA TL notifies affected groups about the meeting using these reports.
    • During meeting if issues resolved then TL updates VSS with these reports.
    • If remain unresolved then escalated to next management level.
    • Even then if issue is not resolved then preventive actions process are initiated.

    7- Testing

    SQA assures that formal software testing is done in accordance with plans and procedures.
    SQA reviews testing documentation for completeness and adherence to standards.
    By test monitoring, SQA assures software completeness and readiness for delivery by executing shipment assurance testing.

    Personals Involved at this stage are:

    • QA Manager
    • QA Engineers
    • Project Manager
    • Project Coordinator

    Tasks Perform at this stage are:

    • Testing approach as defined in test plan.
    • Domain knowledge acquired.
    • TSSR will be made by TL.
    • QAE develop Test case.
    • Test cases executed (Unit, Integration, System).
    • Results are generated as fault reports and escalated to AG.
    • Dev review fault reports and verified after rework.
    • TSSR will be updated with every iteration.
    • Application delivered to client as per release management process.

    8- Audit

    • The sub-process is a fundamental quality assurance technique.
    • Audit will be conducted for all software engineering activities to verify compliance against:
    1. Standards
    2. Processes
    3. Procedures
    • Conformance of development processes to procedures and conformance of product to standards.
    • Also examines conformance of actual status to reported status.


    • Organizational based audits (after every three month)
    • Project based audits (after every Two months)
    • Event driven Audits

    Personals Involved at this stage are:

    • Project Manager
    • QA Manager
    • QA Engineers
    • QA Team Lead
    • Project Coordinator

    Tasks Perform at this stage are:

    • Audit should be according to plan.
    • TL makes and afterwards updates ASSR.
    • Audit checklist will be customized and used to conduct audit.
    • Audit will be conducted.
    • Audit report will be published.
    1. PM, Sr. Mgt. -> Project based
    2. -QE, Sr. Mgt. -> Organizational Based
    Affected Groups are informed of NCR by mail
    Hard copy of Non Conformance Report (NCR) is created and duly signed by Software Engineering Group (SEG).
    NCR report is created and unresolved issues are escalated in issue resolution.

    9- Process Improvement

    • Critical function of SQA is Process Improvement.
    • This sub-process includes research and development need of SQA which results into improved processes, checklist and guidelines.

    Personals Involved at this stage are:

    • QA Manager
    • QA Engineers
    • Quality Engineering

    Tasks perform at this stage are:

    • SQA periodically review Software process and improvement activities.
    • QAE / Dev / Mgt generate process improvement request.
    • QAM review process improvement request.
    • QAM accept / reject process improvement Request.
    • Findings are prepared.
    • QAM will approve and review the recommendations and forwarded to QE.
    • Reports will be posted in VSS.


    SQA Process:

    Process for providing adequate assurance that the software products and processes in the project life cycle conform to their specified requirements and adhere to their established plans

    Why SQA Process:

    There are reasons that sqa process
    • Provides management with appropriate visibility into the process being used and the products being built.
    • Verifies compliance with project requirements
    • Based on a documented plan and processes
    • Assures the delivery of high-quality technical products and services

    SQA Process Activities:

    1. Product Assurance
    2. Process Assurance
    3. Process Implementation

    Product Assurance

    Assure that all plans required by the contract are documented, comply with the contract, are mutually consistent, and are being executed as required.

    Ensure that software products and related documents comply with the contract and adhere to the plans.

    In preparation for the delivery of software products, assure that contractual requirements are fully satisfied and that requirements are acceptable to the acquirer.

    Process Assurance

    Assurance that those software life cycle processes (supply, development, operation, maintenance, and supporting process including quality assurance) employed for the project comply with the contract & plans.

    Assurance that the internal software engineering practices, development, test environments, and libraries comply with the contract

    Process Implementation

    This activity should include the following:

    Quality standards, methodologies, procedures, and tools.
    Procedures for identification, collection, filing, maintenance, and deposition of quality records.Resources, schedule, and responsibilities.V&V, joint review, audit and problem resolution.

    Wednesday, June 30, 2010


    Process Performance Models are used to estimate and predict results to be achieved by following a process.

    There are following process performance models.

    • Effort Estimation Model
    • Defect Estimation Model
    • Time and Effort PPM
    • Release Management PPM
    • Patch Release PPM
    • Testing PPM


    Testing Process Performance Model

    Testing Process Performance model is to predict the important attributes of testing process and monitor the efficiency and performance of testing process by tracking and analyzing the actual data.