iSQI CTFL_Syll2018 Exam Questions

This scenario is using a walkthrough review type and a perspective-based review technique. A walkthrough is a type of review that is relatively informal and led by the author of the work product. A perspective-based review technique is a technique that involves reviewing the work product from different viewpoints or perspectives of various stakeholders. The scenario matches these descriptions, as it involves an informal approach, a meeting leader who is the author of the requirements document, and a goal of improving the software application's usability and accessibility by considering the various stakeholders' viewpoints. Option A is incorrect, as a pair review is a type of review that involves only two people, usually the author and another team member. Option C is incorrect, as a checklist-based review technique is a technique that involves reviewing the work product against a predefined list of items or criteria. Option D is incorrect, as it combines the incorrect descriptions of options A and C.

Priority is an important item of information that is missing from the incident report. Priority indicates the importance or urgency of resolving the incident, based on the business needs and the impact on the stakeholders. Priority is usually assigned by the project manager or the customer, and it helps to determine the order in which incidents should be addressed. Priority may differ from severity, which indicates the degree of impact of the incident on the system or the component under test. Severity is usually assigned by the tester or the developer, and it helps to assess the risk of the incident. For example, an incident may have a high severity but a low priority, if it affects a critical function but only occurs in a rare situation. Conversely, an incident may have a low severity but a high priority, if it affects a minor function but occurs frequently or affects many users. Therefore, both priority and severity are useful information for incident management and resolution.

The other options are not essential information for the incident report, although they may be helpful or desirable in some cases. Recommendations are suggestions or proposals for resolving the incident, which may be provided by the tester, the developer, or other stakeholders. However, recommendations are not mandatory, and they may not be feasible or acceptable in some situations. Name of tester is the identifier of the person who reported the incident, which may be useful for communication or accountability purposes. However, name of tester is not critical, and it may be replaced by other identifiers, such as email address, employee number, or role. Change history is the record of the changes made to the incident report, such as status, resolution, or comments. Change history is valuable for tracking and auditing purposes, but it is not part of the initial incident report, rather it is updated as the incident progresses.

it provides the highest level of transition coverage for the model.Transition coverage is a white-box test technique that focuses on the percentage of transitions that have been exercised by a test suite1. In this case, the model is a state transition diagram that shows the possible states and transitions of a sales order software. The diagram has five states: PLACED, IN PRODUCTION, SHIPPED, INVOICED, and CANCELLED. The diagram has nine transitions: PLACED to IN PRODUCTION, PLACED to CANCELLED, IN PRODUCTION to SHIPPED, IN PRODUCTION to CANCELLED, SHIPPED to INVOICED, SHIPPED to CANCELLED, INVOICED to CANCELLED, CANCELLED to PLACED, and CANCELLED to IN PRODUCTION. Option C covers all nine transitions in the following sequence:

IN PRODUCTION -> SHIPPED

SHIPPED -> INVOICED

INVOICED -> CANCELLED

CANCELLED -> PLACED

PLACED -> IN PRODUCTION

Option A covers only six transitions in the following sequence:

PLACED -> CANCELLED

CANCELLED -> PLACED

PLACED -> IN PRODUCTION

IN PRODUCTION -> CANCELLED

Option B covers only five transitions in the following sequence:

PLACED -> IN PRODUCTION

IN PRODUCTION -> SHIPPED

SHIPPED -> CANCELLED

CANCELLED -> PLACED

Option D covers only four transitions in the following sequence:

IN PRODUCTION -> CANCELLED

CANCELLED -> PLACED

PLACED -> IN PRODUCTION

Therefore, option C is the correct answer.Options A, B, and D are incorrect, as they do not cover all the transitions in the model. Reference:1, Section 4.2.2

The correct answer is D, as it describes a test summary report for executive-level employees.A test summary report is a document that summarizes the results and evaluation of testing activities for a specific activity or phase3.It may have different levels of detail and content depending on the intended audience and purpose3.A test summary report for executive-level employees is typically high-level and includes a status summary of defects by priority or budget3.This type of report provides a concise overview of the quality and progress of testing without going into too much detail or technical information3. Option A is incorrect, as it describes a test summary report for technical-level employees.A test summary report for technical-level employees is typically detailed and includes specific information on defects and trends3.This type of report provides a comprehensive analysis of the quality and progress of testing with relevant data and metrics3. Option B is incorrect, as it describes a test summary report that is neither suitable for executive-level nor technical-level employees.A test summary report that is detailed and includes a status summary of defects by priority or budget is too detailed for executive-level employees and too vague for technical-level employees3. Option C is incorrect, as it describes a test summary report that is neither suitable for executive-level nor technical-level employees.A test summary report that is high-level and includes specific information on defects and trends is too high-level for technical-level employees and too specific for executive-level employees3. Reference:3, Section 2.7

The correct answer is B, as it defines risk level correctly.Risk level is determined by the likelihood of an event happening and the impact or harm from that event4.Likelihood is the probability or frequency of the event occurring4.Impact is the severity or consequence of the event occurring4.Risk level can be calculated by multiplying likelihood and impact, or by using a risk matrix that assigns risk levels based on different combinations of likelihood and impact4. Option A is incorrect, as it does not define risk level correctly.Risk level is not calculated by adding the probabilities of all planned risks to a project, but by assessing the likelihood and impact of each individual risk4. Option C is incorrect, as it does not define risk level correctly.Risk level is not calculated by dividing the sum of all known risks by the sum of all unknown risks, but by assessing the likelihood and impact of each individual risk4. Option D is incorrect, as it does not define risk level correctly.Risk level is not determined by calculating the absolute value of the sum of all potential issues that may occur on the project, but by assessing the likelihood and impact of each individual risk4. Reference:4, Section 2.8