Questions

Quality Assurance Manager (QA Manager) defines the process to be followed at each phase of SDLC. He defines the standards to be followed, the documents to be maintained and sets the standard for the product.

Where as it is the Project Manager’s responsibility to ensure that the things defined by QA manager are being implemented. He develops the product from start to finish with his team and ensures that the product which is to be rolled out is Defect free and it reaches the standards and views defined by QA Manager.

QA managers can audit the process for certain time periods which are being handled by the Project Manager.

 #include<stdio.h>
int main(){
    int num,r,sum=0,temp;

    printf("Enter a number: ");
    scanf("%d",&num);

    temp=num;
    while(num){
         r=num%10;
         num=num/10;
         sum=sum*10+r;
    }
    if(temp==sum)
         printf("%d is a palindrome",temp);
    else
         printf("%d is not a palindrome",temp);

    return 0;
}

Sample output:
Enter a number: 131
131 is a palindrome

In batched operating system the users gives their jobs to the operator who sorts the programs according to their requirements and executes them. This is time consuming but makes the CPU busy all the time.

Scheduler deals with the problem of deciding which of the process in the ready queue is to be allocated the CPU. Short Term Schedulers, Long Term Schedulers

Temperate Cyclones are cyclones of mid-latitudes and hence are primarily under influence of permanent winds of mid-latitudes i.e. westerlies. Their movement is therefore eastwards of their origin with average velocity of 32km per hour in summers and 48km per hour in winters.

Movement of Tropical CyclonesNormally, they move from east to west under the influence of trade winds because trade winds are permanent winds of tropical latitudes. The general direction is therefore westwards from their origin. They advance with varying velocities. Weak cyclones move at the speed of about 32km per hour while hurricanes attain the velocity of 180km per hour or more.

Code coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs.

Integration testing is done at module level when various modules are integrated with each other to form a system or sub-system. Its main purpose is to ensure that interfaces between various modules are working properly; i.e. modules which are working individually are also working correctly together.

System testing is done on a complete, integrated system to evaluate the system’s compliance with its specified requirements. It validates that the system meets its functional and non-functional requirements.

From these definitions, it is clear that the purpose of Integration and purpose of System Testing are different. Therefore, Integration test cases focus more on the interfaces between modules (interface integrity) - the data transfer and their interaction with each other. System test cases focus on testing the product as a whole; i.e. whether the functional, non-functional requirements of the System are met or not. Since System Testing is the final phase before delivery of the product, System test cases should pinpoint configuration related errors along with testing for performance, security, reliability etc.