pairwise generated test cases covers all combinations of two so they are smaller and effective for finding defect.

Orthogonal arrays are used to identify pair wise defect.

It is useful to detect pair wise defects and they can reduce redundancy.

1.  Derive top-level product requirements or technical characteristics from customer needs.

2.  Develop product concepts to satisfy these requirements.

3.  Evaluate product concepts to select most optimum (Concept Selection Matrix).

4.  Partition system concept or architecture into subsystems or assemblies and flow-down higher- level requirements or technical characteristics to these subsystems or assemblies.

5.  Derive lower-level product requirements (assembly or part characteristics) and specifications from subsystem/assembly requirements (Assembly/Part Deployment Matrix).

6.  For critical assemblies or parts, flow-down lower-level product requirements (assembly or part characteristics) to process planning.

7.  Determine manufacturing process steps to meet these assembly or part characteristics.

8.  Based in these process steps, determine set-up requirements, process controls and quality controls to assure achievement of these critical assembly or part characteristics.

[SOURCE -www.npd-solutions.com/qfdsteps.htm ]

5 Vote(s) ]]> http://commoninterview.com/Testing_Interview_Questions/explain-iterative-model-incremental-model-spiral-model-evolutionary-model-and-v-model--1/ http://commoninterview.com/Testing_Interview_Questions/explain-iterative-model-incremental-model-spiral-model-evolutionary-model-and-v-model--1/ Fri, 18 Jun 2010 11:01:58 -0600 priyanka Testing and QA Interview Questions http://commoninterview.com/Testing_Interview_Questions/explain-iterative-model-incremental-model-spiral-model-evolutionary-model-and-v-model--1/

• Requirement stage - Acceptance test 



• Specification stage - System test documents



• Design stage - Integration test



• Coding stage - Unit test

Different Teams work in parallel for each small phase and integrates at the end of the project.

• Requirement Analysis


• Design


• Implementation


• Testing


• Integration


• Maintaianence

Implementation -It is the task performed according to a process. This is the initial stage when the organization implements any new process. 

Institutionalization - It is the task performed according to an organization standard.It is an ongoing process of implementation.

Based on them TPA are calculated.

• Conducting formal Interviews with the leads and the team members


• Documents prepared by the team while following the model


• Conducting survey and questionnaires

• Employee salary and compensation


• Cost of the tools required to implement process including hardware and software


• Cost to provide training


• Vendors, outsourcing  or consultant fees


• Penalties for failure

• Critical - System failure, System crash, Show stopper


• Major - Major functionalities doesn't work


• Minor - Low impact on the system, Cosmetics defects

Continuous Model - In this model processes are individually improved along a capability scale independent of each other.It provides flexibility for organizations to choose which processes to emphasize for improvement . It has 6 capability levels - Incomplete, Performed, Managed, Defined, Quantitatively managed and Optimizing.

Maturity level of a process defines the nature and maturity present in the organization. These levels help to understand and set a benchmark for the organization.

• Level 1 Initial – Processes are characterized as chaotic and adhoc, heroic efforts required by individuals to successfully complete projects. A few Processes are in place; successes may not be repeatable.


• Level 2 Managed – An organization have installed basic management controls. Software project tracking, requirements management, realistic planning, and configuration management processes are in place,  At level 2 organization are summarized as Disciplined as they get the ability to successfully repeat planning and tracking.


• Level 3 Defined- standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is in place to oversee software processes, and training programs are used to ensure understanding and compliance. Cost, schedule and functionality are under control.


• Level 4 Quantitatively Managed – Processes are integrated as whole, metrics are used to track productivity, processes and products.  Project performance is predictable and quality is consistently high.


• Level 5 Optimizing - The focus is on continuous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required. The Project strive to improve the process capability and process performance.

Champions - They have daya to day responsibility for business process being improved. They make sure the Six sigma project team has the required resources to execute their tasks.

Master Black belt - They address the most complex process improvement projects and provide guidelines and training to black belts and green belts.

Green belts - Greens belts assist black belts. They have enough knowledge of six sigma.They apply six sigma methodologies at bottom level to solve problems and improve process

Black belts - They work as team lead or project manager of project chosen for six sigma.Black belts selects projects and train resources, and implement it. They find out the variations and see how to minimize them.

1. Scripts are tedious to maintain. They need to be changed and maintained every time there was any change in system.

2. No proper training was availaible

3. Programming was difficult

The basic roles are as follows

• QA manager - Manages the Testing activities, Owner of the project, manages the team efforts


• Team lead - Prepares Test plan, Assign task to team members, tracks everyday activity, manages test reports, manages test deliverables, 


• Senior Test Engineer - Designing test cases, Defect tracking , designing scripts, focuses on functional testing, Reviews


• Test engineer - Executes test case, focuses on regression testing, Defect tracking

• Tracking number


• Equipment description, type, model


• Location


• Calibration Intervals


• Calibration procedure


• Calibration history


• Calibration Due

A software process is a set of activities that includes all effort to produce a software/product . A process is used by an organization or project to plan, manage, execute, monitor, control, and improve its software related activities.

It is divided in four quadrants

1. Condition


2. Condition alternatives/combinations


3. Action


4. Action entries

Causes = Condition

 Effect = Actions/expected results

The intention is to crash the system with garbage data.

It is an useful tool during testing to capture system requirements that describe states and their associated transitions.It lists all possible state transition combinations not just the valid ones, it unveils combinations that were not identified or documented or dealth with in the requirements. Its beneficial to discover theses defect before coding begins.Using it can help detect defect in implementation that enable invalid path from one state to another

1. Identify the SSH client

 2. Login to remote host

 3. Debugg on remote host by running sshd in debug mode

This model follows completion of logical sequence of stages/phases. The output of one stage becomes input for the next stage.

The following are the steps

Planning -  Project management plan and other planning documents are developed.

Requirements Analysis - Functional requirements documents  and user requirement documents are developed

Design - Detailed requirements are transformed into complete detailed System designs.

Implementation - Development environment is setup, System designs are converted in code.

Integration and testing - Code are integrated and tested for defects

Operations and maintenance - operate and maintain the system in production environment and post delivery in customer environment.

• Test plan


• Traceability matrix


• Test cases 


• Test Scenarios


• Test scripts


• Test data


• Test Results


• Defect log


• Test Summary report


• Release notes

It acess source code of a program and identify the suitable criteria first needed to be defined based on the following criteria

1. Functional coverage - identifies how many functions were executed


2. Statement or line coverage - identifies the number of lines in source code were executed


3. condition/decision coverage - identifies number of loop condition executed


4. Entry and exit coverage - identifies functions or procedures executed from beginning to the end


5. Path coverage - identifies all possible paths from a given starting point in the code has been executed.

Risk analysis can be done in the following steps

1. Identify the risk analysis team


2. Identify risks - Creation of risk scenarios and checklist


3. Estimate the magnitude of the risk by using formulas


4. Select testing priorities - rank the risk and act on it

The ratio of the number of seeded defect detected to the total number of defects seeded provides a rough idea of the total number of unseeded defects that have been detected.