Free and Premium ISTQB CTFL-Foundation Dumps Questions Answers

A test completion criterion is used to determine when testing activities can be concluded. According to the ISTQB Certified Tester Foundation Level Syllabus v4.0, setting test completion criteria helps in defining when the testing objectives have been achieved, which includes reaching a defined coverage level, running out of time or budget, or meeting the expected level of risk acceptance. These criteria are essential for ensuring that the testing process is concluded appropriately and resources are utilized effectively.

The odd one out among the given options is "Functional". The other options—White box, Glass box, and Structural—refer to testing techniques that involve examining the internal structure of the application. In contrast, functional testing focuses on testing the software against its functional requirements without considering its internal structures​​.

Sometimes time/money does signify the end of testing, but it is really complete when everything that was set out in advance has been achieved.

Testing is considered complete when sufficient information has been gathered to assess the quality of the software and to make an informed decision about its release. This includes understanding the risks of any remaining defects, the test coverage achieved, and the test results. It is not practical to wait until all possible test cases have been executed or until no defects remain, as these conditions are often impossible to meet within typical project constraints.

Non-functional requirements define how the system performs a certain function, rather than specific behaviors or functions of the system. Security, performance, usability, reliability, and maintainability are common examples of non-functional requirements. Ensuring the security of customer details is a non-functional requirement because it specifies a quality attribute that the system must have. Reference: ISTQB CTFL Syllabus V4.0, Section 4.1​​.

Designing the test environment setup and identifying any required infrastructure and tools are part of the "Test Analysis and Design" phase. According to the ISTQB Certified Tester Foundation Level Syllabus v4.0, the activities in this phase include creating high-level and detailed test designs, test cases, and test data, and specifying the necessary test environment, tools, and infrastructure. These preparations are essential for the subsequent phases of test execution and monitoring.

Incremental testing approaches involve testing components of the software in increments or steps, allowing for integration and testing of parts of the system progressively. According to the ISTQB CTFL Syllabus, version 4.0, the common types of incremental testing approaches include:

Top-down: Testing starts from the top of the module hierarchy and progresses downwards.

Bottom-up: Testing begins with the lower-level modules and progresses upwards.

Functional incrementation: Adding and testing one function at a time.

Big-bang testing, however, is not an incremental approach. In big-bang testing, all components or modules are integrated simultaneously, and the system is tested as a whole. This approach does not allow for incremental testing and integration and is therefore not considered a type of incremental testing approach​​.

Reviewing the test basis is a key activity in the Test Analysis and Design phase. This phase involves analyzing the test basis documents (such as requirements, design specifications, and use cases) to identify test conditions and design test cases. The ISTQB CTFL Syllabus explains that thorough review of the test basis ensures that the tests are aligned with the specified requirements and design, improving the accuracy and relevance of the tests​​.

Evaluating the testability of requirements (i) and developing and prioritizing test cases (iv) are part of the test analysis and design activities. Repeating testing activities after changes (ii), designing the test environment set-up (iii), and verifying the environment is set up correctly (v) are part of the test implementation and execution activities. These distinctions are part of the fundamental test process, which ensures that each phase of testing is appropriately planned and executed. Reference: ISTQB CTFL Syllabus V4.0, Section 1.4.1​​.

A risk-based approach to testing provides information on the types of test techniques to be employed. This approach prioritizes the testing of features and functions based on their risk of failure and their impact on the organization. By identifying the areas of highest risk, test managers can allocate resources and select test techniques that are most likely to uncover defects in these critical areas. This approach ensures that testing efforts are focused where they are most needed. Reference: ISTQB CTFL Syllabus V4.0, Section 5.2 .QUESTION NO: 85

When assembling a test team to work on an enhancement to an existing system, which of the following has the highest level of test independence?

A. A business analyst who wrote the original requirements for the system.

B. A permanent programmer who reviewed some of the new code, but has not written any of it.

C. A permanent tester who found most defects in the original system.

D. A contract tester who has never worked for the organization before.

Answer: D

In this scenario, the contract tester who has never worked for the organization before has the highest level of test independence. The three others are less independent as they are likely to make assumptions based on their previous knowledge of the requirements, code and general functionality of the original system.

