Download Link for your Favorite E-Book is at the End of this Page ***********************************************************************************ISTQB Advanced Test Manager Exam Preparation (Part 1)

Prior to appearing for exam for ISTQB certification, it is wise to quickly brush up your knowledge by reviewing the following testing related terms that are extremely important from examination point of view.

Part 1 of 12

Q. 1: What is a Technical Review?

A Technical Review (also known as a peer review), is considered to be a formal review type, even though no Managers are expected to attend. It involves a structured encounter, in which a peer/s analyze the work with a view to improve

A walkthrough is a set of procedures and techniques designed for a peer group, lead by the author to review software code. It is considered to be a fairly informal type of review. The walkthrough takes the form a meeting, normally between one and two hours in length.

# Led by the Author# Attended by a peer group# Varying level of formality# Knowledge gathering# Defect finding

<<<<<< =================== >>>>>>

Q. 3: What is anInspection Review?

An inspection is a formal type of review. It requires preparation on the part the review team members before the inspection meeting takes place. A follow-up stage is also a requirement of the inspection. This ensures that any re-working is carried out correctly.

# Led by a Moderator# Attended by specified roles# Metrics are included# Formal process# Entry and Exit Criteria# Defect finding

<<<<<< =================== >>>>>>

Q. 4: What is an Informal Review?

An informal review is an extremely popular choice early on in the development lifecycle of both software and documentation. The review is commonly performed by peer or someone with relevant experience, and should be informal and brief.

Software Validation and Verification can involve analysis, reviewing, demonstrating or testing of all software developments. This will include the development process and the development product itself. Verification and Validation is normally carried out at the end of the development lifecycle (after all software developing is complete). But it can also be performed much earlier on in the development lifecycle by simply using reviews.

<<<<<< =================== >>>>>>

Q. 6: What is Validation?

Validation involves the actual testing. This should take place after verification phase has been completed.

Validation:

confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use have been fulfilled.

Validation:

Are we building the right product?

<<<<<< =================== >>>>>>

Q. 7: What is Verification?

Verification would normally involve meetings and reviews and to evaluate the documents, plans, requirements and specifications. This can be achieved by using reviews and meetings etc.

Verification:

confirmation by examination and provision of objective evidence that specified requirements have been fulfilled.

Verification:

Are we building the product right?

<<<<<< =================== >>>>>>

Q. 8: What is a Waterfall Model?

The Waterfall model is also known as the ‘Sequential model’. Each stage follows on from the previous one. The testing is performed in ‘block’ as the last stage.

Planning or Test creation is not considered until the actual software code has been written. This can result in problems being found much later in the project lifecycle than is desirable.

<<<<<< =================== >>>>>>

Q. 9: What is a V – Model

The V-Model is an industry standard framework that shows clearly the software development lifecycle in relation to testing. It also highlights the fact that the testing is just as important as the software development itself. The relationships between development and testing are clearly defined.

The V-Model improves the presence of the testing activities to display a more balanced approach.

<<<<<< =================== >>>>>>

Q. 10: What is a Spiral Model?

The Spiral model is an incremental testing approach to both Development and Testing. This is used most effectively when the users do not know all of the requirements. From what is known, initial requirements can be defined. Then from these the code and test cases are created. As time goes on, more details of the requirements are known and implemented in further iterations of design, coding and testing phases. The system is considered to be complete, when enough of the iterations have taken place.