iSQI CTFL_Syll2018 Dumps

A key difference between a peer review of code and static analysis of code using a tool is that static analysis targets the code technically whereas peer review is applicable to further aspects. Static analysis focuses on the technical aspects of the code, such as syntax, logic, complexity, quality, security, etc. Peer review can also address these aspects, but it can also consider other aspects, such as readability, maintainability, usability, functionality, etc. Peer review can also provide feedback, suggestions, or opinions from different perspectives or expertise levels. compares these two techniques as follows:

Static analysis tools are software tools that examine (analyse) source code without executing it. They are used by developers as part of their development environment for checking their code against coding standards (rules), finding syntax errors etc.

Peer reviews are manual checking activities where work products such as requirements specifications or code are examined by colleagues (peers) for defects.

A, B, and C are incorrect answers. A peer review does not find defects while static analysis finds failures (A), as both techniques can find defects but not failures. Failures are observed at runtime when executing the code. Peer reviews cannot find missing requirements whereas static analysis can (B), as both techniques cannot find missing requirements but only check conformance to existing requirements. Missing requirements can be found by other techniques such as elicitation or validation. A peer review finds failures while static analysis finds defects ©, as both techniques find defects but not failures. Failures are observed at runtime when executing the code.

After completing the tool selection and a successful proof-of-concept, introducing the selected tool into an organization generally starts with a pilot project, which has the following objectives12:

• Gaining in-depth knowledge about the tool, understanding both its strengths and weaknesses
• Evaluating how the tool fits with existing processes and practices, and determining what would need to change
• Assessing whether the benefits will be achieved at reasonable cost
• Identifying and resolving any technical and organizational issues before deploying the tool on a larger scale
• Providing training, coaching, and mentoring for users of the tool
• Defining metrics to measure the success of the tool deployment

Therefore, the option D is the most typical objective of running a pilot project, as it is essential to ensure the compatibility and suitability of the tool with the current way of working, and to identify any potential risks or challenges that may arise from the tool introduction12.

The other options are not typical objectives of running a pilot project, because they are either part of the tool selection process, or the outcomes of the pilot project. They are:

• To establish whether the tool is available for a free trial period (and for how long) (A). This is part of the tool selection process, which involves gathering information about the tool features, costs, support, and availability12. This should be done before running a pilot project, as it helps to narrow down the list of potential tools and to conduct a proof-of-concept12.
• To provide training, coaching, and mentoring for users of the tool (B). This is an outcome of the pilot project, which aims to increase the competence and confidence of the tool users and to facilitate the tool adoption12. This should be done during and after the pilot project, as it helps to ensure the effective and efficient use of the tool and to address any issues or feedback from the users12.
• To develop a clear set of requirements and objective criteria against which the tool can be evaluated ©. This is also part of the tool selection process, which involves defining the tool requirements based on the needs and expectations of the stakeholders, and establishing the evaluation criteria based on the benefits and risks of the tool12. This should also be done before running a pilot project, as it helps to compare and rank the potential tools and to select the most suitable one12.

References:

• ISTQB Foundation Level 2018 syllabus
• Chapter 6 - Tool Support for Testing | PPT

Assigning resources for the planned activities is an activity that is appropriate to the test planning stage, because it involves estimating and allocating the necessary human and physical resources for testing . Test planning is the process of defining the objectives, scope, approach, and resources for testing . The other options are not activities that are appropriate to the test planning stage, but rather to other stages of testing. Option A is an activity that is appropriate to the test analysis stage, because it involves analysing the test basis (such as requirements, design, or code) to identify test conditions . Option C is an activity that is appropriate to the test implementation stage, because it involves designing and preparing the test environments (such as hardware, software, network, or data) for test execution . Option D is an activity that is appropriate to the test execution stage, because it involves writing a test execution schedule that defines the order and dependencies of test cases or procedures .