Note that independence does not necessarily equate to most useful. In practice most test or project managers would recruit a permanent tester who has worked on the original system in preference to a contract tester with no knowledge of the system. However, when assembling a team it would be useful to have staff with varying levels of test independence and system knowledge.

Independent Verification & Validation (IV&V) is performed by an entity outside the project's sphere of influence to provide an unbiased assessment of the software product. This independence helps ensure that the verification and validation processes are objective and not influenced by the project's internal dynamics. Reference: ISTQB CTFL Syllabus V4.0, Section 1.4.1​​.

Iterative development involves users in the testing throughout the development process. This approach allows for continuous feedback from users, ensuring that the evolving system meets user requirements and expectations. Unlike the traditional waterfall model, iterative development accommodates changes and improvements based on user feedback, making it suitable for dynamic environments like website development. Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.3​​.

The implementation and execution phase of the fundamental test process involves the execution of the tests according to the test plan, where the main task is to compare the actual results of the test execution against the expected results. This phase ensures that the tests are carried out and the discrepancies between the actual and expected outcomes are identified and documented. This information is critical to determining whether the software behaves as intended and meets the specified requirements.

Testing should be stopped based on risk criteria defined for the system being tested. The ISTQB CTFL syllabus v4.0 outlines that the decision to stop testing is influenced by risk levels, coverage achieved, time and budget constraints, and the criticality of the system under test. Stopping criteria should ensure that the risk of remaining defects is acceptable for the project stakeholders​​.

The main purpose of the component build and integration strategy is to specify which components to combine when, and how many at once. This strategy helps manage the complexity of integrating different parts of the system by providing a structured approach to combining components incrementally. It ensures that integration is done systematically, reducing the risk of integration issues and making it easier to identify and resolve problems as they arise​​.

Top of Form

Bottom of Form

The highest level of risk is calculated by considering both the likelihood of failure and the impact value. Risk can be quantified as the product of these two factors:

A: 20% * £100,000 = £20,000

B: 10% * £150,000 = £15,000

C: 1% * £500,000 = £5,000

D: 2% * £200,000 = £4,000

Therefore, Option A (20% likelihood of failure and £100,000 impact value) represents the highest risk value. Reference: ISTQB CTFL Syllabus V4.0, Section 5.2.3 .

Non-functional testing is focused on testing the attributes of a system such as usability, reliability, maintainability, performance, and security. These attributes define how the system operates rather than what the system does. Non-functional testing ensures that the software meets certain criteria that are critical to its operational performance and user satisfaction​​.

Non-functional system testing evaluates various quality attributes of a system rather than specific behaviors or functionalities. According to the ISTQB CTFL Syllabus, version 4.0, non-functional testing encompasses several critical aspects:

Performance testingevaluates how the system performs under different conditions, such as load and stress, to ensure it meets performance requirements.

Usability testingassesses the user-friendliness and overall user experience of the system, ensuring that it is intuitive and accessible for end-users.

The syllabus outlines that non-functional system testing includes testing the quality attributes of the system, which goes beyond just functionality and delves into performance, usability, reliability, and other key attributes​​.

The test basis for integration testing typically includes technical specifications. According to the ISTQB CTFL syllabus v4.0, integration testing focuses on the interactions between components or systems, and the technical specification provides the necessary details about these interactions and interfaces​​.

Configuration management involves practices like status accounting of configuration items, identification of test versions, record of changes to documentation over time, and controlled library access. However, auditing conformance to ISO9001 is related to quality management and not specifically part of configuration management​​.

Early test design can prevent fault multiplication, find faults, and cause changes to the requirements. The ISTQB CTFL syllabus v4.0 explains that starting test design early in the lifecycle helps to identify defects sooner, which can prevent the propagation of defects into later stages and reduce the overall cost of fixing them. While it can influence the requirements, it does not necessarily take more effort, and faults found early are typically less expensive to fix than those found later​​.

The cost of fixing a fault increases as the software progresses through the development lifecycle. Fixing defects identified early in the requirements or design phases is less expensive compared to fixing those found later in testing or after the software has been deployed. This is due to the larger impact on the system, more extensive rework required, and potential disruptions to the user experience in later stages.

The typical sequence of formal review activities includes planning, kick-off, individual preparation, and review meeting. The planning phase sets the scope and objectives, the kick-off initiates the review process, individual preparation involves participants reviewing the materials on their own, and then the review meeting is held to discuss the findings. Reference: ISTQB CTFL Syllabus V4.0, Section 3.2.2​​.

Maintenance testing is performed on an existing operational system that has undergone planned enhancements, corrections, or other modifications. The goal is to ensure that the changes have been implemented correctly and that the system continues to function as intended. This type of testing is not typically used for defect correction during development, user acceptance testing complaints, or the integration of functions in new system development​​.

Debugging is the process that developers follow to find, analyze, and fix the root causes of defects in the software. This includes identifying the source of the problem, correcting the code, and then testing the changes to ensure the defect has been properly fixed and that the fix does not introduce new issues.

A disadvantage of independent testing is that developers might lose a sense of responsibility for the quality of their work. When developers rely too much on independent testers to find defects, they may become less diligent in their own testing and quality assurance efforts. The ISTQB CTFL Syllabus points out that while independent testing can provide an unbiased perspective and identify defects that might be missed by developers, it can also lead to potential downsides such as diminished developer accountability​​.

Variance from programming standards defects (option (A)) are found during the review or static testing process. Therefore a test harness is unlikely to find a defect in programming standards.

Memory leak defects (option (C)) could potentially be found by a test harness designed to run many test cases.

Regression defects (option (D)) could be found using many types of test tool.

Defects in middleware (option (B)) are generally more likely to be found by a test harness or a dynamic analysis tool than by any other type of tool.

Regression testing is designed to verify that recent code changes have not adversely affected existing functionality. It is particularly well-suited for test automation because automated tests can be rerun quickly and consistently. While regression tests are essential in many testing phases, they are distinct from acceptance testing, which focuses on validating that the system meets business requirements.

Test planning involves defining the overall approach to testing, including setting objectives, strategies, and resources. It ensures that the level of detail in test procedures is appropriate for the subsequent test execution phase. Effective test planning helps in aligning the testing activities with the project goals and ensures that the tests are executed as per the defined procedures.

The application failed due to a defect in the purchase identification module. This defect could have been caused by a programmer mistake or an error in the specification. The incorrect counting of purchase attempts indicates a flaw in the logic or implementation of the module responsible for identifying successful purchases.

Effective ways to improve communication and relationships between testers and other team members include communicating factual information in a constructive way (a) and trying to understand how the other person feels and why they react the way they do (b). These approaches foster a collaborative and empathetic environment, reducing friction and enhancing teamwork.

For user acceptance testing (UAT) of the first release of a new software product aimed at a general market and built using Agile methods, appropriate test objectives would be to ensure the product works as expected (c) and to assess the overall quality of the product (d). These objectives focus on validating that the software meets user needs and overall quality standards.

A technical review is a formal type of review that focuses on discussing, making decisions, evaluating alternatives, finding defects, solving technical problems, and checking conformance to specifications, plans, regulations, and standards. It is typically conducted by a team of experts and aims to ensure the technical quality of the product.

Maintenance testing is conducted on the software after it has been delivered to address any issues or changes required due to defects, environment changes, or new requirements. The ISTQB syllabus explains that maintenance testing typically involves impact analysis to determine the extent of regression testing required, thus optimizing the testing effort and focusing on affected areas​​.

The task "verify the test environment set up is correct" relates to the Implementation and Execution phase of the fundamental test process. This phase includes setting up the test environment, creating test data, and executing test cases.

Experience-based test design techniques rely on the tester's skill, intuition, and experience to derive test cases. Techniques like error guessing and exploratory testing fall under this category. These methods do not depend on formal specifications but rather on the tester's understanding of the system and potential areas where defects might exist.

White box testing techniques, also known as structure-based techniques, focus on the internal structure of the software. Decision testing (C) is a white box technique that involves creating test cases to execute specific decision points in the code, such as conditional statements. This ensures that all possible paths through the code are tested, helping to identify defects related to the control flow of the application. Other techniques listed, such as use case testing and state transition testing, are black box techniques that focus on the software's functionality from the user's perspective​​.

The failure rate in testing already completed is a useful metric to monitor progress along with test preparation and execution. It provides insight into the effectiveness of the tests and the quality of the product, helping to identify areas that may require additional attention or resources.

It is generally not feasible to perform exhaustive testing due to time and resource constraints. Instead, testing efforts should be focused using risk analysis and priorities to ensure the most critical areas are tested thoroughly. This approach helps in maximizing the effectiveness of the testing process while managing resources efficiently.

Decision table testing is a black-box test design technique used to test system requirements and to ensure that different combinations of inputs result in appropriate outputs. It is especially useful for testing complex business logic and rules where various combinations of conditions need to be verified.

Debugging is the process where developers identify, locate, and correct defects. Testers are then responsible for confirming that the correction has resolved the original defect. This separation of responsibilities ensures that defects are properly fixed and verified.

Maintenance testing is essential when there is a need to ensure that the software continues to function correctly after it has been modified. Migration to a new platform is a significant change that can impact the software's functionality, requiring thorough maintenance testing to verify that the software performs as expected in the new environment. This ensures that any platform-specific issues are identified and resolved​​.

One limitation of static analysis tools is that they tend to generate a large number of warning messages when applied to new code. This can occur even if the code meets established coding standards, as the tools are designed to identify a wide range of potential issues, leading to a high volume of output that needs to be reviewed and addressed.

Integration testing focuses on the interactions between integrated components or systems. It aims to identify defects in the interfaces and interaction points between different parts of the system. According to the ISTQB syllabus, the test basis for integration testing typically includes software and system design documents, while the test objects are the interfaces and interactions between components. The goal is to ensure that the integrated parts function together as intended​​.

A data-driven approach to test automation design involves separating the test data inputs from the test scripts. This approach allows the same generic script to read different sets of test data and execute the same test steps with various inputs. This method enhances reusability and efficiency in automated testing by allowing testers to run multiple test scenarios using the same script but different data sets​​.

To achieve 100% statement coverage and 100% decision coverage for the provided pseudo code, at least two test cases are required. The first test case should cover the scenario where X > Y, which will execute the statements in the "if" branch. The second test case should cover the scenario where X ≤ Y, which will execute the statements in the "else" branch. This ensures that both the true and false branches of the decision are tested, and all statements in the code are executed at least once.

Equivalence Partitioning is a black-box testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. It helps in reducing the number of test cases while maintaining adequate test coverage.

Experience-based techniques rely on the testers' knowledge, skills, and experience, as well as insights from developers and users, to design test cases. These techniques do not depend on formal models or the internal structure of the software but rather on practical experience and understanding of how the software is likely to be used and where defects are likely to be found​​.

A test condition is defined as an item or event that can be verified by one or more test cases. It can include functions, transactions, structural elements, or quality attributes that need to be tested to ensure the system behaves as expected.

The selection of a software development model should be based on the specific characteristics of the product and project. Factors such as project size, complexity, requirements stability, and team expertise influence the choice of the most suitable development model. The ISTQB syllabus explains that there is no one-size-fits-all approach, and the decision should be tailored to the context and needs of the project​​.

In formal reviews, such as inspections, the role of the moderator is crucial. The moderator is responsible for leading the review process, ensuring that the review is conducted according to the defined procedures, and facilitating the review meeting. The ISTQB syllabus highlights that the moderator's role is to guide the review team, manage any issues that arise during the review, and ensure that the objectives of the review are met​​.

In state transition testing, test cases are designed to execute specific sequences of state transitions. Referring to the provided state transition diagram:

For test case (i) X-Z-V-W, the corresponding state transitions are S1 (X) → S2, S2 (Z) → S3, S3 (V) → S4, and S4 (W) → S2. Therefore, the sequence of state transitions is S1 – S2 – S3 – S4 – S2.

For test case (ii) W-Y-U-U, the corresponding state transitions are S4 (W) → S2, S2 (Y) → S4, S4 (U) → S4, and S4 (U) → S4. Therefore, the sequence of state transitions is S4 – S2 – S4 – S4 – S4.

This ensures that the transitions accurately reflect the states and paths described in the test cases.

An incident report should include additional details such as the status of the incident (e.g., new, open, closed), the degree of impact (e.g., critical, major, minor), and the Test Case Number to provide a complete understanding of the context and severity of the issue.

System testing is a level of software testing where a complete and integrated software is tested. The purpose of this test is to evaluate the system's compliance with the specified requirements. System testing is conducted on the entire system to verify that it behaves as expected and meets the functional and non-functional requirements defined in the scope of the project.

To meet the test plan requirements and logical dependencies, the test schedule should start with re-tests (those that have previously failed), followed by the highest priority tests. Additionally, tests should be scheduled to create necessary test data for subsequent tests. In this case, teste(log in as admin user and create a standard user) must be done first as it is necessary to perform all other actions. Following this, testa(log in as standard user and create customer account) creates the standard user needed for subsequent actions. Then, the highest priority testd(order twoitems or more), which has failed before, should be executed next, followed by testc(create invoice for order), and finally testb(order one item)​​.

Maintenance testing is typically triggered by changes to the operational system, such as data migration, system modification, or system retirement. These triggers require testing to ensure that the changes do not negatively impact the existing functionality. However, the introduction of a test management tool does not directly affect the operational system and is not considered a trigger for maintenance testing​​.

Equivalence partitioning is a black-box test design technique that divides input data into partitions that are expected to be treated similarly by the system. In this case, 0600 falls into the peak-time tariff, 1000 is at the boundary of peak-time but still included in it, and 1200 falls into the off-peak tariff. This ensures that each input is from a different equivalence partition, testing different functional areas of the system​​.

Load testing is a type of non-functional testing used to verify that the system can handle a specified load of users performing transactions within acceptable performance parameters. In this case, load testing would ensure that up to 100 users can carry out transactions simultaneously with response times within 5 seconds. This testing helps identify performance bottlenecks and ensure that the system meets the performance requirements under expected user load conditions​​.

During the test planning stage, it is important to assign resources for the planned activities. This ensures that the necessary personnel, equipment, and time are allocated to execute the test plan effectively. Analyzing the test basis, designing test environments, and writing a test execution schedule are activities that come after the initial planning and resource allocation​​.

The level of risk is determined by evaluating both the impact and the likelihood of an adverse event occurring. This approach ensures that both the severity of potential consequences and the probability of the event are considered. The impact assesses how serious the consequences would be if the event happened, while the likelihood evaluates how probable it is that the event will occur. This combination provides a comprehensive measure of risk, helping organizations prioritize their risk management efforts effectively​​.

According to the decision table, Test Case 1 is valid because an employee who is not a car or motorcycle driver cannot claim expenses, as shown in Rule 1. Test Case 3 is valid because a motorcycle driver can claim expenses, as indicated in Rule 2, with expenses claim band A. However, Test Case 2 is invalid because, according to Rule 5, a car driver with a diesel engine greater than 1600cc cannot claim expenses. The expected result should be that the expense claim is not allowed, not band C​​.

Exploratory testing is highly effective when under severe time pressure because it allows testers to simultaneously learn, design, and execute tests. It is a flexible approach that does not require extensive preparation and documentation, making it ideal for situations where time is limited​​.

An independent test function in an organization helps improve defect finding during reviews and testing by providing an unbiased perspective on the software. Independent testers are not influenced by the development team’s constraints and can evaluate the software more objectively. This leads to the identification of defects that might be overlooked by developers who are too close to their own code. Independent testing enhances the quality and reliability of the software by bringing fresh insights and ensuring thorough testing​​.

The amount of testing effort is highly influenced by the predicted number of defects and the subsequent amount of rework required. If a high number of defects are expected, more effort will be needed to identify, document, and retest the defects after they are fixed. This impacts the overall testing workload significantly compared to other factors such as the ratio of developers to testers, which affects team dynamics but not the core testing effort​​.

Static analysis tools are designed to analyze code without executing it. They are highly effective at identifying issues such as syntax errors, variable declaration, and usage problems. Options A, B, and D are types of defects that static analysis tools can typically detect because they relate to the code structure and syntax. However, Option C refers to a variable having the wrong numeric value passed into it, which is more of a logical error that typically requires dynamic testing to identify. Static analysis tools cannot understand the correct logical flow or expected values in the code, thus making Option C the correct answer​​ .

Static analysis tools are designed to analyze code without executing it. They are particularly good at finding defects related to code structure, such as variables that are not used or improperly declared. These tools can parse the code and identify issues that may not be easily detected through dynamic testing methods. Other issues like omission of a major requirement (A), inadequate decision coverage (B), and component memory leakage (C) are typically found through dynamic testing or higher-level verification techniques​​ .

For a system with complex business rules and many branches, decision testing (a white-box technique) is appropriate because it ensures that each decision point (branch) in the code is tested. Equivalence partitioning (a black-box technique) complements this by ensuring that all functional areas (based ondifferent inputs) are adequately tested. This combination provides thorough coverage of both the internal logic and the functional requirements of the system​​.

Measurement of code coverage is important because it helps ensure that all code is exercised by tests. This does not guarantee that there are no coding errors or that all requirements are covered, but it helps identify untested parts of the code, allowing for better test coverage and more robust testing processes​​.

The correct logical order for the test cases ensures a smooth and realistic flow through the system functionalities. The sequence should start with logging into the system (Test Case 3), searching for available flights (Test Case 1), selecting an available flight (Test Case 4), viewing the selected item in My Flights (Test Case 2), confirming details and booking the flight in My Flights (Test Case 6), and finally printing the confirmation receipt and exiting (Test Case 5)​​ .

Top of Form

Bottom of Form

Statement testing is a white-box test technique that involves creating test cases to execute specific statements in the code. The goal is to ensure that all statements in the program are executed at least once during testing. This technique requires knowledge of the internal structure of the code and focuses on verifying the flow of execution and logic within the program​​.

A Test Procedure Specification is a document that outlines the precise steps required to execute a test. It includes detailed instructions on the setup, execution, and teardown of the test environment, as well as the specific actions to be performed and the expected results. This document ensures that tests are conducted consistently and repeatably​​.

Testing is primarily aimed at detecting defects, verifying the functionality, and providing information to stakeholders for decision-making. While investigating defects is part of the testing process, fixing defects is not typically considered an objective of testing; it falls under the development activities. The main objectives of testing include preventing defects (through early testing activities), gaining confidence in the system, and providing valuable information to stakeholders​​.

Writing test summary reports is typically the responsibility of a test leader or manager, who consolidates testing activities and results to communicate with stakeholders. Testers are more involved in preparing and acquiring test data, setting up and checking the test environment, and reviewing tests developed by others. These tasks are more hands-on and technical, aligning with the role of a tester​​ .

Top of Form

Bottom of Form

The correct sequence in the causal chain is "Error, fault, failure". An error (or mistake) made by a person can lead to a fault (or defect) in the software. When the fault is executed, it may cause a failure in the software system. This sequence is important to understand the cause and effect relationship in software testing and defect management​​ .

In the provided state table, an invalid transition is represented by an empty cell. According to the table, Event E from State S4 is an invalid transition as the cell for this combination is empty. This indicates that the transition from State S4 on Event E is not defined​​.

Top of Form

Bottom of Form

Decision coverage is a testing metric used to ensure that all possible paths (decisions) in the code have been executed at least once. It is not used to verify the correctness of module calls, which ismore related to integration testing or control flow testing. Options A, B, and D describe valid uses of decision coverage, ensuring that decisions are exercised in programs, business processes, and measuring the extent of coverage by a test suite​​ .

The highest level of testing independence is achieved when the testing process is performed by individuals or teams who are completely independent of the development team and the organization. Option B, which involves outsourcing test design and execution to a different company, ensures that there is no bias or influence from the development team or company politics, thereby achieving the highest level of testing independence​​.

Good testing practice involves early involvement of testers in the software development process. This helps identify defects early and provides better understanding and clarification of requirements. Involving testers in reviewing requirements or user stories as soon as drafts are available allows for early detection of defects, which is more cost-effective and efficient. This practice is beneficial regardless of the software lifecycle model used​​ .

Top of Form

Bottom of Form

An incident report typically includes the version(s) of the software under test, expected results and actual results, and precise steps to reproduce the problem. However, the test execution schedule is not a standard part of an incident report. It is more relevant to test planning and management documents rather than incident reporting​​.

A keyword-driven testing approach is effective because it separates the test logic (actions) from the test data. This makes the scripts more reusable and easier to maintain. By organizing tests this way, any changes in the data or the actions can be made independently without affecting the other, enhancing the efficiency and manageability of automated tests​​.

The testability of requirements is evaluated during the Test Analysis and Design stage of the fundamental test process. In this stage, the test team reviews the requirements to ensure they are clear, complete, and testable. The focus is on understanding the test basis and defining the test conditions, test cases, and test data necessary to verify the requirements​​.